5,594,805 Members 36,729 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
mattlgroff
Old
#21  
mattlgroff's Avatar
Recognized Developer - OP
Thanks Meter 2339
Posts: 2,175
Join Date: Dec 2011
Location: San Diego

 
DONATE TO ME
Quote:
Originally Posted by SilentViper View Post
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: [ Click to Expand ]
 
SilentViper
Old
#22  
Junior Member
Thanks Meter 3
Posts: 16
Join Date: 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
 
xlightwaverx
Old
(Last edited by xlightwaverx; 23rd May 2012 at 05:38 PM.)
#23  
xlightwaverx's Avatar
Member
Thanks Meter 23
Posts: 75
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by SilentViper View Post
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
 
SilentViper
Old
#24  
Junior Member
Thanks Meter 3
Posts: 16
Join Date: Jan 2010
Quote:
Originally Posted by xlightwaverx View Post
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
 
xlightwaverx
Old
#25  
xlightwaverx's Avatar
Member
Thanks Meter 23
Posts: 75
Join Date: Jun 2010

 
DONATE TO ME
Bump!
 
Q9Nap
Old
#26  
Q9Nap's Avatar
Senior Member
Thanks Meter 279
Posts: 403
Join Date: 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?
 
mattlgroff
Old
#27  
mattlgroff's Avatar
Recognized Developer - OP
Thanks Meter 2339
Posts: 2,175
Join Date: Dec 2011
Location: San Diego

 
DONATE TO ME
Quote:
Originally Posted by Q9Nap View Post
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

Please do not Personal Message me for help or troubleshooting. They will be ignored.
Owner of Batakang. Recognized Developer at XDA
You can find forum sections for the T-Mobile Prism II over at Droid-Hive under The Batcave.

The Following User Says Thank You to mattlgroff For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes