Hi, I´m really hoping some kind soul will help me out
I have unlocked the tf701t with asus unlock tool. When I boot with "adb reboot bootloader" and choose RCK I first get a normal android avatar but then the android is lying down with a red triangle and nothing happens.
All tutorials I have found is based on flashing root/recovery through fastboot. But I cant get fastboot to work, or boot to the recovery.
I have rooted and flashed CM on like 10 different phones so I´m not a complete noob but for some reason I cant seem to find what I am doing wrong with the tf701t.
I am on 1WW_epad-10.26.1.18-20131217
Or is the screen with "RCK", Android and "Wipe Data" the fastboot screen?
Really hope You guys can help me out,
You need to update your bootloader with the official ASUS update first. Then you can continue. The CW recovery and the custom roms only work on the most update bootloader (which I think is .28 I cant check right now)
The screen that you are on after adb reboot bootloader is fast boot. selecting RCK is recovery. As you have the official recovery that's all there is is the lying android.
Sent from my K00C using XDA Premium 4 mobile app
Boot loader is the part where RCK, Android,WipeData buttons are. Pressing RCK will take u to the recovery. The android lying with red triangle is the stock Asus recovery. If u r trying to install custom ROM, u must first get a custom recovery, so far only CWM recovery works. Then u can install the ROM zip file through the CWM recovery easily. But before getting CWM 4.7, make sure ur on the latest firmware. 10.26.1.18 I believe it is.
Sent from my K00C using Tapatalk
THANKS guys, it was exactly like you said.
I was an a firmwire with the nr: 10.26.1.18 but not the latest "10.26.1.18".
So after updating with Asus firmwire fastboot was working for me and everything went smoothly.
Superhighly appreciated that you took the time to help me out, you guys just made my day
Related
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
drawde40599 said:
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
Click to expand...
Click to collapse
Use fastboot to re-flash recovery img
lcchan1 said:
Use fastboot to re-flash recovery img
Click to expand...
Click to collapse
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
drawde40599 said:
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
Click to expand...
Click to collapse
download clockwork recovery from the app store.
Flash its recovery, then boot into recovery after a successful flash.
Out of curiosity, why did you install a non-rooted version of 2.3.3.?
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Rusty! said:
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Click to expand...
Click to collapse
HELL YA !! thank u much
Thread moved to Q&A, a sub-forum dedicated exclusively for questions like these. Please post all further questions here. Do not post new question threads in development, as you are not doing any even remotely related to Android development. That said, I'm glad you were able to figure out your issue.
Downloading clockworkmod will not work. He is not rooted so he can't flash the recovery with it.
Sent from my Nexus One using XDA App
This happened to me 2 days ago (word by word)!!
From Amon Recovery's page, this is what the problem is:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here"
Here: http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
My problem was even more complicated because I tried flashing froyo without a wipe so my phone started going into boot loop!
Thanks to danger-rat's reply, I was able to get into recovery at least once and then everything came back under control. He said "Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to..."
Here's my thread:
http://forum.xda-developers.com/showthread.php?t=980577
edit: I just realized that you are not able to fastboot either? I was able fastboot and flash recovery onto my phone and then without turning the phone off - I was able to go into recovery straight after flashing amon_recovery.img
passimg back to an earlier version of Android, root, then install a pre-rooted GB...
If you get the "main version is older" error, you're out of luck and your only option is to unlock the bootloader or wait for a new method to be found...
Sent from my Nexus One using XDA App
EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
how were you able to root it
Lord AJ said:
EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
Click to expand...
Click to collapse
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
daniiaroxyo said:
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
Click to expand...
Click to collapse
If the recovery goes back to stock then you should probably try to boot into the recovery before rebooting to system after SP Flash Tool has done it's job.
Hi so I down loaded one more time the recovery thru sp tool
But this time I took the battery out for few seconds instead of rebooting right away
And it worked
Once I rooted back the phone I tried flashing the gapps but it didn't work
I tried changing the permission s thru root explorer for the google base app as I so on a post and nothing
Any ideas
Hi,
On my Mi5 I wanted to put TWRP as recovery in order to flash a custom ROM. Device was unlocked using the chinese dev. rom( checked settings - root access)
I go into bootloader flash the latest twrp 3.0.2-1-gemini and boot into it. Nothing more happens then the splash screen.
Any suggestions what I maybe did wrong? Tried more than one step-by-step guide but can't make it.
Thx
I have the same issue. I thought I solved it by using the previous version (3.0.2.0), which worked the first time, but not the following ones
yes i also experience this problem. It got stuck on TWRP logo. And when i try to reboot and enter recovery mode, the stock recovery replaces TWRP. Hope someone can help us? I'm using twrp-3.0.2-1-gemini.
This is a well known problem. Flash 3.0.2-0 and it will go away.
Sent from my MI 5
yoocharns tip worked - installed that version from twrp gemini section and got into TWRP.
TY
Hi guys, little help please.
So I had the stock firmware 4.3 installed then I tried to flash the boot image of Lineage os. I don't know what I messed up, but I now don't have CWM recovery or TWRP, but a Cyanogen recovery that is very limited. If I try to install the Lineage os or CM 12.5 from there I get an error. How can I go back to TWRP recovery. I'm not able to boot into android any more.
Can some one point me at what i should do, I don't want to mess any more with it?
I need to fix it in the next 36h before I have to go and leave my dad's phone unusable.
Mysteoa said:
Hi guys, little help please.
So I had the stock firmware 4.3 installed then I tried to flash the boot image of Lineage os. I don't know what I messed up, but I now don't have CWM recovery or TWRP, but a Cyanogen recovery that is very limited. If I try to install the Lineage os or CM 12.5 from there I get an error. How can I go back to TWRP recovery. I'm not able to boot into android any more.
Can some one point me at what i should do, I don't want to mess any more with it?
I need to fix it in the next 36h before I have to go and leave my dad's phone unusable.
Click to expand...
Click to collapse
Use Flashtools to install TWRP.img again.
Sent from my Xperia SP using Tapatalk
I had to flash TWRP.img as boot instead of recovery.
Hey there!
I am trying to flash TWRP 3.1.1-0 into my Xperia SP using ADB and apparently it cannot find the "recovery" partition. I've found out I can flash into "boot" instead but my question is, is there a way ( or should I even try) to fix this? I've tried Emma but my device is not supported. It's bootloader is unlocked and I am using Lineage OS 7.1
As far as I've searched in the forums ( https://forum.xda-developers.com/xperia-z-ultra/help/recovery-partition-xz-ultra-flashing-t3453568 ), at least for Xperia Z, it means the bootloader I originaly flashed used a "boot" partition instead of "recovery", right?
The final goal of this quest is to relock my bootloader so Sony Companion can reinstall the original firmware and get it as original as possible.
I am new here and, I hope I am posting this in the right section and I did my research right. This forum is so big it is a little overwhelming.
Thanks in advance!
flash recovery into boot
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!
FuchsXSP said:
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!
Click to expand...
Click to collapse
Yeah that's pretty much where I'm at right now. Whenever I flash TWRP into my Xperia SP using " fastboot flash boot twrp****.img" it works but when the phone boots the TWRP is all that is on the phone. It will not boot into the system. But then, when I install the OS using TWRP, the OS overwrites TWRP and I am back to the old cyanogenmod bootloader.
So answering your questions:
FuchsXSP said:
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"???
Click to expand...
Click to collapse
Yeah that's pretty much how it is done. At least on my Xperia SP. ( I love this phone btw XD)
FuchsXSP said:
After I have done this, I can reboot normally and TWRP will start?
Click to expand...
Click to collapse
Yeah it will only boot into TWRP. You probably wont have access to to your system anymore.
FuchsXSP said:
Then I will be able to install LineageOS?
Click to expand...
Click to collapse
Yeah, just press Install, select the file, and swipe that cool looking safety slider and it should be fine. Beware though older versions of LineageOS had some problems with zip signatures, just make sure to have the newest nightly version (07/12/2017 I guess) and you should be fine.
I have to say though, as anything with android modding, do at your own risk =p.
Here is the solution (at least, the one that worked for me)
I had similar problem - my phone was booting either into Lineage or TWRP, but I had to switch these using ADB commands.
Then I found an application in the Google Play store which can repair this. Look for "TWRP Manager (Requires ROOT)" - from Jmz Software. Free version is good enough.
I installed it and then when I tried to select the option to install TWRP, it tried to install, then complained that there is some problem with my configuration and it looks that it has been repaired. (I'm sorry for not repeating exact messages here, I was doing this about month ago, but when you install this application, the rest is quite self - explanatory).
Anyway, try this. Now my Xperia SP is booting flawlessly - Lineage or TWRP, of course "Reboot to Recovery" option in Lineage also is working correctly !
Xperia SP does not have a dedicated recovery partition like most of other Android phones and a newer Xperia variant. To workaround, the developers of this device have been using different ways of implementing recoveries, the latest and working one is by loading the recovery into our FOTAKernel partition, which is a partition that plays an important role during Stock OTA updates.
Since such a partition serve absolute no purpose when you ventured into custom ROMing, the idea of making use of it for recovery is quite neat. This "feature" is Adrian DC's implementation.
To answer to your question, no, you cannot flash a recovery using fastboot (or any other tools that makes use of fastboot). The options provided by the tool is only limited to partition names, not addresses. You can though, download the FOTA zip from the TWRP thread, and then flash them in the recovery (the one that you booted into because it was installed in /boot). Then re-flash the ROM zip so that the boot image of the ROM gets flashed properly.
It works
Hi,
I have success. On my Xperia SP is now LineageOS 14.1
1. Unlock Bootloader via Sony
2. fastboot flash boot twrp-3.1.1-0-huashan.img
3. reboot SP into twrp
4. wipe and install lineagesOS and opengapps
5. reboot
Now, i can access twrp with second recovery mode (FOTA)
Thanks for your help!! :good:
solved !
sorry to need to bump this thread, but i am having similar issues - i have successfully flashed twrp-huashan as shown in the post above, but on rebooting into twrp, wiping and installing adrian's oreo build, i lose access to twrp
attempting to boot to recovery shows a very brief droid on its back, and then tells me to choose to boot to system or recovery, neitherof which get me back to twrp
any suggestions, as i do not understand why this is so
edit : all is revealed !!
[Recovery][OFFICIAL][UBL] TWRP 3.2.1 Touch Recovery for Xperia SP
https://forum.xda-developers.com/xperia-sp/orig-development/recovery-twrp-3-0-0-touch-recovery-t3309938
Xperia z wont go into recoverymode. blue light with black screen
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?
Blue light indicating fastboot mode on Sony Xperia Z5
Karimano24 said:
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?
Click to expand...
Click to collapse
Well, that's it. The blue light indicates fastboot/recovery mode on the Xperia Z. You can now connect the Xperia to a computer via USB, then run e.g. 'fastboot devices' and it should list your Xperia. Or run 'fastboot flash recovery <image filename>' to flash TWRP onto the Xperia.