Related
My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.
thisisjjd said:
My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.
Click to expand...
Click to collapse
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?
Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.
charesa39 said:
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?
Click to expand...
Click to collapse
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.
thisisjjd said:
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.
Click to expand...
Click to collapse
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051. Pay particular attention to what you need to modify to make sure you don't wipe your userdata.
charesa39 said:
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051.
Click to expand...
Click to collapse
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?
thisisjjd said:
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?
Click to expand...
Click to collapse
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
charesa39 said:
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
Click to expand...
Click to collapse
I thought I had tried that, but thank you, I'll try again. I appreciate your advice.
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.
thisisjjd said:
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.
Click to expand...
Click to collapse
Hmm. Unfortunately, this is issue seems beyond my knowledge. That's odd that yesterday it was showing unlocked, and today it randomly is locked. If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
charesa39 said:
That's odd that yesterday it was showing unlocked, and today it randomly is locked.
Click to expand...
Click to collapse
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.
charsea39 said:
If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
Click to expand...
Click to collapse
I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.
hector333 said:
Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.
Click to expand...
Click to collapse
thisisjjd said:
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.
Click to expand...
Click to collapse
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary. If you are stuck in a boot loop long press the power button to force a reboot, as soon as the screen turns off press the volume down button that will get you to the bootloader. Or if the device is off press and hold both the power button and volume down button to get to the bootloader. Choose recovery with the volume button then press the power button. You should see android laying down with exclamation mark. Press and hold the power button and while holding the power button press and release the volume up button. Stock recovery! Use the volume button to select "wipe data/factory reset" then press power button. If that doesn't take care of it download the factory image and extract, if running 4.4.2 wifi version you should see ;
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
if you double click the "flash-all.bat" with the device already at the bootloader that will flash the complete image including userdata which wipes the device. You can also open flash-all.bat with notepad and remove -w from the script and it should not flash the userdata.img. Or... you could extract all of the images from the "image-razor-kot49h.zip" and flash them seperately with fastboot, whatever images you try to flash need to be in the same folder as fastboot.exe (platform-tools) so you do have multiple options as long as there is no hardware issue that is causing the reboot. Hope this helps!
wantabe said:
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary.
Click to expand...
Click to collapse
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
thisisjjd said:
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
Click to expand...
Click to collapse
Sorry to hear that! I don't remember ever hearing being able to get into the bootloader but not into recovery from there. Your probably right about having to do doing an RMA. If it's any consolation I had a good experience with ASUS when I had to RMA my 1st gen N7 32GB after the speakers went bad.
I'm glad to hear you had a good experience with ASUS support. I have an RMA and am sending it to them. Thanks for your help.
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
mnunez611 said:
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
Click to expand...
Click to collapse
I would say definitely RMA it. With you having a stock tablet it's not worth risking messing something up trying to fix your tablet and then maybe you can't RMA. I would start with Best Buy and them what their warranty period is. If it is within their stories warranty then take it to them. If not then call ASUS.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Help me
Hello Guys I am stuck in a very annoying situation at the moment which is that my nexus 7 has become inaccessiblhttp://forum.xda-developers.com/images/smilies/eek.gife. This is how it happened
one day I tried to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' errohttp://forum.xda-developers.com/images/smilies/crying.gifr. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
thanks in advance
I have the exact same issue as the OP. Can't get to recovery cause the Google logo hangs there. I can fastboot but the N7 is locked since it was not rooted. Using fast boot and Wugs I get the same thing where it just hangs on erasing userdata for hours. Wondering if any fix has been discovered for this since the OP issue was months ago.
Use fastboot OEM unlock command to unlock the boot loader then re flash stock.
Sent from my Nexus 7
I rooted my Verizon LG G4. Afterwards it wouldn't boot completely. It gave a Verizon message and wouldn't completely turn on. I tried to go back to the factory firmware and now I can't get it to boot up at all. No Verizon logo, nothing. Hard bricked? Is it completely shot or can it be fixed? I found a link to unbrick Qualcomm phones but it won't let me post the link here. It is very complicated!
Thanks!
kada598 said:
I rooted my Verizon LG G4. Afterwards it wouldn't boot completely. It gave a Verizon message and wouldn't completely turn on. I tried to go back to the factory firmware and now I can't get it to boot up at all. No Verizon logo, nothing. Hard bricked? Is it completely shot or can it be fixed? I found a link to unbrick Qualcomm phones but it won't let me post the link here. It is very complicated!
Thanks!
Click to expand...
Click to collapse
Can you get into download mode? If so, try to KDZ back to stock or push the backup image you should have made.
Sent from my Xposed VS98613B using XDA Free mobile app
KADA528 - Did you find a fix?
I have the same exact problem. Phone won't turn on after rooting. Cannot get to download screen either.
Hey guys i have the same problem phone wont turn on after root i did everything and it did nothing. I try to turn it on now and it does nothing not even download mode. I connect it to the computer and i hear Windows give me the sound when you plug in a phone.
Unable to revert to stock on vs986
I rooted my Verizon LG G4 using low effort root on version 11A. I am new to this rooting and didn't know how to disable system update. When I got the system update notification, instead of tapping install later, I tapped install now. Of course, the system update failed but since then I am not able to enter download mode to revert to stock. I tried to factory reset but it gives me secure boot error 1003 and just restarts the phone. Is there anything I can do to enter download mode? Thanks in advance.
sunny2015 said:
I rooted my Verizon LG G4 using low effort root on version 11A. I am new to this rooting and didn't know how to disable system update. When I got the system update notification, instead of tapping install later, I tapped install now. Of course, the system update failed but since then I am not able to enter download mode to revert to stock. I tried to factory reset but it gives me secure boot error 1003 and just restarts the phone. Is there anything I can do to enter download mode? Thanks in advance.
Click to expand...
Click to collapse
Turn off the phone, hold volume up, then plug in the USB.
I didn't root my wife's G4, but I have a feeling something is going on. At first, the phone would show the LG splash screen, then go black. Went in and did a factory reset, still the same thing. I took it into a VZW store on December 23rd and they tried doing the same things... as they were doing that another guy walked in with the same issue, same exact model. Anyone know if some sort of push was done recently?
After they processed the warranty repair, I brought it home and tried to re-flash the OG firmware. Now the phone will not power on at all, no bootloader, download mode, etc.
Silver lining is that my wife wanted a phone for the holiday, so I purchased a LG V10 with the intention of returning it within 14 days... she loves the phone, I get $100 back from LG, and I sold her replacement G4 for over $250, so I actually MADE money on the deal, LOL.
sushi-gee said:
Turn off the phone, hold volume up, then plug in the USB.
Click to expand...
Click to collapse
Thanks for your reply. I tried as you described several times but it just starts the phone without going to download mode. I am not able to do a factory reset either. I also tried to boot into recovery using quickboot app but the phone just restarts.
If the phone won't turn on, hold down down volume and power buttons at the same time. Assuming it turns on, turn it off and hold the same buttons again while it's off and then choose clear cache. Had both the unable to turn on and it stuck on the Verizon screen the past few days and this fixed it.
Almighty1 said:
If the phone won't turn on, hold down down volume and power buttons at the same time. Assuming it turns on, turn it off and hold the same buttons again while it's off and then choose clear cache. Had both the unable to turn on and it stuck on the Verizon screen the past few days and this fixed it.
Click to expand...
Click to collapse
Tried this method. Was able to get to recovery. After I tapped wipe cache, the phone restarted, gave the same "secure boot error! Error code 1003, Verizon logo appeared and phone restarted. I have root access. Is there a way to uproot without going into download mode?
---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------
Edit: I meant unroot.
sunny2015 said:
Tried this method. Was able to get to recovery. After I tapped wipe cache, the phone restarted, gave the same "secure boot error! Error code 1003, Verizon logo appeared and phone restarted. I have root access. Is there a way to uproot without going into download mode?
---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------
Edit: I meant unroot.
Click to expand...
Click to collapse
You may want to try KDZ/TOT... http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Just a warning, that's what I tried to do and then my wife's G4 no longer powered on. I was OK because I had a warranty replacement already in progress.
WorldOfJohnboy said:
You may want to try KDZ/TOT... http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Just a warning, that's what I tried to do and then my wife's G4 no longer powered on. I was OK because I had a warranty replacement already in progress.
Click to expand...
Click to collapse
Flashing KDZ/TOT needs to be in download mode. I am unable to enter the download mode or factory reset the phone. When I try to plug the usb cable with the volume up button pressed, it gives me a secure boot error 1003 and boots to system.
sunny2015 said:
Tried this method. Was able to get to recovery. After I tapped wipe cache, the phone restarted, gave the same "secure boot error! Error code 1003, Verizon logo appeared and phone restarted. I have root access. Is there a way to uproot without going into download mode?
---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------
Edit: I meant unroot.
Click to expand...
Click to collapse
Interesting because on the same day I responded, I uninstalled something and rebooted and the phone rebooted and I got to see both the LG logo and the Verizon Wireless boot screen but then when I wasn't looking, it turned black as if the phone was off. Nothing would turn it on until I did the force reboot and then clear cache and the phone was back to normal again.
sunny2015 said:
Flashing KDZ/TOT needs to be in download mode. I am unable to enter the download mode or factory reset the phone. When I try to plug the usb cable with the volume up button pressed, it gives me a secure boot error 1003 and boots to system.
Click to expand...
Click to collapse
So you can't get into Download mode, but can boot into the OS and the "recovery" menu (sorry, I'm coming from HTC phones, so I'm on a different set of terms/boot options)? I don't know of a method that will work to fix Download mode.
I was able to factory reset the phone. First, I unrooted using the su app. Then, I downloaded the Verizon Upgrade assistant that also had a repair assistant. After clicking repair, the repair assistant took about 15 to 20 minutes and said that the phone has been repaired. I went into recovery mode and wiped cache. After that, I used the recovery menu to factory reset the phone and this time, I was successful with the factory reset. Then, I took the system update to update the software to 13b. I don't plan on rooting the phone till a custom recovery such as TWRP becomes available for this phone.
xxjrsmith3xx said:
Hey guys i have the same problem phone wont turn on after root i did everything and it did nothing. I try to turn it on now and it does nothing not even download mode. I connect it to the computer and i hear Windows give me the sound when you plug in a phone.
Click to expand...
Click to collapse
Did you ever figure out how to get it back on?
EDIT: For the solution to this particular issue, head to this post.
Hi, yesterday I successfully did a clean install of OOS 4.0, including Magisk and systemless root. I had everything set up as I wanted it.
Today, I tried the 4.0.1 OTA, after using a Canadian VPN server. It downloaded fine (the full zip), and I launched the OTA.
Phone reboots... into nothing. Now the phone won't boot into recovery mode, or start the system. I thought it was odd, so I flashed stock recovery again (which is what was installed). Still can't boot. Then tried just booting into recovery over fastboot mode. Still no luck.
Then I managed to boot into a modded TWRP. That's something... But tried flashing the OTA from its temp location in TWRP. A couple of "command log" errors, but appeared to patch nonetheless.
Reboot to system though: black screen of nothing, again.
Anyone know what might be the issue, and why it happened after just launching an OTA through the stock dialogue?
Cheers :/
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
abobobilly said:
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
Click to expand...
Click to collapse
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
ememeh said:
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
Click to expand...
Click to collapse
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
abobobilly said:
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
Click to expand...
Click to collapse
I can get to a point of backing up if I want to. Though at the moment, I don't know what I'd backup (maybe just the system partition? I dunno).
I have the same thing: Can get the white 1+ logo, both capacitative button backlights show, the android text logo, but then black screen. Very frustrating. Let me know if you have any luck! I'll update here too.
wierd
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
canceric said:
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
Click to expand...
Click to collapse
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
abobobilly said:
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
Click to expand...
Click to collapse
good thing it worked for you, it bugs me that i cant root the phone since the device doesnt get recognised in fastboot ,reinstalled all the drivers and all, nothing works
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
ememeh said:
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
Click to expand...
Click to collapse
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Shayded said:
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Click to expand...
Click to collapse
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
ememeh said:
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
Click to expand...
Click to collapse
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Shayded said:
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Click to expand...
Click to collapse
Weird. Could be a different problem...
Did you get the install success message?
ememeh said:
Weird. Could be a different problem...
Did you get the install success message?
Click to expand...
Click to collapse
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Shayded said:
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Click to expand...
Click to collapse
Can you still boot back into fastboot and/or recovery?
ememeh said:
Can you still boot back into fastboot and/or recovery?
Click to expand...
Click to collapse
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Shayded said:
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
Click to expand...
Click to collapse
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Shayded said:
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Click to expand...
Click to collapse
Just seen the edit. Okay, makes sense. Good luck :good:
ememeh said:
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Click to expand...
Click to collapse
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Shayded said:
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Click to expand...
Click to collapse
Luckily for you, it doesn't sound like a true hard brick. Sometimes power buttons are just funny like this. In my experience at least (I've come back from near death experiences in a similar way to you before).
In any event, well done! Always such a relief to get things working again.
I'm using pure nexus rom for a while now and didn't give any kind of problem. Was casually using whatsapp on phone and battery was around 50%, phone suddenly started to vibrate. It vibrated for around 10 secs and it finally got shutdown. Now, It doesn't power on. I can enter into bootloader by holding vol down + power button for several seconds (than what it usually takes), but after entering bootloader, it doesn't go into recovery or start the phone. restart bootloader function is restarting bootloader normally but boot into recovery and power on doesn't work. Google logo appears for few seconds and again powers down. Please help! Thanks in advance!!
@cbhhargava, try to connect via fastboot
rp158 said:
@cbhhargava, try to connect via fastboot
Click to expand...
Click to collapse
Fastboot and flash it? It's encrypted. I don't wanna loose my data. But will consider if nothing else works.
i have same shi* trying to flash recovery via fastboot and see if it loads....
@cbhhargava: if fastboot connects, you can erase both of the caches and fladh PureNexus.zip. Without erasing /data. Fastboot-syntax.
didn't work... tryinf to flash stock image via fastboot...
didn't helped either... used Nexus Root Toolkit to flash stock image - still no change. blackscreen after Google boot screen, i'm starting to think it's hard bricked either soft bricked....
then there's the oven-procedure (it's described here often): if it boots after heating, you can save your data and let replace mainboard.
Same issue
cbhhargava said:
I'm using pure nexus rom for a while now and didn't give any kind of problem. Was casually using whatsapp on phone and battery was around 50%, phone suddenly started to vibrate. It vibrated for around 10 secs and it finally got shutdown. Now, It doesn't power on. I can enter into bootloader by holding vol down + power button for several seconds (than what it usually takes), but after entering bootloader, it doesn't go into recovery or start the phone. restart bootloader function is restarting bootloader normally but boot into recovery and power on doesn't work. Google logo appears for few seconds and again powers down. Please help! Thanks in advance!!
Click to expand...
Click to collapse
Downloading stock image hope it works ???
---------- Post added at 06:36 AM ---------- Previous post was at 06:01 AM ----------
same problem exists even after flashing stock image... it boots till the google image and than restarts nothing else..
rp158 said:
@cbhhargava: if fastboot connects, you can erase both of the caches and fladh PureNexus.zip. Without erasing /data. Fastboot-syntax.
Click to expand...
Click to collapse
No change Shuts down after google logo... Checked the oven method but not sure how much it helps.
Found this post. Seems like it's a dead end to me. Phone is out of warranty and what ever ROM I flash by fastboot doesn't boot
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
Click to expand...
Click to collapse
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
ZVNexus said:
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
Yeah might just have to wait until it dies.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
This has never failed!!! .. Unless its hardware
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
Turnoff.. hold the power button and both v+ and v-
For about 10secs.. hope it works for you
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
Click to expand...
Click to collapse
Sorry for replying old post. I have been facing this critical scenario for last two days. The phone never turned off, always looped through unlock warning. No, button working. Can you please share , what about your findings at the end ??