Related
So I unlocked the bootloader and then rooted my phone using the guide from The Unlockr. Now when I boot up my N1, I get to the screen with the still Nexus logo and a lock under it. It will sit there and not do anything else.
What is going on?
How can I get my phone working right again?
When I go to recovery, it will show the X with the lock under it and then it will go black and do nothing...
It does not seem that you have unlocked it yet. Try to do it via ADB and fastboot
What are the exact steps you did?
After unlocking bootloader did you install a custom recovery and flash a Rom?
I first set up ADB on my computer.
Then I rooted my phone with Superboot.
I followed these steps:
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
To me, it sounds like the installed superboot isn't compatible with your Nexus One. And also note that that guide was from early 2010, around which Froyo was around.
Try looking for a more up-to-date guide.
Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
cuongcn said:
Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
Click to expand...
Click to collapse
did u update hboot with an unlocked bootloader...thats no good
are u still can access Hboot?
sometimes, u should flash a kernel with ROM to work on it. if you still running Stock ROM, don;t flash MOD kernel like Holiraider. it will couse boot loop.
if u still able to access HBOTT, no need to worry.
@meatwad0222: I unlocked bootloader and updated hboot. It succeeded in rooting the phone. I got problem when I tried to flash a kernel.
@prahasta: I can't do anything. The phone never turned on again, even if I plugged the charger, the LED was not on. Pressing power button with volume down did not work at all. In general, I can't access to hboot.
Hm... It will be difficult.. hope it wasn't couse by hardware.
Sent from my HTC Raider X710e using xda premium
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
austin4913 said:
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
if Bootloop, at least u still can access HBoot, but he can't do that.
try to connect it to PC with Full Battery. then check if your PC still detect it. if PC can detect it, try to flash Official RUU.
My laptop does not recognized it. It said that it can't find a driver for that. I searched in xda-forum and I found the driver. Right now, in the device manager of my laptop, it says Qualcomm HS-USB QDLoader 9008. I tried to flash an office RUU but it stopped at <waiting for device>
Thank for your replies.
good to hear your laptop still detect the phone.
u need to pick right RUU for your device.
used Hanson tools, choose to unlock your bootloader again (hope this work). after unlock bootloader, and u can acces HBOOT, choose fastboot mode then instal CMW/WCXs recovery. once done, try to access CWM. if u can acces CWM recovery, there is no worries anymore, u just need to instal correct ROM and Kernel.
My laptop only detects the phone as a Qualcomm chip, not as a phone. When running Hasooon tool, it stops at <waiting for device>.
Sounds like it's in dload mode.
If your phone is in dload mode then I think that is a soft brick...it is fixable, from what I read on another thread, but is more difficult...but not impossible..I had to download HTC drivers for my laptop...the following 2 sites contain the files.
http://forum.xda-developers.com/showthread.php?t=1450105
http://www.theandroidsource.com/viv...65-latest-htc-vivid-sync-driver-download.html
Sent from my HTC PH39100 using xda premium
I talked to HTC customer service for repairing. After everything was set up, I thought that I lost my warranty since I rooted my phone (in HBoot, it said RE-LOCK"). I will give a try with the "wire trick" in the thread "Juopunutbear S-OFF". Hopefully after wire those holes, I can access to the debug mode and "wake up" my phone. Otherwise, I have to spend $5 more to buy those warranty stickers on eBay and have the phone fixed.
I thought that it would be a jtag, but it was not. I did not succeed. I have to send it to HTC for repair.
I think I know the reason caused my problem. I tried to recover why I was on S-ON. Thus, the firmware will "fight" each other and the hardware will not know what it should do. The result is a software-bricked phone.
Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.
megahafo said:
Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.
Click to expand...
Click to collapse
What is happening when you enter recovery?
MacHackz said:
What is happening when you enter recovery?
Click to expand...
Click to collapse
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.
megahafo said:
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.
Click to expand...
Click to collapse
try reflashing it and wiping cache etc
MacHackz said:
try reflashing it and wiping cache etc
Click to expand...
Click to collapse
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.
Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?
tokenwoken said:
Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?
Click to expand...
Click to collapse
The cue there if wiping the cache partition.
Riyal said:
The cue there if wiping the cache partition.
Click to expand...
Click to collapse
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?
Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash
tokenwoken said:
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?
Click to expand...
Click to collapse
I had the same problem, going to try to sideload this stock de-odexed rom (didn't work the first few times) and CHILL THE PHUCK out until AOKP.
scared me lol first HTC device, brand new, and I thought I broke it.
P.S I realized that REVOHD uses AROMA, that's why it wouldn't sideload.... Am I Rite?
Similar issue
tokenwoken said:
Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash
Click to expand...
Click to collapse
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!
Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
thanks but....
shrex said:
Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.
suhazgummadi said:
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.
Click to expand...
Click to collapse
You have the zip file of ARHD in your pc extract the boot.img using winrar thats it and you have to put that file in abd/fastboot folder in pc
and everything what i said its to be done in pc
excpet putting phone in fastboot mode
suhazgummadi said:
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!
Click to expand...
Click to collapse
The Sprint version is never going to work on any carrier other than Sprint. It's a CDMA device. The sim slot if for connecting to Sprint's LTE network, but requires a CDMA connection first and foremost to work at all.
Sent from my HTC One using xda premium
Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
megahafo said:
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.
Click to expand...
Click to collapse
Quickest and easiest way to fix this issue is...
'fastboot erase cache'
'fastboot reboot recovery'
hnt20 said:
Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
Click to expand...
Click to collapse
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?
HumorousMaximus said:
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?
Click to expand...
Click to collapse
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:
mky4b11 said:
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:
Click to expand...
Click to collapse
Thanks for the tip, I was able to get back into AROMA but the original issue that got me to this point came up again. Aroma installer runs and during the install it kicks itself out and sends me back to recovery, so the installer doesn't complete. It gets to about 30% and craps out just after it writes system data and starts to install the .apk's. Screen goes black and it reboots itself and sends me to recovery.
thoughts?
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.
Have the same problem and try to solve it with Motorola. No luck at the moment.
lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot
simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.
rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).
You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.
beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...
You're all using the newest fastboot?
flash the factory img
edit.. nevermind, i see ive already said that
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
have you tried fastboot oem unlock again ?
uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk
claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.
holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.
Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.
Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!
You can lock boot loader, you just have to make sure your phone boots first before locking it