Database Info

Updated to RC33 and no longer can enter recovery mode?

Hey all, I had the rooted RC30, and just updated to the RC33. The update itself went fine, but when I am trying to go back into the recovery mode to apply the radio rom update, I cant get the phone to go into recovery mode anymore. I hold the home and power and all it does it cycle the G1 screen. Then boots normally. Anyone have a idea whats up?

Anyone? =/

Ok Im running out of ideas, I tried booting into recovery mode without the memory card inserted, still goes in a reboot cycle and will only boot into the normal mode, wont go into recovery, so I am really confused now. Any advice or so how to get things back to normal would be great please.

try going into the terminal and typing reboot recovery

This just happened to me to i really need help i dont know whats goin on just started... could the phone be possibly bricked? O yea and that process didnt work Tubak is there any other ways to get into recovery mode

Can you boot into the SPL (hold camera button while powering on)? If so, you can fastboot flash the latest recovery.img (from the JFRC33 1.42 build), and that should get you going.

tubaking182 said:
try going into the terminal and typing reboot recovery
Click to expand...
Click to collapse
Says "Operation not permitted"
as for holding down the camera button and powering up, I can get into that screen. So your saying just to reflash the pack I just updated with again? It wont wipe my phone will it?
But yea, would be nice to get things going again. Also oddly when I boot the phone up, normally process media is asking me to either wait or force close. Sometimes another app will be listed as well. Anyone else have that on bootup like if the phone has too much starting up with? Btw thanks for the replies so far. =)

did you run the reboot command as root? if not run it as root, sorry i assumed you knew to but i didn't specify so it can be confusing. also as daveid said you can always try to fastboot flash the recovery image

tubaking182 said:
did you run the reboot command as root? if not run it as root, sorry i assumed you knew to but i didn't specify so it can be confusing. also as daveid said you can always try to fastboot flash the recovery image
Click to expand...
Click to collapse
The response was "Can't open reboot" when I did su reboot recovery
(Edit: Scratch that I feel stupid I wasnt in # mode yet, the reboot command worked however it did the same thing, cycle the G1 screen, rebooted again and booted normal)
Also again on the flashboot, so I use the same file I used to upgrade to rc33? Also it wont wipe my phone would it by that method?
Edit: So if its not too much trouble by doing the fastboot what is the real method of using this? Also which file am I using and will it wipe? And is there any other possible reasons why this could happen that it didnt go into recovery mode?

Mysticales said:
The response was "Can't open reboot" when I did su reboot recovery
(Edit: Scratch that I feel stupid I wasnt in # mode yet, the reboot command worked however it did the same thing, cycle the G1 screen, rebooted again and booted normal)
Also again on the flashboot, so I use the same file I used to upgrade to rc33? Also it wont wipe my phone would it by that method?
Edit: So if its not too much trouble by doing the fastboot what is the real method of using this? Also which file am I using and will it wipe? And is there any other possible reasons why this could happen that it didnt go into recovery mode?
Click to expand...
Click to collapse
You will want to extract the recovery.img from the JF update.zip to wherever you have fastboot installed. Then you will enter a command prompt, change to that directory and issue "fastboot flash recovery recovery.img"
If you need further help see the sticky here.

Ok been a lil while since I went back to this issue.. (Had my phone suspended so wasnt using it) Just got it back running after a month.
I looked at the sticky, but Im guessing Fastboot wasnt installed? So to install it, do I just need to put the fastboot onto the memory card or so? Guess just need lil help cause hate this.. since I cant get into the real recovery, but I can go into the other one.

before u updated to jfrc33 you shouldve done this
if u followed directions on the thread it would worked
so this is the only way i see possible to get the recovery program back
u have to go back to rc29 and then re-root and install the recovery image
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
edit:
check my sig for the jf tutorial
"unlock your dream"

Question tho, I already had jfcr installed w/root before I updated to the newer version, which I was told was fine. I still have my root access atm as well since I use root only apps.
I can still access the other mode by holding down the camera button. So your method your suggesting, is that what I really need to do or is it something else based off this info?

Alternatively, you could push recovery.img to /system using adb.
The init script will reflash it automatically.

billc.cn said:
Alternatively, you could push recovery.img to /system using adb.
The init script will reflash it automatically.
Click to expand...
Click to collapse
adb? Explain some more please? ^^
edit: Using the terminal, ok I saw some similar commands. Ill give this a shot once I get home with my PC. Anything special I need to prep before I do it or just put the img file in the sd root dir and do the adb command for push?

Ok good news. I was more nervous about toying with things I dont know 100% however I sat down a lil more and figured out everything that was being said. The fastboot flash recovery recovery.img worked.
This posted helped ALOT.
http://forum.xda-developers.com/showpost.php?p=3083753&postcount=1
I was under the impression at 1st however that it was done all via the phone itself and not the PC. So thats where my orig confusion started. However I am now back into my recovery mode and can go back to updating my phone. =)
One quick question tho, after I got the PC to be just the ADB interface, how can I get to mount it to my PC again as a mass storage device? Just redo the drivers again? Or is there a way to swap easily between the 2 modes? (I can use a memory reader so its not a big deal but thought id check)

[Q] New Android update bricked phone.

Just got a notice that there was an Android update, I'm assuming a small patch. But now I'm stuck in at the LG boot logo. I can still boot into TWRP recovery. But no matter what I can't start my phone all the way up. How do I fix this?

gpitner said:
Just got a notice that there was an Android update, I'm assuming a small patch. But now I'm stuck in at the LG boot logo. I can still boot into TWRP recovery. But no matter what I can't start my phone all the way up. How do I fix this?
Click to expand...
Click to collapse
You should never install updates if you have installed a custom recovery.
Did you do a factory reset from recovery? That should fix it.
If doing a factory reset doesn't fix your phone, then you need to flash your stock firmware or a custom rom.
Cheers

What worked for me was from the TWRP terminal command was to type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter,
and type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
However I won' take credit for coming up with this, Weston Madsen over at androidcentral and the IRC xda-devs helped me put it all together. A huge thanks to them!

never do update if you have a custom recovery

[Q] Running TWRP on top of CWM with Aroma Installer??

Some of you may be wondering by the title of my thread, "Why in the world would you want to do that? Just install TWRP completely!"
The simple answer to that; I simply can't. I am unable to overwrite my recovery using goo manager/recovery flashes/terminal emulator, etc. And now you must be thinking. "Well just reset your tablet using NVFlash or the ADB Toolkit!" But alas, I just cannot for the one reason that has killed me for the past two years:
No computer will detect my Transformer.
That's right, plugging up my tablet to a computer via USB cable does nothing at all. And no, it is not my USB cable, because I have tried multiple. All I have ever wanted to do was upgrade from Android 4.1, but I cannot, because my current CWM image doesn't fully support it. So this brings us to my first question: Is it possible to run another recovery on top of my current one, just so I can flash a kitkat ROM? Is this even possible? Will it prove ineffective because it's running on top of the incompatible CWM anyway? Any and all answers will be appreaciated. I really wish I could simply use an easy Flash tool, but I just happen to be hated by all devices. Any fix to my recovery issue or my NVFlash/USB cable issue will be GREATLY appreciated! Thank you for your time

What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?

doppelhelix said:
What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?
Click to expand...
Click to collapse
I'm running clockworkmod touch (version 5.something) I don't get any progress bar after flashing a new recovery.zip
if I flash a new recovery.zip, it goes through successfully, but it never actually flashes. I can reboot into android via the "cold-boot" method (booting normally takes me to recovery). I don't know about the su command. I'll get back to you on that.
Edit: u0 [email protected]:/ # is what I get, so no root user. Just u0 with the root pound sign after. That's the only change

creed10 said:
That's the only change
Click to expand...
Click to collapse
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.

doppelhelix said:
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.
Click to expand...
Click to collapse
I followed everything step by step, and it all went just how you described! After nearly two years of having a screwed up tablet, you sir, have helped me resurrect it! I see a donation coming around!

Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru

doppelhelix said:
Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru
Click to expand...
Click to collapse
Sounds great! I will be forever in your debt, kind sir

Unbrickable tf300t

Hello everyone. I am new around here and totally new with android devices. I got my tf300t, installed twrp and flashed to the newest android version. Then my dad suddendly pressed something like restore to the manufactory setting and after that it rebooted and just keep booting with teamwin logo. I can not access twrp recovery mod, it is just in boot loop. I managed to get adb to work, but no fastboot since it does not boot into recovery mode. When I am in adb I can browse the device but the adb reboot bootloader does not work at all. It just hangs there. I can not power off the device because it does not let me, I can not boot into recovery mode with powerbutton and volume down button. After a long power button press it only reboots. I even tried with hard reset button but still the same. Could You please help me somehow? I really need that device for school and I would like to get back into the stock android. Thank you so much for any help.
//edit : I also forget to mention, when I execute adb deviced it shows:
List of devices attached
0123456789ABCDEF recovery
Also the device is unlocked.

Did you tried: adb reboot recovery ?
Did you tried to flash recovery again?
Be sure to use the right recovery for your bootloader. Did you upgraded bootloader to latest ASUS one? One then you're able to flash current recoveries like TWRP like 2.8.5.0 oder 2.8.7.0.
Edit: Also take a look here -> http://droidmodderx.com/prime/?page_id=74

Hello sir. Thank you for answering. I tried adb reboot recovery and it just hangs to be executed... But the tablet is still flashing the teamwin logo. I have the same bootloop as the guy on youtube called Francis Domingo and video called Samsung s5 stuck at TWRP Recovery boot loop (unfortunately I can not add link here).
//edit: Thank you for the link. It look like I have to use option 1a. Is it safe to use that command and I will not make it even more bricked? Thank you so much
//edit2: Now I just realized how to turn off the device to stop from rebooting. I just long pressed power button and up volume button and after the screen went black I kept holding the up volume button. I didn't work with down volume button or if I stopped holding the up volume button after black screen it rebooted again.
//edit3 : Let's say if I get to the twrp mode with option 1a from the link, what do I have to do next to get back to the stock rom (I think it was something like 4.0.3) ? Thank you

What the guy does in 1a is wiping mmcblk0p3.
Afaik mmcblk0p3 is the staging partition. That would be my guess anyway if you had access to fastboot. Usally when you can't boot into recovery, something is wrong in staging. I got the same problem 2 days ago. In this case you usually wipe staging partition via fastboot.
Since you got no fastboot access, you have to try with adb.
After cleaning the staging partition you can flash any recovery you want back again.
The recovery must be flashed to mmcblk0p4 <- 4!!! is the recovery partition. (but you should wipe mmcblk0p3 (3!!!) before)
So I would say, try what solution 1a suggests.
Edit: You can go back to stock android if you want, but there is no reason for this. My advice would be to unlock and root your device, upgrade to latest boot loader (which is done by upgrading to latest stock rom), then flash TWRP 2.8.5.0 and then a useful ROM on top. I'm using the one from timduru which is very nice. You can find it here: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783

Thank you for the answer. Could you please write a step by step to get out of brick and to get the stock version, because the newer one I installed was many times slower. The reason why I would like to have step by step is because I don't wanna mess it even more than it is. Thank you so much.
//the stock rom was much more faster than the one I have installed, I mean... the boot time wad unbelievable slow, same with responses and wifi problem. If there is any other faster rom than stock I would be happy but I don't wanna mess with any bugs or slow boot speed and I can not wait minutes until it boots.

Hm, try the Option 1a from the link.
If done, boot into current recovery. Tell me which version and which recovery do you have.
Top on this we can decide what to do to flash a good ROM.

I had the exact same thing happen to me yesterday. Option #1 worked for me.
I did the steps from option #1 and powered down using the volume up + power. I then tried to boot into TWRP recovery, which only reproduced the same issue.
I redid the option #1 steps, and this time powered down using the power + volume down. I powered back up normally, and it rebooted normally into the ROM.
The tablet now works normally, and I can also boot back into TWRP recovery with no issues.
Thanks for the thread and the link.

Thank you so much Catscratch! After I executed both command from option 1a I can get into the screen, where it shows three options: RCK, Android, Wipe Data
In the top left corner, there is written:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
The tablet can boot into the last ROM but as I said, I would like to have the faster and less buggy rom than this. When I open the settings and click about button there is written: CyanongenMod: 12.1-20150814-NIGHTLY-tf300t and Android version 5.1.1.
If I start RCK it just brings me back to the loop, but now I have fastboot available as it said above and I can list the fastboot devices on computer, which I couldn't before. Should I just execute this command from the computer "fastboot -i 0x0B05 flash system blob" and then "fastboot reboot" or should I download ROM from asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/ -> OS Android -> Firmware and now I don't know which should I choose: If JP or CN or WW or US or TW (Probably US right?). After that should I execute "fastboot -i 0x0B05 flash recovery firmware.img" and then "fastboot reboot" ? Or which ROM should I download to make it even faster and less buggy than stock ROM? Thank you so much again, You saved my tablet
//After I unzipped downloaded US ROM there is no img file. If I remember right the img file is only recovery to reflash the actual one and then when I start the twrp recovery I will select zip file with rom right?

OK, first of all to continue...I assume you got root access. (I think you should have, because you already got CM installed)
Next. Downloads.
Download: https://twrp.me/devices/asusTF300T.html
Also Download ROM+SuperSU: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
And GApps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Push all files to sdcard with "adp push" or in CM. Like you want.
Flash TWRP. (you can skip this step if you already got TWRP 2.8.5.0 or higher version). You don't need latest one.
fastboot -i 0x0b05 flash recovery twrp.img
fastboot reboot
- or -
adb reboot recovery
Now, go into recovery and wipe everything:
- cache
- dalvik
- system
- data
After that flash ZIPs from sdcard. (use "add more zips" option)
1. ROM
2. Gapps
3. SuperSU
Next: Wipe cache and dalvik again (only these two).
Reboot and wait. First boot can take some minutes.

Thank you so much again. Everything work perfectly The rom looks a lot faster than the older one I had there. No issues yet at all. Just awesome. Thank you so much. Really appreciate your kindness and help. You have a nice day !

Thanks. Have fun with your tf300.

Moto G (1st Gen) Always Rebooting into TWRP

Hi All,
I have a Moto G (1st Gen) with Unlocked Bootloader, Custom Recovery (TWRP) and ROM (Cyanomodgen 14.1) installed. After lots of trial and error and much help from threads here everything seems to be working....except for 1 thing. When I restart or turn the phone off and back on it always boots into TWRP.
If I click Reboot and Bootloader in TWRP it goes into fastboot and from there I can select Normal Powerup. This gets me back into Lineage 14.1 and everything works great on the phone BUT if I power off or restart it always goes back into TWRP.
If someone could please help me fix this or point me to the appropriate thread I would be grateful.
Sorry for the long post (I am somewhat clueless despite reading a ton of threads on here)

Bump
I finally found a solution to my bootloop problem and thought I would post back in case others were struggling with this.
In TWRP
1. Go to Advanced--->Terminal
2. Type dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota and hit enter
3. Type: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc and hit enter
4. Reboot into System
Hope this helps someone