Hello, guys. I have the newer line of the 16GB nexus 7's(C90K, iirc), which I just got the other day. Bootloader is unlocked, TWRP is recovery, device is rooted. I checked the md5 of the Bugless Beast flash and all matched up. Yet, every time I flashed it resulted in a bootloop that wouldn't fix itself. I thought maybe I was doing something wrong so I looked at how others were doing it: everything was just right. I factory reset and wiped system for good measure, wiped caches, and installed the ROM.
To make sure that I really wasn't doing anything wrong, I took Paranoid Android and flashed it. It was running in like two minutes. I tried the latest and the second latest of BB releases, so I don't think it's his release but something on my device? I'd appreciate some assistance, guys.
I don't mean to double post, but any ideas?
How long did you let it try booting? I noticed my newer nexus 7 takes longer to flash and first boots seem to be a lot longer as well.
Sent from my SGH-T999 using xda app-developers app
Warrior1975 said:
How long did you let it try booting? I noticed my newer nexus 7 takes longer to flash and first boots seem to be a lot longer as well.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It was a bootloop rather than actually getting anywhere/loading anything. I let it bootloop for 30 minutes a couple times just to see, though.
Related
I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?
Go back to recovery, factory reset, wipe caches and reflash
Sent from my Nexus 7 using xda app-developers app
Try long pressing the power button to turn it off and try booting again. Sometimes it hangs on boot after flashing. Especially with certain kernels.
Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.
SpazticWonder said:
I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?
Click to expand...
Click to collapse
chivo559 said:
Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.
Click to expand...
Click to collapse
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Apocalypse487 said:
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!
chivo559 said:
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!
Click to expand...
Click to collapse
So you fixed it? I updated the bootloader before updating PA to any newer versions. I haven't had bootloops. I followed the DROIDMODDERX video on YouTube when I was on 4.1.1. In the tool kit thread it tells you how to update.
Sent from my SAMSUNG-SGH-I747 using xda premium
Reboot error related to paths?
I flashed my N7 a few weeks back (using goomanager) with 4.2 JB which worked fine. I then put on gapps and got an endless loop of error messages about trying to configure them. At this point I rebooted to recovery and put back on rooted stock 4.1.1.
I thought I would try PA again this week and the ROM flashes OK, but when I reboot the N7 "hangs" at the boot screen and goes no further. The same thing happens if I try SmoothROM. I can go back to rooted stock OK though.
I notice the paths have been updated as per 4.2 but otherwise things appear the same as before.
Any idea why PA now won't boot?
Thanks
mik
A few days back, my wife got me a shiny new nexus 10. This thing is cool for sure. However the one I'm using now isn't the one from a few days back. It is in fact, a replacement because after I hooked into my WiFi and loaded up the apps I have on my GNex off of Google backup, I got a notification for an android update. So I said "SHURE... I need that stuff" so I pushed the item in the notification and it said "push OK to restart...", so I did.... And it did restart to a DEAD ANDY ICON AND A "NO COMMAND" under him! I did a factory reset three times and never got further than the boot animation. The dude at google play support was a bit flummoxed but beyond a reset... Well... He pronounced it mostly dead. So rather than screw up the warranty, I took it back to where we bought it and got a new one.
So here I am again... I'm at JVP15P... And I've got a pending update downloaded and ready to fry my second N10! I've heard 4.2 has some kind of update issue just like this on the N10.... Is that true? What should I do? If this is true how do I get past this... I sure as s**t don't want to return anther one! Any suggestions are most appreciated.
Sent from my Nexus 10 using xda app-developers app
A short time ago, I was unable to update to 4.2.1 from 4.2, either from the automatic update, or from adb sideload. This was because I was using some older factory image (not sure what was wrong with it), but after downloading the latest factory image from Google and flashing it, I was then able to update without any issue
I finally did my updates.
Thankfully all went smooth. Although, my N10 ran as cool as ice before the updates. I could play games for a long time and it would barely get warm. Now it seems to run extremely warm. I wouldn't say hot, but it is noticeably a lot warmer and that is doing nothing but surfing the web.
Not sure what was in that first update, but it changed the way it runs. No other issues though.
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
alias_neo said:
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
Click to expand...
Click to collapse
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It's a boot-loop, technically, but now I'm just being a pedant
I'm not too sure about the toolkits because I don't use them, but yes, you have to unlock to flash stock images.
Easiest way it do download the zip from the dev site, unlock manually, then just double click the flash-all script, that will take care of the rest, then just relock after and happy days.
I know it's a bit nerve racking when it won't boot, but that will get you out of most sticky situations, in the case of boot loops, a wipe/factory reset from recovery should normally solve the issue, if it doesn't just flash the images again as above.
Pesonally, if I'm messing i'll make sure my device is up to date and working, then fastboot boot TWRP (without unlocking or modifying my device) and backup to a USB drive, then, you can restore your system as is at any stage later if things mess up.
fastboot boot is fantastic because it lets you temp boot a custom recovery, and do all your usual stuff (including rooting etc) without replacing the stock recovery, and without unlocking, soon as you reboot, it's gone, cause it just boot the reovery into RAM.
Doctor Dedroid said:
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
If you are talking to me, mine is stock and used regular updates that were DL and ready.
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
alias_neo said:
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
Click to expand...
Click to collapse
Got it! To be sure when I tried to update I was around 60% on the battery level... Hopefully my issue was a fluke or due to a low battery.
Update: all updated and good to go. Thanks one and all!
Sent from my Nexus 10 using xda app-developers app
Okay, so I was listening to a YouTube video via Popup Browser BETA. When the song finished, I tried closing the window, but it wouldn't let me interact with the window. Not sure why. I just figured since the app was in beta it was just confused, so I went to the settings->running applications->I force closed the app. But for some reason, the little window still wouldn't go away. So I decided to reboot my device. Bad idea, apparently...
Now whenever I boot up my phone it'll vibrate, display the Google logo for a few seconds, and then... it goes to a blank black screen. Not a clue why. I've tried:
- Leaving it to charge and rebooting
- Leaving it in the blank black screen
- Booting into recovery, then trying to reboot the device from there
- Clearing cache partition
Nothing works. I still can't boot up my phone again.
I'm running Slimbean 4.2.1 (not the latest version). There really isn't anything that might have triggered this. I can still charge my phone (the charging animation still occurs) and I can still go into CWM Recovery. I'd really rather not have to install a new ROM or anything... but if I have to, is there a way to extract the data I have on my phone now while in recovery or something?
Any suggestions?
EDIT: This has been FIXED. Moderators, if you see this, you can close this thread. If anyone else has this problem, try reflashing your current version of your ROM, that's how I fixed mine. I'm not responsible for damage to your device.
Why haven't you tried reflashing your rom without wiping data?
Sent from my iPad 4
mitchdickson said:
Why haven't you tried reflashing your rom without wiping data?
Sent from my iPad 4
Click to expand...
Click to collapse
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Surpass said:
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Click to expand...
Click to collapse
It's not going to hurt anything. Make a CWM backup of your data if you want.
Sent from my iPad 4
Surpass said:
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Click to expand...
Click to collapse
No way of corrupting your data, as long as you don't select to wipe data partition or data is already corrupted. But this is strange that your phone gone crazy like this. Try to reflash your rom without wiping data and see if your phone will boot up
Sent from my Nexus 4 using xda app-developers app
mitchdickson said:
It's not going to hurt anything. Make a CWM backup of your data if you want.
Sent from my iPad 4
Click to expand...
Click to collapse
I've not got enough free space on my phone I don't think (it's only 16GB, I got about 2GB free).
Unless I'm mistaken the backup will take more than that, yes? Considering I've got a few games apps that probably equate to about 4GB.
gallardo5 said:
No way of corrupting your data, as long as you don't select to wipe data partition or data is already corrupted. But this is strange that your phone gone crazy like this. Try to reflash your rom without wiping data and see if your phone will boot up
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Should I reflash with a newer version of the ROM or should I reflash the old one that I'm running?
EDIT: Woops sorry about double post.
Surpass said:
Should I reflash with a newer version of the ROM or should I reflash the old one that I'm running?
EDIT: Woops sorry about double post.
Click to expand...
Click to collapse
Reflash the same version you were running before this accident, as the newest version requires clean flash. If you want to run the latest version and have your data back, reflash the same version you were running before, then backup your data, wipe phone, flash the latest version and restore your data
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Reflash the same version you were running before this accident, as the newest version requires clean flash. If you want to run the latest version and have your data back, reflash the same version you were running before, then backup your data, wipe phone, flash the latest version and restore your data
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Okay I'll give that a go, thanks for the help and I'll report back my results. :good:
EDIT: Tried downloading the Zip from their site and now it's saying I've got to log in, but no place to register... grr. I might be a bit longer..
Surpass said:
Okay I'll give that a go, thanks for the help and I'll report back my results. :good:
Click to expand...
Click to collapse
Good luck then and if you will have any problem, just write here and don't forget to quote my post so I will get an email notification
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Good luck then and if you will have any problem, just write here and don't forget to quote my post so I will get an email notification
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
WOO! Thanks a lot! Booted up perfectly, and no loss of data or anything like that. Only odd things is it seems to have changed my DPI... but I can change that easily so it's not really a bother. It also made me have to update the Virus Definitions on Avast!, not sure why either.
I shall now proceed to thank all of your posts.
Surpass said:
WOO! Thanks a lot! Booted up perfectly, and no loss of data or anything like that. Only odd things is it seems to have changed my DPI... but I can change that easily so it's not really a bother. It also made me have to update the Virus Definitions on Avast!, not sure why either.
I shall now proceed to thank all of your posts.
Click to expand...
Click to collapse
Great to hear it worked for you now comes the best part, flashing the latest rom
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Great to hear it worked for you now comes the best part, flashing the latest rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes either that or perhaps switch to a new one, I've been with semi-stock Android for quite a while now I'm really liking the port of MIUI V5...
Has anyone tried the 4.3 cm10.2 ROMs found over here (http://androidhosting.org/Devs/Dhacker29/cm-10.2/)? I was going to give it a go last night but for some reason my device got stuck on the "warning your boot loader is unlocked" screen and had to use Matt's utility to give it life... I may give it a try tonight when I'm not expecting any calls...
Sent from my XT907 using xda app-developers app
Yeah, I'm running the latest version of it now. I had the same problem. What worked for me was the following:
1. Wipe everything - system, data and both types of cache.
2. Install CM 10.2 and NOTHING else. Boot the ROM. It should go through now.
3. Once you get to the main screen, reboot into recovery.
4. Install the 4.3 GAPPS version. Reboot, get to the main screen and reboot into recovery.
5. Now flash the 4.3 version of Supersu for CM 10.2
6. Boot one last time into CM 10.2
All the links for everything you need can be found with a Google search. Later I may edit this post to include those links.
Sent from my XT907 using Tapatalk 4
Thank you kindly for the reply... I got it booting finally but couldn't get su permission on TiB and what not... I didn't know about needing the 4.3 su ...I'll flash that now... again thank you kindly
Sent from my XT907 using xda app-developers app
TWRP isn't supported either from what I understand. You need to run CWM.
Any time I install 4.3, it won't reboot. It starts up initially, but I can't get it to get past the Motorola logo upon second boot.
I have tried the normal install method and this method.
Then recovery doesn't see the /data folder so something is wrong with the 4.3 install I presume.
Does it change the location of data?
Yeah I Tried It But It Had No Sound So I Changed Over To 4.2.2 AOKP.
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I was using CWM on my first attempt... this time around I switched to TWRP...
Sent from my XT907 using xda app-developers app
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I use TWRP, works ok. Got sound, data, everything working fine. Battery life sucks, but no surprise there.
My 2c
I'm running it right now. I must have missed the part about flashing SuperSu, because I can't do anything as root. I had trouble the first time I flashed with the phone bootlooping, but I flashed again and that fixed it. Battery life is somewhat poor, but I just found the performance page today (Icon was different, silly me!) so we'll see how it goes with a different governor. I've been having issues with Navigation and Bluetooth audio on anything except stock. Bluetooth audio locks the phone and I have to soft-reset it. Navigation crashes if you try to multi-task while using it.
So, I rooted and saved a backup. I then installed Gummy ROM with ease. I then wanted to try TriForce. I did the factory reset etc. and then installed it. I noticed it said something failed (couldn't find a certain directory I think), although the top said it finished successfully. Now it won't get passed the "Samsung" logo in the beginning of boot.
I know that I added a code prior to Gummy ROM using the "debug" method of turning off the boot animations. Could that have transferred over to TriForce?
What do I do?
Perform a factory reset and see if that gets you bootef
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Perform a factory reset and see if that gets you bootef
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yep I tried to do it and it works. For some reason, my phone can't even be used in my backed-up state... After I enter my pin, my launcher crashes, my system crashes, gapps crashes... lol why is my backup working so poorly?
So I installed Gummy again. At least it's extremely smooth. Missing all my favorite TW featuers though...
Do you know what I might be doing wrong with TriForce? I re-read it's page, and it did mention a long first boot. So I'll try to keep it on for a longer time... going on 5 minutes of blank screen haha.
I'm not sure. I've never had that experience with triforce. Have you tried other tw Roms to see if it also happens. Also did you check to see if MD5 matched?
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
I'm not sure. I've never had that experience with triforce. Have you tried other tw Roms to see if it also happens. Also did you check to see if MD5 matched?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I haven't tried any other TW roms. Do you happen to know of any good ones that get extreme smoothness/performance/fast app opening/less bloat/and good battery life? I'd also like more customization and extra cool things haha.
I'm nearing 20 minutes. Apparently someone said you should flash a different kernel for people having boot problems? Now my screen is flickering randomly... sheesh. But yeah, do you happen to know of a good one?
EDIT: And I actually dont' know what MD5 is really! My phone just "restarted" and now is blank screen again after the samsung logo -___- Do you even know why my original backup isn't working properly with the freezes and everything crashing?