Related
Hello everyone?
My brother just emailed me a question the question in the topic. I told him to ask himself here, but hes at work at XDA is a site he cant access from work.
He had unlocked his bootloader and installed a version of Ginbergread. He then decided to flash back to stock and install the official Gingerbread OTA update, and it worked. Now when he starts his phone up the unlocked indicator is gone, so is he still unlocked and if so, how does he tell?
I think his main goal here is installing CWM Recovery so he can then root using the CWM Recory Root, but honestly, I dont know. Im simply asking the question. So with all that being said, is there a wait to tell if his bootloader is still unlocked or is it always going to be unlocked even if it no longer says unlcoked during the phones start up process?
Now, just in case he asks me, can he install CWM and the CWM Root with official OTA GB Update if he had previously unlocked his bootloader?
I (and my brother) appreciate any info.
if the unlocked text is gone during boot then he will have to unlock the bootloader again but this is not necessary if he only wants to install CWM.
neotekz said:
if the unlocked text is gone during boot then he will have to unlock the bootloader again but this is not necessary if he only wants to install CWM.
Click to expand...
Click to collapse
When bootloader is unlocked, it remains unlocked. You do not have to unlock it again! The word unlocked disappears when you flash back.
Once unlocked, always unlocked!
Sounds good. So if he wants to install CWM, can he just follow this guide: http://forum.xda-developers.com/showthread.php?t=1138541 to install CWM?
I had assumed thats what he wanted to while I was waiting for a reply I emailed him and I was right. He plans on installing CWM and then then root.zip. Will that work?
JohnnyDanger said:
Sounds good. So if he wants to install CWM, can he just follow this guide: http://forum.xda-developers.com/showthread.php?t=1138541 to install CWM?
I had assumed thats what he wanted to while I was waiting for a reply I emailed him and I was right. He plans on installing CWM and then then root.zip. Will that work?
Click to expand...
Click to collapse
he can follow instructions in that post or he can root, download rom manager from market and install cwm recovery from within the app.
although tenfar's recovery works flawlessly on ATRIX and cwm can't wipe or read from external sd card.
to reiterate, ONCE UNLOCKED, ALWAYS UNLOCKED!!!
hope this helps.
Sent from my MB860 using XDA App
That does help. Thanks a lot. Im hoping to get him involved here. I think he can learn a lot. The Atrix is his first smartphone and I think he is just starting to really dig in. Hes not so concerned with messing things up as he has a lot of expendable income, but I think the more he knows, the more he will enjoy his phone.
With this one you can not fool around, why I said this, because if you unlock your bootloader and have the "unlocked" tag at boot but then you flash by RSD MOTO 2.3.4/4.5.91 sbf you will lost the tag at boot, actually your bootloader still unlocked but not funtional until you reflash pudding again. But my point if someone want to service their phone and want to reflash MOTO 2.3.4/4.5.91 sbf so the simple customer service guy did not figure out that you mess with your phone unlocking it, yeap it work for the simple CS guy but for tech guy nope because of the following statement:
If you want to confirm your status:
adb->su->and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000100004000
Here is the mean of some of those numbers:
10000000000010001000100004000
4= BL "unlock" Bootloader Unlock out of warranty unit
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW (fruit cake, etc)
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB MOTO OTA<- this guy can NOT RSD ANY MOTO SBF DOWNGRADE 1.26 / 1.57 / 1.83
I hope it help!
CaelanT said:
When bootloader is unlocked, it remains unlocked. You do not have to unlock it again! The word unlocked disappears when you flash back.
Once unlocked, always unlocked!
Click to expand...
Click to collapse
Yeap TRUE , but when you lost the "unlocked" tag because you reflash 2.3.4 SBF you will lost the "unlocked" tag, so unit still with bootloader unlocked but is not 100% functional, you will not able to moto-fastboot partitions until you reapply pudding again and I think this due to the microboot partition (I think CG47)
rafkong said:
he can follow instructions in that post or he can root, download rom manager from market and install cwm recovery from within the app.
although tenfar's recovery works flawlessly on ATRIX and cwm can't wipe or read from external sd card.
to reiterate, ONCE UNLOCKED, ALWAYS UNLOCKED!!!
hope this helps.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
tenfar's CWM can read both the internal and external SD card, you must have the most up-to-date version though. 4.0.0.2 i believe.
mramirezusa said:
If you want to confirm your status:
adb->su->and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000100004000
Here is the mean of some of those numbers:
10000000000010001000100004000
4= BL "unlock" Bootloader Unlock out of warranty unit
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW (fruit cake, etc)
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB MOTO OTA<- this guy can NOT RSD ANY MOTO SBF DOWNGRADE 1.26 / 1.57 / 1.83
Click to expand...
Click to collapse
That was brilliant, thanks! My Atrix reports the following:
cat /sys/firmware/fuse/ReservedOdm
30000000000030001000300004000
so is it safe to assume that it's unlocked. I'm curious to know what the starting digit (3 in my case) means, as it's different from your example.
Mine looks nothing like your lol
20000000000020002000200004000
I can downgrade all the way back to 2.2
Is there a way to relock bootloader? I tried flashing stock rom via TWRP but the prompt still shows that Device cannot be trusted blalbla unlocked.
Can anyone give me a way how to relock my BL? I also tried SRK tool with relock bootloader with my Unlock code, but it doesnt work.
Thanks
EDIT: Please lock thread. I tried locking via eRecovery and it worked. Thanks
Update your device. Use the full update rom like b161, 201 or whatever you like. That will remove the unlocked bootloader and root as well.
ErvinSoliven said:
Update your device. Use the full update rom like b161, 201 or whatever you like. That will remove the unlocked bootloader and root as well.
Click to expand...
Click to collapse
are u tested it?
mi.alkhamis said:
are u tested it?
Click to expand...
Click to collapse
Yes is tested: at any update (via dialer or three key pressed) with stock firmware, you lose root, twrp and unlocked bootloader (if you have root, twrp and bootloader unlocked).
gtdaniel said:
Yes is tested: at any update (via dialer or three key pressed) with stock firmware, you lose root, twrp and unlocked bootloader (if you have root, twrp and bootloader unlocked).
Click to expand...
Click to collapse
thanks for quick reply/
another question .
i have vns-l21c900b140 .Which ROM root and boot loader problem solved ?
and i download vns-l21c432b160 can i flash this file without any problem such as Antenna ؟i
You have to debrand your phone to make it C432 from C900. Read around forum...
I tried to root H918 T-Mobile, and ended up with just an unlocked bootloader, and no TWRP install.
I'd like to re-lock the bootloader, but I can't find any instructions. Any unroot instructions I've seen, include using TWRP.
Thanks!
Same here, before i ended up bootloader unlocked. Well decided to relock the bootloader
Just fastboot oem locked
jay661972 said:
Same here, before i ended up bootloader unlocked. Well decided to relock the bootloader
Just fastboot oem locked
Click to expand...
Click to collapse
OK. Tried this....and now I get:
Your device is corrupt
It cannot be trusted
and will not boot
Please help!
jeffeil said:
OK. Tried this....and now I get:
Your device is corrupt
It cannot be trusted
and will not boot
Please help!
Click to expand...
Click to collapse
have to wipe the whole phone you must have a custom boot.img
the t-mob version is unlocked via lgs website right
Try this method. As far as I know everything is back to stock at least it acts like it is.
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
Old thread but i found it while trying to restore my US996 back to factory. The kdz method works then you just run the fastboot command to relock the bootloader. Amazing it was that easy to relock the bootloader....
I flashed the 10s update to h918 and very stupidly forgot to flash root so I'm stuck on unrootable 10s. I want to lock my bootloader so can at least have Android Pay working, if i lock it can it be unlocked again or do i have to wait for a root method for the new 10s software?
nymikey said:
I flashed the 10s update to h918 and very stupidly forgot to flash root so I'm stuck on unrootable 10s. I want to lock my bootloader so can at least have Android Pay working, if i lock it can it be unlocked again or do i have to wait for a root method for the new 10s software?
Click to expand...
Click to collapse
I think you can unlock /relock as many times as you want. Root take place after unlocking but you can't do that anymore.
I rooted my v20 f800l a few months ago using dirty Santa method. Everything was going fine until I decided to reset my phone via twrp. I selected system, internal memory, cache and ended up without an os with only access to twrp. I had a nandroid backup but twrp couldnt read or detect the nandroid backup files. With nothing else left to do i flashed it with a kdz file version 10e using lgup software. Now I have my phone running fresh os very smoothly but the bootloader is locked and root/twrp is not there anymore. Now I plan on rooting it again as I'm still on 10e version but I'm not sure if there is a bootloader lock/relock limit, I've already unlocked bootloader once and locked it once, can I do it again? Or is there a limit to it? Please help
lamepsycho said:
I rooted my v20 f800l a few months ago using dirty Santa method. Everything was going fine until I decided to reset my phone via twrp. I selected system, internal memory, cache and ended up without an os with only access to twrp. I had a nandroid backup but twrp couldnt read or detect the nandroid backup files. With nothing else left to do i flashed it with a kdz file version 10e using lgup software. Now I have my phone running fresh os very smoothly but the bootloader is locked and root/twrp is not there anymore. Now I plan on rooting it again as I'm still on 10e version but I'm not sure if there is a bootloader lock/relock limit, I've already unlocked bootloader once and locked it once, can I do it again? Or is there a limit to it? Please help
Click to expand...
Click to collapse
Don't believe there's any limit so go ahead
Sent from my LG-H910 using XDA Labs
I just want to know if it is possible to root and install twrp on htc 10 evo without unlocking the bootloader
Also I want to know if I was able to do this, will the phone be still receiving ota updates?
saviola123 said:
I just want to know if it is possible to root and install twrp on htc 10 evo without unlocking the bootloader
Also I want to know if I was able to do this, will the phone be still receiving ota updates?
Click to expand...
Click to collapse
No need bootloader unlocked so can flash twrp it can get it's updates but have to do it a certain way and I'm don't remember how .I flashed twrp but having problems getting to it was problem on my phone good luck
Hi there,
I have a problem in downgrading my moto g4 play. I have stuck with this problem when I was flashing Android 7.1.1 (HARPIA_NPI26.48-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) via RSD lite 6.2.4. RSD lite failed during flashing boot.img. After that I tried to downgrade to 6.0.1 with this stock rom (XT1607_HARPIA_AMAZON_USA_MPI24.241-2.35-1_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml).
I would like to mention that I have tried same steps with ADB + Fastboot and I was getting the same answer from the phone "version downgraded for boot. Failed to validate boot image"
As I know, the official stock ROMs work without any problem with a locked bootloader.
But I would like to ask is there any other methods for flashing android nougat or downgrade?
Thanks
genadik said:
Hi there,
I have a problem in downgrading my moto g4 play. I have stuck with this problem when I was flashing Android 7.1.1 (HARPIA_NPI26.48-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) via RSD lite 6.2.4. RSD lite failed during flashing boot.img. After that I tried to downgrade to 6.0.1 with this stock rom (XT1607_HARPIA_AMAZON_USA_MPI24.241-2.35-1_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml).
I would like to mention that I have tried same steps with ADB + Fastboot and I was getting the same answer from the phone "version downgraded for boot. Failed to validate boot image"
As I know, the official stock ROMs work without any problem with a locked bootloader.
But I would like to ask is there any other methods for flashing android nougat or downgrade?
Thanks
Click to expand...
Click to collapse
You can't manually downgrade/upgrade the Amazon variant of this device.
Can I use Blank Flash tools for restoring my device?
genadik said:
Can I use Blank Flash tools for restoring my device?
Click to expand...
Click to collapse
Bootloader locked Amazon varient? Not likely.
Sorry that my question will look a bit stupid...But if it's not hard for you, can you explain why??
Thanks
genadik said:
Sorry that my question will look a bit stupid...But if it's not hard for you, can you explain why??
Thanks
Click to expand...
Click to collapse
Commands needed to access essential partitions/files (eg: aboot) are blocked on most devices with a locked bootloader. You can certainly try - me thinks the possibility of yielding an unrecoverable brick outweighs any possible benefit.
Best case it simply fails.
So, in this case, the only solution s service center?
genadik said:
So, in this case, the only solution s service center?
Click to expand...
Click to collapse
Yep (the only reasonable solution IMHO).