Related
I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE
Infos
Why Should I root my phone?
Read Here
What can I do with recovery?
With recovery you can principally flash cooked roms, but also other things like make nandroid backups (Internal memory backups), partition your sdcard, fix problems etc...
If you want root there are 2 methods:
First Method
Is very simple, just download and install InstantRoot.apk (attached)
To install this from sdcard you need a file explorer like ASTRO
After the install a notify that says root access gained should appear, if not try second method
Second Method
This will install also recovery
1. Enable Debug USB from Settings->Applications
2. Download flashrec and install it with file manager like ASTRO
3. Download Amon_RA's recovery and put it in your sdcard
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path:
Code:
/sdcard/recovery-RA-hero-vx.x.x.img
At moment of writing last version is 1.5.2, so the path should be
Code:
/sdcard/recovery-RA-hero-v1.5.2.img
6. Tap Download then flash recoery
7. If you get an error retry from step 3, else continue
8. Turn off your phone and reboot it keeping pressed Home button, recovery should start
9. Connect your phone via usb
10. Download Android SDK and extract all in the same folder
11. Download this and extract it in your sdk/tools folder
12. Open cmd (if you are on windows, if you are on a mac or on linux open terminal) and move to sdk/tools folder using this command
Code:
cd path
13. Give this commands in order
On windows:
Code:
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell umount /system
adb shell reboot
On linux/mac
Code:
./adb shell mount /system
./adb push su /system/bin/
./adb shell chmod 4755 /system/bin/su
./adb push Superuser.apk /system/app/
./adb shell umount /system
./adb shell reboot
14. Now you have root access on your phone
If you want recovery:
Just follow root's second method to the step 7
Flashing Custom roms using recovery:
Custom roms are in Zip format, to flash it is really easy once you have recovery.
Once downloaded a rom put it in your sdcard root, then reboot into recovery (Keep home button pressed while turning on your phone)
Now make a wipe going to Wipe->Wipe data, then come back to main menu and go to Flash zip from sd card, select your zip and you're done
Thanks for the guide How does Nandroid backup fit into this?
maybe you need to tell how to downgrade(or a link to a guide )
nice guide, only i have already rooted my phone(2 months ago or something xD)
@Culturelol
nandroid backup is recommeded when you install a new rom, so you can always back to your original/past rom
So i root with this guide, then nandroid and then i can flash the new rom?
One more small question Is there anything special i should know about flashing the radio?
culturelol said:
So i root with this guide, then nandroid and then i can flash the new rom?
Click to expand...
Click to collapse
Yep
culturelol said:
One more small question Is there anything special i should know about flashing the radio?
Click to expand...
Click to collapse
No, only that you can't flash a GSM radio on a CDMA phone and back, if you do this you'll brick your phone
Exit93 said:
Yep
No, only that you can't flash a GSM radio on a CDMA phone and back, if you do this you'll brick your phone
Click to expand...
Click to collapse
Is that done the same way? Boot to recovery and then flash the radio? And is this done before or after wipe / install of the new rom?
culturelol said:
Is that done the same way? Boot to recovery and then flash the radio? And is this done before or after wipe / install of the new rom?
Click to expand...
Click to collapse
You can install radio whenever you want, it's flashed in another nand partition
nice rom - but the Home button doesnt work - is that normal?
krueck83 said:
nice rom - but the Home button doesnt work - is that normal?
Click to expand...
Click to collapse
Wrong discussion...
If you refer to CKDroid you need to flash googlebits to get home button working...
Exit93 said:
You can install radio whenever you want, it's flashed in another nand partition
Click to expand...
Click to collapse
But it is flashed through the recovery screen?
culturelol said:
But it is flashed through the recovery screen?
Click to expand...
Click to collapse
Yes, it is
Thank you - it works.
Thanks for the instructions.
1-Do you need to follow step 8-12 to get root and flash rom`s or is the android sdk and superuser only if you want to develope yourself?
2- If ypu do this and after want back to stock rom . As far as i`ve read it`s as easy as just flashing from HTC website and you`re back ? Won`t recovery still be left on your phone?
Thanks
Rui-Cruz said:
Thanks for the instructions.
1-Do you need to follow step 8-12 to get root and flash rom`s or is the android sdk and superuser only if you want to develope yourself?
2- If ypu do this and after want back to stock rom . As far as i`ve read it`s as easy as just flashing from HTC website and you`re back ? Won`t recovery still be left on your phone?
Thanks
Click to expand...
Click to collapse
1. Steps from 8 to 12 are only to get root access on stock rom, if you want to change rom you don't need to make those steps
2. To get back to stock rom just flash official update, as far as i know recovery will be deleted
Thanks
Thanks for the guide.
Was being anal and following the guide to the letter (not wanting a brick!) and it just rebooted to stock recovery
Code:
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path: /sdcard/recovery-RA-hero-v1.5.2.img
6. If you get an error retry from step 3, else continue
Should we be tapping the download button once we entered the img location?
Ne0
alfie196 said:
Thanks for the guide.
Was being anal and following the guide to the letter (not wanting a brick!) and it just rebooted to stock recovery
Code:
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path: /sdcard/recovery-RA-hero-v1.5.2.img
6. If you get an error retry from step 3, else continue
Should we be tapping the download button once we entered the img location?
Ne0
Click to expand...
Click to collapse
Yes, sorry it's my fault, correcting...
Sorry silly question
Please could someone tell me, if using the first method the InstantRoot.apk. Will this wipe the current ROM/data/apps etc from the phone or will it just enable Root privilages and leave everything else the same?
Many thanks
Jeremy
It just roots your phone and leaves everything in tact, just did it now.
The guide is not clear on how to flash the rom though. Because it says "If you want recovery" I don't want recovery I just want to flash. I have root now what's next? In simple steps, no recovery required just want CKDroid.
hatski said:
It just roots your phone and leaves everything in tact, just did it now.
The guide is not clear on how to flash the rom though. Because it says "If you want recovery" I don't want recovery I just want to flash. I have root now what's next? In simple steps, no recovery required just want CKDroid.
Click to expand...
Click to collapse
You need recovery to flash roms, it's written on the start of the first post
Hi there.
I have a unbranded DHD on 2.3- 2.36.405.8. It's the official leaked version.
I'd like to root & install leeDroids new Rom based upon the official leaked one.
Could you guys possibly help me out?
I don't want to do anything major, but would like to make my phone better now as I can't see much happening after the gingerbread update. Thanks people.
Sent from my Desire HD using XDA App
Had you rooted previously before you installed the update?
Suggest you google gingerbreak to root your phone, then downgrade your phone to an earlier version so you can S-Off and you can then install custom ROMs.
Guide to downgrade http://forum.xda-developers.com/showthread.php?t=905003
Hi guys. Thanks for your response. It means a lot.
I've never actually rooted any device before, never really had the b*lls lol.
I'll check these threads out & give it a shot.
Thank you very much.
There's not much to get your berries shaking, it's just the radio replacement you should be careful with.
First thing you should do is backup your device with either Titanium or ClockworkMod, though you probably need to root in order to do this, and then anything you might do, you can always revert back to what you had.
When you get to replacing the radio version, read instructions extra careful and be sure to do everything by the book (guide) and to check the checksum on the downloaded files. This could brick your device so no extra precaution is unnecessary..
Happy flashing
Hi guys. Cheers for getting back to me.
Before I start could you tell me whether the following procedures that im going to take will or will not be the right ones please?
1st obtain gingerbreak apk and install on my phone using the downgrade guide on xda
once ive done that use file (http://xdafil.es/DesireHD/RUU/RUU_Ac...032_signed.zip) and put on my sd card..... do I rename this file?
2. Once ive downgraded to this, must i perform a ROOT again to be able to flash a new rom?
3. I want to use this ROM - [ROM&KERNEL] LeeDrOiD HD V3.0.2 GB >EPIC!< |5th May | Official GB Sense 2.1 | TV Anim
4. on the 1.32xxx version do I root and use cwm 2 or 3 and just flash the above rom?
5. When exactly do i use the easy radio off tool please? EasyS-OFF_05.zip (747.4 KB, 20804 views)
Sorry for all the questions, but would be very grateful if someone could help
Edit* also after I write this in cmd
adb push misc_version /data/local/tmp adb shell chmod 777 /data/local/tmp/misc_versi adb shell su
Do I write it exactly as it is? Or does misc_version get replaced with the name of the file?
Cheers.
ok.........
so installed and did gingerbreak, it said didnt work, but asked if i would allow super user permissions to which i said yes.
I opened up a cmd and went to downgrade folder ie; c:\users\ajay\desktop\downgrade
this is where the .zip for 1.36.405.6 is kept.
typed in that code adb etc.... and it said unrecognised command batch etc...
Could someone help us out alittle?
Im pretty dumb at this sort of stuff so my apologies guys.
Hope I manage to install a custom rom, but if i cant then thats cool too.
cheers
Here is my guide i have made and compiled together, follow that and you are done.
---------------------------------------------------------------------------------
HOWTO FLASH CUSTOM ROM ONTO GB DEVICE
Downgrade First!
You might need to format your SD card first before installing Gingerbreak, make a backup of your SD card by copying the files to a safe
place on your PC and then goto Settings - SD and Phone Storage - Click Umount SD card - Click Erase SD card - Click Mount SD card after erasing and formating the card has been
completed.
Gingerbreak help thread for problems:
http://forum.xda-developers.com/showthread.php?t=1044765
1. Download Gingerbreak from http://forum.xda-developers.com/attachment.php?attachmentid=578771&d=1303829207 and install it. Then tap root button.
2. You might get force close errors, just click the force close button and let Gingerbreak do it's job
3. Gingerbreak will in the end, usually say that something went wrong that you need to reboot etc, don't reboot! Just leave it open in your phone, and connect your phone to a PC. Charge only, USB Debugging enabled!
4. Download Android Terminal from the Market and after you installed it you can check if you are rooted, by typing su in the terminal, accept the Superuser request if it shows up and Press "Allow", if you get a "#" you are rooted and the Gingerbreak hack worked.
5. Now open up a terminal window(cmd) on your PC and go to the Downgrade folder on your PC where you downloaded the ADB files from at http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 , execute the following commands:
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
!Now allow SuperUser in phone when dialog comes up!
If you got "#" in the result, you have temporary root! Proceed with commands:
Now type in terminal:
cd /data/local/tmp
./misc_version -s 1.31.405.6
1. Close the terminal window on your PC and set USB connection to disk drive in your phone and download PD98IMG.zip from http://www.multiupload.com/BTJ8KY0KH9 and place it on your SD card, don't extract the zip file!! Do not put the file into a folder of any kind on your SD card.
PLEASE NOTE!! If you can't set USB connection to disk drive you have to reboot the DHD, now you will be able to set USB connection to disk drive and transfer PD98IMG.zip file to SD from your PC.
2. Reboot while holding volume down, it will go to the Bootloader
3. Follow the instructions and Press "Yes" when it asks you if you want to flash PD98IMG.zip (start the update)
4. Done and reboot.
5. Proceed below with the two S-OFF methods and remove the PD98IMG.zip from your SD.
RADIO S-OFF
1. Install and download latest Visionary r14 from http://www.mediafire.com/?xhwc5m7f273l7b2
2. Open Visionary and tap temproot, then attempt permroot now. Your device will reboot.
3. Connect your phone to a computer (make sure you have USB Debugging enabled, Connect charge only!
4. Extract the Radio S-OFF zip file you dowloaded into a folder on your computer from http://forum.xda-developers.com/showthread.php?t=857537
5. Open my "Desire HD easy radio tool.exe" (Windows 7, right click & run as Administrator).
Choose the first option (RADIO S-OFF, Super-CID and Sim Unlock)
Click "Do it". There may be a SuperUser request on your phone, allow it.
6. Done.
ENG S-OFF(You need this enabled to be able to flash RADIO.IMG later)
1. Download and Extract the eng s-off zip file into a folder on your computer from http://forum.xda-developers.com/showthread.php?t=855403
2. Connect the phone to your computer in "Charge only" mode
3. Run "Desire HD easy s-off.exe" from the extracted folder
4. Click "I have RADIO S-OFF" (as you already done RADIO S-OFF earlier), IMPORTANT!
5. Click in "S-OFF" it
6. Your phone is now ENG S-OFF
7. Done
Flashing your ROM
1. Connect your phone using "Disk drive" to the computer.
2. Copy both your full-wipe-1-3.zip from http://dl.dropbox.com/u/15057375/mero01-xda/Wipe/FULL-WIPE-1.3.zip and your CUSTOM ROM zip file to your SD Card
3. Check again that both files are on your SD card because once you full wipe, you won't have a ROM anymore.
4. Disconnect your phone from your computer
5. Install and open Rom Manager from the market
6. Tap on Flash ClockworkMod Recovery and download version 3.0.2.6
7. Wait for it to download (You need a wi-fi or data connection)
8. After it is done press "Reboot into recovery"
9. If you get an icon with a phone and an exclamation mark in a triangle, remove the battery from your phone, reboot and then flash the clockworkmod recovery again
10. Once you are in the clockwork mod recovery, you may use the volume keys as directional keys (up and down) and the power button may be used as Enter.
11. I recommend you do a nandroid back-up. You must have at least 1 gb of free space.
12. Goto Backup and Restore and make a backup of current ROM if something would fail during flash.
13. Select "Install Zip from sdcard"
14. Select "Choose zip from sdcard"
15. Select full-wipe-1-3.zip (It's right under those folders)
16. Confirm by selecting the Yes option in between those "NO"s
17. Wait for it to finish
18. DO NOT REBOOT!!! In case you were not aware, you now have no rom installed
19. Once again select "Install Zip from sdcard"
20. Select "Choose zip from sdcard"
21. Select your rom zip file
22. Confirm your selection (just like with the wipe)
23. Wait for it to finish
24. Please reboot from the recovery menu and flash nothing else before you have rebooted.
Flash recommended Radio for your custom ROM:
1. Download "Radio Flash.zip" from http://www.mediafire.com/?b172o4ftj1mcpn1 and extract it contents on your PC.
2. Put the radio.img file you downloaded for your custom ROM and put it in the same folder as you extracted the "Radio flash.zip" file to.
3. Make sure USB debugging is enabled in your Desire HD before proceeding.
4. Connect your DHD to your PC with the USB cable and make sure you select USB Charge Only!
5. Now goto the Radio flash folder on your PC and execute "Start here.exe"
6. In the terminal window that comes up you will type:
adb reboot bootloader
Your DHD now goes into Bootloader state, when it is in bootloader state you will type:
fastboot flash radio radio.img
When the terminal says that the process is done you will type:
fastboot reboot
7. Now the DHD reboots and everything is done.
!!GOOD TO KNOW!!
TESTING BEFORE FLASHING ANYTHING
Testing Root
1. Download Android Terminal Emulator from the Market
2. Run it and type in "su"
3. Accept the Superuser request if it comes
4. A "#" should appear if nothing is wrong with your root!
Testing Eng S-off and Radio S-OFF
1. Power Down Your Device
2. Go to Bootloader
3. If it says Ace PVT ENG S-OFF your phone is ENG S-OFF.
4. use Volume down to get to system info and tap power button to select
5. check CID for CID-11111111 (if you have this all is done 100%)
6. Reboot
Checking the device state:
1. Go to the bootloader (turn fastboot off, turn off phone, hold vol- and power)
2. If it says ACE PVT SHIP S-OFF in the first line, your device is Radio S-OFF
3. If it says ACE PVT ENG S-OFF, you have ENG S-OFF, go to System info
4. If system info CID is 11111111, your device is SuperCID5.
5. And if you can verify either Radio S-OFF or SuperCID (and you did both), it worked fine and you have both of them
6. You can check your original CID by going to radio tool folder with cmd and typing: "adb shell getprop ro.cid"
To go back to RADIO S-ON:(If you want to go back to RUU stock ROM again)
1. Flash stock ROM (RUU)
2. Temproot using Visionary
3. Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
4. Enjoy your factory-state phone
Prodelin said:
Here is my guide i have made and compiled together, follow that and you are done.
---------------------------------------------------------------------------------
HOWTO FLASH CUSTOM ROM ONTO GB DEVICE
Downgrade First!
Install Gingerbreak v1.2 apk which is latest, you might need to format your SD card first before installing Gingerbreak, make a backup of your SD card by copying the files to a safe
place on your PC and then goto Settings - SD and Phone Storage - Click Umount SD card - Click Erase SD card - Click Mount SD card after erasing and formating the card has been
completed.
http://forum.xda-developers.com/show....php?t=1044765
Click to expand...
Click to collapse
THIS LINK IS BROKEN.. can you check it please?
Hi thanks very much
Ill follow this guide now, and hopefully be sorted.
just quickly, where do i get recommended radio? and during...
4. Open up a cmd and go to Downgrade folder, execute commands:
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
do i press enter after each line of text?
ajay83 said:
Hi thanks very much
Ill follow this guide now, and hopefully be sorted.
just quickly, where do i get recommended radio? and during...
4. Open up a cmd and go to Downgrade folder, execute commands:
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
do i press enter after each line of text?
Click to expand...
Click to collapse
Yes enter after each line
For recommended Radio look into the thread of the custom ROM you will flash, it will say what radio they recommend to their ROM
Hi there.
1st thank you for being so patient with me mate, I appeciate it.
after i typed the 1st line of those commands it wouldnt have any of it. It said....
'adb' is not recognised as an internal or external command, operable program or batch file.
I think I should just leave it. Ill have all the guys on here pulling their hair out coz i cant do the simplest thing lol.
Thanks for your time anyway bud.
Revised my guide to make it easier to read and understand.
ajay83 said:
Hi there.
'adb' is not recognised as an internal or external command, operable program or batch file.
Thanks for your time anyway bud.
Click to expand...
Click to collapse
You need to type adb in the folder you have adb.
If you have adb.exe in folder c:\Downgrade you must go to that folder first and the type adb.
ahh ok.
Thank you very much bud. Legend =)
and where could i get Radio_12.54.60.25_26.09.04.11_M2 please? I read the forum and it seems to be a good recommended one.
I'll give it ago tonight or tomorrow morning and let you know how i got on.
Thanks for all your help and for being patient bud.
ajay83 said:
and where could i get Radio_12.54.60.25_26.09.04.11_M2 please? I read the forum and it seems to be a good recommended one.
Click to expand...
Click to collapse
From the Radio's thread in the development forum.
[EDIT] @Andy: Sorry, not today.
ajay83 said:
ahh ok.
Thank you very much bud. Legend =)
and where could i get Radio_12.54.60.25_26.09.04.11_M2 please? I read the forum and it seems to be a good recommended one.
I'll give it ago tonight or tomorrow morning and let you know how i got on.
Thanks for all your help and for being patient bud.
Click to expand...
Click to collapse
You can get that particular radio from:
http://tinyurl.com/6ynbecn
Mr_JMM said:
From the Radio's thread in the development forum.
[EDIT] @Andy: Sorry, not today.
Click to expand...
Click to collapse
Don't worry you have to be nice all the time. Sometimes It hurts my head being nice. I would of answered the same TBH. Its not like it isn't in a sticky.
Hi there.
gingerbreak worked!
Followed the codes and got superuser access.
I had formatted my sd card prior to doing this btw
I closed the terminal and went to change usb from charge to disk drive and the option had gone. took it out and reinserted and still it wouldnt find it for me to put .zip file on???
It would not show my sd card was there until i re booted?
Its a shame we cant just temproot it with gingerbreak and flash the rooted GB 2.3 leedroid, but then i guess this is where all this -s off stuff comes in right?
I havent got a clue now let alone to begin with lol.
Lads I think i give up =( . Thanks for all the help and advise and patience but your dealing with abit of a numpty here and we could be here a very very long time.
I appreciate all the help & Ill keep my eyes open if a way comes out to permroot 2.3 without downgrading etc...
ajay83 said:
Hi there.
I closed the terminal and went to change usb from charge to disk drive and the option had gone. took it out and reinserted and still it wouldnt find it for me to put .zip file on???
It would not show my sd card was there until i re booted?
Click to expand...
Click to collapse
Same thing happened me, i had to reboot to make SD card show up again, but that is no problem as you have already changed misc_version with adb, you can now just put the PD98 file to the SD card and reboot and flash from bootloader.
Easy.
You have come along way now, just do as i said earlier, the rest is easy, don't give up now
Here is a step by step guide to root your xoom that is already updated to 3.1
You might also find this useful if you relocked your device to get the 3.1 update.
****** WARNING************ WARNING************ WARNING******
1. All steps are for the 3G Verizon Wireless Xoom. The steps are almost the same for WiFi but the files you need to download are different. You can find everything for your Wifi Xoom here: http://forum.xda-developers.com/showthread.php?t=1078019
2. You will lose all data by unlocking your device. This is just something you will need to plan for. Backup everything BEFORE you start this. If you Have any questions about backing up your data I will be happy to help. If you are already unlocked then you dont need to worry about this. /win
****** WARNING************ WARNING************ WARNING*******
How to use this guide
.....PLEASE READ THIS!......
This guide is divided into 3 sections:
1. Root Your Xoom
2. Flash CWR
3. Flash Kernal
These sections must be completed in order. If all you want is root then just do the 1st section. If you want SD card support then you must do all 3 steps.
Each section has its respective folder in the .rar file that I’ve linked Below.
1. Root files
2. CWR files
3. Kernel
As you work your way through this guide I will refer to files located in these folders.
All files used in this guide can be found here:
https://rapidshare.com/files/2447837220/3.1_Root_and_Recovery_Tools.rar
Or Here:
http://www.megaupload.com/?d=S9BTBCC6
***If people are having issues or don't understand how to set up ADB, this post helps a ton, and cuts out things you don't need***
http://www.xoomforums.com/forum/moto...platforms.html
Lets get started!!!!
**********************************
**********************************
Unlock and Root Your Xoom
>Root Files folder<
Steps found here:
http://forum.xda-developers.com/showthread.php?t=968342
1. Download the Motorola Xoom Root Zip file and unzip it.
(I replaced thes files with "root31.img", "SU", "superuser.apk" All found in the "Root Files" folder if you use my download link)
2. Place the files in the SDK Tools folder.
(You can skip the next 3 steps if you’ve unlocked with fastboot previously or if you lost root due to upgrading to 3.1)
3. adb reboot bootloader
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot (name of new boot.img(root31.img attached))
7. fastboot reboot (wait for reboot)
(you will need to enable usb debuging here)
8. adb remount
9. adb push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
_______________________________________________________
Flashed CWR
>CRW Files folder<
Steps found here:
http://forum.xda-developers.com/showthread.php?t=1074979
1. Download the recovery image (CWR.img attached)
2. Pull up your command prompt
3. Adb reboot bootloader
4. Fastboot flash recovery (name of recovery.img (CWR.img))
5. Fastboot reboot
_______________________________________________________
Flashed Kernel
>Kernel folder<
Steps found here:
http://forum.xda-developers.com/showthread.php?t=978013
1. Reboot into recovery. (adb reboot recovery or volume down while booting)
2. Go into "mounts and storage"
3. Select "mount USB storage"
4. Your SD Card will now be mounted on your computer. Drop the kernel (and boot image pack if applicable) onto SD Card.
5. "Go Back" then go into "install zip from sdcard" then "choose zip from sdcard"
6. If you are flashing a boot image pack, flash it first. (3G_light_ON_Speed.zip) Then flash the kernel zip. (Tiamat_Xoom-1.4.2_1.4Ghz.zip)
7. Back out to main menu and reboot.
_______________________________________________________
I am not taking credit for any of these steps I am simply trying to put the info in one place for people who need it.
The files I have attached Via download link are files taken from the threads listed above, I have not modified ANY of these files!
Where did you attach the files?
soooooo could have used this last night! Great job compiling all the stuff into one place!
Sorry, They are still attaching. Its taking forever. I will throw it up on rapidshare or something like like 2 min
2 min 10 sec
z06mike said:
Where did you attach the files?
Click to expand...
Click to collapse
Ok, download link is up there
https://rapidshare.com/files/503342030/3.1_Root_and_Recovery_Tools.rar
Awesome! Thanks
Updated Files.
https://rapidshare.com/files/1651389459/3.1_Root_and_Recovery_Tools.rar
sgtagem said:
Here is a step by step guide to root your xoom that is already updated to 3.1
All steps below were for my 3G Verizon Wireless Xoom. The steps are almost the same for WiFi but the files you need to download are different and must be found on the threads listed below.
All tools can be found here:
https://rapidshare.com/files/1651389459/3.1_Root_and_Recovery_Tools.rar
Unlocked and rooted my Xoom
Steps found here:
http://forum.xda-developers.com/showthread.php?t=968342
1. Download the Motorola Xoom Root Zip file and unzip it. (I replaced this file with the root31.img)
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot (name of new boot.img(root31.img attached))
7. fastboot reboot (wait for reboot)
(you might need to enable usb debuging here)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
_______________________________________________________
Flashed CWR
Steps found here:
http://forum.xda-developers.com/showthread.php?t=1074979
1. Download the recovery image ( I used the image that keeps charging light on)
2. Pull up your command prompt
3. Adb reboot bootloader
4. Fastboot flash (name of recovery.img (CWR.img attached))
5. Fastboot reboot
_______________________________________________________
Flashed Kernal
Steps found here:
http://forum.xda-developers.com/showthread.php?t=978013
1. Reboot into recovery.
2. Go into "mounts and storage"
3. Select "mount USB storage"
4. Your SD Card will now be mounted on your computer. Drop the kernel (and boot image pack if applicable) onto SD Card.
5. "Go Back" then go into "install zip from sdcard" then "choose zip from sdcard"
6. If you are flashing a boot image pack, flash it first. Then flash the kernel zip.
7. Back out to main menu and reboot.
_______________________________________________________
I am not taking credit for any of these steps I am simply trying to put the info in one place for people who need it.
Click to expand...
Click to collapse
When I clicked on the rapidshare link, my anti-virus warning went off with a vengence.
any chance this could be compiled into a one click methods for tards like me?
One adjustment needed, found on my end:
On step 9: "adb shell push su /system/bin" remove "shell", otherwise you end up with "push: not found" error
all the other lines are fine.
First off great instructions for rooting the 3G Xoom. But after going through the process last night there are a few things that may catch up users...
The "adb shell push su /system/bin" command may not work for at least some users or they may get a error. Should be changed to "adb push su /system/bin" or at least put a note to try that if the first does not work.
The "Fastboot flash (name of recovery.img (CWR.img attached))" should be "Fastboot flash recovery (name of recovery.img (CWR.img attached))" I know they should be able to figure this out but may cause some users a headache for a while while they figure it out.
You might also put a note that if you lost root due to upgrading to 3.1 but had earlier did the "fastboot oem unlock" when you were 3.0 or 3.0.1 you don't have to do the "fastboot oem unlock" again. The "fastboot oem unlock" wipes all the data which I don't think is necessary.
Overall though great instruction and I love how you provide a link with all the files right there in the instructions. I hate instructions that vagely tell you to get the files from another post and then not even provide a link to that post.
Dan
I updated the commands should work for all now
This is the 1st guide Ive done so I knew things would be missing, thanks for the heads up. I hate how some of those threads bounce you around like a ping pong ball.
Kamau54 said:
When I clicked on the rapidshare link, my anti-virus warning went off with a vengence.
Click to expand...
Click to collapse
If you are worried about the DL link you can get the files from the threads directly. I would never put my reputation at risk by spreading infected files. Cant really say much more
Brenardo said:
any chance this could be compiled into a one click methods for tards like me?
Click to expand...
Click to collapse
Im sure someone will. I would have no clue how sorry
thanks for the guide!!!
has there been any news about geting the SD working? i had it working om 3.0.1
iDroidNow said:
thanks for the guide!!!
has there been any news about geting the SD working? i had it working om 3.0.1
Click to expand...
Click to collapse
It works after doing all these steps. It will show up as "External"
it does not work on mine with these exact instructions and i have read about others having the same issue.
iDroidNow said:
it does not work on mine with these exact instructions and i have read about others having the same issue.
Click to expand...
Click to collapse
If you boot into recovery and go into mounts and storage can you mount it. if you plug in your computer from this point you should see external.
ok i was referring to seeing it in a File browser (Astro) etc... i guess that is not working yet?
thanks for the information.
Ok I successfully unlocked ZVD (KitKat 4.4.2) and thought I should share my steps in case anyone else was having the same issues as me which was mostly the systemui and home processes crashing on a loop.
First insert the SIM card you would like to use in the LS980. Then download and flash the stock firmware LS980ZVC_12.zip with the LG Tool -> http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Download the ZVD update - > http://www.mediafire.com/download/s5dqwo1cbe68ckb/LS980ZVC_12-LS980ZVD_19_update.zip (Do not flash this OTA update from a rooted rom or custom recovery!)
After flashing ZVC, set the phone to charge only and enable USB debugging by becoming a developer. Go to About Phone->Software Information and keep clicking "Build number" until it says you are a developer. Then go back to the main settings and you will now see "Developer options" and can enable USB debugging in there.
After enabling USB debugging choose charge only and when the RSA Key fingerprint window pops up make sure you check "Always allow from this computer" and then click OK.
Next using the ADB tools, reboot into recovery mode to apply the ZVD update.
Code:
adb reboot recovery
Select "apply update from ADB" with the volume buttons then press the power button. Wait 5 seconds then enter the following command.
Code:
adb sideload path_to_file/LS980ZVC_12-LS980ZVD_19_update.zip
After the update finishes select "reboot system now".
Next turn on airplane mode and root the phone using IO Root -> http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Next install SuperSU and BusyBox. Make sure you open SuperSu to update the SU binary and open BusyBox and install the busybox files.
*OPTIONAL INSTALL TWRP*
Next use ADB to install AutoRec -> http://forum.xda-developers.com/showthread.php?t=2715496.
Code:
adb install path_to_file\LS980_AutoRec.apk
Open AutoRec and flash the new patched kernel and recovery and then reboot. If you get white lines after rebooting, read the warning the OP has posted for the fix. I suggest here you take the time to make a backup and copy the EFS to your computer just in case.
*knock code feature will no longer work
*flash this kernel to enable knock code again and much more - > http://forum.xda-developers.com/showthread.php?t=2725023
*OPTIONAL END*
Now using ADB again, enter the following commands.
Code:
adb pull /system/build.prop
adb shell
su
After entering "su" check your phone to grant SuperUser permission to ADB. Aftering granting su to ADB, exit adb shell.
Code:
exit
exit
Next using Total Commander and the files from here -> http://forum.xda-developers.com/showthread.php?t=2655133 copy all the contents of the "carrier" folder to your phones "/carrier/" directory and choose "overwrite all". I like to delete the "legal.db" first this way I know the copy was successful when I see the new file listed. Do not delete any other files before copying the files over since we want to keep the file and folder permissions and owners of the originals. If Total Commander fails to copy the files over to the phone then you can use a root explorer app to do so.
Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me.
Change the following lines
Code:
ro.carrier=unknown
ro.build.target_operator=SPR
persist.service.crash.enable=0
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
to
Code:
ro.carrier=spr
ro.build.target_operator=spr
persist.service.crash.enable=1
ro.telephony.default_network=0
telephony.lteOnCdmaDevice=0
*ro.carrier and ro.build.target_operator can bet set to "TMO", "ATT", or "spr".
*"TMO" and "ATT" do not correctly display the signal strength in the status bar.
Save the build.prop and use ADB to push it to the sdcard.
Code:
adb push build.prop /sdcard/
Now here is where we have to manually mount the system partition as RW and copy the build.prop over since all the root explorer apps seem to also cause the crashing issue.
Code:
adb shell
su
mount -o remount,rw /system
cp /sdcard/build.prop /system/
mount -o remount,ro /system
reboot
After the phone reboots it should be unlocked. Verify with Radio Switcher that your preferred network type is "WCDMA preferred", if not then change it to "WCDMA preferred". Now add your APN using Tweakker APN INTERNET MMS. If your APN doesn't stick, delete /data/data/com.android.providers.telephony/databases/telephony.db and reboot then add your APN again.
*To remove Bloatware add ".bak" to the following system applications names located in /system/app/ and /system/priv-app/ folders.
Activation.apk
OmaDmclient.apk
SPR_Skyfire_Observer.apk
SPR_Skyfire_Toolbar.apk
SprintExtensionProvider.apk
SprintID.apk
SprintTouch.apk
Vtt-Sprint.apk
xtra_t_app.apk
Zone-Sprint.apk
WIFIOffloader.apk
Click to expand...
Click to collapse
*To fix the issue of the com.android.phone process crashing when you don't dial a 1 in front of the number edit the /data/data/com.android.providers.settings/databases/settings.db file with a SQLlite editor and change in the "system" table "assist_dial" and "assist_dial_init_db_check" to "0". If you don't see those 2 rows then you can add them instead.
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db
sqlite3 settings.db
UPDATE system SET value='0' WHERE name='assist_dial';
UPDATE system SET value='0' WHERE name='assist_dial_init_db_check';
.exit
adb push settings.db /sdcard/
adb shell
su
cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chown system:system /data/data/com.android.providers.settings/databases/settings.db
reboot
*To disable OTA updates and notifications rename the following files
/etc/security/otacerts.zip
/system/app/LGFOTA.apk
Click to expand...
Click to collapse
to
/etc/security/otacerts.zip.bak
/system/app/LGFOTA.apk.bak
Click to expand...
Click to collapse
*To replace the Sprint boot/shutdown animations and sounds with the LG default ones download these files -> https://www.mediafire.com/folder/cmb6jn7z7osmf/LG_G2_Boot_Animation
copy and overwrite the following files to /system/media/
bootanimation_sprint.zip
shutdownanimation_sprint.zip
Click to expand...
Click to collapse
copy and overwrite the following files to /system/media/audio/ui/
PowerOff_Sprint.ogg
PowerOn_Sprint.ogg
Click to expand...
Click to collapse
*LG G3 Theme for G2 -> https://play.google.com/store/apps/details?id=com.lge.launcher2.theme.rocketg3&hl=en
Thanks to all those people who contributed to this. :victory:
Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....
MakisPgr said:
Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....
Click to expand...
Click to collapse
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app
This method worked on my ATT sim card I dont need to dial a 1 in front of #. but didnt work on my Lycamobile simcard and pageplus. still need to dial 1 infront of nuber.
thanks.
来自我的 LG-LS980 上的 Tapatalk
Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app
jsergio123 said:
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes you are right about 1 bar signal, didn't notice, and i fix my mistake settings on APN and mms now works perfectly ... Thank you very much
jsergio123 said:
Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry, I dont know where is it.
ahqiu said:
sorry, I dont know where is it.
Click to expand...
Click to collapse
adb logcat > logcat.txt
Sent from my LG-LS980 using XDA Premium 4 mobile app
Updated the OP for latest ZVD update from Sprint.
Added SQLite instructions.
Also confirmed working myself.
Updated the OP to include the files and instructions to replace the sprint boot/shutdown animations and sounds
Do you know if I would be able to install a custom rom after this? Also, I had the issue before with cloudys rom that would cause app force closing and restarts, should I expect the same this way?
Thanks a bunch
If you want to use a custom asop rom don't follow my guide instead just follow this guide after flashing your rom of choice.
http://forum.xda-developers.com/showthread.php?t=2827043
@jergio123
Do you think this would work to unlock additional bands on the Sprint LGG2 LS980 for T-Mobile USA?
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
I guess the only way to find out would be to attempt it. I only quickly looked through the thread but good find.
Is there suppose to be a custom folder inside the carrier folder I copied over to root directory? After rebooting my device I've notice this custom folder that's not inside the original carrier folder I extracted ?
There should be a "cust" folder, I'm not sure if that is the folder you're referring to.
Will cloudys g3 ROM work with this unlock method?
I'm pretty sure cloudys rom is already unlocked and only requires you to change the radio with radio switcher and add your APN
Don't work
Hello, i can't unlock with this method. In the end, when i turn on the phone unlocked, the phone give me an error and always appear "com.android.phone".
I don't understand this part:
"Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me."
I need edit "built.prop" or not? How?
I'm using the phone in Portugal (gsm carrier), i need to do this part?
Sorry but i really confused.
Thank you
Follow the guide step by step, I don't know how much clearer I can make it.
If you're getting process crashes then you must either restore the system partition from backup or start fresh by re-flashing with the LG tool.
I fixed it myself and hope the advice can help someone:
A) Some of the mistakes i made during editing of the build.prop file
0. While bootlooping constantly hold volume down+power, it WILL boot to the bootloader after some time!
1. Don't use adb shell then adb pull/push, you don't need the shell here! Just use "adb pull /system/build.prop", notepad++ and "adb push build.prop /system/build.prop" to update the file, then set permissions again with "chmod 644 build.prop" and then "ls -l" to make sure the permissions of build.prop show -RW-R--R--
2. To use adb, get into fastboot->recovery and watch out that /system is mounted
3. Use the UniversalADBDriverSetup.msi to install drivers, then check check and check again that you change the drivers used to the ADB ones, not my htc, not android device. Different states of the phone sometimes activate different drivers (IE i plugged my bootloader phone in, changed drivers, got into recovery, had to change drivers again!)
4. Make a .bak file before you change anything inside android!
5. Avoid AROMA Filemanager, every time i tried to type something my keyboard got stuck and i had problems closing it. Without being able to remove the battery this is a huge risk.
B) Regarding OTA:
To disable the OTA updates i installed the app "MyAndroidTools" and disabled Service->System->Update/Upgrade(german: Aktualisierung)->UpdaterCheckIntranetService
Old Stuff:
Update: Got fastboot connecting, but adb not.
New main question: How to choose the rom i am going to flash?
Device Carrier Region Type Kernel Android Size Description
Device is clear, but Region i get TW and TW Wifi. My android Version before was 4.4.2 and i had the ota upgrade to 1.60.xxxx. Is it safe to not know what carrier, region and type i have and just chose Region TW, Type CRC, Android version 4.4.2 1.54.xxx?
Desire 816 hTC Asia TW CRC 3.4.0 v4.4.2 155 MB 1.54.709.2
Can i use the latest android one instead?
Desire 816 APTG TW MR 3.4.0 v4.4.2 156 MB 1.63.500.1
TLTR: reboot loop after rooting and tampering with the build.prop file, can get into bootloader/recovery, usb drivers wont work, how to edit build.prop/reflash stock with zip/add new build.prop?
My Phone as i remember: TW international HTC 816 single sim android 4.4.2
PC win 7 x86 ultimate
Here is what i did before the bootloop:
Rooted the phone with this instruction: https://www.youtube.com/watch?v=vhUBLhdgSPU
Quote: 1. HTC Sync Manager 2. Install ADB Fastboot 3. Unlock Bootloader 4. CWM Auto-Install via ADB Fastboot / Bootloader 5. ALL IN ONE SuperSU .zip file for Internal Storage (Includes Busybox, Init.d Installer, & Write Protection Removal)
Then i wanted to hide the over the air update by modifying the build.prop with root explorer->Jota Text Editor
(renamed it to build.prop.bak first)
I couldn't save it in /system with Jota so i moved it to the location (editing or savind with wrong permissions caused the loop)
rebooting started the bootloop, every 4 minutes it will start again.
i could enter recovery mode holding down and power for some minutes.
then adb and htc sync didn't detect my phone.
i tried using a file explorer [CWM-APP][1.91] AROMA Filemanager + TERMINAL :: 130903 :: Open Source
from http://forum.xda-developers.com/showthread.php?t=1646108 to rename the file, but the keyboard just hangs and produces garbage. Now my two build.prop files are named somewhat similar to jkdfh(ZG and $§BKGddddd, not build.prop and build.prop.bak
after barely closing the filemanager i am trying to get adb to work to change the filename for good
i boot in recovery and into hboot usb, connect the phone and try adb commands
i am now stuck, as none of the usb drivers i tried work.
i did a recovery->wipe data/factory reset and recovery ->wipe cache partition
i tried 15 sec adb drivers, i tried naked usb adb drivers, right now uninstalling every driver then reinstalling htc sync, reinstalling adb 15 sec 1.4.3 version of the drivers. Didn't find the ADB Driver entrys, so i searched and insalled universaladbdriversetup.msi, activated the "android adb interface" driver, have my phone in "fastboot usb mode", windows recognizes it, htc sync pops up but doesn't find a phone, adb still says device not found...
If i can't get the drivers to work, is there an option to not use usb to flash a stock rom from the sd (install zip)?
How do i decide what stock rom i need, how do i prepare it to be flashed as zip?
Please point me into the right direction.
I think I get it?
So I have a Droid 4.
I'm really bad at the jargon here, so if I may, I'll break it down and ask for explanations like I'm five.
My situation: I've been digging all over the internet for hours trying to figure out how to repair my broken build.prop file, which I edited in hopes of making the Droid 4 Compatible with Cricket Wireless. I am now stuck in Bootloop.
My options: I can easily get into the Android System Recovery menu.
@Kakmnesu: As I understand it, I need to:
1.) "update system from ADB" in the recovery menu.
2.) Run the ADB Command line.
3.) Enter "adb pull system/build.prop". This will, as it were, pull the file out so that it might be replaced.
4.) Have a backup copy of the clean build.prop on the external SD card.
5.) Enter "adb push system/build.prop". This will place the CLEAN build.prop from the SD card into the place of the old one and get rid of the old one completely.
What I don't know:
If my understanding of Item 5 is correct.
How can I tell if /system is mounted, and what do I do if it isn't?
What does setting the permissions do, and do I need to do that?
Any help is appreciated.
@sd_shadow, I've been trying to understand your posts and have been gathering what I think I might need should I have to overhaul the whole OS and start clean: I've noticed in your Droid 4 Repository that you have two files:
cdma_maserati_9.8.2o-72_vzw-18-2_1ff.xml
and
VRZ_XT894_9.8.2O-72_VZW-18.8_CFC.xml.
What is the difference between these, and do I need them both, should I need to just clean everything out?
Thanks so much for any of your help
ninthtale said:
So I have a Droid 4.
I'm really bad at the jargon here, so if I may, I'll break it down and ask for explanations like I'm five.
My situation: I've been digging all over the internet for hours trying to figure out how to repair my broken build.prop file, which I edited in hopes of making the Droid 4 Compatible with Cricket Wireless. I am now stuck in Bootloop.
My options: I can easily get into the Android System Recovery menu.
@Kakmnesu: As I understand it, I need to:
1.) "update system from ADB" in the recovery menu.
2.) Run the ADB Command line.
3.) Enter "adb pull system/build.prop". This will, as it were, pull the file out so that it might be replaced.
4.) Have a backup copy of the clean build.prop on the external SD card.
5.) Enter "adb push system/build.prop". This will place the CLEAN build.prop from the SD card into the place of the old one and get rid of the old one completely.
What I don't know:
If my understanding of Item 5 is correct.
How can I tell if /system is mounted, and what do I do if it isn't?
What does setting the permissions do, and do I need to do that?
Any help is appreciated.
@sd_shadow, I've been trying to understand your posts and have been gathering what I think I might need should I have to overhaul the whole OS and start clean: I've noticed in your Droid 4 Repository that you have two files:
cdma_maserati_9.8.2o-72_vzw-18-2_1ff.xml
and
VRZ_XT894_9.8.2O-72_VZW-18.8_CFC.xml.
What is the difference between these, and do I need them both, should I need to just clean everything out?
Thanks so much for any of your help
Click to expand...
Click to collapse
very little difference in the 2, only need one, either should be fine, but 18.8 is newer and should be better.
But you really should post in the Droid 4 section, and if you want reference this thread and/or mention Kakmnesu
the HTC Desire 816 and the Moto Droid 4 are very different devices, and the fixes may be very different.
---------- Post added at 01:02 PM ---------- Previous post was at 12:50 PM ----------
Cricket uses AT&T GMS network?
may need to see http://forum.xda-developers.com/showthread.php?p=25219819#post25219819
Got it. Thanks! I'll move to that thread because it still didn't work.. :\
After flashing CM-12, Both SIM are not working. Flashed stock L firmware but still problem is there... any solution?
Kakmnesu said:
[...]1. Don't use adb shell then adb pull/push, you don't need the shell here! Just use "adb pull /system/build.prop", notepad++ and "adb push build.prop /system/build.prop" to update the file, then set permissions again with "chmod 644 build.prop" and then "ls -l" to make sure the permissions of build.prop show -RW-R--R--
[...]
Click to expand...
Click to collapse
My issue was a bit like yours, only on my One M7. I screwed up the build.prop (replaced the ViperOne one with a Generic M7 one) and got stuck into a black screen after splash screen. The dreaded soft brick. I don't have ADB on my computer, but thankfully I had a copy of the original build.prop in my internal storage. However I couldn't get it to work after using TWRP to copy the file to /system/ multiple times.
I tried -everything- until a google search guided me to your post. The instructions in bold did the trick. You, sir, have saved me a lot of trouble