Tablet is rooted. Tablet has unlocked bootoader.
ROM Manager reports that I have recovery installed - both TWRP and ClockwordMod Recovery 5.8.3.4.
I want to update to 4.4.2 but when I go to try to boot into recovery, via ROM Manager or just manual hold volume down and power, I get the dead Android on his back with a red exclamation. No matter what recovery I try I get this.
Any thoughts on how to get out of it?
Ok.. I used this process to successfully flash the FlatLine CWM Recovery! Which I can now boot into that recovery via RCK selection and recovery bootup (power + vol down key)!
Not sure why the other recoveries were borked... but the key is the FlatLine recovery allows me to boot into recovery.
So this allows one to at least boot into a recovery and make a backup.
BUT this will not, I found out, allow me to install 4.4.2 (CM11) since you must use a TWRP or CWM recovery to install 4.4.2 (CM11) as FlatLine will not allow it
So then I use the same above Fastboot method to push a CWM recovery for the TF201 - fresh download of 5.8.3.4 - since I need a CWM recovery to intall the 4.4.2 (CM11) and... no joy. I push it by fastboot, boot into recovery, select RCK and it says it is going to "booting recovery kernal image" and then just hangs.
so still stuck. Any thoughts? I need to get to a kit kat and tf201 compatible CWM or TWRP recovery to flash the new ROM but I am stuck. I can only boor into the FlatLine recovery, but that does no good now.
So.... I opted to install TWRP 2.7.0.0 and that installed. I was able to boot into it, backup, and then tried it all again and.... FAIL!!
I get the same failed error... ugh!
So a ROM Manager install of 5.8.3.4 CWM fails to even boot
So a Fastboot install of 5.8.3.4 CWM fails to even boot
So a Fastboot install of TWRP 2.7.0.0 boots but fails to allow the 4.4.2 (CM11) install
So a Fastboot install of FlatLine boots but fails to allow the 4.4.2 (CM11) install
http://wiki.cyanogenmod.org/w/Tf201_Info
" Note: Support Status
This device does not support the newest version of CyanogenMod. This may be due to hardware limitations or simply because development is not yet complete. The last version officially supported was based on the jellybean branch of CyanogenMod. "
I believe you cannot run kitkat cyanogenMod as far as I know because you need cwm 6.0.+ version that isn't there . However there is a method to install kitkat on tf201 . I say so because I am running latest version of cyanogenmod snapshot m8 android 4.4.4 on my tf201 . There is just a simple matter of flashing recovery for tf300t ( well when I say simple ... ) on your tf201 .
http://forum.xda-developers.com/showthread.php?t=2773812
take a look at the link above . To install crombi-kk you flash twrp recovery version 2.7.0.1 (I think check the version I don't remember) . however there is no such version for tf201 . I never installed the actual rom but I played around and notice after doing step 2,3,then 2 again (in crombi-kk upgrade instruction) my device won't run cwm for tf201 but works fine with tf300t version of cwm .
I am talking from experience and there is always a chance of bricking as this is not an official guide but I think its what I did .
I was on twrp latest version of tf 300t and I installed cm snapshot m8 android 4.4.4 for tf300t device successfully . after using the rom for a while I noticed hangs when your device was on sleep and you wanted to wake the device , it just wouldn't turn on which forced me to hold power for like 5-10 sec to force a reboot.
I solved this by flashing cwm 6.0.4.7 for tf300t via fastboot . Again seems like development for tf201 and also tf300t is going to hell . so you won't find this version of recovery for tf300t on cwm site .However if you google latest kitkat recovery for tf300t or smthing like that I'm sure you will find it . These I think are ports from other people than acutal cwm team ...
One thing is for sure ... Cyanogenmod cm11 require cwm 6.0.+ or twrp 2.7.0.1 ...
Edit : as always do a backup ... and MOVE IT OUT of internal SD since for some reason it formatted all my data on internal plus my backups ... I messed around with more stuff though . but just in case be prepared for a formatted internalSD ...
I think I bricked it for good this time
I now can no longer fastboot in, so I cannot change recovery apps. I can boot into recovery - TWRP.
I boot up and I no longer have the USB plugin icon and fastboot will just no longer allows me to push a new recovery - says no device present despite having done it 20 times earlier. WHich sucks as I had a TWRP and Flatline recovery saved, an now I am stuck on an older version of TWRP and it does not see the TWRP recovery I made from a newer TWRP version.
This happened when I updated the bootloader to Hairybean.
So I am stuck in a circle where I can boot into an old TWRP, cannot push a new recovery, bastfoot seems borked and the tablet won't boot into Android.
I am sorry to hear that . I can't see where you wen't wrong to the point that broke fastboot . The post no.4 in link above has step to step instruction .
There is always APX mode (if you have backups) . I personally haven't worked with it but you should be able to do a recovery ...
http://forum.xda-developers.com/wiki/APX_mode .
Edit : take a look at the other Thread you posted . you might be on the right track after all .
Related
Hi all I want to ask for your help on that and made a mistake when installing the application GooManager.
I happen to install the application on my tablet GooManager back to my current rom, but the problem that I have is that my tablet really has the lock fastboot, and for that reason I have been looking for other alternatives in order to install custom roms without losing the current rom.
But now I'm in serious trouble because Goomanager urge upon the OpenRecovery-also install TWRP-2.5.0.0-hws7300u.img. using OPENRECOVERYSCRIPT.
This worked perfectly and manages to do the installation, but the problem is that not good for my huawei tablet and did not start properly.
I have now a recovery.img which is the stock of the tablet, but as I have the fastboot lock, I can not install it with adb and other methods I found surfing the web, so I ask for your help, if I can I can show you how to install the stock recovery in a safe and transparent, you do not need that this unlock fastboot.
Or if I can use the OpenRecoveryScript GooManager Scrip somehow to not install the OpenRecovery-TWRP-2.5.0.0-hws7300u.img and achieves install my recovery.img which is what I want to use.
I have similar problem. Installed TWRP 2.5 but it's buggy, cannot complete data backup (hangs with reboot). I need to install a previous twrp version but can't use fastboot for practical reason and rom toolbox crash while starting to flash twrp 2.3 :|
any hint?
Question: goomanager is able to flash a recovery with tablet on and not via adb fastboot, so can we flash a recovery (twrp or stock) via terminal emulator? How?
used good old dd on /dev/block/mmcblk0p17 partition
How and where..
Working on my brothers mediapad.. he have installed twrp 2.3.2.3 and it cant flash either stock or any roms i tested with. it say faild.
So now i want back to stock rom and stock recovery. Or get this crap to work.
Any help.?
I have understood that it can be repaired but from linux, you have to press the button volume + and volume-for more than 30 seconds, this connected via USB and then get access to the 32 partitions mediapad there looking for the recovery.img and replace it by ready stock and fixed the problem.
TheMasterMindGT said:
I have understood that it can be repaired but from linux, you have to press the button volume + and volume-for more than 30 seconds, this connected via USB and then get access to the 32 partitions mediapad there looking for the recovery.img and replace it by ready stock and fixed the problem.
Click to expand...
Click to collapse
how do you return from 10.1 cynogenmod the stock rom?
I've read through the entire HairyBean v2.31 thread , the TWRP 2.6.3.0 thread and the Transformer Prime CM-11.0 thread to get all my info ready ahead of time.
But I just wanted to see if I am correct in what the process should be when moving from HairyBean to CM 11 (or maybe 10.2... if 11 doesn't pan out).
1. First download the HairyBean downgrade bootloader (to sd), CM11 rom (to sd) and gapps (to sd).
2.Then download TWRP 2.6.3.0 recovery and PC tools like nvflash, nake drivers, etc. (to PC).
3. Boot to recovery and flash downgrade bootloader to get me back to 4.1 bootloader. At this point I assume I will not be able to load the ROM anymore, but recovery will work fine. Should I wipe dev, cach, etc. at this point too?
4. Then I would go right into Fastboot to start the TWRP install from PC.
5. Then boot to the new TWRP recovery and install from sd card CM 11 and gapps, wipe dev, cache, etc. and reboot and load into working ROM.
Am I missing anything? Once I'm on the new CM11 ROM, will I be able to simply flash updated nightlies relatively easily? I understand the Prime is easily brick-able (I have a Sero 7 Pro and it is so much easier then the Prime). So if I brick it at this point that I will have to wheelie flash my BLOB files, which I made before moving from stock to HairyBean.
Ok long story short i'm confused as to what's up with this device. I just picked it up and started messing with it. Looks like it has mako bootloader unlock and cwm 6x recovery installed. The only roms it can flash is cm12.1 and the factory ATT images correctly. I tried to update to the newer version of CWM or TWRP via fastboot and the flash takes but no recovery is present. Things i've tried =
Full factory reset via LGE970AT-01-V20j-310-410-MAR-08-2013 (this leaves me with no bootloader/fastboot/recovery) It boots but black screen on bootanimation.
tinybin (both options) only the altern will boot but. (have fastboot but no recovery.)
So long story... In stock firmware I can install freegee and unlock via mako but there will be no recovery if I choose TWRP and CWM won't install anything bt CM... I'm attempting to install Blisspop btw.
Any help would be great. Thank you
hi all. this is my first post, had to make an account to seek help.
in short i rooted my LG G2 D800 at&t, and installed cloudyg2 3.3 on it and forgot to install kk bootloader,
i did make a nandroid backup , the rom didnt worked, i restored the backup and now it also gets stucked at boot screen.
i then tried to copy rom in the mobile using adb push and adb sideload but it doesnt works, now i want to install cwm recovery with a hope to get it fixed.
is there any way to install cwm recovery while in twrp recovery in recovery mode?
thanks in advance
Hi,
I have a Sony Xperia Z2 Wifi tablet (SGP511). It currently has the outdated Cyanogenmod 12.1-20160807 (castor_windy). Because it has a lot of software issues, I decided to switch to a more recent ROM (since CM is discontinued). When I tried to access the CWM recovery I had before, I only got the Cyanogen recovery that came with the CM (where it is impossible to flash anything else but CM updates). So I decided to flash the recovery again using bootloader. The flash was done, but caused a startup loop. The sony logo is displayed and the device swiches off and on again, no matter if I leave it or try to access recovery. It seems that it is bricked, but I figured that by continuously pressing the red button besides the SD hole I can still force it to boot into the CM that is installed. So now I can boot into the old CM, and access bootloader by rebooting it via adb. What should I flash to gain back access to recovery?
Nevermind, I fixed it. By accessing the bootloader by ressetting the tablet using adb command I was able to flash the dual recovery from [NUT] . It worked, so I was able to flash the new AICP ROM from it.