Develop Bugs

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

[Q] Bricked Evo Help!!!

So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks

Do you have htc sync installed? It won't work unless you have the actual htc sync suite installed. Just google it won't cost you anything. I semi bricked my phone but I fixed it. Maybe some things I done in this thread could help you. Just skim through a few of my posts'.
http://forum.xda-developers.com/showthread.php?t=1100781
Sent from my PC36100 using Tapatalk

lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
My last tip would be to put the phone in fastboot and then run the 3.29 ruu exe. It worked for me, here's the link. Just make sure you have htc sync installed and it's not running when u try to run the ruu (from fastboot in bootloader).
http://goo-inside.me/supersonic/sto...0.09.01_NV_1.77_CNV_release_150224_signed.exe
Sent from my PC36100 using Tapatalk

lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.

lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)

I selected the old one because that one never gives me issues, the 3.30 and 3.70 never work for me
Sent from my PC36100 using Tapatalk

k2buckley said:
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)
Click to expand...
Click to collapse
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?

lokoalex said:
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?
Click to expand...
Click to collapse
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.

A1Lonestar said:
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.
Click to expand...
Click to collapse
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.

lokoalex said:
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.
Click to expand...
Click to collapse
Just make sure that the file is named PC36IMG.zip (exactly that).

Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App

k2buckley said:
Just make sure that the file is named PC36IMG.zip (exactly that).
Click to expand...
Click to collapse
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.

linsalata28 said:
Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My brother is impulsive and he didnt like the fact that it bricked on him. If it was me I would have definitely taken it to sprint.

You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App

linsalata28 said:
You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not a bad idea. Might have to find some of those guys.
k2buckley said:
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.
Click to expand...
Click to collapse
I've been trying man. Im getting nowhere with this. I tried the RUU 3.70 and it just crashed asked me if I wanted to debug. So im gonna try one of the older versions. At least its seeing these with the HTC sync working.

lokoalex said:
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.
Click to expand...
Click to collapse
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.

k2buckley said:
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.
Click to expand...
Click to collapse
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!

Maybe try to update or downgrade your hboot version.
Sent from my PC36100 using XDA App

*Assuming you're working on a windows machine*
Go to this site http://shipped-roms.com/index.php?category=android&model=Supersonic
and download ruu 3.70.
Without your phone connected, run the ruu until it gets to the first dialog box (it should have a checkbox that says "I understand the caution..." blah blah).
With this dialog still open, go to start > run and type "%TEMP%" without quotes.
Inside this folder look for a file called "rom" or "rom.zip" (you are going to have to go through all subfolders) depending on your windows settings (Hide extensions for known file types).
When you find it move it to your desktop and rename it to "PC36IMG" or "PC36IMG.zip" accordingly.
Get a card reader and take your sdcard out of your phone and place it in the card reader. Place the PC36IMG file you renamed on the root of the sdcard. Install your sdcard back into the phone and boot into bootloader. This should scan the card and find the PC36IMG and reinstall a bone stock non-rooted 2.2 rom.
If this method fails, it's possible the nand may have been corrupted in the update process. I'm better at troubleshooting if I have the device with me so this is the best I can do.

lokoalex said:
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!
Click to expand...
Click to collapse
That is frustrating. It sounds like there may be a problem with your current boot.img, and maybe that's why it won't let the RUU re-write the boot.img when it's trying. That would also explain you not being able to boot, because if your bootloader is corrupted somehow, then you won't be able to get anywhere at all. Unfortunately, the bootloader you're on (HBOOT-2.16)isn't downgradeable. I'm starting to suspect that you're getting the bootloader version error because when you run the older RUU, it will try to flash an older version of hboot. Since the version you're on is NOT able to be downgraded, it's probably erroring out when it tries to downgrade, but it can't. I would suspect that if the RUU for the 4.22 software was available and you were able to run that one, then it would succeed. The problem is that you're trying to downgrade, and you can't do that. I'm not sure what went wrong when the OTA was accepted, but it seems like something did, and now you're stuck. I would guess that the only way to fix it would be to reflash the OTA (which you can't because you can't boot), or run the RUU for 4.22, which isn't available yet. My speculations may not be accurate, but that's my guess!

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

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

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.

I Have bricked my htc one m8

Hi all i know someone will not be happy i have asked this question that is probs one of the most asked on here from Nubs like me lol.... Basicly i recently got my rooted htc one m8 S-on back, i was planning to sell it so tried to remove the Root from the phone i have somehow managed to Brick it, its under HTC_001 it didnt have a main fw number so i did what others have and read it from the about software section on my phone wich give me 1.54.401.10....... Well i ended up download that one something went wrong either way now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy.... Sorry for the nub questions i did go abit out of my knowledge people say ADB on other forums, im not very clued up with it other than changing the recoverys ive watched youtube vids ect no joy Please can someone give me a Simple Tut or link to help me ive tried following threads and still got no joy http://forum.xda-developers.com/showthread.php?t=2701376 So now i ask the PRO'S please help lol

mikem2273 said:
Basicly i recently got my rooted htc one m8 S-on back
Click to expand...
Click to collapse
Got it back from where???
mikem2273 said:
Sorry for the nub questions
Click to expand...
Click to collapse
No need to apologize for the n00b questions. However, the huge run-on sentences are another story. Take some time to type a post with proper punctuation and sentence structure. It will make it easier for you to get you point across and for us to help.
mikem2273 said:
now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy....
Click to expand...
Click to collapse
Tried and tried what? If you aren't specific in what you have done, what are we supposed to do, guess? Be detailed and be specific when asking for help.
You aren't in bad shape at all if you have recovery and can mount SD. Just put a software 1.x based ROM on the SD and flash it in TWRP.
---------- Post added at 01:48 PM ---------- Previous post was at 01:42 PM ----------
mikem2273 said:
people say ADB on other forums, im not very clued up with it other than changing the recoverys
Click to expand...
Click to collapse
Just use the XDA search function, and search "adb beginner" to find a number of good adb/fastboot tutorials aimed at just that, beginners.
But if you've used fastboot to install recovery, the other commands aren't any harder. Its just a matter of just knowing what commands to use for a given situation.
If you can mount SD, I don't even think you need adb. But its a very valuable tool to know, and can help in a lot of situations.

Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol

Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol

unable 2 load my one m8 to fasboot
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner

nnamathy said:
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
Click to expand...
Click to collapse
Dude ..who are you talking too ?? your post is useless and makes no sense.
Start your own thread ... post an exact description of what you did and whats wrong along with pictures / bootloader / anything that might be of some help

mikem2273 said:
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Click to expand...
Click to collapse
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Your lack of specificity also makes it crippling to try to help. What stock ROM, and where did you get it from?
If you got a stock nandroid, you then need to extract the files from the zip and place them in exactly the right folder, otherwise TWRP won't see it. And you do not use the TWRP "INSTALL" function with a stock nandroid, you use the "RESTORE" function.
A flashable ROM zip, in contrast to a nandroid, can be placed anywhere on internal storage or removable SD, and TWRP will see it and flash it using the INSTALL function.
Its very easy to push a ROM zip to the phone with adb. I already told you how to find BEGINNER tutorials on how to use adb. Don't expect to be spoonfed information that is already readily available on XDA. If you have a specific question regarding adb, ask it. Otherwise just saying "adb is confusing" is not going to help you.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
mikem2273 said:
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
Click to expand...
Click to collapse
Your firmware files aren't "corrupt". They are just outdated, and don't match the ROM your flashed.
OTAs are available for your version. An option if you don't want to s-off, is to return to stock ROM and recovery, and OTA to update the firmware. It seems you are having problems installing the stock nandroids, but I think you just need to properly follow the instructions from the stock nandroid collection thread.
Otherwise, you are stuck running ROMs that are based on 1.x software. Running anything more recent will result in long boot times and broken WiFI, as you've experienced.

Dammit i know excatly where i went wrong and what you meant by you have to open the file up and adb the right files to the right places............ $%$% i have now fully ruined the phone i think i turn it on i get a White screen the phone then goes full black screen and does nothing...... i have connected the phone via usb to the laptop, the laptop notices the phone and usb i click on the phone in my computer nothing is there when it opens i have also gone onto adb and done the "adb devices" and it does not show on the list, is there anything i can do with this now, i am very gratefull for the help even though i haven't been specific and guessed my way through alot of it like a nob,

adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.

redpoint73 said:
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Click to expand...
Click to collapse
At this point I have to assume it's an inability to communicate clearly, not an unwillingness. You have a lot more patience than most for even trying.

redpoint73 said:
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
Click to expand...
Click to collapse
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Background: Rooted, S-Off (via Sunshine), , TWRP 2.8.1.0, was running CleanROM (on the 444 firmware) and tried installing Vanir 444. I did a factory reset and I'm pretty sure I might have went into Advanced and wiped System as well (from the reading I've done, I shouldn't have done that) ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted. When the phone went to reboot, it went to the usual white HTC screen, then went black and never moved past that point.
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do! If I missed any background or details, let me know and I'll elaborate.
TIA!

sigmaxaa said:
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Click to expand...
Click to collapse
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
sigmaxaa said:
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
Click to expand...
Click to collapse
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
sigmaxaa said:
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Click to expand...
Click to collapse
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
sigmaxaa said:
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do!
Click to expand...
Click to collapse
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.

redpoint73 said:
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
Click to expand...
Click to collapse
Thanks for the reply, I do appreciate it. I was able to get it working (after dozens of attempts) and you're absolutely correct...it's all in the timing.