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.
Related
I used Cyanogen's downgrade and rooting process. Seems to work great. However,,,,
I've been searching the MT4G boards on booting into clockwork recovery. I'm still struggling with this. I've tried hboot (hold volume down + power), and that doesn't take me anywhere. I do get a couple of haptic bumps. I also tried volume up + return key + power key. It seems to occasionally get me to hboot, but I think I keep factory resetting, because I loose my google log-in and my root. Note, it does say S=Off on this screen, when I can get to it. The last time, I think I flashed the PD15IMG.zip file when I got into hboot, but honestly I'm not exactly sure. It reloaded several functions and took about 10 minutes, so I think it did.
I can re-root. Once I figure this out, I will go through the perma-root process, but I'm just getting started on my wife's old MyTouch 4G. I've rooted my G1, my Galaxy S2, my G2x, now I'm trying to root and try some customer ROMs for my wife's old and no longer used MT4G.
Can anyone help me out here? Maybe point me to some obvious threads or websites? Bottom line, I want to get into Recovery once I root my phone. I can't seem to get there, except through ROM Manager, which is not very dependable, particularly if I screw something up, or get into an infinite bootloop, like I did flashing AOKP ICS.
TU Homer said:
I used Cyanogen's downgrade and rooting process. Seems to work great. However,,,,
I've been searching the MT4G boards on booting into clockwork recovery. I'm still struggling with this. I've tried hboot (hold volume down + power), and that doesn't take me anywhere. I do get a couple of haptic bumps. I also tried volume up + return key + power key. It seems to occasionally get me to hboot, but I think I keep factory resetting, because I loose my google log-in and my root. Note, it does say S=Off on this screen, when I can get to it. The last time, I think I flashed the PD15IMG.zip file when I got into hboot, but honestly I'm not exactly sure. It reloaded several functions and took about 10 minutes, so I think it did.
I can re-root. Once I figure this out, I will go through the perma-root process, but I'm just getting started on my wife's old MyTouch 4G. I've rooted my G1, my Galaxy S2, my G2x, now I'm trying to root and try some customer ROMs for my wife's old and no longer used MT4G.
Can anyone help me out here? Maybe point me to some obvious threads or websites? Bottom line, I want to get into Recovery once I root my phone. I can't seem to get there, except through ROM Manager, which is not very dependable, particularly if I screw something up, or get into an infinite bootloop, like I did flashing AOKP ICS.
Click to expand...
Click to collapse
Settings>Power>Turn off fast boot.
Power off your phone.
Hold VOLUME DOWN BUTTON + POWER BUTTON.
Now select Recovery.
crazykas said:
Settings>Power>Turn off fast boot.
Power off your phone.
Hold VOLUME DOWN BUTTON + POWER BUTTON.
Now select Recovery.
Click to expand...
Click to collapse
How long? Until after the first bump?
I re-rooted. Can't seem to get there except through ROM Manager...
If you hold vol down and while booting, the phone should boot directly to bootloader. If it doesn't, there may be something wrong with one of the buttons. You have to have the button held down early, though.
You can also use terminal emulator:
su
reboot recovery
Or in adb:
adb reboot recovery
estallings15 said:
If you hold vol down and while booting, the phone should boot directly to bootloader. If it doesn't, there may be something wrong with one of the buttons. You have to have the button held down early, though.
You can also use terminal emulator:
su
reboot recovery
Or in adb:
adb reboot recovery
Click to expand...
Click to collapse
Much thanks for your help.
I cannot boot directly into recovery. It simply doesn't work. Occasionally, I can reset my phone and boot directly into hboot, though I'm not sure what the process actually is. I've only done it twice, and I was just dicking around and didn't track my button sequence. I'm trying to track this methodically, but I really think the process works intermittently, which masks the appropriate process.
I gain SU status in terminal, but I cannot reboot into recovery. I can get in via ADB, so that works.
Two processes into recovery: ROM Manager and ADB.
My issue is I've tried to flash an ICS ROM, in this case Ice Cold Sandwich AOKP 8.5 Final Edition. It gets caught in bootloop. Twice. Can't seem to load up properly.
Could my phone simply be dorked? Maybe I need to push a new recovery file?
Start with something easy like Cyanogenmod 7.2. Make sure you wipe cache, data, and system partitions.
Ok. I got everything working. I think your perception that my down button is non-functioning is the first culprit. Also, I'm not sure why I just boot-looped. I did this for both CM7.1 and for ICS. One other issue is I could not reboot into recovery from stock. I could, however, adb into recovery.
I first loaded CM7.1 plus GAPPs. This just bootlooped. I then got back into recovery via ADB and just flashed CM7.1. This worked. From here, I could use terminal to reboot into recovery. I could also use the CM reboot option right into recovery. At this stage, I flashed GAPPs and that was fine. I then upgraded to ICS and it is working great. My down button still doesn't work, so the only method of getting into recovery in an emergency is via ADB. I can, however, use the reboot option into Recovery from my working phone.
Strange. I might dig deeper to see if I can correct the lingering issues, but it seems to work well, and I finally figured out how to get around with this old phone that's been collecting dust for over a year. Not a bad daily driver. ICS seems very stable, compared with my G2X.
Again, thanks for your help.
Well, progress is always good. Congrats.
I'm not sure if you already did this or not but take the PD15IMG.zip out of the root directory on your SD card. After you remove/move it and get to hboot you should be able to go to recovery. From there you could recover a backup (which hopefully you made before trying to flash a new rom).
Sent from my Dark Unicorn Resurrected v4.1 using xda app-developers app
Good advice. I'll do that.
Sent from my HTC Glacier using xda app-developers app
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 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.
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??