[TUT][CDMA]ROM randomly rebooting? Here are some fixes! (BACK IN BUSINESS!!! :D) - HTC One V

NOTE: This one's a big one if you can't tell! Everyone give a round of applause to simonsimons34 for tracking down the issue. What does this mean? Well, there may not be a need to ever downgrade using the RUU. If you go here (you really can't miss that big, bolded "here"), you will see that he determined the issue is caused by:
a bad battery driver function in the kernel
Click to expand...
Click to collapse
He also took the liberty of building a kernel compatible with 4.2 and putting in a commit for fixing the kernel to work with the newer radio at GitHub. Any ROM builders who see this, please do check it out. As far as everything goes, I haven't personally tested it but I do always encourage people to try it out. Simon has been a great supporter and kernel builder for our device so I have faith that he hath found the Holy Grail. 'Course my thread will have no more existential purpose, BUT it is a great resource so as it is, I will leave it up for the general perusal of the community. Have a great week everybody and I look forward to a new flood of development.
Exciting news y'all! This thread has been stickied! [Hopefully] this will allow continued support and growth of the thread. My personal philosophy is that anything I post shouldn't be locked down to what I know or believe in, so I encourage any reader to put forth their input. What does that mean? It means that if you have a suggestion, by all means inbox me your thoughts. I'm open to continual development of this tutorial through community teamwork. Have a good day everyone!
-------------------------------------------------------------------------------------------------------
Here are some common reasons why your phone will randomly reboot (bootloop). You should only use an RUU (the methods below the "=" signs) if NOTHING ELSE WORKS (because the RUU does a factory wipe of the phone).
Common Problems:
I switched from another ROM and now my phone keeps rebooting...
There are several factors in play here. The commonly accepted fix is backing up your data and doing a full wipe (cache, dalvik cache, system, data) followed by reflashing your ROM.
I upgraded my ROM from blah blah version to blah blah version (ex. 4.0.x to 4.1.x)...
This is because your old Ice Cream Sandwich system stuff may not be compatible with JellyBean (in the case of the example). Wipe system and the caches (dalvik & cache) followed by reflashing your ROM.
I upgraded my ROM (within the same version) and it keeps rebooting...
Every time I upgrade my ROM, I wipe cache. If something funky happens, just wipe system and reflash your ROM.
I flashed a ROM and it won't boot at all...
Either you flashed a ROM for a different device, you flashed a kernel for another device, OR you didn't flash a kernel at all. Make sure everything is for your phone (the HTC One V on Virgin Mobile is the CDMA version known as "PrimoC" whereas the GSM version is the "PrimoU").
=============================
NOTE: This guide is for the One V!
I know the feeling! You're all excited because you just unlocked your One V's bootloader, flashed a recovery, and flashed a steamin' hot new ROM. You boot up for the first time and get ecstatic, the tension building as you put in your Gmail info. You finish the start up but OH NO!!! Your phone reboots! You blame yourself... you blame your cat... you blame your wife... you blame the war in the Middle East. You think, I must've done something wrong! Stupid, stupid, stupid! Don't fret! Take my experience with this quite seriously (despite the jokes). For 2 weeks, I retraced my steps and tried EVERYTHING! I thought it was just the ROM's problem, so I flashed one after another to the same end. Finally, I decided to post a new thread asking for help. Nothing became of the first thread, so I posted a second one. To my great relief, along trotted Curiousn00b. After shoving me in the correct direction, I figured out the rest. A big thanks by the way, Curiousn00b! The following is the method that I used to get my phone to finally run a ROM. Also, a thanks to CafeKampuchia for the quoted directions below.
A few things to make sure you have:
Windows (with Administrator's priveleges)
Fastboot installed and working
Your phone (duh!)
A USB cable
Time and patience
The following quote is from CafeKampuchia's thread over here.
NOTE ABOUT THE FOLLOWING PARAGRAPH: jmztaylor's site is now legally able to host the RUUs again so the download link is right here*
In support of jmztaylor and all of his work for this device, I have decided to also include his website in this thread... *here is the download directory for the HTC One (Primo) device RUUs. I'm not sure if this bug effects other Primo devices, so this especially pertains to the PrimoC (HTC One V CDMA). Thanks jmz for the tip!
Solution #1
CafeKampuchia said:
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thus far you should have the stock recovery back and be bootlocked again. Now, back in fastboot mode, you should already be connected to your computer via USB (if you disconnected, just reconnect it and wait for "FASTBOOT" to change to "FASTBOOT USB")
Run this command:
Code:
fastboot oem rebootRUU
Next, start up the RUU program again and let it run through without interruption. After this process is done, the phone should boot up to the stock ROM. Let it do its thing, but this time don't do the OTA update. From here, just unlock the bootloader again, install your recovery of choice, and install your ROM of choice or reroot the stock ROM (I know some want to keep it stock).
As also pointed out by RoyalYeo, you can let HBOOT take care of the problem:
Solution #2
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse
My personal solution (Solution #1) is the more technical side of things and also exposes you to the nitty-gritty. Having said this, #1 is quite touchy because if you do something wrong, there is a good chance that you could... well uh, brick your phone to be quite honest. On the other hand, #1 requires no SD card (given the event that your SD card won't mount, your SD reader is broken, or you just plain don't have an SD card). Ultimately, the choice is up to you.

y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665

cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Won't work if the ota is already applied from the factory.

cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
You need to downgrade your radios or your guide will be useless no matter what, i followed this post i found on android forums and it worked
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse

robaho said:
Won't work if the ota is already applied from the factory.
Click to expand...
Click to collapse
Or if you applied the OTA via the popup window saying, "Blah, blah, blah, new update available."

Thank you so much for this. I will try it when I get home. Ever since I applied that OTA battery update, I haven't been able to successfully run any other ROM that I have tried. Hopefully this will be the solution that I have been looking for.
Just out of curiosity though, I have a Nandroid backup of before I applied the OTA Rom. If I restore that backup, would that do the same thing as you provide here, or would I definitely have to go through this process?

Won't work. The radio partition cannot be backed up/restored unless you have an s-off device.

Why not point to htcruu.com no premium acct necessary or wait times
Sent from my One X using xda premium

Moved to General section.

I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.

mastertr said:
I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.
Click to expand...
Click to collapse
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...

mastertr said:
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...
Click to expand...
Click to collapse
Did you relock the bootloader before or after flashing PK76IMG.zip? This does make a difference. My suggestion is just to go back through and try again following everything to a tee. Doesn't always work the first time.

I went with your first solution this time and followed the directions step-by-step and it was a success. I am now running AOKP 10 without any boot loop. Thanks!

Bump

It worked thank you
thanks man followed your guide and boom everything went just fine.
1st i had 1 minute problem. now i dont have any.
i confirm that anybody having 1 minute problem can solve it with this tutorial:laugh::laugh::laugh::laugh::laugh:
thanks

Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA

BobbaLouie said:
Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA
Click to expand...
Click to collapse
check ur version
settigs->about >software version

Is the Sprint RUU the one that works on Virgin Mobile?

Euler MD said:
Is the Sprint RUU the one that works on Virgin Mobile?
Click to expand...
Click to collapse
Yes
Sent from my One V using xda app-developers app

Thankyou for this guide. Even though I followed the steps, it didn't work. Maybe it was just my luck but I'll try again soon.

Related

[Q] Root help:"Main version older"

Hey ive been trying to root my evo all day it is on version 2.1-update1. I was able to root my brothers perfectly fine using the downloads and tutorial from the idiot-proof guide to rooting by thebiles. But on mine I get stuck right at the beginning, when i try to flash the PC36IMG my bootloader says main version older. I feel like ive tried everything if anyone can help I'd reallly appreciate it thanks.
Try simple root, and keep trying. I got that same error even with simple root on my buddies 3 times before it worked. Don't know why. Maybe try copying the pc36img to the sd card instead of letting simple root push it...gl!
I agree with the simple root approach. Not trying to highjack your post but I have a question back at you if I may. You say you have one root EVO and one not root? If so the the root has PRI 1.34 and the nonroot 1.40? Could you perhaps do a data speed comparison on these and post the results? I am real curious...
sorry man i saw your post like 2 minutes too late the simpleroot worked right before i refreshed this page thanks for the help though guys appreciate it
one more quick question while PC36IMG was flashing the 2nd "tp" file said bypassed next to it rather than OK like all the others and the first tp had a blank next to it...is this a problem i should look into before unlocking the nand and all that other good stuff?
No problem glad you got it working. This was kinda like going to the casino...getting up to go to the bathroom...coming back to see someone hit the jackpot on your machine....hahaha!!!
That is normal....mine did that.
thanks man appreciate it...one more question for anyone that can help, im using the idiot proof guide and im on step 56 but when i try to enter the adb shell i get an error from command prompt saying "error: more than one device and emulator" i entered the shell perfectly fine like 2 steps before that and used it to flash the new pc36img rom but now i get this error to enter shell again how do i fix this error?
Okay I came here thinking this might finally be it... but nope I tried all the solutions mentioned here but to no avail. I am frustrated and still getting the main version is older. Does anyone know what is causing this error. Please I'm using usb debugging I wiped and backed my SD and have ota that came out in June. I installed Microsoft net frame and htc drivers. I updated simple root and the update log said this was to fix the error but still getting the same error. Any suggestions
I have the same issue, pretty much have tried everything with no luck, kind bummed at the moment, hope someone can help
Thanks
I got to work FINALLY!!!!!
So finally i got the main version error older NO MORE. So i decided to share what i did in hopes that it will work for all of you frustrated out there.
1) Download simple root from xda forum, dont download it anywhere else. The first time i tried i downloaded it at another android forum and even though it may seem the same, this version for some reason was not pushing the files as it suppose to. So again download from forum. Search for it on XDA.
2) Be patient and prepare yourself.
3) Make sure you on the 147 ota version. Not froyo. or before any version before ota because you can use old simple root.
4) After you download it extract it to a folder. Choose whatever location suits you i like desktop so i can delete file after i use it and keep zip. Be sure to update the program. Open it and let it search for downlaod or go to root folder and search for the updater.
5) Before running the program check the obvious. Is usb debugging enable, Do i have microsoft netframe, Are my phone drivers correct. Is the usb cable correctly connected to my computer and phone. Did i choose charge only when connected to the computer.
6) Now on your phone, and this step did it for me, go to Settings>SDandPhoneStorage>FactoryDataReset. Brace yourself this will wipe data it will not change your version. But if you want do a backup the folder of your contacts and whatever you have in your SD card, this is the time to do so. Mount as disk drive, and remember to change back to CHARGE ONLY. I skipped this because rooting was more important than my girlfriends phone number.
7) Now youre noobiness is ready connect phone double check Step 5. In case you missed something.
8) Run the simple root downloaded from XDA forum. Wait for it to push files is wont take long but me patient. Think of it passing 180mb to sd card so it takes some time.
9) Phone will reboot in a screen with skating androids Push power button and WAIT. It will find file and you shouldnt be getting "main version older" reboot error you where getting if you paid close attention to detail. Now update push volume up.
10) Why so impatient wait for it to update files. Once its down just push volume up for reboot. First time it reboots after root or when u flash a rom it usually takes longer, enough to get u nervous but dont be WAIT.
11) Easy sailing now but youre not done yet. Hit recovery once your phone reboot. Choose the method you want i chose Clockwork it works just fine for flashing roms.
12) Congrats your fully root and can flash that cool rom youve been reading about. Suggestions: DamageControl or Cyanogen but go ahead and try whichever you like.
13) YOURE DONE WOOF
If for some reason, it happened to me with AvaFroyo, when you flash your rom it goes on a loop and keeps rebooting dont panic that is what the recovery is for just put your microSD on a card reader delete the rom that is giving you problem and place another one and Reflash. Read how to flash rom you have to wipe on Recovery menu everytime you flash a different rom.
I hope this helps...Its in plain english not Dev English so...

[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.

I can’t delete apps and I can’t reset my phone

For Gizmoe first time post, thanks for your info I found it with a google search, I was trying to follow your suggestion to FiFa_JockeR, but HTC does not have my phone on their web site. Can you please try to help me reset my phone somehow?
I have a HTC Incredible (ADR6300) and I just want to start over with this phone. Verizon stores no help, HTC customer service no help. They try to do what I’ve done already, “a factory reset”. But it just does not reset! with or without the SD card. This all started with the force closes on a few apps. Then I thought I would delete allot of apps just for the heck of it, then I ran into another problem. I can delete an app(s) while the phone is on but when the phone is rebooted or turned off then on again the deleted app(s) reappears. So I can’t delete apps and I can’t reset my phone. It’s exactly the same as FiFa_JockeR (just like the pictures) only we have different phones from HTC. PS phone has never been rooted.
http://forum.xda-developers.com/showthread.php?t=1458066&page=2
For screen shots(the pictures) see first part of this thread. http://forum.xda-developers.com/showthread.php?t=1458066
Then I tried this
http://forum.xda-developers.com/showthread.php?t=2215233
I downloaded and flashed? I put it on my formatted SD card and it loaded
I was excited because things were loading in hboot the file PB31IMG.zip
“Flash latest ruu thru hboot: http://dinc.does-it.net/Stock_Images...15/PB31IMG.zip”
anyway
now it takes about 4 minutes to get past the eye portion of the bootup, then I get “sorry the application bla bla bla has stopped unexpectedly.
please try again. this happens to what must be every app on my phone.
even if I go to settings I get the same thing “sorry the application.........
I just don’t know what to do.
I think the post by cmlusco on Re: [Q] Return to stock might be what I need but I really don’t understand it. I only downloaded the last file because I thought it was all I needed.
any help would be greatly appreciated.
and cmlusco thank you for your Post
ps guess you figured out I’m a nube
sorry if I’m not posting in the right place.
HTC Incredible (ADR6300) said:
For Gizmoe first time post, thanks for your info I found it with a google search, I was trying to follow your suggestion to FiFa_JockeR, but HTC does not have my phone on their web site. Can you please try to help me reset my phone somehow?
I have a HTC Incredible (ADR6300) and I just want to start over with this phone. Verizon stores no help, HTC customer service no help. They try to do what I’ve done already, “a factory reset”. But it just does not reset! with or without the SD card. This all started with the force closes on a few apps. Then I thought I would delete allot of apps just for the heck of it, then I ran into another problem. I can delete an app(s) while the phone is on but when the phone is rebooted or turned off then on again the deleted app(s) reappears. So I can’t delete apps and I can’t reset my phone. It’s exactly the same as FiFa_JockeR (just like the pictures) only we have different phones from HTC. PS phone has never been rooted.
http://forum.xda-developers.com/showthread.php?t=1458066&page=2
Then I tried this
http://forum.xda-developers.com/showthread.php?t=2215233
I downloaded and flashed? I put it on my formatted SD card and it loaded
I was excited because things were loading in hboot the file PB31IMG.zip
“Flash latest ruu thru hboot: http://dinc.does-it.net/Stock_Images...15/PB31IMG.zip”
anyway
now it takes about 4 minutes to get past the eye portion of the bootup, then I get “sorry the application bla bla bla has stopped unexpectedly.
please try again. this happens to what must be every app on my phone.
even if I go to settings I get the same thing “sorry the application.........
I just don’t know what to do.
I think the post by cmlusco on Re: [Q] Return to stock might be what I need but I really don’t understand it. I only downloaded the last file because I thought it was all I needed.
any help would be greatly appreciated.
and cmlusco thank you for your Post
ps guess you figured out I’m a nube
sorry if I’m not posting in the right place.
Click to expand...
Click to collapse
The incredible (ADR6300) is on the www.htcdev.com/bootloader unlocker site, under HTC Droid Incredible *. Best bet is to unlock and flash a recovery, then from recovery do a full wipe. That is if it lets you, i have a feeling you will get errors formating both /data and /cache. If so its pretty much unfixable. There is a mod http://forum.xda-developers.com/showthread.php?t=2175346, that will mount /data and /cache to seperate partitions on your sdcard. This makes the phone a little slower, especially booting. But a slow phone is better than no phone, if you cant get a new one. If you need any help just post back.
Does this mean I'm rooting my phone?
cmlusco said:
The incredible (ADR6300) is on the www.htcdev.com/bootloader unlocker site, under HTC Droid Incredible *. Best bet is to unlock and flash a recovery, then from recovery do a full wipe. That is if it lets you, i have a feeling you will get errors formating both /data and /cache. If so its pretty much unfixable. There is a mod http://forum.xda-developers.com/showthread.php?t=2175346, that will mount /data and /cache to seperate partitions on your sdcard. This makes the phone a little slower, especially booting. But a slow phone is better than no phone, if you cant get a new one. If you need any help just post back.
Click to expand...
Click to collapse
Does this mean I'm rooting my phone?
Will I be putting myself at higher risk of Radio Frequency?
I appreciate the time you’ve put aside to respond to me. Thank you
I will try to follow your directions and will let you know what happens.
I’m at the HTCdev site and reading up on how to do the unlocking.
Thanks
HTC Incredible (ADR6300) said:
Does this mean I'm rooting my phone?
Will I be putting myself at higher risk of Radio Frequency?
I appreciate the time you’ve put aside to respond to me. Thank you
I will try to follow your directions and will let you know what happens.
I’m at the HTCdev site and reading up on how to do the unlocking.
Thanks
Click to expand...
Click to collapse
Yes you are rooting your phone. Im not sure what you mean by higher risk of radio frequency? If your on hboot 1.02 or 1.07, you can skip the ruu bootloader update part of the htcdev site and proceed to the next step.
yes I have 1.07 so I can skip the ruu bootloader update
cmlusco said:
Yes you are rooting your phone. Im not sure what you mean by higher risk of radio frequency? If your on hboot 1.02 or 1.07, you can skip the ruu bootloader update part of the htcdev site and proceed to the next step.
Click to expand...
Click to collapse
oops radio frequency I meant SAR values, and I don’t expect an answer for that. I read the attached paragraph on the HTC site and got concerned.
PS this phone is used for Wi-Fi only, no data plan.
Anyway back to the good stuff.
I’m attaching a picture of my hboot screen, so yes I have 1.07 so I can skip the ruu bootloader update part but I’m unsure how to proceed from here. Am I still rooting my phone? what’s next? I’m really nube at all of this. Will I be returning to the HTC site or somewhere else?
Thanks again for your time.
HTC Incredible (ADR6300) said:
oops radio frequency I meant SAR values, and I don’t expect an answer for that. I read the attached paragraph on the HTC site and got concerned.
PS this phone is used for Wi-Fi only, no data plan.
Anyway back to the good stuff.
I’m attaching a picture of my hboot screen, so yes I have 1.07 so I can skip the ruu bootloader update part but I’m unsure how to proceed from here. Am I still rooting my phone? what’s next? I’m really nube at all of this. Will I be returning to the HTC site or somewhere else?
Thanks again for your time.
Click to expand...
Click to collapse
At the bottom of the ruu update page there should be a proceed / continue button. Click on that and it should move on to having you get an identifier code from your phone, to send to htc.
At the bottom of the ruu update page
cmlusco said:
At the bottom of the ruu update page there should be a proceed / continue button. Click on that and it should move on to having you get an identifier code from your phone, to send to htc.
Click to expand...
Click to collapse
The ruu update page can you attach a link? I’m not sure where that is or what I am doing, What am I doing now flashing rom?
I don't even know what that means. If I’m doing it from the computer or from my SD card. Can you please clarify?
I read your post about using, “There is a mod http://forum.xda-developers.com/show....php?t=2175346”, on the SD card”. Simply Amazing
Thanks
HTC Incredible (ADR6300) said:
The ruu update page can you attach a link? I’m not sure where that is or what I am doing, What am I doing now flashing rom?
I don't even know what that means. If I’m doing it from the computer or from my SD card. Can you please clarify?
I read your post about using, “There is a mod http://forum.xda-developers.com/show....php?t=2175346”, on the SD card”. Simply Amazing
Thanks
Click to expand...
Click to collapse
And this is exactly why you need to read, and learn.
If You're New to Modding/Rooting, Read This First!
HTC Incredible (ADR6300) said:
The ruu update page can you attach a link? I’m not sure where that is or what I am doing, What am I doing now flashing rom?
I don't even know what that means. If I’m doing it from the computer or from my SD card. Can you please clarify?
I read your post about using, “There is a mod http://forum.xda-developers.com/show....php?t=2175346”, on the SD card”. Simply Amazing
Thanks
Click to expand...
Click to collapse
It seems that htc has removed the ruu bootloader update part of the unlock process. Probably because the latest ota should make everyone have an unlockable hboot already. So just do all the steps 1 - 10.
You are not flashing a rom, at least not yet. A rom is basicly an opperating system like windows.
Right now you are getting an identifier token from your phone which you submit to htc in step 10. They will email you back another code with instructions, which you will enter into the phone using hboot and a cmd prompt on your pc.
Just follow all those steps on htcdev and then we will go from there. In your spare time you should read up on rooting and roms and custom recoveries, so that you have some clue of how your phones going to work once were done.
Here I am at HTCdev
cmlusco said:
It seems that htc has removed the ruu bootloader update part of the unlock process. Probably because the latest ota should make everyone have an unlockable hboot already. So just do all the steps 1 - 10.
You are not flashing a rom, at least not yet. A rom is basicly an opperating system like windows.
Right now you are getting an identifier token from your phone which you submit to htc in step 10. They will email you back another code with instructions, which you will enter into the phone using hboot and a cmd prompt on your pc.
Just follow all those steps on htcdev and then we will go from there. In your spare time you should read up on rooting and roms and custom recoveries, so that you have some clue of how your phones going to work once were done.
Click to expand...
Click to collapse
Well here I am at HTCdev trying to do step 1, I Select my Device and click Begin Unlock Bootloader. Then I get this dialog box, “Do you wish to continue?” I click yes and nothing happens, I wait, and wait, then click no and it responds by going back to the prior page where you select your device. So I tried selecting other devices and none of them work, sounds like a problem on their site. So I’m at a stand still maybe you can try it and see if step 1 will work for you? by the way I only see 5 steps,like the Attached Thumbnail I uploaded in post #3. also must be a common problem for htcdev just google htcdev and see the results of autocomplete (Thumbnail).
Update 4/29/13: I think I found the 10 steps, checkout this video.
http://www.youtube.com/watch?v=iyRxI15CUnA
This is what i'm trying to do right?,he recommends getting SDK tools too, is this what I should do? In taking your advice to read up on... I googled "rooting and roms and custom recoveries" that's how I found the video.
Unfortunately I still get the same result at the HTCdev site, can you please see if you have the same issue I do at the HTCdev site?
Thanks
Token Submitted Successfully!
Here we go
I had to use Firefox browser instead of windows Internet Explorer 8
Now just waiting for the email
:good:
Drivers from SDK Manager?
HTC Incredible (ADR6300) said:
Here we go
I had to use Firefox browser instead of windows Internet Explorer 8
Now just waiting for the email
:good:
Click to expand...
Click to collapse
Update to my last post. had to use a different email account in order to receive the unlock bootloader key file.
so now I have it, now and I think I need driver(s) because when the phone is in hboot and I plug it in to the computer via usb cable, the task bar shows Installing device driver software, but a couple of seconds later shows Device driver software was not successfully installed. Tried goggling around and found this http://androidforums.com/incredible-all-things-root/171178-64-bit-android-usb-drivers.html
I also have a Windows 7 64-bit system and not sure how to extract them out of the SDK Manager.
HTC Incredible (ADR6300) said:
Update to my last post. had to use a different email account in order to receive the unlock bootloader key file.
so now I have it, now and I think I need driver(s) because when the phone is in hboot and I plug it in to the computer via usb cable, the task bar shows Installing device driver software, but a couple of seconds later shows Device driver software was not successfully installed. Tried goggling around and found this http://androidforums.com/incredible-all-things-root/171178-64-bit-android-usb-drivers.html
I also have a Windows 7 64-bit system and not sure how to extract them out of the SDK Manager.
Click to expand...
Click to collapse
Here you go follow this http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install.
I'm ready for the next step
cmlusco said:
Here you go follow this http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install.
Click to expand...
Click to collapse
I'm ready to flash a recovery, then from recovery do a full wipe. That is if it lets me.
Thank you:good:
HTC Incredible (ADR6300) said:
I'm ready to flash a recovery, then from recovery do a full wipe. That is if it lets me.
Thank you:good:
Click to expand...
Click to collapse
Any luck?
I need your help to get the right recovery
cmlusco said:
Any luck?
Click to expand...
Click to collapse
No, I need your help with link(s) to where I need to go to get the right recovery like you did for the driver(s). Bam done.
http://www.youtube.com/watch?v=XvazQUYG1kE
I don't want to waste time guessing things and messing up stuff with problematic recovery's. I need one that works even for the novice. I want to get my phone up and running. It's amazing I've come this far.
Thanks to you of course.
I could really use your guidance.
Thanks
HTC Incredible (ADR6300) said:
No, I need your help with link(s) to where I need to go to get the right recovery like you did for the driver(s). Bam done.
http://www.youtube.com/watch?v=XvazQUYG1kE
I don't want to waste time guessing things and messing up stuff with problematic recovery's. I need one that works even for the novice. I want to get my phone up and running. It's amazing I've come this far.
Thanks to you of course.
I could really use your guidance.
Thanks
Click to expand...
Click to collapse
Download this http://dinc.does-it.net/Recoveries/TWRP_2.5.0.0/recovery.img to your pc and place it in the same folder as fastboot.exe and the unlock_code.bin. Put the phone in fastboot mode. Open a cmd prompt in your pc and type
Code:
fastboot flash recovery recovery.img
You should now have twrp recovery installed. To get to it pull the battery, reinsert, and then hold vol down and power untill hboot comes up. Then navigate to recovery and select it. Once in recovery select wipe and then advanced and select everything except sdcard and emmc, then swipe the bar to start the wipe. We will go from there depending on what happens.
Ready for the next step.
cmlusco said:
Download this http://dinc.does-it.net/Recoveries/TWRP_2.5.0.0/recovery.img to your pc and place it in the same folder as fastboot.exe and the unlock_code.bin. Put the phone in fastboot mode. Open a cmd prompt in your pc and type
Code:
fastboot flash recovery recovery.img
You should now have twrp recovery installed. To get to it pull the battery, reinsert, and then hold vol down and power untill hboot comes up. Then navigate to recovery and select it. Once in recovery select wipe and then advanced and select everything except sdcard and emmc, then swipe the bar to start the wipe. We will go from there depending on what happens.
Click to expand...
Click to collapse
Ready for the next step.
I'm attaching pictures of what has happened, worked flawless, excellent instructions, brief and concise. Bam!
Thank you :good:
PS just a note,for now I have not had a SD card installed.
HTC Incredible (ADR6300) said:
Ready for the next step.
I'm attaching pictures of what has happened, worked flawless, excellent instructions, brief and concise. Bam!
Thank you :good:
PS just a note,for now I have not had a SD card installed.
Click to expand...
Click to collapse
Well it looks like everything wiped ok, your partitions are probably fine. So you can just flash a rom of your choosing. Check out the dev section, there are tons of roms there including stock rooted roms if you want to keep the original feel.
Should I install SuperSU?
cmlusco said:
Well it looks like everything wiped ok, your partitions are probably fine. So you can just flash a rom of your choosing. Check out the dev section, there are tons of roms there including stock rooted roms if you want to keep the original feel.
Click to expand...
Click to collapse
1 first screen HTC Incredible
2 teamwin loading screen
3 teamwin main screen, to shut down, I tap reboot
4 at the Reboot Menu I select Power Off then....
5 No OS Installed, “Are you sure you wish to continue” and I Swipe to Power Off.
6 Then I see Install SuperSU, which Roots phone. Should I do this?
Should I install SuperSU?, I tap Do Not Install because I’m not sure what to do.
I want to install the operating system you have or a stock version, Touch Of Blue V3.0
At the dev site I was looking at kernel is that the same as rom?
Can you please guide me with links, let me know which way we are going and how to do it.
Thanks

[Q] Constant crashes/reboots

I have suddenly developed a problem with my DHD. As soon as it connects the network via WCDMA/(3G) it crashes. I can use GSM without any problems. If Mobile data is enable, then that works with 'G' over icon. I have already done a restore to last April and a system reset, but neither made any difference. I have also tried different SIM and SD cards. It started by occasionally crashing with Maps running, and it got quite hot. It would be OK after 4-6 restarts, but now as soon as it tries to connect it crashes.
I am in the UK in SW and mobile coverage is very patchy. There is no 3G at home and only GSM in some rooms.
The phone is unlocked, but with S-on. I have ClockworkMod recovery running, and the system is:
Standard 2.3.5
Kernel 2.6.35.10-g931a37e (Nov 2011)
Sense 3.0
Software 3.12.405.1 with CL199157 release key
Radio 12.65.60.29U_26.14.04.28_M
Any help would be appreciated. I am beggining to think it's a hardware/motherboard problem
Thanks
I think it's a rom problem
Gussta said:
I think it's a rom problem
Click to expand...
Click to collapse
But it is the original ROM, and I get the same after a restore to 12 months ago, and a Factory Restore.
Thanks for the comment.
Factory reset sometimes is not enough.
Try flash it again.
Gussta said:
Factory reset sometimes is not enough.
Try flash it again.
Click to expand...
Click to collapse
A bit more ifo from the Log:
The "Sent to HTC" log file shows this error e.g.
[SMD]ARM9 has CRASHED
[SMD]smem: DIAG '[WCDMA]
07:17:25 FATAL: rrc (rrccsp.c:08982) Failure adding acq. entry in CSP substrate %d (irq0)
Restarting Linux...
I shall try a reflash next.
Thanks
Ratsea said:
A bit more ifo from the Log:
The "Sent to HTC" log file shows this error e.g.
[SMD]ARM9 has CRASHED
[SMD]smem: DIAG '[WCDMA]
07:17:25 FATAL: rrc (rrccsp.c:08982) Failure adding acq. entry in CSP substrate %d (irq0)
Restarting Linux...
I shall try a reflash next.
Thanks
Click to expand...
Click to collapse
I found this thread: http://forum.cyanogenmod.com/topic/50801-random-reboots-2/
It's supposed to be a problem with some version of GB (UK) rom.
If flashing rom, get you the same error you can try use aahk to get S-off on your device, and after that you can flash WWE ROM (it's a standard world wide rom witch allways work the best).
Here's the link of shiped roms: http://www.androidruu.com/?developer=Ace
And if u get s-off you can use this rom: http://forum.xda-developers.com/showthread.php?t=1382235
In first thread that I send you some one said that it can be problem with battery. Try if u have the same problem when you charging it.
P.S.: I have remember now that my friend has the sam problem when he try to use the camera with flash on (even if battery was charged more than half), and when he raplace the battery, everything work fine.
I am a bit confused as I didn't think I needed S-Off to update ROM, provided I manually flashed the boot.img file. I have moved away from AAHK as it is no long supported if you get into trouble.
This problem is curious as it only started a week ago after a trip to Morroco, and curiously there is an identical problem report on the Vodafone forum after a trip to Morroco (see forum-dot-vodafone.co.uk/t5/HTC/WDCMA-Fatal-error-boot-loop/td-p/1605342). No solution though.
I shall have a go at a new ROM, and report the outcome.
Thanks for the help.
Ratsea said:
I am a bit confused as I didn't think I needed S-Off to update ROM, provided I manually flashed the boot.img file. I have moved away from AAHK as it is no long supported if you get into trouble.
This problem is curious as it only started a week ago after a trip to Morroco, and curiously there is an identical problem report on the Vodafone forum after a trip to Morroco (see forum-dot-vodafone.co.uk/t5/HTC/WDCMA-Fatal-error-boot-loop/td-p/1605342). No solution though.
I shall have a go at a new ROM, and report the outcome.
Thanks for the help.
Click to expand...
Click to collapse
If you have stock ROM you can flash it only with stock rom provided with your carrier
With unlocked hboot, with S-off or with goldcard you can flash with other carrier.
In my opinion the best way is always S-off and stock rooted wwe rom.
With this solution when ever you get some problem or birck you can fix it because you have all premissions.
Unlocking hboot with HTC dev is the worst way. People report to many bugs.
About aahk, you can get when ever you want suport for it, here on this forum.
Or you can use AAHK2 by Phiber2000: http://forum.xda-developers.com/showthread.php?t=2367322
Did you try with full battery and mobile phone connected to ac adapter to see if you have the same problem?
This is quick hard work - I have Window 8.1 and I can't get the PC to see the DHD in CMD/Fastboot, so I am a bit stuck. It can't enumerate the device..
HTC Sync works and I have the latest drivers etc. AAHK2 says it can see the DHD whilst it is switched on, but in the bootload, it fails.
I shall have to find a Win7 pc, as it did work when I rooted and unlocked the DHD.
Ratsea said:
This is quick hard work - I have Window 8.1 and I can't get the PC to see the DHD in CMD/Fastboot, so I am a bit stuck. It can't enumerate the device..
HTC Sync works and I have the latest drivers etc. AAHK2 says it can see the DHD whilst it is switched on, but in the bootload, it fails.
I shall have to find a Win7 pc, as it did work when I rooted and unlocked the DHD.
Click to expand...
Click to collapse
Did you try something like?:
http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-81/
or
http://forum.xda-developers.com/showthread.php?t=2596698
Gussta said:
Did you try something like?:
I did look, but there are x64, and I am x86, so 32 bit. I think it should be working OK
Click to expand...
Click to collapse
Ratsea said:
Gussta said:
Did you try something like?:
I did look, but there are x64, and I am x86, so 32 bit. I think it should be working OK
Click to expand...
Click to collapse
Did you try first to go in fastboot with HTC sync opened that he first try to install driver propperly for that mode.
I think I have had the same problem even in WIN 7 x86
Click to expand...
Click to collapse
Gussta said:
Ratsea said:
Did you try first to go in fastboot with HTC sync opened that he first try to install driver propperly for that mode.
I think I have had the same problem even in WIN 7 x86
Click to expand...
Click to collapse
I didn't think this would get so complicated!! I have fired up an old Vista PC, and updated the drivers from the AAHK2 post. They would not install - error reading transform location - so I downloaded the lastest HTC version 4.1.0.1. and used them instead.
I can run 'fastboot getvar all' on a CMD window, no problem, but...... if I try with AAHK2.cmd, it starts, and clears some old stuff, then says, NO phone connected. The phone is in bootloader/fastboot usb mode (in red). I guess its still a driver problem.
This is a dumb question, but I assume the phone should be in Bootloader mode, as I did try the script aahk2.cmd with the phone just running normally, and it did see it and proceeded to the next menu - it suggested option 'h' for HTCDev unlocked phone.
Click to expand...
Click to collapse
Your hboot is: locked, unlocked, relocked?
What it's say in hboot?
Gussta said:
Your hboot is: locked, unlocked, relocked?
What it's say in hboot?
Click to expand...
Click to collapse
unlocked,
If I start it AAHK2 with phone normally on, it starts Ok, It want to download an RUU - I have already done this but maybe have put it in the right place. Should it be on the SD card somewhere (PD98IMG-Xgb.zip)?
Ratsea said:
unlocked,
If I start it AAHK2 with phone normally on, it starts Ok, It want to download an RUU - I have already done this but maybe have put it in the right place. Should it be on the SD card somewhere (PD98IMG-Xgb.zip)?
Click to expand...
Click to collapse
I never use AAHK2.
I only use the AAHK but i think it isn't much difrent.
You can:
when you go in fastboot type: fastboot oem lock
boot in rom
In aahk when you first time download PD98img-GB2.zip it allways stay somwhere in first folder of unziped aahk
after you boot in rom, run aahk2 and if you relocked hboot just press "1" instead of "h".
When I get home I will download AAHK2 and open the script to see what's the difrent's between.
Same Problem!
Hi
I think i have the same problem... I got back from a trip to Morocco last week... my DHD worked fine while over there, but started rebooting as soon as i turned Airplane mode off when landing back in the UK.
It can turn on for periods, and seems very stable when i disable the radio (turning on airplane mode, or removing the SIM). I think it's crashing whenever it searches for a network (regular reboots while driving, but not when sitting at my desk). I can force a reboot by searching for a new network in the settings. Are these symptoms the same as yours?
It's a 3 year old Orange DHD, using the stock build (not rooted yet).
I'd love to know if you get any more clues to your problem.
Ratsea said:
I am a bit confused as I didn't think I needed S-Off to update ROM, provided I manually flashed the boot.img file. I have moved away from AAHK as it is no long supported if you get into trouble.
This problem is curious as it only started a week ago after a trip to Morroco, and curiously there is an identical problem report on the Vodafone forum after a trip to Morroco (see forum-dot-vodafone.co.uk/t5/HTC/WDCMA-Fatal-error-boot-loop/td-p/1605342). No solution though.
I shall have a go at a new ROM, and report the outcome.
Thanks for the help.
Click to expand...
Click to collapse
FlaminDave said:
Hi
I think i have the same problem... I got back from a trip to Morocco last week... my DHD worked fine while over there, but started rebooting as soon as i turned Airplane mode off when landing back in the UK.
It can turn on for periods, and seems very stable when i disable the radio (turning on airplane mode, or removing the SIM). I think it's crashing whenever it searches for a network (regular reboots while driving, but not when sitting at my desk). I can force a reboot by searching for a new network in the settings. Are these symptoms the same as yours?
I'd love to know if you get any more clues to your problem.
Click to expand...
Click to collapse
Hi, and yes pretty much. I have found that if you set the phone to GSM only, it fixes the reboots (as does airplane mode too), and data is still received over 3G if available.
It is very curious about Morocco though. We were in Marrakech for about 5 days, and used the Maps on the phone (offline mode) a lot. I also saw another vodafone report too dated July 2013, so something is happening.
I have now managed to run AAHK2 and rooted and S-Offed the phone, so I shall be trying some other ROMs. I have tried KitKat, but in kept freezing.
Good luck.
Gussta said:
I never use AAHK2.
When I get home I will download AAHK2 and open the script to see what's the difrent's between.
Click to expand...
Click to collapse
Thanks for you patience, I have finally run the AAHK2 script, and after another couple of driver problems, and a failed flash, got it running.
The drivers are different for 2.3.5 vs 2.3.3, so that confused Vista.
Ratsea said:
Hi, and yes pretty much. I have found that if you set the phone to GSM only, it fixes the reboots (as does airplane mode too), and data is still received over 3G if available.
It is very curious about Morocco though. We were in Marrakech for about 5 days, and used the Maps on the phone (offline mode) a lot. I also saw another vodafone report too dated July 2013, so something is happening.
I have now managed to run AAHK2 and rooted and S-Offed the phone, so I shall be trying some other ROMs. I have tried KitKat, but in kept freezing.
Good luck.
Click to expand...
Click to collapse
Ratsea said:
Thanks for you patience, I have finally run the AAHK2 script, and after another couple of driver problems, and a failed flash, got it running.
The drivers are different for 2.3.5 vs 2.3.3, so that confused Vista.
Click to expand...
Click to collapse
Yesterday I stayed long at work so I didn't try anything. Congratulations for success with AAHK2.
If you install kitkat or any other custom rom, before installing you have to do a factory reset from recovery mode, flash new rom, flash boot.img via fastboot: fastboot flash boot boot.img, after that go to recovery mode: factory reset, wipe all cach, wipe dalvik, and everything you can wipe, and reboot.
After that it should work fine. But take in consideration that in all that custom rom always something don't work.
For first testing I suggest that you install stock rooted rom from this thread:
http://forum.xda-developers.com/showthread.php?t=1382235
And in the first post you have as well radio partition. Flash it necessarily.
P.S.: With stock rooted rom, you will not lose S-off, CWM, etc...

[Q] Galaxy Nexus help

Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Probably drivers. Just manually boot into bootloader.. And then flash the factory image.
Sent from my Galaxy Nexus using xda app-developers app
Fastboot reboot-bootloader command will only work if you are already in the bootloader mode anyways...
As @mrgnex said, just do it manually, or use adb commands to boot into bootloader where THEN you use fastboot command.
To manually get into bootloader/fastboot mode; power down, then hold power button and volume up AND down all at same time for few seconds, it'll vibrate and you'll be in the bootloader mode where u can issue the fastboot commands.
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
You don't actually move the factory images onto your phone.
One of the sticky threads here is called "return to stock". That should guide you in the right direction.
Sent from my Galaxy Nexus using xda app-developers app
huzzug said:
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
Click to expand...
Click to collapse
it's great that you're learning to do this Droid life has a good howto, just google "droidlife how to root galaxy nexus"
if worse comes to worse you can use this toolkit that does it for you, it's called wugfresh google "wugfresh nexus toolkit"
If you want to install ROMs you download the zip right on your device (make sure you get a ROM zip file AND a gapps zip file. They are linked in pretty much every OP for ROMs)
Downloading a ROM zip directly from/on device is easiest because then you do not have to transfer the file(s) over to your device in order to "flash"(aka install). Then all you do is go into recovery mode. Then go to install, then choose your ROM zip file. After that installs, then install gapps file the same way, always install gapps zip AFTER the rom zip.
If you use TWRP as your custom recovery you can "queue" your zip installs(choose rom zip and then you can choose to add another zip file and it will flash them both for ya)
And usually it is recommend to do a factory reset from recovery before you reboot into system. (Make sure to not wipe ALL /data...choose factory reset...wiping ALL /data will wipe /sdcard contents as well)
This all might seem foreign and difficult at first, but once you've done it once or twice(or more... you might become what we call a "crack flasher"-one who is constant changing ROM and kernel and setups lol, that's when it gets REALLY fun) so do not get discouraged. Especially if you don't understand the terminology we all use, you will become familiar with it quickly. And remember, Google is your best friend, almost any questions you might have will yield MANY helpful results when you put in a Google search, highly recommend that if using Google for trying to get useful info to put things like "how to install custom recovery "Galaxy Nexus" xda" to get the best info possible )
And do not be afraid to ask us either if you feel lost. It's easier to prevent an issue than to fix it(though fixing a borled Gnex is fairly easy with all the tools available here and elsewhere)
As for going back completely to stock, as mentioned above, to do that you aren't putting any files onto your device itself. You download them to PC(I use my laptop) and install from there using fastboot. When you download the factory img that is for your specific device and unzip it (I believe they still come compressed... If not ignore that part sorry!) You will see inside there is a script called "flash-all.sh" OR if using windows use the "flash-all.exe" that will automate the fastboot commands needed for a full factory stock restore of the device.
I could link you to posts containing useful how-tos and info and such, but right now I'm viewing forum via Tapatalk app on my device and really gonna be lazy and just say look at the "Sticky posts" in General, Q&A, and Development sections, those are most likely what I would link to you here.
After reading through some of those, if you need clarification of steps taken or something, come on back and let us know.
huzzug said:
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Click to expand...
Click to collapse
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
SolGoodGuy said:
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
Click to expand...
Click to collapse
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
ashclepdia said:
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
Click to expand...
Click to collapse
I see an optimus G on swappa for $115. Much better phone.
Actually, I ain't in US guys. And whatever I found was a personal preference as I wanted this model and not any other.
Bumpity bump
huzzug said:
Bumpity bump
Click to expand...
Click to collapse
Bump?
Did you ever try what I said?
You need to download the factory img needed and run the flash all script...
Edit::
HERE go to this thread.
http://forum.xda-developers.com/showthread.php?t=2726518
Follow my advice there, except make sure to grab maguro img for your device. Be sure to grab the correct package for your device (takju yakju, etc...it will tell u in bootloader mode which one u have)

Categories

Resources