Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Bspatch. Trying to get ICS stuck CDMA Razrs back on the path.

OP mattlgroff

23rd May 2012, 04:29 AM   |  #21  
mattlgroff's Avatar
OP Recognized Developer
Flag San Diego
Thanks Meter: 2,416
 
2,263 posts
Join Date:Joined: Dec 2011
Donate to Me
More
Quote:
Originally Posted by SilentViper

Awesome! mind posting just the fastboot commands? I tried interpreting the .bat but haven't had much experience with .BATs and am not entirely sure what you are doing

"fastboot flash boot boot206.img" or "fastboot flash boot boot85.img"
The Following User Says Thank You to mattlgroff For This Useful Post: [ View ]
23rd May 2012, 04:55 AM   |  #22  
Junior Member
Thanks Meter: 3
 
16 posts
Join Date:Joined: Jan 2010
Knowing the methods Matt used, and that updates use the same applypatch method update.zip uses. They would have to change pre existing releases to patch this method


Edit: thanks Matt!
Sent from my DROID RAZR using XDA
23rd May 2012, 06:27 PM   |  #23  
xlightwaverx's Avatar
Member
Thanks Meter: 26
 
90 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Quote:
Originally Posted by SilentViper

Knowing the methods Matt used, and that updates use the same applypatch method update.zip uses. They would have to change pre existing releases to patch this method


Edit: thanks Matt!
Sent from my DROID RAZR using XDA

So, now that all the stuck ones can go up, and eventually leave GB for good and be solely on ICS, are we done? I kinda feel the need to keep working on an ICS2GB method.

Essentially, whatever version your boot.img is, you can install (by force) whatever build that the boot.img is from. If you are on .84, and you want to go to .85, you would have to patch .181GB-boot.img with .85ICSboot.img.p, flash new boot.img, proceed with recovery (by force) of .85. .84 cannot go to .85 and vice versa unless you issue a new boot.img.p patch off of original .181GB-boot.img and then proceed with that ota version recovery install correct?

Now, if u wanted to go backwards, is this where the CDT.bin file would prevent you from doing that? Because if we fastboot a .181 boot.img, it seems to take fine correct? The only issues are cdt.bin, devtree, cdrom, and recovery.

So since we successfully bypassed the CDT.bin preflash validation by copying (DD) a .181GB mmcblk1p18 to (whatever version of ICS leak you're on), rebooting in to fastboot, and flashing old cdt.bin, no issue arrises.

Now, once at that stage when we (by force) fastboot .181 GB files on after replacing cdt.bin, we receive customer ID error on boots, but cdt.bin is flashed, so customer id error keeps popping up because of the other 3 partitions being mismatched (devtree, cdrom, recovery?) I'm thinking out loud...

So, we if DD .181 cdt.bin (p18) along with recovery, devtree, and cdrom, reboot into fastboot, would the .181 fastboot files then be able to pass preflash validation? At that stage, force OTA update of .181GB over passed validated partitions, and then we would have a full 181 OTA install?

I understand the concept of having a locked bootloader, but when we DD these images out of .181GB, wouldn't these images retain their signature? Phew, that's a lot of typing, and then again, thinking out loud.

X
Last edited by xlightwaverx; 23rd May 2012 at 06:38 PM.
23rd May 2012, 07:26 PM   |  #24  
Junior Member
Thanks Meter: 3
 
16 posts
Join Date:Joined: Jan 2010
Quote:
Originally Posted by xlightwaverx

So, now that all the stuck ones can go up, and eventually leave GB for good and be solely on ICS, are we done? I kinda feel the need to keep working on an ICS2GB method.

Essentially, whatever version your boot.img is, you can install (by force) whatever build that the boot.img is from. If you are on .84, and you want to go to .85, you would have to patch .181GB-boot.img with .85ICSboot.img.p, flash new boot.img, proceed with recovery (by force) of .85. .84 cannot go to .85 and vice versa unless you issue a new boot.img.p patch off of original .181GB-boot.img and then proceed with that ota version recovery install correct?

Now, if u wanted to go backwards, is this where the CDT.bin file would prevent you from doing that? Because if we fastboot a .181 boot.img, it seems to take fine correct? The only issues are cdt.bin, devtree, cdrom, and recovery.

So since we successfully bypassed the CDT.bin preflash validation by copying (DD) a .181GB mmcblk1p18 to (whatever version of ICS leak you're on), rebooting in to fastboot, and flashing old cdt.bin, no issue arrises.

Now, once at that stage when we (by force) fastboot .181 GB files on after replacing cdt.bin, we receive customer ID error on boots, but cdt.bin is flashed, so customer id error keeps popping up because of the other 3 partitions being mismatched (devtree, cdrom, recovery?) I'm thinking out loud...

So, we if DD .181 cdt.bin (p18) along with recovery, devtree, and cdrom, reboot into fastboot, would the .181 fastboot files then be able to pass preflash validation? At that stage, force OTA update of .181GB over passed validated partitions, and then we would have a full 181 OTA install?

I understand the concept of having a locked bootloader, but when we DD these images out of .181GB, wouldn't these images retain their signature? Phew, that's a lot of typing, and then again, thinking out loud.

X

Logically and theoretically what you are saying makes sense. I was going to try that first chance i get. Since i just realized that i have the fastboot screen burned in I'm more willing to screw with my second phone

Sent from my DROID RAZR using XDA
28th May 2012, 04:22 AM   |  #25  
xlightwaverx's Avatar
Member
Thanks Meter: 26
 
90 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Bump!
18th July 2012, 07:58 AM   |  #26  
Q9Nap's Avatar
Senior Member
Thanks Meter: 533
 
622 posts
Join Date:Joined: Feb 2009
Donate to Me
So does the no corruption bspatch posted in the op make a flashable boot.img? i used it to patch the bionic 5.9.905 boot.img with boot.img.p from the latest 6.7.235 leak and it does create a file; however the new boot.img is different than the boot.img included in matt's DroidBionicUnstuck.zip utility. I know i can just use the image from this utility, but want to have the technique ironed out for future reference.

is the method from this post...

http://forum.xda-developers.com/show....php?t=1702233

...still the only way to successfully patch boot.img?
18th July 2012, 08:09 AM   |  #27  
mattlgroff's Avatar
OP Recognized Developer
Flag San Diego
Thanks Meter: 2,416
 
2,263 posts
Join Date:Joined: Dec 2011
Donate to Me
More
Quote:
Originally Posted by Q9Nap

So does the no corruption bspatch posted in the op make a flashable boot.img? i used it to patch the bionic 5.9.905 boot.img with boot.img.p from the latest 6.7.235 leak and it does create a file; however the new boot.img is different than the boot.img included in matt's DroidBionicUnstuck.zip utility. I know i can just use the image from this utility, but want to have the technique ironed out for future reference.

is the method from this post...

http://forum.xda-developers.com/show....php?t=1702233

...still the only way to successfully patch boot.img?

The stickied method thread by myself for patching boot.IMG is the only way I know of.

Sent from my Galaxy Nexus using Tapatalk 2

The Following User Says Thank You to mattlgroff For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes