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.
Related
I have a moto E XT1524 with android 5.0.2, after downloading The upgrade that fixes the problem of WIFI, my phone did not turn over ... is dead ... any ideas to resurrect?The upgrade was installed, but did not start anymore
Looking across surely have a phone with "hardbrick" when I connect the device to the PC, in the device manager appears "QHSUSB_BULK" ...
* I read different subjects and no solution for this.... not?
pablo_cba said:
Looking across surely have a phone with "hardbrick" when I connect the device to the PC, in the device manager appears "QHSUSB_BULK" ...
* I read different subjects and no solution for this.... not?
Click to expand...
Click to collapse
Yep, QHSUSB_BULK means that it failed to load the Motorola bootloader. Your device will need to be blank flashed. I don't think the blankflash files for this device are publicly available.
Was your bootloader unlocked? Had you upgraded then downgraded the stock ROM at some point?
squid2 said:
Yep, QHSUSB_BULK means that it failed to load the Motorola bootloader. Your device will need to be blank flashed. I don't think the blankflash files for this device are publicly available.
Was your bootloader unlocked? Had you upgraded then downgraded the stock ROM at some point?
Click to expand...
Click to collapse
Yes!, I upgraded to the 5.1 and later back to 5.0.2, That is what causes the problem? and the bootloader is unlocked...
Sorry for the ignorance, but what a blankflash? Ican expect those files to be filtered?
Thanks!
Did you upgrade your bootloader when you upgraded to 5.1? What could have happened is that the OTA tried to "upgrade" (downgrade) your bootloader. Motorola does not allow bootloader downgrades. It blows a fuse that prevents rollback when you upgrade your bootloader.
Blank flashing is a procedure to install the bootloader on a phone that doesn't have a (working) bootloader. There are Qualcomm tools that can communicate with the boot rom over the "Download Mode" (QHSUSB-DLOAD and QHSUSB-BULK) interfaces. These Qualcomm tools can be used to re flash the bootloader. These tools require special versions of the bootloader images. These images are called the blank flash images. Motorola uses these images in the factory when initially setting up a new device. Public firmware releases don't contain these files. You will need blank flash files for the 5.1 bootloader. Sometimes these files leak.
squid2 said:
Did you upgrade your bootloader when you upgraded to 5.1? What could have happened is that the OTA tried to "upgrade" (downgrade) your bootloader. Motorola does not allow bootloader downgrades. It blows a fuse that prevents rollback when you upgrade your bootloader.
Blank flashing is a procedure to install the bootloader on a phone that doesn't have a (working) bootloader. There are Qualcomm tools that can communicate with the boot rom over the "Download Mode" (QHSUSB-DLOAD and QHSUSB-BULK) interfaces. These Qualcomm tools can be used to re flash the bootloader. These tools require special versions of the bootloader images. These images are called the blank flash images. Motorola uses these images in the factory when initially setting up a new device. Public firmware releases don't contain these files. You will need blank flash files for the 5.1 bootloader. Sometimes these files leak.
Click to expand...
Click to collapse
Thanks for your answer .... then there is no other possibility to wait for a leak of blankfiles ...:crying:
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...
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.
Hi -- we have a LG V30 (US998) that we were told was rooted. On boot up we get the message Your device software cannot be checked for corruption. Lock the bootloader. see g.co/ABH. I read on XDA that means that the phone has only had the bootloader unlocked but it hasn't been rooted. When i used root checker basic it says Sorry! Root access is not properly installed on this device. -- so there is no root access to the phone.
Two questions: Can we get back to the OEM install if we lock the bootloader or by other means? The previous owner says we can't go back but it is obvious that we have an incomplete or unsuccessful attempt at rooting. If we can't go back what is the simplest and most direct root to continue with the rooting? I can follow clear and precise directions -- I did root an old Note 1 but did not follow up as the phone is so old.
thanks in advance
C
Lamanz99 said:
Hi -- we have a LG V30 (US998) that we were told was rooted. On boot up we get the message Your device software cannot be checked for corruption. Lock the bootloader. see g.co/ABH. I read on XDA that means that the phone has only had the bootloader unlocked but it hasn't been rooted. When i used root checker basic it says Sorry! Root access is not properly installed on this device. -- so there is no root access to the phone.
Two questions: Can we get back to the OEM install if we lock the bootloader or by other means? The previous owner says we can't go back but it is obvious that we have an incomplete or unsuccessful attempt at rooting. If we can't go back what is the simplest and most direct root to continue with the rooting? I can follow clear and precise directions -- I did root an old Note 1 but did not follow up as the phone is so old.
thanks in advance
C
Click to expand...
Click to collapse
Yes. You have Bootloader Unlocked V30. They've done most of the hard work for you. By the way, that Bootloader Unlock warning is the badge of freedom. LG tries to make it sound scary. Just ignore it.
Even though you're not rooted, I'm curious if you already have TWRP custom recovery installed? That would really cut down your to-do list!
IF you don't have TWRP custom recovery installed, then you just need to follow Section 6 of the WTF instructions. You're Bootloader is already unlocked. You just need to install TWRP, + three root files, including Magisk and reformat your internal memory.
Exactly what firmware version are you on in About Phone? If you're on something like 20a or 20b, after the paragraph above you would want to update to newer firmware. Or you may already be on newer firmware?
See post #192 of this thread:
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
Or click the huge hyperlink in post #1...
You want to follow the directions in Section 6, but you'll have to read some of the prior sections to download the files you need (ADB, etc.)
I have tried for multiple hours to get fastboot and ADB to work with my S6 Edge but it is not working. I suspect I might need to try older Samsung drivers (I only tried the latest ones as far as I remember). I wanted these tools in order to check if my bootloader was unlocked so that I wouldn't brick my device if I tried to install a custom ROM and TWRP. Anyway I followed a video and installed TWRP on my phone and installed Lineage OS Android 10 without checking the bootloader since the guy in the video did not mention doing so and still installed the custom ROM and TWRP. It is working fine. I know it is most likely that since this was possible, the bootloader should probably be unlocked but I just wanted to confirm with more experienced smartphone modders if this is indeed the case. Is it then safe to root my phone without checking bootloader?
Sub-question: If a person were to theoretically attmept to install custom ROM or TWRP or root the phone while the bootloader is locked, would that result in the root failing but the device still being usable or would the attempt result in the device being bricked? IE if the bootloader is locked is it dangerous to attempt to flash software to the phone or will it result in a harmless "failed" message, etc.?
Thank you.