1399 replies to this topic

[kenbrownstone]

We pulled the link because there were boot looping issues that made the rom unusable.
-Team LiteSpeed- Sent from my FlyingJelly device

cool I will wait for you no matter how long.....lol

[The Persuader]

Yes....no issues other what I mentioned in email...

Working Awesome...

Its Bubba
~Stubborn In Your Bones~
Sent From my FlyingJelly

Its might have something to do when you Wiping Factory...it did happen to me...I've been in slot 1 & 2 in Safestrap no issues

Its Bubba
~Stubborn In Your Bones~
Sent From my FlyingJelly

[The Persuader]

FlyingJelly is still performing Awesome... Its Rock Solid as my Daily Drive not even a Hair-haa of an issue.

Its Bubba
~Stubborn In Your Bones~
Sent From my FlyingJelly

[jgates]

I cant wait to try this... any eta as to when the link will be back?

[prstorero]

I cant wait to try this... any eta as to when the link will be back?

I'm helping t3 fix the boot problem and I may have found it, sent him the apk to put into the zip and flash, if it works you will see it soon

[jgates]

I'm helping t3 fix the boot problem and I may have found it, sent him the apk to put into the zip and flash, if it works you will see it soon

Sounds great! Thanks man

[Gytole]

you guys, deleting the rom slot is not the same as a full partition wipe, theres fragments left over, and if the safestrap folder is still on your sd card after you delete the slot, the slot wasnt "wiped". it's been causing tons of problems with the jb kernel. its borking files on the sd's. I've installed almost every rom first boot while using proper wipes. Boot into stock and wipe internel and external, back up stuff first that you want to keep, I know its a fricking pita, but you might have better results. This roms loaded and is running fine for me, and I got Black Widow to work just fine first boot on proper wipes. could just be my luck...but we swear by wipes. When you delete something, "file fragments" are LEFT over, and they cause problems when files overwrite them. not saying this happens 99% of the time but it's been a high risk factor after the new os, ive suffored from it too, and the only remedy for me has been wiping the internel/external sd's. give it a shot. it takes 5 minutes to boot into stock and wipe them, and to boot back into SS3.11 and create a new rom slot again. it's worth a shot. and fresh stats create a typically worry free install, for me anyways...try it out!

[prstorero]

you guys, deleting the rom slot is not the same as a full partition wipe, theres fragments left over, and if the safestrap folder is still on your sd card after you delete the slot, the slot wasnt "wiped". it's been causing tons of problems with the jb kernel. its borking files on the sd's. I've installed almost every rom first boot while using proper wipes. Boot into stock and wipe internel and external, back up stuff first that you want to keep, I know its a fricking pita, but you might have better results. This roms loaded and is running fine for me, and I got Black Widow to work just fine first boot on proper wipes. could just be my luck...but we swear by wipes. When you delete something, "file fragments" are LEFT over, and they cause problems when files overwrite them. not saying this happens 99% of the time but it's been a high risk factor after the new os, ive suffored from it too, and the only remedy for me has been wiping the internel/external sd's. give it a shot. it takes 5 minutes to boot into stock and wipe them, and to boot back into SS3.11 and create a new rom slot again. it's worth a shot. and fresh stats create a typically worry free install, for me anyways...try it out!

That could very well be the case, but here from what I just finished looking at, I think the booting problem was an apk and jar file. Those who get it did a flash without wipes or got lucky. Roms need their stock framework signature and manifests in order to boot, and it seemed something as messed up there. We will find out when I hear back from t3 with the files I sent him

[satman80]

you guys, deleting the rom slot is not the same as a full partition wipe, theres fragments left over, and if the safestrap folder is still on your sd card after you delete the slot, the slot wasnt "wiped". it's been causing tons of problems with the jb kernel. its borking files on the sd's. I've installed almost every rom first boot while using proper wipes. Boot into stock and wipe internel and external, back up stuff first that you want to keep, I know its a fricking pita, but you might have better results. This roms loaded and is running fine for me, and I got Black Widow to work just fine first boot on proper wipes. could just be my luck...but we swear by wipes. When you delete something, "file fragments" are LEFT over, and they cause problems when files overwrite them. not saying this happens 99% of the time but it's been a high risk factor after the new os, ive suffored from it too, and the only remedy for me has been wiping the internel/external sd's. give it a shot. it takes 5 minutes to boot into stock and wipe them, and to boot back into SS3.11 and create a new rom slot again. it's worth a shot. and fresh stats create a typically worry free install, for me anyways...try it out!

Agree 100% Wipe Wipe Wipe and Wipe, aside from internal and External in SS, then delete Slot then add, then wipe wipe wipe wipe again..

[The Persuader]

If you Wipe Data doesn't this change the Framework ?

Its Bubba
~Stubborn In Your Bones~
Sent From my FlyingJelly

[prstorero]

If you Wipe Data doesn't this change the Framework ?

Its Bubba
~Stubborn In Your Bones~
Sent From my FlyingJelly

Not in a way of effecting the initial boot

[The Persuader]

Not in a way of effecting the initial boot

Would it leave any Residuals from the previous Framework causing boot loop?

Its Bubba
~Stubborn In Your Bones~

[bfederspill]

Would all that wiping be any different for us using dual boot?

Sent from my DROID RAZR using Tapatalk 2

[T3T3droid]

OK guys whew! Thanks to major help from prstorero we got this beast working!!! Ill put to bed all your theories...the fault of the boot loop lies completely on my end. If it booted for you that means you were on a previous beta. this had nothing to do with what kind of wipe you did or if you removed and remade the rom-slot or what slot its put onto. That being said I am uploading now and the MD5 will be ed1191471f748485aa4fedff4abda5d3 and if it isnt please let me know. upload will be done in about 20 min. Thank you guys so much for your patience! YOU GUYS ROCK!!!

[TeamLiteSpeed]

Link is back up guys! If the first one flashed for you please re-flash 1.1 so that you don't run into any issues!

[jp1044]

Here we go guys! This time for reals though.

-Team LiteSpeed- Sent from my FlyingJelly device

[ReSuReKtZ]

Any screen shots?

[T3T3droid]

Any screen shots?

in the OP

[The Persuader]

in the OP

So the protocol to flashing OTA is to Wipe Data/both Caches and No system wipe?

I did Not have any issues with OTA on 1.0...

Just throwing it out there...

Its Bubba
~Stubborn In Your Bones~
Sent From my FlyingJelly

[ReSuReKtZ]

in the OP

Oops, must of missed them the first time i read through it. Anyways nice looking rom, prolly will flash when i get the time too.