Related
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
ThuanBui said:
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
Click to expand...
Click to collapse
I'm having the same problem!
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
andr0idfreak said:
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
Click to expand...
Click to collapse
I've done this many times but still no luck
ThuanBui said:
I've done this many times but still no luck
Click to expand...
Click to collapse
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
monkeying. around said:
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Click to expand...
Click to collapse
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
sideloading 4.4.2 and stuck on boot loop
ThuanBui said:
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
Click to expand...
Click to collapse
bro mime nexus 4 has stuck into boot loop after upgrading from 4.4 to 4.4.2 .i was sideloading the zip dont know whats the issue ......i was rooted but went to stock via nexus roottool kit to get OTA . any suggestion
joshnichols189 said:
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
Click to expand...
Click to collapse
all you got to do is download the toolkit and flash the software your phone is using and put it in fastboot and begin
:good::good::good::good::good::good::good:
Hi!
I managed to get my device totally bricked.
Phone is on bootloop and I only get LG logo and then "Security Error" message. I can't enter recovery mode or download mode. Only mode I'm able to go is the "Hardware key control mode" mode, where I can see my IMEI code. I can't get windows or linux to recognize my phone. I've tried several drivers, but no luck getting my laptop recognize my phone. I have also tried couple of tutorials to solve this problem, but the main problem seems to be that I can't get my laptop to recognize my phone.
Is there anything I could do or should I just buy a new phone?
Hi Jutei,
What led to this bricking? Were you trying to install a ROM? Which ROM was it? Was it a wrong variant? Please be specific as to what you did to brick it..
Also, some people have seen success by installing this driver. Are you familiar with ADB?
y
Hi deathbytalkshow!
I ended up to this stage by rooting with this (http://forum.xda-developers.com/showthread.php?t=2448887) and trying to flash with this (http://forum.xda-developers.com/lg-g2/development-d802/rom-xenonhd-d802-t3036576).
First I wiped data and cache. Then rooted and it went trough with no problems. I tried to flash with this https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager. It booted to recovery and started flashing. Soon it said that flashing failed and after reboot I found myself in this bootloop.
Hope this helps someone to help me.
Try this:
1. Turn phone off.
2. Press POWER+VOL DOWN
3. When LG Logo appears, immediately release POWER+VOL and press and hold VOL UP+VOL DOWN
4r44444 said:
Try this:
1. Turn phone off.
2. Press POWER+VOL DOWN
3. When LG Logo appears, immediately release POWER+VOL and press and hold VOL UP+VOL DOWN
Click to expand...
Click to collapse
Hi, I tried this and got to the factory reset window. It started to do reset, but pretty soon it booted and went back to bootloop. So this didn't help. I'll try those ADB drivers today.
Hi, tried adb drivers, but no luck. My laptop still doesn't recognize my phone. USB gives power, but beside that windows doesn't seems to notice that my device is plugged. Is there anything else I could try?
so you didnt make a backup before flashing? what recovery did you flash? i bricked my phone with rom manager before and will never use it again but i had a backup and was still able to get it to eventually boot into twrp to restore.
Sent from my LG-VS980 using XDA Free mobile app
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
also if you never turned on usb debugging i dont think you can get a computer to see it unless its fully booted.
Sent from my LG-VS980 using XDA Free mobile app
jfletch86 said:
so you didnt make a backup before flashing? what recovery did you flash? i bricked my phone with rom manager before and will never use it again but i had a backup and was still able to get it to eventually boot into twrp to restore.
Click to expand...
Click to collapse
Yeah, I was stupid enough not to backup. The recovery was the stock one. Is that where I went wrong? Should I've had custom recovery installed?
jfletch86 said:
also if you never turned on usb debugging i dont think you can get a computer to see it unless its fully booted.
Click to expand...
Click to collapse
I turned usb-debugging was on before phone got bricked. I think the phone should be found somehow on computer. For example this fix (http://forum.xda-developers.com/showthread.php?p=48765620#post48765620) needs Linux to recognize the phone, but I can't even do that. I guess the problem here is that my phone won't enter the download mode. I'm going to try with couple of different computers when I get back home from my holidays.
I also found another fix to try. I have to drain the battery and after a little re-charge I should be able to enter the download mode. I'm trying this next.
yes thats where you made your mistake. that also makes me think download mode wont work period, but im not positive. im surprised rom manager even tried to flash anything without a recovery. thats why i dont use apps like that anymore because you wouldnt of been able to **** it up that bad on your own. so you said you tried the key combo to take you to the factory restore? if you didnt flash a recovery then i would think you could get that to work. did you look into lg's flash tool? maybe that will somehow read it. i remember seeing a post in the general forum about a way to take the phone apart and short the chip out but ive never had to actually read it so i couldnt tell you whats all involved. sorry bout your phone.
Sent from my LG-VS980 using XDA Free mobile app
---------- Post added at 11:53 AM ---------- Previous post was at 11:49 AM ----------
i forgot to read your link, just now did, why do you say you cant do that?
Sent from my LG-VS980 using XDA Free mobile app
Well, I just got myself in the same boat.
The phone will show the LG Logo then the security error and shut down. When plugged in with a USB to the PC it will just reboot.
Nothing is showing in Device Manager either. I done the same in the stock recovery and I tried to Side load CM12 it failed and straight into this loop.
I got nothing now. I just done see how shorting circuits will fix the issue when it's just software. Absolute nightmare as the 12 months warranty has gone.
I tried to do a hard reset and I get the android man saying its working then it shuts down and starts the error again. I'm unable to get in the Download Mode either and I'm stuck
I don't know what to do now. The flash and Support tool will not recognize the phone.
jfletch86, I tried LG Flash Tool, but the problem is that it just says no devices found. Same problem with fix I linked, I can't do anything to my phone if my laptop doesn't find it. I'm beginnig to loose hope
DvineDNO said:
Well, I just got myself in the same boat.
The phone will show the LG Logo then the security error and shut down. When plugged in with a USB to the PC it will just reboot.
Nothing is showing in Device Manager either. I done the same in the stock recovery and I tried to Side load CM12 it failed and straight into this loop.
I got nothing now. I just done see how shorting circuits will fix the issue when it's just software. Absolute nightmare as the 12 months warranty has gone.
I tried to do a hard reset and I get the android man saying its working then it shuts down and starts the error again. I'm unable to get in the Download Mode either and I'm stuck
I don't know what to do now. The flash and Support tool will not recognize the phone.
Click to expand...
Click to collapse
Oh man, I'm sorry to hear that you are in the same boat. Symptoms are the same. It seems that we have bricked our phones pretty badly. Hopefully someone comes up with fix that works. Problem is that anyone wise enough to fix this isn't stupid enough to end up this stage.
I'm hoping the same too. I just don't know why it wont allow me to do anything.
I have a nexus 4 and I've never had a problem.
I am getting nothing when plugged into my PC and its like the phone is turning on and off in the boot loop and the lg symbol.
I get the hard reset menu but the computer still doesn't recognise.
I just feel sick at the moment !!
jutei said:
jfletch86, I tried LG Flash Tool, but the problem is that it just says no devices found. Same problem with fix I linked, I can't do anything to my phone if my laptop doesn't find it. I'm beginnig to loose hope
Click to expand...
Click to collapse
are u saying you tried the ubuntu/linux fix? if that doesnt work then nothing will.
Sent from my LG-VS980 using XDA Free mobile app
Well, I just got myself in the same boat.
The phone will show the LG Logo then the security error and shut down. When plugged in with a USB to the PC it will just reboot.
Nothing is showing in Device Manager either. I done the same in the stock recovery and I tried to Side load CM12 it failed and straight into this loop.
I got nothing now. I just done see how shorting circuits will fix the issue when it's just software. Absolute nightmare as the 12 months warranty has gone.
I tried to do a hard reset and I get the android man saying its working then it shuts down and starts the error again. I'm unable to get in the Download Mode either and I'm stuck
I don't know what to do now. The flash and Support tool will not recognize the phone.
Click to expand...
Click to collapse
what were you doing, what steps did you do up until this?
got similar problem, g2 stuck on boot loop (going from custom rom back to stock) can enter download mode, cant enter recovery. help needed
ok, after 2 days of ****ing with boot loop... its gone, if u r on d802 eu open and got some questions... mabye i can help
my lg g2 is also stuck in bootloop and flashing rom wont fix it. the only improvement it have shown is android doodle and back to logo screen. please help me out.
taimurarbab said:
my lg g2 is also stuck in bootloop and flashing rom wont fix it. the only improvement it have shown is android doodle and back to logo screen. please help me out.
Click to expand...
Click to collapse
are you using the right bootloader for the rom you are flashing?
Sent from my LG-VS980 using XDA Free mobile app
jfletch86 said:
are you using the right bootloader for the rom you are flashing?
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
i have no idea. please guide me through it.
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.
I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app
Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.
Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.
Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.
Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.
The current state of my tablet is quite curious: Its stuck on Google logo and it will be this way until the battery completely drains.
What I've tried:
- Holding the Power button shuts it down for 1 second...then it boots right back up by itself.
- Recovery (POWER+VOL DOWN) doesnt work, it goes straight to Google screen.
- Connecting via USB to the computer, Windows doesnt recognize the device.
In fact, the only way I found to Turn the Tablet off is popping the back cover and unplugging the battery cable. I've left it unplugged at night, hoping it would clear some sort of Cache, didnt work. Also I've tried unplugging the battery cable, plugging it back and Turning it on with POWER+VOL DOWN in hopes of acessing recovery but it goes straight to Google screen.
Additional Info:
- This happened while I was trying to downgrade from 5.1 to 4.4.4.
- My device is the LTE version of N7 2012
- My device is currently rooted.
@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.
AndDiSa said:
@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough.
Click to expand...
Click to collapse
1 second is the ammount of time the tablet remains off, not the ammount of time i've pressed it. Yes, I've held it 20 seconds obviously.
AndDiSa said:
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.
Click to expand...
Click to collapse
Followed this guide right here: https://drive.google.com/file/d/0Bz6x7k-VkpUJU09paVM5cmh2Xzg/view
All the steps worked until the fastboot flash boot .\boot.img command. Sometimes it would get stuck on the command prompt and the tablet was frozen in Recovery Mode. I had to close the command Prompt, reboot the tablet into recovery again and Flashing another thing first, like recovery and system and THEN i would flash the boot.img.
So theres no hope?
First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs
AndDiSa said:
First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
The one indicated on the guide, named razorg-mob30x-factory-10b7ca08.zip, the link is in the guide link also.
I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs
AndDiSa said:
I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Oh Crap, really? Is there a fix?
Yup, same deal here, not done by me. Now I am stuck in APX mode and I need to somehow flash bootloader back into the tablet. Please, don't tell me there isn't any way to do this...
RavenEffect said:
Oh Crap, really? Is there a fix?
Click to expand...
Click to collapse
Have you tried flashing the images google gives on their website? (they also give a helpful guide)
Charles IV said:
Have you tried flashing the images google gives on their website? (they also give a helpful guide)
Click to expand...
Click to collapse
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
I know for mediatek, there is smartphoneflashtool, which flashes to the device when it's turned off. I don't know if there is an equivalent that you can use.
I don't think NRT does it, so you might be screwed.
There is nvflash ... but only if you have backed up *your* individual device images before you need them. So if your device is already bricked there is no chance ...
Sent from my Nexus 7 using XDA Labs
krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
Problem is that, when you plug the Tablet to the PC via USB, it doesnt recognize the device, like I've stated on the original post, so I cant even get to a step where I can flash any sort of file.
Well, if I think about it, only the bootloader got destroyed. The image is free on google sites. I just have to put the bootloader image into the tablet so I can get to the bootloader and flash everything else with fastboot. There has to be way to do that. I mean if the "BIOS" (screen with google logo) got destroyed, that is bad, but it is just matter of damage on free to share universal loader. There has to be way...
My Galaxy S8 stopped working altogether. It won't turn on or charge. The only thing I can do is open up download mode but only if the phone is plugged in. Trying to boot into safe mode just ends up in a loop where the phone tries to restart. The phone is only discovered on my laptop while in download mode and even then, it shows up as a "modem" with the name MSM8998, which is the chip. I figure if I can get it into recovery mode (which I'm attempting through adb and by hitting the buttons), I may be able to wipe the cache partition and boot normally. If anyone knows how to do this or just any idea on how to recover the media files on the internal storage, it'd be much appreciated
spikedan82 said:
My Galaxy S8 stopped working altogether. It won't turn on or charge. The only thing I can do is open up download mode but only if the phone is plugged in. Trying to boot into safe mode just ends up in a loop where the phone tries to restart. The phone is only discovered on my laptop while in download mode and even then, it shows up as a "modem" with the name MSM8998, which is the chip. I figure if I can get it into recovery mode (which I'm attempting through adb and by hitting the buttons), I may be able to wipe the cache partition and boot normally. If anyone knows how to do this or just any idea on how to recover the media files on the internal storage, it'd be much appreciated
Click to expand...
Click to collapse
My note 5 did this. Ended up being a bad battery
TheMadScientist said:
My note 5 did this. Ended up being a bad battery
Click to expand...
Click to collapse
Yeah that's probably a good guess...going to a repair shop tomorrow so hopefully that's the case. Didn't know if the whole system was just shot.
spikedan82 said:
Yeah that's probably a good guess...going to a repair shop tomorrow so hopefully that's the case. Didn't know if the whole system was just shot.
Click to expand...
Click to collapse
Mine wouldnt boot anything. Other than download mode while plugged in. It was bootlooping and everything just out of nowhere. Its better to make sure that first. If you have a power failure during flash it could cause more damage and corruption
TheMadScientist said:
Mine wouldnt boot anything. Other than download mode while plugged in. It was bootlooping and everything just out of nowhere. Its better to make sure that first. If you have a power failure during flash it could cause more damage and corruption
Click to expand...
Click to collapse
I don't think the battery is the culprit. I installed a new battery and the same issue persisted. I'm trying to figure out how to try to flash the stock rom now but no luck so far.