So, I used to have 13.3.2.3.2 with an unlocked bootloader, but then I was stupid and I didn't disable ota, so my tablet updated itself to 4.5.4.
Today, I saw a post in the "general" section about downgrading from 4.5.X to 3.2.8 and I tried it out, and to my surprise it worked!
So I went from 3.2.3.2 to 4.5.4 and back to 3.2.8
My question is since I used to have an unlocked boot loader, and my tab updated to 4.5.4 and then I downgraded to 3.2.8, do I still have my unlocked boot loader?
And if I still do have my unlocked boot loader, can I install twrp?
Big Thanks!
sorry
bhargavamatta said:
So, I used to have 13.3.2.3.2 with an unlocked bootloader, but then I was stupid and I didn't disable ota, so my tablet updated itself to 4.5.4.
Today, I saw a post in the "general" section about downgrading from 4.5.X to 3.2.8 and I tried it out, and to my surprise it worked!
So I went from 3.2.3.2 to 4.5.4 and back to 3.2.8
My question is since I used to have an unlocked boot loader, and my tab updated to 4.5.4 and then I downgraded to 3.2.8, do I still have my unlocked boot loader?
And if I still do have my unlocked boot loader, can I install twrp?
Big Thanks!
Click to expand...
Click to collapse
Sorry, you lost your unlock; on 3.2.8 you can use only safestrap v3, on 4.5.2 you can use only safestrap v4, so no - no real TWRP for 3.2.8 and higher...
Related
OK...I keep running into this terminology, so I am going to dumb down and ask the questions...
1. If we rooted, following the guide on xda, does this mean it was Loki patched? I am confused on the whole Loki thing in the first place. I have googled and still don't understand.
2. I currently have CWM installed...can I update it thru ROM manager or do I need this Loki patched?
3. Are all ROMs Loki patched? (Some specifically say Loki patches and some don't)
4. Safestrap.... What's that too??? (When would it be used?)
Please clarify in simpler terms...don't flame too hard. Thank you
..and BTW, I have my phone rooted, CWM, updated to MJ7 and running gummy's 4.4
tats_06 said:
OK...I keep running into this terminology, so I am going to dumb down and ask the questions...
1. If we rooted, following the guide on xda, does this mean it was Loki patched? I am confused on the whole Loki thing in the first place. I have googled and still don't understand.
2. I currently have CWM installed...can I update it thru ROM manager or do I need this Loki patched?
3. Are all ROMs Loki patched? (Some specifically say Loki patches and some don't)
4. Safestrap.... What's that too??? (When would it be used?)
Please clarify in simpler terms...don't flame too hard. Thank you
..and BTW, I have my phone rooted, CWM, updated to MJ7 and running gummy's 4.4
Click to expand...
Click to collapse
Ok, originally when the phone was released it had a locked boot loader. Loki is the the exploit used to unlock the boot loader. VZW's first OTA fixed this exploit and permanently locked the boot loader. So those with the original MDK version could unlock the boot loader with LOKI.
Loki is just the means that allows you to use a custom recovery. If you have CWM recovery, then you still have an MDK boot loader, and all roms that work with it have the loki patch applied. Loki is a term you want to look for with your phone since it appears to be MDK.
Safestrap is a solution for those with a locked boot loader (anyone who took the ME7 or Mi1 update). It doesn't allow custom recovery as the boot loader is still locked, but it allows you flash some custom roms over the stock rom.
The latest update MJ7 is the 4.3 update. If you take ANY of the updates from your MDK build, you will lose custom recovery.
Thank you so much!!!!! That makes total sense! I rooted my original MDK, flashed CWM...I steered away from any OTAs as I saw warnings. I still have the original CWM, but wanted to try philz touch. Then kept seeing Loki randomly and it confused me even more. I really appreciate your answer!!!!!
318sugarhill said:
Ok, originally when the phone was released it had a locked boot loader. Loki is the the exploit used to unlock the boot loader. VZW's first OTA fixed this exploit and permanently locked the boot loader. So those with the original MDK version could unlock the boot loader with LOKI.
Loki is just the means that allows you to use a custom recovery. If you have CWM recovery, then you still have an MDK boot loader, and all roms that work with it have the loki patch applied. Loki is a term you want to look for with your phone since it appears to be MDK.
Safestrap is a solution for those with a locked boot loader (anyone who took the ME7 or Mi1 update). It doesn't allow custom recovery as the boot loader is still locked, but it allows you flash some custom roms over the stock rom.
The latest update MJ7 is the 4.3 update. If you take ANY of the updates from your MDK build, you will lose custom recovery.
Click to expand...
Click to collapse
tats_06 said:
Thank you so much!!!!! That makes total sense! I rooted my original MDK, flashed CWM...I steered away from any OTAs as I saw warnings. I still have the original CWM, but wanted to try philz touch. Then kept seeing Loki randomly and it confused me even more. I really appreciate your answer!!!!!
Click to expand...
Click to collapse
No problem. You just want to make sure you look for roms that are flash able through recovery. Safestrap is not for you. There are some roms that are for Recovery (MDK users like us) and they are also safe for Safestrap as well. Currently I'm using Old & Slow's Rooted Stock MJ7.
Perfect! I am a CM fan all the way. And because of the risk, I like to read 100 times before proceeding
318sugarhill said:
No problem. You just want to make sure you look for roms that are flash able through recovery. Safestrap is not for you. There are some roms that are for Recovery (MDK users like us) and they are also safe for Safestrap as well. Currently I'm using Old & Slow's Rooted Stock MJ7.
Click to expand...
Click to collapse
I'm looking to update my mom's phone, I honestly don't remember what I did to it in the past. As far as I can tell it's rooted on NC5, with a lock boot loader (I assume although when booting up I see an unlocked lock with the words "custom" underneath it) and knox is 0x0. Does that mean my bootloader is actually unlocked? and am I following this guide (http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613) to update to the latest version?
Thanks
You are most likely rooted but for sure your bootloader is still locked. As far as updating, if you don't want to keep root or anything then just odin back to stock and accept an OTA. If you want root then there are other ways to update posted in this forum.
So I decided to try out the new root that was found. Restored my phone to stock ZV8 then ran the one click. Flashed the Twrp recovery(didn't fail when flashing), and rebooted. Comes up with Secure boot error. So just saying out there that recovery does not work with the new root method.
I wonder if it's related to the bumping process, and that we don't have a truly unlocked bootloader.
That's what I was originally thinking but then I remembered that zv8 uses a newer bootloader than ZV4. So we need . Updated version of TWRP to work with the bootloader.
That's what I was originally thinking but then I remembered that zv8 uses a newer bootloader than ZV4. So we need . Updated version of TWRP to work with the bootloader.
New root method only allows root at ROM level. LG closed the boot loader security flaw in zv8. U have to go back to zv4, stump the ROM then bump for custom recovery.
Fixed
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
scaftogy said:
I have a functioning but not up to date setup:
Apollo Nexus v2.0.1 which is unfortunately in the stock slot of Safestrap v3.75, no other ROM slots and previous FireOS backup leaves screen blank (boots and ADB accessible).
(The backstory to this: some update had gone wrong at the end of last year I this status is all I could manage to get to a functioning state.)
Now I would like to move to unlocked bootloader, TWRP and CM12.1
I tried to unlock the bootloader using the method with cuberHDX posted in other threads but in fastboot after
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
I am getting
FAILED (remote: Unlock code is NOT correct)
I don't know what seems to be the problem. After the messy "fixes" from the end of last year I cannot quite remember which was the last version of the FireOS (and hence the bootloader that came along with it) that was installed.
--> Can anyone tell me how to find out the version of the bootloader?
Any other suggestions how to get out of my non-upgradeable situation? Any help greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, there is no reliable method to determine bootloader version. If you are confident in the steps you are taking to unlock the bootloader the your system may have upgraded past 3.2.3.2 which is the last version that contains the vulnerability that the unlock exploit leverages. You could try one of the Safestrap Flashable HDX Stock Images (suggest v3.2.6 for greatest compatibility) in the stock slot but this could result in a brick if everything doesn't line up properly. Not sure it is worth the risk given your device may have other lingering issues from the previous update attempt gone bad. Nexus v2 is still highly functional; you can safely update that to v2.05 and add a few Xposed modules to acheive a near KitKat experience.
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
dpeddi said:
- Bootloader shipped with firmwareversion 1[34].3.1.0 <= x <= 1[34].3.2.4 (as we use the rsa bug)
Click to expand...
Click to collapse
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
scaftogy said:
OK, I was afraid that there wasn't any way to determine the bootloader version. Thanks for the clear answer.
Given that the state of my kindle HDX is somewhat complicated I agree that trying something like flashing a stock rom seems rather risky. I just needed someone else to confirm that.
I am fairly confident about the steps I took with cuber and the bootloader unlocking procedure (on linux VM which I use regularly). I am also 98% sure I never let FireOS update. Doing a bit more digging, I found that I have kept all files that I used for flashing last year. There are the following (relevant) files in that folder:
update-kindle-14.3.1.0_user_310079820.bin
update-kindle-14.3.2.4_user_324002120.bin
prerooted14.3.1.0.zip
Safestrap-Apollo-3.75-os3.2.4-B02.apk
apollo-nexus-rom-v2.0.1.zip
That leads me to believe that the bootloader should be version .3.2.4
Now I am a bit confused whether the version .3.2.4 should be unlockable. @Davey126, you wrote that the last one was .3.2.3.2. However the original thread by @dpeddi states in first post:
Could anyone please confirm which one is actually the last version of the bootloader that can be unlocked?
Click to expand...
Click to collapse
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Cl4ncy said:
You need a version below 3.2.4, i.e. 3.2.3.2 or lower.
But the good news is, if you are on 3.2.4 you can use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Click to expand...
Click to collapse
I am on @ggow's CM12.1 now! :victory:
Rolled back with this to .3.0.9, upgraded to stock .3.1.0, rooted, unlocked bootloader, flashed TWRP, and finally flashed CM12.1. Thanks so much for the hint to roll back!
To come full circle to the original question: Determining the version of the bootloader is not possible from adb or fastboot. If you don't know which version of the bootloader you have, it can help to try to find out which roms / updates you flashed before. In my case I had a folder on my PC that showed I must have had .3.2.4.
I would like to find out if I'm able to flash the firmware 4.5.5(from this guide; I will be also follow this guide to root 4.5.5). Does 4.5.5 have its own 4.5.5 bootloaders?
The reason I'm asking is because I read from the top of this thread that after booting a certain bootloader, you would be unable to run other bootloaders. I initially started with a 4.5.5 unrooted --> OS 5 --> 4.5.3 (rooted with kingroot then flashed openrecovery-twrp-2.8.6.0-ariel.img). I was unable to receive OS 5 by simply using "Check for Updates" so I enabled the developer preview for my device. After having OS 5 installed, when looking in System Updates on the fire, I saw "Your device is running Fire OS 5.0.1". Does this mean that my tablet has in fact ran the 5.2.2u2 bootloader and therefore I won't be able to use other bootloaders?
Lastly, I wanted to know if the firmware named update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin from here contains the dreaded 5.2.2u2 bootloaders.