Thanks for that breakdown christim, I now have a better understanding of the problem that occured
and MotoCache1, that is a very good question
Thanks for that breakdown christim, I now have a better understanding of the problem that occured
and MotoCache1, that is a very good question
I must misunderstand your reply because in fact if you use it on anything other than ESE81 you get what we had here. Before we had a SBF for SPRecovery that had no kernel in it, fine, but now I just don't see a beneficial purpose.
Sent from my Droid using Tapatalk
Droid 1 - the "unbrickable" droid.
FRG22D - stock, rooted, ChevyNo1 LV 1.1GHz kernel, SetCPU 2.0.2, Superuser 2.3.6.1
Droid X, Droid 2, Droid 2 Global (Band Unlocked), Droid Pro Global (Band Unlocked)
Recommended reading for newbies: How to ask questions the smart way
This just highlights the importance of having all of the Guides in one central location, and following one guide instead of relying on information from multiple sources across different threads/forums
I think in the case of this particular file the solution is somewhat simple. Remove it from where it is hosted so links to it fail and as those links are discovered update the posts with a link to the updated procedure. Keep the file somewhere the RS guys can get it in case an actual need for it ever comes up.
If someone trashes their phone because they followed something on youtube or another site we can't help that, but I just don't see an ongoing purpose to have any instructions for loading that file. That doesn't mean there isn't one - I may just not be aware of it.
Sent from my Droid using Tapatalk
Droid 1 - the "unbrickable" droid.
FRG22D - stock, rooted, ChevyNo1 LV 1.1GHz kernel, SetCPU 2.0.2, Superuser 2.3.6.1
Droid X, Droid 2, Droid 2 Global (Band Unlocked), Droid Pro Global (Band Unlocked)
Recommended reading for newbies: How to ask questions the smart way
I just updated the 3rd link in my signature. I had removed option 2 briefly weeks ago, making 4 be 3 and 3 be 2, but other threads pointed to an option 2 that didn't make sense for what folks were being sent to.
anyways, long story short - I've replaced the ese81update sbf file with a link to the instructions you have for first time rooters. That should cut down on some confusion and hassles folks go through.
Chris
If you apply a rom or theme - backup first!
If you don't know how to backup...Stop until you do.
hint: I name my backups like this: sg6.0_20100428 or ss4.2_20100626 to easily find them later. rom and date.
Have a Problem, Click here to Visit the Rescue Squad
I ran into this same problem when rooting my phone. I suspected it had to do with the kernel that SPRecovery recognized, but did not realize it actually installed the 2.1 kernel. Thank you Christim for the explanation of why I had to flash and flash and flash, oh wait that was at the bar last night!
I ended up flashing the 2.01 sbf and going from there! Had to make sure my desired update.zip was on my card before updating.
I did notice that while I was in the reboot cycle, the batter indicated completely dead and the charging light was off.
I am replacing my SPRecovery with MotoCache1's now.
Why oh WHY can I not just leave things the HELL ALONE!?!??!?
This just happened to me. Got the D1 up/rooted/nice apps, then figured "Hey, why not install SPR."
Dead battery reboot. An unfortunate man once said:
"Yyyyyyyeeeeeeeeaaaaaaaarrrrrrrrrrggggggggggggghhh hhhhhhhhhhhh!!!!!!!!!!!'
Sooo...now I'm back on 22D, and now accepting an update, all back to stock. I need a beer.