I rooted my phone 2 weeks ago. While backing up and restoring Dem keys, I broke something I don't kno. Now every custom rom I install boots and gets stuck at Phone is starting and then reboots. Tried LOS 16, 17.1 and Pixel experience rom. But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
GOrMHATRe said:
But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Click to expand...
Click to collapse
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
GOrMHATRe said:
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
Click to expand...
Click to collapse
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
SXUsr said:
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
Click to expand...
Click to collapse
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
I have already use flashtool and newflasher. That's how I rooted my phone. Both of them are successful in flashing stock sony firmware. But the custom roms are in zip file. Don't kno of its possible to flash those using flashtool.
GOrMHATRe said:
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
Click to expand...
Click to collapse
Steps :
Remove your screen lock (set it to swipe up or none) and remove all your fingerprints registered.
Download the zip above and extract the boot, system and vendor images
Make sure you have Android 10 TWRP as mentioned above with link
Go to recovery > wipe and wipe system, cache and data nothing else.
Then go to install and flash boot.img as boot image, system.img as system image and vendor.img as vendor image.
Click to expand...
Click to collapse
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
SXUsr said:
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
Click to expand...
Click to collapse
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
GOrMHATRe said:
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
Click to expand...
Click to collapse
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
SXUsr said:
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
Click to expand...
Click to collapse
I tried this but the result was same. Rom boots upto the lock screen. Then when I swipe it shows: phone is starting and goes into bootloop. I even tried an older version of PE Rom whic contain s only img files but again same result.
You kno initially, after I unlocked the bootloader I just installed stock rom and installed LOS on top of it as per guide. It worked well. I coud go into menu and see apps.
But I panicked that I had forgotten to restore drm keys. Instead of first checking camera, I went back and restored the Ta partition and repeated the steps after it upto installation of rom and since then I have faced problems . Restoring ta partition and flashing stock rom after it is where I have made a mistake and broken something. Can this be fixed with twrp. I kno there are options in twrp to format & repair partitions. Coud that help to repair what ever that was broken?
GOrMHATRe said:
Coud that help to repair what ever that was broken?
Click to expand...
Click to collapse
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
SXUsr said:
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
Click to expand...
Click to collapse
Which kernel are you speaking about? I had backed up Ta image using renoroot exploit and restored it using:
adb pull /data/local//tmp/TA-unlocked.img
adb push TA-locked.img /data/local/tmp
Then in window with temp root prompt:
cd /data/local/tmp
de if=TA-locked.img of=/dev/block/bootdevice/by-name/TA
sync
sync
Reboot phone
But actually, when I checked my phone just now and that tmp directory seems empty. So, does that mean TA didn't get restored properly? Is that why I am facing problems? Stock roms seem to be working fine.
As for sony's own flashtool, I have it installed. But thought it doesn't offer any different functionality than newflasher or old flashtool? Woud sony flashtool help me go back to square 1 and make my phone as it was before rooting so that I can do everything again properly?
GOrMHATRe said:
Which kernel are you speaking about?
Click to expand...
Click to collapse
The kernel of the rom. Check your service menu for drm status.
SXUsr said:
The kernel of the rom. Check your service menu for drm status.
Click to expand...
Click to collapse
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
GOrMHATRe said:
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
Click to expand...
Click to collapse
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
SXUsr said:
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Click to expand...
Click to collapse
I will try this but after some time. I have experimented on my phone a lot in recently. Need it to be stable for work for some time now. My secondary phone is not setup to work with gmail etc. Thanks for all the advice you have provided though.
On another note, now that Android 11 is out, do you think we will get a rom based on it for Xz1 compact? I even had a thought of skipping 10 and going for 11 based rom.
thefelineofaveb said:
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
Click to expand...
Click to collapse
I have not touched drm keys after I backed up and restored them for the 1st time.
Related
Hey guys
So I just bought a new Z3C and I'm planning on rooting it and installing CM12.1 on it. But before that I wanna make sure I perfectly understood the entire process. So if anyone could help by answering/confirming some of the things below, I would really appreciate that.
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Thank you very much.
arsradu said:
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Click to expand...
Click to collapse
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
arsradu said:
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Click to expand...
Click to collapse
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
arsradu said:
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Click to expand...
Click to collapse
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
arsradu said:
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Click to expand...
Click to collapse
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
arsradu said:
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
Click to expand...
Click to collapse
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
arsradu said:
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Click to expand...
Click to collapse
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
MyPictures said:
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
Click to expand...
Click to collapse
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
arsradu said:
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
Click to expand...
Click to collapse
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
MyPictures said:
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
Click to expand...
Click to collapse
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
arsradu said:
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Did you install the drivers properly and on which Operating system are you flashing it?
MyPictures said:
Did you install the drivers properly and on which Operating system are you flashing it?
Click to expand...
Click to collapse
I would say yes. I mean...after googling a bit, I saw that I actually don't need to just "ignore" that message asking to press the Back button, but to actually press Volume Down instead. Which I did. And I was able to go into Flash Mode. (Flash Tool says "device connected in Flash Mode"). The device was properly recognized in MTP mode. Still, I had to manually install the Flash-tool drivers to get it recognized in flash mode, as well. Not sure why...
I mean, if the phone was properly recognized without manually installing anything (Windows downloaded and installed its own drivers), why the hell do I need to install custom drivers to get it recognized in flash mode? By the way, this "flash mode" is similar to Samsung's "Download Mode", for as far as I could see. And, just like on Samsung's devices, the access is made by pressing the Volume Down upon booting up.
Anyway, even though the device is now recognized in flash mode, I still get an error trying to flash stock 4.4.4.
I get this:
Code:
14/014/2015 21:14:34 - INFO - Please connect your device into flashmode.
14/016/2015 21:16:28 - INFO - Device disconnected
14/017/2015 21:17:03 - INFO - Device connected in flash mode
14/017/2015 21:17:03 - INFO - Opening device for R/W
14/017/2015 21:17:03 - INFO - Reading device information
14/017/2015 21:17:03 - INFO - Unable to read from phone after having opened it.
14/017/2015 21:17:03 - INFO - trying to continue anyway
14/017/2015 21:17:03 - INFO - Start Flashing
14/017/2015 21:17:03 - INFO - Processing loader.sin
14/017/2015 21:17:03 - INFO - Checking header
14/017/2015 21:17:03 - ERROR - Processing of loader.sin finished with errors.
14/017/2015 21:17:03 - INFO - Ending flash session
14/017/2015 21:17:03 - ERROR - Error in processHeader : 1 : Incorrect function.
14/017/2015 21:17:03 - ERROR - Error flashing. Aborted
14/017/2015 21:17:03 - INFO - Device connected in flash mode
And after a while, it automatically reboots in normal mode.
Windows version is Windows 10. But I'm not sure that's the problem here since, as I said, the device does get recognized both in MTP and flash modes. Also, for as far as I could see, other people are having the same issues on other versions of Windows.
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
MyPictures said:
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
Click to expand...
Click to collapse
Yes, I'm running FlashTool64.exe since I'm running a 64-bit version of Windows.
The device is correctly recognized in flash mode (after manually selecting the driver installed with flash-tool). See the attached image for more info.
But indeed maybe I got the wrong firmware. Problem is that I'm not really sure which one should I choose.
I got one called D5803_23.0.1.A.5.77_Customized_FR.ftf. I don't mind it that it's in French. All of them have English anyway.
Also, I saw one for UK here called D5803_23.0.A.2.105_UK.ftf. Seems to be different.... I will try with that as well.
Update: same error with that UK firmware, as well.
Update2: Well I'm half way there. Got 4.4.4 installed and got it rooted. YAY. Still trying to figure out why adb is not correctly running when trying to backup TA.
Update3: ok, backup done too!
Update4: the boot.img that comes with CM12.1 doesn't seem to have a recovery.... Or if it does, I couldn't boot in it so I can flash CM12.1.
I tried the one from Doomlord (Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img) and that seems to be based on CWM v6.0.4.7.
Problem with that is that, even though I can boot into recovery, I can't flash CM12.1. It says error status 7. Any idea why or how to fix this?
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
MyPictures said:
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
Click to expand...
Click to collapse
Might be. The problem is the device is not correctly recognized upon flashing (it says the device is "Aries" but the ROM is for D5803, D5833, z3c LOL), due to the check made within the updater-script (first line). For as far as I could see, this is a known issue... Not sure why it hasn't been fixed by now.
Anyway, removing that line will get the ROM installed successfully (at least with THAT recovery).
So I'm on CM12.1 , been for a few days now (thank you for your help), and I was wondering if there are any "permanent" recoveries (compatible with CM12.1, of course) that I can flash, something that can give me the ability to boot into recovery (and not Cyanogen Recovery, since that one sucks) and do things like nandroid backup (I know TWRP and CWM can do that, but I couldn't find any permanent version of those (or maybe I just didn't dig deep enough), and I'm not sure they are compatible with CM12.1) and formatting /system. The last one is really important for a clean installation of the ROM, especially since it doesn't look like it's done by the ROM itself.
Hi, everyone this is my first post.
Though I am not new to rooting, but earlier i used to do one click root..so unrooting was also that damn easy.
Recently i rooted my moto x 2nd gen xt1092 by unlocking bootloader and after flashing TWRP and later using SuperSu.
But here is the catch I didn't take nandroid backup before rooting.
So my question is
1 If I take backup now , will this backup be a rooted backup , means that if in future I flash this backup my phone will be directly boot in rooted mode..?
2 If I unroot using supersu are there chances I may stuck in bootloop?
3 now as I alreday have Twrp flashed how can I get to my original OS I once had? 9(system recovery image)
Plz let my doubts get cleared.
thanks in advance
saumyadip said:
Hi, everyone this is my first post.
Though I am not new to rooting, but earlier i used to do one click root..so unrooting was also that damn easy.
Recently i rooted my moto x 2nd gen xt1092 by unlocking bootloader and after flashing TWRP and later using SuperSu.
But here is the catch I didn't take nandroid backup before rooting.
So my question is
1 If I take backup now , will this backup be a rooted backup , means that if in future I flash this backup my phone will be directly boot in rooted mode..?
2 If I unroot using supersu are there chances I may stuck in bootloop?
3 now as I alreday have Twrp flashed how can I get to my original OS I once had? 9(system recovery image)
Plz let my doubts get cleared.
thanks in advance
Click to expand...
Click to collapse
1. yes, you can do a full backup of system, data, recovery, boot, etc (default configuration of backup) and when you do a restore you have the same root system.
2, sometimes, you have a 50% of possible failure, the best option is flash the stock system files and after do a ota update or similar (never do a downgrade, can kill your phone(hardbrick))
3. Via bootloader (down volume button when you turn on the phone)
Write or copy this lines on bootloader mode (in the same folder where you have execute the command for your unlock code for the unlock of boot loader)
fastboot flash recovery recovery.img
fastboot reboot
The recovery is on image of StockRom.
Sorry my English, I`m Chilean.
cyker31 said:
1. yes, you can do a full backup of system, data, recovery, boot, etc (default configuration of backup) and when you do a restore you have the same root system.
2, sometimes, you have a 50% of possible failure, the best option is flash the stock system files and after do a ota update or similar (never do a downgrade, can kill your phone(hardbrick))
3. Via bootloader (down volume button when you turn on the phone)
Write or copy this lines on bootloader mode (in the same folder where you have execute the command for your unlock code for the unlock of boot loader)
fastboot flash recovery recovery.img
fastboot reboot
The recovery is on image of StockRom.
Sorry my English, I`m Chilean.
Click to expand...
Click to collapse
Thanks cyke31.
My two doubts are absolutely clear.
I have a doubt regarding the 3 point.
where I will find that recovey.img file?
And after flashing that recovery.img file will I get back to my stock rom, that I had before TWRP was installed ?
Can I take OTA updates?
Will TWRP get uninstalled ?
your english is pretty good..
I am Indian ....so don't worry . I'm not grammar NAZI..
saumyadip said:
Thanks cyke31.
My two doubts are absolutely clear.
I have a doubt regarding the 3 point.
where I will find that recovey.img file?
And after flashing that recovery.img file will I get back to my stock rom, that I had before TWRP was installed ?
Can I take OTA updates?
Will TWRP get uninstalled ?
your english is pretty good..
I am Indian ....so don't worry . I'm not grammar NAZI..
Click to expand...
Click to collapse
I recommend downloading the stock rom and do a clean install , because any change you've made in system, will generate bootloop...
Here the links to the Rom (you must download The xt1092 version)
Firmwares 4.4.4 hasta 5.0.X: https://mega.co.nz/#F!TkIwRTjR!m7W1V35qfLBiiUargAx1vg
Firmwares 5.1 y 6.0: https://mega.co.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
And them install via guides on xda.
cyker31 said:
I recommend downloading the stock rom and do a clean install , because any change you've made in system, will generate bootloop...
Here the links to the Rom (you must download The xt1092 version)
Firmwares 4.4.4 hasta 5.0.X: https://mega.co.nz/#F!TkIwRTjR!m7W1V35qfLBiiUargAx1vg
Firmwares 5.1 y 6.0: https://mega.co.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
And them install via guides on xda.
Click to expand...
Click to collapse
so its better to flash system files than flashing recovery.img
though I'm in no mood to unroot my device. just wanted to know the consequences. I'll do normal backup of my current rooted rom. If in case anything happens I'll flash stock system files from motorola website.
Thanks for the info.
Xposed is the reason I rooted my device. Heard that is better to take nandroid backup before installing Xposed.
saumyadip said:
so its better to flash system files than flashing recovery.img
though I'm in no mood to unroot my device. just wanted to know the consequences. I'll do normal backup of my current rooted rom. If in case anything happens I'll flash stock system files from motorola website.
Thanks for the info.
Xposed is the reason I rooted my device. Heard that is better to take nandroid backup before installing Xposed.
Click to expand...
Click to collapse
Yes, but xposed is a thing, and the modules are totally different thing,Xposed by itself does not cause any problems...
yeah know that but...wanted to be sure..... as there is no service center in my state
So I was an idiot, I've resigned myself to this fact because I've clearly done something wrong.
TWRP installed, rooted and booted.
Then I tried to flash a new ROM from here using TWRP and well... that's where things went tits up. Something in TWRP said in red about not being able to mount something. The loading screen was stuck and then it just bootlooped over and over again. I downloaded a stock ROM, wiped system and tried to flash but now it's stuck on the "your device is shifty" screen and I'm totally out of ideas...
Please refrain from pointing out what a moron I've been.
Thanks in advance to anyone who can save this wretched soul.
do you have access to bootloader with fastboot?
seeing a lot of threads like this around here. Don't want to offend you or anybody else but just that someone has said it: First thing you do after flashing TWRP is a backup :angel:
hope you get your things sorted though. Can your please provide a more detailed list of things you did? How did you try to flash the stock rom you downloaded? dload forced update? flashed in twrp? etc.
lomunet said:
do you have access to bootloader with fastboot?
Click to expand...
Click to collapse
I can still get in to bootloader and fastboot mode no problem.
seeing a lot of threads like this around here. Don't want to offend you or anybody else but just that someone has said it: First thing you do after flashing TWRP is a backup
hope you get your things sorted though. Can your please provide a more detailed list of things you did? How did you try to flash the stock rom you downloaded? dload forced update? flashed in twrp? etc.
Click to expand...
Click to collapse
Yeah I realised I should have done that the second things started going wrong, I got cocky. And I tried to flash the stock with TWRP; downloaded it to my laptop, put it on the SD card and then in to the phone. Every process that the installation or wipe or any of the other actions performed by TWRP is followed by a line saying "Failed to mount '/ data' (Invalid argument)". I tried to follow the forced update of the stock but I couldn't seem to get that to work either ( this method stechguide.com/marshmallow-stock-rom-for-huawei-p9 ). After all that I can't think if there's anything else.
zandercook1 said:
I can still get in to bootloader and fastboot mode no problem.
Yeah I realised I should have done that the second things started going wrong, I got cocky. And I tried to flash the stock with TWRP; downloaded it to my laptop, put it on the SD card and then in to the phone. Every process that the installation or wipe or any of the other actions performed by TWRP is followed by a line saying "Failed to mount '/ data' (Invalid argument)". I tried to follow the forced update of the stock but I couldn't seem to get that to work either ( this method stechguide.com/marshmallow-stock-rom-for-huawei-p9 ). After all that I can't think if there's anything else.
Click to expand...
Click to collapse
Ok, so a few things:
-The failed to mount /data message probably means that you have an old version of TWRP, check the thread again and make sure you use at least RC3 (newest one afaik).
-Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery which you can flash back the same way you flashed twrp (using fastboot, or SRK tools). Once you have stock recovery, you can force the update by putting the update file in a folder on your sdcard (internal or external) called "dload". Then you turn off the phone and start it by holding volume up, volume down and power.
-Alternatively you could use a custom rom, which you can find in the dev thread. Custom roms can and should be flashed in TWRP.
Try relocking botloader and installing stock rom with this tool
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
clouds5 said:
Ok, so a few things:
-The failed to mount /data message probably means that you have an old version of TWRP, check the thread again and make sure you use at least RC3 (newest one afaik).
-Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery which you can flash back the same way you flashed twrp (using fastboot, or SRK tools). Once you have stock recovery, you can force the update by putting the update file in a folder on your sdcard (internal or external) called "dload". Then you turn off the phone and start it by holding volume up, volume down and power.
-Alternatively you could use a custom rom, which you can find in the dev thread. Custom roms can and should be flashed in TWRP.
Click to expand...
Click to collapse
I keep pressing the up/down + power buttons but it keeps going to TWRP, as for the out of date version I have 3.0.0-0 but as lomunet suggested I'm downloading the srk tool. That's what I originally used to install TWRP in the first place. For the stock ROM to boot do I need to do anything to the file when it's downloaded (ie zipped or unzipped)? Nosing around a few other threads I noticed they mention something about making a file in the root of the file, and I hope you'll pardon my ignorance, but I have no idea how to do that. As for the custom ROM, I'll try that again when srk tools has finished downloading and I've reinstalled TWRP.
lomunet said:
Try relocking botloader and installing stock rom with this tool
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
Click to expand...
Click to collapse
And I'd just like to thank you two for your patience!
Edit:
Ok so, I installed the latest TWRP (3.0.2-eva-modaco-rc3) and that went off without a hitch. Using the SRK tools that lomunet suggested I tried to sideload the stock ROM but the error message of " cannot read 'sideload\ROM.zip' " keeps popping up. I'm downloading a custom ROM (forum.xda-developers.com/p9/development/rom-huawei-p9-fromfuture-newworld-t3390820) as I type to see if that works flashing it through TWRP.
zandercook1 said:
I keep pressing the up/down + power buttons but it keeps going to TWRP, as for the out of date version I have 3.0.0-0 but as lomunet suggested I'm downloading the srk tool. That's what I originally used to install TWRP in the first place. For the stock ROM to boot do I need to do anything to the file when it's downloaded (ie zipped or unzipped)? Nosing around a few other threads I noticed they mention something about making a file in the root of the file, and I hope you'll pardon my ignorance, but I have no idea how to do that. As for the custom ROM, I'll try that again when srk tools has finished downloading and I've reinstalled TWRP.
And I'd just like to thank you two for your patience!
Edit:
Ok so, I installed the latest TWRP (3.0.2-eva-modaco-rc3) and that went off without a hitch. Using the SRK tools that lomunet suggested I tried to sideload the stock ROM but the error message of " cannot read 'sideload\ROM.zip' " keeps popping up. I'm downloading a custom ROM (forum.xda-developers.com/p9/development/rom-huawei-p9-fromfuture-newworld-t3390820) as I type to see if that works flashing it through TWRP.
Click to expand...
Click to collapse
if twrp works the rom must be work without problems...
zandercook1 said:
I keep pressing the up/down + power buttons but it keeps going to TWRP
Click to expand...
Click to collapse
clouds5 said:
Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery
Click to expand...
Click to collapse
you really need to flash stock recovery first to flash stock firmware. It won't work as long as you have TWRP installed you can use SRK tools to flash stock recovery.
If you are always stuck, jus download "DC Phoenix"(i don't know if i'm authorized to post the name ?), it's a paid app but it's worked for me. Just boot to fastboot mode, and flash your firmware with the app
clouds5 said:
you really need to flash stock recovery first to flash stock firmware. It won't work as long as you have TWRP installed you can use SRK tools to flash stock recovery.
Click to expand...
Click to collapse
Ahhhh right right right. So I need to remove TWRP first, then use SRK tools to flash the stock recovery?
... so, how do I remove TWRP?
zandercook1 said:
Ahhhh right right right. So I need to remove TWRP first, then use SRK tools to flash the stock recovery?
... so, how do I remove TWRP?
Click to expand...
Click to collapse
Installing stock recovery will remove TWRP.
You're all heroes.
zandercook1 said:
You're all heroes.
Click to expand...
Click to collapse
You are a batman yourself.
Hello everyone,
I'm in a little trouble. I need to install custom recovery on my Xperia SP C5302 but I have no PC.
How can I install TWRP ( preferred ) / CWM/Philz on my device ? Is there any way ?
Thank You.
Note : There's a cyber cafe beside my house. But all their computers are running Windows XP.
If there's no way to install without PC then can I be able to install custom recovery on my device with Win XP ?
Thanks again.
Do you have root?
TechnoSparks said:
Do you have root?
Click to expand...
Click to collapse
Yes I'm rooted and my bootloader is unlocked.
Are you ready to bear any risks?
TechnoSparks said:
Are you ready to bear any risks?
Click to expand...
Click to collapse
Yes I'm. but what kinda risk ? soft brick ? or something else ?
rhrokib said:
Yes I'm. but what kinda risk ? soft brick ? or something else ?
Click to expand...
Click to collapse
Most likely soft brick. But who knows, hard bricks even happen when they never touched anything for some people.
TechnoSparks said:
Most likely soft brick. But who knows, hard bricks even happen when they never touched anything for some people.
Click to expand...
Click to collapse
okay. Is there any way to install TWRP without PC then ?
or any custom recovery. philz, CWM anything
Install a terminal emulator by Jake Pelvich from Play store.
Extract the official TWRP img from the TWRP fota zip, or, if you already downloaded an official img, put it into the root of your internal storage.
For ease of access, but still mnemonic, rename the img into "twrp.img"
Open your terminal emulator, and enter "su" and run. This will make the terminal to request root, as you're elevating the shell into root.
Now, we "dd" the TWRP image into your FOTA partition. Copy and run the following:
Code:
dd if=/storage/emulated/0/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel bs=4096
Reboot to check if recovery is accessible after hitting volume up when LED lights up
TechnoSparks said:
Install a terminal emulator by Jake Pelvich from Play store.
Extract the official TWRP img from the TWRP fota zip, or, if you already downloaded an official img, put it into the root of your internal storage.
For ease of access, but still mnemonic, rename the img into "twrp.img"
Open your terminal emulator, and enter "su" and run. This will make the terminal to request root, as you're elevating the shell into root.
Now, we "dd" the TWRP image into your FOTA partition. Copy and run the following:
Reboot to check if recovery is accessible after hitting volume up when LED lights up
Click to expand...
Click to collapse
Thanks a lot. Maybe it works. But how to boot into recovery ?
explain me please.
rhrokib said:
Thanks a lot. Maybe it works. But how to boot into recovery ?
explain me please.
Click to expand...
Click to collapse
Like already mentioned, press volume button UP when the LED lights up during your XSP bootup
TechnoSparks said:
Like already mentioned, press volume button UP when the LED lights up during your XSP bootup
Click to expand...
Click to collapse
There is no LED during bootup. Either I didn't understand. I tried with software to boot into recovery. But my device just complete a reboot everytime. What to do ?
rhrokib said:
There is no LED during bootup. Either I didn't understand. I tried with software to boot into recovery. But my device just complete a reboot everytime. What to do ?
Click to expand...
Click to collapse
What ROM are you using? You need a ROM that can boot a FOTAKernel recovery, and not all of them can (especially stock based ones, since stock by default doesn't allow this).
Ditto.
If you are not using a ROM that supports booting from TWRP, then I can't suggest a method to install other recoveries without a PC.
I do not say it is impossible though, but it'll take a lot of brain power, and moderate understanding of shell scripting in order to reverse engineer the other recoveries provided in the dev subforum.
TechnoSparks said:
Ditto.
If you are not using a ROM that supports booting from TWRP, then I can't suggest a method to install other recoveries without a PC.
I do not say it is impossible though, but it'll take a lot of brain power, and moderate understanding of shell scripting in order to reverse engineer the other recoveries provided in the dev subforum.
Click to expand...
Click to collapse
I tried with Terminal Emulator and it seems okay. But I can't boot into recovery. Tried a lot of process. Doesn't work. Now can I install TWRP with pc ? or I need to flash my stock back to install from PC as I replaced my stock img file ?
Again if I flash stock now, will my bootloader be locked again ?
rhrokib said:
I tried with Terminal Emulator and it seems okay. But I can't boot into recovery. Tried a lot of process. Doesn't work. Now can I install TWRP with pc ? or I need to flash my stock back to install from PC as I replaced my stock img file ?
Again if I flash stock now, will my bootloader be locked again ?
Click to expand...
Click to collapse
Like already explained by Tomoms and me, you need a ROM that supports booting recovery from the FOTA partition in order for my explained method to work. You didn't also tell us which ROM you are using.
No, you dont need to flash your stock back. Leaving the FOTA partition replaced does no absolute harm at all.
If you flash stock, your bootloader will still remain unlocked. In order to relock, you will need to explicitly relock it, by using the relock bootloader option provided by flashtool. If you backed up your TA partition, restoring it will automatically relock your bootloader.
TechnoSparks said:
Like already explained by Tomoms and me, you need a ROM that supports booting recovery from the FOTA partition in order for my explained method to work. You didn't also tell us which ROM you are using.
No, you dont need to flash your stock back. Leaving the FOTA partition replaced does no absolute harm at all.
If you flash stock, your bootloader will still remain unlocked. In order to relock, you will need to explicitly relock it, by using the relock bootloader option provided by flashtool. If you backed up your TA partition, restoring it will automatically relock your bootloader.
Click to expand...
Click to collapse
Okay thanks everyone. I finally installed TWRP, CWM as well as Philz.
I was using 4.3 Stock. Finally installed those from Doomlord's thread. That was really handy to use.
again thank you all for supporting me.
rhrokib said:
Okay thanks everyone. I finally installed TWRP, CWM as well as Philz.
I was using 4.3 Stock. Finally installed those from Doomlord's thread. That was really handy to use.
again thank you all for supporting me.
Click to expand...
Click to collapse
Alright, good to know you finally installed the recoveries. 4.3 Stock ROM does not support my method explained in my recent post. And no problem!
SOLVED - See second post
-----------------------------------------
Hi there, I'm big trouble.
I have a F8131 with unlocked bootloader. The system was on the latest Oreo.
I tried to flash the latest TWRP using flashtool. After it finished, I get a bootloop, which goes through the unlocked warning to the Sony screen again and again.
What should I do now? Thanks to you all for helping in any way possible!
EDIT: I reflashed TWRP from command line using flashboot and now I can get to TWRP, but now it tells me there is no OS installed (WTF?), so if reboot I go back to the bootloop. Should I try to flash a rom from TWRP, is there something I am missing?
Luckily I was able to solve the issue. I will leave this here in case someone is stuck in the same situation.
1) Use Flashtool in flashmode to flash the FTF firmware you get from XperiFirm into the phone. If you get an error related to drivers, use the Flashtool drivers tool (located in a subfolder in the Flashtool installation folder) to install a set of working drivers (also applies to flashboot drivers).
2) After flashing, disconnect the phone and reconnect it in flashboot mode. Flash TWRP through fastboot commands in a cmd terminal. Flash a boot.img if you have one.
3) This should work, and you should be able to continue to boot your phone or get into TWRP to flash custom packages (Safety, DRM fixes, Magisk, etc) or ROMs.
leandrox said:
Luckily I was able to solve the issue. I will leave this here in case someone is stuck in the same situation.
1) Use Flashtool in flashmode to flash the FTF firmware you get from XperiFirm into the phone. If you get an error related to drivers, use the Flashtool drivers tool (located in a subfolder in the Flashtool installation folder) to install a set of working drivers (also applies to flashboot drivers).
2) After flashing, disconnect the phone and reconnect it in flashboot mode. Flash TWRP through fastboot commands in a cmd terminal. Flash a boot.img if you have one.
3) This should work, and you should be able to continue to boot your phone or get into TWRP to flash custom packages (Safety, DRM fixes, Magisk, etc) or ROMs.
Click to expand...
Click to collapse
um, i need assistance with this
can you help me with it?
velva said:
um, i need assistance with this
can you help me with it?
Click to expand...
Click to collapse
Sure. Where are you at right now?
leandrox said:
Sure. Where are you at right now?
Click to expand...
Click to collapse
About drm fix, is it the same file all phone could use? Or is it special, like TA images? I walk around xda, and somehow i am still not understand.
hasbyduryea said:
About drm fix, is it the same file all phone could use? Or is it special, like TA images? I walk around xda, and somehow i am still not understand.
Click to expand...
Click to collapse
I used the one available at posts with tutorials for installing Kernel + TWRP + Roms for my device. I am not sure whether the drmfix is the same for all Sony Xperia devices.
Nevertheless, I don't think it worked for me, as my keys don't look like they have been recovered when I check them. I haven't noticed any problems so far, though, so maybe it's not a big deal.