This video is me talking about what I've done so far to try and bring my N7 back from the dead.
http: //www . youtube . com / watch?v=0IviRtW4_QM
Basically, it won't turn on. I tried to flash the Beats audio driver since I'd heard that it improves the audio a little bit. I flash it, clear cache just in case, reboot system, it says that "Android is upgrading" and that it's "Updating app x of y". The "Updating app x of y" text goes away and simply says that Android is upgrading. It wouldn't go away or continue to boot fully into Android, so I held the power button and rebooted my N7. Now it won't boot into anything. It won't boot into Android. It won't boot into recovery. The bootloader freezes when plugged into a power source. It freezes when booted into the bootloader under battery and then plugged into a power source.
I don't know what to do to make my N7 live again. Any help would be appreciated.
Maby try to format the data partion.
If that not works format system and reflash the ROM your using.
If you has no rom flashed flash stock back.
Instrucions on this site.
https://developers.google.com/android/nexus/images
Or simply take a CM10.1 nightly.
http://get.cm/?device=grouper
and flash gapps
http://goo.im/gapps/gapps-gb-tegra-20110118-signed.zip
Related
A message popped up from Samsung to install an update (I had been pressing cancel for the past week on this update). It says click OK to reboot and apply update (something along those lines) so I do. Now I am stuck with a tablet that won't boot. If I hold the power button it says "Samsung Galaxy 10.1" after about 12 seconds, but then it goes away and back to darkness. Nothing else. Holding power and volume up does nothing.
Someone know what is going on and have any idea how to resolve?
The best way is to restore any backup you have from cwm recovery. Else grab a stock firmware and flash it with ODIN or if zip than CWM recovery. For luck, try clearing cache and data in recovery, first!Perhaps it may work saving you all fuss of flashing a firmware.
I cannot even boot that far too get into recovery. And I just noticed that although I can't boot, the backlight is on (on a solid black screen).... wtf
You can't hold volume down and power button to enter recovery?
Nope. I plugged into my computer and for some reason with the USB connectd it let me enter recovery. Flashed a backup and rebooted, but now I have no wifi... im confused.
it occured once to me when i tried to overclock, it never worked except when installing a new rom... Try to root the device and then install a new rom
OK, was a helluva night messing with ROM and kernel installs... I have yet to go back to completely stock (that's next up tonight, unfortunately), but I installed Starburst ROM and the Wifi still didn't work so I then installed pershoot's kernel and now when I boot the screen is extremely distorted kind of like this: http://t1.gstatic.com/images?q=tbn:ANd9GcTsKa5IoQxnesGdUjykWDDggoQZ38yZ2VXSgPAQ09NOCnETzl9-
As a side note, when I say the wifi is not working, it still shows all networks and allows me to connect just like normal. However when connected no apps can access the network...
Can someone point me to a thread on how to revert EVERYTHING back to stock so I can start fresh? TIA!!
http://forum.xda-developers.com/showthread.php?t=1171089
Should have all the files you need. From where you are now I would flash the stock OTA 3.1 or TW then flash the stock recovery and do a factory reset from that recovery. That should get rid of the garbled screen.
Thanks buddy. On my way to grab the files now
I heard the update was pulled as it sometimes rewrites the bootloader improperly. You might need to send it in, unfortunately.
Hi there,
I was able to boot the Q fine. I enabled USB debugging, used ADB to reboot into bootloader ran the oem unlock/unlock_accept command successfully. I rebooted and flashed CWM recovery v 6.0.2.7 steelhead. Once this was done, I rebooted into recovery and used adb to push the latest stable release of CM 10.1 to the sdcard. I then flashed this via CWM recovery, and performed a factory reset.
Now that I have rebooted system, it just sits on the cyanogenmod loading splash screen. I left it for over 2 hours at first, then I power cycled device and left it over night. I attempted to go back into recovery, but covering the LED on the top does not seem to result it anything. I power cycled the Q again, and held my hand over the LED from boot to attempt to get into recovery but I am not able to. I also powered device up and waited until the ring LED began to light up, then covered the top LED to see if this allowed to boot into recovery but still no change.
I let the Q boot up once more, and after sitting on the splash screen loading for about 10 minutes, I connected the device back to my PC, and found that adb can see the device. However now that it is running CM 10.1, adb security is enabled and my PC is unauthorized. I am unsure how to proceed at this point. Do I need to try a different PC than the one that was originally used to flash to see if it works (I doubt it will as that wont be authorized either, right?) or am I doing something wrong while trying to get into recovery?
If anyone can shed some light, or assist even getting into recovery, or providing a way to get around the adb authority requirement it would be greatly appreciated.
Ok scratch the above.. I managed to tap on the top LED about 50 times during boot, at which point it turned to red solid LED ring and loaded enough for me to get in using fastboot. I flashed the recovery again, ran a factory reset/wipe cache on it twice, and rebooted. it is now sitting at the home screen ready for me to purchase an OTG USB cable tomorrow and set up cyanogen mod!
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
I recently bought a Google Nexus Player, first impression: I love it! :laugh:
The Nexus Player has Android 6 (Marshmallow) installed on it.
Since I'm new to the whole Modding, Rom(ing), Rooting, Flash(ing), I would like to ask for some help from the more experienced guys
I did invest some time into the matter though, and with some help from vids & literature over the internet I came a long way..
BUT..
I'm not quite there yet!
Here is the situation: I tried to install CM12.1 Recovery, that did not end as expected! Could not get it started although I've followed all the correct steps to get it installed it crashed every time I chose for a startup in Recovery Mode. So, I looked for an alternative, and came across TWRP Custom Recovery. Fortunately, this one did install correctly.
So, after installing TWRP Recovery successfully I downloaded Official CM-12.1 for Nexus Player (fugu) BUILD from dhacker29's Official Topic. With it, I downloaded the GApps for Android 5.1 x86 Full Android Experience Package: gapps-lp-x86-20150527-signed.zip from the same CM-12.1 Topic.
Both files are then copied to a USB Stick. After I connect my USB Stick with an OTG Cable to my Nexus Player, I then start up Bootloader, choose Recovery Mode by navigating with the Button under the Nexus Player & start up the TWRP Recovery.
Once I'm in TWRP Recovery Mode, the first time i did a WIPE -> ADVANCED WIPE and removed the CASH & DALVIK CACHE by confirming "Swipe to Wipe".
After cleaning up stuff, i go back to the Home menu. Here I clicked INSTALL, navigated to my USB Stick, containing the files:
- cm-12.1-20151205-NIGHTLY-fugu
- gapps-lp-x86-20150527-signed
First I've installed the Cm12.1 Nightly Build zip file, immediatly after that I've installed the gapps zip file. Both successfully.
Now that is done, I've rebooted my Nexus Player from within TWRP.
Upon startup, the Cyanogenmode Logo popped up. So far so good..
Then the screen switches. It says: (*)
Adroid Startup
Installing X app from 105 apps..
I see all 105 apps being successfully installed, but then:
Adroid Startup
Finishing Booting..
Once the "Finishing Booting" message pops up, my Nexus Player will not go pass by this procedure!
I see the blue stripes turning clockwise, but it never ends.
I wait and wait, but nothing. It never finishes Booting, therefor it will NOT finish the install procedure.
So my Nexus Player has become pretty un-usable now.
When I do a restart by holding the button below my Nexus Player while I plug in the power cable, I get into boot loader, then I choose Normal Boot. From here the whole (*) process starts again, ending up with the "Finishing Boot" screen, and again I get stuck on this point of the procedure..
Now i have no idea how to install the Original Firmware (Android 6 Marshmallow) back again that came on my Nexus Player.
Nor have I any idea on how to make this CM-12.1 work!
Is it possible to do a new clean install of the original Nexus Player Android Marshmallow 6 Firmware OR a new clean install of the CM-12.1 GApps via TWRP? Resulting to work..
Any help would be appreciated..
Love from Holland, the Netherlands
Cheers!
Adilost said:
I recently bought a Google Nexus Player, first impression: I love it! :laugh:
The Nexus Player has Android 6 (Marshmallow) installed on it.
Since I'm new to the whole Modding, Rom(ing), Rooting, Flash(ing), I would like to ask for some help from the more experienced guys
I did invest some time into the matter though, and with some help from vids & literature over the internet I came a long way..
BUT..
I'm not quite there yet!
Here is the situation: I tried to install CM12.1 Recovery, that did not end as expected! Could not get it started although I've followed all the correct steps to get it installed it crashed every time I chose for a startup in Recovery Mode. So, I looked for an alternative, and came across TWRP Custom Recovery. Fortunately, this one did install correctly.
So, after installing TWRP Recovery successfully I downloaded Official CM-12.1 for Nexus Player (fugu) BUILD from dhacker29's Official Topic. With it, I downloaded the GApps for Android 5.1 x86 Full Android Experience Package: gapps-lp-x86-20150527-signed.zip from the same CM-12.1 Topic.
Both files are then copied to a USB Stick. After I connect my USB Stick with an OTG Cable to my Nexus Player, I then start up Bootloader, choose Recovery Mode by navigating with the Button under the Nexus Player & start up the TWRP Recovery.
Once I'm in TWRP Recovery Mode, the first time i did a WIPE -> ADVANCED WIPE and removed the CASH & DALVIK CACHE by confirming "Swipe to Wipe".
After cleaning up stuff, i go back to the Home menu. Here I clicked INSTALL, navigated to my USB Stick, containing the files:
- cm-12.1-20151205-NIGHTLY-fugu
- gapps-lp-x86-20150527-signed
First I've installed the Cm12.1 Nightly Build zip file, immediatly after that I've installed the gapps zip file. Both successfully.
Now that is done, I've rebooted my Nexus Player from within TWRP.
Upon startup, the Cyanogenmode Logo popped up. So far so good..
Then the screen switches. It says: (*)
Adroid Startup
Installing X app from 105 apps..
I see all 105 apps being successfully installed, but then:
Adroid Startup
Finishing Booting..
Once the "Finishing Booting" message pops up, my Nexus Player will not go pass by this procedure!
I see the blue stripes turning clockwise, but it never ends.
I wait and wait, but nothing. It never finishes Booting, therefor it will NOT finish the install procedure.
So my Nexus Player has become pretty un-usable now.
When I do a restart by holding the button below my Nexus Player while I plug in the power cable, I get into boot loader, then I choose Normal Boot. From here the whole (*) process starts again, ending up with the "Finishing Boot" screen, and again I get stuck on this point of the procedure..
Now i have no idea how to install the Original Firmware (Android 6 Marshmallow) back again that came on my Nexus Player.
Nor have I any idea on how to make this CM-12.1 work!
Is it possible to do a new clean install of the original Nexus Player Android Marshmallow 6 Firmware OR a new clean install of the CM-12.1 GApps via TWRP? Resulting to work..
Any help would be appreciated..
Love from Holland, the Netherlands
Cheers!
Click to expand...
Click to collapse
Mine does this every once in awhile. I found that unplugging and plugging it back in will fix it
Phone crapped out low batt. Plugged in rebooted, got to SIM card unlock screen, held power to force reboot (this the way to recalibrate battery on stock ROM, reset, charge to 100%.) Now, no matter I am stuck in a boot loop. 10 Mins nothing happening... Can still access recovery but unless default directory holds latest Lineage OS ZIP? (Is it still there?) Then may have to pull merged SD, format then manually download LOS on laptop & reflash.
Dayum!
fleamour said:
Phone crapped out low batt. Plugged in rebooted, got to SIM card unlock screen, held power to force reboot (this the way to recalibrate battery on stock ROM, reset, charge to 100%.) Now, no matter I am stuck in a boot loop. 10 Mins nothing happening... Can still access recovery but unless default directory holds latest Lineage OS ZIP? (Is it still there?) Then may have to pull merged SD, format then manually download LOS on laptop & reflash.
Dayum!
Click to expand...
Click to collapse
Confusing lines! Please, write clearly and provide useful information about your phone, it will help XDA members to help you..
Things i got,
You had stock ROM before bootloop happened and now you want to flash lineageOS, right ?
Things missing between,
Does your phone have unlocked bootloader ?
Does it has TWRP recovery installed ?
If not unlocked, then which version of stock ROM you had ?
Sorry, so many words, so little info!
I am happily running latest LOS nightly & latest TWRP on a Moto G4 Plus Athene build.
I once read that to recalibrate battery you needed to hold power button till phone turns off, continue to hold till on again. You would then charge to 100%. Charging to 80% mostly gives false threshold, hence turning off when rang.
I successfully booted phone to SIM unlock screen then held power till off then on, problem being it now sits at boot screen for all eternity! Rebooting from recovey same story. Turning off then on same story. Is there anything else to try before attempting reflash?
fleamour said:
Sorry, so many words, so little info!
I am happily running latest LOS nightly & latest TWRP on a Moto G4 Plus Athene build.
I once read that to recalibrate battery you needed to hold power button till phone turns off, continue to hold till on again. You would then charge to 100%. Charging to 80% mostly gives false threshold, hence turning off when rang.
I successfully booted phone to SIM unlock screen then held power till off then on, problem being it now sits at boot screen for all eternity! Rebooting from recovey same story. Turning off then on same story. Is there anything else to try before attempting reflash?
Click to expand...
Click to collapse
Try to clear delvik-cache and cache from
TWRP> wipe > advance wipe (don't wipe "data"). then reboot. (As delvik-cache is deleted, it will take time to rebuild delvik files)
If it take more time than 10 minutes, you will have to reflash.
In case, if any app store your data and you don't want to lost it (say massages/chat history/etc), then you can first give a try by dirty flashing.
For dirty flashing,
Download lineageOS.zip and gapps.
Move it to phone or directly flash from external sdcard, just wipe cache and delvik-cache, don't wipe "data" it will erase everything (apps and app-data)
If still doesn't boot after 10 minutes, then you will have to clean flash the ROM.
So is this due to instability?
Thanks!
Clean flashed but bootloop continues, do I need to flash stock then try again?
Edit: We in, hand up skirt!