Database Info

How to DOWNGRADE Desire S with S-ON

Warning! I don't recommend this to users who are new to Android since there is a possibility of bricking your device. I will not be responsible if this happens.
It will downgrade everything even the HBoot using a HTC signed ROM. I've downgraded RUU_Saga_Telstra_WWE_1.36.841.3 with HBoot 0.98.0002 to Hboot 0.98.0000 of RUU_Saga_HTC_Thailand_1.35.1113.2.
First you need below tools and applications. I will not explain everything since I'm assuming you already know how to use it and make it.
1. ADB tool to access you device thru shell.
2. ADB driver - you may install HTC Sync since it has ADB driver in it.
3. HEX Editor - I used HxD.
4. Spare micro SD with Goldcard.
5. Card reader to make your life easier.
6. Update.zip ROM you will use to downgrade(rename it to PG88IMG.zip).
6. GingerBreak-v1.20.apk to temp root our device.
Step 1: Copy GingerBreak-v1.20.apk to your spare micro SD and insert it into your phone.
Step 2: Enable USB debugging in your device and connect it to your PC(Charge only). Make sure the drivers are installed properly. If not, install HTC Sync.
Step 3: Install and run GingerBreak-v1.20.apk. It will force close other apps(this is normal just close it). The gingerbreak application will promp that something goes wrong with the rooting(can't remember the actual spiel) but actually we already have our temp root.
Step 4: Run you ADB tool and issue command su to have root access. You can now see in your device that Superuser app is prompting you to allow the ADB root access. Accept it.
Step 5: On the # prompt, issue command dd if=/dev/block/mmcblk0p17 of=/mnt/sdcard/mmcblk0p17.img (to copy mmcblk0p17 to your SDcard). Power off your device and copy mmcblk0p17.img to your PC.(You can also use the command shell to copy it into your PC if you know how to do it).
Step 6: Open mmcblk0p17.img using your Hex editor. On the 11th line(I think), modify the current version to 1.28.401.1(since this is the lowest version I know). Save it and copy back to SDcard. Insert the sdcard and turn your phone on.
Step 7: Run GingerBreak-v1.20.apk again and follow step 3 to 4.
Step 8: On the # prompt, issue command dd if=/mnt/sdcard/mmcblk0p17.img of=/dev/block/mmcblk0p17 (to copy back mmcblk0p17.img to your phone). Do this as quickly as possible since the temp root access sometimes loose its effect.
Step 9: Power off your device and remove your SDcard. Using your card reader, delete everything(not format) in your microSD(with Goldcard) and paste your PG88IMG.zip.
Step 10: Hold volume down + power to boot to recovery and the phone will do the installation itself. Wait until you have your downgraded ROM.
This is how I do it. Hope you won't encounter any problem with this procedure. Good luck!
I want to give thanks to all the XDA members for the knowledge I acquired for this procedure and to the developer of Gingerbreak.
You may also check sonikz procedure on post #4. I think his procedure is faster. You may use which one is easier for you to follow.

Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...

panosfx said:
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
Click to expand...
Click to collapse
Good question i think, if i remember well, on the desire (or HD?) sometimes downgrading was a way of getting to a version of software where you then could get root again !From that point on you could get a recovery installed and install some nice roms. I dont know if thats whats going on here, i wouldn't dare to hope that ...?

Me n00b me downgrade
Newrad67, I have compiled a n00b way to achieve very similar results:
First off you need to create a Gold Card
Use the memory card that came with the phone, may as well hey!
Install Goldcard helper from market, run it and copy the CID for MMC2
This number has already been reversed so go to here, fill out the required fields.
That will then email you an image file. You can then using Gold Card Tool flash your image file to your phones SD card via the phones USB cable.
Next for the actual downgrade
You'll need this unzipped
in a command prompt, goto the directory you unzipped to
connect the phone via USB
then:
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
Click to expand...
Click to collapse
This copies the files to the phone and changes the permissions so they will function
adb shell
Click to expand...
Click to collapse
This will enter the terminal for the phone
./data/local/tmp/GingerBreak
Click to expand...
Click to collapse
This will then temp root the phone you should now have # at the terminal prompt instead of $, which means you have higher privileges
From this point you can then run misc_version (Thanks to Blezz for the version number) This changes the version reported by the phone to 1.27.405.6, you cannot check this on the phone tho, as it will still report the other number.
cd /data/local/tmp
./misc_version -s 1.27.405.6
Click to expand...
Click to collapse
From here you can then install the update/downgrade from the exe, no need to dump zip files or anything. As with anything here, results may vary and I won't be buying new hardware if it breaks yours! But it works a treat on mine.

This can be used with paulobriens test signed RUU HTC update to get root/boot/recovery installed on s-on .
If it just were public
Sent from my HTC Desire S using XDA Premium App

panosfx said:
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
Click to expand...
Click to collapse
This is why I recommend this only to advance users.
Our Desire S with S-On was released with Gingerbread ROM and Hboot that still not possible(as of now) to have custom boot recovery. Since we are on S-On, it is still not possible to be rooted and use custom ROM.
As far as I know, we don't have any official ROM except for Gingerbread. Correct me if I'm wrong. The list can be seen in this post. http://forum.xda-developers.com/showthread.php?t=1002506
I'm just sharing this to people who wants to change their ROM if they want to change to a different one. Like me who installed the latest ROM from TELSTRA and find the bloatware annoying. I've done this to get back to the ROM I'm more comfortable using.

Yeah I'm pretty much with you mate, no way to do anything more practical than flash a clean European Rom currently..... Not really a vast amount of progress either. Anything we should be doing to help get permanent root? Anyone?
Sent from my HTC Desire S using XDA App

Thankkssssss
It works on my s-on DS
Thanks a lot

i really like it how sonikz is doing now like it was his idea how to downgrade it using adb gingerbreak and misc_version lol
i'm gonna stop my rooting tries + supporting here for the desire s, hating such people like him

I never said it was my idea and I have in a posted my thanks to the relevant people in other threads, I didn't mean to rub anyone the wrong way... I hadn't seen a adb version of gingerbreak until Friday and I'm sure you know the apk is very unpredictable or at least it is on my phone so I couldn't use misc_version, it just kept kicking errors.... Hey I just threw it out there, my bad

okay
no it isnt the apks fault, maybe u forgot to use "su" in adb shell after using the apk, which u dont need for the command line version
anyway, maybe there is a way to get past the s-offf
in titanium backup there's a recovery exploit to remove files from s-on phones
we just need to know how the exploit is working and if it still working with 2.3
2nd option is i am getting a 2nd desire s soon.. it's a bugged on, radio destroyed and he don't get it repalced so he gives it me
maybe i can get the desire hd bootloader running somehow.. even if i am sure it will be a lot of work to get in

Plz guys... Get a grip.. we share.. whocares about credit.. come on..
Keep sharing.
Sent from my HTC Desire S using XDA Premium App

Worked
Sent from my HTC Desire S using XDA Premium App

@Rexton270: what worked?
@brokenworm: what you meant by the paulobriens test RUU?

@brokenworm:
it's not paul's ruu, the files he published been released 1 day before at 911snipers blog
sadly without ruu too

what ROM to get root
after doing that, what ROM is it better to download in order to become root ?
thanks

pdaGeek13 said:
after doing that, what ROM is it better to download in order to become root ?
thanks
Click to expand...
Click to collapse
If you are on S-ON, none as of now.
Sent from my HTC Desire S using XDA Premium App

> 2 hours
running for more than 2 hours now, normal ?
sonikz said:
Newrad67, I have compiled a n00b way to achieve very similar results:
First off you need to create a Gold Card
Use the memory card that came with the phone, may as well hey!
Install Goldcard helper from market, run it and copy the CID for MMC2
This number has already been reversed so go to here, fill out the required fields.
That will then email you an image file. You can then using Gold Card Tool flash your image file to your phones SD card via the phones USB cable.
Next for the actual downgrade
You'll need this unzipped
in a command prompt, goto the directory you unzipped to
connect the phone via USB
then:
This copies the files to the phone and changes the permissions so they will function
This will enter the terminal for the phone
This will then temp root the phone you should now have # at the terminal prompt instead of $, which means you have higher privileges
From this point you can then run misc_version (Thanks to Blezz for the version number) This changes the version reported by the phone to 1.27.405.6, you cannot check this on the phone tho, as it will still report the other number.
From here you can then install the update/downgrade from the exe, no need to dump zip files or anything. As with anything here, results may vary and I won't be buying new hardware if it breaks yours! But it works a treat on mine.
Click to expand...
Click to collapse

no not normal, restart your phone and try again
cause it's s-on nothing can happen to your system so don't worry and just restart

Blezz said:
no not normal, restart your phone and try again
cause it's s-on nothing can happen to your system so don't worry and just restart
Click to expand...
Click to collapse
same thing with this log:
$ ./GingerBreak
./GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 s
[**] (C) 2010-2011 The Android Exploid Crew. All rig
[**] Kudos to jenzi, the #brownpants-party, the Open
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 25104 GOT start: 0x00014360 GOT end: 0x000
[*] vold: 25104 idx: -1024 fault addr: 0xfffb2284
[*] vold: 25162 idx: -2048 fault addr: 0xfff4e284
[*] vold: 25212 idx: -3072 fault addr: 0xffeea284
[*] vold: 25262 idx: -4096 fault addr: 0xffe86284
[*] vold: 25312 idx: -5120 fault addr: 0xffe22284
[*] vold: 25363 idx: -6144 fault addr: 0xffdbe284
[*] vold: 25414 idx: -7168 fault addr: 0xffd5a284
[*] vold: 25466 idx: -8192 fault addr: 0xffcf6284
etc ....
and sometimes:
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
:-(

[GUIDE] STOCK (8.2.3.9/8.2.3.13/8.4.4.5) to 3.1 (PRIME! v1.4) + Overclock!

This guide is for you if you currently have a STOCK EEE Pad transformer running on the 8.2.3.9, 8.2.3.13, or 8.4.4.5 update If you are already rooted and have CWM, skip to part 3 or 4 as appropriate
I rooted and upgraded to 3.1 yesterday and found the guides a bit scattered (and may be hard for Android newcomers to understand). I thought I'd write a new consolidated step-by-step guide for everyone
IF YOU WOULD LIKE A VIDEO TUTORIAL, PLEASE LET ME KNOW! IF THERE'S ENOUGH INTEREST, I'LL MAKE ONE!
SKIP TO PART 2 IF YOU ARE ALREADY ON 8.2.3.9
REQUIREMENTS:
-MicroSD card (THIS MUST BE IN YOUR TRANSFORMER AT ALL TIMES DURING THIS PROCESS!)
-Patience
-Brain
If you'd like to download all of the files first, the steps highlighted in GREEN contain files you need to download.
DISCLAIMER: As always, this guide is for information purposes only. I cannot be held responsible for any damage you may incur on your device. Proceed at your own risk!
ALSO, THIS WILL WIPE YOUR INTERNAL/EXTERNAL SD CARD SO HAVE EVERYTHING BACKED UP JUST IN CASE
PART 0: ADB and Drivers
1) Download adb from here: http://www.mediafire.com/file/vix9hcmm23ohtbc/adb.zip
and the ASUS ADB Drivers from here: http://www.mediafire.com/file/rgr9d77picbxwz3/ASUS_Android_USB_drivers_for_Windows.zip
2) Unzip the contents of adb.zip to C:\Android
3) Install the ASUS ADB drivers
4) On your transformer, go to Settings -> Applications -> Development and make sure "USB Debugging" is checked
5) Plug in your TF into your computer via USB
6) Open a command prompt (WinXP: Start -> Run -> cmd | Vista/7: Start -> type "cmd" and hit enter)
7) Type
Code:
cd C:\Android
8) To test whether ADB is working, type the following into the command prompt and hit enter
Code:
adb devices
If you've done everything correctly up to this point, you should see a bunch of numbers listed under "List of devices attached"
PART 1: Downgrading to 8.2.3.9
The 8.2.3.13 update is currently unrootable so we'll need to downgrade to 8.2.3.9 first
1) Grab the 8.2.3.9 upgrade from here (THIS IS FOR THE US SKU ONLY!): http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
If you have the WW SKU (not in the US), download this one: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_WW_epad_user_8239.zip
If you have the TW SKU, download this one: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_TW_epad_user_8239.zip
2) Open up the file you downloaded in step 1 and unzip the Asus folder onto the ROOT directory of your microSD card. Make sure you copy the entire Asus folder and not just the files inside it!! The transformer will NOT detect the update file if there is no Asus folder on the root of your SD card.
3) Insert your microSD card into your Transformer. On the bottom right hand corner in the notification area, there should be a message saying that an update has been detected. Tap that message to start the update. Let it do its thing (it'll take about 5-10 minutes and reboot once it's done)
PART 2: Rooting and installing CWM
Now we'll need to root and install Clockwork Mod Recovery
4) Download the following root package: http://www.mediafire.com/file/1otzpglspbfb9p8/TF101_ROOT.zip
5) Unzip the contents of the root package into C:\Android
6) Open a command prompt and navigate to C:\Android (type "cd c:\Android" without the quotes)
7) Type the following commands in order
Code:
adb push gingerbreakBB /data/local/
Code:
adb shell chmod 777 /data/local/gingerbreakBB
Code:
adb shell
Code:
/data/local/gingerbreakBB
This should execute the gingerbreak program which will do the dirty work for us After about 5-10 minutes, you should be presented with a "#" symbol, which means root has been acquired.
DO NOT CLOSE THIS WINDOW!!
If you get an error, type "exit" (without quotes) and hit enter. Then reboot your TF and try it again:
Code:
adb shell
Code:
/data/local/gingerbreakBB
8) Download hashmyfiles.zip from: http://www.mediafire.com/file/o1tkpx159919hp8/hashmyfiles.zip
This program calculates the MD5 checksum of a file. We need to make sure our CWM file isn't corrupted or else you can brick your Transformer.
9) Run hashmyfiles and drag CWM_BLOB_V5 from C:\Android into the window. The MD5 checksum should be 8c9ef19b726e76fd73de4632db7e4288. If this doesn't match, redownload the root package and try again.
10) Open a new command prompt window and navigate to C:\Android once again
11) Type the following in order
Code:
adb push CWM_BLOB_V5 /data/local
Code:
adb pull /data/local/CWM_BLOB_V5 cwmblob_retransfer
There should now be a file in C:\Android called "cwmblob_retransfer". Drag this file into hashmyfiles and see if the MD5 checksum is 8c9ef19b726e76fd73de4632db7e4288. If it isn't, repeat step 11 and try again.
12) Return to the shell I told you to keep open in step 7 and type
dd if=/data/local/CWM_BLOB_V5 of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
13) Your TF will reboot (if it doesn't reboot by itself, do it manually) and you will see a progress bar on the ASUS EEE Pad logo splash page.
14) Your device is now rooted with CWM installed!
PART 3 (OPTIONAL, HIGHLY RECOMMENDED): CWM3.1.0.1 mod by solarnz
This part installs a modded ClockworkModRecovery developed by solarnz. It skips /data/media (your internal storage partition) during Nandroid backups and factory wipe/resets. This way, your internal storage isn't wiped during nandroid backup/restores.
15) Download the modded CWM from here: http://dl.dropbox.com/u/13093938/XDA/Transformer/recovery-3.1.0.1-solarnz-R3-240511-1908.zip
MD5 checksum is 4470bee75f3318f07ec1eb5ddcee1f96.
16) Move the zip file (do not unzip) to the root of your microSD card and insert into your Transformer.
17) Reboot your Transformer into CWM:
Turn Transformer off
Hold down the POWER button and the VOLUME DOWN button simultaneously until you see a message on the top left portion of the screen
When you see this message, release the two buttons and immediately press VOLUME UP as the message states
18) Scroll down to "Install Zip From SD card" using the VOLUME DOWN button and hit the power button to select it
19) Scroll down to "Choose Zip form SD Card" and hit the power button
20) Select "recovery-3.1.0.1-solarnz-R3-240511-1908.zip" and flash it!
21) Reboot your Transformer!
PART 4: PRIME! v1.4
22) Download the latest build of PRIME! v1.4 from here: http://forum.xda-developers.com/showthread.php?t=1052380
23) Make sure you verify the MD5 checksum before you transfer it!
24) Copy the ROM zip file over to the root of your microSD card and reboot your Transformer into CWM
Turn Transformer off
Hold down the POWER button and the VOLUME DOWN button simultaneously until you see a message on the top left portion of the screen
When you see this message, release the two buttons and immediately press VOLUME UP as the message states
25) Repeat steps 18-20, but this time, select the PRIME! ROM zip file and flash that.
26) BAM WELCOME TO Rooted HONEYCOMB 3.1!!!
PART 5 (optional): Overclocking
In order to overclock, we will need to use a custom kernel. The only custom kernel as of this post is the Clemsyn-Blades overclocking kernel (currently on version 5). It offers up to a 1.6Ghz overclock (stock is 1Ghz)! Not all Tegra2 processors can run at this speed though so your mileage may vary!
27) Grab the latest overclocking kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1109630
28) Copy the kernel zip file to your internal SD card
29) Reboot into ClockworkMod Recovery and make a Nandroid backup by going to "Backup and Restore".
30) Install the kernel by going to "install zip from SD card" and selecting the kernel file
31) Wipe the cache by selecting "Wipe cache partition"
32) Wipe the dalvik-cache by selecting "Advanced" then "Wipe Dalvik Cache)
33) Reboot and grab CPU Master from the Market
34) Set your overclock and you're good to go If you get lockups, try reducing the overclock
FAQ/Troubleshooting:"]
Q: HELP! I closed the shell window when I wasn't supposed to! Now it just tells me "Cannot copy bootmsh. Permission denied"
A: Run the following commands in a new terminal window and start over
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
Q: CWM gives me the error: "E:can't mount /sdcard"
A: Format your SD card with your computer, and try copying the files onto the SD again.
CREDITS:
Androidroot.mobi for the original rooting guide
solarnz for the modded CWM
Roach2010 for making PRIME! v1.4
clemsyn for the Clemsyn-Blades overclocking kernel
Thanks for reading If you're feeling generous, feel free to buy me a beer

Awesome guide mate, good work.

Roach2010 said:
Awesome guide mate, good work.
Click to expand...
Click to collapse
Wouldn't be possible without your work on Primordial

PART 1: Downgrading to 8.2.3.9
The 8.2.3.13 update is currently unrootable so we'll need to downgrade to 8.2.3.9 first
2) Open up the file you downloaded in step 1 and unzip the Asus folder onto the ROOT directory of your microSD card. Make sure you copy the entire Asus folder and not just the files inside it!! The transformer will NOT detect the update file if there is no Asus folder on the root of your SD card.
3) Insert your microSD card into your Transformer. On the bottom right hand corner in the notification area, there should be a message saying that an update has been detected. Tap that message to start the update. Let it do its thing (it'll take about 5-10 minutes and reboot once it's done)
I have to downgrade from 3.1 US leaked to 8.2.3.9 WW the method that you wrote does not work (for me) I tried several times but the update stops almost instantly after reboot with an exclamation mark..
some help?

MimiK said:
PART 1: Downgrading to 8.2.3.9
The 8.2.3.13 update is currently unrootable so we'll need to downgrade to 8.2.3.9 first
2) Open up the file you downloaded in step 1 and unzip the Asus folder onto the ROOT directory of your microSD card. Make sure you copy the entire Asus folder and not just the files inside it!! The transformer will NOT detect the update file if there is no Asus folder on the root of your SD card.
3) Insert your microSD card into your Transformer. On the bottom right hand corner in the notification area, there should be a message saying that an update has been detected. Tap that message to start the update. Let it do its thing (it'll take about 5-10 minutes and reboot once it's done)
I have to downgrade from 3.1 US leaked to 8.2.3.9 WW the method that you wrote does not work (for me) I tried several times but the update stops almost instantly after reboot with an exclamation mark..
some help?
Click to expand...
Click to collapse
Did you initiate the update from the notification? Also, do you have the US or WW version (hardware-wise, not the currently installed software)

r34p3rex said:
Did you initiate the update from the notification? Also, do you have the US or WW version (hardware-wise, not the currently installed software)
Click to expand...
Click to collapse
start from the notification, my hardware is WW (italian) with 3.1 US leaked

Did you download the WW downgrade file? I just added it to the guide

r34p3rex said:
Did you download the WW downgrade file? I just added it to the guide
Click to expand...
Click to collapse
yes, but it did not work for me .. I solved it with a guide found on a French forum.
1. I renamed the file WW_epad-user-8.2.3.9.zip in EP101_SDUPDATE.zip
2. I put it in the root of microsd
3. restarted with vol down + power, then vol up
4. I waited until the end of the installation
5. I restarted with vol down + power and I did the wipe
now have 3.0.1 ww 8.2.3.9 and I'm ready to root, and primordial
thanks very much !

I'm getting to the part right after rooting and at the bottom it says:
[!] dance forever my only one
# _
when I go to type something in this window nothing happens...any advice?
UPDATE: FIXED! My cmd prompt must have frozen...Just had to run: adb shell rm /data/local/tmp/boomsh & adb shell rm /data/local/tmp/sh and start over from step #7. Have clockwork installed and am about to flash primordial 3.1.

dude.... awesome work...
But u wouldnt believe how retarded people can get.
So despite of the huge big red "do not close the shell", i closed it!
now when i start over from the beginning, i get "cannot copy boomsh. : permission denied". WAT DO I DO???

MimiK said:
yes, but it did not work for me .. I solved it with a guide found on a French forum.
1. I renamed the file WW_epad-user-8.2.3.9.zip in EP101_SDUPDATE.zip
2. I put it in the root of microsd
3. restarted with vol down + power, then vol up
4. I waited until the end of the installation
5. I restarted with vol down + power and I did the wipe
now have 3.0.1 ww 8.2.3.9 and I'm ready to root, and primordial
thanks very much !
Click to expand...
Click to collapse
Cool, good info to have

psycho2097 said:
dude.... awesome work...
But u wouldnt believe how retarded people can get.
So despite of the huge big red "do not close the shell", i closed it!
now when i start over from the beginning, i get "cannot copy boomsh. : permission denied". WAT DO I DO???
Click to expand...
Click to collapse
Run the following commands, and start over
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh

Can this be used with netformer kernal? I installed and it wouldnt boot. If it cant is there another kernal that will make it overclock.

So I got my tablet downgraded to 8.2.3.9, and when I run the gingerbreakBB from the shell, it runs for a few minutes and it shows the following...
Code:
[*] vold: 0918 idx: -0021540
[*] vold: 0918 idx: -0021539
--code break--
[*] vold: 0918 idx: -0020901
[-] Bad luch. Fixed vold?
$
So the fact that it didn't show #, I'm assuming it failed. I ran the gingerbreakBB again from that $, and got this.
Code:
$ /data/local/gingerbreakBB
/data/local/gingerbreakBB
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Detected honeycomb! Starting honeybomb mode (scale=10).
[+] Found system: 0xaff181a1 strcmp: 0xaff37b85
[+] Found PT_DYNAMIC of size 240 (30 entries)
[+] Found GOT: 0x00017368
[+] Using device /devices/platform/sdhci-tegra.2/mmc_host/mmc1
[*] vold: 0918 GOT start: 0x00017368 GOT end: 0x000175e8
Now I get a permission denied if I try typing su at the shell. What happened? What do I need to do??

mike6200 said:
Can this be used with netformer kernal? I installed and it wouldnt boot. If it cant is there another kernal that will make it overclock.
Click to expand...
Click to collapse
3.0.1 kernels can't be used with 3.1. Until ASUS releases the source of the 3.1 kernel, I'm afraid we won't have any custom kernels
tycoonbob said:
So I got my tablet downgraded to 8.2.3.9, and when I run the gingerbreakBB from the shell, it runs for a few minutes and it shows the following...
Code:
[*] vold: 0918 idx: -0021540
[*] vold: 0918 idx: -0021539
--code break--
[*] vold: 0918 idx: -0020901
[-] Bad luch. Fixed vold?
$
So the fact that it didn't show #, I'm assuming it failed. I ran the gingerbreakBB again from that $, and got this.
Code:
$ /data/local/gingerbreakBB
/data/local/gingerbreakBB
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Detected honeycomb! Starting honeybomb mode (scale=10).
[+] Found system: 0xaff181a1 strcmp: 0xaff37b85
[+] Found PT_DYNAMIC of size 240 (30 entries)
[+] Found GOT: 0x00017368
[+] Using device /devices/platform/sdhci-tegra.2/mmc_host/mmc1
[*] vold: 0918 GOT start: 0x00017368 GOT end: 0x000175e8
Now I get a permission denied if I try typing su at the shell. What happened? What do I need to do??
Click to expand...
Click to collapse
Reboot and try running gingerbreakBB again

r34p3rex said:
Reboot and try running gingerbreakBB again
Click to expand...
Click to collapse
After rebooting the tablet, rm the gingerbreakBB and recopying it to /data/local/, I re-ran the gingerbreakBB from shell, not showing any progress yet. Going to give it to 10:45 EST to report what's happened.
Thanks.

Can i just install a 3.0.1 over my 3.1
I am rooted

tycoonbob said:
After rebooting the tablet, rm the gingerbreakBB and recopying it to /data/local/, I re-ran the gingerbreakBB from shell, not showing any progress yet. Going to give it to 10:45 EST to report what's happened.
Thanks.
Click to expand...
Click to collapse
After 11 minutes, the prompt never did anything. Closed prompt, reopened and rm gingerbreakBB from shell. Turned tablet off, inserted sdcard (per instructions from http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/) says sdcard must be in at all times, which I did not have. Copied gingerbreakBB back to /data/local/, re ran the program from shell and now it's actually doing something.
Just finished, and showed #. That proves that you MUST have a MicroSD Card inserted at all times during the root process. Might want to add that to your guide. Now I will finish up, and let you know how it goes.
Thanks!

Nice guide! Wish it was out for me when i was doing this stuff to my TF the other night!

tycoonbob said:
After 11 minutes, the prompt never did anything. Closed prompt, reopened and rm gingerbreakBB from shell. Turned tablet off, inserted sdcard (per instructions from http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/) says sdcard must be in at all times, which I did not have. Copied gingerbreakBB back to /data/local/, re ran the program from shell and now it's actually doing something.
Just finished, and showed #. That proves that you MUST have a MicroSD Card inserted at all times during the root process. Might want to add that to your guide. Now I will finish up, and let you know how it goes.
Thanks!
Click to expand...
Click to collapse
Good to know! Will add it
mike6200 said:
Can i just install a 3.0.1 over my 3.1
I am rooted
Click to expand...
Click to collapse
Do you have CWM installed? Are you on official 3.1?

[q] Samsung Admire rooting

Is there any possible way to root the new Samsung Admire for Metro PCS?
I've tried:
GingerBreak
Z4root
Universal Root(I think the name is)
Haven't tried:
Superoneclick
Any idea's or anything?

Dude!! Thank You for putting up this thread.. made me register to the site. Anyhow I have had the phone for a good 4 days now and I have been searching ALL over the internet.. Nothing.. I think you are the first person to post this. LOL you beat me f***ER. Anywaysz. I tried GingerBreak also.. didnt know about it till today.. Nothing...
BTW just want you to know i tried superOneClick first and it doesnt work.. not on 2.3.4 anyway.. i think only up to 2.2.1? soo Yeaa. WE need something here.. If we work together i think we can get something sooner lol. SOMEONE HELP US!
Samsung Admire
Gingerbread.EH02
Android 2.3.4
Metro PCS
Kernel 2.6.35.7
Great phone btw.. 800mhz.. looking to root and hopefully ill be able to hit the ghz... Paid only $80 for it with new line.. that i dont even need a contract for.. love metro man..

Same here, got one for my wife yesterday. Any devs out there with some good advise?

me too i just made an account so i can post this, GINGERBREAD.EH02 is he build number btw if anyone might need it. I hope someone makes this phone rootable, i miss my setcpu and wifi tethering from my optimus v

HELPPP PLEASE. Samsung Admire. New Phone. 2.3.4. Break. Metro PCS.
Anyone!! please.. anybody. Im dying here. We need an OC K at least. Any one click fix to root this samsung phone. Maybe a few changes to a couple lines of an existing break. Cant be too Different than the rest out there. 2.3.4 we need to break it.

We need it bad

I'm in the same boat, had it since Thursday and looking forward to rooting it.

SuperOneClick 2.1.1 Log
SuperOneClick v2.1.1.0
Checking drivers...
Failed
Killing ADB Server...
OK 0.73s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.58s
Waiting for device...
OK 0.44s
2.3.4
Getting manufacturer...
samsung
OK 0.03s
Getting model...
SCH-R720
OK 0.11s
Getting version...
EH02
OK 0.09s
Checking if rooted...
False
OK 0.19s
Installing BusyBox (temporary)... - Step #1
527 KB/s (1062992 bytes in 1.968s)
OK 2.48s
Installing BusyBox (temporary)... - Step #2
OK 0.08s
Rooting device... - Step #1
rm failed for /data/local/tmp/boomsh, No such file or directory
OK 0.06s
Rooting device... - Step #2
rm failed for /data/local/tmp/sh, No such file or directory
OK 0.03s
Rooting device... - Step #3
525 KB/s (16830 bytes in 0.031s)
OK 0.58s
Rooting device... - Step #4
OK 0.09s
Rooting device... - Step #5
OK 0.03s
Rooting device... - Step #6
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x000163b4
[+] Using device /devices/platform/msm_sdcc.1/mmc_host
[*] vold: 0000 GOT start: 0x000163b4 GOT end: 0x000163f4
OK 30.97s
Rooting device... - Step #7
OK 27.41s
Remounting /system with read-write access...
mount: Operation not permitted
FAILED
Does anyone know how to get around this? I need to change the Location to Read-Write.. no clue how to though.

I joined these forums to learn how to root my admire, and so it seems its not possible yet?

Samsung admire root?
Does anyone have any idea how to root this or when a root will be made for this I can see it becoming a popular phone for the price and features. I can't wait for a root for this anyone have any idea how long it will take before one is released? For the price of the phone it is incredibly nice much nicer and faster than the optimus or huawei M835

Samsung Admire ROOT
Ugh been looking everywhere 2... I guess its just to soon

I am also in search of Root for the Admire.

There might be one way but I don't know how to boot into our recovery menu.
http://androidforums.com/admire-all-things-root/400892-question.html#post3128788

Egypt1ancraz said:
SuperOneClick v2.1.1.0
Checking drivers...
Failed
Killing ADB Server...
OK 0.73s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.58s
Waiting for device...
OK 0.44s
2.3.4
Getting manufacturer...
samsung
OK 0.03s
Getting model...
SCH-R720
OK 0.11s
Getting version...
EH02
OK 0.09s
Checking if rooted...
False
OK 0.19s
Installing BusyBox (temporary)... - Step #1
527 KB/s (1062992 bytes in 1.968s)
OK 2.48s
Installing BusyBox (temporary)... - Step #2
OK 0.08s
Rooting device... - Step #1
rm failed for /data/local/tmp/boomsh, No such file or directory
OK 0.06s
Rooting device... - Step #2
rm failed for /data/local/tmp/sh, No such file or directory
OK 0.03s
Rooting device... - Step #3
525 KB/s (16830 bytes in 0.031s)
OK 0.58s
Rooting device... - Step #4
OK 0.09s
Rooting device... - Step #5
OK 0.03s
Rooting device... - Step #6
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x000163b4
[+] Using device /devices/platform/msm_sdcc.1/mmc_host
[*] vold: 0000 GOT start: 0x000163b4 GOT end: 0x000163f4
OK 30.97s
Rooting device... - Step #7
OK 27.41s
Remounting /system with read-write access...
mount: Operation not permitted
FAILED
Does anyone know how to get around this? I need to change the Location to Read-Write.. no clue how to though.
Click to expand...
Click to collapse
The creater did not fix this bug.

aaronmy said:
There might be one way but I don't know how to boot into our recovery menu.
Click to expand...
Click to collapse
To get into Recovery Mode:
1) Turn phone off.
2) Press and hold Back, Volume Down, and Power keys.
3) Continue holding all three keys until device powers on and recovery menu appears.
Navigate using volume up/down keys, and Home key for enter.
Took me a few minutes to figure out how to do it myself last night.
UPDATE: Tested the method you linked to, does NOT work.

elexion said:
To get into Recovery Mode:
1) Turn phone off.
2) Press and hold Back, Volume Down, and Power keys.
3) Continue holding all three keys until device powers on and recovery menu appears.
Navigate using volume up/down keys, and Home key for enter.
Took me a few minutes to figure out how to do it myself last night.
Click to expand...
Click to collapse
Thanks worked like a charm
But the update did not.

Samsung Admire
First off the noob video was/is funny as H+!*. I'm stuck in the same boat with rooting my Samsung Admire. Metro PCS is my carrier. I'd like any updates on rooting ASAP, thanks.

Something caught my eye but I don't understand. Can someone help.
http://forum.xda-developers.com/showthread.php?t=788108:confused:

aaronmy said:
Something caught my eye but I don't understand. Can someone help.
http://forum.xda-developers.com/showthread.php?t=788108:confused:
Click to expand...
Click to collapse
I don't think there are kernals compatible with the samsung admire's kernal. There might be, but I'd rather not risk bricking my phone.

I have a feeling that we won't get root for a while, unless someone can find a developer somehow, seeing that all of these new 2.3.4 devices just getting root access.

[Q] Hasoon2000's HTC Vivid All-In-One Kit

I used the tool on my HTC Vivid running 4.0.3 ICS
Unlocked bootloader - easy
Flash arecovery - easy
More Flash Recovery documentation is needed. Without documentation, how do you know which recovery to install. The tool lists the following: 1) CWM 5.5.0.4 (GB) 2) WCXs CWM(GB / ICS). Does GB stand for Ginger Bread and ICS for Ice Cream Sandwich?
Also, to root the phone, do you need to install a Kernel? If so, some documentation on the various kernels available would be very helpful.
Also when performing perm root, instructions say press a button to complete the process. What button? Phone power/volume or Enter on DOS prompt. I've tried this n times x n ways without success.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

"Android is installing" on EVERY reboot
Could it be that after "Perm Root" is run the phone reboots. During bootup the phone always goes into an Android is installing loop. Maybe the endless update loop always overwrites the root that was just applied.

"Android is installing" on EVERY reboot
Going to "Settings/Storage" and performing a "Factory Data reset" did not take care of the "Android is Installing" that occurs every time the phone restarts.
After bootup the phone works ok; however, if I restart the phone the "Android is Installing" will repeat.
What's the solution?

Still trying to fix "Android is Upgrading" issue
A forum entry suggested setting fastboot mode to fix the "Android is Upgrading" issue.
Goto -> settings/Power/Fastboot checked
Performed restart
"Android is Upgrading" loop occurred again
This above did not work

Still trying to fix "Android is Upgrading" issue
A forum suggested wiping the davlic cache to fix the "Android is Upgrading" loop.
From All-In-One Kit, applied perm root
# FYI: this leaves phone in recovery screen
wipe davlic cache from Recovery menu
reboot
same "Android is Upgrading" loop occurred again
Above did not work

HTC White Screen after Flash Stock Kernel
I flashed the Stock Kernal using the "Hasoon2000's HTC Vivid All-In-One Kit"
NOTE:
> The Kernel Flash failed on "adb remount" - output shown below.
> Other command seemed successful.
After flashing reboot, the phone stays on HTC white screen forever.
I need help to Unbrick this phone.
Note: If I pull out/in the battery, I can successfully perform the following:
> adb reboot-bootloader
> or adb reboot recovery
#####################
# Flash Stock Output
#####################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Unknown error: 0
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb push Kernels/ModulesStock/system /system
push: Kernels/ModulesStock/system/lib/modules/spidev.ko -> /system/lib/modules/spidev.ko
push: Kernels/ModulesStock/system/lib/modules/lcd.ko -> /system/lib/modules/lcd.ko
push: Kernels/ModulesStock/system/lib/modules/cpaccess.ko -> /system/lib/modules/cpaccess.ko
push: Kernels/ModulesStock/system/lib/modules/bcm4330.ko -> /system/lib/modules/bcm4330.ko
4 files pushed. 0 files skipped.
2001 KB/s (608638 bytes in 0.297s)
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>adb reboot bootloader
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>fastboot flash boot Kernels/Kernel-HereStock/boot.img
< waiting for device >
sending 'boot' (2838 KB)... OKAY [ 0.735s]
writing 'boot'... OKAY [ 1.088s]
finished. total time: 1.823s
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>fastboot reboot
rebooting...
finished. total time: 1.937s
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

More on my HTC Vivid Behavior
Please see the following. Any help fixing my phone will be highly appreciated.
#################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb reboot-bootloader
Phone screen shows:
*** UNLOCKED ***
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0025
MICROP-0360
Mar 1 2012,17:09:49
...
*** The above worked
Selected power down
################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb reboot recovery
Phone screen shows:
Android system recovery
- Reboot system now
- USB-MS toggle
- Backup/Restore
...
- Developer menu
- Power off
------------------------
...
RA Revamped
Build: Made for WCX ILLUMINATI SERIES BY GINM
#################################################
From Recovery wipe / all
reboot
same, get's stuck at HTC White screen
Have to pull battery out and start again
################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb get-serialno
HT1ASVJ27111
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb get-state
unknown
################################################
C:\Android\HTC_VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb shell
~ # ?[6nls
ls
/sbin/sh: ls: not found
~ # ?[6nls -la
ls -la
/sbin/sh: ls: not found
~ # ?[6ncd /
cd /
~ # ?[6nls
ls
/sbin/sh: ls: not found
~ # ?[6n

Was S-On the reason for the flash failure?
Did the Flash Kernel to Stock fail because my phone was S-On?
It seems Hasoon2000's HTC Vivid All-In-One Kit is not noob proof.

Almost Solved - Restored HTC Vivid to Stock
I restored my HTC Vivid to Stock using the PROCEDURE below
PROCEDURE:
1) Perform PROCEDURE: Put phone in bootloader
2) Perform PROCEDURE: Relock bootloader
3) Perform PROCEDURE: Obtain Flash Media (PH39IMG.zip)
4) Perform PROCEDURE: Flash back to Stock
5) Your phone should now be restored to stock
Discovered all is not well:
The Radio on the restored phone is not working.
PROCEDURES ARE SHOWN BELOW:
##################
# PROCEDURE: Put phone in bootloader
##################
power off phone (remove/insert battery)
connect phone to computer via usb
Open command prompt
C:\Android\VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
##################
# PROCEDURE: Relock bootloader
# NOTE: I Ignored the FAILED meesge
# WHY? Put phone back in bootloader, the screen says "relocked"
##################
C:\Android\VIVID\Vivid_All-In-One_Kit_v2.1\Vivid_All-In-One_Kit_v2.0\Data>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.027s
##################
# PROCEDURE: Obtain Flash Media (PH39IMG.zip)
##################
Download PH39IMG.zip file - this includes recovery, system, everything stock
Verify the file is good by Using WinMd5Sum utility
Good MD5 = ab2ad5f3eebbbbb246da204b4d78d418
save the file at the root of your sd card
power off phone (i.e. remove battery)
put the microSD card back into your phone
##################
# PROCEDURE: Flash back to Stock
##################
Perform PROCEDURE: Put phone in bootloader
FROM the phone's bootloader:
- boot to bootloader to initiate the update
- It should automatically find the zip file in the microSD and flash the stock image
*** What I remember about the upgrade - may not be exact ***
When the upgrade starts the phone says some stuff about the image
THE upgrade installs 3 or 4 items
reboots to continue the upgrade
continues installing a list of items, you should see all ok's for each
After upgrade completed, the screen displayed a Green battery
I pressed power button and the phone rebooted correctly
*** Yahoo my phone is fixed!!! I am back to stock. ***
##################
# Lesson Learned
##################
Be very careful. Read, read, and read some more. Learn to be patient.
Don't trust anything blindly do your home work.
##################
# Credits
##################
Obtained the raw procedure from the following post:
http://forum.xda-developers.com/showpost.php?p=20807914&postcount=2
##################
# Future s-off reading
##################
Without s-off you cannot flash other kernels
S-off seems to be required for perm root
ControlBear (the wire trick) for s-off: http://unlimited.io/
Revolutionary s-off (not supported on htc vivid as of 5/23):
http://unrevoked.com/rootwiki/doku.php/public/revolutionary

Factory Data Rest killed the phone
From the phones settings menu, I performed a factory reset. I did this because of the radio issue.
The phone is now 100% dead. Does not do anything. I don't think this is a happy ending. I tried.

[Q] root 2.77.651.8

Anyone successfully downgrade and unroot 2.77.651.8?
I flashed UU_Speedy_S_Sprint_WWE_2.77.651.8_Radio_1.08.01.0111_NV_SPCS_2.97_01206_PRL60674_release_275849_signed.exe
I followed indirect’s method. That did not work. Followed his method without the script.
Then I tried JohnnyCakeXM’s method with indirect’s.
Best I get is either caught into a bootloop or it just say’s permission denied
Here is a log of my output in command prompt typing each item one at a time
the only reason why i used shifty son of a. is because it had all the tools needed in one download.
i manually typed everything in.
C:\ShiftySonOfA>adb push tacoroot.sh /data/local/tmp/taco
adb server is out of date. killing...
* daemon started successfully *
207 KB/s (2129 bytes in 0.010s)
C:\ShiftySonOfA>adb shell chmod 755 /data/local/tmp/taco
C:\ShiftySonOfA>adb shell sh /data/local/tmp/taco --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
reboot: Operation not permitted
*REBOOTED INTO RECOVERY WITH HTC Quick Root v1.1.13. press Volume+, Volume- and Power at the same time and rebooted the system. once phone was back up and running i did the following.
C:\ShiftySonOfA>adb shell sh /data/local/tmp/taco --root
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
/data/local/tmp/taco: cannot create /data/local.prop: permission denied
reboot: Operation not permitted
C:\ShiftySonOfA>adb shell dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
adb server is out of date. killing...
* daemon started successfully *
/dev/block/mmcblk0p17: cannot open for write: Permission denied
one with any ideas on this? or suggestions?
kind of sick of the stock rom. i want to try something new already.

rchris494 said:
Anyone successfully downgrade and unroot 2.77.651.8?
I flashed UU_Speedy_S_Sprint_WWE_2.77.651.8_Radio_1.08.01.0111_NV_SPCS_2.97_01206_PRL60674_release_275849_signed.exe
I followed indirect’s method. That did not work. Followed his method without the script.
Then I tried JohnnyCakeXM’s method with indirect’s.
Best I get is either caught into a bootloop or it just say’s permission denied
Here is a log of my output in command prompt typing each item one at a time
the only reason why i used shifty son of a. is because it had all the tools needed in one download.
i manually typed everything in.
C:\ShiftySonOfA>adb push tacoroot.sh /data/local/tmp/taco
adb server is out of date. killing...
* daemon started successfully *
207 KB/s (2129 bytes in 0.010s)
C:\ShiftySonOfA>adb shell chmod 755 /data/local/tmp/taco
C:\ShiftySonOfA>adb shell sh /data/local/tmp/taco --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
reboot: Operation not permitted
*REBOOTED INTO RECOVERY WITH HTC Quick Root v1.1.13. press Volume+, Volume- and Power at the same time and rebooted the system. once phone was back up and running i did the following.
C:\ShiftySonOfA>adb shell sh /data/local/tmp/taco --root
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
/data/local/tmp/taco: cannot create /data/local.prop: permission denied
reboot: Operation not permitted
C:\ShiftySonOfA>adb shell dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
adb server is out of date. killing...
* daemon started successfully *
/dev/block/mmcblk0p17: cannot open for write: Permission denied
one with any ideas on this? or suggestions?
kind of sick of the stock rom. i want to try something new already.
Click to expand...
Click to collapse
Check the last post in JohnnyCakeXM's thread, I posted a fix for the problem you're having
Alternatively, I am putting together a 2.2 to 2.3.4 OTA rooting utility, if you just want to wait a couple days that will be available soon.
Sent from my PG06100 using Tapatalk 2

CNexus said:
Check the last post in JohnnyCakeXM's thread, I posted a fix for the problem you're having
Alternatively, I am putting together a 2.2 to 2.3.4 OTA rooting utility, if you just want to wait a couple days that will be available soon.
Sent from my PG06100 using Tapatalk 2
Click to expand...
Click to collapse
i tired that, for some reason it still seems to do the same thing. i will just wait for the rooting utility. i am in no real rush.

rchris494 said:
i tired that for some reason it still seems to do the same thing. i will just wait for the rooting utility. i am in no real rush.
Click to expand...
Click to collapse
Hmm, that's weird, it worked perfectly for me. Try running the 2.77.651.8 RUU and then using the method in JohnnyCakeXM's thread, the thing is that I was going to be using that same fix I posted in the 2.77.651.8 thread in my utility...but hmm, that's weird, just tell me what happens after you run the RUU and try again (PM me with your results please)
EDIT: Did you make sure you had fastboot disabled? Thats the only other thing I can think of off the top of my head that could have messed it up
Sent from my speed-y