Database Users

impossible to root HELP ME PLEASE

To all devs out there ,im been trying to root the hero for a week now ,ive tried every guide going also the gold card with 10 different sd cards with no luck.the rom what ive got is the release 2.73.405.66 rom.it has the new nboot is thats why i cant flash.is there any way i can wipe all date and software so i will have nothing on the phone and then install an earlier rom, its just an idea as im starting to lose it with this fone.i hope someone can help me or do i have to wait for the official update from htc

with this rom version you need to create a goldcard and downgrade your rom before you can install a custom rom. if you have problems with the goldcard you should be more specific.
waiting for the update doesn't seem like the best idea, because it might take some until a security flaw is found that allows to root the rom when already installed on the phone. if you have the custom recovery image you will be able to install the (pre-rooted) update short time after it was released.

You should be able to use fastboot for this issue.
Search around the forums, (also http://hero.modaco.com) and read about it.
All you need is the fasboot tool, a usb cable and the "debugging mode" switched on at ur phone...

everytime i create the gold card and try to downgrade the rom it states boot error 140.i follow the guides very indepth i get the serial number from the sdcard than i reverse the string and then replace the first two numbers or letters with 2 zeros how can you tell when the goldcard is on the sdcard.when i replace the sdcard back in sdcard reader it states that the folder is empty.im quite clued up on winmo but android is giving me a headache

wouldn't the fastboot give you the "remote: not allowed" error?
anyway, you can try:
start your phone by holding back and pushing power, you should see three skating androids. put recovery image in the folder where your fastboot.exe is, open terminal and go to that folder and type:
Code:
fastboot boot recovery-RA-hero-v1.5.3.1.img
if that works report back.
for the goldcard i can't help, never did it.

at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!

rednose30 said:
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
Click to expand...
Click to collapse
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!

mjames_84 said:
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
Click to expand...
Click to collapse
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!

TastyBurger said:
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
Click to expand...
Click to collapse
Hi
I have tried making a goldcard, and installed via. the RUU shown here.. 405.5 .. but then I tried using Flashrec to get another recovery image, it failed making the first step...
So is my phone rooted or did something go wrong ?

the phone is still unfortunately not rooted. I would've tried the fastboot method
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk

just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!

nicknyhk said:
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
Click to expand...
Click to collapse
Very similar story. I did make a goldcard but hadn't got as far as finding out how to extract the update.zip out of the RUU exe, in order to use it. I tried running the RUU to see what would happen & my Hero downgraded.

Root AT&T R2CA016 Help!

I need help rooting my x10a ive probaby tried everything the side loading the tricking of the desktop manager, im really on the brink right now i need clear guide to do this i just really want to be able to install PdaNet on my phone and ive been searching around but i could only get to some point till i get an error or wont be reognized or i cant find the folders asked on the tutorials even when i have hidden folders set to be seen or when i thoroughly search the computer long story short i really need help or maybe i could send my phone over to someone overhere in florida please guys ide appreciate the help and if its to much i can send maybe some amount of money via paypal i would really appreciate it guys
Sent from my X10a using XDA App

Hit up this:
http://forum.xda-developers.com/showthread.php?t=790505
Should tell you what you need. I believe sideload wonder works only if you have installed the android sdk which you can just google and download it. Put the android sdk in the root of your c: drive of your computer. I think you need to place the sideload wonder in the tools section of the android sdk too. Afterwards, I had problems getting the phone to be recognized by my computer. I got mine to work by installing SEUS on my computer and preparing it for update. It will install the necessary drivers for your phone to work. (There is also an update for AT&T rom if you want to install it, but I haven't seen any difference after the update.)
FYI - I never got sideload wonder to work on my computer, but I did learn how to use the adb method of sideloading apps. Sideload wonder is just a "pretty" version of the adb method, so I would just learn how to do it via that way. You can check out this thread called adb for noobs.
http://forum.xda-developers.com/showthread.php?t=532719
PM me if you have any questions but replying on the first thread I posted will probably get you better results, but of course read up first!
Good Luck.

I did get to root my phone updayed the busybox and couldnt.sideload apps anymore, unrooted.the phone and re-rooted still nol luck reinstalled seus 2 times and re rooted 2 times and cant downoad non market apps im stuck with a rooted phone and cant downpad thirdarty apps what up with tht i need help!
Sent from my X10a using XDA App

is there someway i can get my phone to tether i dont care if it bluetooth or wired just need to tether!
Sent from my X10a using XDA App

fix for semibrick with no 3 button mode(black screen and vibrate)

hi all thought i would share my experience with SGS semi brick in the hope that some of you would find it usefull.
firstly i would like to thank everyone in the dev community for all the information and hardwork going on out there.
secondly thanks ryanaz for the great software Z4Root and oclf they worked great (once i used them properly my own fault)
thirdly if im repeating information thats already been covered elsewhere then i apologise in advance but i couldnt find it
back to topic: stock SGS with 2.1 on tmobile uk connected to windows 7 pc
last night i managed to semi brick my phone in the following way:
1. updated to froyo using official method via kies
2. ran z4root and executed temporary root
3. ran oclf seemed to work ok but following oclf reboot i ended up with black screen and occasional vibrate with glowing softkeys if touched and nearly crapped myself as i broke my phone
from research it seems that this problem indicates a fooked partition screwing up the internal sd and logically it is probably because i used temporary root as the root is removed following a reboot so during oclf reboot memory may have been corrupted.
i have since used permananent root and oclf and it worked really well no problems
my phone does not have the 3 button recovery mode and i was gettin a bit concerned after hours trawling the net it seemed i was going to have to go for the 301k resistor jig which i didnt really fancy.
fear not i figured out a method of getting into download mode without 3 button method or 301k jig using odin and adb commands.
its a combination of different methods for different things and it may not work for everyone but it worked for me. maybe some of the more experienced dev's can shed some light on it or refine the process.
required:
odin
pit file
rom files
adb
slight dos command knowledge (easy to find on net if you dont have it)
its important to say at this point that the phone wasnt fully bricked as the fault indicated the bootloader was intact and if the following works for you then the procedure should work.
quick check to see if it may work connect phone via usb with battery out, boot up odin, put battery into phone and switch on. if its recoverable then it will show a connection in odin in yellow with a com# (# will be a number indicating a com port. the number isnt important so long as theres one there)
if you try and flash the phone it will fail no matter what pit or rom you use as you cannot get into recovery or dowload mode.
to get into download i had a play with adb (search adb for how to use it. i hadnt heard of it before yesterday it requires knowledge of command line use in dos mainly just to navagate to the adb folder and execute adb. search dos commands if you cant figure it out and look for CD for change directory and dir for dir list)
important bit:
follow the procedure earlier to get phone communicating with odin then start adb. once in adb i used the command:
adb reboot recovery
and hey presto my phone went into download mode i was then able to reflash the phone using the normal Odin methods.
now i have my lovely phone with a faster operating system, streamlined rom and root access happy days.
just as footnote i had never messed with android before yesterday as i had always been on windows mobile so with a bit of research its amazing what you can learn. and i know this guide isnt very n00b freindly but its how i best remember it from last night after searching various things for 5 hours(ive slept since then) if any of it is incorrect then i apologise in advance but ive left it intentionally vague as the experienced dev's will know what im talking about and the n00bs(like me yesterday) it wont hurt you to go and research the topic and you might learn something instead of just posting questions all the time
peace out
p.s. forgot to mention ensure that you kill any kies processes running on your pc before attempting this and ensure you have internet connection so windows 7 can obtain drivers if required. xp or vista may require drivers to be manually installed though not sure

thank you so much!!! you just saved my phone. I was going to send it to a service, but now I can flash it with odin

Or, the morale of the story, always make sure you have 3BR

LG G2 Fastboot

Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.

Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)

For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.

Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks

You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app

I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.

demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks

dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks

Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app

Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.

[Q] [Help Please] LG g2 d802 No ROM / Boot Issue

see post 4

see post 4

see post 4

d802 int
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!

kye1987 said:
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
Click to expand...
Click to collapse
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for

XxZombiePikachu said:
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
Click to expand...
Click to collapse
Cheers I'll see if the supermarket has them at a half reasonable price, otherwise ebay has them for £1 delivered and I'll have to wait. Thanks for the reply and confirmation that would work though.