(Copy/Paste the following commands into command window)
adb push busybox /data/local/
adb push psneuter /data/local/
adb push misc.img /data/local/
adb shell chmod 777 /data/local/busybox
adb shell chmod 777 /data/local/psneuter
adb shell /data/local/psneuter
(After you run psneuter ADB is killed but restart itself. This is not a problem.
Copy/Paste into command window)
adb shell /data/local/busybox md5sum /data/local/misc.img
The command window MUST display the following checksum value:
c88dd947eb3b36eec90503a3525ae0de
If it does not match, DO NOT PROCEED! You must redownload the file to your sd card and rename to continue.
(Copy/Paste into command window)
adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
adb reboot bootloader
Once you do this your phone will reboot into the Bootloader. When your phone loads the Bootloader you can unplug the USB cable from your computer. Leave the command prompt window open, we will need it later.
Bootloader should be highlighted in blue. Press the power button to start. (Don’t hold, just press)
The screen will change and Fastboot will be selected. About 10 seconds later it will continue to the next step.
You should see some files loaded and checked. Don’t worry about the warnings, this is normal. Your screen will eventually clear and you will see “checking pg05img.zip.
did all of the above. Confirmed the check sum was correct. when going into fastboot and checking pg05img.zip it stated no image file. I dont want to re boot my phone in case i mess something up. can someone please help? How do i get the image on there correctly from this point?
this is the same step i am stuck at and i narrowed out that its not a spelling error in the file name. It seems that the pg05img.zip removes itself from my SD card everytime i get into the bootloader thats y i cant get to the next step which is to update. Very frustrating. I am going to try another SD card tomorrow.
Depending on how you have your OS configured, it may not show known file extensions. So if you renamed the file to PG05IMG.zip, it may actually be saved as PG05IMG.zip.zip This will not affect the MD5 sum as they are independent of filename, however the bootloader will not recognize this as a PG05IMG file.
Also, I'm not certain about the TB, but most phones do not charge will in the bootloader, so if you let it stay on too long, do not proceed without a bump charge first.
Are you using the most recent rooting method by jcase? And the 5 files required to root? It doesn't sound like the exploits did what they should. What RUU version are you starting with?
I'm looking at what you've said your doing as far as your method and its not the latest jcase method. That said, just copying and pasting big blocks of commands doesn't work. And if you're not using the latest jcase method, I don't know what downloads you've been using and I don't think older ones would work. There's a number of outdated methods on various dev's own websites that won't work. Looks like that's what you've got here. This is the thread you should be following. http://forum.xda-developers.com/showthread.php?t=996616 jcase and the other dev's who've worked on this can also be found on IRC at chat.andIRC.net channel #thunderbolt for live help.
Related
***Note: this is a "for noobs by noobs" post: meant to guide people step-by step. The only needed info I don't cover is BASIC dos commands like "cd" (the only one you really need for this). I didn't post this in development b/c I've added basically nothing except more thorough instructions for noobs like me. Hope this helps!!!***
If Temp Root was worth messing with at all, IMO it was worth messing with in order to do a titanium backup. That's what I was able to successfully with the method below.
I haven't seen this thread's equal here in the 3D forums, so I figured I would repost. All credit where credit is due! Teamwin and then Joel.bourquard for this write-up/slight modification to teamwin's solution.
SO: basically follow the write-up below exactly. I downloaded Titanium Backup and Superuser directly from the market before beginning. Also, after you've finished his steps you can simply click to open Titanium Backup (no need to fool with Superuser) and it'll recognize root, find all your programs(including system data/programs), etc etc. Works like a charm!
NOTE for NOOBS: Download the attached zip --I've included the needed ADB files as well. Attach your EVO 3D using a USB cord and make sure USB debugging is turned ON (check in Settings-->Applications-->Development) and also make sure you aren't letting your PC access your SD card (go to Settings-->Connect to PC and change default to "Charge Only")
Once you've downloaded and unzipped them, open a command prompt (start menu, type "cmd" and type enter). Once in the command prompt, navigate to wherever you downloaded/extracted the zip. FROM THERE, type in each command in the writeup below EXACTLY AS WRITTEN (with quotation marks and everything). Once you've done the last ste (adb shell "/data/bin/root.sh") you can grab your device and open Titanium Backup and VOILA!
----
THE WRITE-UP
Type these commands AS WRITTEN into your cmd prompt after you've (1) downloaded superuser and Titanium Backup from the market (2) downloaded and extracted the zip and (3) navigated your command prompt to the location where you extracted those files.
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
BINGO! Now open Titanium Backup and you're good to go!
For more info, PLEASE see the sources!
http://forum.xda-developers.com/showthread.php?t=1151735
http://therootofallevo.com/forums/viewtopic.php?f=8&t=76
sweet havent gotten it to work for me but ill keep on trying haha guess im a hardcore noob
No worries, me too! As long as you can change directories is dos you should be fine
Sent from my PG86100 using XDA App
panamaniac said:
***Note: this is a "for noobs by noobs" post: meant to guide people step-by step. The only needed info I don't cover is BASIC dos commands like "cd" (the only one you really need for this). I didn't post this in development b/c I've added basically nothing except more thorough instructions for noobs like me. Hope this helps!!!***
If Temp Root was worth messing with at all, IMO it was worth messing with in order to do a titanium backup. That's what I was able to successfully with the method below.
I haven't seen this thread's equal here in the 3D forums, so I figured I would repost. All credit where credit is due! Teamwin and then Joel.bourquard for this write-up/slight modification to teamwin's solution.
SO: basically follow the write-up below exactly. I downloaded Titanium Backup and Superuser directly from the market before beginning. Also, after you've finished his steps you can simply click to open Titanium Backup (no need to fool with Superuser) and it'll recognize root, find all your programs(including system data/programs), etc etc. Works like a charm!
NOTE for NOOBS: Download the attached zip --I've included the needed ADB files as well. Attach your EVO 3D using a USB cord and make sure USB debugging is turned ON (check in Settings-->Applications-->Development) and also make sure you aren't letting your PC access your SD card (go to Settings-->Connect to PC and change default to "Charge Only")
Once you've downloaded and unzipped them, open a command prompt (start menu, type "cmd" and type enter). Once in the command prompt, navigate to wherever you downloaded/extracted the zip. FROM THERE, type in each command in the writeup below EXACTLY AS WRITTEN (with quotation marks and everything). Once you've done the last ste (adb shell "/data/bin/root.sh") you can grab your device and open Titanium Backup and VOILA!
----
THE WRITE-UP
Type these commands AS WRITTEN into your cmd prompt after you've (1) downloaded superuser and Titanium Backup from the market (2) downloaded and extracted the zip and (3) navigated your command prompt to the location where you extracted those files.
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
Click to expand...
Click to collapse
Looks great, yet i have a question..... In your instructions.....you make a command which I believe means to create a new folder.... You use "mkdir"........ I have a lot of
Or school DOS commands in my head and it reminds me of the MD make directory command... Is mkdir correct ?
mkdir is the long version of md, IIRC....
at first i wasn't gonna bother with temp root, but one of the things i did need was titanium backup to restore a bunch of data.
this worked absolutely perfect!
thanks for the great write up
Here's a more detailed explanation than you're likely to find elsewhere, which I wrote:
***Note: this is a "for noobs by noobs" post: meant to guide people step-by step. The only needed info I don't cover is BASIC dos commands like "cd" (the only one you really need for this). I didn't post this in development b/c I've added basically nothing except more thorough instructions for noobs like me. Hope this helps!!!***
If Temp Root was worth messing with at all, IMO it was worth messing with in order to do a titanium backup. That's what I was able to successfully with the method below.
I haven't seen this thread's equal here in the 3D forums, so I figured I would repost. All credit where credit is due! Teamwin and then Joel.bourquard for this write-up/slight modification to teamwin's solution.
SO: basically follow the write-up below exactly. I downloaded Titanium Backup and Superuser directly from the market before beginning. Also, after you've finished his steps you can simply click to open Titanium Backup (no need to fool with Superuser) and it'll recognize root, find all your programs(including system data/programs), etc etc. Works like a charm!
NOTE for NOOBS: Download the attached zip --I've included the needed ADB files as well. Attach your EVO 3D using a USB cord and make sure USB debugging is turned ON (check in Settings-->Applications-->Development) and also make sure you aren't letting your PC access your SD card (go to Settings-->Connect to PC and change default to "Charge Only")
Once you've downloaded and unzipped them, open a command prompt (start menu, type "cmd" and type enter). Once in the command prompt, navigate to wherever you downloaded/extracted the zip. FROM THERE, type in each command in the writeup below EXACTLY AS WRITTEN (with quotation marks and everything). Once you've done the last ste (adb shell "/data/bin/root.sh") you can grab your device and open Titanium Backup and VOILA!
----
THE WRITE-UP
Type these commands AS WRITTEN into your cmd prompt after you've (1) downloaded superuser and Titanium Backup from the market (2) downloaded and extracted the zip and (3) navigated your command prompt to the location where you extracted those files.
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
BINGO! Now open Titanium Backup and you're good to go!
For more info, PLEASE see the sources!
http://forum.xda-developers.com/show....php?t=1151735
http://therootofallevo.com/forums/vi...c.php?f=8&t=76
That's a good write up, but if you want easy, download the script by Jeremy found here: http://forum.xda-developers.com/showthread.php?t=1152101 and run it. Install titanium backup and your all set. No need for all the adb commands and he includes SU and busybox for you.
cruise350 said:
That's a good write up, but if you want easy, download the script by Jeremy found here: http://forum.xda-developers.com/showthread.php?t=1152101 and run it. Install titanium backup and your all set. No need for all the adb commands and he includes SU and busybox for you.
Click to expand...
Click to collapse
This is the same thing. It was made not to long after J.eremy released his method. It suppose to stick and not lose root until reboot. That's why its called better temp root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
r0cky0790 said:
This is the same thing. It was made not to long after J.eremy released his method. It suppose to stick and not lose root until reboot. That's why its called better temp root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
Click to expand...
Click to collapse
Tried both methods, J.eremy's and this one. While i'm able to get the almighty root access. Wifi Tether and Titanium do not recognize it. Although they do request it. guess I'll keep playing with my shell
Facts:
Laptop connected to my phone uses Ubuntu linux
Unlocked my Amaze successfully
I have the RecoveryInstallerForNoobs2.0
I have chmod'ed all the pertient files to be executable
With phone in fastboot mode, doing 'sudo ./fastboot devices' returns the serial number
Problem:
'sudo ./Flash.sh' returns the following output:
./Flash.sh: 1: adb: not found
: not found 2:
Additional facts:
I am a n00b and I am aware my life's output at age 32 is dismal
I have read the "read first for linux..." thread, "how to root" thread and the "faq before posting" thread
I have searched the site but possibly not hard enough, ergo my own impudent thread
What to do??
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Double0EK said:
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Click to expand...
Click to collapse
what he said turn on debugging on your phone. also make sure the zip file is unzipped into a folder
Debugging is on in the settings and the recovery for noobs zip is unzipped.
I flashed mine manually using the fastboot command...
But I only know how to do it with a windows machine.
Put the recovery.img in your AndroidSDK/tools folder , open cmd , cd to the tools folder and type "fastboot flash recovery recovery.img" being if you renamed it to recovery.img..(if it wasn't renamed then you need to type the name of the recovery img.)
Sent by accident from my Amaze using Tapatalk
ryurage said:
Debugging is on in the settings and the recovery for noobs zip is unzipped.
Click to expand...
Click to collapse
don't go to fastboot, the script should automatically kill and restart the adb shell...just turn on your phone and run flash.sh... if that doesn't work Rename the shellscript from flash.sh to flash.command, then associate it with Terminal.app
let me know if those work, if not, I've got some other tricks but it's a little bit more complicated.
@seansk, I renamed the file and tried it with the same resulted output:
./flash.command: 1: adb: not found
: not foundmand: 2:
Btw, I run the flash script one of two ways, 1. sudo ./flash.command or 2. bash flash.command
I could be wrong but I think the issue possibly lies in the script:
adb kill-serveradb reboot bootloaderfastboot flash recovery recovery-cwm-ruby-5.0.2.7.imgfastboot rebootexit
Perhaps adb has to be in my PATH? I'm open to other suggestions too.
One more thought, assuming the adb daemon is shut down, maybe this command would do it: 'sudo ./fastboot flash recovery recovery-cwm-ruby-5.0.2.7.img'?
hmm that thing has been up for months...I've only had two people having trouble and havn't heard back from the other guy...so I hope there's nothing wrong with the scrip...I will look into it again...unfortuantely my vitual machine for mac is down right now, don't know when I'll get it back up and running...
try these
1)To start the shell-script 'file.sh':
sh file.sh
bash file.sh
2)Another option is set executable permission using chmod command:
chmod +x file.sh
Now run .sh file as follows:
./file.sh
ultimately if you have a windows computer it would be much easier...or if you can also here's the new recovery from xboarder I havn't updated this zip file yet... you can edit the recovery script to change the name to this file name: recovery-cwm-ruby-5.5.0.4.img
if all else fails follow the second method here from xboarder (you need an sd card): http://forum.xda-developers.com/showthread.php?t=1316855
Download file to your computer
2. make sure its named PH85IMG.zip
3. Copy to sdcard (external one) then restart your phone in fastboot, by holding down the volume down and power.
4. Wait for it to say do you want to update (press volume up)
5. Press power button to reboot
6. Reboot Phone into recovery as normal and enjoy clockworkmod recovery with fixed charging and sdcard
Well I've had my first issue with my shiny new handset! I rooted it this afternoon and decided to modify the build.prop to change the dalvik heap size as recommended by various people. However on rebooting, the phone's now hanging on the splash screen.
I can get into download and recovery ok - any ideas on how to fix this? Is build.prop editable in either of these modes?
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
As said extract the original one from the rom and push it manually via adb push command
Sent from my GT-I9300 using Tapatalk 2
Oddly enough I used the build.prop editor app from the Play store. Seems that the issue was that it didn't put an 'm' at the end of the line specifying the size - so it read as '128'. Anyway, I've done what you suggested, and it worked - excellent stuff, thanks!
Next time, just use Jota Text Editor on your phone
I have use it many times to edit my build.prop file and never have issue
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
guitarplayer365 said:
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
Click to expand...
Click to collapse
Make sure you're not in a readonly directory on the host,
a default cmd in windows will start in the dir of %ComSpec% (Usually C:\windows\system32).
Abd will try to put files wherever you're located in you filesystem, unless you tell it otherwise. (adb pull {source} [destination])
Sent from my GT-I9300 using XDA
T0yK4T said:
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
Click to expand...
Click to collapse
How do I do ADB pull/push if I can only get to the stock recovery screen? (The one with Mr. Android on his back with the ! above him)
BTW, I'm on a Note 3
Check the permissions!!!!!
The build.prop file should have 644 permissions.
Check if it fits, else change them using adb.
See other thread
http://forum.xda-developers.com/showthread.php?t=1927198
Hi all-
I have unknowingly renamed the framework-res.apk file to framework-res.bak, following the suggestion of a website (who had said to copy the file over, not rename it). I had no idea that would make the phone instantly useless, and render everything inoperative
I was rooted. All I need to do is copy the backup back over, but how?
I am able to get into CMM-based Recovery v5.0.2.7 and can mount the system directory and see it on my PC, but for some reason the framework directory is invisible. There is talk on the web about getting to a prompt and typing:
adb push framework-res.apk /system/framework/framework-res.apk
But how in the world do you get to a prompt? I don't see it on any menu, anywhere and the adb command is unrecognized on my OS.
Hoping I'm not ruined...... thanks for any advice.
Samsung Captivate Glide Android 2.3, Ubuntu
To get ADB, you first have to install the Android SDK.
http://developer.android.com/sdk/index.html
Then, you have to put ADB in the PATH variable.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that, you can just type adb in the command prompt and it should work.
Hi,
I downloaded the SDK tools and got the adb command, but when I mount the phone with recovery I still don't see any framework directory.
I got to DOS and navigated to the directory where my copied framework-res.apk file was, and ran:
c:\adb\adb push framework-res.apk L:\framework\framework-res.apk
it replied with:
1319 kb/s (7979827 bytes in 5.905s)
However, then I rebooted the phone and it won't get past the SAMSUNG screen at all, it just sits there forever.
- why can't I see the framework directory, even though I have mounted it through CWM based recovery?
- can I see it using the ADB tools?
- has just copying the copied file back over, destroyed the cell phone? I can't possibly see how.
Thanks for any help
OK I found out the problem.
you need to use forward slashes and put the whole pathname in:
C:\adb\adb push framework-res.apk /system/framework/framework-res.apk
Thats assuming you have the adb command in the c:\adb directory.
It seems the phone is working again.
WHEW! Man that file is dangerous. be warned.