I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
hecksagon said:
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
Click to expand...
Click to collapse
Interesting I wonder if its repeatable? I guess its will be hard to test unless you already messed up, nobodys gonna mess up on purpose just to try this out without a hardware recovery option but maybe someone who messes up on accident will report back here on what they found out.
Wasn't able to repeat it on the Ouya kernel with CM ROM installed but it seems to work all the time if you get a boot loop in CM10 kernel and CM ROM. I'm still not feeling safe enough to actually flash the CM kernel, so I am still using fast boot to boot the kernel from a laptop.
On a side note, I do have xbmc set up as my launcher and have list of working skins that can launch android apps from. Once I figure out how to get the crazy CPU usage I am getting worked out I plan to make a guide for a full media center.
Related
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Okaay said:
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Click to expand...
Click to collapse
root the tablet
then install ROM manager and flash the official recovery from there
works perfect
The bug is that you cannot boot into any recovery (cwm/twrp/stock) from bootloader unless you are plugged into you computer via a usb cable. The only other way to boot is to use a script but that requires a working system partition.
Sent from my Nexus 7
I have the same problem and I flashed the official CWM from Rom Manager. I made a nandroid before I messed with it and when I went to change the LCD Density, I don't know what happened but now it won't boot. I can't get into CWM either. I figure I'll use ADB when I get home to try and reboot into recovery, if not I'll search the forums for the stock image and reflash. If there is a HW workaround to get booted into it from the device itself that would be awesome. I had to do a battery pull to keep it from rebooting itself and killing the battery.
I've always had Rom Manager Pro and immediately after rooting, used it to flash backups, update to 6.0 cwm, etc. If your rooted you must have that or Goo Manager for TWRP flashing anyway. Might as well start immediately.
There is a thread somewhere here dealing with changing density. The Nexus7 has problems when you simply use a density changing app.. You must change density by modifying prop.build. You can do this using a root explorer app, or by using Rom Toolbox Pro. I use Rom Toolbox and it worked perfect.
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
jmhalder said:
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
Click to expand...
Click to collapse
Will that command allow me to access recovery to restore my backup?
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
yeahthatsme said:
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
Click to expand...
Click to collapse
I believe you need to be on the bootloader screen? I haven't flashed anything from Asus in a while, not since my original Transformer.
chrisjm00 said:
Will that command allow me to access recovery to restore my backup?
Click to expand...
Click to collapse
Code:
fastboot boot recovery.img
where recovery.img is a CWM image, should allow you to get into the recovery to fix whatever you messed up. Note that ADB is only functional if you already have CWM or Android booted... in the bootloader, fastboot is all that's available.
I have the same issue. Stuck at the Google logo with a padlock at the bottom. I didn't flash anything with ROM Manager just the recovery.img through fastboot, then did a fastboot reboot. Now I'm lucky if I can get the thing to stay off when I hold the power button it just pops back up to the padlock with Google logo.
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
CooLoserTech said:
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
Click to expand...
Click to collapse
Has anyone figured a way to access recovery using the buttons only? I've tried TWRP 2.2 and the newest cwm, and on a cold start from power off, it sticks at the Google logo. During a bootloop you are screwed unless you have a laptop within arms reach. Until this is rectified I'm leery of flashing anything. The whole point is being able to restore a nandroid in a crisis. I haven't found that ability yet. If anyone knows a way, please educate me!
Guess we can just wait. Besides there's not much development yet anyways. Would love to use AdFree and root explorer though.
Sent from my Nexus 7
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
Recommend downloading quickboot. It is a paid app but it boots you to recovery no hassles with the buttons
Sent from my Nexus 7 using Tapatalk 2
Ya i have tried several version of CWM and TWRP and manually reinstalled cwm via adb. but all of them don't let me boot from the bootloader, i get the google logo like everyone else. Not sure what else to try, need to not take any risks until there is a fix i guess ^_^ hope someone gets some ideas
Hello,
I have tried searching but haven't been able to find a similar issue for any android devices (amazing right?). My nexus 7 will not respond to any soft reboot. From power menus to terminal to factory reset (yes including from ROM recovery and the like). It will reboot from the 10second press, but as we know that is pretty ineffective considering the nexus 7 has that bug where you can't access recovery from boot loader. I have tried connecting to a PC to force recovery, Nada.
So now I am out of idea. Also, for the next 2 weeks I don't have a PC, only a gnex and nexus 7...
Any help appreciated.
update your bootloader and recovery, that bug has been fixed. what rom are you running, every single reboot/power off option works here.
I can't update it without being able to reboot. And I know its not a common issue.. hense why I ask for help... I am not reporting a issue, I am asking for ideas... thanks for the tremendous comprehension though
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
MatAuc12 said:
I can't update it without being able to reboot.
Click to expand...
Click to collapse
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
MatAuc12 said:
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
Click to expand...
Click to collapse
let the battery die and power itself off, then charge it. flash another kernel for sure.
simms22 said:
let the battery die and power itself off, then charge it. flash another kernel for sure.
Click to expand...
Click to collapse
I did let it die for cold boot and again, understanding my problem means since I can't initiate a reboot or get into recovery I cannot flash anything
BillGoss said:
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
Click to expand...
Click to collapse
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
MatAuc12 said:
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
Click to expand...
Click to collapse
boot pressing volume down while pressing the power button into the bootloader, flash a different kernel via fastboot. you can flash franco kernel in fastboot, since it is in boot.img form, or extract the stock boot.img from a stock rom and fastboot flash that. ive had similar behaviors with test kernels, faux forgot something in the kernel. then download and flash the newest bootloadee to fix your recovery from bootloader bug.
Try simms22 approach first.But if you can't get into fastboot and you can boot into the ROM- then you could try rewriting the boot.img. Get the boot.img/kernel you want and use the dd command to write it.
Warning: you can do serious damage with the dd command.
If you need some help with this, let me know. But I accept no responsibility if things go terribly wrong.
Sent from my Nexus 7
So I flashed the latest nightly of CM10 onto my TF101. It was working well, nice and smooth... except I couldn't seem to install the Play store. I tried several different APK's including the latest one, and none of them seemed to work. The app would simply crash as soon as it started to load. So then I tried to flash in the Google Apps apk from this page. It seems to have replaced the entire CM10 build with that package, and since I'm such a genus with the greatest of ideas I had already deleted the CM10 zip file that was on my sdcard (because why would I EVER run into problems with flashing nightlies when I have so little experience doing so?)
So now my tablet is stuck in Clockwork MOD purgatory. It won't reboot into anything but CWM recovery, and I can't access the sdcard from my adb shell. Trying to push that CM10 zip file just results in a "protocol error."
Please help. I did want to replace this tablet with something newer, but I didn't want to do it this soon, nor did I want to lose the ability to sell this one or give it to a family member in need of a computing device.
Restore it to stock with Easy Flasher then start over. There's other ways to recover too, if you search the forums/google for "(tf101) recovery loop".
Lethe6 said:
Restore it to stock with Easy Flasher then start over. There's other ways to recover too, if you search the forums/google for "(tf101) recovery loop".
Click to expand...
Click to collapse
I started to try that, but for some reason I couldn't get into apx mode. It would just default into the CWM recovery when you press volume up. However, if you press nothing it seems to start a "cold boot" process which brought up CM10. The play store problem seems to be fixed though. The only problem is that if I don't hold the volume down button when I boot or reboot and let it "cold" boot, it goes right back into CWM recovery. I'm not sure if this will cause problems, but for now I can deal with it. I'll bring it back to stock and start all over with it if I start seeing any problems.
So thanks! Your advice helped, just not in the way you intended
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
poldie said:
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
Click to expand...
Click to collapse
Try Quick Boot in the Playstore.
sfobrien said:
Try Quick Boot in the Playstore.
Click to expand...
Click to collapse
I might try that but really I'm more concerned about my recovery going missing when I exit it.
Strange, never seen that and can't reproduce it. I suggest switch to TWRP and maybe custom ROM and see if that corrects the issue.
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
mhausig said:
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
Click to expand...
Click to collapse
I don't think anything actually happened - it just warned me that it might, and that I could either do nothing, or copy some files into system.
In the end I used TWRP which doesn't have the same problem.
This allowed me to return to my original problem, where I discovered that my game doesn't have a bug; instead, every single Nexus 10 has a problem with multitouch which Google doesn't even acknowledge, let alone fix.
I woke up and my phone was not turned on, when I did turn it on it turned right back off. So I wen't to recovery to reflash NexusV4from clsa but my /data and my /system could'nt be mounted so I fixed this by changing my file system from EXT4 to EXT2 and once again back to EXT4 on both the system and data, so after all of that I flashed Nexus and it booted up and then I decided to go back to the recovery and flash everything I had on there at once like Dolby Atmos and it would not boot after that it was stuck at the "your device is not trusted screen" so then I decided to flash B180 stock rooted Magisk from madvane20 and now my device with bootlooping and also the recovery splash screen pops up when I want to goto it and then it shuts off and then goes right back to boot
Can someone tell me or help me fix this, I currently don't have a computer for adb but I could use my fams computer. Thanks!!!
My suggestion would be to go back to https://forum.xda-developers.com/huawei-ascend-xt/development/rom-ascend-xt-nexusxt-b160-t3597766 and follow the instructions to get that working again like you had it. You may have to reinstall B160 firmware like instructions say.
Any idea what led to the phone getting corrupted? Be sure to make a full TWRP backup again once you get it working again and good luck
@InfinityXDA,
Were you not having problems with notifications not working with NexusV4 ROM like many reported in that thread? If you were having notification issues, maybe just flash and stick with the stock B160 ROM. Add Xposed, etc after installation.
Everything was fine for me bro @divineBliss
divineBliss said:
@InfinityXDA,
Were you not having problems with notifications not working with NexusV4 ROM like many reported in that thread? If you were having notification issues, maybe just flash and stick with the stock B160 ROM. Add Xposed, etc after installation.
Click to expand...
Click to collapse
I can't flash anything because the recovery does not work, like I said above it shows the splash screen and then reboots to the system and gets back in the bootloop.
Sounds like you need a PC to be able to do use bootloader to reflash recovery and maybe boot and system, then possibly have to flash the entire NexusV4 with TWRP depending on what happens after that.
InfinityXDA said:
I can't flash anything because the recovery does not work, like I said above it shows the splash screen and then reboots to the system and gets back in the bootloop.
Click to expand...
Click to collapse
divineBliss said:
Sounds like you need a PC to be able to do use bootloader to reflash recovery and maybe boot and system, then possibly have to flash the entire NexusV4 with TWRP depending on what happens after that.
Click to expand...
Click to collapse
Well crap I'll use my fams pc I guess
You're going to need to use fastboot at the very least.. I believe you can get to it via holding volume down and the power button. Then it's just a matter of hooking it up to a pc (only way otherwise would be usb otg or specialized equipment none of us have), and running the necessary commands to install twrp. I usually boot to new recovery first, though, to make sure everything works - file corruption is a lot rarer than the old days,but it still happens
-n0cturne- said:
You're going to need to use fastboot at the very least.. I believe you can get to it via holding volume down and the power button. Then it's just a matter of hooking it up to a pc (only way otherwise would be usb otg or specialized equipment none of us have), and running the necessary commands to install twrp. I usually boot to new recovery first, though, to make sure everything works - file corruption is a lot rarer than the old days,but it still happens
Click to expand...
Click to collapse
Do you think corruption happened??