I flashed clockworkmod recovery a couple days ago, not knowing that TWRP was out there. I'm trying to flash TWRP but now my phone won't boot into recovery after flashing. I tried erasing the cache and still no luck. Here's how I did it
Code:
#fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.672s]
finished. total time: 0.672s
# fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.116s]
writing 'recovery'...
OKAY [ 0.877s]
finished. total time: 1.992s
Then when I try to boot into recovery I get the HTC logo with pink text saying it's booting into recovery, it stalls, and then reboots normally. I'm running CM 10.2 and using adb in linux mint.
i had the same problem, i just left clockwork on there, i gave up after flashing it like 30 times. I did all the exact same things as you. Also checked the MD5 and verified what i had was what it was. Just letting you know i had the same problem as you, id love to find a answer myself. BTW you can still flash clockwork back on it to do recoveries.
I've come across more than one person online who has the same problem too but no definative answer.
I wonder what would happen if you wiped the recovery partition in CWM and then tried flashing twrp...
What if you tried the recovery in the thread about taking the update. And then flash twrp...worth a shot.
Sent from my One.
Chilidog said:
I wonder what would happen if you wiped the recovery partition in CWM and then tried flashing twrp...
Click to expand...
Click to collapse
I'll give that a shot this afternoon.
brymaster5000 said:
What if you tried the recovery in the thread about taking the update. And then flash twrp...worth a shot.
Sent from my One.
Click to expand...
Click to collapse
Which thread are you referring to?
I had this same issue , here is what I did to fix the issue . I flashed a modded hboot to remove the red text and now I boot into recovery every time .
cbrown245 said:
I had this same issue , here is what I did to fix the issue . I flashed a modded hboot to remove the red text and now I boot into recovery every time .
Click to expand...
Click to collapse
Hmmmm, now you got me.... Still doesnt explain why it works for some and not others
cowmoo32 said:
I flashed clockworkmod recovery a couple days ago, not knowing that TWRP was out there. I'm trying to flash TWRP but now my phone won't boot into recovery after flashing. I tried erasing the cache and still no luck. Here's how I did it
Code:
#fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.672s]
finished. total time: 0.672s
# fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.116s]
writing 'recovery'...
OKAY [ 0.877s]
finished. total time: 1.992s
Then when I try to boot into recovery I get the HTC logo with pink text saying it's booting into recovery, it stalls, and then reboots normally. I'm running CM 10.2 and using adb in linux mint.
Click to expand...
Click to collapse
You're using the wrong image for TWRP on the HTC One. What you want is
"openrecovery-twrp-2.6.3.0-m7vzw.img".
I had a problem while trying to flash TWRP as well (I got my root and s-off with rumrun) , I'm just going to stick with CM, its much simpler anyway.
cowmoo32 said:
I'll give that a shot this afternoon.
Which thread are you referring to?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2469057
Sent from my Oney Bone.
Related
Edit - Problem was after flashing hboot I could not boot into recovery .... I tried multiple recovery images AmonRa and Cwm but it would never boot.
Solved - I have no idea how, I downloaded the recovery image again with the same link as the previous images, all md5sums were ok, but the 4th download worked and I was able to flash + boot into recovery again? Do I have some other problem though because I don't see why it took so many flashes for me to be able to access recovery again?
Alphrev Cm7 r2
Bravo PVT1 Ship S- OFF
Hboot-6.83.1002
Radio-5.17:52.18
C:\android\tools>fastboot devices
HT~~####93 fastboot
C:\android\tools>fastboot flash hboot bravo_alphaspl-cm7r2.img
sending 'hboot' (512 KB)...
OKAY [ 0.096s]
writing 'hboot'...
OKAY [ 0.164s]
finished. total time: 0.261s
C:\android\tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\android\tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.040s
Reboot to recovery - stuck on splash??? Using Reflex S...
Edit - After trying to boot to recovery, sat on splash screen for 40 mins and then my bootanimation randomly started... everything is just back to normal?
I can't seem to be able to flash recovery though, it just doesn't boot into it?! I've tried a couple of images and checked md5sum's but it always sticks on splash??
hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway
bortak said:
hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway
Click to expand...
Click to collapse
I shouldn't of posted really but something that usually take 10 minutes took an hour or two.... I used the exact command everytime and the same files... It just didn't work!? I'm still really confused but happy it's working
UPDATE: Still no solution found - new Ideas very welcome.
Hi there,
I'm at the end of my wits with my HOX which is with a german o2 branding. After getting stuck in bootscreen after athe OTA-Update from 1.26.207.2 to 1.28.207.9 - which failed for some reasons. I tried to install different Custom-Roms, none of which would boot beyond the first HTC-Screen.
The latest one I tried was Cyanogenmod, that did boot fully but I got constant "andoidupi crashed" messages, so I tried to reflash it.
After that things got weird, because right now I can't really do anything anymore. If I try to relock it via "Fastboot oem lock" it just reboots and it boots straight into CWM 5.8.3.1 but when I get back to bootloader its still "**** UNLOCKED ****"
I can flash boot.imgs via fastboot flash... but even so its says at the command prompt that it was successful flashed, it really isnt. No matter what - at reboot I will boot into CWM.
It is like working on a virtual machine - the HOX gives all the right responses, but noting I try to flash is permanent.
I can't relock, I can't flash new recoverys, can't flash new boot.img and everything I push onto the SDCARD via adb is gone after reboot. If I delete a file that is actually on the SDCARD it will be back after reboot, like it was never really deleted.
I already checked my drivers, switched off Antivir, tried it on a different PC, reinstalled the drivers etc etc.
My HOX is from German o2
I've got HBOOT 0.94.0000 and Radio 1.1204.90.13
If anyone has any suggestions besides "You have to fastboot flash recovery/boot..." and "Don't forget to erase cache after every flash" I'd be very thankfull
Best regards,
Thad
did you try to re-download your fastboot ?
and did you navigate on CMD to the right place where your fastboot folder is stored ?
You need to flash the stock recovery before you relock your bootloader.
Flash stock recovery
Relock bootloader
Install ruu
Hope this helped
EDIT: Just read your post again and you said you've tried flashing recoveries, sorry, its late here
Sent from my HTC One X using xda premium
i made a compilation of threads about this matter, it might help you. check it out..
http://forum.xda-developers.com/show....php?t=1692681
Thanks for all suggestions on the topic
@muamers
I redownloaded fastboot multiple times, but its all the same, sadly The problem is: It seems to work. I get all the right replies on the command prompt, but after rebooting nothing is flashed.
@mikey0105
The link goes to a 404 page - could you post it again?
Thank you
tadeausz said:
Thanks for all suggestions on the topic
@mikey0105
The link goes to a 404 page - could you post it again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1692681
Thank you Gibeon & mikey0105
I retried all the steps there, but still no change.
The problem still is the same. This is what I get in response:
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.044s]
finished. total time: 0.045s
>fastboot flash boot boot.img
sending 'boot' (4156 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.470s]
finished. total time: 1.008s
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.034s
>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
sending 'recovery' (5760 KB)...
OKAY [ 0.829s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.548s]
finished. total time: 1.377s
So everything should've worked out great. But not so, because in reality he really hasn't flashed anything to the HOX permanently. When I reboot to recovery I still have the OLD CWM without fixes. The boot.img isn't flashed either.
As I said: It's like working on a virtual machine, where nothing really has any effects, it's a if all the fastboot commands only affect the RAM but are not really flashed to Memory.
And I still can't relock, still can't reboot-bootloader from Bootloader.
Any other ideas are welcome...
Greetings,
Thad
Bump.
Nobody any more ideas?
Bump. Still no solution after many month
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
robchongke said:
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
tadeausz said:
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
Click to expand...
Click to collapse
are you doing
fastboot flash recovery recovery.img
Or
fastboot boot recovery.img
I'm not sure the second one works, but if it did, it would do what you describe. So do the first.
help
I'm running ICJ ROM AOKP. last time I flashed this rom and flashed the gapps too,
Now I want to install a new package of gapps, SO, do I need to wipe data, cache, dalvic cache to install the gapps ???
Note that I'm going to install ONLY the gapps...
THANKS
aimen7 said:
i'm running icj rom aokp. Last time i flashed this rom and flashed the gapps too,
now i want to install a new package of gapps, so, do i need to wipe data, cache, dalvic cache to install the gapps ???
Note that i'm going to install only the gapps...
Thanks
Click to expand...
Click to collapse
That's the third time I've read this question from you.
STOP POSTING IT NOW!
BenPope said:
That's the third time I've read this question from you.
STOP POSTING IT NOW!
Click to expand...
Click to collapse
sorry, I'm CONFUSED about that
Aimen7 said:
sorry, I'm CONFUSED about that
Click to expand...
Click to collapse
Make 1 new thread or search....don't go posting it in every Q&A thread !
That is confusing ! :thumbdown:
Hi
Last year i was using Android Revolution custom firmware, after which i went back to stock, i stayed with stock about 1 year , then yesterday tried install Android Revolution HD, but i think i mess it up big time because i am stuck in boot screen . I tried looking for a RUU but apparently my phone is using a newer version of RUU which i can not find. I spent 1 day looking for solutions but none helped, now i am stuck. Please help. Sorry for my English , Thank You
give more info : hboot number ? what recovery ? flashed the boot.img ?
Mr Hofs said:
give more info : hboot number ? what recovery ? flashed the boot.img ?
Click to expand...
Click to collapse
version-main: 4.18.401.2, hboot 1.72.000 .recovery-clockwork-touch-5.8.4.0-endeavoru , 5.1204.167.31
. i think i flashed the boot.img , at least one of them, i did a lot of flashing , trying to recover from my mistakes
okey here we go, first flash this recovery (for working touch in recovery)
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
then you flash the boot.img from the rom.zip (copy it again to the fastboot folder and make sure its the correct one)
then enter the recovery and perform a full wipe
- factory reset (full)
- wipe cache partition
- ADVANCED - wipe dalvik cache
- MOUNTS & STORAGE - format cache, data, system
then install the rom.zip and reboot
Mr Hofs said:
okey here we go, first flash this recovery (for working touch in recovery)
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
then you flash the boot.img from the rom.zip (copy it again to the fastboot folder and make sure its the correct one)
then enter the recovery and perform a full wipe
- factory reset (full)
- wipe cache partition
- ADVANCED - wipe dalvik cache
- MOUNTS & STORAGE - format cache, data, system
then install the rom.zip and reboot
Click to expand...
Click to collapse
just waiting to charge a little bit, because i can not flash anymore, As soon as i charge my phone i will fallow you instructions and revert with updates. Thanks
ursache marian said:
just waiting to charge a little bit, because i can not flash anymore, As soon as i charge my phone i will fallow you instructions and revert with updates. Thanks
Click to expand...
Click to collapse
make sure you charge inside the recovery, it does not charge in bootloader or the bootscreen !
Mr Hofs said:
make sure you charge inside the recovery, it does not charge in bootloader or the bootscreen !
Click to expand...
Click to collapse
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.369s
any suggestions ?
I found that batch file in other post , and i just started charging now.
ursache marian said:
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.369s
any suggestions ?
Click to expand...
Click to collapse
yea put your phone in the recovery and hook it up to the main charger !!! and leave it there for 2 hours
Mr Hofs said:
yea put your phone in the recovery and hook it up to the main charger !!! and leave it there for 2 hours
Click to expand...
Click to collapse
I can not access recovery , it's staying only in boot menu , but i found a batch file witch apparently if i run it it will charge the phone for me to be able to flash the recovery that you sent .
Yeah cool. How many mV is it ?
Mr Hofs said:
Yeah cool. How many mV is it ?
Click to expand...
Click to collapse
Managed to charge so i can flash , but no luck
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.172s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.379s.
ursache marian said:
Managed to charge so i can flash , but no luck
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.172s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.379s.
Click to expand...
Click to collapse
remote not allowed indicates a relocked/locked bootloader ! and to be sure rename the recovery to just recovery.img
fastboot flash recovery recovery.img
fastboot erase cache
Mr Hofs said:
remote not allowed indicates a relocked/locked bootloader ! and to be sure rename the recovery to just recovery.img
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
C:\New folder>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.167s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.377s
C:\New folder>fastboot erase cache
erasing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.217s
C:\New folder>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.169s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.378s
unlock the bootloader !
Mr Hofs said:
unlock the bootloader !
Click to expand...
Click to collapse
OK, bootloader unlocked , flashed your recovery, now waiting for it to charge a little bit more. After i do a recovery wipe , i would like to install Android revolution HD, Yesterday i got stuck when i installed android revol HD becouse i couldn't select "next" button, my touch was not working, and using the Up and Down buttons was impossible. Now i see that in this recovery touch is working so maybe i will be able to install this Android HD firmware afterall.
Thank you for you help
ursache marian said:
OK, bootloader unlocked , flashed your recovery, now waiting for it to charge a little bit more. After i do a recovery wipe , i would like to install Android revolution HD, Yesterday i got stuck when i installed android revol HD becouse i couldn't select "next" button, my touch was not working, and using the Up and Down buttons was impossible. Now i see that in this recovery touch is working so maybe i will be able to install this Android HD firmware afterall.
Thank you for you help
Click to expand...
Click to collapse
no problem, let me know the result
Mr Hofs said:
no problem, let me know the result
Click to expand...
Click to collapse
i managed to flash boot and flash android hd 31.3 with your recovery.img, on mine the touch was not working . Thank you again.
Okidoki !
CASE CLOSED !
Hi guys, I would like to ask for a help. I was on New Layout (SlimKat 9.0). I wanted to try something at Old Layout ROM, so like a stupid I wiped everything (cache, data and system thru recovery), then I flashed fastboot flash boot boot.emmc.win (Old Layout Backup) and Old Layout TWRP.
But after that, I can't access recovery (I only see picture of TWRP for 1 second, then it reboots with bootloop). So I flashed New Layout TWRP again together with fastboot flash boot boot.emmc.win (I got backups from Old & New Layout).
Then I tried
fastboot flash boot boot.emmc.win
fastboot flash system system.ext4.win
fastboot erase cache
but nothing helps. I am simply without ROM and accessible recovery. Anybody has idea what to do please? Thx a lot!
lesmil said:
Hi guys, I would like to ask for a help. I was on New Layout (SlimKat 9.0). I wanted to try something at Old Layout ROM, so like a stupid I wiped everything (cache, data and system thru recovery), then I flashed fastboot flash boot boot.emmc.win (Old Layout Backup) and Old Layout TWRP.
But after that, I can't access recovery (I only see picture of TWRP for 1 second, then it reboots with bootloop). So I flashed New Layout TWRP again together with fastboot flash boot boot.emmc.win (I got backups from Old & New Layout).
Then I tried
fastboot flash boot boot.emmc.win
fastboot flash system system.ext4.win
fastboot erase cache
but nothing helps. I am simply without ROM and accessible recovery. Anybody has idea what to do please? Thx a lot!
Click to expand...
Click to collapse
Download this guide and follow it. It should get you back to old layout.
How do I get back to the Old Layout?
Guide on Going Back to Normal Layout
Updated link to old recovery.
teemo said:
Download this guide and follow it. It should get you back to old layout.
How do I get back to the Old Layout?
Guide on Going Back to Normal Layout
Click to expand...
Click to collapse
Thx for reply teemo. Already tried that. Still getting bootloop (blue image of TWRP appears for 1 second, then it reboots). Battery was fully charged (green LED). Even got this result from CMD:
C:\fastboot>fastboot flash boot boot.emmc.win
sending 'boot' (8192 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.675s]
finished. total time: 1.910s
C:\fastboot>fastboot flash recovery twrp-recovery-hox-2.8.1.0.img
sending 'recovery' (7720 KB)...
OKAY [ 1.136s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.623s]
finished. total time: 1.761s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.222s]
finished. total time: 0.223s
No idea what to do now
lesmil said:
Thx for reply teemo. Already tried that. Still getting bootloop (blue image of TWRP appears for 1 second, then it reboots). Battery was fully charged (green LED). Even got this result from CMD:
C:\fastboot>fastboot flash boot boot.emmc.win
sending 'boot' (8192 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.675s]
finished. total time: 1.910s
C:\fastboot>fastboot flash recovery twrp-recovery-hox-2.8.1.0.img
sending 'recovery' (7720 KB)...
OKAY [ 1.136s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.623s]
finished. total time: 1.761s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.222s]
finished. total time: 0.223s
No idea what to do now
Click to expand...
Click to collapse
Can you boot to recovery ?
teemo said:
Can you boot to recovery ?
Click to expand...
Click to collapse
Nope. I wish I could. I only see TWRP blue image for 1 second or so, then it goes to bootloop.
Did you try the famous:
fastboot erase cache ?
teemo said:
Did you try the famous:
fastboot erase cache ?
Click to expand...
Click to collapse
Sure I even pasted it in post I never forget to do this.
lesmil said:
Sure I even pasted it in post I never forget to do this.
Click to expand...
Click to collapse
Hmm everything look right.
Could you try the recovery from my link.
teemo said:
Hmm everything look right.
Could you try the recovery from my link.
Click to expand...
Click to collapse
The file was not found But I got this version of TWRP (from you) stored on external hdd as a backup, and on my D partition. It's still the same. Bootloop. I wish I could transfer some ROM zip to sdcard and install it lol.
lesmil said:
The file was not found But I got this version of TWRP (from you) stored on external hdd as a backup, and on my D partition. It's still the same. Bootloop. I wish I could transfer some ROM zip to sdcard and install it lol.
Click to expand...
Click to collapse
No not the link from the guide. The link I posted in post #2. Download and flash.
teemo said:
No not the link from the guide. The link I posted in post #2. Download and flash.
Click to expand...
Click to collapse
Still the same result :/
C:\fastboot>fastboot flash recovery twrp2810-HOX.img
sending 'recovery' (7720 KB)...
OKAY [ 1.157s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.638s]
finished. total time: 1.798s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.221s]
finished. total time: 0.223s
try this may help
also try adb push commands
dado323 said:
try this may help
also try adb push commands
Click to expand...
Click to collapse
Thx, but no progress :S
u can try one x click to install recovery ,like long time ago i **** everthing on my phone ,i didnt have anything on my phone so i use Philz 5.15.9 the SD card mount function work only on that recovery that was like 2 years ago
dado323 said:
u can try one x click to install recovery ,like long time ago i **** everthing on my phone ,i didnt have anything on my phone so i use Philz 5.15.9 the SD card mount function work only on that recovery that was like 2 years ago
Click to expand...
Click to collapse
I tried to flash every recovery now via One X click by now, no success to enter recovery. Always 1 second "blink" and reboot. No idea, maybe time for bed now lol
OH YEAH, at least managed CWM 6.0.4.8 WOHOO At least some progress... ^^
good luck
dado323 said:
good luck
Click to expand...
Click to collapse
Thx but I am stuck again lmao. As I was on New Layout, UMS doesn't work. Sideload - same. omg. Will do it tomorrow. But weird thing is, that only latest CWM and philz touch 6.19.3 were able to be installed.
After this, TWRP 2.8.1.0 installed. Everything's going to normal. Thanks both of u guys
. . I have an old One X here, unused for a looong time. Recently I tried to update it and started the process by updating my Recovery (to TWRP 2.6.3.0). Soon after that I found out that most new ROMs have a new partitioning schema and I needed to switch. When trying to update the recovery, I used the fastboot flash and it went ok:
Code:
$ ./fastboot flash recovery /d/twrp2853-BiG.img
sending 'recovery' (8090 KB)...
OKAY [1.134s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [0.687s]
finished. total time: 1.820s
. . After that I did the "fastboot erase cache":
Code:
$ ./fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.213s]
finished. total time: 0.213s
. . Then I rebooted into recovery directly--I know about ROMs that flash the stock recovery when first booting, but this is not applicable to this case since I'm in a custom ROM and booting directly to recovery--, but it is still the old recovery (2.6.3.0). I tried flashing older recoveries (2.6.1.0) and repeating the process every way I could think of (more "erase caches", more "flash recovery"ies etc) but I'm stuck in this 2.6.3.0 version. The weird thing is that I flashed this version yesterday and it went all smoothly, no problems at all (flash recovery, erase cache, reboot).
. . Any tips or ideas why it is not working anymore? I want to update it to change to the new layout so I can flash new ROMs, but this it really blocking the process.
Did you try to wipe your HOX including /data as well as /system partition? This - in the guide if how to achieve new storage layout - is one of the important prerequisites and done prior to flashing the TWRP.BIG
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
dsnunes said:
. . I have an old One X here, unused for a looong time. Recently I tried to update it and started the process by updating my Recovery (to TWRP 2.6.3.0). Soon after that I found out that most new ROMs have a new partitioning schema and I needed to switch. When trying to update the recovery, I used the fastboot flash and it went ok:
Code:
$ ./fastboot flash recovery /d/twrp2853-BiG.img
sending 'recovery' (8090 KB)...
OKAY [1.134s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [0.687s]
finished. total time: 1.820s
. . After that I did the "fastboot erase cache":
Code:
$ ./fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.213s]
finished. total time: 0.213s
. . Then I rebooted into recovery directly--I know about ROMs that flash the stock recovery when first booting, but this is not applicable to this case since I'm in a custom ROM and booting directly to recovery--, but it is still the old recovery (2.6.3.0). I tried flashing older recoveries (2.6.1.0) and repeating the process every way I could think of (more "erase caches", more "flash recovery"ies etc) but I'm stuck in this 2.6.3.0 version. The weird thing is that I flashed this version yesterday and it went all smoothly, no problems at all (flash recovery, erase cache, reboot).
. . Any tips or ideas why it is not working anymore? I want to update it to change to the new layout so I can flash new ROMs, but this it really blocking the process.
Click to expand...
Click to collapse
I use this program and it works well. http://we.tl/8gYJ8tgcer