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 !!!
Related
hi, I recently rooted my one x and had it been working perfectly, until... I flashed cm9 wit galxy s3 addon pack which works well, but now I cannot boot into recovery to restore my nandroid or change roms.
basicly when I try to boot into recovery it flashes with some script with the rommanager logo then boots into cm9
so could you kind folks either suggest how to get into recovery, or tell me how to flash a rom on my sd card or my nandroid through fastboot thanks!
any help would be much appreciated!
dobbo30 said:
hi, I recently rooted my one x and had it been working perfectly, until... I flashed cm9 wit galxy s3 addon pack which works well, but now I cannot boot into recovery to restore my nandroid or change roms.
basicly when I try to boot into recovery it flashes with some script with the rommanager logo then boots into cm9
so could you kind folks either suggest how to get into recovery, or tell me how to flash a rom on my sd card or my nandroid through fastboot thanks!
any help would be much appreciated!
Click to expand...
Click to collapse
I guess your first option should be to flash the RECOVERY again through fastboot and also erase cache. Then try to get into recovery again. Maybe you can also try the app called "quickboot" from the market and try to get to recovery from there.
So first go to fastboot and
1) fastboot flash recovery "name of recovery".img
2) fastboot erase cache
and then WITHOUT booting the rom try to get to recovery through bootloader
Hi guys, first time poster here, hope i've got the right sub-forum.
So i've ran into some issues whilst attempting to flash the maXimus v2.2 custom rom to my HOX. Here's what i've done so far:
Unlocked bootloader via HTCdev
Installed Clockwork Mod + SuperSU
Created a Backup using Nandorid, as well as a Titanium apps backup.
I then attempted to flash to maXimus v2.2 by doing the following:
Copy ROM zip file onto HOX
Boot into Clockwork Mod Recovery
wipe data factory reset
wipe dalvik cash
Install zip from SD card
All seemed to go okay, but i'm now stuck in a boot loop. I think the problem is that I didn't copy boot.img to my phone before the flashing process, as I was over-reliant on the tut I was using and it didn't mention this.
to rectify the situation, i've tried rebooting into bootloader and sending the fastboot erase cache and fastboot reboot-bootloader commands, but still stuck in the bootloop.
My question is two part - firstly, how do I escape this situation? Secondly, when I go to reflash my HOX, where do I get the boot.img file from?
Thanks in advance, i've tried to be as detailed as possible but this is my first time flashing a custom ROM so if I missed anything out please let me know!
loz_the_guru said:
Hi guys, first time poster here, hope i've got the right sub-forum.
So i've ran into some issues whilst attempting to flash the maXimus v2.2 custom rom to my HOX. Here's what i've done so far:
Unlocked bootloader via HTCdev
Installed Clockwork Mod + SuperSU
Created a Backup using Nandorid, as well as a Titanium apps backup.
I then attempted to flash to maXimus v2.2 by doing the following:
Copy ROM zip file onto HOX
Boot into Clockwork Mod Recovery
wipe data factory reset
wipe dalvik cash
Install zip from SD card
All seemed to go okay, but i'm now stuck in a boot loop. I think the problem is that I didn't copy boot.img to my phone before the flashing process, as I was over-reliant on the tut I was using and it didn't mention this.
to rectify the situation, i've tried rebooting into bootloader and sending the fastboot erase cache and fastboot reboot-bootloader commands, but still stuck in the bootloop.
My question is two part - firstly, how do I escape this situation? Secondly, when I go to reflash my HOX, where do I get the boot.img file from?
Thanks in advance, i've tried to be as detailed as possible but this is my first time flashing a custom ROM so if I missed anything out please let me know!
Click to expand...
Click to collapse
Enter to HBOOT in the Bootloader
Unzip the Android_Fastboot KIT V2.2.zip and run the Install Boot.img.bat after you get OK, Reboot your HOX and it will not be in bootloop
Hero! All sorted now, many thanks!
Quick question - do I have to run install boot.img.bat every time I flash, or is my phone now good to just go via install Zip from SD card each time?
flash everytime until we are s-off
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
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
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader