Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
bricklayer16 said:
Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
Click to expand...
Click to collapse
To self-reply, for some reason, adb reboot bootloader wouldn't work, but adb reboot recovery got me into fastboot. I've managed to get things repaired.
Related
Good Morning All -
A few days ago, I dualbooted my N7 with Ubuntu. The installation went fine and the tablet was working with no issues over the last several days. Last night, I was using the tablet and set it down. I went to pick it up (roughly 5 minutes later) and the touch screen was unresponsive. I was at the lock screen but couldn't get it to unlock. I pushed the wrong key-combo first and the device took a screen shot.
I was able to reboot into fastboot and attempted to go to recovery. The device would just hang at the Google logo. I pushed a factory firmware update from my Ubuntu system and attempted to reset -- no joy. This morning, I used Nexus Root Toolkit from my Windows 8 machine to see if I could get it up. Root Tool kit worked fine, pushed the images over again and restarted but it continues to hang at the Google logo.
Looking for any other advice folks may have on getting the device to boot.
EDIT: I can get to the bootloader fine and the computer recognizes it.
Thanks!
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
xbi0s said:
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
Click to expand...
Click to collapse
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
antonio824 said:
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
Click to expand...
Click to collapse
I'm unable to get into the restore menu. Hangs at the Google logo when attempting to get there.
I've tried about any solution I could find... Bumping one last time before I torch the unit :\
Nothing can be done. Its something inside. If its the 2013 model, call and get it rma'd. Sorry man.
Sent from my LG-LS970 using XDA Premium HD app
Resurrecting this thread to keep a work log.
I made have made some progress but hitting another roadblock. I've been holed up at home due to an auto accident so I started tinkering with the N7 2013 again.
Using the Nexus Root Toolkit, I am able to launch "Boot Temporary - Custom Recovery" from the advanced options. The problem I now run into is TWRP's touchscreen will not work. I attempted to do volume up/down to see if I could select but it wouldn't. The software is not frozen as I can see the temperature changing.
Anyone have any thoughts or information on how to boot another custom recovery that uses button inputs? I appreciate any input.
Updates:
1. I was able to push TWRP via "fastboot flash recovery." It went to the Google Logo then loaded TeamWin screen. I started to see errors when the program launched. "Unable to mount..." multiple times then the device rebooted. Device stuck on the Google screen.
2. Shut the device down, booted back into Fastboot. Selected Recovery and it began loading again. This time, the app launched and worked. Touchscreen does not work but the CPU temp is fluctuating and minutes tick up.
Update 4:49PM Central:
1. I am able to install and boot into TWRP 2.8.0.1 through TWRP 2.7.1.1. Those versions load but of course touch screen does not work.
2. I have been unable to get CWM to load... It installs fine but I cannot boot into.
3. The factory recovery images also do not load.
So today for the first time tried to mess around with my phone, but i failed miserably. I rooted my phone with Kingo ROOT, and then followed the instructions on the wiki page, but at step 4 things got messed up, my phone got stuck at the SONY logo with the blue light turned on and it wouldnt do anything, so i removed the battery, now it boots up at the cyanogen recovery but i cant do anything from there , everytime i close the device when i boot it , it boots to this menu. I have tried everything to get it back to normal but nothing seems to work. I will tell exactly what i did in order to reach in this state. I downloade the nicki nightly cm, and moved the boot.img to my platform-tools folder in which i run on command prompt the following commands :
fastboot flash boot boot.img
fastboot reboot
After that my phone gets stuck and i can only access Cyanogen Recovery, does anyone have any idea what to do?? :crying: :crying:
Have you tried flashing the rom using cyanogen recovery?
Hi all,
I've been running PA 4.6 (KK 4.4.4) smoothly for a few weeks now, then suddenly a few days ago it started to reboot to the OPPO logo and is now stuck in a bootloop showing only OPPO logo. Only way to stop it is to power down. Sometimes it won't even power up, then after I leave it for a few hours, it'll power up, but again OPPO logo bootloop. I'm able to boot into fastboot (that's finicky, too - it happens if I'm lucky). When I do "adb devices", nothing shows up, but when I do "fastboot devices", I can see my device.
I tried to flash a recovery through fastboot, and it says flashed successfully, but when I try to reboot, it still does the OPPO logo bootloop. Can you please help me figure this out?
At one point, while I was pressing this button and that in the middle of doing fastboot stuff, somehow it booted up to my homescreen successfully, but after like 30 seconds, it rebooted, and it's been on OPPO logo bootloop ever since. Please help.:crying:
raddatt said:
Hi all,
I've been running PA 4.6 (KK 4.4.4) smoothly for a few weeks now, then suddenly a few days ago it started to reboot to the OPPO logo and is now stuck in a bootloop showing only OPPO logo. Only way to stop it is to power down. Sometimes it won't even power up, then after I leave it for a few hours, it'll power up, but again OPPO logo bootloop. I'm able to boot into fastboot (that's finicky, too - it happens if I'm lucky). When I do "adb devices", nothing shows up, but when I do "fastboot devices", I can see my device.
I tried to flash a recovery through fastboot, and it says flashed successfully, but when I try to reboot, it still does the OPPO logo bootloop. Can you please help me figure this out?
At one point, while I was pressing this button and that in the middle of doing fastboot stuff, somehow it booted up to my homescreen successfully, but after like 30 seconds, it rebooted, and it's been on OPPO logo bootloop ever since. Please help.:crying:
Click to expand...
Click to collapse
Are you unable to boot into recovery too? Try booting into recovery and factory resetting the phone.
Thank you for replying. Yes, unable to boot into recovery I can only boot into fastboot. From there, when I do the reboot to recovery command, it says successful in cmd, but the phone goes back into the OPPO logo bootloop.
Bump.. anyone, please?
Sounds like you're gonna have to download the N1 ADB drivers and fix your phone that way. There should be a tutorial for that on XDA here somewhere
IAmOmicron said:
Sounds like you're gonna have to download the N1 ADB drivers and fix your phone that way. There should be a tutorial for that on XDA here somewhere
Click to expand...
Click to collapse
I know this is super late, but thank you for your reply. I did that and was able to flash the stock recovery via fastboot (cmd said Writing, then successful at 0.182 seconds), but when I reboot (doesn't reboot via buttons, had to do "fastboot reboot") the same problem returns - boot loop at Oppo logo. Any ideas please? Thanks again.
Hello there
After my phone randomly rebooted while watching a video it ran into a bootloop.
I had been running LineageOS for the past couple of months and everything was fine up until yesterday.
I have tried restarting, and everything and only managed to reflash twrp via adb and force it to boot into twrp, but now it's stuck booting into that.
when I try to boot into lineage I only see the boot animation of lineage that never stops, and when I boot into twrp I see the boot screen of that, which never stops.
I've let the phone do its thing for so long that it has run out of power, so it's not something that just takes a long time. I feel like this thing is completely bricked now.
Anyone maybe got a solution? Any help would be appreciated.
Hi,
Think I might have the same issue, except I didn't flash or modify anything on the phone. I'm running all stock ROM and all the rest.
Stuck in a bootloop in recovery mode. Mini partition does not recognise the phone. Same with QPST. QComDloader does, but only for a few seconds, so whatever I try it's not fast enough before the next reboot...
Whats are the options? I don't want to have to send it back to China
Hey guys, been a hot minute since I've been around these parts but I've got a weird one for you.
I'm stuck in a boot loop. I can get into the bootloader using pwr+vol up, but thats it. If I try to enter recovery it boot loops.
Using fastboot commands and I can get things to flash (so it says), but am still stuck in this bootloop.
Tried loading TWRP using fastboot boot twrp.img and it says it succeeded but then loops without ever getting the TWRP splash
Tried extracting the img files from the most recent OTA downloaded from google from the payload.bin and flashing those with no success.
Tried flashing the boot.img out of LineageOS and it still loops afterwards... I'll admit that this was a last ditch effort and I hope I didn't screw myself, but I figure I can just reflash if needed since I can still access fastboot.
I feel like since I can get into the bootloader that there's got to be SOMETHING I can do, but nothing seems to be working. Is this old phone truly bricked? Any ideas??
A little extra info. I was on a stock rom, it was rooted for a while and eventually after some of the ota's I lost it and didn't bother getting it back. the bootloader unlocked, though, so there's that.
ridethisbike said:
Hey guys, been a hot minute since I've been around these parts but I've got a weird one for you.
I'm stuck in a boot loop. I can get into the bootloader using pwr+vol up, but thats it. If I try to enter recovery it boot loops.
Using fastboot commands and I can get things to flash (so it says), but am still stuck in this bootloop.
Tried loading TWRP using fastboot boot twrp.img and it says it succeeded but then loops without ever getting the TWRP splash
Tried extracting the img files from the most recent OTA downloaded from google from the payload.bin and flashing those with no success.
Tried flashing the boot.img out of LineageOS and it still loops afterwards... I'll admit that this was a last ditch effort and I hope I didn't screw myself, but I figure I can just reflash if needed since I can still access fastboot.
I feel like since I can get into the bootloader that there's got to be SOMETHING I can do, but nothing seems to be working. Is this old phone truly bricked? Any ideas??
Click to expand...
Click to collapse
As a rule of thumb
-- A 'bricked phone' is usually unresponsive, won't power on, and doesn't function normally.