How did you guys install TWRP again? - Sony Xperia M

I'm on stock 4.3 and decided to flash a custom ROM again on this phone. But.. I can't find a recovery for this device on stock anymore. I can't download CWM recovery for stock (just kept popping up with ads and never downloading the recovery file :/ ). So I went ahead and downloaded the RR ROM and extracted the boot.img out of it and flashed it in and boot into the Android Recovery (was expecting at CM recovery tho, it just says "Android Recovery" at the top left corner). Thought I could install the ROM from there, but no :
-- Install /storage/6FCB-1A04/<theROM>.zip
Finding update package...
Opening update package...
E: failed to map file
E: Error exit from the fuse process : 0
Installation aborted.
Also, there's a periodic spam of " E: failed to find /misc partition"
Idk where else I haven't search, I even tried fastboot flash boot twrp.img
That booted into recovery but the touch isn't working somehow. What did you guys do?

fml
For anyone having troubles with recovery on stock : https://forum.xda-developers.com/showpost.php?p=51410401

Related

Issue with clockworkmod...

Hi...
Yesterday i've installed cwm 3.x.x.x and flashed cm nightly build #18. Today i've downgraded the cwm cause i couldn't get any connection to my dhd with the neew recovery (fastboot commands just came back with an error i can't remember atm). The downgrade was flashed through terminal emu, code:flash_image recovery /sdcard/clockwork-recovery2.1.5.3.img and went fine. I then changed the splashscreen through fastboot as i have before and no problem here. Then i desided to make my own splash in gimp and when i tried to flash that it failed and wouldn't write and now i have this error in cwm:
E:can't mount cache:recovery/command
E:can't mount cache:recovery/log
E:can't open cache:recovery/log
I've tried to flash back to cwm 3.x.x.x through terminal emu and then use rom manager to flash 2.1.5.3, but still same issue when booting into cwm and still a fail when trying to flash splashscreen (and yes the cwm changes beween flashes in terminal, green 2.1.5.3, orange 3.x.x.x)
Is it because off cm7 build #18 that i can't use cwm 2.1.5.3 to flash through fastboot.
I havn't tried another rom like leedroid to see if that changes, i'm a tad afraid that it won't wipe nor flash cause of this error and hence brick my phone.
I've got a nandroid from the beginning of this month, but thats a cwm 2.1.5.3 backup, can that be restored in cwm 3.x.x.x?
Ohh cuold it be that i've morphed some icons plus FM radio skin?
Any help is welcome
TIA Dousan... Aka Martin...
e:the error i get when flashing splash1 with fastboot:
writing 'splash1'... FAILED (remote: image update error)
e2: Fixed the splash1 error - image had the wrong dimensions... :S
Dousan said:
Hi...
Yesterday i've installed cwm 3.x.x.x and flashed cm nightly build #18. Today i've downgraded the cwm cause i couldn't get any connection to my dhd with the neew recovery (fastboot commands just came back with an error i can't remember atm). The downgrade was flashed through terminal emu, code:flash_image recovery /sdcard/clockwork-recovery2.1.5.3.img and went fine. I then changed the splashscreen through fastboot as i have before and no problem here. Then i desided to make my own splash in gimp and when i tried to flash that it failed and wouldn't write and now i have this error in cwm:
E:can't mount cache:recovery/command
E:can't mount cache:recovery/log
E:can't open cache:recovery/log
I've tried to flash back to cwm 3.x.x.x through terminal emu and then use rom manager to flash 2.1.5.3, but still same issue when booting into cwm and still a fail when trying to flash splashscreen (and yes the cwm changes beween flashes in terminal, green 2.1.5.3, orange 3.x.x.x)
Is it because off cm7 build #18 that i can't use cwm 2.1.5.3 to flash through fastboot.
I havn't tried another rom like leedroid to see if that changes, i'm a tad afraid that it won't wipe nor flash cause of this error and hence brick my phone.
I've got a nandroid from the beginning of this month, but thats a cwm 2.1.5.3 backup, can that be restored in cwm 3.x.x.x?
Ohh cuold it be that i've morphed some icons plus FM radio skin?
Any help is welcome
TIA Dousan... Aka Martin...
e:the error i get when flashing splash1 with cwm 2.1.5.3:
writing 'splash1'... FAILED (remote: image update error)
Click to expand...
Click to collapse
CWM 2.x cannot access ext4 partitions, so whilst you've got gingerbread on there it will throw up all kinds of errors, you should be good to restore a cwm 2.x backup with cwm 3.x but you will have problems restoring the whole backup as cwm 3.x can't write /boot at present
ghostofcain said:
CWM 2.x cannot access ext4 partitions, so whilst you've got gingerbread on there it will throw up all kinds of errors, you should be good to restore a cwm 2.x backup with cwm 3.x but you will have problems restoring the whole backup as cwm 3.x can't write /boot at present
Click to expand...
Click to collapse
Cheers mate, thanks for the answer... Had a feeling it might be something with the new ext4...
Just weird i could flash one splashscreen today after reverting to cwm 2.1.5.3?
Will stay with the new CM7 builds, really nice and smooth
Anyway was just afraid of bricking the phone if did have to restore a nandroid.
So it's the same story with the fastboot commands or what, not working with ext4?
Dousan said:
So it's the same story with the fastboot commands or what, not working with ext4?
Click to expand...
Click to collapse
shouldn't think so, certainly fastboot is working fine for me on cm7
Lol, noob me i was trying to flash a corrupt splashscreen (not the right dimensions) all fixed and the fastboot commands works for me aswell
Back on track... Thanks again for your help

ROM Manager/Recovery signed zip problem!

Hello ... I ask you a little help on ROM and Recovery Manager.
I just root the galaxy S2 with the procedure supercurio, so my ROM is basically stock ... I was a XWKDD.
ROM Manager (in his opinion) regularly install ClockworkMod 4.0.0.2, but when I restart in recovery and launch the update.zip I get the following error message:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Googling a little I found how to sign files .zip and also modded 3e recovery to ignore the signs ... but none of these workarounds work ...
So how I can use 3e recovery with unsigned files?
Or ... how can I replace the 3e with the 2e recovery? (There ROM with the 2e, which do not differ much from the stock ROM?)
if you have CWM 4.0.0.2 toggle signature verification to OFF

[Q] Not able to update my HOX to 4.18.401.2

Hi all,
Today my phone notified me there was an update available for my device, 4.18.401.2, which included stuff like Android 4.2.2 and Sense 5. I went ahead and downloaded it and my phone prompted me to install it. I hit the button and the phone rebooted, but to my surprise it went into CWM and came up with the following error:
Finding update package...
E: unknown volume for path [INTERNALSDCARDownload/OTA_ENDEAVOR_U_JB_50_S_HTC_Europe_4.18.401.2-3.20.401.1_release_3302999mwn06o7zbi85sv7.zip]
E: Can't mount INTERNALSDCARDownload/OTA_ENDEAVOR_U_JB_50_S_HTC_Europe_4.18.401.2-3.20.401.1_release_3302999mwn06o7zbi85sv7.zip
Installation aborted.
So, I tried to manually install the .zip in CWM:
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
> Install untrusted package? > Yes
Installing update...
assert failed: check_cid(getprop("ro.cid"), <bunch of 0000000001111111111122222222222222333333333333334444444444444" and CID's> == "t"
E: error in OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.3-3.20.401.1_release_31823765m022e6p4w085de.zip (Status 7)
Installation aborted.
On some website I read this:
Just make sure your phone already runs with 3.20.401.3, likely if you are still on 3.20.401.1 you might encounters install error via CWM custom recovery. Install this first.
(sorry, can't post URL here because I don't have 10 posts yet.)
Click to expand...
Click to collapse
So I went ahead to try and install that using CWM too:
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
I really don't know what to do now...
You need to flash stock recovery
Sent from my HTC One X
n1kos said:
You need to flash stock recovery
Sent from my HTC One X
Click to expand...
Click to collapse
I will flash stock recoveries tomorrow, thanks for your quick reply.
Hi,
I have exactly the same problem, and I have been searching on how to install a stock recovery, however there are loads of versions and I cant figure out which one to use. Can anyone point me to a complete idiots guide as to identift how to do this?
Many Thanks,
-,-
Great, today I flashed the stock recovery and tried to install the update and the phone just COMPLETELY wiped itself. Even the SD-card...
How is this possible?
Willemnz said:
Great, today I flashed the stock recovery and tried to install the update and the phone just COMPLETELY wiped itself. Even the SD-card...
How is this possible?
Click to expand...
Click to collapse
When I upgraded to 4.2.2 everything was wiped too.
1) It DOES warn you that you may lose ALL DATA, including SD. READ the install notes. They are there for a reason.
2) On that basis I backed up everything. Hope you did.

Jacked up Phone

Ok so I cannot figure out what I did to my phone. I have s-off and my phone was rooted with TWRP Custom Recovery. I do not know why I did this but I installed the CWM app and installed the newest CWN recovery for the HTC One. I rebooted into CWM and tried wiping data. It got stuck on that so I rebooted and it gets stuck on the HTC boot up screen. When I go back into the bootloader and try installing the TWRP recovery using fastboot flash recovery recovery.img it gives me a remote: not allowed. When I do fastboot oem lock it says phone is already locked. I then do fastboot oem rebootruu and I get (bootloader) [err] command error!!! When I try rebooting into cwm I just get E: can't mount /cache/recover/commad, E: can't mount /cache/recovery/log and a bunch of other e: cant mount and open errors. Not sure how to get my phone to install the TWRP recovery and get a custom rom back on there. Anyone have any solutions?
slaz13 said:
Ok so I cannot figure out what I did to my phone. I have s-off and my phone was rooted with TWRP Custom Recovery. I do not know why I did this but I installed the CWM app and installed the newest CWN recovery for the HTC One. I rebooted into CWM and tried wiping data. It got stuck on that so I rebooted and it gets stuck on the HTC boot up screen. When I go back into the bootloader and try installing the TWRP recovery using fastboot flash recovery recovery.img it gives me a remote: not allowed. When I do fastboot oem lock it says phone is already locked. I then do fastboot oem rebootruu and I get (bootloader) [err] command error!!! When I try rebooting into cwm I just get E: can't mount /cache/recover/commad, E: can't mount /cache/recovery/log and a bunch of other e: cant mount and open errors. Not sure how to get my phone to install the TWRP recovery and get a custom rom back on there. Anyone have any solutions?
Click to expand...
Click to collapse
Isn't it "fastboot oem reboot ruu" ?
Its
fastboot oem rebootRUU
Are you still s-off?
Sorry guys I actually some how got everything working again. Thanks!!

Can't apply updates, Status 7 error

Hi all!
I'm in a big trouble. Recently I bricked my M8s, and I had to get back to stock. Unfortunately, RUU for my phone didn't work (constant htc_fastboot crashes during the process), and trying to flash zip from bootloader ended in "Device halted due to Large Image update fail!" error, so I had to flash the raw system.img image to the /system partition in twrp. The OS eventually booted up but now I'm unable to apply any system upgrade! While installing downloaded update in recovery I get this error:
Code:
Verifying current system...
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
The same thing happens when I try to apply update from OTA package provided by mr Lalleman.
I don't know anymore what to do, can someone help?

Categories

Resources