Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
xida1125 said:
Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
Click to expand...
Click to collapse
Wipe cashes in the recovery, if it doesn't help flash latest factory image without userdata
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
xida1125 said:
Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
Click to expand...
Click to collapse
In my experience with bootloops is that when you you update to an new ROM sometimes the kernel gets affected in the process. It's happened to me a few times but my phone is rooted so I do a lot more flashing and updating.
It's an easy fix tho, use the Toolkit and open the Launch screen look at the top middle and there should be a tab for flashing the boot.img, in your case since your on stock ROM just restore the image file for the build number that is currently running. So if you just updated to Android N, the build number will start with an N. The toolkit will install the correct file to restore the phone back to normal working order.
His bootloader is locked, thus he can't use the toolkit or fastboot.
@xida1125: Enter into the recovery and wipe the cache. That may fix the bootloop. If it doesn't, download the latest OTA and sideload it. Be prepared for the possibility of having to factory reset the device if nothing else works.
Strephon Alkhalikoi said:
His bootloader is locked, thus he can't use the toolkit or fastboot.
@xida1125: Enter into the recovery and wipe the cache. That may fix the bootloop. If it doesn't, download the latest OTA and sideload it. Be prepared for the possibility of having to factory reset the device if nothing else works.
Click to expand...
Click to collapse
I'm gonna try that tonight, not sure how to sideload it but I'm sure I'll figure it out. I already gave my mom my Nexus 6P to use and she likes it because it has a better camera. I tried factory reset in bootloader but it didn't do anything. Forgot to try and go into recovery menu.
If you've switched devices with your Mom, you can probably factory reset in recovery without issue. Sideloading an OTA is reasonably easy. Download the OTA, move it to internal storage, and from recovery there should be a menu option to sideload the OTA.
Once you've gotten everything fixed, dig into the developer options and enable oem unlocking in both the N6 and the N6P. Doing so will not unlock the bootloader, but will give you the opportunity to unlock the bootloader if the need or want arises in the future.
Strephon Alkhalikoi said:
If you've switched devices with your Mom, you can probably factory reset in recovery without issue. Sideloading an OTA is reasonably easy. Download the OTA, move it to internal storage, and from recovery there should be a menu option to sideload the OTA.
Once you've gotten everything fixed, dig into the developer options and enable oem unlocking in both the N6 and the N6P. Doing so will not unlock the bootloader, but will give you the opportunity to unlock the bootloader if the need or want arises in the future.
Click to expand...
Click to collapse
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Based upon your descriptions, it's sounding more and more likely that you have a dead emmc chip. In other words, hardware failure.
xida1125 said:
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Click to expand...
Click to collapse
May you try the steps without a inserted simcard, otherwise I hope for you it's not the hardware
xida1125 said:
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Click to expand...
Click to collapse
OK... Here we go...
You have fastboot and adb on your computer?
Boot to fastboot... On your phone
Use fastboot to wipe userdata and cache... (I forget the commands... Google is your friend)
Try and boot... Be patient... It's gotta rebuild ART... Will take some time
If no boot...
I THINK... THINK (repeated because I don't know for sure) you can flash the factory images without unlocking the bootloader... Because they are signed by Google...
FWIW... It's something on your data partition... Or in cache...
It sounds like the phone shutdown while writing to disk...
As long as you haven't done something really dumb... Like wiping boot, aboot, system, etc... You should be able to bring it back...
Also... There is a fastboot command that will tell you partitions on the device... Not sure if the N6 has the command... That would give you more information...
This... Is a textbook example of why you shouldn't use toolkits... You're stuck... And haven't read enough or experimented enough to know how to fix your device...
Related
Hi all,
Got a sensation XL here which isn't rooted, nor has it been altered in anyway, not sure what happened to it to be honest and it's not actually mine either.
It's still s-on, I can get to the bootloader no problem, but factory reset just doesn't do anything, it just puts it back in the boot loop.
Any ideas?
Thanks.
PS: I'm thinking it's bricked.
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
MinecraftZombi.es said:
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
Click to expand...
Click to collapse
It's not been unlocked, it's just a stock handset, not branded, so with the official ruu, how do i flash it?
Thanks for replying m8.
make sure htc sync is installed on a PC (just for the drivers, you don't want to actually use it)
Plug the phone in via the USB (Direct, not through a hub)
Run RUU file on PC.
that should be it.
Thanks pal, fingers crossed eh.
Will let you know if it worked.
It didn't work
Tried both of the Europe RUU's but it still hasn't worked, says signature error?
Both of the files took an hour to download each.
Seriously hating this now
Any other ideas??
Thanks.
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
MinecraftZombi.es said:
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
Click to expand...
Click to collapse
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
dladz said:
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
Click to expand...
Click to collapse
Actually no i didn't i just used the HTC method.
What can i flash to get this thing working man, it's killing me, even factory reset doesn't work? That's just not normal, i'm s-on, i don't think theres an s-off method for the XL yet? Maybe there is.
But i'm really restricted as to what i can do, i've got fastboot and it works fine but besides that i'm lost.
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Ok so it's not bootlooping now on factory reset, it's just stopped on the white HTC screen after hitting factory reset.
I'll leave it there for a bit and see how it goes, i don't think it's going to progress though.
The device is defo unlocked.
Going into recovery brings it back to the bootloop.
It's different on factory reset just not recovery and neither are progressing, i'll give the other recovery a whirl.
Lol failed battery low
MinecraftZombi.es said:
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Click to expand...
Click to collapse
Nah m8, none of them worked or changed anything, the only difference being that factory reset on the stock recovery just stayed on the white htc screen, no change besides that.
Any other ideas? and thanks for taking the time to help me too.
I appreciate it.
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
MinecraftZombi.es said:
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
Click to expand...
Click to collapse
well i've been looking for some official ruu's to flash, one up from the one i'm on would do it i reckon, or at least give me a starting block.
I tried the test rom from a thread and now i can't find it
Will look again, find it and flash it, the test one didn't work, so i'm going to try a slightly older one.
fingers crossed, again.
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
Hi guys,
I seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!
Gunny007 said:
Hi guys,
I seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!
Click to expand...
Click to collapse
instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
clsA said:
instructions
Click to expand...
Click to collapse
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.
Gunny007 said:
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.
Click to expand...
Click to collapse
your just flashing a rom ...nothing to do with getting updates
clsA said:
your just flashing a rom ...nothing to do with getting updates
Click to expand...
Click to collapse
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!
Gunny007 said:
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!
Click to expand...
Click to collapse
Good to here
Hi,
I've just gotten a friend's HTC one that is soft bricked. Bootloader, Recovery and RUU are accessible, but normal boot hangs. hboot is 1.55
There's some important data on the phone he asked me to recover, pics, contacts etc. However, I can't think of a way to access the data. ADB is unauthorized ofcourse.
Can anyone think of a way to authorize adb, pull the whole emmc or just make the whole system boot somehow, maybe issuing some command for minimal/safe boot using fastboot -c?
Thanks,
Nemesis_00 said:
Hi,
I've just gotten a friend's HTC one that is soft bricked. Bootloader, Recovery and RUU are accessible, but normal boot hangs. hboot is 1.55
There's some important data on the phone he asked me to recover, pics, contacts etc. However, I can't think of a way to access the data. ADB is unauthorized ofcourse.
Can anyone think of a way to authorize adb, pull the whole emmc or just make the whole system boot somehow, maybe issuing some command for minimal/safe boot using fastboot -c?
Thanks,
Click to expand...
Click to collapse
is the bootloader locked?
alray said:
is the bootloader locked?
Click to expand...
Click to collapse
Yes, it's fully stock. Otherwise I would have flashed a different recovery and pulled everything off it.
Unlocking the bootloader will wipe the phone.
Nemesis_00 said:
Yes, it's fully stock. Otherwise I would have flashed a different recovery and pulled everything off it.
Unlocking the bootloader will wipe the phone.
Click to expand...
Click to collapse
yeah I know.
You probably already tried every basic thing to make the reboot to the OS? Like erasing cache, re-flashing the kernel or even the entire firmware?
alray said:
yeah I know.
You probably already tried every basic thing to make the reboot to the OS? Like erasing cache, re-flashing the kernel or even the entire firmware?
Click to expand...
Click to collapse
I had erased the cache, it didnt help.
How can I re-flash only the kernel or the system partition with a locked bootloader and S-ON?
I can flash the whole RUU, but it will wipe the device.
Any other ideas?
Thanks
So my phone has decided to soft-brick itself after upgrading to Lollipop. It never even made it a single normal bootup after the upgrade. I get to the Optimizing Apps screen and then it shuts itself down after that finishes. I can't get into the OS, but I can boot into Recovery Mode. I've tried to wipe the cache partition to no luck. I haven't tried to Wipe Data/Factory Reset because I want to try and recover my data.
I haven't rooted the device or put on a custom recovery. Is there any way to get in there and grab the files off? I can see the device listed under 'fastboot devices' using ADB but don't know where to go from here. I tried to flash a custom recovery but it doesn't work because the bootloader is locked?
Am I basically screwed and my only option to just factory reset and lose my data?
I found a rooted ROM on rootjunkysdl (sorry I'm new and can't link) Can I use RSDLite to flash that on the device and go from there?
achobgood said:
So my phone has decided to soft-brick itself after upgrading to Lollipop. It never even made it a single normal bootup after the upgrade. I get to the Optimizing Apps screen and then it shuts itself down after that finishes. I can't get into the OS, but I can boot into Recovery Mode. I've tried to wipe the cache partition to no luck. I haven't tried to Wipe Data/Factory Reset because I want to try and recover my data.
I haven't rooted the device or put on a custom recovery. Is there any way to get in there and grab the files off? I can see the device listed under 'fastboot devices' using ADB but don't know where to go from here. I tried to flash a custom recovery but it doesn't work because the bootloader is locked?
Am I basically screwed and my only option to just factory reset and lose my data?
I found a rooted ROM on rootjunkysdl (sorry I'm new and can't link) Can I use RSDLite to flash that on the device and go from there?
Click to expand...
Click to collapse
The rooted rom that you see there is a kitkat rom. Since your bootloader is now expecting lollipop, flashing that would be a very bad idea. In fact, since you've taken the lollipop update, the odds of you ever being able to root your device are unfortunately near 0. But to answer your question, full firmware files for the 5.1 Turbo firmware have not yet been released by Verizon. That's what you would need to flash with RSDlite. So your options are to wait for those or to factory reset.
TheSt33v said:
The rooted rom that you see there is a kitkat rom. Since your bootloader is now expecting lollipop, flashing that would be a very bad idea. In fact, since you've taken the lollipop update, the odds of you ever being able to root your device are unfortunately near 0. But to answer your question, full firmware files for the 5.1 Turbo firmware have not yet been released by Verizon. That's what you would need to flash with RSDlite. So your options are to wait for those or to factory reset.
Click to expand...
Click to collapse
Would something like this work? http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
If it's just for a hardbrick could I flash the wrong firmware then use this tool to get it working again?
achobgood said:
Would something like this work? http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
If it's just for a hardbrick could I flash the wrong firmware then use this tool to get it working again?
Click to expand...
Click to collapse
At a glance, it seems like that should work. I'm not too familiar with that method. Also, you're in luck. It seems that Verizon dropped the official image today. You can find it here: http://forum.xda-developers.com/dro...-5-1-image-t3152229/post61744745#post61744745