What's new
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!

Get Unstuck from ICS Leak 200 (AKA Upgrading from 200 to 206) INSTRUCTIONS

No...because you can't flash back to an older kernel/bootloader. The updating procedure (OTA, fastboot, whatever) does not allow for it.

The OTA's allow you to update stock (.219) or itself (.200 to .200, .206 to .206 and .208 to .208). What they are doing with this procedure is using the stock GB kernel (the .219) and patching it with the files in the OTA (since that is what it does), then flashing the .219 system so the OTA can update it. Since the .208 OTA is able to update a .219 kernel and a .219 system.....AND a .208 kernel/system....it sees the .208 kernel and proceeds, sees the .219 system and updates it.

There is no way to actually flash an older kernel back to the device.
 
Is there any way to completely wipe the internal disk (partitions, kernel, drivers, etc.) and then do a 219 fastboot?

I'm guessing probably not since fastboot requires some basic files to be on the internal disk in order to fastboot.
 
Last edited:
Confusing

Sorry man this is just too confusing. I don't understand what state you want the phone to be in when trying to flash the 208 update. Rather than try to use a tool designed for the Razr, why not just post the few commands from a CMD prompt?

My understanding is that you want me to:
  1. Flash 208 Kernel using ap-fastboot mode
  2. Flash GB files using RSD Lite?
  3. Flash 208 package update using "update from sdcard"?
This won't work, it bombs on cdt.bin when trying to flash GB files and good thing it does. The thread you refer to is also very vague about what to do because it's meant for a completely different phone.

I tried flashing the 208 kernel and it works fine, even boots and runs fine but it obviously won't update from there because of the build.prop issue. So, what's next?

Rather than referring to a different post using a tool not designed for the D4 that could possibly trash my phone (the 85 kernel?) can you clearly state what files go on the phone before flashing 206 update to 208?
 
You have steps 1 and 2 reversed, you flash 219 (which will give a bunch of errors) then flash 208 kernel, then do the whole 208 update through recovery.

The purpose is to get the leak to think you're on GB. When you flash 219 it places all GB files on the phone except the kernel because you can't downgrade kernels from the leak to GB. Then you flash the latest kernel. Now you have a phone with GB and a leak kernel. At this point you can update to the latest leak because when it updates it will see the GB files so it passes one check and it will see its own kernel so it will pass the next check.

You do not use RSDlite for any of this.
 
orangechoochoo said:
Is there any way to completely wipe the internal disk (partitions, kernel, drivers, etc.) and then do a 219 fastboot?

I'm guessing probably not since fastboot requires some basic files to be on the internal disk in order to fastboot.
Click to expand...

AP-Fastboot does not require anything to be on the internal disk. it's a true ROM based utility. Recover, on the other hand, does.

I'm convinced there is a way to return to STOCK, as you seem to infer. You have to be very careful though, the "recovery" partition must be intact or you can't run "recovery" from the fastboot menu and install the update. I know there is a way to trash the root directory forcing the update to rebuild the entire directory structure, including recovery and kernel. But how to do it while leaving the phone in a flashable state is the question.

What I did accidentally while trying to root the device was to try to flash the GB system.img over the top of the 206 ICS update. It resulted in a "flash error" that is easy to fix. Next I got a "boot error" which I think is what caused the next part to happen. When I re-flashed the correct system.img back to /system it cleared the boot error but the phone would not boot. I then entered recovery using apt-fastboot and re-flashed the 206 update. The update didn't just update, it completely rebuilt the entire root directory structure from scratch, deleting everything on the internal system NAND chip, recreating system directories, unpacking archives, patching system files, patching preinstall files, checking signatures and finally rebooting. I'm convinced that if I had used recovery to flash the original GB update it would have taken me back to STOCK. What I'm worried about is the boot error. That error could conceivably become permanent unless you know what to do to recover from it. But I'm convinced it was that error condition that triggered a complete rebuild of the system partition when I installed the 206 update.

If I get gutsy I'll try generating a boot error again and see if it will rebuild the entire system from scratch. I recovered from it before so I can probably do so again. I just have to remember exactly what I did to cause the boot error.

If I find anything out I'll start a new thread: Restoring stock GB after ICS leak.
 
So do you think we can flash the 219 image and then fastboot the stock 219? Then we can use the instructions from the GB to ICS leak thread and move to 208 and retain root?
 
siggma said:
Sorry man this is just too confusing. I don't understand what state you want the phone to be in when trying to flash the 208 update. Rather than try to use a tool designed for the Razr, why not just post the few commands from a CMD prompt?

My understanding is that you want me to:
  1. Flash 208 Kernel using ap-fastboot mode
  2. Flash GB files using RSD Lite?
  3. Flash 208 package update using "update from sdcard"?
This won't work, it bombs on cdt.bin when trying to flash GB files and good thing it does. The thread you refer to is also very vague about what to do because it's meant for a completely different phone.

I tried flashing the 208 kernel and it works fine, even boots and runs fine but it obviously won't update from there because of the build.prop issue. So, what's next?

Rather than referring to a different post using a tool not designed for the D4 that could possibly trash my phone (the 85 kernel?) can you clearly state what files go on the phone before flashing 206 update to 208?
Click to expand...


You first put your phone in fastboot mode.then proceed with step 1. Which is to flash 219. You do this through the razr utility not rsd lite.


Once that's done, again put your phone in fastboot mode and flash the 208 boot image using the unstuck tool in the op. BUT since the op is meant for 206, you need to download the 208 boot image and put that in the folder, replacing the 206 boot image. (You need to rename the 208 boot image to boot206). Go here for more info

http://www.droidforums.net/forum/droid-4-roms/211413-6-16-208-kernel-6-16-206-users-only.html


Then go to recovery and flash the 208 update.
 
Is there any way to fastboot or push rootkeeper's SU backup (or a someone's 208 img with SU backup in it) so we could restore root once you jump from one leak to another leak? Someone will tell me that you cannot push without root but when we go through the Unstick process it doesn't mention anything about previously having root, plus when you flash 219 it will keep the kernel from the leak and flash everything else and remove root, but you can still flash the leaked boot.img file without root. So my point is it appears to me that you can push/flash things with the Unstick utility without root, so it may be possible to push/flash the SU backup without root too.

Alternatively, I know we can place a backup SU on one of the data/local folder since that is read/writeable. I'm wondering if there's a way to change rootkeeper so it looks there for the backup.
 
Last edited:
Those with the Samsung Galaxy who went to ICS and retained root How to upgrade to ICS 4.0.4 -- Also OPTIONAL How to root ICS 4.0.4 - Android Forums [GUIDE]{ROOT}How To Root The ICS Leak - xda-developers

The tool they use is ODIN which I think is similar to the Unstick Utility which lets you flash files. Then they download SU.zip to their SD card and then flash Clockwork Recovery. Now in Clockwork they can install the SU.zip and then install busybox.

Maybe after upgrading to 208 someone using the Unstick tool can flash superuser.zip (obtained from someone who has root on 208), then boot into recovery and install the superuser.zip from recovery. Or use the Unstick utility to install CWR, flash the 208 SU.zip, then install busybox.

I don't know anything about programming, but maybe my ideas can help programmers come up with solutions. I really want to find a way to keep root going from leak to leak otherwise if we choose to move to another leak we won't have root for quite a while until the ICS root method is released (who knows when that will be).
 
Last edited:
Seems like you need to flash something that's signed, which means it probably won't work (there's no "true" clockwork recovery for Droid 4, or any phone with a locked bootloader, you only have things like safeboot which are not full replacements for the system recovery and can only access limited things).


orangechoochoo said:
Those with the Samsung Galaxy who went to ICS and retained root How to upgrade to ICS 4.0.4 -- Also OPTIONAL How to root ICS 4.0.4 - Android Forums [GUIDE]{ROOT}How To Root The ICS Leak - xda-developers

The tool they use is ODIN which I think is similar to the Unstick Utility which lets you flash files. Then they download SU.zip to their SD card and then flash Clockwork Recovery. Now in Clockwork they can install the SU.zip and then install busybox.

Maybe after upgrading to 208 someone using the Unstick tool can flash superuser.zip (obtained from someone who has root on 208), then boot into recovery and install the superuser.zip from recovery. Or use the Unstick utility to install CWR, flash the 208 SU.zip, then install busybox.

I don't know anything about programming, but maybe my ideas can help programmers come up with solutions. I really want to find a way to keep root going from leak to leak otherwise if we choose to move to another leak we won't have root for quite a while until the ICS root method is released (who knows when that will be).
Click to expand...
 
You must log in or register to reply here.

Similar threads

L
Get OUT fastboot loop ICS leak
Replies
5
Views
4K
grizzy3
G
J
Bricked Droid 4 going from Leak .213 to Fastboot ICS?
Replies
13
Views
4K
jingyen
J
J
Stuck on old ICS leak? Not for long.
Replies
0
Views
2K
Jungle King 76
J
M
simplified 208 upgrade guide with root
Replies
2
Views
2K
JKingDev
J
H
[Rom-Stock] Motoblur 6.16.206 (Ics Leak) For Safestrap [2012-06-17]
2
Replies
17
Views
11K
nowell29
N
Back
Top