Related
i have a tmobile g2 and used visionary to root and it did not work right but my s-off and i can not root any way i try,if i have stock rom what do i have to do to reinstall the stom rom and will this make my g2 go back to s-on?
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
renn9420 said:
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
iv tried that and nothing works at all,i was told i needed s-on again because s-off is what i have and no matter what i try i can not root this **** phone!!!!!!im ready to throw it out the window.
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
steviewevie said:
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
Click to expand...
Click to collapse
im about to try it
hightechlive said:
im about to try it
Click to expand...
Click to collapse
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
hightechlive said:
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
Click to expand...
Click to collapse
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
steviewevie said:
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
Click to expand...
Click to collapse
yes i did get forked xxx children message,but i this is different for me
init_module 'wpthis-OTA.ko' failed
i get this
local/tmp/init_module 'wpthis-OTA.ko' failed
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
fastludeh22 said:
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
Click to expand...
Click to collapse
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
hightechlive said:
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
Click to expand...
Click to collapse
*Following instructions in that post includes a wipe. This will delete settings, 3rd party apps, mms etc. Be sure to backup what's needed.
These directions are for windows computers:
Do not unzip the file. It should be clockwork recovery 2.x.x.x.img. just rename it recovery.img. The root of c just means not in any folders. So after naming it recovery.img put it on c. It will then be c:\recovery.img
Then when you open up cmd window, goto sdk folder like when you use adb. With your phone booted into hboot with usb connected. You type this into cmd window: "fastboot flash recovery recovery.img" without the quotes. Then finish following pervious link.
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
i type in command window but it says can not load recovery img
hightechlive said:
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
Click to expand...
Click to collapse
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
fastludeh22 said:
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
Click to expand...
Click to collapse
i type in command window but it says can not load recovery img
im doing everything you said?
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
fastludeh22 said:
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
Click to expand...
Click to collapse
i did that,this i what i did i download and change the name and put the zip file in the c root,open command and went to the tolls folder after the other things to get there in command and this is what it says
says can not load recovery img
What zip file? The recovery should be an img file.
fastludeh22 said:
What zip file? The recovery should be an img file.
Click to expand...
Click to collapse
that what im saying when i down load the file if is zip up and when i unzip it says i can not open it?
when i download it this is the name of the file
recovery-clockwork-2.5.1.2-vision (1)
I went to clockwork thread and clicked link. It dl's as .img file for me. This is the direct link I'm talking about. http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
If your using that, check this. In an open window/folder in windows. Click tools, then folder options. Select view tab. Uncheck "hide extensions of known file types". Then the file extensions should show at the end of every file. Make sure its named right now.
HTC Desire USB Bricked Without Root
Hey guys, got a really tricky one for you here...
Some people may have seen a thread I posted the other day about problems that had arisen with my HTC Desire, well I have managed to find out that these problems are being caused by a USB Brick.
As of now I have managed to restore SD Functions however my phone will still not connect to the computer, and the phone won't recieve a network signal from Orange.
I read through this tutorial here and also this one here. My problem is, all the requirements of the fix, my device does not meet. My phone is not rooted, it is running the latest software and has the latest HBoot.
I also found this that looked very promising, however when I tried to log into my Google account on my phone, everytime it said it couldn't make a connection, I left it for a few hours and the same thing, I can't help but think this is due to the USB brick?
I just really need some help, is there anything I can do to restore USB functionality? The phone is being sent to HTC tomorrow, however I can cancel at any point. Please, I know there are so many amazing people on XDA that can help me. Thankyou
*UPDATE* - After using the Fastboot code to enable the SD Card, my Sim Card is now working. I have been able to log into my G-Mail account and download the terminal emulator which is an apparent fix in one of the posts I linked above, however this doesn't work. Please can someone help me
hy did you try to reinstal the software ???? the original os or an upgrade??
en_mih said:
hy did you try to reinstal the software ???? the original os or an upgrade??
Click to expand...
Click to collapse
I have done a factory reset, re-installed the PB99IMG and also flashed an RRU. All the problems persist
Really need help with this guys! E-Mail - [email protected]
jaaystott said:
Really need help with this guys! E-Mail - [email protected]
Click to expand...
Click to collapse
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
leinad said:
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
Click to expand...
Click to collapse
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
HQRaja said:
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
Click to expand...
Click to collapse
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
jaaystott said:
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
Click to expand...
Click to collapse
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
leinad said:
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
Click to expand...
Click to collapse
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
jaaystott said:
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
Click to expand...
Click to collapse
:-( (10 characters)
leinad said:
:-( (10 characters)
Click to expand...
Click to collapse
I really appreciate the help you gave me mate, even if I asn't able to fix my device, thankyou for the time.
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
moley10 said:
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
Click to expand...
Click to collapse
I found a way around this, as I was having the same problem. Try This ->
cat /sdcard/rageagainstthecage-arm5.bin > data/data/rageagainstthecage-arm5.bin
Do that for the two other commands that follow that, then follow the instructions as given, that should work.
HQRaja said:
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
Click to expand...
Click to collapse
Link to your blog? =)
ok, so i did that, no longer got errors.. seemed to work but after reboot still the same, doesnt connect to my pc, and device manager it is still being shown as 'qualcomm cdma technologies msm' in other devices!
is the purpose of those commands to moved the files to certain directory? i can get temp root with visionary to perhaps just move the files in root explorer?
thanks for all the help. its much appreciated!
Hello,
I've got a similar problem but this solutions doesn't work for me, because I cannot create a CID.
Any ideas?
Thanks in advance
hi,
i managed to create files etc and still am stuck with the same problem... searched hi and low for days,
hopefully someone will be able to find us a solution..
You mean creating the mtd from that site? Thats because you need to type the Build Number not the kernel version.
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]
This is a how-to to get ATT LG Optimus Pro rooted USING THE FILES PROVIDED BY FIDDY619 AS IN HIS POST FOR THE REGULAR OPTIMUS G here http://forum.xda-developers.com/showthread.php?t=2181103.
So the files are not mine, but the how to is !!!!!!!!!!!!!! Since some people complained about how to use these files on Linux here it is.
I am reproducing my post here:
Thanks to fiddy619 (OP) for the script and files !!
After some failures, I got my ATT LG Optimus G Pro E980 - got today - on Ubuntu. Here is what I had to change to get the linux script Root.sh to work.
YOU MUST HAVE ADB INSTALLED AND WORKING. Your 'adb devices' command in terminal must return a device number or you will get device not found. In Ubuntu, adb is as easy as just downloading and extracting the files and adding the prprper path: see here
http://ubuntuforums.org/showthread.php?t=1918512.
When editing your path dont forget to
$ sudo gedit ~/.bashrc
Then add to the end of the file...after last line:
export PATH=${PATH}:${HOME}/android-sdk-linux/tools:${HOME}/android-sdk-linux/platform-tools
CHANGE the 'tools' and 'platform-tools' folder path to what your file location is. You MAY not need to do the android rules bit if your phone mounts.
FOR UBUNTU:
1. Download and extract files to your favorite location. You need to remember and know the path to the location.
2. The Root.sh uses adb to push the files 'busybox', 'su' and 'superuser.apk' to the phone. HOWEVER, the location of these files depends n where you saved them on the computer.
3. Open Root.sh.
4. Find "$ADB push busybox /data/local/tmp/busybox" and change the first 'busybox' (underlined) to proper location of your file on your Ubuntu. Thus, for me I changed the line as follows:
$ADB push /home/MyUserName/Downloads/Root-Universal-linux/busybox /data/local/tmp/busybox
5. Do this for the followng lines also, changing location of 'su' and 'Superuser.apk' based on where it is on you compu.
$ADB push su /system/xbin/su
$ADB push Superuser.apk /system/app/Superuser.apk
6. Click save to save script file.
7. Put phone in 'Charge Mode' and connect to computer.
8. To run the script open terminal and
$ sudo sh '''drag and drop Root.sh file here"
Hit Enter.
9. Adb will start and it MUST say device found for you to proceed.
10. The next four lines -after 'device found' that show are INSTRUCTIONS FOR YOU. So disconnect phone >>> Disable Usb debugging >>> Enable USB debugging>>> Plug phone back in. ESSENTIALLY DISCONNECT PHONE AND ENABLE DEBUGGING AND THEN RECONNECT.
11. It will do some stuff and show:
uid=0(root), gid=0(root)
"If uid=0(root), gid=0(root) is displayed"
"Press Enter to Continue once phone is running"
"If uid=0(root), gid=0(root) is NOT displayed"
"Press Ctrl+c to quit"
The stuff in quotes again are INSTRUCTIONS. The line before it is what you should see to follow instructions: So if "uid=0(root), gid=0(root)" shows before the instruction set, you are good to go and can press 'enter'.
12. It will push the require busybox/su/etc files and change permissions and reboot. IF YOU GET ANY ERROR HERE ABOUT 'su' file not found, or 'busybox' file not found, then check Root.sh for that you entere the location of the files properly in step 4.
13. After rebooting you should see supersu installed.
Bravo!!!!
HIT THE THANKS BUTTON !!!!
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:
Sorry, had to
Sent from my SGH-I747 using Tapatalk 2
Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest
You need to be rooted for this to work.
CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest