I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress
What you need if you want to root your Gingerbread rom:
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759
Nice, thanks!
OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update
TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.
Sorry for newb question... What does S-OFF mean?
Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files
timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough
There is another recovery available from GOAPK with Reboot function that works.
can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery
I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk
With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S
Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully
So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .
Related
Hello, everyone!
How do I flash this .zip?
http://forum.xda-developers.com/showthread.php?t=682828
HTc hero 2.1
Thanks
Do you have root access on your phone?
Word of advice: If you have superuser 2.1 or 2.2.2 or whatever already working well, I wouldn't install 2.3.1 until more people verify it works flawlessly or unless there is something specific about 2.3.1 that you need. 2.3.1 came out just a day or 2 ago, and many apps already had issues with 2.2.2... I personally still use 2.1. If you do choose to use 2.3.1, tell us how it goes.
I've been following that thread for a few days, and many people had issues getting 2.3 working, but it looks like the dev fixed the bugs and made 2.3.1 flashable.
In general, to flash any zip:
Copy zip to root of sdcard (i.e., sdcard main directory, not inside a folder)
Boot to recovery: turn phone off, hold home+power
Backup/Restore > nandroid + ext backup!! (just in case you don't like post-flash results)
Flash zip from sdcard, choose the zip you want to flash
Reboot
i did that it said installed fine but nothing showedup
You don't see superuser in your app drawer anymore? Or what?
You should see 'Superuser Permissions' in your app drawer. But the SU program doesn't actually 'show up' unless it's actively being called -- in other words, you'll basically only see it when another program requests superuser permissions....programs like setcpu, Autokiller, file explorers.
c00ller said:
Word of advice: If you have superuser 2.1 or 2.2.2 or whatever already working well, I wouldn't install 2.3.1 until more people verify it works flawlessly or unless there is something specific about 2.3.1 that you need. 2.3.1 came out just a day or 2 ago, and many apps already had issues with 2.2.2... I personally still use 2.1. If you do choose to use 2.3.1, tell us how it goes.
I've been following that thread for a few days, and many people had issues getting 2.3 working, but it looks like the dev fixed the bugs and made 2.3.1 flashable.
In general, to flash any zip:
Copy zip to root of sdcard (i.e., sdcard main directory, not inside a folder)
Boot to recovery: turn phone off, hold home+power
Backup/Restore > nandroid + ext backup!! (just in case you don't like post-flash results)
Flash zip from sdcard, choose the zip you want to flash
Reboot
Click to expand...
Click to collapse
i see the su app but when i do this it only boot loops and stays looping forever unless i pull battery
what am i missing im using clockworkmod recovery
Are you using a custom ROM or kernel? Or do you still just have the stock 2.1 on your phone? If you're using an overclocked (OC) kernel or a ROM that is built with an OC kernel in it, this could be the reason for the bootloops. Some phones aren't capable of booting up at OC speeds.
stock 2.1 although rooted obciously
If you are on a ICS leak now and want to move to another check out this new tool here: http://forum.xda-developers.com/showthread.php?t=1779810
You can use this to restore stock Gingerbread if you are on a modified GB or to go from one ICS to another.
This is the original D4 tool with additions created by several others and repackaged-edited by me.
UPDATE NOTICE: If you downloaded the tool on 06/20 from about 10pm eastern till noon the next day the script was an old version. It is correct now. Just download again.
06/22 9 AM Eastern - updated superuser binary to most recent version.
06/23 12:30 PM Eastern - updated links for 6.16.213 (thanks again droidian1441)
06/25 10:30 PM Eastern - Revised script, that includes a data save option for restoring GB and the best change. The flashing of the GB files and the ICS Kernel to jump from one ICS to another is now all in one. Removed the push file to sdcard (some thought you could do this after you started flashing the system).
06/30 11 AM Eastern - add new link to download all files.
07/01 10:30 Eastern - Updated Superuser (3.1.3) + binary and VoodooRootKeeper (2.0.3) to latest versions. Update ICS root for Dan Rosenburg's root script, this will install superuser and busybox. The other root method didn't seem to install busybox in proper location and resulted in some malfunctions of root only apps. If you installed the previous root script, use voodoo to temporary unroot, then uninstall superuser. Run the new script and you should be good. Note on the latest version of superuser scroll to the left for the update binary menu. Also contains a temporary unroot and OTA protect root.
Some users have reported driver trouble especially after moving to ICS and trying to root.
Go here to get the driver update tools: https://motorola-global-portal.custh...p/30,6720,8302
Some have reported that the USB utility didn't fix there trouble and had to download motocast, which downloaded new drivers.
Thanks again to 1898trouble07 (droidforums) for the data save tip.
I am on longer putting a full version out. It was was just too big to maintain updates. Everything you need is here. You just have to download a few things and move around a couple of files.
First read this entire post at least twice, skipping any step will be BAD!. Then download everything you need for this.
1. All downloads are listed here: http://d-h.st/users/jsnweitzel/?fld_id=3413#files
Other download links below.
1. Get the Tool Here: https://docs.google.com/open?id=0Byw...URLSjQ5V29pYk0
or here: https://www.dropbox.com/s/132a5i038luy4vu/Droid4withICSfix-rootLITE (3).zip
or here: https://docs.google.com/open?id=0Byw...XV2N2N3cTBoQW8
This is a double zip extract until you see the .bat files and a "files" folder. Double click the script to run the tool.
2. Get the GB 219 Fastboot files here: http://sbf.droid-developers.org/cdma...1FF_01.xml.zip
or here: https://docs.google.com/open?id=0Byw...WswcF91MkxkODA
3. If you are just restoring GB this is all you need. Extract the fastboot zip files and copy them to "files" folder of the tool.
If you are just restoring GB, rooted and running the data save option...It might mess up your root. I don't really know for sure. It will erase the superuser binary and the backup if you are running the rootkeeper, but should keep superuser installed. Therefore you may be in a half rooted stuck state and running the root again may not work. I don't have a phone on GB to test this out. To be extra cautious you may want to run the unroot, restore GB then root again. Let me know what you experience and I can update the post.
If you want to go to ICS and are on GB. Then download (see item one below) the D4213 and put it on your external sdcard Boot to recovery and flash from external. You don't have to be rooted. but if you are the easy way to keep root is to use voodoo's rootkeeper. Protect root, temporarily unroot, reroot, flash the ota, then restore root. If you mess up just use the tool to run the ICS root.
If you are moving from one ICS to another keep reading. Downloading the following two files.
1. Get the ICS OTA currently 6.16.213 ICS here: https://docs.google.com/open?id=0Byw...jVSanRzaTZ5alU
This is a double zip to open until you see the folder named D4213, then copy this file to the external sdcard of your phone.
2. Get the matching Kernel 6.16.213 (boot.img) here: https://docs.google.com/open?id=0Byw...1J0VFBCY1NBM2M
Unzip this folder and copy the boot.img to the "files" folder of the tool. It must be named "ICSFIX" for the tool to work.
If you are going from one ICS to another this is the basic procedure. This uses a fair amount of your pc resources. Don't have a bunch of other programs running. Set the phone to MTP for USB and be sure debugging is on (system setting, developer options).
Be sure you charge your battery first. This is a long process be patient. You will get several errors (INFO validation type) if you are on ICS and flash the GB files. Just let it finish.
1. Charge your battery to 100% and have a high quality usb cable. Sometimes the process fails so you might have to do it twice. When in fastboot mode the battery will not charge.
2. Put the D4213 zip on your external sdcard; just copy and paste with windows.
3. Boot to bootloader and select fastboot (power down, hold both volume buttons and press power, release power, select ap fastboot). You can use the tool for this step but will have to manually do it later.
4. Select menu 16 and flash the GB files plus the boot.img of 213. This will take a while just let it finish and follow the prompts when ask to press a key to continue. You will get some errors (Info validation type). Just let it run and finish.
5. Your phone will reboot and attempt to update (android with spinning ball).
6. Let it run until the screen goes blank and the red "M" appears.
7. Then force a power down and boot to the bootloader.
9. Select recovery. When you see the android with the red exclamation press both volume buttons. Select apply update from external storage and chose the 213 zip.
10. Once complete reboot.
11. ENJOY
12. Root ICS if you want.
If you use this to install vodoo's root keeper make sure your screen is unlocked. If not it seems to hang up sometimes. You should immediately get a superuser request.
Finally this is windows only. If someone writes the linux script I can add it in later. Let me know if you have any issues, suggestions, questions or problems.
As usual doing any of this is at your own risk and may render your phone to be a nice paperweight.
Here is the full menu of the tool:
1. Fastboot GB to stock and ERASE DATA (You can use this to restore stock Gingerbread if you are on a modified GB)
2. Fastboot GB to stock and SAVE DATA
3. Root GB
4. Unroot GB
5. Install Voodoo Rootkeeper
6. Install Safestrap for GB
7. System Pull
8. Overclock for GB
9. Boot to Fastboot
10. Boot to Recovery
11. ADB Shell
12. Reboot phone
13. Flash the ICSFIX Kernel (This is not necessary to jump from one ICS to another, use menu 16. Left in for advanced users only)
14. Install Safestrap for ICS
15. Droid 4 ICS Root
16. D4 ICS Fix (Jump from one leak to another) and SAVE DATA
Thought fastboot back to gb after going to the leaked ics caused a brick?
Sent from my DROID4 using xda premium
twizzles said:
Thought fastboot back to gb after going to the leaked ics caused a brick?
Click to expand...
Click to collapse
Yes, but not completely. The phone will still be able to go into fastboot mode which then allows you to flash the necessary files for the upgrade to work.
Gotcha. Thanks a lot
Sent from my DROID4 using xda premium
What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?
If you are on GB and want to do a stock restore this will do it for you. If you are on a ICS leak it's one of the steps you need to move up.
Now I will feel more comfortable in flashing the update!, thanks man. Great job.
Sent from my DROID4 using XDA
stereokid said:
What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?
Click to expand...
Click to collapse
You can't go back to GB if you are on a ICS leak. You can upgrade to a newer leak. Here are the instructions: http://www.droidforums.net/forum/dr...k-200-aka-upgrading-200-206-instructions.html
Same ones can be used to go up to 208. The tool has everything you need.
If im on 206 do i have to flash to 208 in order to flash the new 211 version? And whats in the updates? Enough to take the risk yet again of flashing a leak?
Sent from my DROID4 using xda premium
You can go right up to 211. I haven't changed the tool yet so you will have to replace the 208 files with the 211 files. I will be modifying the tool soon for 211.
Is there an eta for the tool update by any chance? Thanks
Sent from my DROID4 using xda premium
I have started working over the script, with an idea to simplify a step too. But will test on my own phone before I post. You can use the tool as-is if you rename the boot.img and the ota. There is one little hiccup in the script after pushing the boot.img (kernel), but it's doesn't affect the process. Hope to have it up in a few hours.
The new tool is up with some instructions too. The Lite version is good to go, the other is still uploading.
Is it possible to use this tool to flash up from gb? I'm currently using eclipse on safestrap (I know id need to remove safestrap) but didn't know if this will only work with those already on the leaks or if we can use straight from gb
Sent from my DROID4 using XDA
This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
If you want to move to ICS you might be able to uninstall your rom, safestrap and fix the logwrapper renaming. I think I saw a thread about that somewhere.
For anyone trying to download I was having some issues setting up the links for gdrive. Just haven't used it before for file sharing. All should be good now.
jsnweitzel said:
This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
Click to expand...
Click to collapse
If you can, you might want to edit that first sentence to specify that it can restore your phone to stock GB _if you haven't upgraded to ICS_.
Thanks for the suggestion...just saw that 212 is coming. Will be updating once I get a copy.
Ok I just updated the OP, with all the downloads you need. But it's late I am a bit tired. Let me know if something is out of sorts or a link is broke or wrong. It was just too much to keep the full tool up to date and upload.
Link to the tool is broken unfortunately
jgardner said:
Link to the tool is broken unfortunately
Click to expand...
Click to collapse
Not sure what happened there. I did the link over. Try it now:https://docs.google.com/open?id=0BywuYGr-7VrYcURLSjQ5V29pYk0
Some users on droidforums.net had trouble when they just clicked the link. Not sure why, but it worked if they did a copy and paste to the browser.
Before you root your LG Revolution:
Install the latest USB driver software
http://www.lg.com/us/support-mobile/lg-LGVS910
===============
You MUST do this.
===============
All Credit goes to das7982,
I just found the answer.
___________________
use root explorer and go into
system/etc/ and delete the file called
install-recovery.sh
Why? BECAUSE Clockwork will not work without deleting the install-recovery.sh
because it is a shell script designed to over write any new recovery you try to flash over it.
THEN ROOT:
Download
http://forum.xda-developers.com/showthread.php?t=1348557
Extract and run "V8 all in one root + CWM"
and choose install root and CWM and viola.
Generally I would move this thread as a duplication, however, until the OP of the root tools adds this in his first post, I'll let it stay.
The install-recovery.sh and on other devices boot-recovery.p are previously known issues which cause the installed custom recoveries to get overwritten when booting back into a stock rom. This file should be deleted after root, and before installing a custom recovery, unless you plan to boot immediately into Custom Recovery and install a custom rom.
The issue, is you have to ROOT FIRST and gain /System RW.
So the title should be "Before you install CWM". (not sure how the root tool works if you can just root only, or if the author can add the cmd to delete this file when rooting and installing CWM. Should be able to somehow. They do it in the 500 forum)
But sometimes people miss this 1 little step, so the thread will remain.
Rock On!
MD
I thought this thread was a joke because to root your phone via PC you have to install the drivers so ADB can even see the hardware...
Lol
I was gonna say who has a revo that is not rooted.
This makes sense. Bcuz of the .p file or the install-recovery.sh, the aio's repeatedly fail at fully installing cwm. If you push cwm directly from the device, you don't even have to mess with the .p or the install-recovery.sh.
Regardless of anything, It's a good find KangKilla. Awesome clarification MD.
[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?
please fix dead links
dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.
please fix dead links
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.
[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient
[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone
server stilll unreachable.
I recently started playing pokemon go and I am getting really frustrated while playing because it lags soo much and my phone is generally quite slow now. I have been told rooting and installing a good ROM can help with this and I have never attempted this, could someone please explain what rooting and ROMs are and their benefits and a how to guide for this phone and also the best ROM?
I know there are loads of threads on this but if someone could link me best threads I would be eternally gratefull!!
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Hyoretsu said:
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Click to expand...
Click to collapse
Thank you soo much for your reply and sorry about my late reply. My variant is LG-D405n and software version is V20c-234-30. I think I understand what Root and ROM is thx.
So could you link me to the best method to root and install ROM on my phone?
And what is the best ROM for my device to free up the RAM and CPU used on my device to increase my phone speed?
First of all, install these required apps:
http://king.myapp.com/myapp/kdown/img/NewKingrootV4.9.6_C151_B309_en_release_2016_08_18_105203.apk (For rooting)
https://play.google.com/store/apps/details?id=com.cgollner.flashify (For flashing the Custom Recovery)
https://play.google.com/store/apps/details?id=jackpal.androidterm (For terminal emulation)
Custom Recovery:
TWRP: http://forum.xda-developers.com/devdb/project/dl/?id=18679&task=get
Personally recommended Custom ROM, CyanogenMod (Ports Android updates to older phones plus some tweaks) and Gapps (Google Apps, it's needed to have things like calculator, play store, etc):
CM13: https://download.cyanogenmod.org/get/jenkins/175208/cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J8-w7.zip
Gapps: http://opengapps.org/ (Go to this link, select ARM in platform, 6.0 in android and Nano in variant, then just click the download image button)
Put the TWRP img, the CM13 rom img and gapps on microSD or internal storage. Open Kingroot and click on the green button after the 3 introduction images. After a few minutes, your device will be rooted. Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Then, go to flashify and flash your custom recovery image (TWRP or CWM) in the flash recovery img option. After this, reboot into recovery by pressing Volume Down + Power and when you see the LG Logo, let go of the Power button and press it again. Then select yes two times with the volume keys for selection and power button to actually select the options (Don't worry, your device won't be factory resetted if you successfully installed custom recovery). Then, if you want, make a backup of your entire phone (recommended, just in case something goes wrong or if you just want your apps back when the process is done) in the Backup section and then do a factory reset through the Wipe option (Don't select anything, just swipe the bar). Select the Install option and select your ROM zip. After this, do the same process as the ROM installation but this time with Gapps zip. There you go, now you have CM13 installed. If you want root again, you don't have to install Kingroot again this time, as CM13 has built-in root, just enable Developer options and activate root and you're ready to go. Also, if you want the apps you had before the installation, just restore your backup (ONLY THE DATA PARTITION, otherwise CM13 will be uninstalled and replaced with stock ROM). If something goes wrong and you accidentally brick your device, just reply and I'll help you fix it. (If helped, click the Thanks! button)
Hyoretsu said:
Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Firebird3334 said:
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Click to expand...
Click to collapse
You have to change "(aboot.bin storage directory) with the directory in which aboot.bin is stored. And no, you don't need SuperSU, when you use the su command, a KingRoot window will open, just say yes.
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Firebird3334 said:
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Click to expand...
Click to collapse
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Hyoretsu said:
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Click to expand...
Click to collapse
You have helped me out so much already! Thank you so much!
But just one more thing though, could you explain how to install magisk and xposed in layman's term so I can use Android Pay?
I don't know what magisk is nor layman's term, but to install Xposed just go to this thread: http://forum.xda-developers.com/showthread.php?t=3034811, download both Xposed installer apk and xposed zip. Install xposed apk and flash xposed zip
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
amonlb said:
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
Click to expand...
Click to collapse
First of all, you don't need to use that TWRP build, you can use the latest one. To fix the only errors that should appear (Updater error 7 and 6), delete the first lines of updater-script until you reach the ui_print part (the first line of your file should be "ui_print("Target: 1471683591");"). Also, delete any double spaces that exist (there should be two, one before "abort" at line 27 and the other before "abort" at line 30). If it still gives the same error, try wiping Cache, data, system and dalvik-cache partitions, try to install the ROM, it'll give the error. Now, reboot your phone and try to install without wiping anything. (To properly see the line indications, open the file using Notepad++)