[q] Samsung Admire rooting - General Questions and Answers

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.

Related

[App] [26.04.2011][v1.2] GingerBreak APK (root for GingerBread)

NOTICE: Gingerbreak is an exploit that has been fixed in many of the latest Android versions and releases. If it does not work, it does not work. I can't "fix" the exploit, you will have to wait for a new exploit to come out, or root a different way!
About
The GingerBreak APK is a wrapper around the newly released GingerBreak exploit (credits to The Android Exploid Crew), which is meant to attain root access on GingerBread. This specific exploit may work on various Froyo and Honeycomb versions as well.
What the APK and exploit do is as follows:
- The APK puts the right files in the right place to run the exploit
- The APK runs the exploit
- The exploit attempts to attain root access
- If it succeeds, the exploit remounts /system as read-write and runs the installer script
- The installer script attempts to install the su binary and superuser APK, and reboots
Some important things to know:
- You must have USB debugging enabled on your device
- You need to have an SD card (formatted and) inserted - if it doesn't work, try formatting the SD card in your computer, or switching it with a different (or old, etc) SD card
- The APK must be installed to device, NOT SD card
- The exploit may take a while to run, but not more than 10 minutes, if it does, get me a logcat, and reboot the device. In rare occasions, even if the device does not reboot, you may still have root. So check that out after you manually pull battery after 15 minutes or so of being stuck.
- Always reboot between root attempts!
- While (temporary?) root access may be attained, due to locked bootloaders, efuses, S-ON, and whatnot this may still not work on your device. For temproot purposes, use the raw binary exploit (linked below), not this APK.
- The GingerBreak exploit should not be used to attain temproot and continue using the device. It fscks vold, you do not want to be running like that. You want to reboot! So if the root doesn't stick, you (still) have a problem.
Installation
- Optional: Press the Thanks button below this post
- Make sure USB debugging is enabled
- Make sure you have an SD card (formatted and) inserted
- Get the APK on the phone somehow, and install it
- Open the APK, press the root button
- Wait a few minutes. If there are no problems, the device will reboot (note that the reboot itself can take like 10 minutes due to cache wipe)
- Make sure the Superuser app is install and working
- Optional: Install BusyBox from Market (I personally prefer the stericsson installer)
- Optional: Uninstall GingerBreak, you don't need it on your phone anymore
- Optional: Make a donation
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) - often this works (a fix for both issues is being looked at)
NO IT DOES NOT WORK ON THE GALAXY ACE (yet ?)
WORKS ON A RARE SGS2, BUT NOT ON MOST (seems to be only pre-release devices that are rootable this way)
ACER A500 / ICONIA Look here (click). Will eventually be integrated, I guess
Donate
Donate to Chainfire by PayPal: click this link
Donate to The Android Exploid Crew by PayPal: [email protected]
Report!
Please report back if it does or doesn't work on specific devices. If it doesn't, don't forget to post your logcat as attachment, and mention your device details and GingerBreak version.
Credits
- I made the APK and did some slight modding to the exploit code to install from an APK
- The exploit ("GingerBreak") itself is made by The Android Exploid Crew. Original code can be found here: http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
Manual rooting
From v1.1 it is no longer possible to manually root the device over an ADB connection using the files from this APK. Please use the original binaries from the c-skills website to do this. There are several guides posted here on XDA about how to do this manually, some are mentioned/linked-to in the first few pages of this thread.
Note
GingerBreak is not specific to any device, but there is code in there that may not work on device X or Y. The exploit is generic, but that does not mean one size fits all, nor does it mean that there will be no firmwares out there that fix this exploit. A special version may need to be compiled for your device, ask your favorite hacker from your specific device's forum. This APK is meant to make the process easier, but also adds dependancies so that it may not work on your device.
AGAIN, THIS DOES NOT WORK ON S-ON DEVICES !
Changelog
26.04.2011: v1.2
- Removed some code that may break operation while the code itself isn't needed
- Added UnRoot option
- The APK now logs exploit output semi-live
22.04.2011: v1.1
- Modded exploit code to not need /data/local/tmp - this should fix the problem extracting assets as well as be more compatible with various devices (in theory). In case the APK notices that this cannot work, it will warn you about this.
- Added some warnings and errors to the APK
21.04.2011: v1.0
- First release of APK
- Slight mods to the exploit source to have it work better from APK
Sources
Attached archive contains the modified sources for the exploit part of this APK. I will publish new versions only when it changes; the APK may be updated to a newer version, this does not necessarily mean the exploit has changed
Also, apologies for the few days delay in posting the source.
Genius tool!
Congrats to C-Skills to for the exploit of course.
PS: if you want it to work on Galaxy S II: extract in /app-cache instead of /data/local/tmp
Finally this has come out
Sent from my a Vibrant using the xda premium app
Will this work on any phone
Sent from my a Vibrant using the xda premium app
supercurio said:
Genius tool!
PS: if you want it to work on Galaxy S II: extract in /app-cache instead of /data/local/tmp
Click to expand...
Click to collapse
Will be looked at! (I'm sure it'll need more modifications for other devices as well, hehe)
I get an error saying 'could not extract assets'. Is there a solution for this?
Running 2.3.3.
Sent from my GT-I9000 using XDA App
I am trying to root using adb.
Can anybody tell how long will it sleep/wait after displaying
[*] vold: 1965 GOT start: 0x00014344 GOT end: 0x00014384
to complete the root
(@robin2)
try:
adb shell mkdir /data/local/tmp
will it work on Nexus S? Anyone tried yet?
please see the steps below
E:\Downloads\New folder\SuperOneClickv1\SuperOneClickv1>adb push gingerbreak /da
ta/local/tmp
586 KB/s (16830 bytes in 0.028s)
E:\Downloads\New folder\SuperOneClickv1\SuperOneClickv1>adb shell chmod 777 /dat
a/local/tmp/gingerbreak
E:\Downloads\New folder\SuperOneClickv1\SuperOneClickv1>adb shell /data/local/tm
p/gingerbreak
[**] 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 system: 0x6fd17f09 strcmp: 0x6fd37c89
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014344
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 1965 GOT start: 0x00014344 GOT end: 0x00014384
That's not my modded version, so don't ask me.
why would you need on a nexus s ??
it is one of the most simple phone to root and get superuser ...
there are many guides in the development section for the nexus s look there
i would much prefer to use one of those as i know it will work !!
I cannot create/remove any directories/files in /data/local/ because I don't have root access.
I've tried...
Sent from my GT-I9000 using XDA App
For those that want to root manually, you can follow this: http://forum.xda-developers.com/showthread.php?t=1044582
It's for a Nexus One (tested), so if you want to use the step-by-step for a different device, you will have to change the partitions in the mounting commands.
Hi! I have Nexus One and is currently on an unrooted 2.3.3
I placed the APK file on my SD card and when I tried to launch it, all I got was "could not extract assets" what should I do?
curiousitykilledthepat said:
Hi! I have Nexus One and is currently on an unrooted 2.3.3
I placed the APK file on my SD card and when I tried to launch it, all I got was "could not extract assets" what should I do?
Click to expand...
Click to collapse
For people getting "could not extract assets" error execute
adb shell rmdir /data/local/tmp
and then
adb shell mkdir /data/local/tmp
The above post worked for me. Thanks.
Been thinking a bit about how things are done in the v1.0, going to do some massive changes for the next release that should make it much more compatible.
:/
it doesn't root the Desire S, unfortunately

[Q] HTC Desire HD - Can't Downgrade from Gingerbread to 1.32.405.6

Hi,
I was following the article :
[GUIDE] How to downgrade 1.7x/1.8x/2.x to 1.32.405.6
@ http://forum.xda-developers.com/showthread.php?t=905003
.
The cursor blinks after this line:
Code:
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
I have waited for almost an hour, but nothing happens, and I have to break using Ctrl+C.
My questions is, what am I doing wrong/ what needs to be done? Cause I see other posts where the output shows many more lines similar to the one above, and then the # (root) prompt, but I don't get it.
-- Phone: HTC Desire HD [Unlocked]
-- OS: Just received OTA Gingerbread: 2.3.3; s/w version: 2.37.720.3
-- Factory Reset Done
-- PC Connection is in : Charging mode and USB Debugging
Complete output:
Code:
G:\htc desire hd\Mod\Setups\Downgrade>adb push misc_version /data/local/tmp
1104 KB/s (15837 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb push GingerBreak /data/local/tmp
1173 KB/s (16830 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
G:\htc desire hd\Mod\Setups\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] 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: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
Thanks in advance,
Gautam
Downgrade Failed
I got the same result.. Needed help.. :sad:
Same here. Any help would be appreciated
Ok guys even I am stuck here too and I had posted about this, but no one replied, however I got down to googling tactics and the most statisfying reason that I have come up with (reasoning is based on the countless articles and websites about gingerbread and gingerbreak) is that the gingerbreak crack is for a different version of of gingerbread, a version which was launched before we Indians, got out version of gingerbread and thats why our DHDs are getting stuck at the same place over and over again. It's all because of different s/w version numbers.
I guess we all have to wait for a gingerbreak version that is applicable across all DHD ROMs, only then can we be able to downgrade. There might be other way(s), but I know none. This is my two bit about what all of us, are going through when following the downgrade guide. I may be wrong, I may not be. If you have a different thing to say about it, then by all means let all of us hear it.
Thanks Ruben for the clarification. I think you're right. The following two links suggest that as well.
Check out (Google them as I can't paste links due to the less # of posts that I have):
Google Patches GingerBreak Exploit, But Don’t Worry – We Still Have Root (For Now)
Change Iab98d71c: Detect Android devices vulnerable to CVE-2011-1823
I was trying to downgrade so that I could install Android Revolution HD 5.1.7 on my DHD. Any other way to achieve the same? I wish I knew this; just updated to Ginger a few days ago.
The pleasure was all mine Gautam, just trying to do my part to help other Indian DHD users. anyways check out this page http://forum.xda-developers.com/showthread.php?t=905003&page=149 and I believe jkoljo is already on the job.
Unfortunately there is no other way to downgrade the gingerbread 2.37 hoping for an exploit from, The Android Exploid Crew and jkoljo.
is it cuz we are indians?
Same exact problem. Spent more than 24hrs finding a solution. Really bored of the stock ROM and the gingerbread update does not even have enough visual changes. Zzz really wish someone does something about it
Once again Indians have a disadvantage.
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)
ericjennings said:
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)
Click to expand...
Click to collapse
1st you will need the following files
GingerBreak from http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
misc_version from http://www.multiupload.com/A9PNGVBWBE
Default rom http://forum.xda-developers.com/showthread.php?t=905003
and Android SDK http://developer.android.com/sdk/index.html
Also you will need a clean SD card 1 gig or more should be fine (smaller is better)
Unzip GingerBreak and misc_version into a folder say c:\Downgrade (I normally use 7Zip)
You should have:
c:\Downgrade\GingerBreak with 5 Files
c:\Downgrade\misc_version with 4 Files
Make sure you installed Android SDK's Platform tools and updated your path to reflect this
IE: run SDK Manager and install Android SDK Tools and Google USB Driver pack if you don t have HTC Sync driver running.
Format the SD card and copy the rom.zip into the base of the card, not a sub directory. (Do not unzip)
Now: Plug in the phone to the USB and make sure Debugging is on and the phone is set to charge only.
Then open Command prompt ie: run cmd.exe
Go to your Downgrade directory and test if your adb command is in the path. ie: run it and make sure it lists switches and not say file not found
Then run as follow
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
adb shell
./data/local/tmp/GingerBreak
if you fail to get root ie: prompt does not return to # or get a endless sendmsg() failed? Error, reboot the phone and repeat the commands above. The phone I used, took 3 tries to get this right.
at the # run the following
cd /data/local/tmp
./misc_version -s 1.31.405.6
When its done exit cmd and goto your phone, Reboot it while pressing volume down.
It will come up with a menu and follow the update instructions.
You should then be on Android version 2.2 when done.
Please note the rom that is supplied works with unbranded phone only if you have a branded phone you will need to make a goldcard. If you want to know how to make one, google is your friend sorry.
You must have htc sync installed!
**** I TAKE NO RESPONSIBILITY IF THE BELOW PROCESS DOES NOT WORK FOR YOU & IF YOU BRICK YOUR PHONE - DO THIS AT YOUR OWN RISK ****
What you need :
- MicroSD card with SD Adapter
Procedure :
1. You need to setup ADB on your PC and download the Android SDK, guide here:
How To: Set Up ADB/USB Drivers for Android Devices | The Unlockr
2. Create a GoldCard here (remember to open the SD Card as a PHYSICAL DISK) :
How To: Create a Goldcard | The Unlockr
3. Download the Generic Software here :
http://androidfiledepot.com/Storage...ravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe
4. Insert the Goldcard into the Desire and connect it to your PC. Run the software downloaded in step 3.
5. This will flash your Desire with a generic HTC version of the OS.
6. Enjoy!
If you see error 131, you don't have htc sync!
Nilseby, thanks for the suggestion.
I tried your method, and the process starts; phone switches off and HTC in displayed in White. After a few minutes, it says, that it can't go through with this, and the program just hangs. I powered on the phone and it's back to the way it was. Flashing didn't go through. I created a gold card as well and formatted, still no luck.
2.37.720.3
Why, oh why did I upgrade to 2.37.720.3?
I actually wanted to root my DHD so that I could take screenshots of its screen. Now that it is being reporting that as of now 2.37.720.3 is not downgradable, is there any other way to take screenshots of my phone's screen? Other than, of course, taking pics with another camera.
Thank God!
I am using RCMIX HD Kingdom v 1.2 with Sense 3.0 on my DHD and when I saw I downgrade guide from Gingerbread to get root access, I decided to upgrade to the official 2.3.3 in India. I saw the initial posts in that thread say that the method worked really well.
I had almost made up my mind to try the official update knowing that I can downgrade using the guide, but just before doing that I thought I'd read the more recent posts and guess what I realized the Indian software number 2.37.720.3 cannot be downgraded! Which means no root access and no custom ROMs (at least for now). I immediately changed my mind and didn't upgrade.
Thank God!
Good decision av. Just wait till this issue gets sorted out and then dive in. I was too eager to see what was up with Mr.Ginger and curosity killed the cat.
Sent from my Desire HD using XDA App
We in Australia have the same problem regret upgrading.
Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out
guitarist7 said:
Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out
Click to expand...
Click to collapse
yeah..
now i cant do anything with it
I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases
DotNetRules said:
I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases
Click to expand...
Click to collapse
What do you mean by getting a GoldCard to work? Is the phone not mounting it or something?

Rooting Problem

I keep getting this error and idk why plz help
Installing BusyBox (temporary)... - Step #2
OK 0.03s
Rooting device... - Step #1
2079 KB/s (585731 bytes in 0.275s)
OK 0.31s
Rooting device... - Step #2
OK 0.03s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.02s
Rooting device... - Step #5
OK 7.04s
Remounting /system with read-write access...
error: closed
FAILED
Just so you know...the process to root differs with almost every phone. Without having your phone specs it is pretty hard to help you out.
sorry i forgot to put them but i have an lg optimus v with 2.2.2 stock froyo

[Q] Problem rooting motorola milestine with SuperOneClick

Phone: Motorola Milestone
Android version: Froyo 2.2
SuperOneClick version: 2.1
Log:
SuperOneClick v2.1.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
2.2.1
Getting manufacturer...
motorola
OK
Getting model...
Milestone
OK
Getting version...
95431830
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
1422 KB/s (1062992 bytes in 0.730s)
OK
Installing BusyBox (temporary)... - Step #2
OK
Rooting device... - Step #1
cannot stat 'C:\Users\Aaron\Downloads\SuperOneClickv2.1-ShortFuse\Exploits\psneuter': No such file or directory
OK
Rooting device... - Step #2
Unable to chmod /data/local/tmp/psneuter: No such file or directory
OK
Rooting device... - Step #3
OK
Rooting device... - Step #4
./psneuter: not found
FAILED
Too tell you the truth, I do not know what this error means, but I can tell you another rooting method that is meant for froyo operating systems. It is easier than the method you are currently attempting, and should get the job done. OK, go on Google and look up z4root. Make sure it is the newest version and download it. Install it on your phone, you may have to allow non,market apps in the settings menu. Open the app hit permanent root, wait a little while, your phone should reboot and you are officially rooted. If z4root freezes up, it is OK, this app can not brick your device because it is just a security exploit. Pull the battery and try again. I hope this works for ya.
The antivirus on your desktop might have deleted the actual exploit (psneuter). Try to keep your antivirus disabled while repeating all steps (starting from installing the application, since the previous install might have been corrupted by the antivirus).
Or, better, use the vulnerable recovery method.

How to install CWM on TF101? I'm not kidding, I didn't find the answer so far here

Ok,
Before people start complaining I should not post this: I have searched the forum and have not found a solution. Therefore please let me specifically describe my situation and please when responding, be accurate, exact, non-ambiguous, complete, and correct.
I have a Chinese TF101 with build HRI66.CN_epad-8.2.3.13-20110511 (I assume that translates to build 8.2.3.13)
I tried running the ROOT guide located in http://forum.xda-developers.com/showthread.php?p=17285912#post17285912
Unfortunately that does not work on my TF101. I get:
[**] 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: 0086 GOT start: 0x00017368 GOT end: 0x000175e8
Followed by never ending silence and no Root.
Someone told me that this guide does not work on my build standard, and gave me links to windows/linux root guides.
These don't work because I have a Mac. I do not have windows and I do not have linux, I only have Mac, and I know no one with a PC that I can borrow for this exercise, so it has to be done from my Mac and not any other platform.
What I want is:
1) Root my TF101
2) get CWM on there
3) get the latest Prime ROM on there.
Can someone please explain to me what I need to do to get prime 1.8 installed on build 8.2.3.13 of a chinese TF101?
Sorry if I sound direct, but I know very little about this stuff and so far I have found nothing that works. Since I know nearly nothing other than how to follow accurate complete correct unambiguous instructions, I would love it if someone can actually provide me with those.
That method only work for 8.2.3.9 or lower.
8.2.3.13 and up use NVFlash method.
Also since you're on 8.2.3.13 you have the option to downgrade to 8.2.3.9.
After which you can root and install an updated root rom
Ok, so can you please explain to me how to use NVFLASH on a Mac? If it is not posisble, can you explain to me how to downgrade to 8.2.3.9?
I'd be very gratefull!
UPDATE: Just saw your response on the other post. I think this will help me a lot! Thanks!
I also had cn firmware, using nvflash is very easy, I use windows and follow the tutorial from YouTube ..

Categories

Resources