Related
Guys,
Would you mind to write up a tutorial how you root your DHD ?
I'm a newbie for android and i have no idea.. been trying to read articles and i still cant understand.
I have downloaded the file called dhd_root.zip and now what ?
some people are mentioning about the gscript and blar blar blar.. what is all that about??
i have no idea what to do now... please help..
*please do not flame me for not using the search function as i read few of them and i do not understand at all*
Thanks
I personally used Evostance's guide, it was very simple and easy to follow: http://forum.xda-developers.com/showthread.php?t=834427
That's the link. I do believe there are simpler methods now using Visionary. Just check the Development sub-forum and they have more tutorials there
Sylpher said:
I personally used Evostance's guide, it was very simple and easy to follow: http://forum.xda-developers.com/showthread.php?t=834427
That's the link. I do believe there are simpler methods now using Visionary. Just check the Development sub-forum and they have more tutorials there
Click to expand...
Click to collapse
Hey Sylpher,
I did tried to read Evostance's guide but where is the guide?
Step By Step Guide - Download link below
11/11/10 V2
http://www.multiupload.com/KK66WUNUWS
See the main thread for details on the root:
http://forum.xda-developers.com/showthread.php?t=805327 ----> i do not understand at all... all those code like listed below
Go to adb shell, switch to root (su) and do the following:
insmod /sdcard/wp-(version).ko
for example: insmod /sdcard/wp_g5ed1769.ko
This will disable wp (will be enabled on reboot though...)
dd if=/sdcard/hboot_eng.nb0 of=/dev/block/mmcblk0p18
This will install engineering hboot
totally confused.
The link that he provides includes all the files + the tutorial (in a PDF file). So yeah just download that first and it should be quite straightforward from there on.
Sylpher said:
The link that he provides includes all the files + the tutorial (in a PDF file). So yeah just download that first and it should be quite straightforward from there on.
Click to expand...
Click to collapse
Sylpher,
Thank you so much for the info (The link that he provides includes all the files + the tutorial (in a PDF file).
I have no idea there is a tutorial file inside the zip.
I will give it a go when i got home and then pm you after that.
Thanks again.
No problems
You can try this too, a member here compile it. http://hemorrdroids.net/overclock-undervolt-your-desire-hd/
if you dont already have a file explorer then download astro from market place
download visonary r12 from here and copy apk file to sd card on the phone and install from there
http://android.modaco.com/content/h...722/10-nov-r12-test-visionary-one-click-root/
download superuser from market place and install on the phone
make sure usb debuggging is enabled on the, also unkown sources is allowed phone(settings/applications/development)
run visionary and don not check any of the 3 box on the screen
run temp root and let it finish
then attempt perm root it will ask for super user permission, allow this and the phone should root and reboot
to test it has work down load adfree from market place and see if it runs, if it does you have full root
simples
nmyseteroious said:
You can try this too, a member here compile it. http://hemorrdroids.net/overclock-undervolt-your-desire-hd/
Click to expand...
Click to collapse
that's a really good tutorial. I think i'll follow that one when i decide to root and s-off my DHD.
SupremeBeaver said:
that's a really good tutorial. I think i'll follow that one when i decide to root and s-off my DHD.
Click to expand...
Click to collapse
Although I wouldn't recommend anyone to rush into the act of rooting their device, do bare in mind, that the exploit we are using to obtain root will be patched sooner or later, so whilst thinking about it I would be very wary of applying any future OTA upgrades as so you may find you once more have an unrootable device
HTC Thunderbolt Windows One Click Root
This is a simple batch file that will guide you in rooting your device.
It is pretty easy to follow along but please take your time and read everything. It has only been tested a few times so please report any errors or issues you find.
Huge thanks to NetForce-TX on IRC for testing along with helping, I owe you!
Also thanks to Jcase for guidance
TeamAndIRC and Captainkrtek (Me) are NOT responsible for any bricks, fires, or damaged/broken hardware due to this process
If you wish to read the batch files contents either open it with notepad or check the pastebin
Instructions are included in the file when running it along with where to get the necessary files.
Prerequisites:
Drivers Installed & Working
SDK Installed with ADB
Exploits.zip with contents extracted to your ADB dir
PG05IMG.zip
Downgrade RUU
A Thunderbolt running 605.6 or 605.9 Firmware
You can download the OneClickRoot here
I will update this from time to time if needed, If you have issues with the batch file please PM me on XDA or find me on irc.andirc.net #Thunderbolt.
I will not reply to your PM if you want me to help you root your phone!
UPDATE: If SU acts up (IE: Force closes) flash this via CWM
Reserved for Linux version
Wow, looks easy! But I'm glad I did it through ADB. Nice job!
pinhead875 said:
Wow, looks easy! But I'm glad I did it through ADB. Nice job!
Click to expand...
Click to collapse
Thanks! It is pretty simple, only a few things you have to do manually (no possible workaround) such as flashing from the bootloader.
Anyone try this yet?
sent using Tapatalk on the TB.
egeorgia said:
Anyone try this yet?
sent using Tapatalk on the TB.
Click to expand...
Click to collapse
Already a few people have tested it, all successes
so we set the phone to debug mode and the usb mode to just charging?
i was going to to the other root ;set up my ADB earlier but chickened out... i already have the files downloaded
Cg006 said:
so we set the phone to debug mode and the usb mode to just charging?
i was going to to the ot her root and set up my abd earlier but chickened out... i already have the files downloaded
Click to expand...
Click to collapse
Yeah exactly, just debug and charging, until you have to copy over the roms then you will set the USB mode to mount SD
I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?
alphatectz said:
I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?
Click to expand...
Click to collapse
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423
Captainkrtek said:
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Ok, I'll unroot and use the one click method. Thx
can we get a poll maybe to see success rate
Can we get a Step by Step Instruction Guide? it would be nice for us beginners
ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....
b33zy682 said:
ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....
Click to expand...
Click to collapse
You need to put the contents of exploits.zip in the same directory ADB is in
ok what in that zip needs to go where?
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
b33zy682 said:
ok what in that zip needs to go where?
Click to expand...
Click to collapse
take everything that is in exploits.zip and move it to your android sdk directory specifically the location of adb.exe (will either be in platform-tools or tools) as for the two RUUs, they can be anywhere but you will have to move them at one point to your SD card. That is about it
Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
Yes you should
Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
damn right! lol
hey guys!
im new with my Iconia A500. i just updated to 3.2 and found out it cant be rooted.
is there any new way of rooting it coming up without downgrading the software?
im currently on Acer_A500_7.006.03_COM_GEN1
mewan said:
hey guys!
im new with my Iconia A500. i just updated to 3.2 and found out it cant be rooted.
is there any new way of rooting it coming up without downgrading the software?
im currently on Acer_A500_7.006.03_COM_GEN1
Click to expand...
Click to collapse
Not yet. We have to wait and see.
By the way, how about a "call for dev" to the people who rooted A500 in the first place?
Not yet, but could use some help
I captured the update.zip and rooted it but can't get it to run. I'm not sure if it only works if the manufacturer signs the update.zip because I can only sign with a test certificate, trying to get this resolved.
I have to get these Iconia 500 rooted as it is fubar'ng our fleet. We root and install a sales/inventory/delivery system in /system/app and then un-root. Therefore employees can reset them all they want and not have to set them back up and they can wipe them clean of personal data when they leave the company without fubaring the company application. Deploying via the market place cannot be done (we only want employees using the app) and using 'unknown sources' isn't a solution. Plus, most of our employees easily wipe them clean all the time as they play around and learn them. Having the application in /system/app solves every one of these issues. The ACER's update nukes everything is system. Why would they not just modify their applications and leave mine alone?
Thanks to ACER, these folks just deleted out all of our applications and data because all the employees said 'yes/ok' to the update. Now who won't do that?
So, I've got several here for testing and welcome anyone's ideas because they are junk or I will have to flash them back to 3.1 and remove the ability to do updates.
Thanks
http://code.google.com/p/acer-a500/downloads/list
EDIT: changed to second set of four files (5-8)!
First 4 files on that page are a rared version of stock 3.2.
Open rar1 and it will unrar all 4. Flash the tablets with it, but I'm not sure you can unroot it afterwards?
CWM - Not loadable is it?
This uses the clockwork recovery doesn't it? You cannot load the CWM unless your have root??? What I really need is to be able to use the stock recovery.
So how do you use CWM without out rooting? Sort of a catch 22?
Now I could download to 3.1 and then install CWM and then apply the update using the modified CWM, but that sort of is a long way around isn't it?
timmyDean said:
This uses the clockwork recovery doesn't it? You cannot load the CWM unless your have root??? What I really need is to be able to use the stock recovery.
So how do you use CWM without out rooting? Sort of a catch 22?
Now I could download to 3.1 and then install CWM and then apply the update using the modified CWM, but that sort of is a long way around isn't it?
Click to expand...
Click to collapse
If you're already stuck on stock 3.2 it's your only option.
kjy2010 said:
First 4 files on that page are a rared version of stock 3.2.
Open rar1 and it will unrar all 4. Flash the tablets with it, but I'm not sure you can unroot it afterwards?
Click to expand...
Click to collapse
thanx alot bro!
im kinda new to this so...to flash the files i just paste it in my sd card as "update.zip" and then power off and then hold (power on) + (vol+)..then it should automatically happen right??
also i am currently on 3.2.. will it work?
mewan said:
thanx alot bro!
im kinda new to this so...to flash the files i just paste it in my sd card as "update.zip" and then power off and then hold (power on) + (vol+)..then it should automatically happen right??
also i am currently on 3.2.. will it work?
Click to expand...
Click to collapse
Ummm no lol, you'll have to go back to 3.1, root, cwm, and then update.
kjy2010 said:
Ummm no lol, you'll have to go back to 3.1, root, cwm, and then update.
Click to expand...
Click to collapse
ahh damn!!
i guess i gotta downgrade or just wait!
thanx alot man!!
kjy2010 said:
Ummm no lol, you'll have to go back to 3.1, root, cwm, and then update.
Click to expand...
Click to collapse
so is it possible for me to downgrade to 3.1 from 3.2 just by flashing the OTA 3.1 given in this post
[ http://forum.xda-developers.com/showthread.php?t=1113878 ]
using the default recovery?
Root for 3.2 can be done!!
From a post by eglathangion on the Developer’s Board:
Googling and surfing around the 'net, I found this repository.
Go to code.google.com/p/acer-a500/downloads/list
The latest filelist shows:
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part1.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part2.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part3.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part4.rar
My remarks on what I did when tried this out and it worked!
1.I downloaded the (4) files, extracted them to a new folder as .zip files.
2.Copied to my ext-sdcard in a folder
3. After the (4) files were installed as described above, I then booted into Recovery and installed each one individually. After each file I DID NOT "Reboot system now", but rather chose to install the next .zip until all (4) were installed.
4. Rebooted system. All my apps were still there. The only things I did have to do is root with Iconia Root app, install Superuser and set up my e-mail accounts again. When I ran an app that required root access, I simply had to allow access with Superuser.
Everything else was there as it was before the install and everything is working great. ! Did this 3 days ago and no issues!
so, can i download these 4 files, extract into the 1 large file, put on my ext-sd renamed as update.zip and flash from clockwork?
bidniss said:
From a post by eglathangion on the Developer’s Board:
Googling and surfing around the 'net, I found this repository.
Go to code.google.com/p/acer-a500/downloads/list
The latest filelist shows:
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part1.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part2.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part3.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part4.rar
My remarks on what I did when tried this out and it worked!
1.I downloaded the (4) files, extracted them to a new folder as .zip files.
2.Copied to my ext-sdcard in a folder
3. After the (4) files were installed as described above, I then booted into Recovery and installed each one individually. After each file I DID NOT "Reboot system now", but rather chose to install the next .zip until all (4) were installed.
4. Rebooted system. All my apps were still there. The only things I did have to do is root with Iconia Root app, install Superuser and set up my e-mail accounts again. When I ran an app that required root access, I simply had to allow access with Superuser.
Everything else was there as it was before the install and everything is working great. ! Did this 3 days ago and no issues!
Click to expand...
Click to collapse
If anyone has success with this please post. Thank you.
bidniss said:
From a post by eglathangion on the Developer’s Board:
Googling and surfing around the 'net, I found this repository.
Go to code.google.com/p/acer-a500/downloads/list
The latest filelist shows:
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part1.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part2.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part3.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part4.rar
My remarks on what I did when tried this out and it worked!
1.I downloaded the (4) files, extracted them to a new folder as .zip files.
2.Copied to my ext-sdcard in a folder
3. After the (4) files were installed as described above, I then booted into Recovery and installed each one individually. After each file I DID NOT "Reboot system now", but rather chose to install the next .zip until all (4) were installed.
4. Rebooted system. All my apps were still there. The only things I did have to do is root with Iconia Root app, install Superuser and set up my e-mail accounts again. When I ran an app that required root access, I simply had to allow access with Superuser.
Everything else was there as it was before the install and everything is working great. ! Did this 3 days ago and no issues!
Click to expand...
Click to collapse
are you sure you are on the stock 3.2 recovery??
because as far as i know and correct me if im wrong, the 3.2 stock recovery does not give you the ability to chose which file you wish to flash. it just flashes the file "update.zip" file..
Also , just for clarification. If i do as previously mentioned to install this, will I still have clockwork recovery or will it flash he new Acer stock recovery?
bidniss said:
From a post by eglathangion on the Developer’s Board:
Googling and surfing around the 'net, I found this repository.
Go to code.google.com/p/acer-a500/downloads/list
The latest filelist shows:
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part1.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part2.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part3.rar
CWM_Root_Acer_A500_7.006.03_COM_GEN1.part4.rar
My remarks on what I did when tried this out and it worked!
1.I downloaded the (4) files, extracted them to a new folder as .zip files.
2.Copied to my ext-sdcard in a folder
3. After the (4) files were installed as described above, I then booted into Recovery and installed each one individually. After each file I DID NOT "Reboot system now", but rather chose to install the next .zip until all (4) were installed.
4. Rebooted system. All my apps were still there. The only things I did have to do is root with Iconia Root app, install Superuser and set up my e-mail accounts again. When I ran an app that required root access, I simply had to allow access with Superuser.
Everything else was there as it was before the install and everything is working great. ! Did this 3 days ago and no issues!
Click to expand...
Click to collapse
DO NOT listen to this post (1 post wonder).
First off those four files are rar files that once you begin the extraction, will extract themselves into one large file. There is no way to flash those four files seperately.
Second, root and su are included in that ROM, so no need to root (as indicated in the title of the files).
Please don't Brick your device by listening to these directions!
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
ichnach said:
so, can i download these 4 files, extract into the 1 large file, put on my ext-sd renamed as update.zip and flash from clockwork?
Click to expand...
Click to collapse
The answer to your question is YES, that's the proper way to install this ROM.
I gave the link to this on the previous page of this thread.
kjy2010 said:
DO NOT listen to this post (1 post wonder).
First off those four files are rar files that once you begin the extraction, will extract themselves into one large file. There is no way to flash those four files seperately.
Second, root and su are included in that ROM, so no need to root (as indicated in the title of the files).
Please don't Brick your device by listening to these directions!
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
The answer to your question is YES, that's the proper way to install this ROM.
I gave the link to this on the previous page of this thread.
Click to expand...
Click to collapse
Didn't work. Got stuck at the ACER screen.
mkomarinski said:
Didn't work. Got stuck at the ACER screen.
Click to expand...
Click to collapse
Pilot error then, explain your steps please?
mkomarinski said:
Didn't work. Got stuck at the ACER screen.
Click to expand...
Click to collapse
as far as i know, if you are on 3.2 already it wont work!
mewan said:
as far as i know, if you are on 3.2 already it wont work!
Click to expand...
Click to collapse
If he's trying to flash ROMs with stock 3.2 recovery, he needs to sell his tab and get an IPad before he bricks his tab lol
Hey friends! I was looking at this thread: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307 and I decided to create my own thread about the same topic, however this thread is much more simplified and is for those people who are new to rooting Xperia smartphones.
So without further ado here are the steps
Part One: downloading prerequisites
in order to flash .ftf firmware files to downgrade your phone to lollipop for TA backup you will need.
1. Java JDK :
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
2. XperiFirm(not neccesary if you plan to stay on LP)
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
3. Flashtool
http://www.flashtool.net/downloads.php
4. Android SDK
http://developer.android.com/sdk/index.html#downloads
5. iovyroot(not necessary if you do not want to backup DRM)
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
other prerequisites:
Patience
Mountain Dew or Starbucks
A small bit of knowledge on command line interfaces
Part Two: Downloading firmware
1. Open up XperiFirm
2. Select your device from the list
3. Select your model number(can be checked in Settings > about phone > Model Number
4. Pick your country and carrier(does'nt really matter, best firmware to use is UK customised and Singapore customised)
5. Click the latest release in 'available releases'
6. A dialogue should pop up, tick 'automatic unpack'
7. Wait for download to complete
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing
Part Three: Downgrading firmware
Download the firmware here: http://www.xperiablog.net/forum/resources/xperia-z5_e6653_32-0-a-6-152_central-europe-5_generic.477/
1. Place the file in c: Users/*account name*/.flashtool/firmwares
Open up Flashtool
2. Press the lightning bolt icon
3. Choose Flashmode and click ok
4. choose the firmware you downloaded(Do not choose the one you created)
5. Tick "user data" in the box at the top right hand corner
6. Press flash and wait
Part Four: DRM backup and unlock
1.Extract iovyroot
2. make sure USB debugging and unknown sources are enabled
3. Open up backupdrm.bat and wait
4. make sure there are no errors before proceeding(this usually takes a couple of tries)
5. IMPORTANT keep a safe online backup of your DRM keys.
6. Open up flashtool
7. click on BLU
8. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
9. Select your device and follow the instructions
9. after getting the unlock key, paste it inside the BLU dialogue in flashtool
10. wait, then profit!
11. now flash the .FTF that you created
12. boot your device into fastboot(plug in power cable and press vol down when your phone is switched off)
13. Download androplus kernel v23 and above from here: https://kernel.andro.plus/
14. Extract boot.img and put it in the android SDK inside of 'platform-tools'
15. Press shift+right click inside of the same folder
be sure to install xperia z5 fastboot drivers)
16. click 'open command window here'
17. run fastboot devices and make sure it detects your device
18. run this command here : fastboot flash boot boot.img
19. Reboot and DONE
Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.
gamer649 said:
Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.
Click to expand...
Click to collapse
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata
_LLJY said:
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata
Click to expand...
Click to collapse
Every other Sony phone I've owned (M, Z1 compact, Z2) refused to boot after a downgrade. The main thing to remember when downgrading is to take a backup before doing so to prevent data loss, I've experienced it myself firsthand so I know how stressful it can be.
In the TA backup part you should add a step to make sure the script actually worked and didn't stop with an error, before proceeding on to unlocking BL. I had to reboot my phone & run the script several times before successfully pulling it off.
Hello!
I'm new to the Sony family as you can see in my signature and I wouldn't call myself n00b, but the whole procedure with the extra partitions is so confusing! Thank you for trying to break it down!
the usual 3 step way (1 unlock bootloader, 2 flash recovery, 3 flash SuperSU) is still present but there are some other steps before them.
As i can understand, all the hassle is just for the backup of the TA partition.
I think that we must start with your step 3, just to avoid confusion such as the step 3.4. Please post a direct link to the firmware you suggest, I can't download it because it requires me to register there too.
Also, you should break the part 4 at the step 11. If I'm not mistaken, the order should be 1, 3, 4 (1-10), 2 , 2.5, 4 (11-19).
In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk
DeathStroke said:
In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Latest andro kernel have drm keys intergrated bro
working for e6633 dual ?
I had a doubt! On Part Three, can I use the given E6653 ftf for my E6683? Or I should download the .152 ftf for my exact device model i.e. E6683?
Help me bro @_LLJY
good guide
easy follow
had overheat problem i need help...!
any one please ?
updated from support ( device no pc)
after update full overheat on camera use
Can you guys please help me?
My friend got a 5803, I backed up his DRM keys and unlocked the bootloader but can't root it.
If someone could be so kind to help us it'll be great, I did it to my 6653 but for some reason I can't root this one.
Sent from my E6653 using XDA-Developers mobile app
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
Unpack firmware Ftf file with flashtool and see is there file called FWINFO.Delete this file and pack Ftf using Ftool and you will not have peoblems with flash.
Sent from my Sony Xperia Z5
Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?
feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
I did two things to try to fix this:
1: Use the previous version of flashtool (0.9.18.6) instead of the current one
2: Use the Software Repair function of Sony's Xperia Companion application
I don't know which of these helped (it might have been neither, actually) but in the end I was able to flash Lollipop 5.1.1 onto my Z5 and use iovyroot to back up the TA partition.
Hi, this is kind of off-topic but this is the best thread for this question I could find.
I was in a hurry to get rid of the bloated, horrible stock rom, and I did not back up my DRM keys. I did patch my current kernel with the DRM fix from another thread here at XDA. Now my question is:
What kind of functionality did I lose from this, except not being able to restore to stock and relocking bootloader?
klemen241 said:
Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?
Click to expand...
Click to collapse
Hello, look at this video:
h**ps:.youtube.com/watch?v=dTlosea6SJE
But at first, i installed at my Z5 the latest Kernal v36 and then i installed the TWRP 2.8.7.0, but i think you can install the newest TWRP too.
At last you install the SuperSu with TWRP, than you have full root!
Creating FTF not possible
hej,
i have a problem creating the FTF as described in Part 2.5:
-i downloaded the latest version via xperifirm (E6653_Customized DE_1298-3675_32.2.A.0.253_R3C)
-i deleted the fwinfo.xml & all .TA files from the folder
-flashtool is hanging here now:
-05/016/2016 09:16:25 - INFO - Streaming from file : C:\Users\hek\Desktop\Sony Xperia Z5\E6653_Customized DE_1298-3675_32.2.A.0.253_R3C\boot\boot_delivery.xml
05/016/2016 09:16:25 - INFO - Adding rpm_S1_Boot_MSM8994_LA1_2_2_40_AID_1_KITAKAMI-TEST-HWID009400E1-SWID0A-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
05/016/2016 09:16:25 - INFO - Adding Sumire_S1BootConfig_MiscTA.ta to the bundle
-tried it with singapore customized and german customized (¬ deleting the .TA-files & manually unselecting all TA files in flashtool)
what could be the issue here or is there another way to get the latest version on the phone after unlocking it?
or is it safe just to install the latest version as described here without deleting the .TA-files? (http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224)
thanks for any input!
--
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing
I used iovyroot and it created taxxxxxx.img that it has 2mb. I think so I read so time ago that taxxxxx.img had 500kb... Is it my ta wrong?? Or it's normal??
Thanks!
Enviado desde mi Z1 mediante Tapatalk
Why yet another guide? Why should you follow this guide?
This is more of a future reference for myself, but might be beneficial to some other people, hence why I decided to post it.
Thanks to the "dirty cow" exploit (CVE-2016-5195), we now have a more simple way of backing up the TA partition compared to existing guides, which all relied on another exploit that involved downgrading the firmware, thus making the whole process a bit more complicated.
Unfortunately, as you can probably tell, it's still not a painless ordeal, just "less" painful. But hey, at least you have a choice.
To keep this step-by-step walkthrough guide simple and straightforward, I am focusing on just the steps and skipping the explanations.
Let's get started!
Prerequisites
Important: Your phone must be vulnerable to the "dirty cow" exploit, any firmware version with security patch level 2016-12-01 or earlier should work, such as 32.2.A.5.11. Basically, any MM or LP firmware.
Currently there is no way of backing up the TA partition on Android 7.0 Nougat firmware, you will need to downgrade to MM or earlier firmware first.
Remember to backup all your data before you downgrade, since a downgrade is akin to a factory reset. Downgrade instructions:
Follow Step 0, skip Step 1 and 2
In Step 3, download a MM or LP version firmware. For the sake of simplicity, I suggest you download the one labeled Storefront.
Follow Step 4 and 5
Done, your phone is now downgraded, skip the remaining steps. Continue with the guide as usual from Step 1
Note: If the DRM keys are irrelevant to you (TA partition already backed up/restored/lost) and would just like to root, then you can root using this guide on all firmware versions including Android 7.0 Nougat without downgrading. In this case, you can skip Step 1 and Step 7. Depending on your situation, you can also skip other parts of this guide, such as Step 2 if your bootloader is already unlocked, or in Step 5 don't wipe anything (leave all boxes unchecked) to retain your apps and data for a firmware upgrade.
Computer setup with correct drivers and adb/fastboot connection ability.
Enable USB debugging on the phone:
Settings > About phone > Tap multiple times on Build number until Developer options is enabled
Settings > Developer options > USB debugging > Toggle ON
XperiFirm for downloading official Sony firmware directly from Sony's servers
Flashtool for flashing firmware
Battery preferably more than 80% remaining, loss of power while flashing can brick your phone
Step 0 - Backup your phone (optional)
Move all your data to your SD card using the native tool: Settings > Storage > Transfer data to SD card
Use Sony's Backup & restore app to make a backup: Settings > Backup & reset > Xperia Backup & restore > More > Manual backup > Select SD card > Select content to backup
Personally, I choose everything except apps, they can be re-downloaded from the Play Store at any time, plus they take a long time to backup and restore not to mention eats up free space
Step 1 - Backup the TA partition
Download this wonderful TA Backup tool, unzip to desired location
With the phone powered on, connect the USB cable to the computer, then plug the micro USB end to the phone
Open command prompt (Start > Run > cmd), navigate to the directory where you unzipped the TA Backup tool
Run the following command:
Code:
backupTA
The tool will run and if successful, you should see at the bottom the words "TA Successfully pulled to TA_E5823.img".
TA_E5823.img is the TA partition image file, actual filename will be longer and differ for everyone so to keep it simple we'll just refer to it as TA_E5823.img in this guide.
Please check that the file is 2,097,152 bytes. If not or file is missing, then the backup has failed.
If it fails, just run the tool again a few times, or try rebooting your phone then rerun the tool. If you just can't get it to work, seek help from the tool thread.
Step 2 - Unlock the boot loader
Visit Sony's website and follow the instructions carefully
Important: Pay attention to the warnings. No, really, unlocking the boot loader will wipe your DRM keys (hence the need to back them up in Step 1) and trigger a factory reset, erasing everything on your phone.
After you've successfully unlocked the boot loader, unplug your phone and leave it powered off
Step 3 - Download stock firmware
Run XperiFirm, locate the correct Xperia Z5 Compact version of your phone (E5803/E5823) and download the firmware of your choice.
General recommendation is to download the "Customized" version that's available for your country.
Step 4 - Create a FTF file from the firmware
Open Flashtool
Tools > Bundle > Create
Select source file > Locate the folder where you saved the firmware from XperiFirm in step 3 > You should see your device name appear automatically in Device and the folder list below populated
Branding > The same as Operator in XperiFirm, e.g. Customized AU
Version > The version you downloaded, e.g. 32.2.A.5.11
Hint: Both Branding and Version information is in the folder name
In folder list, select the first item, hold SHIFT and select the last item so that all items are highlighted, then click the "- >" button > The folder list should now be empty, and the Firmware content field populated
Click Create, if successful you will see "Bundle creation finished"
Note: The FTF file is saved to %userprofile%\.flashTool\firmwares by default
Step 5 - Flash the FTF file
Click the lightning symbol in Flashtool > Flashmode
Source folder should be pre-selected to the default location mentioned above and "Sony Xperia Z5 Compact" listed in Firmwares
Expand all the arrows and select the version number
Under Wipe/Sin check all options (APPS_LOG, DIAG, SSD, USERDATA), leave all other options unchecked
Click Flash, wait for an instruction prompt to pop up
Plug the USB cable to your computer if it isn't already plugged
Turn off your phone if it isn't powered off, hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Flashtool will begin flashing the firmware automatically. It can take a long time, 10~15 minutes is normal, wait until completed
Unplug your phone and do not power it on yet
Step 6 - Patch the kernel
Download this awesome rootkernel tool, unzip to desired location.
Extract the kernel image file kernel.sin from the FTF file using any file compression program such as 7zip, WinZip, WinRAR, etc.
Open Flashtool > Tools > Sin Editor > Sin file > Locate the kernel you just extracted > Click Extract data. You should now have a file named kernel.elf in the same folder
Copy kernel.elf to the rootkernel folder
Download the latest stable version of the SuperSU ZIP file and copy the entire ZIP file to the rootkernel folder. Do NOT unzip it!
Rename the SuperSU ZIP file name so that it starts with SuperSU (case sensitive) instead of UPDATE-SuperSU, e.g. SuperSU-v2.79-20161211114519.zip
Note: if you're patching Nougat firmware, you may want to use phh's superuser instead of SuperSU due to potential battery drain. See rootkernel thread for more info. If you use phh's superuser, you will need to install the apk from the Play store after Step 8.
(optional) Download the latest Xposed framework ZIP file and copy it to the rootkernel folder. Do NOT unzip it!
Note: this only works with rootkernel v5.0 or later, if you're using an earlier version of the rootkernel tool, skip this and skip Step 9
At time of this edit (2017/2/22), Xposed does not support Android 7.0 (Nougat), so if you're trying to patch a Nougat kernel, do not include xposed. You can check the official Xposed thread for latest announcements to see if it's supported
Open command prompt and navigate to the rootkernel directory
Enter the following command:
Code:
rootkernel kernel.elf boot.img
You will be prompted to make a series of choices, including whether you want to install SuperSU and Xposed. Type Y for all of them.
If you didn't see the prompt for SuperSU (required) or Xposed (optional), check the filename of the ZIP files. Remember they're case sensitive.
You should now have a boot.img file in the rootkernel folder, that is your rooted kernel
Step 7 - Flash the DRM keys (one-time procedure)
tobias.waldvogel (rootkernel developer) said:
Flashing this file with flashtool will write your device key to an alternative unit, from where the drmfix library will pick it up.
This is a one-time task. It will survive a complete reset of the phone or Android system upgrade.
Click to expand...
Click to collapse
Copy the TA backup file TA_E5823.img from Step 1 to the rootkernel folder, then enter the following command in command prompt:
Code:
flash_dk TA_E5823.img DK.ftf
This will create a DK.ftf file in the rootkernel folder
Open Flashtool > Click the lightning symbol > Flashmode > Source folder > Locate the rootkernel folder
"Sony Xperia Z5 Compact" should appear under Firmwares, expand the arrows until you see DeviceKey and 1.0. Select 1.0, click Flash and wait for an instruction prompt to pop up
Hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Wait until operation is completed, then unplug the cable from your phone. Do not power on yet
Step 8 - Flash the kernel
Hold the VOLUME UP button and plug in the micro USB cable. Wait until the LED indicator turns blue, then release the VOL UP button.
Enter the following command in command prompt to flash the rooted kernel:
Code:
fastboot flash boot boot.img
After completion, congratulations, you've successfully rooted your phone!
Now you can turn on your phone, the first boot will take a very long time to initialize, don't worry.
If you see the boot animation for more than 30 minutes, then it's time to worry. First try again from Step 6, and if you still can't complete boot, go up a step starting from Step 5. If that still fails, start over from Step 3.
Step 9 - Finish installation of Xposed (optional)
In Step 6, if you chose to include the Xposed ZIP file, which means you want to install Xposed, then there's one more step to complete the installation.
Download the unofficial Material Design Xposed Installer.
Currently, this is the only Xposed Installer that works with the systemless Xposed integration method used by the rootkernel tool. Using the official Xposed Installer will not work.
Go to Settings > Security > Unknown sources > Toggle ON
Copy the Xposed Installer apk to your phone and install it.
Done!
Personal list of xposed modules to install for self reference. This is in no way a recommendation list, your preferences will vary.
Amplify
Android Phone Vibrator
App Locale
BootManager
Disable Low Battery Notifications
DynamicAlarmIcon 2
HideBatteryLowAlert
Keep Trash (broken at the moment)
Lockscreen Album Art Remover
MinMinGuard
NeoPowerMenu
NoHeadsetNotification
Ringer and Notification Volume Unlink
RootCloak
Use USB for Marshmallow V 1.2
XperiaFMwoHS
Xposed Torch: Physical keys
Youtube AdAway
Bonus - How to unroot/fully restore DRM/return to 100% factory state
Thank you for taking the time to write this guide!
best guide for root, thanks!
Fantastic guide, Thank you very much for that!
I had trouble getting the latest version of flashtool (09231) to work (mac and PC). It froze when I was trying to create the new bundle.
After downloading the older version (09186) it worked without problems.
However, currently I am stuck at step 6, running cmd 'rootkernel kernel.elf boot.img':
I get the message:
Code:
Rootkernel V5.11
- Unpacking kernel
error: Android boot magic not found
Unknown boot image format
Aborting
UPDATE:
I found the reason for the img file creation failure.
I was not patient enough in copying the kernel.elf file over. While the flashtool says file with size X created it was still compiling and only a minute later or so finished writing the file. In other words, I copied over the 'unfinished' kernel.elf and that's what caused the issue.
Trying to boot now
Thanks again for this nice guide!
Cheers,
Malcolm
Hey Malcolm, did you manage to complete the process successfully?
good news
thanks for your help. very good tutorial, realy made easy to understand
successfully rooted my nougat z5c with this,
you the best thanks
brokich said:
Hey Malcolm, did you manage to complete the process successfully?
Click to expand...
Click to collapse
Hi Brokich,
Unfortunately not (yet).
After finishing step 7 my device is stuck at the bootloader
I've tried now several times re-flashing (steps 5-7) but unfortunately no luck yet...Will try to repeat the whole procedure over the next days again.
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Hello guys
On step 5 i get this error
5/031/2017 13:31:03 - INFO - Device connected in flash mode
05/031/2017 13:31:28 - INFO - Selected Bundle for Sony Xperia Z5 Compact(E5823). FW release : 1298-5497_32.2.A.5.11_R13C. Customization : Customized UK
05/031/2017 13:31:28 - INFO - Preparing files for flashing
05/033/2017 13:33:12 - INFO - Please connect your device into flashmode.
05/033/2017 13:33:13 - INFO - Opening device for R/W
05/033/2017 13:33:14 - INFO - Start Flashing
05/033/2017 13:33:14 - INFO - Processing loader.sin
05/033/2017 13:33:14 - INFO - Checking header
05/033/2017 13:33:14 - ERROR - Processing of loader.sin finished with errors.
05/033/2017 13:33:14 - INFO - Ending flash session
05/033/2017 13:33:14 - ERROR - null
05/033/2017 13:33:14 - ERROR - Error flashing. Aborted
05/033/2017 13:33:14 - INFO - Device connected in flash mode
Any idea why ?
notabene said:
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Click to expand...
Click to collapse
Did you backup your TA-partition before the bootloader status was unknown?
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
Yes, why?
---------- Post added at 01:13 PM ---------- Previous post was at 12:49 PM ----------
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
I was able to flash FTF file. But not the kernel.
notabene said:
yes.
Click to expand...
Click to collapse
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
zegovernator said:
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
Click to expand...
Click to collapse
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Bootloader unlock allowed : yes
Remote Lock state : UnLockd
Checked DRM all OK
notabene said:
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Click to expand...
Click to collapse
Flash a .tft from the MM version your backed up your TA image from. When flashing, ensure to tick everything under wipe except TA Misc.
Well finally was able to do all the steps, but phone wont boot. Stucked in Sony logo, led is yellow and then power off..
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Need to use phone tomorrow, how can i revert to stock for a while since I cannot do it throught Xperia companion?
---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------
Malcolm143 said:
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Click to expand...
Click to collapse
Did you use customized firmware? I did not, i used Tmobile CZ
Now with bootloader unlocked even PC Companion doesnt work..
So the problem is after flashing custom kernel with rootkernel+DRM fix.
So after hours of trying from step 5 with different settings for kernel, I ended up with stock rom flashed via flashtool..
tried to flash back DRM keys from Dirty cow TA Backup, using this command flash_dk TA_E5823.img DK.ftf but when rebooted in service menu drm keys are still gone..
EDIT:
Seems like there is more users with same issue with Z5C and latest rootkernel
https://forum.xda-developers.com/xp...matic-repack-stock-kernel-dm-t3301605/page200
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
mhaha said:
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
Click to expand...
Click to collapse
Thanks, will try in the evening.
Just to know, if I'm upgrading from previous firmware version, do I have to do all steps or I can start from step 4 (flashing ftf file)?