right
i am going to have send my a100 back. the touchscreen issue is driving me nuts and i cant keep it in its crrent state. i am shipping it back to the retailer for a full refund rather than pay to ship it back to acer. at the end of the day i cant be doing with the hassle. so i need to know how i go about unrooting it and locking the boot loader back up and basically restoring it to stock.
i will have a read of the forums but with work being all rather busy and a deadline for return i am a little pushed for time so if anyone out there knows and would be kind enough to link me to a thread or simply tell me that would be appreciated.
cheers
You could flash stock boot loader and flash an official ota
sent from your future.
das_webos_transformer said:
You could flash stock boot loader and flash an official ota
sent from your future.
Click to expand...
Click to collapse
If hes just rooted just run the ota it'll do boot loader too. He didn't mention a custom rom or recovery, but if he does then doing it in that order will lock it up. Stock recovery then stock rom then bootloader last. Basically stock recovery > ota then you're fine.
Tapatalked from my Galaxy S II.
hey guys thanks for the replies.
ok sorry i should have said i have unlocked the boot loader rooted it and instaled twrp recovery. i never got round to putting a rom on it (i have only had it about 6 or 7 days), i removed root by accident when i wiped it but obviously the unlocked bootloader and recovery remained. so with this in mind then exactly what would i do?
flash stock rom>flash stock bootloader?
would that also remove recovery?
edit sorry i didnt remove root when i wiped it i merely lost the superuser app so i am actually still rooted.
rockmonkey1973 said:
hey guys thanks for the replies.
ok sorry i should have said i have unlocked the boot loader rooted it and instaled twrp recovery. i never got round to putting a rom on it (i have only had it about 6 or 7 days), i removed root by accident when i wiped it but obviously the unlocked bootloader and recovery remained. so with this in mind then exactly what would i do?
flash stock rom>flash stock bootloader?
would that also remove recovery?
edit sorry i didnt remove root when i wiped it i merely lost the superuser app so i am actually still rooted.
Click to expand...
Click to collapse
Root occurs in system, which isn't affected by wipes, so yeah SU is still there, just the app to control it is gone, which you discovered already.
As you have twrp, unlocked a200 bootloader but stock rom, the process is pretty simple.
Get the ics ota, name it update.zip place it on the root of the external sd card, no folders.
Power on holding volume - (closes to lock switch) and press power for 3 seconds, once the text starts up in the upper left corner, let everything go.
Should install stock rom, which will do the following:
1 wipe cache
2 flash new rom system
3 "flash" a100 bootloader
4 reboot into android
5 flash over twrp and place stock recovery in place
This will all occur on it's own once you get it loading up update.zip
5 only happens if it boots and is completely stock with /system/etc/install-recovery.sh intact.
3 can happen as long as it uses the update.zip
2 can fail, if it does but proceeds to flash bootloader twrp will be locked out, however a stock rooted rom as you have will still boot, and we can cover replacing the recovery with stock at that point if needed.
1 always happens, regardless of any other steps being met or finished.
mate thanks for helping here. i had to fix my phone which died after a bad flash of a back up in cwm... long story wont go into it... but it did eat up a good one or two days. so i havent gotten round to sorting anything out here with the tablet.
now i am going to try to flash the build prop and install one or two roms. flex reapers and cm10 all look good and i am hoping that that combination with maybe with over clocked kernal will be enough to fix the screen problem.
now i know it is unlikely if it is a hardware fault but i need to try because i would like to keep this tablet and the place i got it from havent got any more. it was pretty inexpensive at 127 pounds and i will be unlikely to find any other store that has stock at that price so if it goes back it goes back for good. hence me wanting to try to keep it.
so i am gonna flash the roms and the build prop now. if it doesnt fix it then i will be back for a little help in reverting it back to stock. by the way where can i find the ota ics release?
i will have a look on the forum i am sure it has to be here somewhere but just in case!!!
edit: got them edit no i havent i cant download them? the site is offline... anywhere else they can be gotten from? maybe acers website? will check now. just realised i have the stock rom installed! will make a back up now.
http://forum.xda-developers.com/showthread.php?t=1307046
so you reckon it could be as simple as simply flashing the official rom to take the tablet all the way back to stock including the locking of the bootloader and removing the recovery? that would be nice and simple and easy which will be a real welcome change from the norm. fingers crossed that is all that is needed.
To go stock that is all that's needed. In vaches thread there is one decrypted on a drop box, that's our only one unless vache brings his stuff back online.
Well there is the service ROM which will be stock, but not what is supposed to be there. At first glance its stock though. Wouldn't suggest it for a return.
Tapatalked from my Galaxy S II.
ok this post was confusing. i am running stock ics at the moment. the bootlaoder is unlocked i have root and the recovery is twrp.
so i have downloaded the update found in the drop box folder here.
http://forum.xda-developers.com/showthread.php?t=1307046
it was already called update and it has a zip extension. so it is update.zip.
i have put it in both mnt/external_sd/ and also /sdcard/ none of them work.
all i get when i hold the volume and power button is taken into twrp recovery.
i thought it flashed automatically? can i flash it through recovery? bit worried about doing that because if it removes recovery while it is flashing i will be screwed.
will wait here now until someone can confirm what i am doing wrong because i cant afford to brick it.
i can be a bit to smart for my own good at times.
could the problem be that i am already running the latest ics official release? should i flash a custom rom? just throwing out some ideas here because i aint got a clue why it hasnt worked.
anyone know? i need to ship this back to the retaler tomorrow and i would prefer not to do it with an unlocked bootloader and custom recovery.
things is i am stumped because i thought i had done all that should be needed to flash the update and the only thing i can think of is because the firmware is up to date (possibly even newer than the update.zip) it wont update.
rockmonkey1973 said:
anyone know? i need to ship this back to the retaler tomorrow and i would prefer not to do it with an unlocked bootloader and custom recovery.
things is i am stumped because i thought i had done all that should be needed to flash the update and the only thing i can think of is because the firmware is up to date (possibly even newer than the update.zip) it wont update.
Click to expand...
Click to collapse
In that case flash the stock recovery and run the bootloader for a100 that came in the unlock boot loader zip. Run the a100 script instead of the a200 script, that will lock it. Do this after stock recovery flashing.
Or, put back install-recovery.sh and reboot, that will replace the stock recovery then run the a100 boot loader script. You'll still be rooted but try update.zip again after stock recovery and boot loader are done.
Tapatalked from my Galaxy S II.
pio_masaki said:
In that case flash the stock recovery and run the bootloader for a100 that came in the unlock boot loader zip. Run the a100 script instead of the a200 script, that will lock it. Do this after stock recovery flashing.
Or, put back install-recovery.sh and reboot, that will replace the stock recovery then run the a100 boot loader script. You'll still be rooted but try update.zip again after stock recovery and boot loader are done.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
mate you have been incredibly helpful. i mean seriously.
i will do as you suggest however i have a question how am i supposed to flash these files? do i do it through recovery? please dont say adb because i have never used that program dont know why i just tended to stay away from it zips and nandroids always seemed so much easier.
i have edited this post due to being slightly confused and thought it best to save the gushing praise until after the tab is stock! sorry mate i hate being a pain and i am reading all i can on locking the bootloader but there doesnt seem to be any guide i can follow. most of the threads i have found are for bricks and my tab is certainly not beicked... and i want it to stay that way.
rockmonkey1973 said:
mate you have been incredibly helpful. i mean seriously.
i will do as you suggest however i have a question how am i supposed to flash these files? do i do it through recovery? please dont say adb because i have never used that program dont know why i just tended to stay away from it zips and nandroids always seemed so much easier.
i have edited this post due to being slightly confused and thought it best to save the gushing praise until after the tab is stock! sorry mate i hate being a pain and i am reading all i can on locking the bootloader but there doesnt seem to be any guide i can follow. most of the threads i have found are for bricks and my tab is certainly not beicked... and i want it to stay that way.
Click to expand...
Click to collapse
Well....adb. You used it before with the scripts to unlock the boot loader.
http://forum.xda-developers.com/showthread.php?p=23868002
Right above the download it mentions running the a100 script to revert to locked a100 boot loader.
Only do this with a stock ROM installed!
After that it'll be manually installing the recovery with fast boot or replace the stock /system/etc/install-recovry.sh
If it was just renamed, then name it back. If it was deleted it'll need replaced, it will revert to stock recovery on its own after booting with it in place.
Tapatalked from my Kindle Fire - Jellytime AOSP
thanks again my friend. funny i never realised i was flashing stuff with adb when i was doing things like that!
i always thought adb was a command line interface like say ssh and that you needed to use some sort of software like putty.
anyways just to bring this to a close. i never got time to flash it back to stock. i simply left the official ota on and reset it. have already received the refund so all is good. shame i am unlucky with tablets. i had a faulty archos 80 g9 and then this. guess i will hold off for a while maybe until i feel my luck has changed for the better.
cheers again mate.
Related
Super long story short, handshake between 3G/4G wasn't wokring on 4.4.4 Liquid on Toro gnex so i used This guide to revert back to the highest stock build and try a different rom. Since i had the newest bootloader already installed, i didn't flash it.
Everything worked great, booted fine. I wanted to then get CWM installed. While getting to the bootloader, i noticed its the stock bootloader, or what looks to be stock. And now ADB cannot talk to my phone, thus no CWM, thus no root, thus no other roms to install. What do i do?
crap
Oh ****, looks like i dont' know anything about anything. I read somewhere i needed to hold down and power to get to the bootloader. When i did that i brought me to that unfamilure screen that said 'odin' at the top.
When i held up and down and power, it brought me to my original bootloader - the one i didn't flash. So how the **** are there 2 of them and how bad is this?
iceman845 said:
Oh ****, looks like i dont' know anything about anything. I read somewhere i needed to hold down and power to get to the bootloader. When i did that i brought me to that unfamilure screen that said 'odin' at the top.
When i held up and down and power, it brought me to my original bootloader - the one i didn't flash. So how the **** are there 2 of them and how bad is this?
Click to expand...
Click to collapse
LOL
Dude chill out your phone is acting completely normal.
Even when using a custom rom you retain the original bootloader.
ADB is not supposed to work from within the bootloader.
You need to use Fastboot to flash a custom recovery from the bootloader screen.
Once you have a custom recovery you can flash a ROM.
So Google how to fastboot a recovery onto your device.
The Odin screen that you saw can be used along side the Odin program to return your device to stock if you wish to do so.
roger
DR3W5K1 said:
LOL
Dude chill out your phone is acting completely normal.
Even when using a custom rom you retain the original bootloader.
ADB is not supposed to work from within the bootloader.
You need to use Fastboot to flash a custom recovery from the bootloader screen.
Once you have a custom recovery you can flash a ROM.
So Google how to fastboot a recovery onto your device.
The Odin screen that you saw can be used along side the Odin program to return your device to stock if you wish to do so.
Click to expand...
Click to collapse
Thanks for the info. I ended up getting an odd red exclamation mark during startup to the updated bootloader. Restarted and got stock up and running. Reflashed to slimkat, and finally my radios are working correctly. Cheers
So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.
You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.
Yeah that's what I did yesterday thanks for the response!
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
iSike said:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
Click to expand...
Click to collapse
Open SuperSU->Settings->Unroot?
j to the 4n said:
Open SuperSU->Settings->Unroot?
Click to expand...
Click to collapse
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
iSike said:
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
Click to expand...
Click to collapse
When I unrooted using SuperSu it ruined my installation also. I was stuck in a bootloop until I installed TWRP and reinstalled SuperSu, terrible!!! It eventually unrooted and I relocked bootloader but nothing worked so I was forced to root and unlock bootloader again.
I am wondering though, how did you return to stock? I really want the latest AT&T stock but when I install that RUU .exe it gives me error 155 so I can't install it. I was using 1.32 stock AT&T and wanted to install 2.6 (I think that's what it is, it's Android 5.1).
I am S-On, and not S-off, could that be an issue? Bootloader is unlocked and I am rooted now.
You know how u r supposed to rename the ruu u want to flash (assuming you downloaded the stock ruu for your carrier and device). The problem for me was, I could never connect my device thought adb after I rooted it (fast boot worked when I put it in fastboot). Even when I could give a command , it could never load the ruu. So what I did, was right click the ruu and click run as admin. It should open up a page on the top saying something about a ruu/rom utility. Make sure you device is connected and had usb debugging( before you got stuck in the loop hopefully). Now click accept and all that good stuff on the utility, it should scan your phone and show u your current rom image, and then show you the latest rom image. Click update and it will boot your phone to boot loader and begin sending it to your phone. IMPORTANT: DO NOT TOUCH YOUR PHONE. Now here's the catch, if it said it failed or something about a USB error, close the program and start it up again. If your phone is stuck without the download bar moving(displayed on your phone), you are going to have to hard reset it. Google how to do it for your device (just a button holding combination). And start the program again. It will take a couple times for the program to work (mine took about 5-6 times). But it will work sooner or later. I am not home atm, but when I get home, I will find the link to the page where this info is displayed in a more orderly fashion and with pictures. It will be tonight, probably about 9 hours. Try this though, if it is too confusing, wait till I post the link. Good Luck!!
EDIT: Sorry just got back home from a long day haha, I'll be sure to look for the link tomorrow. But my directions above should be good, give it a try.
Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!
butneveragain said:
Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!
Click to expand...
Click to collapse
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!
butneveragain said:
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!
Click to expand...
Click to collapse
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!
xunholyx said:
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!
Click to expand...
Click to collapse
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?
butneveragain said:
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?
Click to expand...
Click to collapse
No it's not a problem, and something that I have already assumed.
If you were S-Off, you wouldn't need to re-lock your bootloader before running the RUU.exe
Those "some people who were saying" are incorrect.
butneveragain said:
I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them.
Click to expand...
Click to collapse
Yeah, people need to stop saying that. Its completely false. RUU is an official HTC recovery tool, and its intended to work on stock (s-on) devices.
You only need s-off to flash RUU as unintended by HTC, such as:
- flash an older version RUU than what is on the phone ("downgrade")
- Change CID/MID to flash another version's RUU
- Flash RUU with unlocked bootloader
- Flash a hacked/unsigned RUU
xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
My phone is stuck on boot screen... How can I turn off the device if my vol+ button does not work?
First, let me start off by saying I'm an idiot; my phone was stuck in a bootloop and out of panic I tried to fix the problem and only made it worse. Now I'm left with no OS installed and I'm stuck at my custom recovery.
I am using twrp as my custom recovery and I'm able to use my mac to send files successfully to my phone. The problem arises when I try to flash the zip and I am prompted with the message that says that the file is corrupted. I tried installing multiple zip files onto my phone and when returning it to stock did not work I even tried to flash Cyanogen Mod. Each time I was greeted with the same message.
This sucks because I just bought my nexus 5x and I don't want to lose it to a stupid mistake. If anyone could help in anyway that would be amazing. If not I will still accept prayers for my potentially dead phone.
-Carlos
Edit: problem solved. I did what you guys said and returned to stock and didn't panic. Thanks so much.
you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot
Giorgos Chatziioannou said:
you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot
Click to expand...
Click to collapse
Yeah as said above there is no need for panic.
Even if your recovery wont flash the zips you can flash the stock factory images via fastboot manually (i dont now if its available on mac if not boot a linux live disk).
And if your bootloader is still locked unlock it reboot to bootloader and then flash the images.
By the way you should provide more information such as os details twrp version bootloader state and so on...:fingers-crossed: