Hi,
XT1527 surnia_retca_cus 2016-11-18
this phone doesn't seem to allow flashing a custom recovery (fastboot flash went ok but still boots into stock no matter what). Fastboot boot with twrp image didn't work either (stuck on splash screen)
I now tried flashing a stock rom but couldn't find exact same model. Phone is now bricked (flashing gpt.img fails).
Any suggestions? Thanks
Foldback said:
Hi,
XT1527 surnia_retca_cus 2016-11-18
this phone doesn't seem to allow flashing a custom recovery (fastboot flash went ok but still boots into stock no matter what). Fastboot boot with twrp image didn't work either (stuck on splash screen)
I now tried flashing a stock rom but couldn't find exact same model. Phone is now bricked (flashing gpt.img fails).
Any suggestions? Thanks
Click to expand...
Click to collapse
Flash the twrp and the boot into it and allow modification to keep twrp then flash any custom rom
riyan65 said:
Flash the twrp and the boot into it and allow modification to keep twrp then flash any custom rom
Click to expand...
Click to collapse
Ok, I managed to flash both the twrp.img and the boot.img from a "surnia_retca...similar but not same...cid14" onto it but it still fails to start twrp, saying as before "Error: failed to load kernel! Boot up failed".
Foldback said:
Ok, I managed to flash both the twrp.img and the boot.img from a "surnia_retca...similar but not same...cid14" onto it but it still fails to start twrp, saying as before "Error: failed to load kernel! Boot up failed".
Click to expand...
Click to collapse
Are you on stock rom or custom???
If on stock you need to flash the firmware again, if on custom just flash the custom ROM again, it will fix your problem.
riyan65 said:
Are you on stock rom or custom???
If on stock you need to flash the firmware again, if on custom just flash the custom ROM again, it will fix your problem.
Click to expand...
Click to collapse
I originally only had the stock rom, which would not go into twrp as recovery after flashing (going into stock recovery instead).
I did not back up this stock rom and tried a similar, but slightly older one (XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip) which failed the gpt stage of flashing and after that the stock was gone.
It now only has the bootloader working, with the above problems.
Foldback said:
I originally only had the stock rom, which would not go into twrp as recovery after flashing (going into stock recovery instead).
I did not back up this stock rom and tried a similar, but slightly older one (XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip) which failed the gpt stage of flashing and after that the stock was gone.
It now only has the bootloader working, with the above problems.
Click to expand...
Click to collapse
You were lucky as your device didn't get hard Bricked, if you flash a older firmware then the device has, then it going to hard brick and you won't get bootloader too. So it just a paperweight.
If you want to flash stock rom then flash the ROM by removing the gpt and bootloader command, if any error occurs keep going and then reboot the device. Your device will work.
That worked, thanks very much! Using the XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip, it gave an error for the mfastboot erase customize line, but then booted into Android and stock recovery was back as well.
I am now back to the problem of getting the device to run the twrp recovery. It flashes OK but gives "Error: failed to load kernel! Boot up failed" when rebooting and going into Recovery from bootloader. Stock recovery is gone after this new attempt. What's going wrong? I am using twrp-3.3.1-0-condor.img
Foldback said:
That worked, thanks very much! Using the XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip, it gave an error for the mfastboot erase customize line, but then booted into Android and stock recovery was back as well.
I am now back to the problem of getting the device to run the twrp recovery. It flashes OK but gives "Error: failed to load kernel! Boot up failed" when rebooting and going into Recovery from bootloader. Stock recovery is gone after this new attempt. What's going wrong? I am using twrp-3.3.1-0-condor.img
Click to expand...
Click to collapse
Your using different twrp for different devices which cause the issue of kernal. Flash this twrp and it going to work.
https://twrp.me/motorola/motorolamotoelte.html
riyan65 said:
Your using different twrp for different devices which cause the issue of kernal. Flash this twrp and it going to work.
https://twrp.me/motorola/motorolamotoelte.html
Click to expand...
Click to collapse
You're a star! Surnia twrp is working. When I started I didn't know about the different Moto E's (I was looking at the /e/ fork of LineageOS for Moto E, and they officially only list condor). Hence I only tried condor...
Luckily there is an unofficial /e/ build for surnia. This installed successfully by adb sideload. Mission accomplished, thanks again for your help!
PS.
Check out https://doc.e.foundation/what-s-e
it's a very good idea.
Related
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.
So I am stuck on TWRP 2.7.1.0 and i am running slimrom 4.4.4 on a c6833 and the reason for this is because it's the only thing that will boot on my phone. There was some intense trial and error a few months ago and a few days with a bricked phone but I finally got it running again, and I am nervous about messing things up again.
I am wanting to move to a more up to date ROM either scrubber port 5.1 or remix 5.1.1, but they both ask for updated TWRP to install. And I can't update TWRP using the TWRP tool from the store. It downloads but when it tries to install it says there is a problem. Previously, trying to update TWRP would result in SONY bootloops. I was about to try the dd method but just wanted to make sure it was safe.
I am a bit of an idiot (I got rid of my encrypted keys on day 2 of owning the phone) so any help would be appreciated.
Thanks!
walkingagh said:
...
Click to expand...
Click to collapse
The easiest way is to use Rashr. It should set everything up automatically. You may then reboot to recovery from the ROM, or by holding Vol- when the LED turns purple on boot-up.
If that doesn't work, for whatever reason, try dd or Flashtool. Using Flashtool, you can flash openrecovery-twrp-2.8.5.0-togari.img with the phone in Fastboot mode.
Let me know if you have any further questions!
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
So Rashr still says I have 2.7.1.0 installed. :/
walkingagh said:
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
Click to expand...
Click to collapse
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Awesome thanks! Will I need to do this each time I flash a ROM? Or can I just jump from something like scrubber to something else?
I know this is an old thread but is that the boot image I need to run TWRP 3? If so, can I do this via dd?
Triflot said:
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Click to expand...
Click to collapse
That file has expired, any chance you can re-post it?
Hello guys
Today I had to change the simcard in my phone (rooted OOS with blues Park kernel) and after that the phone wouldn't boot up - bootloop. Then I tried flashing the stock rom through TWRP and I got the message "encryption unsuccessful" and couldn't pass through that screen. I've tried flashing purity rom (available in G+) and it won't boot either. I still can boot up to TWRP and fastboot, any solution?
Thanks in advance
if encryption is unsuccessful, first flash oos full zip ,then flash oos recovery via fastboot, do a factory reset via oos recovery. You will be able to boot but all internal storage data will be gone.
saurabh40629 said:
if encryption is unsuccessful, first flash oos full zip ,then flash oos recovery via fastboot, do a factory reset via oos recovery. You will be able to boot but all internal storage data will be gone.
Click to expand...
Click to collapse
Thanks a lot, I'll try with that. Btw do you know where can I get the stock recovery to flash via fastboot?
matapr0 said:
Thanks a lot, I'll try with that. Btw do you know where can I get the stock recovery to flash via fastboot?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?pref=2&pli=1
ExtremeNuker said:
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?pref=2&pli=1
Click to expand...
Click to collapse
thank you guys but it won't let me flash the stock recovery via fastboot. The last line I get is:
FAILED (remote: device not unlocked cannot flash or erase)
I can't also unlock the bootloader as it can be done only with the stock recovery... what a mess :crying:
Any other suggestion?
I'm not sure but You can try to flash stock recovery via .zip file. It is for flashify app so i don't know if it can be flahed with TWRP.
here it is: http://www.filedropper.com/oneplusxstockrecoveryflashify
But i think You should try to flash full stock rom and see if Your phone will boot
here is the link: https://mega.nz/#!VssWCQba!QI_nF22jllVMbCNz5tc38roGdVninSwX34mzJ8PtUSk
hello, not sure what's going on here but I can't boot normally (it just stays on the OnePlus logo)
can't boot to recovery either, still just the logo. (vol down & power)
I have fastboot, and tried to flash a genuine twrp recovery... http://i.imgur.com/TY300qg.png
as you can see from that image, it was successful - but I still can't boot into it.
if I try the hardware keys, again it's just the OnePlus logo, and if I try do it from fastboot without flashing, I get this...
http://i.imgur.com/TObXGB9.png
please keep in mind I definitely got the right image from the twrp website, and the sha1sums match.
so, I tried the official cyanogen recovery from their site instead, and it's the same story - it won't boot.
and during all this, I can't boot normally either.
at the moment I'm thinking I need some sort of full rom that can be flashed with fastboot. it may be possible to convert the flashable version from OnePlus (http://i.imgur.com/KvMHvaZ.png) to a fastboot one with a tool like sdat2img.py. But I got a FAILED (remote: Unknown chunk type) when I tried to fastboot flash system system.img with the new system.img I got from sdat2img.py
anyway, any help would be much appreciated - this is very annoying.
thank you,
Senan
You try flashing stock recovery?
Exodusche said:
You try flashing stock recovery?
Click to expand...
Click to collapse
Hello, I can't find a stock image that can be flashed with fastboot. I only have the full stock rom, but it's meant for flashing with recovery.
sentriz said:
Hello, I can't find a stock image that can be flashed with fastboot. I only have the full stock rom, but it's meant for flashing with recovery.
Click to expand...
Click to collapse
You miss understand. You are trying to fastboot flash custom recoveries like twrp/cynogen. I am asking about the OnePlus X original stock recovery. You can flash full stock Rom with stock recovery.
Exodusche said:
You miss understand. You are trying to fastboot flash custom recoveries like twrp/cynogen. I am asking about the OnePlus X original stock recovery. You can flash full stock Rom with stock recovery.
Click to expand...
Click to collapse
I said in the first post that I have no recovery to boot to. Are you saying I should flash the stock recovery with fastboot? if so, how would it be different to flashing the twrp or cyanogen recovery. and if it would differ, could you try help me find a stock recovery that I can flash with fastboot?
thank you,
Senan
You tried the oos3?
Omicron Technics
sniper20 said:
You tried the oos3?
Omicron Technics
Click to expand...
Click to collapse
the OO3 recovery? only tried 2 recoveries
Download this and fastboot flash it.
http://oxygenos.oneplus.net.s3.amazonaws.com/OPX_MM_recovery.img
Exodusche said:
Download this and fastboot flash it.
http://oxygenos.oneplus.net.s3.amazonaws.com/OPX_MM_recovery.img
Click to expand...
Click to collapse
this is the first recovery I've tried that worked! thank you very much.
I'm gonna try sideload a nice ROM now, cheers.
sentriz said:
this is the first recovery I've tried that worked! thank you very much.
I'm gonna try sideload a nice ROM now, cheers.
Click to expand...
Click to collapse
okay, I get "Installation failed" in the recovery after about transferring about 35% of the ROM via sideload
I should also note that I get a "wiping failed" when I try to wipe from that recovery
sentriz said:
okay, I get "Installation failed" in the recovery after about transferring about 35% of the ROM via sideload
Click to expand...
Click to collapse
You have to flash 2.2.2 with that recovery first. Just download it to your phone storage. Then your back into the game. I think what you did was flash OOS3 and changed bootloader. That is why you were having problems with twrp.
I have done fasboot format of my phone and erased recovery. So i flashed boot.img of stock rom After flashing boot image i tried to reboot to recovery mode but it is stuck at boot logo. What should i do to boot into stock recovery? Thanks
As far as I know, the rmn3 doesn't have a stock recovery installed.
You can, however, use MiFlash to flash a MIUI ROM. Run through setup, and you should be able to flash a custom recovery from there.
But why?
akjain said:
I have done fasboot format of my phone and erased recovery. So i flashed boot.img of stock rom After flashing boot image i tried to reboot to recovery mode but it is stuck at boot logo. What should i do to boot into stock recovery? Thanks
Click to expand...
Click to collapse
People shift from stock recoveries to custom recoveries like TWRP! But why do u want to even do the vice versa?
ckflash09 said:
People shift from stock recoveries to custom recoveries like TWRP! But why do u want to even do the vice versa?
Click to expand...
Click to collapse
i want to unroot the device and now i am not able to flash custom recovery from fastboot mode. I m getting error as recovery partiton missing or not found
Try this way!
akjain said:
i want to unroot the device and now i am not able to flash custom recovery from fastboot mode. I m getting error as recovery partiton missing or not found
Click to expand...
Click to collapse
Flash miui rom using miflash tool,, root access will be lost and whatever the problem is,, should be resolved! Then try flashing recovery using fastboot and make sure the driver's see properly installed on your pc! :cyclops: