Pre-history:
Some day I decided to test different kernels on Nexus 5 ..
And after few tests I accidentally flash kernel (via recovery zip) for Nexus 4 to my Nexus 5....
And as I learned later:
N4 - /dev/block/mmcblk0p6 - is boot (kernel)
But!
N5 - /dev/block/mmcblk0p6 - is bootloader
And when I reboot device, I haven't bootloader.... ---> and I haven't fastboot or adb access...
Then...... Goooogle..... No result... All program use adb or fastboot which I haven't...
Then despairingly I try to hold different combinations of hardware buttons...
And!!!
I found second (reserve) bootloader on Nexus 5!!
I hold for a few seconds all buttons
Added: your device must be powered off!
Volume up + power - this will power off your Nexus 5!
Volume up + down + power - this will boot reserve Bootloader
And then I see partition table for Nexus 5 and restore my primary Bootloader using "dd" command ))
su
dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6"
Information:
N5 - /dev/block/mmcblk0p6 - aboot - is primary bootloader
N5 - /dev/block/mmcblk0p11 - aboot - is reserve bootloader
Sorry for my English...)
yea, that second bootloader has been known about for a while now. but, good job at fixing your device, and its a good post with great info
This is the first time when booting to the secondary bl have saved the phone.
I have tried to tell many people to try to hold down all the buttons to get into the secondary bl but they were simply unable to do that.
Maybe this only works when aboot partition damaged, and in other cases when tz, rpm, sbl1 or sdi got overwriten it simply does not work.
There are sbl1b, tzb, rpmb but there is no backup partition for sdi
Upon a bl upgrade these are the partition which got updated: sbl1, aboot, sdi, tz, rpm
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
This is the first time when booting to the secondary bl have saved the phone.
I have tried to tell many people to try to hold down all the buttons to get into the secondary bl but they were simply unable to do that.
Maybe this only works when aboot partition damaged, and in other cases when tz, rpm, sbl1 or sdi got overwriten it simply does not work.
Click to expand...
Click to collapse
Maybe, because I do it when my Nexus 5 is charging? -No...
Their devices must be powered off - Volume up + Power
Andriy2 said:
Maybe, because I do it when my Nexus 5 is charging? -No...
Their devices must be powered off - Volume up + Power
Click to expand...
Click to collapse
Yes , the device must be powered off. By the way it is enough just to hold down volume - key then connect usb cable to boot to the primary bl when the device is powered off. The same true for the backup bl too.
If the bl got damaged the phone goes to Qualcomm Download mode. In this mode the screen is turned off so it is hard to tell is your phone turned on or off. You have to press the power key for a certain amount of time to turn off your phone. If you dont press it for enough time the device will not turn off or it is just restarts to qualcomm dl mode. If you press it too long the phone turns on again and goes to qualcomm mode. Maybe this caused problem to other people to gain access to the backup bl. Or maybe you cant access to backup bl if any of these partitions are damaged: sbl1, rpm, tz, sdi even if they have backup partitions just like aboot.
Anyway I cant be 100% sure until I brick my device or I get a bricked nexus from someone else.
Note: To force your device to qualcomm dl mode you have to turn on your device and press all the keys down, you will see the screen is off, but when you connect the phone to the pc you will see a new device.
Tapatalk-kal küldve az én Nexus 5-el
There is abootb on all nexus devices, but we haven't found a way to load this on not LG device yet.
asschool said:
There is abootb on all nexus devices, but we haven't found a way to load this on not LG device yet.
Click to expand...
Click to collapse
they work in different ways, on the n4 the abootb is lgnpst mode, not an adb mode
Just came here to say that I got here when I used the hellscore management app to kill my nexus 5, heh. I happened upon the backup bootloader by accident... And got a stock image loaded. This thread would have saved me the better part of a day has I found it.
Sent from my Nexus 5 using Tapatalk
LeoRex said:
Just came here to say that I got here when I used the hellscore management app to kill my nexus 5, heh. I happened upon the backup bootloader by accident... And got a stock image loaded. This thread would have saved me the better part of a day has I found it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yea, i remembered it, thankfully i found it quick(but not quick enough.
simms22 said:
yea, i remembered it, thankfully i found it quick(but not quick enough.
Click to expand...
Click to collapse
I found this AFTER I wiped everything... had I known both this and that all that was wrong was a messed up boot loader, I could have preserved some stuff on my internal storage.
lesson learned.
Sent from my Nexus 5 using Tapatalk
I used this Hellscore Kernel Manager app to download a version of HellScore Kernel and Flash. The app gave me an option to download the Kernel <hammerhead..xxxxxxx>, I selected it and flashed away. After a reboot, my phone was hard bricked. I am quite sure the version of the kernel, or the bootloader it packages along, are NOT tested/verified for Nexus 5. There was no way to unbrick the phone after you do this. Please note, if you are downloading the HellScore kernel from his d-h.st/users/hellsgod respository, this kind of messup never happens. This app is the culprit for auto downloading a non-tested kernel that overwrites the /boot partition with a wrong one - thus hard bricking the Nexus 5.
Had I seen this post / idea before - i could have saved on the replacement Logic board that the LG service center suggested.
Thank you!
Just helped someone else I didn't know all of that previously!
Thanks.
I can't get into second bootloader...
Maybe I don't press the keys correctly..
LeoRex said:
I found this AFTER I wiped everything... had I known both this and that all that was wrong was a messed up boot loader, I could have preserved some stuff on my internal storage.
lesson learned.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yea, unfortunately sh*t happens. but now we know, in case its needed again. its too bad that this post wasnt anywhere that would have been easy to find.
simms22 said:
yea, unfortunately sh*t happens. but now we know, in case its needed again. its too bad that this post wasnt anywhere that would have been easy to find.
Click to expand...
Click to collapse
well.... it's just a matter of finding the right search terms I guess. the problem here is that there's no error and the first time you hit it, you have no idea what the hell is wrong.
I mean, for the first 15 minutes or so, I thought the phone was completely toast. then I lucked into the secondary and realized that if I can get into that, at least I'll be able to flash stock. I can certainly see people just giving up and getting it replaced.
as an aside... If THIS didn't hard brick the phone, man, you must really have to put in effort to completely do this phone in.
LeoRex said:
well.... it's just a matter of finding the right search terms I guess. the problem here is that there's no error and the first time you hit it, you have no idea what the hell is wrong.
I mean, for the first 15 minutes or so, I thought the phone was completely toast. then I lucked into the secondary and realized that if I can get into that, at least I'll be able to flash stock. I can certainly see people just giving up and getting it replaced.
as an aside... If THIS didn't hard brick the phone, man, you must really have to put in effort to completely do this phone in.
Click to expand...
Click to collapse
yea, generally it really is hard to brick a nexus. but there are ways if you really want to
Very useful tut for me
hey guys i had that problem 3 weeks ago!
flashing wrong kernel to my device!! and it's gone!
then after many research i convinced i have to send it to service center of LG.
they resurrect it.
thanks god.
i think they using JTAG process
aryalireza said:
hey guys i had that problem 3 weeks ago!
flashing wrong kernel to my device!! and it's gone!
then after many research i convinced i have to send it to service center of LG.
they resurrect it.
thanks god.
i think they using JTAG process
Click to expand...
Click to collapse
just out of curiosity how much did it cost you?
aryalireza said:
hey guys i had that problem 3 weeks ago!
flashing wrong kernel to my device!! and it's gone!
then after many research i convinced i have to send it to service center of LG.
they resurrect it.
thanks god.
i think they using JTAG process
Click to expand...
Click to collapse
Can you confirm that they havent replaced you motherboard?
Related
I JUST got my nexus 7, i installed LCD Dencity Modder, i cant boot and im totally new to android. I had just rooted it. HELP!!!
Take a deep breath. Breath IN and out
use the nexus root kit in the dev forum to push the original firmware back to your device.. The awesome Developer has included all instructions on his thread.. Then learn a bit more about ANDROID. PLEASE ..
GOOD LUCK.. if this were not a nexus device you could have just thrown 250.oo away .. :highfive::good:
also there is a reset somehow. could be hold both vol up vol down and then push and hold power.. might take you into nv flash or stock recovery . not read much on this device as far as that. But will when its in my hand.
erica_renee said:
use the nexus root kit in the dev forum to push the original firmware back to your device.. The awesome Developer has included all instructions on his thread.. Then learn a bit more about ANDROID. PLEASE ..
GOOD LUCK.. if this were not a nexus device you could have just thrown 250.oo away .. :highfive::good:
also there is a reset somehow. could be hold both vol up vol down and then push and hold power.. might take you into nv flash or stock recovery . not read much on this device as far as that. But will when its in my hand.
Click to expand...
Click to collapse
Thank You!!! im not normally this ignorant, but my total andriod usage probably ads up to <30mins.
I do know android, and I somehow got stuck at the Google screen. Tried to boot into recovery from ROM manager and now I just freeze at the Google screen. Cant get into recovery, only fast boot. Not at my computer right now but can I flash recovery from the fastboot menu? I tried resetting by using all three buttons but it just sticks at the Google screen
Sent from my Full AOSP on Toro-VZW using xda app-developers app
im not sure holding those buttons in that config is correct was just a guess.You should yes be able to push new recovery with fast boot. as this is how its useally done.. AS I Posted in the above i looked at the root tool kit . it looks as thou it has a auto push to restore the device . I ASSUMED it was nv flash or fast boot. Since i do not have the device i cant say for sure.
there is also some kind of small hole on the left side . This could also be a reset. again TRY AT YOUR OWN Risk. im only guessing on experience with other android devices .
I should stop replying to i need help threads until i know more of this device as its only guessing .
Good luck . let us know what you learn from getting you back to normal boot. will help avoid this stuff in future.
erica_renee said:
im not sure holding those buttons in that config is correct was just a guess.You should yes be able to push new recovery with fast boot. as this is how its useally done.. AS I Posted in the above i looked at the root tool kit . it looks as thou it has a auto push to restore the device . I ASSUMED it was nv flash or fast boot. Since i do not have the device i cant say for sure.
there is also some kind of small hole on the left side . This could also be a reset. again TRY AT YOUR OWN Risk. im only guessing on experience with other android devices .
I should stop replying to i need help threads until i know more of this device as its only guessing .
Good luck . let us know what you learn from getting you back to normal boot. will help avoid this stuff in future.
Click to expand...
Click to collapse
I have been able to use that combo for a hard reset on the device last night, but it doesn't seem to help with the loop I'm stuck in. I know that there is cwm recovery on here since I did a nandroid after I rooted. I did see the hole on the side but I had assumed it was a mic hole. Kinda afraid to stick anything in there I just got back to my parents from my sisters graduation party so I may try to give reflashing recovery a shot before I leave here. I'll post results when I hopefully have progress
Sent from my Full AOSP on Toro-VZW using xda app-developers app
mrich137 said:
I have been able to use that combo for a hard reset on the device last night, but it doesn't seem to help with the loop I'm stuck in. I know that there is cwm recovery on here since I did a nandroid after I rooted. I did see the hole on the side but I had assumed it was a mic hole. Kinda afraid to stick anything in there I just got back to my parents from my sisters graduation party so I may try to give reflashing recovery a shot before I leave here. I'll post results when I hopefully have progress
Sent from my Full AOSP on Toro-VZW using xda app-developers app
Click to expand...
Click to collapse
OOOPS On the hole thing. your prob right .
As far as the combo doing hard reset. if its not fixing the boot looP its a soft reset . hard reset would restore your device settings .
erica_renee said:
OOOPS On the hole thing. your prob right .
As far as the combo doing hard reset. if its not fixing the boot looP its a soft reset . hard reset would restore your device settings .
Click to expand...
Click to collapse
There are actually two holes on the device; one on the top near the left corner, and another on the left side above the 4 pin dock connectors. Pretty sure these are dual mics for noise canceling, for the Google Now. I may be wrong, but still don't recommend sticking a paperclip in there.
Ok. On the WugFresh Nexus Root Toolkit that I used last night to unlock and root there is an option to unroot and relock bootloader. This is normally done over adb, which I did not have access to, but if you select the "My device won't boot" option, it will do it over fast boot. Now that my device actually booted up correctly, I am unlocking and re-rooting. All is good, despite now having to set everything up all over again.
On a side note, I highly recommend WugFresh's Root Toolkit. I used it for my Galaxy Nexus before when it was just a command line script that would do all of the work for you, now it is built with a complete GUI that makes things even easier.
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie
berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...
I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.
I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.
My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.
Well, I was browsing around the market and my n5 just abruptly shut itself off. It hasn't been able to turn back on since. I've tried every key/charge/magic trick in the book so its DEAD!
Happy to jump in the RMA line at this point but was wondering if any others can confirm DEAD devices. The RMA thread is kinda full of nitpick issues but a dead device is a dead device.
This was the only discussion chain I could find on the issue but maybe someone from google will comment on dead devices. lol
https://productforums.google.com/forum/#!msg/nexus/lI6A3fA8bvw/d3eQlqEqabEJ
EDIT:
so it appears holding down both volume buttons + power while it's plugged in to the charger (not USB to PC) will temporarily boot the phone. You can then do a restore to stock and issue gets fixed. :good:
Damn. That blows.
Sent from the jaws of my Hammerhead!
mrro82 said:
Damn. That blows.
Click to expand...
Click to collapse
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Since I was able to get it booted tethered to the power I'm going to have it drain the battery to dead and see if it resets itself or something. Maybe a bad idea but I guess I don't care at this point it's already RMAd and I don't know what else to try. lol
Zenoran said:
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Click to expand...
Click to collapse
Do you have a backup you can attempt to restore?
Have you tried to adb into it?
Delete damn it
I would never install twrp.
There is a stock rom in here somewhere. Flash it boot loader and see what happens.
Synyster06Gates said:
Do you have a backup you can attempt to restore?
Click to expand...
Click to collapse
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.
Zenoran said:
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.
Click to expand...
Click to collapse
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701
caribouxda said:
I would never install twrp.
Click to expand...
Click to collapse
Why wouldn't you? In situations like this, it is extremely helpful. Do you expect him to install CWM or something? From my understanding, at least when I first got my phone and flash a custom recovery, CWM wasn't booting. If you are here to try and press your opinion on which custom recovery you prefer, go to their official thread.
Sent from my Nexus 5 using XDA Premium 4 mobile app
floxrin said:
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.
Zenoran said:
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.
Click to expand...
Click to collapse
That's good to hear man. I couldn't imagine how I'd feel if that happened to me. Thankfully XDA us the place that it is and the members, for the most part, have the ability to help us troubleshoot most of our issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I went to install the most recent up date. When it got done installing it started to reboot. It then got stuck on the HTC start up screen. I do not know a whole bunch on phones but did a little research and tried to recover and reboot the phone and neither worked. I would really like to find a fix that does not involve erasing all my data. I have all the pictures of my baby from the past year, from the time that he was born until now, and I would really hate to lose those. Thank you!
foreveryours117 said:
I went to install the most recent up date. When it got done installing it started to reboot. It then got stuck on the HTC start up screen. I do not know a whole bunch on phones but did a little research and tried to recover and reboot the phone and neither worked. I would really like to find a fix that does not involve erasing all my data. I have all the pictures of my baby from the past year, from the time that he was born until now, and I would really hate to lose those. Thank you!
Click to expand...
Click to collapse
Maybe some more information... what ROM, was this a stock OTA? If you have custom recovery and are attempting to flash a custom ROM, then try to reflash...if you have lost your data already or to avoid data loss;try side-loading a ROM...can't tell you much from what I've read, but if you can hold power+ volume down simultaneously for about 15 secs you should end up in recovery, if you installed a custom recovery; e.g.Philz, TWRP, CWM...then you'll pop up there....
It is safe to say that if you don't have any of these custom recoveries then you'll need to use the RUU found in the Dev section....
foreveryours117 said:
I went to install the most recent up date. When it got done installing it started to reboot. It then got stuck on the HTC start up screen. I do not know a whole bunch on phones but did a little research and tried to recover and reboot the phone and neither worked. I would really like to find a fix that does not involve erasing all my data. I have all the pictures of my baby from the past year, from the time that he was born until now, and I would really hate to lose those. Thank you!
Click to expand...
Click to collapse
... by the look of you message, it feels you havent unlocked your bootloader and here i will be happy to be wrong. if you have already then you got a bright chance of flashing a custom recovery via fastboot and retrieving your data mounting the storage from recovery ...
Devilish_Angel said:
... by the look of you message, it feels you havent unlocked your bootloader and here i will be happy to be wrong. if you have already then you got a bright chance of flashing a custom recovery via fastboot and retrieving your data mounting the storage from recovery ...
Click to expand...
Click to collapse
No I have not done this. I am assuming there is no way to do that at this point?
hooover said:
Maybe some more information... what ROM, was this a stock OTA? If you have custom recovery and are attempting to flash a custom ROM, then try to reflash...if you have lost your data already or to avoid data loss;try side-loading a ROM...can't tell you much from what I've read, but if you can hold power+ volume down simultaneously for about 15 secs you should end up in recovery, if you installed a custom recovery; e.g.Philz, TWRP, CWM...then you'll pop up there....
It is safe to say that if you don't have any of these custom recoveries then you'll need to use the RUU found in the Dev section....
Click to expand...
Click to collapse
I am sorry, I am completely stupid when it comes to phone. I know that I have not done any customizations. It is not rooted and would not have a custom ROM, not quite sure what that is. Everything should be stock. So what would I have to do to do the option that you have stated? I apologize for my lack of knowledge.
does your pc recognize the the phone when you plug it in? you could try extracting the data like stated before, but you're not rooted so that'd be a problem. an ruu would be your best bet, even though you'll lose your data. I HIGHLY suggest creating a dropbox and backing up your photos, it has done wonders for me.
playonword said:
does your pc recognize the the phone when you plug it in? you could try extracting the data like stated before, but you're not rooted so that'd be a problem. an ruu would be your best bet, even though you'll lose your data. I HIGHLY suggest creating a dropbox and backing up your photos, it has done wonders for me.
Click to expand...
Click to collapse
It recognizes it to an extent. My computer will ding recognizing that it is plugged in but since it does not go past the start up screen you can't get into the phone storage. I do have a dropbox but with the thousands of pictures on my phone it unfortunately only stored a month or so of pictures. I am not so much worried about the phone, as I have insurance on it and can get it replaced. Just really want the pictures. When looking online I had read something about unlocking the boot menu and downloading a ROM I believe. Do you know anything about that and if it would work for me? Or is that the same thing as the RUU?
foreveryours117 said:
No I have not done this. I am assuming there is no way to do that at this point?
Click to expand...
Click to collapse
... you can but then you are gonna lose everything after unlocking so there is no point ...
Mine gets stuck on boot screen occasionally. Sounds weird but hold the phone drectly up to a light bulb and try to reboot the phone. This works for my particular problem. Not sure why but it does.
foreveryours117 said:
It recognizes it to an extent. My computer will ding recognizing that it is plugged in but since it does not go past the start up screen you can't get into the phone storage. I do have a dropbox but with the thousands of pictures on my phone it unfortunately only stored a month or so of pictures. I am not so much worried about the phone, as I have insurance on it and can get it replaced. Just really want the pictures. When looking online I had read something about unlocking the boot menu and downloading a ROM I believe. Do you know anything about that and if it would work for me? Or is that the same thing as the RUU?
Click to expand...
Click to collapse
Hold power and vol-down together until it reboots into bootloader. Connect to USB and select 'fastboot' on the bootloader menu. That should get you to fastboot. From there, you can HTCDEV unlock the thing (in all likelihood).
Hello guys! So I bought a 64gb version of Nexus 6 just before new years eve and it started having issues in february. It got fully replaced by the service company for a new one. Yesterday my phone started complaining that I have insufficient storage. I checked how much memory I had and it said "32gb". So I'm using now a 32gb instead of a 64gb version which I was supposed to get from warranty. Nobody told me about the switch and the store where I bought it from said there has happened a mistake.
The thing that makes this tricky is that I've dropped the phone and the top layer of the screen is cracked. The screen itself works 100%, no color issues or issue tracking finger. It's just the top layer of protective glass that's bricked http://i.imgur.com/g6Se9dd.jpg They should contact on moday to me about this but what are really my options? If there never would had been a failure from their side, I would be living hapily with a 64gb bricked screen nexus 6 and have no issues. Do you think there are going to be more expenses for me due to their mistake?
Checked all papers over the issue. In the document over the repair, it states that they give me a new 64gb model of the phone.
One thing I started wondering about this morning. As me and my friend rooted my N6, we installed his stock image on it due to mine bugging out. He has a 32gb of N6. Could this affect it also? Both android system and disc checker app says I have left 23.03gb, aka. 32gb model.
FiresStream said:
Hello guys! So I bought a 64gb version of Nexus 6 just before new years eve and it started having issues in february. It got fully replaced by the service company for a new one. Yesterday my phone started complaining that I have insufficient storage. I checked how much memory I had and it said "32gb". So I'm using now a 32gb instead of a 64gb version which I was supposed to get from warranty. Nobody told me about the switch and the store where I bought it from said there has happened a mistake.
The thing that makes this tricky is that I've dropped the phone and the top layer of the screen is cracked. The screen itself works 100%, no color issues or issue tracking finger. It's just the top layer of protective glass that's bricked http://i.imgur.com/g6Se9dd.jpg They should contact on moday to me about this but what are really my options? If there never would had been a failure from their side, I would be living hapily with a 64gb bricked screen nexus 6 and have no issues. Do you think there are going to be more expenses for me due to their mistake?
Checked all papers over the issue. In the document over the repair, it states that they give me a new 64gb model of the phone.
One thing I started wondering about this morning. As me and my friend rooted my N6, we installed his stock image on it due to mine bugging out. He has a 32gb of N6. Could this affect it also? Both android system and disc checker app says I have left 23.03gb, aka. 32gb model.
Click to expand...
Click to collapse
Fastboot flashing the factory image will do this. To get your full 64gb of memory back, from bootloader do >
fastboot format userdata
NOTE: this will wipe the contents of your SDcard, so back it up on your PC first.
Yeah to echo the above, its quite common on the nexus to accidentally appear you have the smaller version after a flash...reflashing stock should fix it.
Doesn't it say which version you have in the bootloader?
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
FiresStream said:
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
Click to expand...
Click to collapse
No, there's no such thing as a wrong stock image. They're not storage-exclusive. Just a bad flash, it happens sometimes.
FiresStream said:
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
Click to expand...
Click to collapse
No, you didn't. This happens with the 64gb versions. Factory reset after flashing factory image usually prevents it.
So I guess, nandroid backup and then reinstall. The backup should get everything back so I don't need to spend 4 hours to set up my phone accounts/settings etc?
FiresStream said:
So I guess, nandroid backup and then reinstall. The backup should get everything back so I don't need to spend 4 hours to set up my phone accounts/settings etc?
Click to expand...
Click to collapse
Not sure. Try it and see. Be sure to save it to your PC, as "fastboot format userdata" will wipe your SDcard.
****...
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
FiresStream said:
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
Click to expand...
Click to collapse
the toolkit is where you made the mistake. you have to flash the factory image via fastboot while you are hooked up to a computer while you're in the bootloader. if you have no idea what you are doing, toolkits wont help you out. read how to do it right, thete are a few threads here explaining for you, in detail.
---------- Post added at 05:09 PM ---------- Previous post was at 05:02 PM ----------
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
FiresStream said:
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
Click to expand...
Click to collapse
What happens when you try to reboot to Android? Your bootloader is locked so there isn't much you can do if you can't boot Android.
Do you have stock recovery or TWRP?
Tried quite a few options already in the Nexus Root Toolkit but without any results...
Anything specific I should give a try to hopefully let me sleep this night in peace?
Bootloop, just nothing... It just displays "Google" logo and does nothing further.
FiresStream said:
Bootloop, just nothing... It just displays "Google" logo and does nothing further.
Click to expand...
Click to collapse
try this via fastboot, and see if itll boot up. you have to be in the bootloader to use fastboot..
fastboot format cache
fastboot format userdata
then try booting up and enabling oem unlock.
simms22 said:
try this via fastboot, and see if itll boot up. you have to be in the bootloader to use fastboot..
fastboot format cache
fastboot format userdata
then try booting up and enabling oem unlock.
Click to expand...
Click to collapse
Got android studio installed from some time ago, just need to find out how to push the commands from cmd...
FiresStream said:
Got android studio installed from some time ago, just need to find out how to push the commands from cmd...
Click to expand...
Click to collapse
and hows android studio gonna help? you arent building an app.. you need to use fastboot.
simms22 said:
and hows android studio gonna help? you arent building an app.. you need to use fastboot.
Click to expand...
Click to collapse
Gotta say I'm hopeless in my situation... Got fastboot and abd drivers installed now, now I just need to find out how to use them...
FiresStream said:
Gotta say I'm hopeless in my situation... Got fastboot and abd drivers installed now, now I just need to find out how to use them...
Click to expand...
Click to collapse
thats ok, i was useless with fastboot at one time as well. at the very beginning, is when its the hardest, just because you are clueless. once you do it one time, its much easier every time after.
simms22 said:
thats ok, i was useless with fastboot at one time as well. at the very beginning, is when its the hardest, just because you are clueless. once you fo it one time, its much easier every time after.
Click to expand...
Click to collapse
Got the commands done which you suggested, how should I proceed?
FiresStream said:
Got the commands done which you suggested, how should I proceed?
Click to expand...
Click to collapse
try booting up. if you boot up, enable developer options, then go into them and enable oem unlocking. then you can unlock the bootloader and flash a factory image.
btw, i found this thread about using fastboot. its an older thread but.. http://forum.xda-developers.com/showthread.php?t=2277112