Database Info

noob in need of help sorry to break the rules =/

i am a real noob =/!!!! i have a htc sensation, s off with clock work recovery, i have recently been trying to use i.c.s. i tried super cid-ing with i thought had worked but didn't, so i downloaded a zip file to upgrade my firmware, flashed the zip but it said it failed. so i just wiped and restored my old rom. a good few hrs later my sensation decided to fart so i did a battery pull to find my phone booting into h boot with a white screen with and unpacked zip file. i unpacked and rebooted now im stuck in a boot loop can any one please help ???? want my phone back

bootanimation loop? You really did a wipe? sounds like you forget it.
Just wipe it and flash again. Just to be certain, also wipe dalvik cache.
Otherwise your backup is meaby corrupt or something, I already had some corrupt backups with clockworkmod. For your original rom, do nandroid backup with aw amon ra recovery. That is saver.

Assuming that your backup is not corrupt, follow this guide
Do you want to go back to Gingerbread?
You need to flash the proper firmware Hboot 1.17.
If you are superCID'ed: Download it HERE. (Thanks to ziggy1001 for the firmware package)
If you are not superCID'ed: Download the corresponding file according to your cid and mid HERE. (Thanks to Kohr-Ah for the User-Friendly Firmware)
Follow the same steps you've followed to upgrade the firmware, but this time with the Hboot 1.17 PG58IMG.zip file.
Flash superwipe script for sensation
Flash Gingerbread ROM
Flash recommended radio
Or you can just restore your Gingerbread NANDROID backup, if you have one, AFTER downgrading the firmware and flashing the radio.
Click to expand...
Click to collapse
You need the correct firmware and radio for your ROM. Alternatively, you could use that guide to try upgrading to ICS again.

yes always wipe b4 restrore or new flash just to make sure there is no conflictin files, have tried all that but it goes back into boot loop. tried flashing the rom i had first. just bootloop then when i go back to recovery there just this update. im guessing from the firm ware zip that didnt work. thanks for the help guys its doin my head in

Just to make sure, you removed the PG58IMG.zip from your SD card, right?

so if i take it of it will sort it self out???

Yes! It should. You definitely need to remove that zip.
From the same guide that I linked to before:
Remove the sd card from the phone
Hold volume-down + power to boot into bootloader.
Wait 10 seconds until the bootloader is fully loaded
Now your bootloader screen should read:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07M
Insert the sd card now
Connect your phone to the PC via USB
Navigate with the volume button and select recovery with the power button
Wait for the recovery to boot
Select -Toggle usb storage-
Phone is now connected in USB storage mode
Delete the PG58IMG.zip file from the sd card in you computer
Select disconnect
Press back to return to the main screen of 4ext recovery
You are good to go, continue to the Flashing the ROM section.
Click to expand...
Click to collapse

Safe, thank you very much will crack on with it and let you know how it goes. Thank you again.

thank ou very much, have sorted the boot loop, have flashed with miui but its keeps restarting it self =/ why is this ????

you mean it Starts up fine, then after some given amount of time it restarts? Or during booting?

yes that is what i mean sorry. goin to flash back to my old rom.

If you can boot it, and actually use the phone for some amount of time, then it reboots randomly. Sounds like a Rom, or undervolt issue. Maybe try a Different Rom

Thanks all for your help, have flashed a new Rom and really happy with it. Gonna leave it alone so I dont break it again

Glad to hear that
Sent from my Inspire 4G using xda premium

You and my girlfriend pmsl

[Q] Paranoid noob question regarding S-off and previous Bootloader

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much

fashofasho said:
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
when you did S-OFF in order to install Cyanogen JB first you had to flash the latest fw version and then the rom
the rom you tried to install requires the latest fw version
now are you still s-off?
what is now your hboot version?
what is your fw version?

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
i got confused
.i think your answer is going for fashofasho

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
Thanks for the reply. Okay so here is where I am currently at. I haven't done anything since I reflashed stock ROM throguh RUU after the fail cyanogen flash. On this stock ROM whenever I load into bootloader it still says s-off 1.17 but I did lose my clockworkmod. So according to your instructions I should either clockworkmod again or 4ext now, that's okay right? If so, going to flash firmware then cyanogen!! Or is there a problem that I have s-off but not recovery.
P.s. there is no point in running revolutionary and have it s-off again when I already have it right, just thought it might be necessary to make things fresh

If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app

Skipjacks said:
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?

fashofasho said:
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
Click to expand...
Click to collapse
flash su-2.3.6.3-ef-signed.zip first and then install 4ext recovery

You're over engineering this. You don't need to root your current ROM first. That's an extra step since you're s-off.
If you are s-off it's really simple to get 4EXT recovery.
First, download this and put it on the root directory of your SD Card (meaning not in a folder, just on the SD Card. Do not rename it)
http://d-h.st/qnm
I got this download link from here...
http://forum.xda-developers.com/showthread.php?p=21989107
Click Thanks for Joaquinf in that thread. He made the 4EXT zip that's flashable through the bootloader.
That is 4EXT made into a zip file that's flashable via the bootloader, which you can do when you are S-off.
So put that file on the SD card, power the phone off, pull the battery out for a second and put it back in (this stops fastboot so you can get back to the bootloader). Then hold volume down and power at the same time. You have to hit both buttons at the same time. If it goes to the splash screen, pull the battery and try again.
When the bootloader loads up it will immediately find the PM58IMG.zip file. It will ask you if you want to install the update. Say yes by hitting volume up I think (it will tell you how to say yes)
Put the phone down and don't touch it until it tells you it's done. Should just take a second. But seriously don't touch it. Leave it alone.
If that works, you've just flashed 4EXT. You can check it by pulling the SD card out (so it doesn't try to flash the PM58IMG again) and rebooting to the bootloader and selecting 'recovery' from the menu. 4EXT should boot up.
This entire process so far shouldn't take more than 3 minutes total. It just sounds like a lot.
To see this detailed out by someone else in case you want to check what I'm saying, read steps 4 and 5 of the first post in this thread.
http://forum.xda-developers.com/showpost.php?p=21989063&postcount=1
Give the author 'thanks' again because he's awesome and deserves it.
Now you've got 4EXT installed. Great. You're 1/3rd of the way home.
Now you need to update your firmware. Delete the PM58IMG.zip file you used to flash 4EXT off the SD card (use a card reader or boot the phone up and delete it, whatever works. You can also use 4EXT as a card reader now too by choosing USB storage from inside 4EXT. It will give you access toteh SD card on your computer now)
Now get new Firmware from this thread.
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
try the 3.33 firmware universal. First download link in post 2 of the thread above.
CHECK THE MD5 SUM!!!! I'M NOT PLAYING AROUND HERE!!! You are worried about bricking your phone, this is where you can do it if the firmware .zip is bad.
Put that PM58IMG file on your SD and flash it in the bootloader the same way you flashed 4EXT recovery a minute ago. (If you're still in 4EXT recovery you can use it's power menu to reboot into bootloader easily.)
This will take a minute. The phone will shut off and go black in the middle of this process. Your heart will skip a beat. Relax. It'll come back on. Again, put the phone down and walk away while it does it's thing and don't touch it until it says it's done.
Delete the PM58IMG file from your SD card.
You are now 2/3 of the way there. Your phone WILL NOT boot up right now because your ROM is not compatible with your firmware. Relax. That's supposed to happen.
Now you can flash CM10. Make sure you have the CM10.zip file on your SD card nad GApps. (Bruce has Gapps in his downloads page). Delete the PM58IMG firmware file from your SD card (that's important)
Pull the battery again so you can get back into bootloader. Get into bootloader (power + volume down)
Select Recovery
4EXT should boot up.
Go to the Wipe menu. Wipe all partitions except SD card. (Old ROM is now gone)
Go back to the main menu.
Install from SD
Find the CM10.zip file you should have downloaded and put onto the SD card. Flash it.
This will take about 3 minutes. 4EXT will flash it and ask if you want to reboot. You do not yet. Not you need to flash Gapps the same way you flashed the ROM.
When that's done, now you can reboot. You shoudl see the CyanogenMod boot animation after the splash screen. Give it a few minutes to boot up this first time. Once it boots, set it up the way you like it. If you enjoy it, donate a few bucks to the developer, Bruce.
You don't have to root CM10. It's already rooted when you boot it up the first time.

[OTA Help] I updated my device - Now says "Recovery Verified Failed"

Hi guys,
My tablet is rooted (and back to fully stock ROM from Acer's website). I updated OTA just a moment ago, and I was totally shocked to see the message "Booting kernal recovery image - Recovery verified failed..."
I tried rebooting, fastbooting,....they all don't work. How should I move on? What can be done now?
Please do help me. I need the tablet, and never knew such a situation could arise.
Thanks!

Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?

got the same problem. how do you get into fastboot again?

Liquidator said:
Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?
Click to expand...
Click to collapse
I assume yes, it is locked since I went back to a fully Stock ROM (which includes the locked bootloader?). But what has a bootloader got to do with an OTA update?
What I mean by they all don't work is that, even when I try shutting down, rebooting or enter stock recovery using the volume keys + power button, nothing works. Absolutely nothing! The screen just stays there.
I then thought, let the battery run down and maybe I can enter stock recovery and flash the zip for the stock ROM again from my SD card, but this doesn't work. The tablet just boots again to that same screen, with a message saying wiping off update cache and something to do with cdm.
I fear my device is gone. If anyone can lead me to getting back my device up and running, as a small token of appreciation, I will provide you with either $10 via PayPal or a $10 Google Play Gift Card code. This is really important for me, and I can't seem to find any help on this matter on the Internet.

I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.

Temporeiches said:
I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.
Click to expand...
Click to collapse
No, we don't have a same problem. I don't have CWM on my device, and I am doing an OTA. I can do absolutely NOTHING other than stare at the error message in red ink and the static Acer logo.

Okay sorry. Just want to tell you that I flashed the stock rom and so I lost CWM. If i find a way to fix mine ill tell you and it might help you.

As an update, after letting the tablets battery drain out and then charging it back up, the message I am seeing now is a little longer:
Erasing cache before SD update...
SD Update cmd: recovery
--Update_package=sdcard:update.zip
Booting recovery kernal image
Recovery verified failed...
PS: If anyone can make sense of this message, please tell me.

If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.

Liquidator said:
If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.
Click to expand...
Click to collapse
So how do I get this latest firmware? I can't find on acers website.

himmatsj said:
So how do I get this latest firmware? I can't find on acers website.
Click to expand...
Click to collapse
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update

Temporeiches said:
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update
Click to expand...
Click to collapse
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!

himmatsj said:
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!
Click to expand...
Click to collapse
Try this:
Here's how to get into fastboot (bootloader) manually:
Turn off your tablet
Hold the Volume Down (**) button and press the Power button
As soon as the tablet vibrates, let go of only the Power button (keep the Volume Down (**) button pressed) and immediately start switching the Screen Rotation Lock slider back and forth.
If this works continue.Connect your device to PC. Open your device manager look for fastboot under other devices and right click on it and select update driver. Then click browse my computer for driver software and locate the folder i could send by mail, just ask me. Click Next, and it might say it is a threat, but click continue (its safe as I edited it myself) and let it install. Next download http://forum.xda-developers.com/showthread.php?t=1661324 and use it to unlock bootloader. Next follow instructions on http://forum.xda-developers.com/showthread.php?t=1866378 Then place a ROM from NoThrills on an external sdcard, and insert it into the tablet. If the tablet is shut down get into CWM through the key combination for ICS bootloader power and ** sound button and for JB bootloader
* PowerON+Vol-
* At the first vibration release PowerOn, keeping Vol- pressed
* At the second vibration release Vol- and press Vol+
Next flash the rom from external sdcard and reboot. Now things should work.

Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.

himmatsj said:
Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.
Click to expand...
Click to collapse
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.

malos1984 said:
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.
Click to expand...
Click to collapse
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)

himmatsj said:
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)
Click to expand...
Click to collapse
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.

malos1984 said:
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.
Click to expand...
Click to collapse
Yeah, I hope someone who is directly involved in these things like NoThrills can come and enlighten us.

Thread moved to Q&A
MD

Problem SOLVED!
Hi guys,
For all those having the "recovery verification failed" error while trying to do OTA, I know the fix!
The key is, you need to restore stock recovery manually. There's a zip file of the stock recovery here (at the bottom of the first post). Just restore stock recovery as per usual.
Steps to follow in brief:
1) Install stock recovery manually from HERE
2) If your's isn't the stock Acer ROM, download the correct ICS version for your region from HERE (place it as update.zip and follow steps as per normal to flash)
3) Go to settings>apps>all apps>systemupdater, and then clear data/cache.
4) Reboot tablet and you should get an OTA notification.
5) You're done!

[Q] My HTC One S has no OS - SOLVED

When trying to restore/unroot my One S something bad happened. I'm not sure, but I or the program I tried to use somehow erased the memory and completely removed the phone OS. What should I do to get my phone back to life?
EDIT:
My phone is back to life!
The solution that worked was a mixture of a few previously posted on xda.
I followed this tutorial: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing
Under ROM flashing I did steps 4-7 and then flashed the boot.img for my chosen Rom(Currently UTB: http://www.connect-utb.com/utb-rom-for-the-htc-one-s/) via CMD. Then I powered down, waited for a bit, and started the phone again. The phone finally worked as it was supposed, I got past boot image and entered the normal phone configuration.
The reason I chose UTB Rom was because someone else have had positive results with this Rom
(http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 post #8),
which also proved correctly for me as I tried to install another Rom without success just a few mins later. (To get it to work again I followed my own instructions above, and it worked)
Thanks for your help! And I hope this solution will guide and help others with similar problem in the future!
-Heart

HeartOfFart said:
When trying to restore/unroot my One S something bad happened. I'm not sure, but I or the program I tried to use somehow erased the memory and completely removed the phone OS. What should I do to get my phone back to life?
Click to expand...
Click to collapse
Hello,
If you can get to the bootloader then you should relock it and flash the RUU for your phone. That will return it to stock and you can reroot or do whatever.
Rsotbiemrptson

You could also just reflash the ROM of your choice by going into TWRP custom recovery, mounting your sd card and copying the ROM over.
Then flash the ROM, and dont forget to also fastboot the relevant boot.img for that rom.
TWRP recovery is better than CW as it does allow you to mount your sd card. So download TWRP (google it) and fastboot flash recovery <filename>.img
then load the recovery then mount sd card. You should be good to go from there, unless your SD Card is corrupted. If that is the case, then check http://forum.xda-developers.com/showthread.php?t=2086156

Rsotbiemrptson said:
Hello,
If you can get to the bootloader then you should relock it and flash the RUU for your phone. That will return it to stock and you can reroot or do whatever.
Rsotbiemrptson
Click to expand...
Click to collapse
Yes, I can get into bootloader, but can't find the right RUU for my version.

Thanks guys, it's awesome that you help me!
Didn't find the correct RUU, so I get an error..
The other method posted will be tried out tomorrow!

AKToronto said:
You could also just reflash the ROM of your choice by going into TWRP custom recovery, mounting your sd card and copying the ROM over.
Then flash the ROM, and dont forget to also fastboot the relevant boot.img for that rom.
TWRP recovery is better than CW as it does allow you to mount your sd card. So download TWRP (google it) and fastboot flash recovery <filename>.img
then load the recovery then mount sd card. You should be good to go from there, unless your SD Card is corrupted. If that is the case, then check http://forum.xda-developers.com/showthread.php?t=2086156
Click to expand...
Click to collapse
I'm trying, but it doesn't work for me. Will give some more effort into this tomorrow. Does anyone have a good way to find the right RUU?

Android Revolution HD 7.3

Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain

Cainsmoker said:
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Click to expand...
Click to collapse
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?

rzr86 said:
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
Click to expand...
Click to collapse
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?

Cainsmoker said:
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Click to expand...
Click to collapse
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)

The speedy reply is much appreciated.
I'll go ahead and update the firmware and see where that lands me. I figured it could have been a problem from the get go but in the original thread for the HD 7.3 Rom the firmware link has been removed (likely since it was from 2011)
Thanks for the point in the right direction Rzr, and I'll let you know how it goes!
rzr86 said:
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
Click to expand...
Click to collapse

Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?

Cainsmoker said:
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Click to expand...
Click to collapse
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done

rzr86 said:
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
Click to expand...
Click to collapse
With the phone being in a boot loop I can't get it detected by my computer to remove/add anything from the SD card. I do have the HD 7.3 ROM on and the Gapps that's required but it never makes it past the "beats audio" splash screen. I have no idea what's going on with it but will try any suggestions you've got up your sleeve.

Ahhhhh....I've gotten a fix for this!
I was unable to do anything because of the update zip which wanted me to update every time bootloader was initiated. By keeping my case off I removed my SD card to be able to boot in recovery and then put the SD card back in to load the HD 7.3 zip from the card. This seemed to take care of the problem.
Thanks for the help Rzr