Develop Bugs

How can i go back to default?

I tried the "IDIOT-PROOF Root Guide! NAND Unlock and ADB Update!!".... to no avail.
I had fallowed the instructions to a tee and around step 55 it all went down hill, it was supposed to automatically flash a ROM and it did nothing, and now i have probably screwed it up worse. Phone is still 100% functional but i would like to reset back to factory settings, no root, no nand, no custom rooted ROMS, nothing.
Does anyone know of a way to get my phone back to the way it was when i walked out of Best Buy earlier today?
Thanks for the help and all the great resources here at XDA.
Daugusta.

Search for and run the RUU

Step 55? Thats the idiot proof guide? I followed the original guides and there were like 10 steps max..

Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.

Daugusta12 said:
Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=685835&highlight=RUU
This is not flashed, its an exe so its run while your phone is plugged in. Should go smoothly, but as always know the risks of flashing anything
I've heard toasts method is pretty solid for rooting.

Quick question wouldn't this be in Q & A? Not trying to come off as a jerk. Just my 2 cents
Sent via the Sprint HTC EVO

RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta

I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.

Trust me im not giving up

Try the 1-click Root Method
I looked at the fifty-five step root method and peed my pants, then I hit up jiqqaman's one-click root method. Stable root, and you can flash the stock (rooted) rom.
[forum.xda-developers.com/showthread.php?t=706411

Diesektor said:
I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.
Click to expand...
Click to collapse
When I have ran an rru from previous HTC phones I have had to have sync up. But then again its never been at a black screen
Sent via the Sprint HTC EVO

Ya, i had the HTC sync running as well, synced up fine with my comp but the RUU still gave me the same error.

Im running this on Win 7 64 Bit, im guessing the 64 bit may be the problem. ill try it on a different comp and see how it goes.

Just tried it on a 32 bit Windows 7 comp, still same issues.

Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.

Daugusta12 said:
RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta
Click to expand...
Click to collapse
It should work. After the program doesn't recognize it, while your phone is at the HTC logo. Close the program on your pc and start it again.

Daugusta12 said:
Just tried it on a 32 bit Windows 7 comp, still same issues.
Click to expand...
Click to collapse
There shouldn't be any problems caused by 64-bit OS. I used Win7 Ult 64-bit and it worked fine. Do you have the HTC Sync drivers? That may fix the problems you have.
EVO'D_OUT said:
Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.
Click to expand...
Click to collapse
I noted this too, only I didn't have an iPhone, just an iPod Touch. Despite this, I am having a lot more fun with Android and how it works. I.E. *.9.pngs which made made jaw drop when I understood how it works. SO AMAZING.
I don't think I will ever be much of a dev, but who knows. I have been digging through a TON of documentation over the past 2-3 weeks.

Thread moved to Q&A.

well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.

EVO'D_OUT said:
well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.
Click to expand...
Click to collapse
Great question.. Some of these long winded threads need trimming and a definite answer listed out. Clutter = confusion

Simple root(compared to joeykrim) for shw-m110s and galaxy cousins

http://forum.xda-developers.com/showpost.php?p=8406167&postcount=223
So this already has a home. But I'm seeing that it works, very likely in ALL galaxy S cousins, and in fact possibly even in all 2.1 and 2.2 android phones. This is NOT the joeykrim method but it's related (but simpler and better, and obvious to most of you devs). Sadly this slowly gets rediscovered somewhere about once every two weeks for the past couple of months . There's a thread in epic started a few days later with the same trick, and a thread on droid forums:
http://www.droidforums.net/forum/re...08-multiple-phones-root-them-unroot-them.html
a couple of weeks earlier with the same trick. And a page on cyaongenmod where they show it for just one of the cousins.
It's nice for anyone who doesn't want to flash, and/or doesn't have a fully working recovery mode needed to use some of the one click methods (update.zip). Moreover... it probably works on pretty much EVERYTHING. The one clicks distract attention from the fundamental solutions because they don't always work on everything and new phones come out like popcorn.
Also I've included some useful related information about how to setup some of the popular initial root tools (with some personal bias, but not unlike a custom ROM), and how to undo it all. Making it a whole package custom ROM alternative (albeit a very lite alternative ). I haven't seen another post with all of this in one place.
I don't know where I should post this though because there is no general forum that I guess is likely to get read much that connects all the devices this may work on. But since it's working on more devices now and probably on froyo too, it seemed it might be helpful to someone to expose it a little beyond the shw-m110s sticky on issue 6. (even it has already been exposed before).

isnt this the same as superoneclick lag fix?
this didnt work for me on my i9000 froyo rom.

Ok.. well, does rageagainstthecage still work? Do you know? Did you try just that? the information "it didn't work" isn't very helpful. But then when you have one button you tend to get one response, and that's partly my point.
If you can get root with rageagainstthecage, the rest can all be worked out. And much more easily if more people in the community start to fear less the internals cause they're given information about what's going on, and it's VERY simple, as you can see in my post.. there's only ONE thing (properly installed su) you need to have root on ANY device. (getting root is a different issue, but the hard part is done) And there's no reason not to be explaining that in the BIG FAQ.
Indeed.. it looks like it probably is the same thing (but it's not really documented) . That did not exist when I first posted it.. hence why I worked it out myself. Personally I'm not a fan of one click anything, not as the primary reference at least. Because, ok.. it seems rageagainst the cage probably works on anything. A decent faq somewhere actually EXPLAINING what's required for root, and what rageagainstthe cage does (losely) and at least an example of how to use it on some device then is a good starting place for new phones.. new froyos.. good reference info.
However instead what happens is somebody else comes out with their latest method.. releases it as the mysupermagiconeclick method.. or even if it's script, without any explanation (and most people wouldn't understand, but maybe a few would). And then what happens?
Joeykrims script gets adopted on like 5 diferent devices where it isn't even needed(no offense to him.. he provided what he knew and got some people going who wouldn't have been otherwise). Multiple problems are created because of it. and that's not even a one click. That's a script for people who aren't too afraid to type script and still nobody noticed it wasn't needed?
Now a big one click comes out and someone just says "this doesn't work".
I see so many people saying "I don't know how to use adb" (even after you just told them "type adb push". It's very different that the winmo atmosphere a few years ago.
Anyway, I rageagainsthecage is the only alternative I know of to flashing or update.zip so it would be good if it got a little more attention I think and if people stopped treating the task of copying in 3 little files with permissions like some mystery work for "devs" to handle and folks to praise on high. I mean it's nice if someone can make a gui(and it takes work).. but it's amazing how hard it is often to just find an explanation of the very simple thing that's actually being done. (edit: even in Clshortfuses superoneclick thread.. he links to an older thread with the commands, but it's in page 49 or so.) There's like 5 commands needed with about 2 slight variations (nand unlocking and the setuserid joeykrim problem) that will root anything without flashing or destroying data, and that's not explained in a simple faq around here.)

By the way another reason it might not work is the rageagainsthecage exploit doesn't always (usually though) work the first try, and works better on some usb ports than others.

elsewhere:warlordxp said:
I have a problem with rooting my JP6
The Odin version seems to get well. But after reboot no root.
Then i tryed the SuperOneClick version.
I get this msg.
Pushing rageagainstthecage...
failed to copy 'rageagainstthecage' to '/data/local/tmp/rageagainstthecage': No such file or directory
OK
Click to expand...
Click to collapse
and I found the same thing on some german site.
maybe /data/local/tmp doesn't exist on froyo for I9000. If anyone was playing with a prompt and had instructions that point out that you only to need to copy it to ANY place where you can write and execute, they might figure out what's going on in one minute, and find another place to copy it to like just /data/local or wherever tmp got moved to. In every case I've seen problems, it was never that the exploit didn't work.
Now ok.. it's possible that somehow they've figured out a way to completely block writing new executable files anywhere from a shell. In which case it would need to get installed through an apk maybe, but it's still possible. Applications do run, all the time; so can this. Knowledge is power... not one click buttons.

ok then ill give you a bit more detail.
you are right, i cant see why it is failing although i can see where it is failing. if i had access to the script to see the steps its trying to take i could work it out but its compiled into a binary as far as i am aware.
the script pushes the file to the device, and it runs for the first loop. it installs the su command and superuser.apk, then loops back to make further changes (i.e. it kills adb and reestablishes a connection). when it loops back it tries to mount something, and fails saying "failed to find mount point" or something similar.
the su command works in shell/terminal until the phone is rebooted, then it is lost. the superuser doesnt work at all (i.e. no superuser requests are generated by apps requiring it, they just fail saying root not available).

kanemari said:
ok then ill give you a bit more detail.
you are right, i cant see why it is failing although i can see where it is failing. if i had access to the script to see the steps its trying to take i could work it out but its compiled into a binary as far as i am aware.
the script pushes the file to the device, and it runs for the first loop. it installs the su command and superuser.apk, then loops back to make further changes (i.e. it kills adb and reestablishes a connection). when it loops back it tries to mount something, and fails saying "failed to find mount point" or something similar.
the su command works in shell/terminal until the phone is rebooted, then it is lost. the superuser doesnt work at all (i.e. no superuser requests are generated by apps requiring it, they just fail saying root not available).
Click to expand...
Click to collapse
Great it sounds like you basically understand what is going on and aren't afraid of a tiny bit of typing. I think MANY people fit that description including myself a few weeks ago. But... the steps are not usually explained as you say. So... click the link in my first post again. It's all explained there. I've started a section there on exceptions.. including what I think might be going on with yours, but your description is a little different from the ones I copied in, so we don't know yet. So go at it, and good luck. I'll be glad to help if I can but my crusade is to get more people who want to to be able to play with it themselves (and to be able to ask questions too, though especially when getting new devices/roms rooted)
I assume you know about adb and and how to run it by hand in the first place. I don't describe that and there are faqs that do, including I think the Big FAQ. That obviously must work first.
P.S. I may add some linux/mac scripts shortly... piece of cake to do.. already did it for the joeykrim method. CLShortFuse is adding linux support but it involves 175 MB of cross-platform compatibality libraries and is at least almost as hard to setup as it is to just use adb. To each his own. It's a neat accomplishment if it works.
For me I push the unroot script to my phone and can unroot when I walk in a store if I want to. I like Rynza's apk for that, but it doesn't work with my phone (3 button, yes... update option, no )

too much verbage for me daddybear...
but anyway ill give it a shot next time i need to root my device and let you know if i come up with anything useful.

The first to admit to cracking the code . But you only get full credit if you know the reference too!
the su command works in shell/terminal until the phone is rebooted, then it is lost.
Click to expand...
Click to collapse
actually.. if this is really true.. it's almost certainly a joeykrim style problem. The other symptoms are harder to follow, especially depending if superuser never worked or only didn't work after reboot. Anyway, this will certainly get resolved in time I'm sure. If you had su working at all.. then it's just a matter of applying the right tweaks/work arounds (which are likely already known).

[SCRIPTS][Win] A100 Flashing Toolkit v1.1 7-16-12 Discontinued

As I wrote the guide I realized the files, scripts, and images are scattered through multiple threads, which makes finding what you need difficult, even from a main thread (the guide for example). This was compounded even more when I was writing the CM9 Install Guide for the CyanogenMod Wiki and listed the commands themselves, it became huge, intimidating, and looks extremely daunting, I can only imagine what a new flasher must think seeing it! And and so I decided perhaps I can fix this, and with that I present to you...
The A100 Flashing Toolkit!
What is it?
A single zip file that, when unzipped, contains EVERYTHING you need, ADB, fastboot, scripts, CWM recovery image, everything you need to take your stock ICS A100 through rooting, unlocking the bootloader, and flashing CWM recovery (twrp coming soon)!
How is it used?
Its a set of 6 PC scripts, 3 for windows users (.bat) and 3 for linux users (.sh). Run in order from the same folder, and you can just click and run, reboot, click and run, reboot, click and run, install custom rom, done!
You MUST already be on ICS! This is not for HC, if you are on HC update to ICS FIRST!
Instructions
Make sure you are on ICS! Read the bold red letters above! You have been warned! You should already have installed the Acer USB drivers for ADB to work.
Ok, now you're on ICS....right?
Download and unzip the file to whatever folder you can remember, for example c:\acer or ~/acer.
Open your file manager of choice and browse on over to where you unzipped the files, and get ready.
Windows
Right click on A100-root-win.bat and select Run as Adminitrator.
Once that is finished, let your tablet reboot.
Once it's rebooted, right click on A100-unlock-win.bat and select Run as Administrator.
Once this finishes, let the tablet reboot again (the script will tell you what's happening)
Once it's rebooted, right click on A100-recovery-win.bat and select Run as Administrator.
Allow it to finish, it'll reboot a couple times.
Half the time it reboots into recovery, other reboots into system, not sure why it happens.
If it boots into recovery, go ahead and make a full backup, might as well.
If it boots into system, reboot into recovery and make a full backup, might as well.
At this point, you can now wipe and install a custom ROM, see the A100 Guide in General for ROMs and instructions on this.
Linux
Execute A100-root-linux.sh and allow it to run.
Once that is finished, allow tablet to reboot.
Exectute A100-unlock-linux.sh and allow it to run.
Let the tablet reboot
Execute A100-recovery-linux.sh and allow it to run.
It'll either reboot into recovery, or system, it does one or the other for some reason.
If rebooted into recovery, make a full backup.
If rebooted into system, reboot into recovery and make a full backup.
Wipe and install a new custom ROM, see the A100 Guide in General for ROMs and instructions on this.
How to boot into recovery
There's a few ways, 1 way is an app like quick boot, you can use adb by typing adb reboot recovery or you can do it manually.
Power off the tablet.
Press and hold the volume - button, closest to power and lock switch.
Holding volume - press and hold Power.
Hold until the screen says Booting recovery kernel then let go.
You should be in recovery, either CWM, TWRP, or stock, whatever you have installed.
As always I am open to suggestions, advice, or reports! Feel free to post up or PM me with any issues, questions, bugs, or ideas!
Download
A100 Flash Toolkit 1.1 7-16-12
Now featuring the correct bootloader!
Thanks to smokku for pointing this out.
Who do we thank for this package?
ZeroNull: Alot of the scripting is based on his work, and borrows his ADB and fastboot executables.
ptesmoke: Uses his CWM recovery.img file
CyanogenMod Iconia Team: For allowing me the chance to write for the Wiki, and realizing this NEEDED to be done.
Anyone else I'm forgetting, I'm sorry I will add you as soon as I remember (feel free to drop me a note!)

Sounds great, many thanks.

Thanks for all you hard work and patience.

a100 flash program
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat

Birbey said:
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Click to expand...
Click to collapse
Oh wow OK I'll take a look I must have mixed everything up. My desktop is littered with files from all these projects. I'm sorry about that I should have double checked everything before I uploaded it. If the called files are different then the scripts it must be the old version mixed with new scripts or something. I should have it squared away sometime tonight/tomorrow morning.
Edit: I'm assuming by saying command prompt you use windows, the a100-root-win.bat file looks fine, was this one giving any issues?
I'm checking the second and third now for whatever is going on.
Tapatalked from my Galaxy S II.

Fixed.

I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA

diegof18 said:
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
Click to expand...
Click to collapse
You have to be FAST when it gets there, it times out in like half a second it seems.
When you run it, have the tab in your hand, fingers on volume - and volume + (volume - is next to the lock switch). As soon as you see the screen change, hit volume - then volume +. It takes a few tries usually. It'll just sit there until you reboot afterwards.

Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.

elander said:
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
Click to expand...
Click to collapse
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.

thanks for the info.
pio_masaki said:
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks

elander said:
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
Click to expand...
Click to collapse
I'm not sure, but I don't think resetting these puts them back to 100% if rooted, the root stays since it sits in /system. You'll have to manually remove SU then reset to get rid of the root, I think. Other option is restore through the update.zip method which should wipe /system. You could try a hard reset and see if it removes SU or not, it might.

Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"

NeO_CooL said:
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
Click to expand...
Click to collapse
Not quite clear on what you're asking, but as far as I know it should work on any version bootloader unless they changed it on some update, which wouldn't surprise me.
What is the whole message, and when is it occuring?

I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?

NeO_CooL said:
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
Click to expand...
Click to collapse
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.

Forgot to say i´m using the windows version.
Thanks

pio_masaki said:
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Click to expand...
Click to collapse
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 (not unlockable) bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445

smokku said:
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 not unlockable bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
Click to expand...
Click to collapse
It's just labeled a100, it isn't the actual a100 blob. But go ahead and use that link until I get the chance to go back through it, I'm obviously messing it all up somewhere, I may have used the a100 blob and gotten it mixed up with the a200 blob when I was renaming and shifting things around. I'll pull the download for now until I get the chance to get it all sorted out, sorry guys.
Edit OK its back up with the proper boot loader for unlocking. I can't believe I did that. Huge thanks to smokku for pointing that out!

No worries.
And yeah, you have to be quick when it asks to toggle unlock, like half a second quick.

Now I've DONE It! (Help...please?)

So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?

mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Can you boot in to recovery or bootloader (holding power+vol down)?
Sent from my HTC6500LVW using XDA Premium 4 mobile app

That I can

mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Put the stock odexed rom from my thread in development section in your adb/fastboot directory on your PC.
Enter Recovery, assuming you installed a custom recovery.
If not, do that first, using the links in Flyhalfs threads in our Verizon One Original Dev section.
In Recovery go to Advanced in TWRP I believe and do adb sideload > swipe to sideload.
Then you will need to enter in terminal: adb sideload filename.zip from within the fastboot directory with the stock file in that same directory.
Use the filename of the zip you are sideloading. Once its done pushing, it will flash the rom and then you can reboot.

I had tried straight off after the root to install CWM and it gave the option to do TWRP. I had a blank black screen and then kind of stalled so I forced it into the bootloader screen and just reset. In the present time if I attempt the recovery selection it just stalls again, a black yet obviously backlit screen. My new download of ADB does not look the same as it had when I did the last phone either. I don't know what I've fouled up here.

I'll send it out at this point to make the pain go away and have someone undo it.

mySStery_machine said:
I'll send it out at this point to make the pain go away and have someone undo it.
Click to expand...
Click to collapse
I can try and walk you through getting fastboot or adb set up so that you can try fixing it on your end.
It's also pretty well laid out in guides on Google.
If you really wanted to have it fixed for you, I'm about 12 hours or so south of where you are if you wanted to mail it here and back.
Up to you, hit me up via PM if you decide you wanna mail it.
Otherwise, myself and/or others will gladly help you undo it I'm sure man.
Then you wouldn't have to be without it for a few days.

You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.

mySStery_machine said:
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
Click to expand...
Click to collapse
Sounds good, I'll shoot you my gmail/Hangout info and we can get you squared away I'm sure.
Yeah, I'm up above there just a little, about 2 and a half hours or so from there.

Sounds good, I'm ready to tackle tonight whenever and for however long it takes.

Ok, have deleted and redownloaded the ADB files, yours as well as the TWRP. I have the recovery and your file chilling out in C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools . What now my new found savior?

Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *

mySStery_machine said:
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
Click to expand...
Click to collapse
Double check the md5 of the downloaded file.
Also shorten the path to the file, at least the folder names leading up to it, so that it's more direct.
Less chance of error or too deep of a path.
Something Like:
C:\Android\sdk\sdk\platform-tools>adb sideload 1.10.605.15_Deodex_Full.zip
Click to expand...
Click to collapse
You will have to rename a directory and a file or so to get it like that and this may not be the issue, but should certainly eliminate potential for issues.

Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?

mySStery_machine said:
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
Click to expand...
Click to collapse
Yeah try that, you may need to grab HTC Sync and install it if you haven't if your existing drivers aren't cooperating.

MD5 was corrupt, I finally got it to push.

Used pdaNet for drivers.

mySStery_machine said:
Used pdaNet for drivers.
Click to expand...
Click to collapse
Cool, glad that worked.
If you have any further issues or success, let me know.
Sounds like you should be good to go though.

Downloading another version to see if I can get the info across and get this One cooking again!

So should I do the other .zips below the post with your links for the firmware?

Need To Obtain Procedure As To How To Get Into Recovery Mode

Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David

Davy49 said:
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Click to expand...
Click to collapse
Hi David!
Holy cow, you've installed the entire studio? That's way more than you need. Just get the Platform Tools here: https://developer.android.com/studio/releases/platform-tools
At a user level, all you'll ever need are ADB and fastboot. Then enable developer settings, enable USB debugging and use the command 'adb reboot recovery'. You sure power + volume down don't work? Or power + volume up for fastboot (to get custom recovery installed)? Note that I have made zero research on this device so it may deviate (I'm on mobile right now). If any of those steps seem difficult or you're unsure how to proceed, just let me know where exactly you're stuck.
Oh and when you send an adb command to your device for the first time (like 'adb devices') it will likely show a trust notification on your screen, asking you to allow this computer to send adb commands. Make sure the remember checkbox is on.
Good luck!
Wrapped with delicious Fajita [emoji896]

Hi Timmy,
Thanks for being nice and explaining the process to me, that sounds pretty easy. Today my biggest problem is getting vanced to install on my amazon fire 7 tablet (2019 Edition). I've had it running normally on there previously, but a couple of day's ago I started the vanced app and noticed that I wasn't signed into my google account anymore. And when I attempted to sign in I received the now famous notice that said google server's were busy, please try again later. But knowing I had it running before, motivates me to get it running again. In the interim, I'm using the Web Tube app.
David

That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David

Davy49 said:
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Click to expand...
Click to collapse
Proper reboots in between? I don't see how web view would be related but it's always a good exercise to remove recent installations one by one, retrying Vanced in between. Be sure to share your findings if you encounter a potential culprit. It's important for the community to learn from that.

Hi Timmy (I guess it's okay to use this name),
I think before I do anything else, I'll go back and re-read the instructions on how to properly install it. Unless google has done something on their end, I should be able to get it functioning properly. It was installed previously, that's why I don't know what happened.
Thanks,
David