Related
Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville
Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!
Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.
Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?
Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?
Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.
Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?
n.N.n. said:
Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?
Click to expand...
Click to collapse
do you reboot into recovery when done or straight to OS
playya said:
do you reboot into recovery when done or straight to OS
Click to expand...
Click to collapse
The guide says to unlock bootloader, reboot to os, change settings, flash recovery, reboot, root.
But after your input, I did try it without the complete reboot and it worked. But shouldn`t a flashed recovery be persistant?
Edit: Did a second reboot, now there is the stock recovery again =/ But the root persisted.
[Q] Cannot enter recovery after flash of TWRP
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon
Have tried several recovery images
timmaaa said:
Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes, I have tried both TWRP 2.7.1.0 and 2.7.1.1 and Stock-recovery.img from 2008-12-31 - they all freeze in Android prompt when I try to boot in recovery mode. The only difference being, that only TWRP 2.8.0.1 causes the prompt to tyrn blue and then fade away.
The device just displays the Android [1+ said:
logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.
Trie advanced reboot to recove - no luck
habnzrot said:
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.
Click to expand...
Click to collapse
When I select reboot - recovery, I just get a brief message that 1+1 is rebooting and then it freezes in the Android prompt as before.
Re: can't flash a recovery that will work
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Success, finally
driftt said:
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.
Click to expand...
Click to collapse
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
Thanks milesman, but as you can see from the post above, the using the Philz image was successful. However, your suggestions may help other people, since the process really seems not to be robust.
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
TorkelJensen said:
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
I've had my OPO for a couple of weeks now and have had this problem all along. It took until today that i found this thread with someone having the exact same problem as me. After flashing a LOT of different recoveries (and different versions) I too noticed the only recovery I could successfully enter is Philz (although not all versions). I would prefer TWRP as recovery, but as long as I have one that is working that's good enough! It does however annoy me that almost nobody else has this problem. It makes me believe there is something wrong with the device. Flashing recovery in fastboot is always successful according to the logs. Erasing recovery in fastboot before flashing new one did not solve the problem either.
Before unlocking the bootloader, installing recovery and rooting, I updated the device from 33R to 38R. I now regret not doing that before updating...
I uploaded two videos showing the artifacts. The videos were recorded right after installing openrecovery-twrp-2.8.1.0-bacon.img from goo.im.
Since I haven't posted that much on XDA before I wasn't allowed to post links, please copy and paste.
youtu.be/jYJUfOOjaUE
youtu.be/GYcSjUKpOaE
Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
As written in the first post by n.N.n. this problem is not related to this option. The checkbox is unticked and recovery doesn't get replaced by CMs stock, it fails to boot.
Couldn't flash any recovery until I unchecked the "update CM recovery" option in the developper, thanks for the tip ! I didn't think this was also protecting the recovery !
I've had same exact probem when flashing twrp 2.8.x.x from fastboot or twrp. As a last resort I gave Flashify a go and to my surprise, it worked.
I had the same problem, but PhilZ's lastest (6.58.8 as of now) worked for me. I wonder why this is happening to some of us, but I'm glad I sorted it.
Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
Thanks, that solved the problem for me! I've flashed TWRP and CWM, but after rebooting into recovery mode there was always the CM stock recovery. After unchecking this in the dev settings it worked as it should.
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This worked for me thanks.
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This doesn't work for me.
erasing 'recovery'...
OKAY [ 0.026s]
finished. total time: 0.026s
Still stock recovery after flashing TWRP. Why is this so weird?
The Update thing in Developer is unchecked.
My other OPO was perfect
---------- Post added at 02:32 PM ---------- Previous post was at 02:19 PM ----------
TorkelJensen said:
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
This works for me.
Click to expand...
Click to collapse
After installing Custom Recovery (mine id TWRP), turn off the handphone. After that, do directly the boot to recovery (On/Off Button + Volume Down). DO NOT do the normal start, since the system will erase the custom recovery (and instal the "standard" recovery)
I've followed instructions to unlock my bootloader which is done. I'm not sure if - "Device is unlocked. Status Code 3:" is correct or not, but that is what I see.
After unlocking I flashed TWRP 2.6.3.0-xt1032.img and it flashed correctly according to adb (attached). When I reboot the phone into bootloader and select recovery the screen just goes blank. I also tried "recovery-clockwork-touch-6.0.4.7-falcon.img", which seemed to flash OK in adb. The bootloader screen goes blank when I select recovery on the phone for CWM as well.
Both recovery flashes showed a similar result on the phone - this paste is for CWM
In Moto bootmode:
USB Connected
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:07b2000
cmd: flash:recovery
Mismatched partition zize (recovery)
The phone has stock Android 5.0.2 installed and still works, but I can't get any further than flashing the recovery image in adb. I did flash the logo.bin in adb and it seemed to flash correctly .
I'm running Windows 8.1, USB 3 ports.
Is there something I'm missing, or a different way to do the root? I'm stuck at this point, but luckily can run with the stock ROM for now.
I would appreciate any help I can get, Thanks
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
koshikas said:
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
jjcdennis said:
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
Click to expand...
Click to collapse
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
koshikas said:
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
Click to expand...
Click to collapse
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
jjcdennis said:
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
Click to expand...
Click to collapse
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
koshikas said:
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
Click to expand...
Click to collapse
Thanks again.
If I find a correct ROM (I do have a KitKat 4.4.4 version), do I flash back with adb, or with mfastbootv2?
The ROM I showed was from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
I have also found a firmware link on this thread "http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795" that looks to be in the correct format. There are thorough instructions on how to flash the firmware, but I am not sure if this will fix my issue or not.
Would appreciate any advice on how to proceed.
Thanks
I finally understood your comment "...can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries". I got a copy of the stock firmware, extracted the recovery from it and flashed it via adb to the phone - ok. I then tried to get into phone fastboot recovery, but was faced with the blank screen again. I flashed twrp 2.8.7.0 and the same thing in fastboot recovery - blank screen. I also tried cwm 6.0.5.1 and the same thing, blank screen.
ADB sees the device and accepts the commands, but the Motorola fastboot recovery doesn't open any of the recoveries. Nothing else in the bootloader seems to work ie: Factory - blank screen.
Every one of the recovery files other than the stock recovery shows a pink colored error "Mismatched partition size (recovery).
Anybody have any ideas as to what I can do to get a recovery to work?
Is there a different way to root this phone?
@jjcdennis i think you should post this to one of the active threads, since nobody with experience (this is well beyond mine) has dropped in yet. i would highly recommend; http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Moved to http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
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.
Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please
I think this
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system
Jaco2k said:
Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system
Click to expand...
Click to collapse
I tried to do the same, but everytime I try to boot into recovery from fastboot, I get the same error
- FAILED (remote: Failed to load/authenticate boot image: Load Error)
Even tried different versions of twrp but same is happening
So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
In your first post you say "after installing TWRP"
If you have correctly installed TWRP you should be able to get to recovery by holding down power button and volume up button.
Jaco2k said:
So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
Click to expand...
Click to collapse
I did, installed TWRP quite a while ago before all this.
I was testing the latest dp on my mobile, but later I decided to revert back to stable. I flashed the pie version in local upgrade and wanted to start over.
So after booting once, I rebooted into TWRP and mistakenly selected system partition along with local storage in wipe option.
And now fastboot is the only thing I can boot in
I somehow don't think you are telling the story exactly as it went
I am assuming you flashed a full build and rebooted without flashing TWRP in-between.
Also, I am assuming you have flashed an older build that has the fastboot bug.
This means that you might be pretty screwed.
You can try to ADB push the full OTA via fastboot and flash it there using command line.
I guess at this point you are not caring anymore if you keep your data, right?
Also, there were some patched boot images laying around that might be worth flashing to see if fastboot is working on them.
As you have come across, there is a fastboot bug in some builds - I guess at some point it was fixed and then it reoccurred.
---------- Post added at 03:43 PM ---------- Previous post was at 03:39 PM ----------
BTW, I guess the link already posted in this thread might be your best bet, since you have removed TWRP when you flashed the updated build and you cannot fastboot recovery, as you have found out, due to a bug from OnePlus.
JerryDaBaaws said:
Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please
Click to expand...
Click to collapse
Just get the fastboot ROM for the same version you're on. For example 9.5.10 then you HAVE to use the one for 9.5.10.
https://androidfilehost.com/?w=files&flid=294300
Just download the Fastboot ROM (Make sure it's for your device as well). If on GM21aa then that's the one you use.
Put the phone in Fastboot mode and attach the phone to PC
Type Fastboot devices and make sure it comeback with your device serial number (like 6 or 8 digits, cant remember exactly)
Unzip the fastboot ROM and click on Flash-all.bat
Your phone will be like new as if shipped with 9.5.10 or whatever ROM you're on. There will be no root/TWRP/files (photos or music). You will have to do it all again but your phone will be working.