I have been using Cyanogenmod 11 version along with CWM recovery for some time. Recently I installed a theme which crapped on my wifi settings (simple but irritating problem) which I couldn't fix it any which way. Long story short, I tried to install a new boot.img and ended up "soft bricking" my phone. I feel terrible on doing so, since honestly I loved the mods!!
Since the recovery I already had (CWM) wasn't helping me, I tried to flash a new recovery (TWRP) into the phone. After flashing (which worked), when I went to recovery mode, the touch screen nor the volume buttons were working in TWRP. Got frustrated and I tried to flash the old CWM recovery and it keeps giving me this error:
"writing recovery...
<bootloader> Formatting partition SOS done
Failed: <remote:err = 0xa>"
So, Things that are working in my phone are: Fastboot
Things that aren't working in my phone are: adb, not able to flash the recovery with fastboot, boot of course isn't happening..
Ideally I am planning to flash a new recovery and somehow copy a new boot.img and flash the same. Please help. If you feel this problem has already been discussed, you could just pass me on there.
PS: I have already tried solving this by looking at replies from many such forums...
Got it fixed!!
Somehow got PhilZ recovery installed and from then on, it was easy sailing!! I realized that the img should be less than 8MB. Not sure why but it is, what it is. :victory:
Related
Hi everyone,
I just got my G Pro a couple days ago. I've been trying to read up as much as I can on the phone. I bought the phone used. It's on the V10k firmware (value pack or whatever they call it) and it was rooted, but I never did check to see if it had a custom recovery installed. Now, I installed FreeGee from the Play Store and had it flash TWRP 2.6.1. Installed successfully. But, when I reboot the phone, and I push a button to enter recovery mode, it takes me to CWM 6.0.2.8 by 985hPaKick v1. To top it off, if I "reboot recovery" from within CWM, or if I use "adb reboot recovery," it'll take me to TWRP. Anybody have a clue what's happening, or is this normal and I'm just not hip to it yet? I would've figured that if CWM was on here originally and I didn't know it, flashing TWRP would've just overwritten CWM. I'd like to be able to flash custom ROMs and such but I've never had this occur to me with an Android before, and I'm not trying to brick this thing. Any help and guidance would be greatly appreciated. Thank you!
Im new to the LG world also. I dont know how this happened but if you flash back to stock via LG flash tool then reroot. You can Freegee a recovery over the stock one just reflashed. When I flashed the TWRP recovery the touch screen was dead(when in recovery mode) so I reflahed CWM over it with Freegee and it worked. Hope this helps
Thanks bud, I'll give it a try.
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.
It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help
Hey guys, I just recently got some parts for my old One X to start playing with it again (bored with ios). I was running an older version of ViperXL and wanted to get lollipop so my goal was to put CM12.0 on my phone. My recovery was twrp but a version that was older so I had to update it. The in app update wasn't working so I updated cwm instead. When I did this I tried to boot to recovery and it would attempt to go to recovery but then boot back to the os.
Then I was trying to flash the recovery using fastboot which resulted in the same problem. Somewhere in there I flash the recovery.img as my boot image (sudo fastboot flash boot recovery.img) This made my phone repeatedly try to boot into recovery. I tried flashing new ViperXL boot.img as well as a couple others but none let me get into my os again. Now it is just a bootloop trying to start my phone up.
When I try flashing a .zip I get the error 'FAILED (remote: not allowed)'. Flashing recovery and boot images work though.
I've tried a lot and done a lot of searching but nothing can get me into recovery or even out of any sort of bootloop.
I'm using Ubuntu and my phone is S-On if that means anything.
Thanks!
Try restoring any backups of old roms from the recovery. Make sure Recovery is written properly in recovery partition. If this works fine , the appropriate boot.img shud be automatically flashed , i guess.
If u dont have a backup , try finding another one x user using a custom recovery, create a backup from his mobile and copy it to ur sd card by mounting it thru recovery and restore it.
If it doesnt work , wipe all the partitions - System , cache, boot and recovery.. then try flashing a Recovery and then a Boot.img and a rom.
I havent faced such a situation. Just my suggestions as no experts have responded.
Cheers if u have already sorted it out !!!
Dear All,
Here's the problem:
The Goal: To Install CM-12.1 Custom ROM
What I have done:
1. Installed TWRP Recovery Manager and no matter how many times I tried, was unable to install TWRP Recovery
2. Installed Flashify, not possible to install TWRP, CWM or any other recovery!
3. Installed Rashr and finally was able to get PhilZ Touch 6 Recovery installed on the phone.
Rebooted to recovery and it's working! Great!
Now, I have the CM-12.1 zip file on the external SD card but can't flash the ROM no matter how many times I try. Yes, I did wipe factory reset and all the wipes possible, NOT ABLE TO INSTALL the Custom ROM.
The real problem now is that before I tried installing the custom ROM, I accidentally made a mistake, a really bad one too.
When my phone was starting normally, in Flashify (or Rashr, I don't remember now) I selected the downloaded TWRP recovery image for Kernel and rebooted the phone. Yes, a dumb move, I know, but for some stupid reason I did that! And now the phone won't start!!!
Getting this msg:
Set Warranty Bit: kernel
Plus, when I boot into Philz Touch 6 recovery, not able to install ROM or do anything else either.
I managed to install Aroma File Manager, and deleted some of the twrp recovery images, but still getting the kernel error.
Also, in Philz Touch recovery, I have done something wrong and I think I may have lost ROOT access. Tried several times to Re-Root Super SU but it says now install Super SU from the Market. How can I install Super SU from market if I cannot get the phone to start in the first place.
Anyway, if anyone knows how to fix these issues or has experienced similar problems, please share the steps you took to solve the problem.
All the help is appreciated!
Thanks vey much in advance!!!
P.S. Please write in comments if any screen capture is needed.
BOOTLOOP!
If anyone can, please help, I can't use my phone for over a week now!!!
the phone is stuck in bootloop!
the recovery I was using apparently wasn't the right version for my gt-i9192 and for some stupid reason it thought that my phone is gt-i9190!!! i was using twrp 3.0.0.0 serrano3gxx by the way. and i could not install the custom rom, the right rom for gt-i9192... because the recovery thinks my phone is gt-i9190... stupid right
so i installed openrecovery-twrp-2.8.7.0-serranodsxx-STABLE-signed zip file using the twrp recovery itself. and now i can't even go to recoery mode!!! WOW!! I think i ****ed up this phone big time!!!
i know there was a warning to not install the recovery using the recovery itself, but i didn't have a choice.
i did that because Odin is not working for my phone!! can't install anything with odin...
it just gets stuck and never finishes the flash. can't install anything with odin, nothing at all. just gets stuck!!
so now the problem is this stupid bootloop and on top of that i can't even get the phone to start the recovery, when I try, it goes back to this bootloop problem. by the way this is the bootloop msg:
Set Warranty Bit : kernel IN YELLOW COLOUR and the phone logo: Samsung Galaxy S4 mini GT-I9192
Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?
Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img