Related
Alright im already rooted and i flashed clockwork recovery image and I want it gone. I'm trying to go back to Amons recovery image. However when im in the command and I type in adb push recovery-ra-eris.img /sdcard I get no such file or directory error... but i have the file in the tools folder of my androidsdk... any thoughts
fenwaynomar45 said:
Alright im already rooted and i flashed clockwork recovery image and I want it gone. I'm trying to go back to Amons recovery image. However when im in the command and I type in adb push recovery-ra-eris.img /sdcard I get no such file or directory error... but i have the file in the tools folder of my androidsdk... any thoughts
Click to expand...
Click to collapse
Dumb question, but I gotta ask it...
Are you running with the tools folder in your path, so you can execute adb commands from anywhere in the shell? Or are you actually *in* the tools directory as you run the command?
Either way, maybe you should try specifying the full path of recovery-ra-eris.img (as in C:\path\to\recovery-ra-eris.img or /path/to/recovery-ra-eris.img).
I have the tools directory open as im doing the command... i didnt have this problem last time i did this... so idk whats wrong
corrosivefrost said:
Dumb question, but I gotta ask it...
Are you running with the tools folder in your path, so you can execute adb commands from anywhere in the shell? Or are you actually *in* the tools directory as you run the command?
Either way, maybe you should try specifying the full path of recovery-ra-eris.img (as in C:\path\to\recovery-ra-eris.img or /path/to/recovery-ra-eris.img).
Click to expand...
Click to collapse
And isn't the correct version Recovery-RA-eris-v1.6.2?
I downloaded it and thats the recovery image im using but it saves as recovery when i zip it
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
fenwaynomar45 said:
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
Click to expand...
Click to collapse
Here are the steps I have used over and over, so try this. And I used this link for the recovery, so maybe download this one and give these commands and recovery a shot.
Download Link: http://www.sendspace.com/file/jje5xr
Extract file contents to your \tools\ directory of your Android SDK
Open up a command prompt and go to your tools directory, and execute these commands: (MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THESE COMMANDS WON'T WORK! MAKE SURE IT IS ON "CHARGE ONLY")
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
Type dir recovery-ra-eris.img in your c:\AndroidSDK\tools directory. If it comes back with nothing, then you actually put the file somewhere else (don't worry, happens to me from time to time).
fenwaynomar45 said:
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
Click to expand...
Click to collapse
whats with everybody elses free version of rom manager not flashing the alternate recovery? im still a huge fan of ease of use personally. and its always worked im too scared to flash using it but i always flash the recovery when they update just to check it out.
and fyi renaming the recovery to something simple like recovery.img always makes things in the terminal easier as the gentleman above had mentioned
Hi everyone, I am writing this post because there is currently no information on rooting the Telstra specified Motorola Xoom from the Stock 3.1 and still keeping 3G (the latest 3.1 update, not the problematic one). Since I don't have enough post to be able to write in Development section, I just write it over here and I take no credit for this.
With this root, you don't have to flash any custom recovery at all.
1/. Ensure that you have the Motorola Xoom STOCK 3.1, N_01.83.35P, H.6.3-25-5 or you can move back to stock, flash everyback from
developer.motorola.com/products/software/MZ601_H.6.1-38-9_Telstra_Australia.zip/
and receive the official OTA update.
2/. Ensure that you have already UNLOCKED your Motorola Xoom bootloader. This will wipe your device out so be very careful.
3/. Download the attachment file to this thread, which contain the new unsecured boot, su and superuser.apk file
4/. Enable USB Debugging on your Xoom
5/. Open command prompt, write the following code:
Code:
adb reboot bootloader
6/. Now your AU Xoom will reboot, continue to type this:
Code:
fastboot flash boot newtelstraboot.img
fastboot reboot
7/. Wait for your AU Xoom to reboot to HC. Open your command prompt, type this:
Code:
adb remount
adb shell su /system/bin
adb shell ln –s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
Now you got root on your Australian Xoom from Telstra with working 3G.
Cheers
Screenshots:
img638.imageshack.us/img638/1516/screenshot1ew.png
img21.imageshack.us/img21/1907/screenshot2ck.png
Shouldn't be Step 7 more like ->
Step 6
Code:
fastboot flash boot newtelstraboot.img
fastboot reboot
Step 7
Code:
adb remount
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/
adb reboot
BTW: it should be called Non-US Xoom instead of AU Xoom
Oh, thks,
There are something I want to say though:
First, I don't think you should really need a reboot at the end of step 7. It works for me without the need to reboot.
Secondly, I'm not quite sure if my procedure works with other non-AU xoom. I have just been able to test on 3 Australian Telstra Xooms. At least they all work!
However, I'm new so I am willing to learn from you all. Thanks.
Aahk2 is out please use that method instead, fully automated and much easier :
http://forum.xda-developers.com/showthread.php?t=2367322
Warning thanks to hacktrix2006:
hacktrix2006 said:
Also before anyone continues make sure you run cat /proc/kmsg | grep 'mmc0:0001' If you have a M4G2DE EMMC stop do no use clockworkmod recovery or even try to root as you will fry your EMMC.
If you have SEM04G EMMC then your safe to continue.
If your using the PD98IMG.zip from the retired AAHK just remember its no longer support.
Personally i would use the firmware.zip file from the tutorial which is included in the http://tau.shadowchild.nl/files/ace-tools.zip its safer that way just remember to backup your boot.img as its important if you want to boot back into sense 3.0.
Click to expand...
Click to collapse
THIS GUIDE IS MAINLY this guide (http://tau.shadowchild.nl/attn1/?cat=6) SIMPLIFIED TO SOME EXTENT. with parts that werent included in the guide added to the guide and resources added to the ace-tools folder that would have to be downloaded separately.
PREFACE:
Download this and unzip it somewhere (reccommend C:\ root folder): http://www.multiupload.nl/MXW371YT87
Full HTC Desire HD guide to root, S-OFF/Sim Unlock
1.Unlock the bootloader at http://htcdev.com/bootloader/
2.Copy your Unlock_code.bin file that you got in the email to the ace-tools folder.
step 2.2: reboot into fastboot
step 2.3: execute in cmd-prompt "fastboot flash unlocktoken Unlock_code.bin"
3.Download rooted stock rom: http://www.multiupload.nl/20T9R21IGY
(link to rom thread: http://forum.xda-developers.com/showthread.php?t=1382235&highlight=rooted+stock )
step 3.2 Make a effen GOLDCARD!!!
3.3 copy the ROM zip file to your SD card.
4.Install recovery image:
Open cmd and type:
•cd (eg cd C:\ace-tools)
Ensure your phone is connected to your PC and then boot into bootloader, then navigate to fastboot.
In cmd:
•fastboot flash recovery recovery1.img
5.boot into recovery through bootloader and Install the ROM you placed on the SD card, (via install zip fileselect the rom zip)
6.Reboot the phone, ensure the rom is working fine and you have root access you can test this by turning on usb debugging then:
•Adb shell
•Su
You should see the $ turn into a #. If this happens, congrats you have root access.
Then type this:
•Exit
Then again:
•Exit
Then:
•Adb push boot.img /data/local/tmp
•adb shell
root
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
•adb pull /data/local/tmp/boot.img
•adb push goldcard /data/local/tmp
•adb shell
root
chmod 775 /data/local/tmp/goldcard
•adb shell
root
cat /sys/class/mmc_host/mmc2/mmc2:*/cid
take note of the string of numbers and letters that appear.
then:
•adb shell /data/local/tmp/goldcard -c -o /data/local/tmp/goldcard.img
•adb shell
root
dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
•adb push misc_version /data/local/tmp
•adb shell chmod 775 /data/local/tmp/misc_version
•adb shell /data/local/tmp/misc_version -s 1.11.111.1
7.If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
•Fastboot oem lock
Then type:
•fastboot oem rebootRUU
•fastboot flash zip firmware.zip
•fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
•fastboot flash unlocktoken Unlock_code.bin
then flash boot.img in ace-tools folder:
•fastboot flash boot boot.img
next:
•fastboot flash recovery recovery.img
8.boot to recovery again then:
•adb push gfree /tmp/
•adb shell chmod 775 /tmp/gfree
•adb shell /tmp/gfree -f
reboot to bootloader and you should see it says S-OFF at the top of the screen, if It does congrats your done.
VICTORY:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have also posted this over at modaco:
http://www.modaco.com/topic/361797-...-30android-235-guide-to-root-s-offsim-unlock/
Nice work
Report it with the little orange triangle.
bananagranola said:
Report it with the little orange triangle.
Click to expand...
Click to collapse
updated first post again, opened thread in QandA section, thought it was more appropriate, ill leave it to the mods to decide which section it should be in, this thread is based on my experiences last night .
Step 3 reduced, to simpify method even further.
Does not work for me... got bootloop after flashing ROM. Any ideas?
Guide worked for me!!!!!
Hi all, reporting back my experience with this guide...
Prior to using this guide, I was already HTCDEV unlocked, rooted and custom rom (SVHD V1.3.0)
I basically followed this guide with a few little needed changes.
1st I backed up my rom using 4ext recovery.
1. same
2. same
3. same
4. There was no file named "recovery1.img" in ace-tools, so I just flashed the "recovery.img" (If you already have custom recovery flashed, I don't think you need to do this step but I did it anyway).
5. Because I was already on custom rom with different kernel (boot.img) than stock (rooted) rom, before I reboot into recovery, I extracted boot.img from stock rooted zip downloaded from the link and flashed it from fastboot (if you don't do this your rom may not boot).
5a. reboot into recovery and flashed rom
6. there was a typo in the line
"• adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img"
there is an extra space between local & /tmp/ at the end of line, the command line should read
• adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local/tmp/goldcard.img"
7. If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
• Fastboot oem lock<------ phone rebooted itself after this command so needed to go back to bootloader fastboot (I did a quick battery pull)
Then type:
• fastboot oem rebootRUU
everything else was good....
My Hboot screen is the same as OP screen shot.
I reflashed the 4ext recovery I previously had, then did a system restore of my backup and booted into SVHD with out a hitch.
I pretty sure that's all, I hope this helps.
androidmodd said:
I probably won't ever update this.
THIS GUIDE IS MAINLY this guide (http://tau.shadowchild.nl/attn1/?cat=6) SIMPLIFIED TO SOME EXTENT. with parts that werent included in the guide added to the guide and resources added to the ace-tools folder that would have to be downloaded separately.
PREFACE:
Download this and unzip it somewhere (reccommend C:\ root folder): http://www.multiupload.nl/MXW371YT87
Full HTC Desire HD guide to root, S-OFF/Sim Unlock
1. Unlock the bootloader at http://htcdev.com/bootloader/
2. Copy your Unlock_code.bin file that you got in the email to the ace-tools folder.
3. Download rooted stock rom: http://www.multiupload.nl/20T9R21IGY
(link to rom thread: http://forum.xda-developers.com/showthread.php?t=1382235&highlight=rooted+stock )
copy the ROM zip file to your SD card.
4. Install recovery image:
Open cmd and type:
• cd <the directory of the ace-tools folder> (eg cd C:\ace-tools)
Ensure your phone is connected to your PC and then boot into bootloader, then navigate to fastboot.
In cmd:
• fastboot recovery1.img
5. boot into recovery through bootloader and Install the ROM you placed on the SD card, (via install zip fileselect the rom zip)
6. Reboot the phone, ensure the rom is working fine and you have root access you can test this by turning on usb debugging then:
• Adb shell
• Su
You should see the $ turn into a #. If this happens, congrats you have root access.
Then type this:
• Exit
Then again:
• Exit
Then:
• Adb push boot.img /data/local/tmp
• adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
• adb pull /data/local/tmp/boot.img
• adb push goldcard /data/local/tmp
• adb shell chmod 775 /data/local/tmp/goldcard
• adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
take note of the string of numbers and letters that appear.
then:
• adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img
• adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
• adb push misc_version /data/local/tmp
• adb shell chmod 775 /data/local/tmp/misc_version
• adb shell /data/local/tmp/misc_version -s 1.11.111.1
7. If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
• Fastboot oem lock
Then type:
• fastboot oem rebootRUU
• fastboot flash zip firmware.zip
• fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
• fastboot flash unlocktoken Unlock_code.bin
then flash boot.img in ace-tools folder:
• fastboot flash boot boot.img
next:
• fastboot flash recovery recovery.img
8. boot to recovery again then:
• adb push gfree /tmp/
• adb shell chmod 775 /tmp/gfree
• adb shell /tmp/gfree -f
reboot to bootloader and you should see it says S-OFF at the top of the screen, if It does congrats your done.
VICTORY:
View attachment 1858622
I have also posted this over at modaco:
http://www.modaco.com/topic/361797-...-30android-235-guide-to-root-s-offsim-unlock/
help me out if you feel like it by signing up to dropbox with my refferal link:
Always have your stuff when you need it with @Dropbox. Sign up for free! http://db.tt/G8qfL77X
Click to expand...
Click to collapse
ranger4740 said:
Hi all, reporting back my experience with this guide...
Prior to using this guide, I was already HTCDEV unlocked, rooted and custom rom (SVHD V1.3.0)
I basically followed this guide with a few little needed changes.
1st I backed up my rom using 4ext recovery.
1. same
2. same
3. same
4. There was no file named "recovery1.img" in ace-tools, so I just flashed the "recovery.img" (If you already have custom recovery flashed, I don't think you need to do this step but I did it anyway).
5. Because I was already on custom rom with different kernel (boot.img) than stock (rooted) rom, before I reboot into recovery, I extracted boot.img from stock rooted zip downloaded from the link and flashed it from fastboot (if you don't do this your rom may not boot).
5a. reboot into recovery and flashed rom
6. there was a typo in the line
"•adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img"
there is an extra space between local & /tmp/ at the end of line, the command line should read
•adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local/tmp/goldcard.img"
7.If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
•Fastboot oem lock<------ phone rebooted itself after this command so needed to go back to bootloader fastboot (I did a quick battery pull)
Then type:
•fastboot oem rebootRUU
everything else was good....
My Hboot screen is the same as OP screen shot.
I reflashed the 4ext recovery I previously had, then did a system restore of my backup and booted into SVHD with out a hitch.
I pretty sure that's all, I hope this helps.
Click to expand...
Click to collapse
Thanks, ill update first post again.
After using this unlock and S-off method, I have been able to update my radio using the PD98IMG.ZIP via bootloader. file found on this post http://forum.xda-developers.com/showthread.php?p=39412003
Sent from my HTC Desire HD using xda app-developers app
vonski said:
Does not work for me... got bootloop after flashing ROM. Any ideas?
Click to expand...
Click to collapse
For your issue, you had already flashed custom Rom and boot.IMG before this guide? I think You need to flash the boot.IMG from the rom.
Sent from my HTC Desire HD using xda app-developers app
problems at step 8
androidmodd said:
I probably won't ever update this.
THIS GUIDE IS MAINLY this guide (http://tau.shadowchild.nl/attn1/?cat=6) SIMPLIFIED TO SOME EXTENT. with parts that werent included in the guide added to the guide and resources added to the ace-tools folder that would have to be downloaded separately.
PREFACE:
Download this and unzip it somewhere (reccommend C:\ root folder): http://www.multiupload.nl/MXW371YT87
Full HTC Desire HD guide to root, S-OFF/Sim Unlock
1. Unlock the bootloader at http://htcdev.com/bootloader/
2. Copy your Unlock_code.bin file that you got in the email to the ace-tools folder.
3. Download rooted stock rom: http://www.multiupload.nl/20T9R21IGY
(link to rom thread: http://forum.xda-developers.com/showthread.php?t=1382235&highlight=rooted+stock )
copy the ROM zip file to your SD card.
4. Install recovery image:
Open cmd and type:
• cd <the directory of the ace-tools folder> (eg cd C:\ace-tools)
Ensure your phone is connected to your PC and then boot into bootloader, then navigate to fastboot.
In cmd:
• fastboot recovery1.img
5. boot into recovery through bootloader and Install the ROM you placed on the SD card, (via install zip fileselect the rom zip)
6. Reboot the phone, ensure the rom is working fine and you have root access you can test this by turning on usb debugging then:
• Adb shell
• Su
You should see the $ turn into a #. If this happens, congrats you have root access.
Then type this:
• Exit
Then again:
• Exit
Then:
• Adb push boot.img /data/local/tmp
• adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
• adb pull /data/local/tmp/boot.img
• adb push goldcard /data/local/tmp
• adb shell chmod 775 /data/local/tmp/goldcard
• adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
take note of the string of numbers and letters that appear.
then:
• adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img
• adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
• adb push misc_version /data/local/tmp
• adb shell chmod 775 /data/local/tmp/misc_version
• adb shell /data/local/tmp/misc_version -s 1.11.111.1
7. If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
• Fastboot oem lock
Then type:
• fastboot oem rebootRUU
• fastboot flash zip firmware.zip
• fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
• fastboot flash unlocktoken Unlock_code.bin
then flash boot.img in ace-tools folder:
• fastboot flash boot boot.img
next:
• fastboot flash recovery recovery.img
8. boot to recovery again then:
• adb push gfree /tmp/
• adb shell chmod 775 /tmp/gfree
• adb shell /tmp/gfree -f
reboot to bootloader and you should see it says S-OFF at the top of the screen, if It does congrats your done.
VICTORY:
View attachment 1858622
I have also posted this over at modaco:
http://www.modaco.com/topic/361797-...-30android-235-guide-to-root-s-offsim-unlock/
help me out if you feel like it by signing up to dropbox with my refferal link:
Always have your stuff when you need it with @Dropbox. Sign up for free! http://db.tt/G8qfL77X
Click to expand...
Click to collapse
Hi I am having problems from step 8 onwards
8. boot to recovery again then:
• adb push gfree /tmp/
• adb shell chmod 775 /tmp/gfree
• adb shell /tmp/gfree -f
When i type adb push gfree /tmp/ in CMD I get
c:\ace-tools>adb push gfree /tmp/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
c:\ace-tools>
Any ideas I can not seem to get past it
saucernerp said:
Hi I am having problems from step 8 onwards
8.boot to recovery again then:
•adb push gfree /tmp/
•adb shell chmod 775 /tmp/gfree
•adb shell /tmp/gfree -f
When i type adb push gfree /tmp/ in CMD I get
c:\ace-tools>adb push gfree /tmp/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
c:\ace-tools>
Any ideas I can not seem to get past it
Click to expand...
Click to collapse
Hmm that's a problem with ADB on your computer, it can be for a number of reasons, but try restarting your PC checking for background ADB related plugins/processes and try running the commands again.
If it still doesn't work try another PC if available.
androidmodd said:
Hmm that's a problem with ADB on your computer, it can be for a number of reasons, but try restarting your PC checking for background ADB related plugins/processes and try running the commands again.
If it still doesn't work try another PC if available.
Click to expand...
Click to collapse
Thats great thanks got a bit futher now
OK I killed all of the ADB plugins and this is what I now get
c:\ace-tools>adb push gfree /tmp/
2916 KB/s (722728 bytes in 0.242s)
c:\ace-tools>adb shell chmod 775 /tmp/gfree
c:\ace-tools>adb shell /tmp/gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.21
New .modinfo section size: 196
Attempting to power cycle eMMC... Failed.
Module failed to power cycle eMMC.
c:\ace-tools>
I am still show as "ACE PVT SHIP S-ON RL
Anything else
ranger4740 said:
Hi all, reporting back my experience with this guide...
Prior to using this guide, I was already HTCDEV unlocked, rooted and custom rom (SVHD V1.3.0)
I basically followed this guide with a few little needed changes.
1st I backed up my rom using 4ext recovery.
1. same
2. same
3. same
4. There was no file named "recovery1.img" in ace-tools, so I just flashed the "recovery.img" (If you already have custom recovery flashed, I don't think you need to do this step but I did it anyway).
5. Because I was already on custom rom with different kernel (boot.img) than stock (rooted) rom, before I reboot into recovery, I extracted boot.img from stock rooted zip downloaded from the link and flashed it from fastboot (if you don't do this your rom may not boot).
5a. reboot into recovery and flashed rom
6. there was a typo in the line
"•adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img"
there is an extra space between local & /tmp/ at the end of line, the command line should read
•adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local/tmp/goldcard.img"
7.If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
•Fastboot oem lock<------ phone rebooted itself after this command so needed to go back to bootloader fastboot (I did a quick battery pull)
Then type:
•fastboot oem rebootRUU
everything else was good....
My Hboot screen is the same as OP screen shot.
I reflashed the 4ext recovery I previously had, then did a system restore of my backup and booted into SVHD with out a hitch.
I pretty sure that's all, I hope this helps.
Click to expand...
Click to collapse
Did you read this post about the errors in the guide I wrote?
androidmodd said:
Did you read this post about the errors in the guide I wrote?
Click to expand...
Click to collapse
HI
Yep I have read through everything over the last two days and followed all the steps just stumbling at the last hurdle
I'm sorry, you'll have to wait for someone better at this than I am to help, did you ensure that you HTC-Dev unlocked before attempting this step?
androidmodd said:
I'm sorry, you'll have to wait for someone better at this than I am to help, did you ensure that you HTC-Dev unlocked before attempting this step?
Click to expand...
Click to collapse
Gfree failed to cycle eMMC at the end of the s-off procedure, so something's gone wrong.
I don't pretend to be an expert with DHD, and this is a bit different from working with HTC legend.
Just checking that you did the hboot update to version 2.00.029 (htcdev) and unlocked.
It sounds like it might be a hardware fault with phone. I have heard about lots of DHD users with fried eMMC but never with legend.
Sent from my HTC Desire HD using xda app-developers app
ranger4740 said:
Gfree failed to cycle eMMC at the end of the s-off procedure, so something's gone wrong.
I don't pretend to be an expert with DHD, and this is a bit different from working with HTC legend.
Just checking that you did the hboot update to version 2.00.029 (htcdev) and unlocked.
It sounds like it might be a hardware fault with phone. I have heard about lots of DHD users with fried eMMC but never with legend.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Yep I'm on HBOOT 2.00.0029 and my eMMC says boot next to it I just can not get cid to change from ORANG001 and sim is still lock
Bloody ORANGE
everything seemed to work fine until the final stages.
I have even tried Easy Radio tool but this fails after trying to push and I have also tried the Ultimate Multi Tool which allows me to Flash and check status but will not S-Off or Super CID or sim Unlock it just fails at the final stage
Ideas anyone
What radio are you on, you have to have a certain radio to exploit with.
hacktrix2006 said:
What radio are you on, you have to have a certain radio to exploit with.
Click to expand...
Click to collapse
HI
Radio is show as 26.14.04.28_M
Cheers
If you have successfully unlocked your HTC One M7 Bootloader, you will see the following text at the top of your Bootloader screen:
Code:
*** UNLOCKED ***
And, if you installed a custom recovery, it will change to the following:
Code:
*** TAMPERED ***
*** UNLOCKED ***
You can get rid of your TAMPERED text and/or change your LOCKED, RELOCKED or UNLOCKED status. This guide applies to all HTC One M7 Hboot versions.
Minimum requirements:
1. Your HTC One must be S-OFF.
2. Your device must be rooted.
There are different ways of achieving the same results, but this is the easiest (and safest) method using a tool called revone: http://forum.xda-developers.com/showthread.php?t=2314582. Note that revone is primarily intended to be used to S-OFF but it also has some very useful additional features, which are exactly what we're going to use here. You will find all the commands in the original revone thread but if you're having difficulties, then this guide for "noobs" should be helpful.
Stepwise procedure:
1. You need adb and fastboot. Download both in a single package: http://goo.gl/T6InE - credits to mike1986. Extract the folder "mini-sdk" and place it at C:/
2. Download revone: http://revolutionary.io/revone. Place it in your adb and fastboot folder, for example, C:/mini-sdk/
3. Connect your HTC One to your PC via USB cable. Boot up your HTC One and leave it on its homescreen. Test if the USB connection is working by clicking on the Start button > Run > type "CMD". This will open the Command Prompt window. From there, type:
Code:
cd c:\
cd mini-sdk
adb devices
You should see the serial number of your phone to confirm successful adb connection. This is what i get:
Code:
C:\Documents and Settings\Administrator>cd c:\
C:\>cd mini-sdk
C:\mini-sdk>adb devices
List of devices attached
FA36******** device
4. Now, you need to copy revone to your phone. In the same Command Prompt window, type:
Code:
adb push revone /data/local/tmp/
Here is my log to confirm that revone has been successfully copied:
Code:
C:\mini-sdk>adb push revone /data/local/tmp/
2893 KB/s (648208 bytes in 0.218s)
5. Now, open an adb shell by simply typing:
Code:
adb shell
You should see the following:
Code:
C:\mini-sdk>adb shell
[email protected]:/ #
If you see the $ symbol instead of the # symbol, type su (your HTC One needs to be rooted otherwise this won't work).
6. Use the Command Prompt to move to the folder where you placed revone on your phone and and set new permissions:
Code:
cd /data/local/tmp
chmod 755 revone
Here is what it looks like on my Command Prompt window:
Code:
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
7. Now, you can finally remove the TAMPERED text and switch between LOCKED, RELOCKED or UNLOCKED. Following from above, if you want to get rid of the TAMPERED text, type:
Code:
./revone -t
If you want to set the Bootloader as LOCKED, type:
Code:
./revone -l
If you want to set the Bootloader as RELOCKED, type:
Code:
./revone -r
If you want to set the Bootloader as UNLOCKED, type:
Code:
./revone -u
After you've made the changes according to what you want, you can now reboot the device and check if the changes have been applied. Type:
Code:
exit
exit
adb reboot bootloader
You should now be in the Bootloader menu and you can confirm the changes.
If this was useful, just click on the THANKS button!
tried it but stuck here
c:\sdk>adb push revone /data/local/tmp/
then it just sits there any ideas?
nathlynn22 said:
tried it but stuck here
c:\sdk>adb push revone /data/local/tmp/
then it just sits there any ideas?
Click to expand...
Click to collapse
Make sure your phone is on its homescreen (not bootloader or fastboot). Did you follow step 2 and 3? Did you see your serial no. after typing adb devices?
electronical said:
Make sure your phone is on its homescreen (not bootloader or fastboot). Did you follow step 2 and 3? Did you see your serial no. after typing adb devices?
Click to expand...
Click to collapse
yeah mate followed it all just in the end tried couple more times as revone thread said it can crash ETC SO ALL SORTED NOW THANKS. sorry about useless post
Hi, I havev a problem during the procedure :
"You should see the following:
Code:
C:\mini-sdk>adb shell
[email protected]:/ #
If you see the $ symbol instead of the # symbol, type su (your HTC One needs to be rooted otherwise this won't work)."
I see the $ symbol, but when I type su, nothing happend, error " "su"is not recognized as an internal or external command"
I need to reflash a modded recovery to root device ?
I want to return 100% stock
EDIT : the response was : YES ! thanks for your work !
@electronical
thanks for this very easy to understand tutorial buddy
... Note that revone is primarily intended to be used to S-OFF (applicable only if you have Hboot 1.44)...
Click to expand...
Click to collapse
So does that apply only to S-OFF'ing or to everything?
EDIT: I found another method and I successfully reset the TAMPERED flag
worked perfectly. thanks for the great guide :highfive:
commencal661 said:
So does that apply only to S-OFF'ing or to everything?
EDIT: I found another method and I successfully reset the TAMPERED flag
Click to expand...
Click to collapse
By "... Note that revone is primarily intended to be used to S-OFF (applicable only if you have Hboot 1.44)..." what i meant is that you can use revone to S-OFF only if the device has Hboot 1.44, otherwise Rumrunner is required in order to S-OFF.
It's simple enough, but to avoid the remote possibility of anyone else having the same confusion, i have edited that bit of info out. However, it's important to keep in mind that you can't S-OFF with revone if your device has Hboot 1.54 or above. But if your device is already S-OFF, you can use revone to remove the tampered flag and lock/relock/unlock, irrespective of your Hboot version.
Perfect!! Great and simple to follow tutorial.
Thanks!
electronical said:
If you have successfully unlocked your HTC One M7 Bootloader, you will see the following text at the top of your Bootloader:
Code:
*** UNLOCKED ***
And, if you installed a custom recovery, it will change to the following:
Code:
*** TAMPERED ***
*** UNLOCKED ***
You can get rid of your TAMPERED text and/or change your LOCKED, RELOCKED or UNLOCKED status. This guide applies to all HTC One M7 Hboot versions.
Minimum requirements:
1. Your HTC One must be S-OFF.
2. Your device must be rooted.
There are different ways of achieving the same results, but this is the easiest method using a tool called revone: http://forum.xda-developers.com/showthread.php?t=2314582. Note that revone is primarily intended to be used to S-OFF but it also has some very useful additional features, which are exactly what we're going to use here. You will find all the commands in the original revone thread but if you're having difficulties, then this guide for "noobs" should be helpful.
Stepwise procedure:
1. You need adb and fastboot. Download both in a single package: http://goo.gl/T6InE - credits to mike1986. Extract the folder "mini-sdk" and place it at C:/
2. Download revone: http://revolutionary.io/revone. Place it in your adb and fastboot folder, for example, C:/mini-sdk/
3. Connect your HTC One to your PC via USB cable. Boot up your HTC One and leave it on its homescreen. Test if the USB connection is working by clicking on the Start button > Run > type "CMD". This will open the Command Prompt window. From there, type:
Code:
cd c:\
cd mini-sdk
adb devices
You should get the serial number of your phone. This is what i get:
Code:
C:\Documents and Settings\Administrator>cd c:\
C:\>cd mini-sdk
C:\mini-sdk>adb devices
List of devices attached
FA36******** device
4. Now, you need to copy revone to your phone. In the same Command Prompt window, type:
Code:
adb push revone /data/local/tmp/
Here is my log to confirm that revone has been successfully copied:
Code:
C:\mini-sdk>adb push revone /data/local/tmp/
2893 KB/s (648208 bytes in 0.218s)
5. Now, open an adb shell by simply typing:
Code:
adb shell
You should see the following:
Code:
C:\mini-sdk>adb shell
[email protected]:/ #
If you see the $ symbol instead of the # symbol, type su (your HTC One needs to be rooted otherwise this won't work).
6. Use the Command Prompt to move to the folder where you placed revone on your phone and and set new permissions:
Code:
cd /data/local/tmp
chmod 755 revone
Here is what it looks like on my Command Prompt window:
Code:
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
7. Now, you can finally remove the TAMPERED text and switch between LOCKED, RELOCKED or UNLOCKED. Following from above, if you want to get rid of the TAMPERED text, type:
Code:
./revone -t
If you want to set the Bootloader as LOCKED, type:
Code:
./revone -l
If you want to set the Bootloader as RELOCKED, type:
Code:
./revone -r
If you want to set the Bootloader as UNLOCKED, type:
Code:
./revone -u
After you've made the changes according to what you want, you can now reboot the device and check to see if the changes have been applied. Type:
Code:
exit
exit
adb reboot bootloader
You should now be in the Bootloader and you can confirm the changes.
If this was useful, just click on the THANKS button!
Click to expand...
Click to collapse
This is very useful and it works. I am able to S-OFF (Windows 8, 32Bits) and removed the "tempered" and change "unlocked" to "locked" just like original. Crushalot, thanks for this, but can you point out how I can remove the "red descriptions (the development purpose...)" on boot screen and the Tell HTC, please?
Wait to hear from you
Hi there, first of all amazing guide, I've been trying to remove all flags but seemed way too hard to do it , but as easy as it may be I'm kinda stuck here. When I run the adb device command I don't get anything, it doesn't find any device :S any idea what's going on? Also, I'm trying to get my phone to stock for warranty purpose after I've done this if I have available the 4.2 or 4.3 update (I don't remember which one) and I run it through TWRP will this unroot the phone?
THANX http://forum.xda-developers.com/images/smilies/laugh.gif
Ricky-Lim said:
This is very useful and it works. I am able to S-OFF (Windows 8, 32Bits) and removed the "tempered" and change "unlocked" to "locked" just like original. Crushalot, thanks for this, but can you point out how I can remove the "red descriptions (the development purpose...)" on boot screen and the Tell HTC, please?
Wait to hear from you
Click to expand...
Click to collapse
Removing the red banner: http://rumrunner.us/hboots/
Tamiis said:
Hi there, first of all amazing guide, I've been trying to remove all flags but seemed way too hard to do it , but as easy as it may be I'm kinda stuck here. When I run the adb device command I don't get anything, it doesn't find any device :S any idea what's going on? Also, I'm trying to get my phone to stock for warranty purpose after I've done this if I have available the 4.2 or 4.3 update (I don't remember which one) and I run it through TWRP will this unroot the phone?
Click to expand...
Click to collapse
See link above for removing red banner. To go back to 100% stock: http://forum.xda-developers.com/showthread.php?t=2358738
electronical said:
Removing the red banner: http://rumrunner.us/hboots/
See link above for removing red banner. To go back to 100% stock: http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Hi, I used the rumrunner hboot. Red banner removed. OK
I want to go back to 100% stock but I don't want to brick my device!!
I'm in 3.62.401.1 stock rom with the rumrunner hboot.
thanks
Thanks mate!
The "-s 0 -t" from revones description really had me disoriented, didn't seem to work, but your commands worked perfectly! Thanks a lot!!
Hi i followed the commands, I can get rid of the tampered flag but I get an error when I try ./revone -l
[email protected]:/data/local/tmp # ./revone -l
./revone -l
revone v0.2.1
revone failed (error code = -1)
Any idea?
If I am s-off with rumrunner... Can I use this guide to remove tampered? Or is only for renove s-off phones?
Sent from my HTC One using Tapatalk 4
Can this be done in Terminal Emulator?
Sent from my Nexus 7 using xda app-developers app
I s-offed a while ago with revone. I need to send in for warranty. Just looking to get unlocked removed. I already flashed stock recovery. Do I need to have a custom recovery to run -l command?
If so, can I still flash stock recovery after I relock the device?
what is it?
commencal661 said:
So does that apply only to S-OFF'ing or to everything?
EDIT: I found another method and I successfully reset the TAMPERED flag
Click to expand...
Click to collapse
what is the another method bro? thanks
Ok, so I got TWRP on the phone then I used Flash Fire to try and get Android 7 while maintaining custom recovery (and even was supposed to inject SuperSU. It went and did it's thing and on boot I saw SuperSU on phone so I thought hey I am good sweet. HA, Well open it and it said can't find binary, ut oh. I go to manually boot recovery and it wipes user data instead so I lost TWRP.
Well Ok, I thought. Let me LG UP the modified TOT and select refurb to just get me back to Marshmellow with TWRP and try again. YEAH RIGHT. Looks like the Android 7 update blows another qfuse and now LG UP just states anti rollback version is smaller than installed.
I WANT ROOT I PAID FOR THIS THING IN FULL WHY IS IT SOO HARD FOR MANUFACTURERS TO ALLOW ME ACCESS TO MY OWN HARDWARE. When I buy a computer with an OS they don't give me a user only level account and tell me it is for my own good. They allow me to do whatever I WANT because you know why I BOUGHT THE HARDWARE IN FULL AND the supreme court has said no subsidy locks allowed as when a user buys a device it is theirs not yours. I feel this is another version of a subsidy lock at the rate we are going and I can't wait until someone with the time and money sues an OEM and wins us the right to not jump through all these damn hoops to be allowed to do what we wish with the hardware we buy IN FULL NOW.
Ok, rant over, Anyone out there know of a way to root android 7 on the H830? I dunno if a dev could maybe mod up a 20a image so that we can LGUP it to the H830s that have Android 7 and need root.
@RealPariah here ya go follow this Thanks to @godfather123189 for finding these instructions:
i can confirm dirtycow worked for me to reflash twrp. you have to make sure to have the newest version of twrp.img. i was also able to root 20a with the newest supersu.zip.
i will try going back to 10j nandroid i had made before i upgraded to 20a
download all the files from here:
https://build.nethunter.com/android-tools/dirtycow/arm64/
and follow these instructions:
**pushing files**
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb push twrp.img /sdcard/twrp.img
**end pushing files**
1) adb shell
2) cd /data/local/tmp
3) chmod 0777 *
4) ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
5) ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
6) exit
7) adb logcat -s recowvery
"<wait for it to tell you it was successful>"
8) CTRL+C
9) adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
10) adb shell
11) getenforce
"<it should say Permissive, adjust source and build for your device!>"
12) cd /data/local/tmp
13) ./dirtycow /system/bin/run-as recowvery-run-as
14) run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
15) run-as su
16) dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
Well you arent alone. And I agree , I fully own my device and I think I should be able to do what ever the living F*&% I want with it .
Its only a question of time though,these guys are the best there are at cracking through companies 'efforts at locking us out of our own shiznat....in the meantime setup the stuff you can without ROOT (no Titanium Backup....*sniff) LOL.
Before long we'll wake up and see TWRP attached to the ROM like before and all will be well. Cheers
OK after 2 days of attempting this without even wrapping my head around the idea of how to access /data/local/temp without being rooted to begin with I hereby surrender :crying:
Thanks for posting this for dayum sure, I only wish I was a more proficient SDK user as to be able to utilize it.
I mean Im fully versed in the very basics of Fastboot/ADB as a long time Nexus user.Push,pull flashing recoveries and the other relatively easy stuff.But I cant get this worth a crap .....
Thanks guys
Jonathanpeyton said:
OK after 2 days of attempting this without even wrapping my head around the idea of how to access /data/local/temp without being rooted to begin with I hereby surrender :crying:
Thanks for posting this for dayum sure, I only wish I was a more proficient SDK user as to be able to utilize it.
I mean Im fully versed in the very basics of Fastboot/ADB as a long time Nexus user.Push,pull flashing recoveries and the other relatively easy stuff.But I cant get this worth a crap .....
Thanks guys
Click to expand...
Click to collapse
I struggled with it at first I would be glad to assist I'm not at home but when I get home and can access my desktop I would be glad to try to explain it better.
---------- Post added at 06:45 AM ---------- Previous post was at 06:12 AM ----------
Jonathanpeyton said:
OK after 2 days of attempting this without even wrapping my head around the idea of how to access /data/local/temp without being rooted to begin with I hereby surrender :crying:
Thanks for posting this for dayum sure, I only wish I was a more proficient SDK user as to be able to utilize it.
I mean Im fully versed in the very basics of Fastboot/ADB as a long time Nexus user.Push,pull flashing recoveries and the other relatively easy stuff.But I cant get this worth a crap .....
Thanks guys
Click to expand...
Click to collapse
OK here goes my best attempt at explaining it, you need to have your phone turned on with Android debugging turned on as well plug your phone into the pc and then accept the request from adb to access the device. Then start running the adb commands starting with the ones under ***pushing files*** then start following the steps 1-16. Let me know if you have any more questions or something you don't understand. Hopefully this was helpful. P.S. I also had all of the downloaded files inside my adb folder and opened the command window from that folder.
shaneg79 said:
@RealPariah here ya go follow this Thanks to @godfather123189 for finding these instructions:
i can confirm dirtycow worked for me to reflash twrp. you have to make sure to have the newest version of twrp.img. i was also able to root 20a with the newest supersu.zip.
i will try going back to 10j nandroid i had made before i upgraded to 20a
download all the files from here:
https://build.nethunter.com/android-tools/dirtycow/arm64/
and follow these instructions:
**pushing files**
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb push twrp.img /sdcard/twrp.img
**end pushing files**
1) adb shell
2) cd /data/local/tmp
3) chmod 0777 *
4) ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
5) ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
6) exit
7) adb logcat -s recowvery
"<wait for it to tell you it was successful>"
8) CTRL+C
9) adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
10) adb shell
11) getenforce
"<it should say Permissive, adjust source and build for your device!>"
12) cd /data/local/tmp
13) ./dirtycow /system/bin/run-as recowvery-run-as
14) run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
15) run-as su
16) dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
Click to expand...
Click to collapse
This worked great! Thank you! After TWRP was flashed via steps above I just followed the video I linked below from the 8:20 mark and formatted data and then flashed dmverify encrypt and super su (both downloads in vid) and now I'm back to rooted on 7.0 nougat with TWRP and supersu!
Go dirtycow!
Thank you shaneG79 and Genardas this made all the difference!
so An Instruction List ,a Thoughtfully Worded Explanation and You Tube Video are worth a 1000 words
shaneg79 said:
I struggled with it at first I would be glad to assist I'm not at home but when I get home and can access my desktop I would be glad to try to explain it better.
---------- Post added at 06:45 AM ---------- Previous post was at 06:12 AM ----------
OK here goes my best attempt at explaining it, you need to have your phone turned on with Android debugging turned on as well plug your phone into the pc and then accept the request from adb to access the device. Then start running the adb commands starting with the ones under ***pushing files*** then start following the steps 1-16. Let me know if you have any more questions or something you don't understand. Hopefully this was helpful. P.S. I also had all of the downloaded files inside my adb folder and opened the command window from that folder.
Click to expand...
Click to collapse
Any Idea why Im still getting a "permission denied" affter my chmod 0777* here?
1) adb shell
2) cd /data/local/tmp
3) chmod 0777 *
4) ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
that seems to throw it all out of wack..
Jonathanpeyton said:
Any Idea why Im still getting a "permission denied" affter my chmod 0777* here?
1) adb shell
2) cd /data/local/tmp
3) chmod 0777 *
4) ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
that seems to throw it all out of wack..
Click to expand...
Click to collapse
I think there may be a space between the last 7 and the * I can't be sure though because I copy and pasted it into the adb window
shaneg79 said:
I think there may be a space between the last 7 and the * I can't be sure though because I copy and pasted it into the adb window
Click to expand...
Click to collapse
I think you may be right,and as I am copy pasting now Ive been been able to get past it.
I still was able to get root last night with it but was denied access to data in the end so I had to go back.Thank you!
when you finally get to "adb shell reboot recovery" did yours boot to the Firmware Update page? or to something else....mine repeatedly goes to Firmware update then of course isnt seen by adb anymore and no recovery is ever flashed I dont think..
Jonathanpeyton said:
when you finally get to "adb shell reboot recovery" did yours boot to the Firmware Update page? or to something else....mine repeatedly goes to Firmware update then of course isnt seen by adb anymore and no recovery is ever flashed I dont think..
Click to expand...
Click to collapse
No mine rebooted and I finished the rest of the steps I would try going through the steps again and copy and paste everything into adb window. I think in order for twrp to be flashed you have to finish all 16 steps.
shaneg79 said:
No mine rebooted and I finished the rest of the steps I would try going through the steps again and copy and paste everything into adb window. I think in order for twrp to be flashed you have to finish all 16 steps.
Click to expand...
Click to collapse
Roger will do thank you!
nah its no good.No matter what it will only go to that Firmware page.All the commands are correct.It must be something in my setup itself.
I had wondererd am I supposed to leave the cable in for the entirety of the 16 steps (which I have done)?
Jonathanpeyton said:
nah its no good.No matter what it will only go to that Firmware page.All the commands are correct.It must be something in my setup itself.
I had wondererd am I supposed to leave the cable in for the entirety of the 16 steps (which I have done)?
Click to expand...
Click to collapse
Yes I did, you might try using lg up and reflashing 20a and then trying again.
OK I went full on fresh as possible all installs.
Uninstalled reinstalled all drivers/ utils (Uppercut,LGUP ect.)
Copied all instructions to a separate file to ease copying
all before taking your advice (which I thought sounded like the right direction to go) and reflashing 20a.KMZ in LGUP.
Still the result is the same,step 9 (reboot to recovery) leads only to the Firmware Update screen ~~~~~> https://drive.google.com/open?id=0B03a0JRwWhkwX1RQdmlSRmh5c0U AND https://drive.google.com/open?id=0B03a0JRwWhkwT0lMNEViNGIxWkE
Also I want to mention, when I try to directly copy the chmod as is (0777 *) I get a permission denied so Ive been changing it to 0777* (no space between the asterisk [regex] and the last 7) which seems to work as I am able to continue entering code....
man and I thought Samsung devices were a pain to root lol.
Thanks so much for all the help so far Im usually not this much trouble....
Jonathanpeyton said:
OK I went full on fresh as possible all installs.
Uninstalled reinstalled all drivers/ utils (Uppercut,LGUP ect.)
Copied all instructions to a separate file to ease copying
all before taking your advice (which I thought sounded like the right direction to go) and reflashing 20a.KMZ in LGUP.
Still the result is the same,step 9 (reboot to recovery) leads only to the Firmware Update screen ~~~~~> https://drive.google.com/open?id=0B03a0JRwWhkwX1RQdmlSRmh5c0U AND https://drive.google.com/open?id=0B03a0JRwWhkwT0lMNEViNGIxWkE
Also I want to mention, when I try to directly copy the chmod as is (0777 *) I get a permission denied so Ive been changing it to 0777* (no space between the asterisk [regex] and the last 7) which seems to work as I am able to continue entering code....
man and I thought Samsung devices were a pain to root lol.
Thanks so much for all the help so far Im usually not this much trouble....
Click to expand...
Click to collapse
You're not being any trouble I just wish I knew why yours isn't working correctly
ok update..... I used the devices internal settings to do a factory reset then reinstalled 20a.THAT made it to where I am now able to grant the proper permissions to /data/local/tmp.However,I still wind up at the Firmware Update page after >adb shell reboot recovery instead of the recovery screen or just a reboot....but I guess its small progress.
shaneg79 said:
@RealPariah here ya go follow this Thanks to @godfather123189 for finding these instructions:
i can confirm dirtycow worked for me to reflash twrp. you have to make sure to have the newest version of twrp.img. i was also able to root 20a with the newest supersu.zip.
i will try going back to 10j nandroid i had made before i upgraded to 20a
download all the files from here:
https://build.nethunter.com/android-tools/dirtycow/arm64/
and follow these instructions:
**pushing files**
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb push twrp.img /sdcard/twrp.img
**end pushing files**
1) adb shell
2) cd /data/local/tmp
3) chmod 0777 *
4) ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
5) ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
6) exit
7) adb logcat -s recowvery
"<wait for it to tell you it was successful>"
8) CTRL+C
9) adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
10) adb shell
11) getenforce
"<it should say Permissive, adjust source and build for your device!>"
12) cd /data/local/tmp
13) ./dirtycow /system/bin/run-as recowvery-run-as
14) run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
15) run-as su
16) dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
Click to expand...
Click to collapse
Thank you so much... And whom ever is behind this I anyway... One word... Genius... Simply Genius.. Well that was 2 words
Accidental double post see next post, my bad...
Accidental double post