I have been trying the 3 step root for a good while now, and after everything is pushed to the phone, it tells me to "choose the bootloader option and press power........" if you did it this way you know what im talking about. Anyway, my phone never boots into bootloader. In all but two times of trying it has stayed at my normal homescreen. when i finally get to the boootloader, a very rare occurrance, i press power, let the rom flash, and when it should ask me to update, it gives me the attached picture. Its so frustrating because I'm a noob. please help!
I didn't use Easyroot but from what I've read you need to follow the instructions in that pdf file I linked you exactly. Apparently some steps may need to be repeated multiple times.
This user had the same warning as you after the OTA and said he got it working by just following the instructions and performing steps until it worked.
http://forum.xda-developers.com/showthread.php?p=15632108#post15632108
I've tried it over and over again, and typically got no result, but thanks for leading me in the right direction. I'm not running custom firmware... To my knowledge. I'lltry to reinstall everything on the phone and computer that has anything to do with adb like one of the posters said. Again, thanks!
Related
I am sure by now you have caught some of my posts floating around the forum in a near panic with confusion. Here are the steps I have taken followed by the issue I am dealing with. I understand I may have taken these steps out of order and am very interested in getting some detailed help on how to fix the issue I am in.
Starting with a fresh stock Atrix I..
Step 1 - Ran Adeo for version 0.1 I downloaded all of the drivers correctly from the MobileTech video website however I honestly don't know what this even means.
Step 2 - Rooted using Super Once click.
Step 3 - I tried to install the Gingerbread theme but after much frustration and many failed attempts I found out I suffer from the missing ADBD file.. I read the thread and it said to download the file unzip it and add it to SBIN.. I have done this countless times and my phone is still unreadable but AROOT, Super once click and Adeo installer..
Rebooting removes the file as mentioned in that thread but I can never actually get anything to recognize my device while the file is in there.
I am set to USB connection NONE and using the Debugging setting in the ON position.
At this point I want to start all over.. Completely go back to stock and then try again, maybe not even that.. I am very turned off of this experience and am starting to get worried considering the investment in this phone I have. (Full Retail)
I understand many people on this forum are not only busy but do no suffer from this problem but I have also seen some incredible help given so as always anyone who is willing to help me just know it will be very appreciated. Thanks!
JoshRH said:
I am sure by now you have caught some of my posts floating around the forum in a near panic with confusion. Here are the steps I have taken followed by the issue I am dealing with. I understand I may have taken these steps out of order and am very interested in getting some detailed help on how to fix the issue I am in.
Starting with a fresh stock Atrix I..
Step 1 - Ran Adeo for version 0.1 I downloaded all of the drivers correctly from the MobileTech video website however I honestly don't know what this even means.
Step 2 - Rooted using Super Once click.
Step 3 - I tried to install the Gingerbread theme but after much frustration and many failed attempts I found out I suffer from the missing ADBD file.. I read the thread and it said to download the file unzip it and add it to SBIN.. I have done this countless times and my phone is still unreadable but AROOT, Super once click and Adeo installer..
Rebooting removes the file as mentioned in that thread but I can never actually get anything to recognize my device while the file is in there.
I am set to USB connection NONE and using the Debugging setting in the ON position.
At this point I want to start all over.. Completely go back to stock and then try again, maybe not even that.. I am very turned off of this experience and am starting to get worried considering the investment in this phone I have. (Full Retail)
I understand many people on this forum are not only busy but do no suffer from this problem but I have also seen some incredible help given so as always anyone who is willing to help me just know it will be very appreciated. Thanks!
Click to expand...
Click to collapse
At a glance I would try looking into the adb offline issue [fixed] thread in this section. though thats from the glance over what you seem to behaving and use aroot, superoneclick is sai by some devs to make a mess of things.
Sadly this is my actual problem. I do suffer from the missing ADBD file however unlike others in that thread I am unable to get anything to work after adding the file back in.
Someone has to have a solution to this. I know my OP is long but I'm at a loss here.
Sent from my MB860 using XDA App
At this point I would be willing to make a hefty donation to a devs paypal to help solve my issue.
Would anyone at least be able to offer advice on what to do from this point forward? Thanks
JoshRH said:
Would anyone at least be able to offer advice on what to do from this point forward? Thanks
Click to expand...
Click to collapse
Warning this will restore your phone to a "updated" stock build and will wipe all your data
1) Download this http://bandbinnovations.com/OLYFR_U4_1.5.2_SIGNED.rar
2) Change the .rar to .gz then extract with .7zip or Winrar
4) Install if not already the 32 bit http://www.multiupload.com/QNFILE4F07 and/or 64 bit http://www.multiupload.com/FIN3KYUD7S
5) Install RSD Lite 5.0 (from here http://www.mirrorcreator.com/files/1TFKDEHB/rsdlite_5.0.msi_links )
6) Turn off the phone
7) Turn on the phone while holding the volume button top
8) Once again, press the volume key up
9) click the ... icon in rsd lite select the firmware file and click start
10) grab a beer and wait until it says passed
So I unsuccessfully attempted to root my HTC Amaze. I unlocked my bootloader successfully, and followed the directions from one of many online guides; specifically the "Zerg Rush Root" method (I hope you guys are familiar with the method, the guide on this forum seemed to be the manual way). The problem occurred towards the end of the process where the phone finally reboots itself into 'root' mode.
Let me describe the steps I took to get to that point. I apologize for the length, I wanted to be as in-depth as possible. Please bear with me.
After unlocking my bootloader, I would execute the "Zerg Rush" program; the command prompt would pop up, do its thing, and seem to finish with no errors. I press a key to finish and close the command prompt when it asks for it, and wait to see if my phone went through any changes. No change. So I reboot my phone. Again, no change. Thinking there might've been a hiccup somewhere, I repeat this whole process once more with the same result.
I then realize that I didn't extract the "Zerg Rush" program to the directory the online guide told me to extract it in. I didn't think the directory made a difference. So I moved the folder to the instructed directory and executed the program once more.
This time, in the command prompt, towards the end when it lists "xxx zerglings sent" and "finding a new path", there were extra commands that I haven't seen during the first two tries. The command prompt then gets to the point where it says "awaiting response from device" and my phone starts to reboot. This is when the problem occurred.
My phone got stuck in a boot-loop (the droid emblem rocketing upwards followed by the HTC logo) with no sound. This loop went on for about 15-20 min all the while with the command prompt continuing to display "awaiting response from device" until it finally booted and displayed the lock screen. I slide the unlocker and immediately notice the phone is sluggish, has no sound, doesn't vibrate on touch, and has no service. Apps and Widgets might've been missing from the homescreen too but I cannot confirm this with certainty.
After a few minutes of panicking, I decide to reboot the phone. Luckily, it booted like normal, in non-root mode. All the functions returned and is currently in its factory setting. Bootloader is still unlocked.
At this point, I'm scared to re-attempt the rooting. I fear the infamous "Bricking" of the phone which pretty much renders the it irreparable.
So my questions are:
What could've caused this? Could it be because of the first two unsuccessful attempts?
Are there any precautionary steps I should take to ensure my phone's safe operation?
Is it safe for me to attempt rooting again? And if so, which method should I use?
DougieJK said:
So I unsuccessfully attempted to root my HTC Amaze. I unlocked my bootloader successfully, and followed the directions from one of many online guides; specifically the "Zerg Rush Root" method (I hope you guys are familiar with the method, the guide on this forum seemed to be the manual way). The problem occurred towards the end of the process where the phone finally reboots itself into 'root' mode.
Let me describe the steps I took to get to that point. I apologize for the length, I wanted to be as in-depth as possible. Please bear with me.
After unlocking my bootloader, I would execute the "Zerg Rush" program; the command prompt would pop up, do its thing, and seem to finish with no errors. I press a key to finish and close the command prompt when it asks for it, and wait to see if my phone went through any changes. No change. So I reboot my phone. Again, no change. Thinking there might've been a hiccup somewhere, I repeat this whole process once more with the same result.
I then realize that I didn't extract the "Zerg Rush" program to the directory the online guide told me to extract it in. I didn't think the directory made a difference. So I moved the folder to the instructed directory and executed the program once more.
This time, in the command prompt, towards the end when it lists "xxx zerglings sent" and "finding a new path", there were extra commands that I haven't seen during the first two tries. The command prompt then gets to the point where it says "awaiting response from device" and my phone starts to reboot. This is when the problem occurred.
My phone got stuck in a boot-loop (the droid emblem rocketing upwards followed by the HTC logo) with no sound. This loop went on for about 15-20 min all the while with the command prompt continuing to display "awaiting response from device" until it finally booted and displayed the lock screen. I slide the unlocker and immediately notice the phone is sluggish, has no sound, doesn't vibrate on touch, and has no service. Apps and Widgets might've been missing from the homescreen too but I cannot confirm this with certainty.
After a few minutes of panicking, I decide to reboot the phone. Luckily, it booted like normal, in non-root mode. All the functions returned and is currently in its factory setting. Bootloader is still unlocked.
At this point, I'm scared to re-attempt the rooting. I fear the infamous "Bricking" of the phone which pretty much renders the it irreparable.
So my questions are:
What could've caused this? Could it be because of the first two unsuccessful attempts?
Are there any precautionary steps I should take to ensure my phone's safe operation?
Is it safe for me to attempt rooting again? And if so, which method should I use?
Click to expand...
Click to collapse
How long did it take for you to type this up?
Did you try this thread: [HOW TO] ROOT HTC RUBY / AMAZE 4G
In the x amount of time that you spent typing that up you could have already had it rooted.
Lol you just pulled a "too long, did not read" on me. I did spend a good minute trying to articulate my experience. My main concern was whether if it was safe to attempt rooting after what happened. I'll take your response as an All-Clear and get right to it. Thanks
DougieJK said:
Lol you just pulled a "too long, did not read" on me. I did spend a good minute trying to articulate my experience. My main concern was whether if it was safe to attempt rooting after what happened. I'll take your response as an All-Clear and get right to it. Thanks
Click to expand...
Click to collapse
Yeah pretty much.
DougieJK said:
At this point, I'm scared to re-attempt the rooting. I fear the infamous "Bricking" of the phone which pretty much renders the it irreparable.
Click to expand...
Click to collapse
It's pretty much impossible to brick your phone with S-ON right now
DougieJK said:
So my questions are:
What could've caused this? Could it be because of the first two unsuccessful attempts?
Are there any precautionary steps I should take to ensure my phone's safe operation?
Is it safe for me to attempt rooting again? And if so, which method should I use?
Click to expand...
Click to collapse
You should read the HOW TO Root guide, FAQ, and READ THIS FIRST,
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
I would try to install the RUU to get it back.
It's probably not Bricked.
You can also check out the more full unlocking procedure http://forum.xda-developers.com/showthread.php?t=1690919
I believe one or both these procedures could be started while in the bootloader.
I'd try the RUU first though.
Look in the Sticky thread in Dev for the RUU (an EXE you run on the PC).
greek goddess said:
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
Click to expand...
Click to collapse
This happened to me as well. Then i realized i have both my old Epic4g AND my new EVOLTE plugged into my computer. I unplugged my epic and voila. it worked just fine. If it still doesnt work, try restarting your PC and redo the process.
Thanks guys for your answers. problem is resolved, but I will what happened in case anyone else has this problem.
I couldn't get the drivers to install on my laptop so I went to the desktop and ran the root. The error messages I got were like this: after the second reboot (supposed to reboot 3 times) it would say "device offline" and it filled the whole screen with that line. Then it said "error too many emulators" and then it would say it was done and that is as far as it would go. It did not boot a third time. I could reboot it, but it would only get as far as the screen JUST before the unlok ring comes up, and that's it.
After posting this thread I read another thread where someone suggested holding the volume down and power to bring up stock recovery and doing a factory reset from there (rookie mistake, I have had the Epic Touch for a while and forgot about the Evo's stock recovery). That got me back. THANK GOD! But still no root.
I didn't want to give up trying to I went back to my laptop and still without necessarily "installing" the drivers, went ahead and tried running the root and VIOLA! It worked flawlessly!
So I don't understand what was going on with the desktop though with the "device offline" and "too many emulators" thing, so if anyone could shed some light on that, I would appreciate it.
glad to hear you got it fixed but if you would have had to filed a claim then you can always say you lost it or something like that.
Well i have been looking all over for help with my phone. I have figured out that i tried to flash a rom without unlocking my bootloader. Well im running windows 8.1 and for some reason i couldnt get my computer to recognize the phone at all. After using 3 or 4 different guides i gave up for a few days so not to get too aggrivated. I mean its my own fault but my back up phone sucks lol. So i borrowed my wifes laptop running win 7. I Followed this guide androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html. For the first time since i started trying to solve my issue everything seemed to work got the s/w screen to appear in reverse and using the cmd prompt that says wiating for device then starting the .bat file from the download it says on the bat cmd prompt that everything worked. well at the bottom its says done then comes up with C:\fastboot\yours. i have been browsing google but i havent been able to find what i am supossed to do with the yours file. i tried putting a kdz file into the file location and running it from that but no luck. after a few min the phone auto reboots and comes back with the security error screen and not the backwards one. i have tried doing the hard reset at the point but no luck. if someone could please help with what i need to do with the fastboot/yours area that would be awesome. Or at least point me in the right direction cuz google isnt wanting to be my friend with the searches.
Android noob in training:
Sobih
help
Well i have tried several times now with using my wifes windows 7 laptop. i can get everything to work with the screen coming up backwards and in the command prompts it says that the fastboot is done then loads the command fastboot/yours which with the file i downloaded that file was empty. really unsure on what i need to do at this point. from the guides i have read it seems that im at like a step or 2 from getting the phone to work but after 30 seconds while still plugged in it reboots and loads the secruity error screen. from what i have read i should be able to do a factory reset by holding the volume and home button and then pressing the power for 3 seconds but it just reboots into the error. any help would be much appreciated i really dont want to have to buy a new phone.
Seems like that guide is more for when flashing a recovery on the locked bootloader and things go wrong. It was suggested a few posts down on the first page of that guide that if your problem happened when you were trying to flash a rom you might want to follow this : http://androidforums.com/optimus-l9-all-things-root/792689-guide-unbrick-manual-update-updated.html or http://forum.xda-developers.com/showthread.php?t=2085344 (the xda one seems more complete) .
sigh
Well im still stuck on the security error screen. i got the phone to boot into the backwards fastboot screen 1 time and cant remember how to do it again. i can boot into the s/w upgrade mode. if i go to use the lg support tool being that im in the united stats my options is upgrade recovery or help. well if i go to upgrade recovery im told that my phone has the latest upgrade already. if i try and use the moduptest that come in a lot of the unbricking guides it makes me turn the internet back on even with having hte shttps and everything else that is listed in the various folders. i only have the omap44 on my device manager 1 time but there is also 2 lg mobile modems. im thinking my issue lies with the fact thta i dont have the adb file for the device manager. i have donwloaded and uninstalled various times but still no luck. i dont remeber how i got the phone to the backwards fastboot but i remember i was following a guide and the op had to open one file and while that one was stuck on "waiting for device" he opened another one becasue that was the only way he could get it to connect. Any help would be awesome. not trying to rely on everyone else but after several weeks trial and error im at my wits end with it.
thanks
sobih
can you please help me with a soft unbricking of my lg g vista (vs880 [11b]) from verizon usa? i found the 880-11b firmware file, at least i think its the right one. if you know of/ come across this and are sure of its validity i would trust that more. i found and downloaded via a google search. i initially think i may have accidentally deleted the splash pic for the carrier when it boots. this caused it to just black screen after the lg logo n the backlight would flash like it was stuck in a boot loop just the image file was missing. after a little more research i figured out how to put it in the download mode so that i can use a pc to try repair or reinstall whatever it needs. i am unsure if i need the sdk or adk toolkits for a repair in the download mode to work. while on that screen it says its plugged in and waiting to download firmware via usb under the progress bar it tells me not to unplug until download is completed. its not showing up in "my computer" however. and i've never had to do s software/firmware download or setup when the phone wasn't in full normal working order. i simply want to put back the out of the box software back in place. firmware 88011b and 4.4.2 os. just want to be sure i get the proper files/and or programs/ directions to use those resources properly the last thing i want is to guess at something that i could ask someone more experienced for help with and end up bricking it beyond repair. any and all help is very appreciated and i must ask you to please explain each step as clearly and "dumbed down" as possible as you can. if i need to use a program i've never used before {i.e. i hear things like odin mentioned in the forums but i don't understand or have any experience with any pc to phone applications so the more detailed any instructions can be made the better. anything that most ppl who have started tinkering with their devices usually know as common sense or steps that seem implied if not specifically mentioned i'll miss. i have been reading n lurking for months n managed to root the device. but had another issue i accidentally caused soon after which resulted in a factory wipe and some time to remember what i did that rooted it after spending a day on it the first time n trying many things it took me a while to refind what i had done that worked. then this happened. i'm sure with the proper files/tools it'll be fine but i need help to know what those are and to be sure i do it right the first time. i know if i don't there may not be a second chance. thank you again in advance for your patience and help.