Related
Here new RUU for Hero
http://shipped-roms.com/shipped/Her...8.55.06P_6.35.15.14_release_142740_signed.exe
Enjoy!
What language it is for Fr stands for French !!!!
Is this specific to Orange GSM Hero?
stuck up
Using goldcard I installed this RUU on Hero
Should say sorry to myself as this RUU updated the bootloader and I am stuck up and not able to root it again or load any other RUU even though I am using the goldcard.
If I donot use goldcard it gives error of customerID and if I use goldcard it gives bootloader error (error 140)
So not able to install custom recovery or this is not accepting the super user or terminal emulator.
It seems that it has altered the bootloader or partions.
If I run this RUU again it installs fine.
So if anybody has intentions of rooting the device again, I advice that one should not run this RUU and update the device.
Can anybody help me out to bring it back to bootloader and instal the custom recovery.
Or should I say I am stuck up ?
@anant
Try this: http://www.villainrom.co.uk/forum/s...o-Root-The-2.1-RUU-or-OTA-Update-For-The-Hero
can anyone pull the radio or at 15.14 is it the same as previous?
incomer said:
@anant
Try this: http://www.villainrom.co.uk/forum/s...o-Root-The-2.1-RUU-or-OTA-Update-For-The-Hero
Click to expand...
Click to collapse
Yes tried this. No help
You can consider my experience as moderate but not expert.
Tried all the known methods to root this but no help.
It is not giving write permission when in adb shell command. Permission denied is answer.
in terminal emulator not giving the su (super User) permission.
I think I am stuck up.
Can any body help ??????????
Will be grateful.
Have you tried to root it using the newbie guide to rooting found in the development forum? I can't link yet, but it shouldn't be hard to find.
I installed an OTA update on the Hero a couple of weeks back, might have been the same update as this one, and I couldn't use VR's batch script to root after that. But I was able to use Universal AndRoot with no problems.
Slugbug said:
Have you tried to root it using the newbie guide to rooting found in the development forum? I can't link yet, but it shouldn't be hard to find.
I installed an OTA update on the Hero a couple of weeks back, might have been the same update as this one, and I couldn't use VR's batch script to root after that. But I was able to use Universal AndRoot with no problems.
Click to expand...
Click to collapse
Thanks for your reply.
Tried this guide for sure before also.
But without success. Actually the universal androot installs and gives su access successfully.
But using Terminal emulator and flashing image to flash.img it gives me error in read error ( out of memory ) which I fail to understand how to correct.
I have used this guide before also where it worked flawlessly. But in this ROM I suppose to root it again we need to take something extra.
Can anybody help???????????
You can try to download and install a task killer from the market and kill running applications. Should free up enough memory for the recovery image to be flashed.
After doing with the PERM ROOT, i did reboot my G2 with volume down+power, "s-off" shows on the screen, but something just happened.
after rebooting, i just uninstall VISIONary, then i rebooted my G2 again, to make sure, i did volume down+power again. Good, s-off is still there. When i came into the home screen, i pressed the Root Explorer, oooooops, i got no root access to open this software....
To check this, i re-install VISIONary, --root now---"your device is already rooted".
All in all, i have the "s-off", but i have no root access.
Help!!!
A big thanks here and looking for some one would like to answer me.
Install Superuser (from ChainDD) and make sure it allows access for your root explorer. Also, try the steps again to get S-Off. After you do the 'sync' command, do a reboot back to your home screen (not bootloader) to see if the changes stick.
And don't start a new thread. Post in the old one.
Make sure Visionary is not set to "Root on Boot".
Reboot the phone and run Visionary again.
Make sure you have the newest version of visionary. Run it to root, open terminal emulator type in "SU" then type "sync" wait two minutes. reboot the phone.
You don't need visionary after you get pern root. I don't have it anymore. If you followed the guide then you should be golden.
Sent from my T-Mobile G2 using XDA App
superuser is useful, but when i redid this step"# /data/local/tmp/root",it was told that # /data/local/tmp/root not found. after sync, i still can not obtain the root access...
fox_lee said:
superuser is useful, but when i redid this step"# /data/local/tmp/root",it was told that # /data/local/tmp/root not found. after sync, i still can not obtain the root access...
Click to expand...
Click to collapse
Did you just try running su?
-RotorDemon- said:
Make sure you have the newest version of visionary. Run it to root, open terminal emulator type in "SU" then type "sync" wait two minutes. reboot the phone.
Click to expand...
Click to collapse
This is what did it for me, I had S-OFF and no SU/Root last night.. took 3 seconds..
Yes, if i uninstall superuser, "su" won't pass the premit. If i keep superuser in my G2, "su" will pass but i need confirm it with superuser...
I have this problem and I deleted visionary because I thought I didn't need it and when trying to get it back its not in the market so I can't try using it again to get the perm root eventhough I have soff
Sent from my T-Mobile G2 using XDA App
-RotorDemon- said:
Make sure you have the newest version of visionary. Run it to root, open terminal emulator type in "SU" then type "sync" wait two minutes. reboot the phone.
Click to expand...
Click to collapse
latest version? u mean R12 or R11?
v6tc said:
This is what did it for me, I had S-OFF and no SU/Root last night.. took 3 seconds..
Click to expand...
Click to collapse
What version of VISIONary did u use? r11 or r12(tested), and did u just work it out?
kicknik said:
I have this problem and I deleted visionary because I thought I didn't need it and when trying to get it back its not in the market so I can't try using it again to get the perm root eventhough I have soff
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Then you'll need to visit the VISIONary thread and download it from there. It was suspended from the Android Market.
Try to do the stock PC10.img to start all over and just go thru the steps.
Sent from my T-Mobile G2 using XDA App
Well I had the r12 version. Tried the temproot (checked for su and it was there.) and then permroot (the phone forced a reset) when it came back on, there was no root. So I decided to go manually. Followed all instructions here http://forum.xda-developers.com/showthread.php?t=833965. Did Everything exactly besides step 6. Well I did it but it said that I already had root. So i proceeded with step 7 and waited five minutes (just to be sure) and then restarted. Checked and confirmed that s-off. Powered on the phone and still no root access. I figured that step 6 may have thrown me off so i tried step 6 and 7 again to no avail. Stuck with s-off but no root.
I had perma-root yesterday. Working and tested... mui happy.
Got OTA update late last night (Southeast US / Tampabay FL). Accepted it like a dumbass.
Currently:
Phone works... I didn't get "teh brix".
VISIONARY tells me "your device is already rooted"
SuperUser has my Root-apps listed with green radio buttons.
su from terminal results in permission denied
screenshot will no-longer run (This program requires root access)
Recovery Boot = S-OFF
Confused = Yes, very
Can't re-root as visionary won't really run properly. Uninstalled Visionary and installed Visionary+. Still says "Your device is already rooted".
S-off no boot fix?
So to reply to my own thread once I've gone through all of the steps repeatedly, I wound up with s-off and no root. even after running visionary+ temp root and then entering (in terminal emulator on the phone) su (granted superuser) and then typing sync and then reboot. Did this over and over again with the same result but to get it to work(for me anyways) i had to run temproot, and then run permroot and then reboot. Mind you, I have already done this step before but it didnt seem to work until afterwards. Hopes that this helps SOMEONE.
For people facing a similar issue, use the RATC method instead of VISIONary, you should get perm root then.
I had the same issue I followed unforgiven's instructions
forum.xda-developers.com/showthread.php?t=833965
after step 7 and you reboot run visionary again and you should gain perm root, hope this helps.
Sent from my T-Mobile G2 using XDA App
Sorry, what is the RATC method of rooting?
Okayy, so
i want to get started with all the " Rooting " and installing those awesome " Custom Roms " But of course i have a couple of questions. Since its the first time i am experimenting with android devices. I jailbreaked my iPhone but i already found out that its not quite the same as rooting and installing custom roms.
Now about the questions.
I am a poor scholar with no money and can't afford it to lose my cellphone So. what is the chance of bricking my desire hd meanwhile the rooting process ? i already googled a few times but can't seem to find anyone who bricked it am i right ?
And is there somewhere a list where all the terms will be explained ?
like S-OFF Hboot the diffrence between Clockworkmod and Cynogenmod and all of that ?
Many Many Thanks ! ( And i would thank you even more if you hit that reply button :'D )
Sent from my Desire HD using XDA App
Nobody has bricked a Desire HD yet while rooting or S-OFFing it, so it is relatively safe. The process itself is considered dangerous, but for example my S-OFF tools check so much things before continuing, that there should not be a problem.
Check the android dev subforum, there is a sticky roll up thread that contains useful links. Read the introductory guide first, it explains a lot of things.
ClockworkMod: a custom "application" in your phone, that can flash (write) any ROM (custom software including operating system). It does not depend on the OS, so it is useful for even the most hopeless situations where your system does not boot for whatever reason.
CyanogenMod on the other hand is simply a ROM, based on years of hard work. It does not contain HTC Sense.
Sent from my Desire HD using Tapatalk
I think it is only really possible to brick your phone when doing the ENG S-OFF.
Read carefully, do the right steps and you have 5% risk to all of it i guess
Can u plz tel me the rooting what steps have to do after rooting and how can I install froyo for my x10mini....thanx
Sent from my E10i
Check Android Development... cant be very different from it
Good Luck
Okay i wanted to get started, found this tutorial on the interwebz
http://hemorrdroids.net/how-to-root-s-off-and-install-custom-roms-on-the-desire-hd/
thought this was exactly what i wanted to do but now i'm already stuck when i want to downgrade it ?
The first time when i did the last adb shell it gave me the "#" wich should mean it is not right, i am pretty sure i dont have a temp root because i haven't done anything to my phone until today.
So i tried the steps again but when i hit enter while entering this command:
adb shell /data/local/tmp/psneuter
i get the following error : mmap<> failed. Operation not permitted
I won't continue if i get an error so.. any help OR another tutorial wich gives me exactly what i want ?
A reboot of the device seems to work thanks anyways.
Downgraded my device succesfully.
Wickedd said:
Okay i wanted to get started, found this tutorial on the interwebz
http://hemorrdroids.net/how-to-root-s-off-and-install-custom-roms-on-the-desire-hd/
thought this was exactly what i wanted to do but now i'm already stuck when i want to downgrade it ?
The first time when i did the last adb shell it gave me the "#" wich should mean it is not right, i am pretty sure i dont have a temp root because i haven't done anything to my phone until today.
So i tried the steps again but when i hit enter while entering this command:
adb shell /data/local/tmp/psneuter
i get the following error : mmap<> failed. Operation not permitted
I won't continue if i get an error so.. any help OR another tutorial wich gives me exactly what i want ?
A reboot of the device seems to work thanks anyways.
Downgraded my device succesfully.
Click to expand...
Click to collapse
I rooted my phone for the first time two days ago and I got the same error as you did. I tried just of curiousity to change this command:
"adb shell /data/local/tmp/psneuter"
To this:
"adb shell chmod 777 /data/local/tmp/psneuter"
And it solved my problem, let me know if it helped.
Hello,
First I want to say how much this forum has helped me in the past with my DroidX and Bionic.
I upgraded to an HTC One last month and using instructions here, ran rumrunner on it to unlock and S-off. After successfully rumming it, I had root and all was good. I hadn't bothered to install twrp or Cyanogen because I wasn't planning on flashing any roms anytime soon.
About a week later, the phone wanted to do an OTA update. I did it without checking to see if it would break anything. After the update, I no longer had root. Superuser was saying the binaries were not there and it couldn't install them.
I tried running rumrunner again, downloading the correct package for the newer software version. It seemed to work ok in the command prompt but I still didn't have root access.
Today, I tried pushing Twrp. The command prompt appears to have completed correctly but when I try to boot to recovery, it shows the HTC screen with the red dev text for about a minute, then it just restarts and boots normally.
I appreciate any help.
~Mike
michaelsteinbach said:
Hello,
First I want to say how much this forum has helped me in the past with my DroidX and Bionic.
I upgraded to an HTC One last month and using instructions here, ran rumrunner on it to unlock and S-off. After successfully rumming it, I had root and all was good. I hadn't bothered to install twrp or Cyanogen because I wasn't planning on flashing any roms anytime soon.
About a week later, the phone wanted to do an OTA update. I did it without checking to see if it would break anything. After the update, I no longer had root. Superuser was saying the binaries were not there and it couldn't install them.
I tried running rumrunner again, downloading the correct package for the newer software version. It seemed to work ok in the command prompt but I still didn't have root access.
Today, I tried pushing Twrp. The command prompt appears to have completed correctly but when I try to boot to recovery, it shows the HTC screen with the red dev text for about a minute, then it just restarts and boots normally.
I appreciate any help.
~Mike
Click to expand...
Click to collapse
Make sure you have the vzw htc one twrp
Yeah I would make sure you're using the vzw twrp, i did the exact same thing that you did and just simply pushing twrp recovery and flashing superuser.zip in recovery regained root access for me. I didn't have to run rumrunner twice.
The TWRP site lists phone models:
TWRP for HTC One [m7]
TWRP for HTC One (Sprint USA) [m7wls]
I downloaded the m7 variety. My One is on Verizon. There are other "One"s listed but they are Max, S, SV, V, VX, X, and X+.
edit: Ok, I got it. I did a search and found an xda post by Flyhalf205 with the correct file.
Thanks guys.
~Mike
Hey all,
I just wanted to pose a few questions. I've spent about 20 hours going through forums and articles to root my Verizon HTC One, and a heck of a lot of the information out there is very dated, and often contradictory. I've tried condensing it into a single procedure, but am having problems.
Here's the procedure for a brand new phone straight from a verizon store yesterday, running Android 4.3, with hboot 2.55, as I understand it; the information that I believe is now out of date, wrong, or not for 4.3/ 2.55; and the problem(s) I'm running into:
Procedure:
1) Unlock the bootloader and get s-off -- Firewater should be able to do this using the temproot method
2) Flash recovery mod, I was going to use CWM since it worked so nicely on my Incredible for 4 years -- this requires an unlocked bootloader and s-off, done the standard way via fastboot
3) Use CWM to flash superuser in recovery -- push the zip to sd, flash it from recovery
4) Happy times with my old set up back
Misinformation:
1) HTCdev -- no longer allowed for HTC One by Verizon, can't unlock bootloader this way. Renders a lot of the threads irrelevant now that this is not a valid route
2) rumrunner -- works for Android 2.2.4, not 2.3, and up to hboot 2.54
3) firewater "standard method" -- useless to anyone attempting to root a new device for the first time
4) "flash ARHD, then run firewater" -- again, not useful if you're trying to get CWM and SU on your phone for the first time
Problems:
1) The big one. Running temproot/ firewater, I acquire root access after running temproot, but when I run firewater after I get
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
preparing, one moment
The first bottle is open
chugging..........
C:\adb>
Click to expand...
Click to collapse
with the adb shell crashing out, and my phone will freeze, requiring a hard reboot.
2) I got a few suggestions to use rumrunner (before I decided rumrunner was 2.2.4, from the sources I could find). The process would be going fairly smoothily, until it would crash with the error "looks like device is not rooted AND lacks an unsecure kernel. su or FU!!" I also once got an error about "unexpected process or ROM" but haven't been able to replicate it.
3) Found some advice for "flashing CWM without s-off"...that obviously didn't work, but I thought I might as well try
4) Not so much a problem as a concern...I'm a bit worried about my drivers. I think they are good and up to date, I got them from HTCsync, and have full adb and fastboot control to my device, but still...
The Jury
So, what's your take? Am I missing something obvious?
Update
atewsleybooth said:
So, what's your take? Am I missing something obvious?
Click to expand...
Click to collapse
Update
I tried going through the firewater procedure on OSX instead of Windows, with the exact same results (crashing out of adb shell). This leads me to believe that the problem is with the device, and not the computer. Does that sound right?
I switched cables, got one instance where I actually received "somebody pissed in the firewater reboot and try again." However, 2 reboots since with the same cable and port have both gone back to crashing out of the shell.
Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.
Gizmoe said:
Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.
Click to expand...
Click to collapse
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.
atewsleybooth said:
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.
Click to expand...
Click to collapse
Have u tried to factory reset the device?
Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.
cmlusco said:
Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.
Click to expand...
Click to collapse
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.
atewsleybooth said:
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.
Click to expand...
Click to collapse
Weird. Glad you got it to work though.