I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?
Related
I read through many threads and have followed the official Sony bootloader unlocking instructions. I have requested and received the unlock code from Sony via email. I have downloaded the inf file and placed it in the correct folder in Android SDK (which I also updated). But I am cannot access fastboot mode, I hold down Vol + and plug in the USB cable but the device shows a red led and goes into charging mode. Also the PC never prompts me to install fastboot driver it simply loads the SP as Sony mass storage device (in device manager).
I have read that some people seem to think that the SIM lock affects the ability to access fastboot but this SP is SIM unlocked. Sony's official guide to unlocking the bootloader says I need to access fastboot mode to enter the unlock code but how can I unlock the bootloader if I can't get into fastboot mode?
hmmm... don't know really... i once entered fastboot mode by mistake, while trying to root stock rom. wasn't reading instructions and put device in a fsatboot mode instead of debugging... was on stock rom so don't know if custom rom would let me do that. should check myself... if anything i know it is possible to get me that blue light shining.
To enter fastboot mode in Xperia SP just power down the phone and hold down the volume up key while pluging your phone into your pc
If you need flashmode do the same thing but with the volume DOWN button held down.
I´ve got the same problem. I can´t enter in flashmode neither in fastboot mode. I´m on windows 8 32bits and I installed the .245 Deodexed ROM with a problem on root and without CWM. I don´t know what to do now, please help me.
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
jackaros said:
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
Click to expand...
Click to collapse
Thanks for trying to help, but I understand that flashmode and fastboot are accessed using the phone. Actually the phone needs a piece of software like flashtool to keep it in flashmode otherwise it drops into charging mode. I didn't mention my computer so I don't know where you got that from.
As I explained, I am unable to access fastboot with stock ROM (1.257) and a custom ROM (based on 2.245) so it can't be a ROM bug or the flashing process having gone wrong.
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Ze Tolas said:
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Click to expand...
Click to collapse
It may be a flashtool problem you are right because 2 incidents with different Roms that both use flashtool to flash those roms.....
its pretty much self explenatory.
skojevac said:
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Click to expand...
Click to collapse
Interesting. Ok, I've read up on the process. So I use the various stock .ftf files and flashtool with the phone in flash mode? Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. If I do it, I will nandroid backup first, of course, but I think I remember reading in one thread that someone managed to soft brick their XSP doing this very thing.
Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. [/QUOTE said:
that's why you need to complete rooting procedure. root stock 1.257 kernel, than back to stock 2.245 with root preserved, and before you would install CWM try to put device in a fastboot mode, this assuming you still have a UB.
Click to expand...
Click to collapse
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
SuicideFlasher said:
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
Click to expand...
Click to collapse
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
skojevac said:
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
Click to expand...
Click to collapse
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
gandalf_grey91 said:
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
Click to expand...
Click to collapse
I said before, it's new firmware (maybe RU) with a Windows Flashtool issue. Today i did flash kernel to my SP using Linux client.
Same issues
gandalf_grey91 said:
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
Click to expand...
Click to collapse
Hi, I have some similar issues. I've also been flashing some stuff and whenever I try to go to fastboot it just boots into CWM. Very annoying to say the least. The dark blue light goes on when i hold down volume up and for a short moment I see the fastboot driver installing on my computer. But before it completes it's already in CWM.
Not sure what to do from here on wards, maybe some advice on which kernel to flash? I am pretty sure the latest kernel I flashed is the .254 root kernel from doomlord.
Ps. I really would like to flash CM when it becomes available as nightly :angel:
Thanks in advance!
Fast boot mode for xperia ion hspa???
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
I had already installed cm10.1 jb for my xperia ion.
Now i tried to install cm11 kitkat for my xperia ion.
Every thing is gone good.
But now got stuck up with a problem.
fast boot mode is active only for 5 seconds while connecting my xperia ion to System with flash tool.
help me to do the need ful.
Guide me to download compatible drivers and flash tool for fast booting process.
If you have UNLOCKABLE bootloader, then you dont have a FASTBOOT mode on your phone. Its just pure luck. some phones dont have it... kind of a sony crap... I also happen to be one of those LUCKY ppl. no unlock, so stuck with Stock kernel forever.
When you connect your phone to Flashtools in FLASHMODE...
See for a string BOOTLOADER: NOT_ROOTABLE.... it means you belong in the lucky group...
If it says rootable, then you're doing something wrong.
Pardon me if i read something incorrect. i skimmed through all the posts before posting.
Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.
Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer
If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)
err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.
Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.
Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.
Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking
toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.
You don't need adb.
sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
Any help, advice etc would be hugely appreciated. Thanks
Markh2001 said:
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
Any help, advice etc would be hugely appreciated. Thanks
Click to expand...
Click to collapse
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
AndroidSlave said:
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Click to expand...
Click to collapse
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Markh2001 said:
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Click to expand...
Click to collapse
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Markh2001 said:
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2588979 for easy adb installation. Read this too http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481.
To get into bootloader mode power down the device and after that press volume down + power. Here`s a guide to setup the sdk/adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Markh2001 said:
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Click to expand...
Click to collapse
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Markh2001 said:
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Click to expand...
Click to collapse
There is nothing you can do with a locked bootloader, claim warranty/RMA
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Markh2001 said:
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Click to expand...
Click to collapse
Next time enable usb debugging and ENABLE OEM UNLOCK, both in developer options. You can flash the latest firmware available directly in fastboot by flashing the individual img files.
Here is a link to setup adb/platform-tools https://www.google.nl/url?sa=t&rct=...orial/&usg=AFQjCNGolazOWoMssTikMpokJ6TtwEND5A.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Markh2001 said:
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Click to expand...
Click to collapse
Well click the power button and in the next screen scroll down with the volume button to select yes and push power.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Markh2001 said:
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Click to expand...
Click to collapse
Click yes, see my above post
gee2012 said:
Click yes, see my above post
Click to expand...
Click to collapse
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Markh2001 said:
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Click to expand...
Click to collapse
Sure, but first we have to get the phone working again,
Hi guys, thank you ahead for helping me.
I've unlocked the bootloader successfully and installed TWRP and Rooted, but found some issues with Banking apps, PayPal, NFC, Google pay, so I decided to lock the bootloader again.
Following the procedure by Jerry08 downloaded C35, installed via TWRP, and stock recovery was restore just fine.
But while trying to access Bootloader I'm not able to, tried:
adb reboot fastboot
adb reboot bootloader
Holding Vol down and power
Deep-in test says: "you can only apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode"
Last method worked, I get "bootloader" with Chinese words flashes for a second and then reboots to system.
I'm able to boot into stock recovery, but not into Bootloader for some reason, Formatted Data and tried again without luck.
Any suggestions?
Installed RMX1931EX_11_A.09_200116_dfb212dd.ofp with Auth-Flash and MSMTool, you need to purchase credits 7$, use #3 MSMtool from Auth-fash and done bootloader locked and brand new phone.
But bootloader was still unlocked, and not able to access bootloader via adb reboot bootloader.
In-deph test exit does not work either
any updates i have the same problem
mike_san said:
Installed RMX1931EX_11_A.09_200116_dfb212dd.ofp with Auth-Flash and MSMTool, you need to purchase credits 7$, use #3 MSMtool from Auth-fash and done bootloader locked and brand new phone.
But bootloader was still unlocked, and not able to access bootloader via adb reboot bootloader.
In-deph test exit does not work either
Click to expand...
Click to collapse
solved ????
terrymorris said:
solved ????
Click to expand...
Click to collapse
Nope, still cant access to bootloader to lock it, it keeps rebooting even after using realme flash.