Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
mrbix said:
Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
Click to expand...
Click to collapse
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
mrbix said:
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
Click to expand...
Click to collapse
correct driver installation was a bit difficult also for me. good to know you solved the problem
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thank you. I had the same issue as OP, Google found me this thread and using flashtool 0.9.20.0 worked.
Related
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
AronR said:
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
I did this a week ago, and what a carry on I had, I thought i bust my tablet
I downgraded to .370 version using official firmware with flashtool, then I rooted using DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit (this is the easy part)
Then I used .109 version firmware (stripped ftf and flashable zip) - this is where it went wrong as I got into a boot loop
http://forum.xda-developers.com/showthread.php?t=2671276
I used both DE versions (German) for the flash/install - still works on UK tablet
I think there is a specific order to install busybox before or after dual recovery - this might be where it went wrong for me.
I also used an older version of dual recovery, (TabZ-lockeddualrecovery2.7.94-BETA.installer) and have yet to flash to the latest version
Sorry this is a bit muddled.
I just got my tab a couple days ago I guess I screwed up upgrading from 370 to 109. Following along closely to this thread
Sent from my SGP311 using Tapatalk
This is a guide that I wrote to enable root on Android version 4.3, build number 10.4.1.B.0.109 for SGP311. Follow at your own risk. I will not be responsible for damage to your Xperia Tablet Z! I am going by memory and XDA posts I have re-read.
Please read this first then follow the steps!!
1. Firstly you need to ensure you have the drivers installed for your tablet, so you could install Sony PC Companion http://www.sonymobile.com/gb/tools/pc-companion/
2. On your tablet make sure that Developer options is enabled (if not, press About tablet in the tablet settings menu several times), USB debugging is ticked and Verify apps over USB. Also turn on Unknown sources in Security settings
3. Assuming that the tablet is running version 10.4.1.B.0.109 you need to downgrade to version.370
4. Download and install Flashtool by @Androxyde http://www.flashtool.net/download.php - install this to your C: drive
5. Download the official .370 (I used SGP311_10.1.C.0.370 DE_Unbranded.ftf) firmware from here http://forum.xda-developers.com/showthread.php?t=2402863 thanks to @DevMark. This file should be placed inside the firmwares folder of Flashtool and thanks to @ donedos for his initial suggestion
6. Download the rooting kit from http://forum.xda-developers.com/showthread.php?t=2333566. Thanks to @DooMLoRD
7. It is suggested that a backup is carried out on the tablet as this flash/root will wipe the data from it – I never did this, as I was quite happy to install apps/.apk again, and I had a lot of crap on my tablet anyway
8. Open up Flashtool, power off the tablet, and plug the usb cable into the tablet.
9. With the tablet still turned off press the volume down button, and plug the usb cable into your PC, this should get your tablet into flash mode
10. There is a lightning bolt symbol on top left corner of Flashtool, click this, and two options should pop up. I think you click the top one; if so, you will be prompted to locate the .ftf file, select the .370 file. If this file is not visible, you probably need to select the second option that popped up!
11. The tablet should be flashing now, and takes a few minutes or so. Instructions will appear in Flashtool to unplug and power on your device.
12. It will take a while for your tablet to turn back on; when it does you might need to carry out the actions again in 2. above. Just make sure you are running firmware .370 now instead of .109
13. Now connect you tablet again to USB, device drivers might install again. Open up/extract DooMLoRD_Easy-Rooting-Toolkit_v17 and click the runme_win.bat file and follow the instructions – your tablet should now be rooted. Check for the Super SU app in your app list, or if it’s not there install from Play Store.
14. Download the file Xperia Tablet Z (SGP311) 10.4.1.B.0.109 VMo De from here http://forum.xda-developers.com/showthread.php?t=2671276, thanks goes to @bernddi . Extract the file so there are two files (SGP311_10.4.1.B.0.109_VMo De_stripped.ftf and SGP311_10.4.1.B.0.109_VMo De.zip)
15. Download and use this file http://www.winmd5.com/ to verify the md5 checksum matches the .109 files you downloaded.
16. If everything is okay, place the large zip file onto the root of your external memory card, and the .ftf file into the firmwares folder of Flashtool (later on don’t mix this file up with the .370 file)
17. Download the correct version of XZDualRecovery file for your tablet, – thanks to @[NUT]. I first tried the most recent version, but had problems with flash and root, so then I tried the older version TabZ-lockeddualrecovery2.7.86-BETA.installer. Files are linked from here http://forum.xda-developers.com/showthread.php?t=2261606.
18. Download and Install BusyBox from the Playstore, and run the app, then install again to your Tablet (using default options I believe) – this install failed first time for me, if same happends with you try again until it works
19. Connect your .370 rooted tablet to your PC, and run the DualRecovery file by clicking on install.bat – this will install the recovery to your tablet
20. Your tablet should power back on, or you’ll need to turn it on yourself. Make sure stuff works fine, you might need to carry out No. 2 again, I’m not sure
21. You should also have a file called NDR Utils on your tablet, if not install from the PlayStore, and run this. The option to boot into Philz Touch Recovery should be visible, select this option and reboot. You can reboot by pressing power up, while the tablet is turning on, but I have problems getting this to work. NDR makes it much easier
This is where it might get risky. It appears that the older version of DualRecovery does not have the option to verify the md5 checksum, but if the file winmd5free said the numbers match you should be okay
22. In recovery you need to select Install Zip, then select install zip from storage/sdcard1, then go to the zip file, and press it. The flashing of version .109 should begin – it takes a while
23. After the flash you must power off the device, DO NOT reboot
I believe this is where I got into a boot loop, and I am not certain how I got out of it. This link might help http://forum.xda-developers.com/showthread.php?t=2703882. Thanks to @Cat McGowan. When I finally got out of the boot loop, I started all over again from step No.8!
24. Open up Flashtool again, and flash the stripped ftf file like you did in No. 9 and No. 10
25. Follow the instructions to disconnect and power on your tablet, you should now have version .109 and still be rooted after the initial setting up of the tablet.
Please let this work!
If there is anyone reading this that spots an error or omission please post it
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
cirovi said:
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
Some root apps and recovery need it.
Sent from my SGP311 using Tapatalk
cirovi said:
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
actually it is already integrated in recovery package (/xbin/busybox), so there is no need to install it manually.
Well my tab went tits up a little while back, and I followed my guide and it worked
worked perfect for me... thank you very much
Help Needed
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
---------- Post added at 11:25 PM ---------- Previous post was at 11:16 PM ----------
CentinelX said:
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Ok I managed to get out and install 370 again. But where did I go wrong?
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Hello guys, any ideas? Thanks!
jakeortega said:
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Click to expand...
Click to collapse
Hello guys, any ideas? Thanks!
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
es0tericcha0s said:
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
Click to expand...
Click to collapse
Thank you es0tericcha0s for this information.
What I'm trying to do right now is updating my SHV-e160s from 4.0.4 to 4.1.2 using Kies v2.6. Unfortunately, I'm getting this error "Failed to run firmware upgrade: unknown error.". Until now, I'm afraid to update my firmware manually as I don't have much knowledge to do that.
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Alright, I'll try these steps immediately and will comeback for the result. Thanks again.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Hello, sorry I forgot to ask, will this root my device? I'm afraid I might bricked it.
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
es0tericcha0s said:
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
Click to expand...
Click to collapse
Hello again es0tericcha0s, I haven't tried the instructions that you gave me yesterday as I'm still downloading the firmware, last night I encountered an issue after enabling my Bluetooth, something like "NFC Service has stopped." just keeps on popping up. So I turned off the bluetooth then restarted my phone, it went well for a while.
After that, I enabled my 3G Cellular Data to check what was NFC service error is, after a few minutes, I lost my signal, phone turned to No Service, then in Settings -> About Phone, I got an Unknown Baseband.
EDIT
I got No Service since last night up until now.
EDIT Oct. 13, 2015 9:49 AM +08:00 Manila Time
I manage to update my phone from ICS 4.0.4 to JB 4.1.2. But still, my baseband is Unknown and I have no signal.
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
es0tericcha0s said:
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
Click to expand...
Click to collapse
I also though of that, hopefully not.
When I first got the phone, my gf sent me our pictures via bluetooth , no issues occured. After a while, I noticed that there are so many photos of the previous owner (around 1000+) and mp3s (around 1000+ also). So I connected the phone via usb to my pc and deleted all those pictures and mp3s inside the My Computer -> SHV-E160S -> Phone (Computer\SHV-E160S\Phone). After doing so, I started to encouter some issues, when enabling the bluetooth, the phone hangs and reboots then the error 'NFC service has stopped' keeps on popping up, until it went Unknown Baseband.
Now, the phone keeps on rebooting similar to the symptoms that it gets when baseband version is unknown.
I'm looking for solutions to fix the unknown baseband and saw the Back up and Restore EFS, I just need to root the device to try this fix. Maybe I'll post an update whether if I manage to solve this problem or not, if it didn't fix the issue then maybe the problem is the baseband chip. what a crap!
This is my reference for the EFS Fix
http://techbeasts.com/2014/07/13/fix-samsung-galaxy-unknown-baseband-version-guide/
Thanks!
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
es0tericcha0s said:
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
Click to expand...
Click to collapse
So I need to install TWRP first before rooting the device? Also I'm planning to use a rooted stock firmware which is 4.1.2, I just don't know the difference between UH24 and MH2, I've read that UH24 is already old and it's better to use a MH2 build and what is the Recovery UH24/MH2?
EDIT:
I forgot, I cannot check my current Baseband since it is still unknown.
EDIT: 12:30PM +8:00
I managed to get my Build#, it is MH2, I'm currently looking for a rooted 4.1.2 MH2 download link.
Way faster and easier to use the method I outlined, but either way should work.
es0tericcha0s said:
Way faster and easier to use the method I outlined, but either way should work.
Click to expand...
Click to collapse
Sorry, I'm really a root virgin here. While following your advise, I'm also currently looking at this guide -> http://forum.xda-developers.com/showthread.php?t=1924535. I'm done downloading Tegrak for MH2, a small problem I encountered here is I don't have a folder named 'sdcard' in my phone, so I created one and copied the 'Kernel' .zip, also I copied it to usbStorage folder.
I'm about to flash the 'Recovery' .tar to my phone. Hoping a success result
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
es0tericcha0s said:
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
Click to expand...
Click to collapse
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
jakeortega said:
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
Click to expand...
Click to collapse
Finally! I'm done rooting my phone, though I encountered another issues again. My Menu Button and Back Button does not work.
UPDATE: 4:08PM +8:00GMT
I think I found the problem as to why my Menu button and Back button doesn't work. I'v check my Baseband and it is -> E160SKSJMH1 and my Build # is -> JZO54K.E160SKSJMH2. Am I using a wrong FW as supposed to what I should be using? Which build should I install, the MH1 or the MH2?
Also, the Tegrak Kernel I've used is Build 48 for SHV-E160S MH2. I've also tried factory resetting the phone but the issue still exists.
Thanks!
UPDATE: 4:41PM +8:00GMT
Managed to fixed the issue by updating my Touch Firmware. Cool!
Hey folks. I'm in need of some help, but need to provide some background info as it seems there might be a few ways to correct this.
Background
I had a recent bad Nandroid mess up a restore process which somehow led to me losing root. I was on XDABBEB's 47A stock rooted ROM for months, then went to try the 3.1.1 ROM recently. I found that I wanted to go back, then BOOM! Bad restore from my data NANDROID. Then I:
Got stuck in a boot loop.
Rebooted into recovery
Saw the LG Recovery
(Stupidly?) chose to wipe cache
Continued to boot from LG Recovery
Went immediately to TWRP
Wiped Data and caches
Rebooted
At this point, I got back into 47A, but obviously without any data. I soon found that, though SuperSU was installed, it wasn't working:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-rot - consult the relevant forums for your device!
Click to expand...
Click to collapse
At this point, I checked Root Checker app and, surely enough, it says I wasn't rooted.
I checked ADB and tried to su from the prompt ($) and
Code:
su: notfound
However, adb reboot recovery brings me to TWRP
I tried TOT'ing on my Windows 10 (x64) machine, but it wasn't working:
PID: FAIL
IMEI: Unknown
[23:59: 0] CrossDL [Unknown] to [VS985].SW ***The text on this line continues, but I can't read it***
00000064
Error: [23:59: 0] CrossDL [Unknown] to [VS985].
Click to expand...
Click to collapse
I'm lucky in that my phone is currently working fine. I'm on 47a with everything working fine ... just not rooted, which I would really like to be.
So, my question is, what should I do next? I know some options that I have, I just don't know what options I should try or in what order I should try them...I understand some of the jargon and background info, but I don't understand the true inner workings of rooting and therefore don't feel comfortable making these choices on my own.
So, to all of you people that are way more intelligent at this than I am...
Should I try restoring my rooted 49A backup from TWRP?
Should I try to flash SU binaries in TWRP?
Should I TOT from my work machine that is Windows 7?
Should I KDZ on Windows 10?
Thanks in advance for your collective help.
This inquiring mind wants to know!
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone. In that case, you must flash back to 10B via the TOT method. That way, you can then root with Stump and then install TWRP, flash the correct boot images, and then reflash XDEBs ROM.
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method. It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
iBolski said:
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone
Click to expand...
Click to collapse
Correct. xdebbeb's stock 47A on a non-K model
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method.
Click to expand...
Click to collapse
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
Click to expand...
Click to collapse
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
my.ads0 said:
Correct. xdebbeb's stock 47A on a non-K model
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
Click to expand...
Click to collapse
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
iBolski said:
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
Click to expand...
Click to collapse
I just want to make sure that you're aware that I am NOT on pure stock 47A. I'm on xdabbeb_stock_vs98547a.zip from here.
When I flashed back from his 3.1.1 ROM, I flashed to my backup of the above ROM, which had Root. The SYSTEM flash from my nandroid back to his version of 47A worked without incident, but the DATA flash of my nandroid failed, left me in a bootloop, after which I performed the actions outlined in my original post. That squarely left where I am now, with no root, but on his version of 47A (I never had the stock 47A on my device before) with TWRP as my recovery.
In the end, I'm game for trying different things, but ideally, I'd like to try the least invasive method (trying to flash SuperSU in TWRP?; trying to flash my xdabebb 3.1.1 version?) ) before trying any other method or going to the extreme method (TOT'ing). I just am trying to avoid TOT'ing since my phone IS working AND the fact that I would have to do that at work. It would suck to go from a working phone to a broken phone without being able to fix it without knowing that I tried all of the least invasive methods first. I just need guidance from people like you as to what will or won't work in my situation.
The reason for this post is that I wasn't sure that you were aware I wasn't on pure stock 47A, but on xdabebb's version, which maybe you had overlooked and offered me more options? If you were aware of that and everything above is irrelevant, then I'm cool with that. Just tell me so. I just didn't want that fact overlooked.
Thanks again for entertaining my inquisitiveness, iBolski.
Well, trying to install the SuperSU binary zip from TWRP didn't work. That got me flashing blue & red lights. I tried restoring my XDABEBB 49A 3.1.1 install and that didn't help either. Both TOT & KDZ methods are failing on my PC (Windows 10) with both not able to read the phone properly (can't see imei). I will maybe try to uninstall the drivers or just wait until Monday to try my windows 7 machine at work.
Oops.
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
my.ads0 said:
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
Click to expand...
Click to collapse
Awesome. I saw your earlier post about being on XDEBB but that didn't matter. You were at a point that flashing back to 10b was your best option to get back to XDEB. That's why I kept saying you needed to flash back to 10B if you wanted to get back on XDEBB because where you were at that point was messed up, so it was just best to flash to 10b clean.
Glad you got it all worked out!
I've been having issues with battery drain and recently some apps aren't notifying me so I know it's time for a back up and restore. I figured since Nougat is out and seems to be tweaked to a working version, I might as well just flash that. (I haven't gotten the update yet w/ E583 UK version.)
I'm a TOTAL noob when it comes to flashing and resetting - I rooted a Samsung previously but never modded my Z5C at all. I need a good guide for how to flash the rom and do everything I need to do to back up/restore/flash a new ROM.
At the moment, I'm downloading FlashTool 0.9.23.1 but need to know where to get an official version of .376 or .378. I am coming from 32.2.A.0.305 Android 6.0.1 unmodded and don't need to root. TIA!
I really wish there was a step-by-step guide for this. Been trying to parse steps together but: Flashtool gives me error when I try to decrypt files. (tried to get from XperiFirm but it kept erroring on downloads. I walked away and didn't get any error messages so assume it worked but maybe not.) I really just need the regular ftf file but don't know where the most reliable one is. Got one from somewhere but didn't try that one. Flashtool won't recognize my device but I might have figured that out from using Xperia Companion. Companion says my phone is up to date so I'm just repairing it from there and reinstalling my current os. (6.0.1 I guess) Still would like the latest Nougat though.
Follow this guide [Guide] How to root Z5C - the new, less painful way (using dirtycow exploit), start at step 3 and end with step 5 and you should be good. You don't need to unlock the bootloader to flash an official ROM so skip any of the other steps.
-flashed TWRP 3.5
-flashed LineageOS 18.1 - worked!
-then tried to encrypt the phone - now stuck in a bootloop
I can get into TWRP and re-flash LineageOS, but it's still stuck in the bootloop.
How do I get the phone working again?
I tried: flashing cache, system, data, internal storage, and calvik but still stuck in the bootloop
Any ideas would be much appreciated. Thank you!
Edit: is this FTF and FlashTool the correct way to fix this? https://techbeasts.com/how-fix-sony-xperia-bootloop-issue-bootloader-unlock/
arkadione said:
Edit: is this FTF and FlashTool the correct way to fix this? https://techbeasts.com/how-fix-sony-xperia-bootloop-issue-bootloader-unlock/
Click to expand...
Click to collapse
I used for unlocking in 2015 the xperia flashtool but it doesn't seem to work properly under win10.
Last year I flashed my phone via the Sony flashtool "Emma". If you're using this it will automatically recognize the phone in flashmode and show possible images for download and flash.
It could be hard to get the drivers set up right under win 10. I suggest to do this on an device running win 7 or older. I got it somehow running under win 10 but i can not reproduce how it finally worked. Maybe it works out of the box with Emma. I was struggling with flashtool and finally trying with Emma it worked with my bugged driver setup.
But i don't know if it is possible to get rid of the encryption that way (flashing an original system image) but i am assuming it should work and seems like the last option you have.
uncle-sam said:
But i don't know if it is possible to get rid of the encryption that way (flashing an original system image) but i am assuming it should work and seems like the last option you have.
Click to expand...
Click to collapse
Thank you! I will try tonight. I only have a Windows 10 system to use ( and lots of linux systems) so I'll just have to try and make it work.
I don't think the encryption actually worked. it just crashed. i didn't realize that the LOS18 rom didn't support encryption, a stupid stupid mistake that is going to cost me lots of time now. note for other newbies: never enable encryption!
thanks for confirming what my next steps should be.
arkadione said:
Thank you! I will try tonight. I only have a Windows 10 system to use ( and lots of linux systems) so I'll just have to try and make it work.
I don't think the encryption actually worked. it just crashed. i didn't realize that the LOS18 rom didn't support encryption, a stupid stupid mistake that is going to cost me lots of time now. note for other newbies: never enable encryption!
thanks for confirming what my next steps should be.
Click to expand...
Click to collapse
I wish you good luck! If you get Emma working out of the box please report. This would give me a better feeling about playing around with this phone.
I know there is a Linux version of flashtool. I don't know if it is still supported and possible to get all required packages. I didn't got it running under ubuntu.
report so far: not going well
-tried FlashTool 0.33 by Androxyde in Linux (Kubuntu 20.04)
Code:
Error: dl failure on line 534
Error: failed /home/elias/Desktop/FlashTool/x10flasher_native/jre/lib/server/libjvm.so, because /lib/x86_64-linux-
gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/elias/Desktop/FlashTool/x10flasher_native/jre/lib
/server/libjvm.so)
-tried FlashTool 0.30 but when i plug in my phone and put it into flashmode, nothing flashes, and phone reboots after 1 minute back into the bootloop
-now tried through TWRP again: formatted, wiped everything, putting LOS18 back on there and it magically works..crisis averted! I thought about doing this after this person said this https://forum.xda-developers.com/t/...os-18-1-for-z5c-suzuran.4205135/post-84604389
arkadione said:
report so far: not going well
-tried FlashTool 0.33 by Androxyde in Linux (Kubuntu 20.04)
Code:
Error: dl failure on line 534
Error: failed /home/elias/Desktop/FlashTool/x10flasher_native/jre/lib/server/libjvm.so, because /lib/x86_64-linux-
gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/elias/Desktop/FlashTool/x10flasher_native/jre/lib
/server/libjvm.so)
-tried FlashTool 0.30 but when i plug in my phone and put it into flashmode, nothing flashes, and phone reboots after 1 minute back into the bootloop
-now tried through TWRP again: formatted, wiped everything, putting LOS18 back on there and it magically works..crisis averted! I thought about doing this after this person said this https://forum.xda-developers.com/t/...os-18-1-for-z5c-suzuran.4205135/post-84604389
Click to expand...
Click to collapse
I had the same experience under Windows with the one min reboot. I think this is driver related. I always have this reboots with flashtool. Only with Emma the phone stays in flashmode.
Congratulations. So you don't have to worry about flashtool anymore.
arkadione said:
note for other newbies: never enable encryption!
Click to expand...
Click to collapse
Encryption should work now: "cryptfs: Fix legacy QCOM HW FDE encryption"
Latest ROM: Klick
Berni-0815 said:
Encryption should work now: "cryptfs: Fix legacy QCOM HW FDE encryption"
Latest ROM: Klick
Click to expand...
Click to collapse
oh really. now i'm tempted to try it again. hmm...
As I've written: It should work! There is absolutely no guarantee!