Jump to content


Photo

Snatched that sheezy-Soak Update


  • Please log in to reply
228 replies to this topic

#41 Hashcode

Hashcode

    King-Of-Code

  • Developer
  • 227 posts
  • Twitter:Hashcode0f

Posted 10 July 2013 - 09:40 AM

I pride myself in being able to come up with really stupid ideas and causing myself all kinds of issues. LMAO.  I may give it another try and see how painful I can make this on myself.  Or I may go back to CM 10.1 and call it good.  LOL.

 

When you flashed TWRP, did you go into recovery immediately after that?  It should disable the install-recovery.sh similar to CWM.



#42 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 09:42 AM

When you flashed TWRP, did you go into recovery immediately after that?  It should disable the install-recovery.sh similar to CWM.

 

Yes, I tried to.  I was in AP Fastboot mode, flashed TWRP, shut it off, booted it up into recovery and it came up stock every time.  Freaking damn phone.  LOL


Non potest esse nisi unus


#43 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 09:46 AM

So, now that I've been through this ride, I can't FXZ back to MR2 anymore.  The flash looks like this:

 

07/10/13 14:15:40  Multi upgrade started for 1 phones
07/10/13 14:15:40  [Device ID: 0] 1/26 flash sbl1 "sbl1.mbn"
07/10/13 14:15:41  [Device ID: 0] 2/26 flash sbl2 "sbl2.mbn"
07/10/13 14:15:42  [Device ID: 0] 3/26 flash sbl3 "sbl3.mbn"
07/10/13 14:15:43  [Device ID: 0] 4/26 flash rpm "rpm.mbn"
07/10/13 14:15:43  [Device ID: 0] 5/26 flash tz "tz.mbn"
07/10/13 14:15:44  ERROR: 5/26 flash tz "tz.mbn" -> Phone returned FAIL. - on device ID 0.
07/10/13 14:15:44  [Device ID: 0] 5/26 flash tz "tz.mbn" -> Phone returned FAIL.
07/10/13 14:15:44  ERROR: Failed flashing process. - on device ID 0.
07/10/13 14:15:44  Multi upgrade finished.

Non potest esse nisi unus


#44 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 09:50 AM

Stupid question time.  Does anyone (cough cough Hash?) have a list of all the partitions on the HD and what the hell they are?  Coming from the OMAP world this Snapdragon stuff still eludes me.


Non potest esse nisi unus


#45 Hashcode

Hashcode

    King-Of-Code

  • Developer
  • 227 posts
  • Twitter:Hashcode0f

Posted 10 July 2013 - 09:52 AM

Yeah part of the update is gpt_main0 partition which is like OMAP style cdt.  It looks to contain partition entry info (not sure if it's eactly like cdt).  This is probably what is causing the fail on tz.  Interesting that sbl1-3 and rpm will flash tho.



#46 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 09:53 AM

You'd think with an unlocked bootloader we'd be able to flash those things regardless of the security they have.  Isn't that the point of having an unlocked bootloader?  :)


Non potest esse nisi unus


#47 mikepahl318

mikepahl318

    Member

  • Dedicated Supporter
  • PipPip
  • 102 posts
  • LocationUSA
  • Current Device(s):Droid Turbo 64GB, 2013 Nexus 7 32GB

Posted 10 July 2013 - 09:54 AM

wow - this got crazy fast.



#48 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 09:56 AM

Sorry.  :)


Non potest esse nisi unus


#49 Hashcode

Hashcode

    King-Of-Code

  • Developer
  • 227 posts
  • Twitter:Hashcode0f

Posted 10 July 2013 - 10:00 AM

Here's what I know off hand

 

aboot -> /dev/block/mmcblk0p5 (emmc_appsboot firmware?)

abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p31
cache -> /dev/block/mmcblk0p35
cdrom -> /dev/block/mmcblk0p37
cid -> /dev/block/mmcblk0p28
devtree -> /dev/block/mmcblk0p30
dhob -> /dev/block/mmcblk0p21 (this is related to signature checking)
fsg -> /dev/block/mmcblk0p24 (firmware?)
hob -> /dev/block/mmcblk0p20 (related to signature checking)
kpan -> /dev/block/mmcblk0p33 (kernel panic partition)
logo -> /dev/block/mmcblk0p29 (logo partition -- literally can write a new raw logo file to it for the initial splashscreen)
mbl -> /dev/block/mmcblk0p19 (main bootloader)
misc -> /dev/block/mmcblk0p26 (usually used for communication w/ recovery but looks blank)
modem -> /dev/block/mmcblk0p1 (modem firmware files mounted as /firmware)
modemst1 -> /dev/block/mmcblk0p17 (?)
modemst2 -> /dev/block/mmcblk0p18 (?)
padA -> /dev/block/mmcblk0p9 (?)
padB -> /dev/block/mmcblk0p16 (?)
pds -> /dev/block/mmcblk0p27 (similar to omap)
persist -> /dev/block/mmcblk0p22 (hdmi keystore, etc)
recovery -> /dev/block/mmcblk0p32
rpm -> /dev/block/mmcblk0p6 (qcom firmware)
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2 (secondary bootloader 1)
sbl2 -> /dev/block/mmcblk0p3 (secondary bootloader 2)
sbl2Backup -> /dev/block/mmcblk0p10
sbl3 -> /dev/block/mmcblk0p4 (secondary bootloader 3)

sbl3Backup -> /dev/block/mmcblk0p11
sp -> /dev/block/mmcblk0p25 (?)
ssd -> /dev/block/mmcblk0p23 (?)
system -> /dev/block/mmcblk0p36
tombstones -> /dev/block/mmcblk0p34 (logging)
tz -> /dev/block/mmcblk0p7 (qcom firmware)
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p38
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
 

 


  • BytecodeMe, SamuriHL and Tucknology like this

#50 Hashcode

Hashcode

    King-Of-Code

  • Developer
  • 227 posts
  • Twitter:Hashcode0f

Posted 10 July 2013 - 10:01 AM

Samurai does your AP Fastboot screen show the sbl2 security downgraded message and then the 4 fail codes?



#51 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 10:06 AM

Not anymore.  But it did when I tried to FXZ back to MR2.  Once I restored my MR4 nandroid everything appears to be normal in AP Fastboot.  However, I don't think the nandroid messes with what the update installs on most of the partitions.  I was going to attempt something stupid real quick but I don't know how far down the rabbit hole I wanna go with this thing.  It'd be useful information to have though.  

 

Hash thanks for the list.  That's very helpful!


Non potest esse nisi unus


#52 jasonbeth

jasonbeth

    n00b

  • Members
  • Pip
  • 11 posts
  • Twitter:conley_jason
  • Google+:https://plus.google.com/u/0/115320663968725022579/posts/p/pub
  • Current Device(s):Verizon LG G2 VS980

Posted 10 July 2013 - 10:08 AM

So far so good. I'm fully stock with the unlocked boot loader and I was able to take the update. It said it failed once the phone booted back up but it is showing the newer version in the about phone section. As to whether or not it can be rooted I'm not sure at work now and can't check. I did boot into fast boot and it is showing the boot loader still unlocked.

#53 Hashcode

Hashcode

    King-Of-Code

  • Developer
  • 227 posts
  • Twitter:Hashcode0f

Posted 10 July 2013 - 10:10 AM

So far so good. I'm fully stock with the unlocked boot loader and I was able to take the update. It said it failed once the phone booted back up but it is showing the newer version in the about phone section. As to whether or not it can be rooted I'm not sure at work now and can't check. I did boot into fast boot and it is showing the boot loader still unlocked.

 

You can see what failed by doing this as root in adb: cat /cache/recovery/last_log


  • BytecodeMe and SamuriHL like this

#54 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 10:16 AM

Ok, I heavily modified my RSD script for my House of RAZR_HD and was able to I believe successfully flash back to MR2.  We'll find out in a second if it worked or not but I got no errors in RSD this time.  That means I should, in theory, be able to apply the update again.

 

Hash, do you know if anything critical happens in the update after the moto_bl_backup()?  That's where the update stops for anyone who's unlocked.


Non potest esse nisi unus


#55 Hashcode

Hashcode

    King-Of-Code

  • Developer
  • 227 posts
  • Twitter:Hashcode0f

Posted 10 July 2013 - 10:30 AM

Ok, I heavily modified my RSD script for my House of RAZR_HD and was able to I believe successfully flash back to MR2.  We'll find out in a second if it worked or not but I got no errors in RSD this time.  That means I should, in theory, be able to apply the update again.

 

Hash, do you know if anything critical happens in the update after the moto_bl_backup()?  That's where the update stops for anyone who's unlocked.

 

 

That's like the very last line in the update.  So I doubt it.

 

Also for those interested, I re-flashed TWRP and everything went swell.  Here's the updated TWRP 2.6 .img:

Please Login or Register to see this Hidden Content

md5sum: 86ed11dd04eea72b2848cb14c8989279

 

EDIT: Also looks like you only see that downgraded message once on the AP fastboot screen.  It's gone now on mine.



#56 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 10:33 AM

That's like the very last line in the update.  So I doubt it.

 

Also for those interested, I re-flashed TWRP and everything went swell.  Here's the updated TWRP 2.6 .img:

Please Login or Register to see this Hidden Content

md5sum: 86ed11dd04eea72b2848cb14c8989279

 

EDIT: Also looks like you only see that downgraded message once on the AP fastboot screen.  It's gone now on mine.

 

Awesome.  Thanks man!  I'm about to rock this update again, reinstall TWRP, install root, and nandroid it.


Non potest esse nisi unus


#57 livinginkaos

livinginkaos

    I don't know what I'm doing anymore.....

  • Administrator
  • 15,282 posts
  • Google+:Hangouts - livinginkaos@gmail.com
  • LocationOregon
  • Current Device(s):Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7

Posted 10 July 2013 - 10:47 AM

That's like the very last line in the update.  So I doubt it.

 

Also for those interested, I re-flashed TWRP and everything went swell.  Here's the updated TWRP 2.6 .img:

Please Login or Register to see this Hidden Content

md5sum: 86ed11dd04eea72b2848cb14c8989279

 

EDIT: Also looks like you only see that downgraded message once on the AP fastboot screen.  It's gone now on mine.

Thanks Hash! I just realized that I was still on 2.3.2.3 !


b2wvCBn.png

Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7


#58 mikepahl318

mikepahl318

    Member

  • Dedicated Supporter
  • PipPip
  • 102 posts
  • LocationUSA
  • Current Device(s):Droid Turbo 64GB, 2013 Nexus 7 32GB

Posted 10 July 2013 - 10:52 AM

Some are reporting receiving the 9.20 update this morning....



#59 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 July 2013 - 10:53 AM

There.  Finally.  Got the update installed, rooted, and am now nandroiding the damn thing.  That was painful.  :D


Non potest esse nisi unus


#60 mikepahl318

mikepahl318

    Member

  • Dedicated Supporter
  • PipPip
  • 102 posts
  • LocationUSA
  • Current Device(s):Droid Turbo 64GB, 2013 Nexus 7 32GB

Posted 10 July 2013 - 11:01 AM

There.  Finally.  Got the update installed, rooted, and am now nandroiding the damn thing.  That was painful.   :D

whats the verdict? i am rooted and unlocked. can i accept? do i have to use voodoo?

 

I have stock recovery






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users