timmy10shoes
Member
System data and kernel changes have nothing to do with each other. It works as long as your coming from a custom rom.
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Downgrade to 902 - No app or data loss
- Thread starter SamuriHL
- Start date
Works great.. Once it is set up it only takes 30 mins to go from one leaked ICS to another.
You mean as long as you're coming from a leak, correct?
jcwilliams
Senior Member
just wanted to say thanks to timmy for taking time outside the forums to help me with this. i was quite confused at first and along with computer issues made me want to just not do it but its working and i am about to boot into the 230 leak! thanks again timmy and op for this! it works!
Waiting for Device
I verified my folder looks identical to the image provided in the top post. USB debugging is enabled and latest moto drivers installed. I used MTP and got stuck on "Waiting for Device" when I execute RUNME.bat. I also tried Mass Storage and PTP settings with the same result. Anyone else get stuck here and figured out how to get past it? Thanks!
I verified my folder looks identical to the image provided in the top post. USB debugging is enabled and latest moto drivers installed. I used MTP and got stuck on "Waiting for Device" when I execute RUNME.bat. I also tried Mass Storage and PTP settings with the same result. Anyone else get stuck here and figured out how to get past it? Thanks!
jcwilliams
Senior Member
had the same issue... boot into fastboot mode and itll take off
Doh!
Another issue. Anyone got stuck on "writing preinstall"? Not sure what to do here. It's been on this step for 10 minutes and I'm freaked that if I unplug the phone now it will be bricked. I did have SafeStrap installed on my device, could that be killing the process? Should I wait for it to time out?
Last edited:
jcwilliams
Senior Member
Just wait. Did the same thing to me also
O.K. I had a failure to write cdt.bin, logo.bin and ebr even though they were right there in the directory with all the other files.
This resulted in a general failure.
I got stuck on the dual core screen, pulled the battery and rebooted into recovery, sideloaded .902, side loaded.905. Both loaded fine.
Tried to load the .230 file and got a signature failure - abort.
So I rebooted and now seem to be on 230. I have no idea whether or not it worked, but handset resports that it did.
We'll see.
RMD
This resulted in a general failure.
I got stuck on the dual core screen, pulled the battery and rebooted into recovery, sideloaded .902, side loaded.905. Both loaded fine.
Tried to load the .230 file and got a signature failure - abort.
So I rebooted and now seem to be on 230. I have no idea whether or not it worked, but handset resports that it did.
We'll see.
RMD
Very strange issues some of you are having with flashing. I'm wondering if it's a USB port and/or cable issue that's causing some weird issues. I've not had any problems and lots of others have used it successfully, as well. Really not sure where these differences in experience are coming from. 
Yes, I cannot imagine why it chose not to write three files which were present in the directory.
The biggest issue I face now is vetting the various upgrade files floating around.
They came so fast for a while and I dropped off line for several weeks.
Now I have a variety of "blur" files on my HD that are likely useless at best and dangerous at worst.
RMD
The biggest issue I face now is vetting the various upgrade files floating around.
They came so fast for a while and I dropped off line for several weeks.
Now I have a variety of "blur" files on my HD that are likely useless at best and dangerous at worst.
RMD
