Database Develop

[Q] Strange problems posted nowhere else. (Involving unrooting, ruu, ota)

I'm trying to install an OTA update to get to the newest version of android for my (Rogers) ONE M7.
I had:
- Unlocked the bootloader
- Flashed a custom recovery
- Flashed a custom kernel
- Installed Supersu and rooted phone
- BUT KEPT STOCK ROM
Phone worked wonderfully with no problems but slowly became dated (4.4.2)
My phone still received OTA's, after ignoring them for a while I would like to move to the newest available (5.1) for all the upgrades like ART.
I then:
- Flashed stock recovery (successfully)
- Flashed stock kernel (successfully)
- Relocked bootloader (successfully)
- But this is where the weirdness starts. I can't unroot, and thus the OTA fails.
I have tried:
- Full unroot using supersu
- Disabling super user
- Uninstall Supersu
- Deleting all .su, su, supersu.apk, busybox (which I suppose supersu installed?) and all other associated files using file explorer.
- Using apps like Universal Unroot.
The best I can do is temporarily remove root by using supersu full unroot, BUT UPON RESTART THE PHONE REINSTALLS SUPERSU AND ROOTS ITSELF. This has me completely stumped.
I then tried installing a ruu to wipe the root off my phone but the ruu always crashes at 5%... with windows telling me "htc_fastboot.exe stopped working".
I tired extracting the ruu and flashing it using fastboot but in that case the cmd window fails with "invalid sparse file format at header magi"
And yes, the MID, CID and carrier match up exactly for my phone and the ruu.
The only option I have left is to redo everything so I can flash an (updated) custom rom on my phone. But I want to stay on stock rom so I don't lose all my files. Which I wouldn't with an OTA, or when using HTC's awesome backup feature (which I'll lose with a custom rom). (As well as holding its resale value!)
Thanks for reading, if anyone know's how to get around this seemingly impossible problem please let me know!!

123ethan said:
I'm trying to install an OTA update to get to the newest version of android for my (Rogers) ONE M7.
I had:
- Unlocked the bootloader
- Flashed a custom recovery
- Flashed a custom kernel
- Installed Supersu and rooted phone
- BUT KEPT STOCK ROM
Phone worked wonderfully with no problems but slowly became dated (4.4.2)
My phone still received OTA's, after ignoring them for a while I would like to move to the newest available (5.1) for all the upgrades like ART.
I then:
- Flashed stock recovery (successfully)
- Flashed stock kernel (successfully)
- Relocked bootloader (successfully)
- But this is where the weirdness starts. I can't unroot, and thus the OTA fails.
I have tried:
- Full unroot using supersu
- Disabling super user
- Uninstall Supersu
- Deleting all .su, su, supersu.apk, busybox (which I suppose supersu installed?) and all other associated files using file explorer.
- Using apps like Universal Unroot.
The best I can do is temporarily remove root by using supersu full unroot, BUT UPON RESTART THE PHONE REINSTALLS SUPERSU AND ROOTS ITSELF. This has me completely stumped.
I then tried installing a ruu to wipe the root off my phone but the ruu always crashes at 5%... with windows telling me "htc_fastboot.exe stopped working".
I tired extracting the ruu and flashing it using fastboot but in that case the cmd window fails with "invalid sparse file format at header magi"
And yes, the MID, CID and carrier match up exactly for my phone and the ruu.
The only option I have left is to redo everything so I can flash an (updated) custom rom on my phone. But I want to stay on stock rom so I don't lose all my files. Which I wouldn't with an OTA, or when using HTC's awesome backup feature (which I'll lose with a custom rom). (As well as holding its resale value!)
Thanks for reading, if anyone know's how to get around this seemingly impossible problem please let me know!!
Click to expand...
Click to collapse
When your have problems flashing a RUU, just flash the Same version Firmware first then the RUU
also your PC needs all the C++ installed (2005 - 2008 - 2010 both x64 and x32 bit versions)

T stuck in recovery mode,ROM not installing,5% battery.

So I decided to install cyanogenmod WhiteNeo ROM on my xperia T
did the entire process alright.
for recovery, CWM din't work so downloaded app from playsore and got TWRP from there.
the followed the steps from here to reach till step 8 from wiki.cyanogen guide.
stuck at step 8. DOn't get how to perform it because it is confusing.
altenrately sentthe zip package to sd card and tried there but says Error executing updater binary in zip.
I am stuck.
5%battery left.
and I dont know what to do.
can't even get out of Recovery mode.
device is unresponsive when connected to USB and is powered off.
can anyone please sort this out and explain in simple words how to get out of this mess?
p.s: if battery expires,then what happens?

tried installing stock firmware using flashtool
but
07/014/2015 19:14:54 - ERROR - Error in processHeader
all the time
googled all the solutions
none works
help please?

You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.

WhiteNeo said:
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
Click to expand...
Click to collapse
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.

aber96crombie said:
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
Click to expand...
Click to collapse
Reverting to stock FOTA and getting official CM recovery (which won't flash anything but official CM builds and gapps) can be done with flashtool and a suitable ftf or using a Terminal command that you will find on the last pages of my CM12.1 thread for Xperia T.
TWRP version should be visible in settings or what one would call a "status bar".
And the force-closing gapps are just the result of a broken or outdated recovery. I've already been reported the same issue after creating a FOTAKernel TWRP for a friend.
You should be able to flash official CM12 gapps from Cyanogen Recovery.. Just google those.

Stuck with cm recovery and no bootloader Xperia Z1

Hello everybody,
I rooted my Xperia Z1 about 8 months ago in order to install the 5.1.1 update which didn't roll out for my device probably because it was a global version (5.0.1 was the last OTA). I did a clean install with no problems, flashed DualRecovery, SuperSu, and BusyBox was working just fine. Everything was working perfectly.
About 3 months ago, I tried updating BusyBox, only to tell that the update failed (couldn't install in the path it used to be try changing the path), I read and read, and found that the solution was to delete a certain file from root that prevented me from modifying certain folders and their content(even with root access), and then do a clean install in a different path than the former one. However, I couldn't gain root access to my files, no root explorer worked! It bugged me, but I was busy at that time, so I couldn't resolve it.
Few weeks later I tried rebooting into recovery, but no method worked, no apps, no key combination, no adb, nothing at all worked! After 2 hard days I managed to install TWRP recovery using NUTS recovery project. I rebooted several times, and it was still working. I then installed BusyBox with no problems, and everything was back to perfect. Later I decided to install CM 12.1 because I always used on my Samsung Galaxy Nexus and I always loved it. So using my now working recovery, I backed everything up on a USB and then flashed CM 12.1 WITHOUT its recovery along with a GAPPS package.
CM was installed, which then rebooted into its recovery and tried to install the GAPPS package. The GAPPS installation was a fail. CM recovery asked me to try using TWRP to do such installation ( go figure! ); in fact, CM recovery couldn't flash anything besides another CM 12.1 update. After this point I wasn't able in any possible way to enter TWRP nor install it. Even if I want to flash using fastboot I couln't! adb reads my device just fine, and can use it to reboot into flashmode, which doesn't seem to be functioning properly. The blue light turns on but there isn't a thing on the screen, fastboot can't recognize is it and hence I can't flash anything using fastboot.
Should I reflash partitions if this could be done on Z1? ( I did it before on my Nexus ) Can I use Odin? I even doubt I can enter download mode on my phone
Any help would be much appreciated.
Thanks in advance!

Anyone?
No?
Ok! :sad:

Is your bootloader unlocked? To run cm on our z1 you need an unlocked bootloader because cm needs a custom kernel.
You can try Sony companion app or androxydes flashtool in combination with a pre-rooted ftf to reach stock again.

The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
I managed to install TWRP using TWRP Manager app that I downloaded from APKmirror website. I installed GApps and it is working fine right now.
TWRP Manager said that I should have a FOTA recovery or something like that, and if I don't have one then I am installing the recovery on my responsibility.
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!

Mohdhamm said:
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Click to expand...
Click to collapse
AFAIK, Emma hasn't been updated for a LONG time. It will remain defunct with no updates and no support. Use flashtool from androxyde if you want to continue using Sony's stock ROM.
No bootloader or flash mode detection: That usually means the drivers that interfaces with your phone is missing. Search around XDA for the correct fastboot and adb drivers for your PC's OS.
My approach for fixing your issue: Find the right drivers and put a stable Lollipop ROM on your sdcard. If you have fastboot working (make sure you have unlocked bootloader), flash boot image from the Lollipop zip and flash the recovery image found in some Lollipop threads. If everything goes well, your phone will bootloop, but you'll have working recovery. Press Vol Down when the Sony Logo appears on screen to enter TWRP. Since you saved a backup of your phone elsewhere, erase all the partitions (minus sdcard), format them to ext4, and flash the Lollipop ROM from your sdcard.

[SOLVED] c5502 5.1.1 Stuck on black blank screen, Unlocked bootloader, No recovery!

Hello Xperia ZR users,
I had dual recovery i flashed RR M and RR N rom's in a single day. the next day i restored stock rom which i have backup approximately 5.30 gb it took so much time to boot whole 60 percent charging had been gone so i flashed stryflex mm rom for sony look but again i thought to use stock rom so this time i restored stock backup rom through otg pendrive because my external storage got write permissions problem when i installed stryflex! but now also same happened device taking so much time to boot and i thought to flash rr nougat but i wiped everything through dualrecovery and i removed battery as dualrecovery not showing anything in otg pendrive now there is also no recovery available to flash anything!
Xda user Robin guided me to flash stock rom through firmtool but ended with errors in xperia firmtool log file!
So now i am having black blank screen! no recovery unlocked bootloader! i had installed adb drivers through flashtool drivers and also installed other universal adb drivers but pc is not showing my device in adb devices list in command prompt! My device is showing in Device manager as ADB interface! when i connected my phone through fastboot mode !
Please help me!
SOLUTION : If u are using custom roms and want to go back to stock rom 5.1.1 ?! and while flashing are u experiencing blank screen after a successful flash through flashtool or experiencing any errors in flashtool while flashing?! Well there are two methods to flash stock roms! Successfully!!
Method 1 : whatever the custom rom you are in! Just flash the stock 5.1.1 rom in your phone through flashtool but with other pc! Yes other pc, pc with no drivers installed regarding adb! Try out your friends laptop or pc! Don't forget to install flashtool, fastboot and your xperia model drivers through flashtool drivers exe file! which is located in c drive!! Also install adb setup file that install all drivers all over pc! And just flash the stock 5.1.1 rom through flashtool! There are 99.99999% chance that stock rom will be successfully flashed in your phone! If this doesn't work!! It's your bad luck and its definitely pc problem not your phone! Then just follow method 2 to flash the rom!
Method 2 : flash the twrp img through flashtool (use any flashtool version!) by entering into fastboot mode and select flash the kernel option and select the twrp img file in your pc (i mean u have to download the twrp 3.0.3 img and use it ! ) twrp will be successfully installed in ur phone and then flash the stock jellybean 4.1.2 version the download link is available below! it is an ftf file convert the ftf file into zip file and then flash through recovery! that's it u will be booted to stock jb firmware and it will ask to factory reset on first boot press yes option it will take few minutes and then it will be booted to jb rom!! restore drm keys if u have the backup and update the os through xperia companion!! or else flash the 5.1.1 zip through recovery!
Note: only flash the jb rom i tested flashing kitkat it doesn't worked!
Stock jellybean firmware Link:
https://forum.xda-developers.com/showthread.php?t=2384512
PRFCreator tool:
https://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904

I uploaded a flashtool log file ! Please help!!

Delta solution
I was also stuck with same error, I Banged my head in all forums with all rookie answers.
Why this problem occurs?
Ans: Because the user has installed Marshmallow or Nougat ROM on Lollipop. Even if you try to
come back on Lollipop stock, it won't accept the TA partition and won't go further (Although CM 10/11/12/13/14 or ASOP 10/11/12/13/14 RR-M/N WORKS without ERROR, but I assume user is hungry for STOCK 5.1.1 LOLLIPOP).
So, what's the solution, either you need backup of your TA partition OR - and if you haven't like me. Nothing to worry. You just need Stock JellyBean ROM (THIS IS IMPORTANT).
My solution will 100 percent work (Its Brahmastra ).
Step 1) download https://forum.xda-developers.com/showthread.php?t=2384512
Step 2) download flash tool version which is mentioned in the above link , I used 0.9.11. Version 0.9.19.8 is HELL - You will never succeed with this version)
Step3) flash... Even if you encounter error [17] no worries, if no error, still no worries (If you get error after TA partation is done...you are through, if you encounter before TA partition, it is worrisome)
Step 4) fastboot -i 0x0fce oem unlock 0xxxxxxxxxxxxxxx69
Step 5) fastboot flash boot boot. Img (twrp or PhilZ recovery) or STEP 8)
Step 5) download customized 5.1.1 by chippa
Step 6) goto TWRP (Recovery) and install customized , NO CMW recovery
Step 7) beer for me, go to STEP 10
Step 8) use flash tool to install C5502_10.7.A.0.222_1273-5765_R1E
Step 9) It boots after 3 sec
step 10) go to step 7 (beer loop mode)
If you go to SONY service centre, those M*F* will say, your screen is damaged, because once you push power button, it vibrates and goes to blank screen.
OR
You have locked your bootloader and you simply need to unlock the bootloader in ( STEP 4 ) and you will start with normal BOOT procedure.
How to unlock the bootloader?
Ans: http://www.cyanogenmods.org/forums/topic/unlock-bootloader-android-phone-using-fastboot/
OR
Relock bootloader (boot), then unlock bootloader (boot the device)
Cheers,
Dr. Lamda

Ok man thanks for your help! I am really surprised that someone gave me the solution! Well, i think i repaired my device! I don't know exactly what i did was correct or wrong few days before i installed a universal adb driver that repaired the driver in pc although there was an existing adb driver! And then i installed an old adb setup because i found that new adb not works sometime! And then through flashtool ver 0.9.23. something , i flashed the twrp 3.0.3 img by fastboot mode it installed successfully! And then i just flashed a rr nougat rom through recovery. I seen so many errors while wiping and flashing rom and gapps! But phone rebooted successfully! After that i see that selinux is set to enforcing rr nougat rom and i can't go to recovery mode so i same flashed twrp img through flashtool but it only rebooting to twrp i pulled off battery and booted again it was successfully booted to ROM!
Hey! Can i flash customised 5.1.1 through recovery ?! as now i am in nougat !

sandeepxperia said:
Ok man thanks for your help! I am really surprised that someone gave me the solution! Well, i think i repaired my device! I don't know exactly what i did was correct or wrong few days before i installed a universal adb driver that repaired the driver in pc although there was an existing adb driver! And then i installed an old adb setup because i found that new adb not works sometime! And then through flashtool ver 0.9.23. something , i flashed the twrp 3.0.3 img by fastboot mode it installed successfully! And then i just flashed a rr nougat rom through recovery. I seen so many errors while wiping and flashing rom and gapps! But phone rebooted successfully! After that i see that selinux is set to enforcing rr nougat rom and i can't go to recovery mode so i same flashed twrp img through flashtool but it only rebooting to twrp i pulled off battery and booted again it was successfully booted to ROM!
Hey! Can i flash customised 5.1.1 through recovery ?! as now i am in nougat !
Click to expand...
Click to collapse
Yes! you can go back to 5.1.1 by the above procudure

If you want to revert back from RR - N to stock firmware then use flashtool-0.9.18.4 and first flash stock 4.4.4 firmware/ boot then flash stock 5.1.1 firmware.

Lλmdα said:
Yes! you can go back to 5.1.1 by the above procudure
Click to expand...
Click to collapse
so i can flash the customised 5.1.1 rom by chippa through twrp recovery, right?

moly.maji , i love u brooooooo with your help what i did was i downloaded a jelly bean 4.1.2 rom and flashed through twrp 3.0.3 recovery by converting the ftf file to zip file (thanks to my other bro xda member robin for telling the info about prf creator pc software tool that converts ftf to zip) and it was successfully booted to jellybean stock rom !
and i am saying to whoever facing to flash the stock rom after updating the device to custom roms to prevent any errors to return to stock 5.1.1 firmware while flashing through flashtool it may be driver related errors in pc or any error just use the flashtool for flashing the twrp img! only by going to fastboot mode and then select flash the kernel option through that select the twrp img that's it within seconds the twrp will be installed in your phone and through twrp recovery flash the jellybean 4.1.2 rom ! i tested flashing kitkat but failed! so flash only jellybean rom!! that's it your phone will boot to jb rom and then if u have backup of drm keys restore and update the os through xperia companion or flash the 5.1.1 rom through recovery that's it !!

my device cant be detected and refused to go into fastboot or Recovery mode
is there any way?

Prerooted firmware update on rooted xperia Z3C

Hello,
If I ask stupid questions, please, be patient with me, I just want to make sure I don't mess up things.
A long time ago I rooted my phone using https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343, but at that time I didn't want to flash lolipop - I have been staying with 4.4.4 until now.
Now I would like to upgrade to let's say Marshmallow, stock version, and keep root. I have a very old TWRP recovery installed on the phone. I remember the original rooting process was rather complicated, but now it seems to me, that it should be much simpler, I guess this is what I should do:
On PC:
1. Install original z3c drivers
2. Install latest flashtool
3. Use flashtool to install latest TWRP recovery, like from here: https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113
4. Download pre-rooted Marshmallow image, however, I am not sure if these https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 are pre-rooted
5. Put the image on the sd card and install it directly from the TWRP recovery
Am I right?