So, I just decided to try and Flash the old TF101 with Katkiss 6.0.1 and Gapps, but I always get stuck on the same problem.
My TF101 is running Android 4.0.3 ICS and USB Debugging is on
I downloaded TWRP app on the transformer, as well as the latest .blob flash file through the app.
Before this, I rooted the tablet using Kingroot.apk, which worked. When I went to flash the tablet with the recovery, the app noted "Recovery Partition not found".
I tried to boot into recovery mode on my own, (Pressing Pwr + Volume down , Then hitting Volume Up), The android screen popped, up and then flashed to a fallen android with a red triangle.... The screen stays on this for a minute and then boots into the normal system. I can't even boot into recovery through ADB, using the
Code:
adb reboot recovery
, The tablet will just reboot normally, not into recovery mode.
The Device does recognize through ADB....
Is my recovery partition just non existent? Even when I just let the system though without pressing volume up, it only gives me the option of (Android) or (Erase Data). when I click erase data, ill stay on the asus loading screen indefinitely and nothing will happen until i turn it off and on.
I just cant seem to boot into TWRP for some reason, and that means I just cant install the downloaded custom ROM.
How Can I fix this and boot into TWRP? I've tried for hours and have been hung up due to the same problem each time, even after rooting.
Did you already solve that problem? I also need a solution.Thanks
Related
I successfully rooted my 3G XOOM today, installed ClockworkMod Recovery, but can't get into recovery mode! No matter what I do, I get stuck at a screen showing "Entering Android Recovery Mode Reading ODM fuse:1".
I waited for several minutes, and nothing happened. I tried to format th SD card, but didn't work too.
If I manually reset the Xoom, it stars normally and everything works fine.
Did you wait 3 seconds at the Motorola screen and hit volume down and then volume up? Were you able to get in it before?
Yes, i did that, but it gets stuck at that same point. And no, I never tried to enter recovery mode before.
How did you flash recovery the first time. Did you flash or push? Have you tried to push the recovery?
The first time I flashed recovery using the button inside ClockworkMod, and CWM said it went fine.
How can i push recovery? Using adb?
Got it! I don't know what caused the problem, but flashing the newest version of CWM recovery using this guide solved it!
Now I can proceed updating my Xoom to HC 3.1.
what worked for me was volume-down volume-up while holding down the power buttom ( like a shift key )
When booting into recovery mode, the system hangs.
(It can boot normal without a problem)
The device had JB without root, so did the following:
1. Installed the ASUS bootloader unlock utility
2. Installed TWRP 2.3.1.0
3. Installed CleanROM 2.4
Now, when booting into recovery mode:
Via the shut-down menu, the system reboots into the white ASUS logo screen and hangs
Via power+volume Up, and selecting the [RCK] icon, the system hangs (the top left of the screen says "Booting Recovery kernel image")
I'm guessing the system is looking for a ROM file and simply can't find it.
Do you guys ROM experts know what I did wrong and what the fix might be?
After reinstalling TWRP - Recovery mode is working again!
I'll leave this post up in case it happens to anyone else.
Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.
Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.
The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.
I recently picked up a virus on my rooted A510 and want to re-flash Nothrills.
I am unable to access recovery, either by holding Vol Down while powering on or with Vol Up while powering on.
Is there another method? (The power down menu has no restart/reboot to recovery option either)
Installed CWM with flashify and now I'm stuck in a permanent boot loop.
Either I power up normally and it stays on the ACER screen or I power up to CWM and it switches off and on again ad infinitum.
Help?!
I eventually got a little further. On the third PC I tried, using Linux, I was able to access fastboot as sudo and reflash CWM.
This time, when restarting to recovery I got the full CWM interface and I could reflash the ROM from the ZIP file.
however, after restarting I'm back to being stuck in
Bootloader version JB-d0ca683 (unlock mode)
Hi
My Max (M1) does not boot into recovery mode. I have researched and tried all key option, but I can only ever get the bootloader or a normal boot.The only way it works is via adb reboot recovery, fastboot reboot recovery gives me a normal boot.
The problem is that when booting after a recovery flash the partition seems to be overwritten again, so when I boot recovery from bash I only ever get the standard recovery manager, not the one I flashed. So I guess I would have to do it via the phone keys after flashing, right?
Am I missing something?
hiya there!
do your volume keys work correctly? the phone should boot into recovery if the vol- is detected while the phone is starting up (while its showing the asus logo/powered by android)
the only way you could stop the OS from overwriting your custom recovery is by booting straight into it right away (fastboot reboot-recovery doesn't usually work, atleast for my phone).
are you sure you're flashing the correct recovery? if the recovery is corrupt (or atleast not for your specific phone), the phone tends to just ignore and boot to the OS
does vol- while powering on the phone work when its running the standard recovery?
keep in mind, your phone's model is usually listed as one of those (as long as its a legit Max (M1)):
X00PD
X00P (i dont find a diff. between this and X00PD, considering that the stuff made for it works on it aswell)
Z555KL
Z556KL