Related
I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?
stivelio said:
I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?
Click to expand...
Click to collapse
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.
gee2012 said:
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.
Click to expand...
Click to collapse
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0
stivelio said:
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0
Click to expand...
Click to collapse
Your radio is not 5.0 compatible (stock), everythinhg has to be 100% stock and not rooted to be able to install the OTA
And if I unlock bootloader I will lose my data. Right?
stivelio said:
And if I unlock bootloader I will lose my data. Right?
Click to expand...
Click to collapse
Yup, there is no other way though. Backup everything you can before you unlock.
-Edit- You could try to root the device with CF Auto Root, install Bootunlocker from PLay and unlock the Bootloader without loosing data. Then unroot from the superSU app and flash the 5.0. radio, wipe caches in recovery or fastboot erase cache and see if the OTA can be installed
by sideloading it in stock recovery, link to the OTA http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
gee2012 said:
Yup, there is no other way though. Backup everything you can before you unlock.
Click to expand...
Click to collapse
Ah ok. I guess I will wait until 5.1 or something to do this when there are major updates
im on android 6.0.1 official want to downgrade to lolipop to flash CM 12
and notficition of app like facebook and whatsapp not appered counter or number a notifiction
I believe you need to downgrade to lp before you can unlock the bootloader and install twrp.
audit13 said:
I believe you need to downgrade to lp before you can unlock the bootloader and install twrp.
Click to expand...
Click to collapse
how to downgrade and what is the unlock boot loader ?
and when i bought phone what is the default ? that boot loader is locked ?
You may be able to use the Panasonic Eluga software to downgrade to lp.
You must unlock the bootloader to install twrp and cm.
Some info here: http://forum.xda-developers.com/idol-3/development/tool-tools-idol-3-5-5-4-7-t3441781
When flashing anything to any phone, things can go wrong; therefore, I suggest that you familiarize yourself with flashing and be ready in case of disaster.
audit13 said:
You may be able to use the Panasonic Eluga software to downgrade to lp.
You must unlock the bootloader to install twrp and cm.
Some info here: http://forum.xda-developers.com/idol-3/development/tool-tools-idol-3-5-5-4-7-t3441781
When flashing anything to any phone, things can go wrong; therefore, I suggest that you familiarize yourself with flashing and be ready in case of disaster.
Click to expand...
Click to collapse
its falid to flash by panasonic eluga it's load to 2 % and falid after that
can i know what's problem
and when i flash by panasonic must to be unlock boot loader ?
You can't flash twrp unless the bootloader is unlocked. The bootloader cannot be unlocked on MM, only LP.
Thread about TWRP: http://forum.xda-developers.com/ido...e-guide-to-getting-root-t3267400#post64231945
hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:
Hi, is It possible to relock bootloader for to have warranty back?
Thanks
once you flash the stock img, it will be locked again.
Till Nougat, we had dload method which locks it fully (other method for unlocking it would just re-lock it)
shashank1320 said:
once you flash the stock img, it will be locked again.
Till Nougat, we had dload method which locks it fully (other method for unlocking it would just re-lock it)
Click to expand...
Click to collapse
Hey, i am in the same situation and after flashing the stock rom + stock recovery my bootloader is still unlocked, and i still get that "This device has been unlocked and can't be trusted" screen on boot.
Is there any way to manually lock the bootloader?
Edit: i found this SRKTool and i was able to easily relock the bootloader. You need the Unlock code though and it resets your phone, so backup your data.
https://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797 @alboz83
Arrandale said:
Hey, i am in the same situation and after flashing the stock rom + stock recovery my bootloader is still unlocked, and i still get that "This device has been unlocked and can't be trusted" screen on boot.
Is there any way to manually lock the bootloader?
Edit: i found this SRKTool and i was able to easily relock the bootloader. You need the Unlock code though and it resets your phone, so backup your data.
https://forum.xda-developers.com/mate-8/development/[email protected]
Click to expand...
Click to collapse
Yes it will only relock the bootloader but not lock. Anyone experienced with this can get this that you had unlocked your bootloader earlier
Arrandale said:
Hey, i am in the same situation and after flashing the stock rom + stock recovery my bootloader is still unlocked, and i still get that "This device has been unlocked and can't be trusted" screen on boot.
Is there any way to manually lock the bootloader?
Edit: i found this SRKTool and i was able to easily relock the bootloader. You need the Unlock code though and it resets your phone, so backup your data.
https://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797 @alboz83
Click to expand...
Click to collapse
I relocked yesterday bootloader and my relocated easily. I can not find the update of stock firmware. Once found update. I clicked on update, update failed. I have not got the update since then. So I did relock. Very easy to relock. But my mobile update is not happening. Please give me some help
Sent from my [device_name] using XDA-Developers Legacy app
shashank1320 said:
once you flash the stock img, it will be locked again.
Till Nougat, we had dload method which locks it fully (other method for unlocking it would just re-lock it)
Click to expand...
Click to collapse
Many people say that if we flash stock rom the bootloader stay unlock. Or i have to flash in a particular mode?
With the tool i can relock but not lock, right?
alboz83 said:
Many people say that if we flash stock rom the bootloader stay unlock. Or i have to flash in a particular mode?
With the tool i can relock but not lock, right?
Click to expand...
Click to collapse
Yup
i Read somewhere that if u flash the stock rom using dload after u have relocked the bootloader, the bootloader status will change from relock to locked. does this work? can anyone try and confirm this? i want to make sure of this before i unlock. I would be greatful forever.
Thanks
Anzee said:
i Read somewhere that if u flash the stock rom using dload after u have relocked the bootloader, the bootloader status will change from relock to locked. does this work? can anyone try and confirm this? i want to make sure of this before i unlock. I would be greatful forever.
Thanks
Click to expand...
Click to collapse
Have tried to this more than 100 times and it works fine. It will be locked BL rather than relock
shashank1320 said:
Have tried to this more than 100 times and it works fine. It will be locked BL rather than relock
Click to expand...
Click to collapse
If u flash stock?
Thank you thank you thank you you're a life saver ♥
Anzee said:
If u flash stock?
Thank you thank you thank you you're a life saver ♥
Click to expand...
Click to collapse
Yes. Did you solve the BL state?
shashank1320 said:
Yes. Did you solve the BL state?
Click to expand...
Click to collapse
No I haven't even unlocked the bl yet. I just wanted to make sure it the relock to lock state was possible before I unlock. I will do so soon when I get some time.
Anzee said:
No I haven't even unlocked the bl yet. I just wanted to make sure it the relock to lock state was possible before I unlock. I will do so soon when I get some time.
Click to expand...
Click to collapse
Yes you can always do via full ota or flashing the stock firmware via dload. Not hard to do to retain warranty:silly:
shashank1320 said:
Have tried to this more than 100 times and it works fine. It will be locked BL rather than relock
Click to expand...
Click to collapse
But dload method not work only for a single update.app file? With view 10 there are 3 files
alboz83 said:
But dload method not work only for a single update.app file? With view 10 there are 3 files
Click to expand...
Click to collapse
Use the first file, update.zip. it will contain a update.app file around 3 GB. Can use this single file.
shashank1320 said:
Use the first file, update.zip. it will contain a update.app file around 3 GB. Can use this single file.
Click to expand...
Click to collapse
Really? And I have to install over the same firmware, not an update? For example, now I'm on 162 build with unlock bootloader. If I install only update.zip of 162 build with dload method, I obtain the lock bootloader?
alboz83 said:
Really? And I have to install over the same firmware, not an update? For example, now I'm on 162 build with unlock bootloader. If I install only update.zip of 162 build with dload method, I obtain the lock bootloader?
Click to expand...
Click to collapse
Yes.
hello all guys!
i have honor 10 (now col-l29)
before rebranding (col-tl10)
may i relock the BL safety?? i have official rom
ecsalos said:
hello all guys!
i have honor 10 (now col-l29)
before rebranding (col-tl10)
may i relock the BL safety?? i have official rom
Click to expand...
Click to collapse
Why you want to relock, to gain warranty?
If so, better dload the current firmware and it will lock it safely.
because, i dont want to see everytime when i reboot my phone,this stupid message, who tells me that i have unlock bl...
i have 8.1.0.151 (c432)
i was downloaded this version when im trying to rebranding.. for official site..
if i relock with this version, the worse scenario it will be...??? brick???
if i dload the current firmware, i will install it with TWRP again? and after it will be locked safety?
and what firmware i must to dload?
I sucessfully installed Orange Fox Recovery in my Redmi Note 7 Pro (violet). But then after that I wanted to go back to the stock rom so I flashed it with Mi Flash. The Rom which I flashed was Global Stable Fastboot Rom (Version 11.0.8.0) but after flashing an error appeared that the system has been destroyed. Then I tried to unlock my bootloader, that took place successfully and my phone booted but the bootloader was still unlocked, I want to lock my bootloader. But whenever I do this the System Gets Destroyed.
You probably have the Chinese version and are flashing the Indian rom. Try to flash the Chinese rom and lock the bootloader and see if it works.
Harsh Ahuja 2509 said:
I sucessfully installed Orange Fox Recovery in my Redmi Note 7 Pro (violet). But then after that I wanted to go back to the stock rom so I flashed it with Mi Flash. The Rom which I flashed was Global Stable Fastboot Rom (Version 11.0.8.0) but after flashing an error appeared that the system has been destroyed. Then I tried to unlock my bootloader, that took place successfully and my phone booted but the bootloader was still unlocked, I want to lock my bootloader. But whenever I do this the System Gets Destroyed.
Click to expand...
Click to collapse
U cant relock ur bootloader bruh ri8 now.
sourav24071999 said:
U cant relock ur bootloader bruh ri8 now.
Click to expand...
Click to collapse
When it can be relock again?
sourav24071999 said:
U cant relock ur bootloader bruh ri8 now.
Click to expand...
Click to collapse
Then when can I relock my bootloader again? Because I want to lock my bootloader
dark3578 said:
You probably have the Chinese version and are flashing the Indian rom. Try to flash the Chinese rom and lock the bootloader and see if it works.
Click to expand...
Click to collapse
No, I never had the China Version it is the Indian Version. Can u send me the link of the Chinese Rom
Harsh Ahuja 2509 said:
Then when can I relock my bootloader again? Because I want to lock my bootloader
Click to expand...
Click to collapse
Let's see.. no info yet
I am also having the same issue. I have tried multiple methods. I flashed Chinese rom, and then tried relocking the bootloader. It did not work.
I also tried flashing MIUI 10, and after flashing the fastboot rom of MIUI, I tried relocking bootloader. It did not work as well.
I want to relock my bootloader.
After unlocking bootloader I am facing just one issue, that is, my internet goes off (volte signal + internet) while receiving an incoming call. While it does not goes off and internet works fine when making outgoing calls. Are you also facing this issue? I am using Airtel.
Also, can someone please help us out?
I have did same it will work for me with unlocked bootloader and got a little issue with accessibility player in youtube
Not a big deal ?