Did I brick my One S? - HTC One S

Hey guys, so I'm worried I might have bricked my One S, or at least messed it up beyond what I can personally repair.
Basically what happened was that I was trying to install the Auto brightness patch (http://forum.xda-developers.com/showthread.php?t=1638559) onto my One S, because I wasn't happy with the batterly life. Stupidly, I tried to install it without checking accurately for matching RUU version numbers. I thought the Virtuous Ville v1.40 ROM I was running had a 1.78 base, but it has a 1.70 one. Still, I figured that in case anything went wrong, I would just make a nandroid backup and restore. Unfortunately this did not work out so well.
My phone got stuck in a boot loop, so I reset it. When I tried to restore my Nandroid backup, I got an error saying "can't mount /sdcard" or something of the sort. Other Nandroid backups had always worked.
I think before entering recovery, I selected "factory reset" on the HBOOT menu instead of "recovery" by accident. It still loaded into the recovery though, so I wasn't sure what I had actually done. If I did press the wrong thing don't know if that somehow messed up the recovery's access to the SD card.
So now I don't know what to do. I don't mind having to reinstall everything and losing my data, I just want my phone to work. Everytime I try to turn it on it gets stuck in a boot loop, and there doesn't seem to be any way I can access my storage for either nandroid nor installing any roms.
Any help would be immensely appreciated.

Sorry guys, false alarm.
For anyone that's curious, all I had to do to fix my problem was simply reflash CWM recovery(interim touch). Not sure what went wrong, but I think that was that fixed it. Unfortunately I lost all my data and customizations(not sure ifbecause of the factory reset in HBOOT or because I also accidentally clicked on "clear storage" >_>) but since i just got the phone a few days ago and have been installing ROMs very frequently, it's no biggie.
Can a mod close this?

napilopez said:
Sorry guys, false alarm.
For anyone that's curious, all I had to do to fix my problem was simply reflash CWM recovery(interim touch). Not sure what went wrong, but I think that was that fixed it. Unfortunately I lost all my data and customizations(not sure ifbecause of the factory reset in HBOOT or because I also accidentally clicked on "clear storage" >_>) but since i just got the phone a few days ago and have been installing ROMs very frequently, it's no biggie.
Can a mod close this?
Click to expand...
Click to collapse
You shouldn't be using the interim release of the touch recovery anymore.
There is an official release now: Official Touch Recovery
And yes, you lost everything because you did a factory reset... it's all in the name you know... 'factory reset' - does it ring any bells?

I'm having the same problem here. I've tried to fastboot flash alternate recoveries and keep getting the sdcard error. I was trying to install cm9 and now phone won't boot and no sdcard!
Any help would be GREATLY appreciated........

Try this: http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using Tapatalk 2

Related

[Q] Boot loop or Brick? HELP?

GOT IT FIXED
Thanks to fabricatedhero for the brain pulse to try and just root it!
First this isnt my G2X, I am trying to help a co-worker. She isnt Tech-savy by any means... lol... any way here is her story:
She got the OTA pop-up and thought it was a virus (yeah shes that smart) then she said she accepted the update as it kept asking. She started the update and it took hours over night and it never finished she said so she pulled the battery durring the s/w update screen. Then it started the boot loop.
Now my story:
The G2x is bone-stock
I did the NVflash successfully... Flashed the stock recovery via:http://forum.xda-developers.com/showthread.php?t=1056847 ... Still have the boot loop issue and wont boot into recovery. I searched and even Googled and everything is the same, and of which nothign is working for me.
I tried to maybe catch something from the boop loop and also from the S/W update screen... NOTHING... Clearly this is software issue; The only thing I have yet to confirm is if I place the stock update on sd card and see if itll pick that up.
The issue I see there is I cant google for the life of me what the "special" name of the update would be called. Nor do I have a clue what to really call it. I know for most phones its NOT "update.zip" more like "espring13" or somethign like that...
Can any Jedi MAster help me? Thanks!
ok found the file name:
LG-P999-V10f.zip
Still boot-looping and that didnt work...
resources
http://theunlockr.com/2011/05/23/how-to-unroot-the-t-mobile-g2x/
Use. The nvflasher to put Cwm on it and go under restore and re-format sd, cache, and etc
Then go and do gummans froyo 2.2 stock rooted rom
Also there's a post about how to do the GB update on here as well.
Sent from my LG-P999 using XDA Premium App
Did you try a simple factory reset? If you still have stock recovery and rom try holding volume up + power until the reset process begins.
G2X CM7
So I will have to root the device? I guess that makes sense...
Keep in mind I cant get into stock recovery period...
cwm worked! wipped everything, still nothing, gonna flash a new rom
update:
ok SDcard doesnt show have to mount internal storage to apply update... *crosses fingers*
**worked running newest nightly of CM7 with CWM recovery

Htc one s bootloop

Hi iv got a HTC ONE S, it is stuck on boot loop is there any way i can get my pictures and data off my phone? thanks
Can you get into the recovery? And are you running a custom recovery?
If you can get into your recovery(cwm or twrp) you can plug it into usb and mount it as usb storage.
If I helped in any way please hit thanks
Just fix the bootloop. Sounds like you gave up on it. Can you get into the bootloader? Hold volume down and power. Till the device shuts off. Then redo that method and poof. Hboot. If you can. What hboot version are you on?
Sent from my HTC One S using xda app-developers app
I have the same problem, phone keep reboot and will not turn on, i can get into recovery, but can not get contact via USB, what am i doing wrong?
Any step by step how to get out pictures before setting it back to factory settings
recovery loop
Just rooted HTC One S TMOUS using Hasoon 2000's tool. tried CWM backup of rooted stock, then followed instructions for PA 2.52 + gapps. Got stuck on PA boot screen. Won't boot all way up.
Phone will only boot into recovery. adb reboot bootloader goes into recovery. can't get into hboot to restore stock using RUU.
Advice?
Thanks kindly.
Same Problem here.
I wanted to join a wifi-network, then the htc freezed and now it's in bootloop.
I still read some oder threads in the internet but not realy good ideas I like.
Does anyone know whats happening in HBoot when I use "Clear Storage"? Does he clear the phone-memory or the SD-Memory? Or anything else?
Bond246 said:
Same Problem here.
I wanted to join a wifi-network, then the htc freezed and now it's in bootloop.
I still read some oder threads in the internet but not realy good ideas I like.
Does anyone know whats happening in HBoot when I use "Clear Storage"? Does he clear the phone-memory or the SD-Memory? Or anything else?
Click to expand...
Click to collapse
did anyone solve this? I have an unbranded unrooted HTC One S that is also stuck in a bootloop. I was just scanning the WIFI networks from settings and then the phone started looping by itself and only stopped after the battery was empty.
The phone is not modified in any way. I can get into hboot with power-volume down but then what? I don't really feel like doing a factory reset. Is there any other way out? Does the factory reset help?
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Sent from my HTC One S using xda app-developers app
gingi007 said:
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ya seen someone say that not sure if it was you but also some people have found having to many saved hotspots can also send you into a bootloop.
in my case for sure it was the google account cause i did factory reset, and had no saved hotspots and still it happened when i switched the wifi on\off after the factory reset(i mead got into boot-loop and needed a factory reset).
it is a serious bug\problem - i can't believe this can happen because of such a silly configuration.
the OS of HTC is not stabled at all!
If your bootloader is locked, then you dont have too many options re getting information off of your phone. Someone else may be able to post ideas. A factory reset may be your only option..
If you have already unlocked your bootloader, my suggestion would be to flash the latest TWRP Custom Recovery (google it). You can connect to your computer via usb through TWRP and access your sd card to get pictures, videos etc off of it.
Through TWRP you can also have access to adb.exe (ie using adb.exe commands and not just fastboot.exe commands, and thereby access all sorts of adb related commands (backups, linux shell, etc).
In order to actually fix the bootloop, well, usualy I find this is due to issues with the Kernel and custom ROM you are flashing (either one or the other), and so would reflash whatever worked before (ie a previous ROM or previous kernel).
But if this is all happening on a device you have not rooted nor flashed anything custom... Well, then that is a good question!
AKToronto
gingi007 said:
in my case for sure it was the google account cause i did factory reset, and had no saved hotspots and still it happened when i switched the wifi on\off after the factory reset(i mead got into boot-loop and needed a factory reset).
it is a serious bug\problem - i can't believe this can happen because of such a silly configuration.
the OS of HTC is not stabled at all!
Click to expand...
Click to collapse
Ya I'm not saying what you said is wrong or didn't work for you but I do think I could be right about kongo09 and Bond246 issue since it did happen when dealing with wifi and seen a few people say the same thing.
I am in a bootloop. What i did to get the phone start is just press first down volume button then power button (keep holding them until the phone goes oof). Inmediatily when the phone go off, stop pressing anything. ANYTHING, BE FAST, and it will boot normally. I am now tryying to get the stock recovery to avoid this sht.
gingi007 said:
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Click to expand...
Click to collapse
Did the factory reset make you lose all your data? As in: pictures etc? I have read varying stories regarding this, some say you lose it all, some say you don't.
I have some recordings of interviews on there that I really(!!!) cannot lose. Does anyone know if HTC has the possibility to recover files from a phone in this condition?
jazzmijnhv said:
Did the factory reset make you lose all your data? As in: pictures etc? I have read varying stories regarding this, some say you lose it all, some say you don't.
I have some recordings of interviews on there that I really(!!!) cannot lose. Does anyone know if HTC has the possibility to recover files from a phone in this condition?
Click to expand...
Click to collapse
If you unlocked the bootloader then you could flash TWRP which will let you mount SD for the PC.
Darknites said:
If you unlocked the bootloader then you could flash TWRP which will let you mount SD for the PC.
Click to expand...
Click to collapse
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
jazzmijnhv said:
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
Click to expand...
Click to collapse
Not much you can do then because even unlocking could wipe SD.
Not sure if its possible with a locked bootloader but you may want to try getting into your bootloader then try typing fastboot boot <working kernel file>
Replace the phrase "<working kernel file>" with a stock boot.img that you know works.
As you can see this command is different from fastboot flash boot <working kernel file>.
This may get you out of the bootloop if you had kernel issues, and may allow you to load a kernel temporarily. Not sure if it works on locked bootloaders but it might.
If all you can access is the bootloader and fastboot, then you really have to play around with fastboot commands. See http://android-dls.com/wiki/index.php?title=Fastboot for the list.
Good luck!
jazzmijnhv said:
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
Click to expand...
Click to collapse
Stock bootloader, same bootloop scenario - factory reset wiped everything including photos, music, other files. Clear storage seems to keep everything except the installed apps and configuration. It's the 4th time I'm doing it unfortunately :

[Q] Hard-Brick I535 After Restoring from Nandroid Backup?

I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.

[Q] Factory reset?

So I'm S-off, Firewater, SuperSU, CWM, stock software, I have not loaded a ROM, fastboot flashed the nohbootimg firmware update, added the HTC browser, and flashed the OTA-killer.
Can I do a Factory reset without it messing something up? I'm having 3 issues that I want to see if a reset will fix, one is my alarm clock keeps turning itself off, another issue is that when I turn the phone on it seems to take a long time to "Prepare Sim card" , and the last issue is that I get a email "login failed" notice which is poping up before the phone starts seeing the data connection.
Thanks
Dragbike Racer said:
So I'm S-off, Firewater, SuperSU, CWM, stock software, I have not loaded a ROM, fastboot flashed the nohbootimg firmware update, added the HTC browser, and flashed the OTA-killer.
Can I do a Factory reset without it messing something up? I'm having 3 issues that I want to see if a reset will fix, one is my alarm clock keeps turning itself off, another issue is that when I turn the phone on it seems to take a long time to "Prepare Sim card" , and the last issue is that I get a email "login failed" notice which is poping up before the phone starts seeing the data connection.
Thanks
Click to expand...
Click to collapse
If you are simply stock and rooted... you can factory reset using CWM without any issue.
Worst case scenario if you are backed up...
http://forum.xda-developers.com/showthread.php?p=52115727
Since you have not installed a ROM I would think a factory reset would be a good first step. You will probably lose some if the customization you have done, but I wouldn't think you would lose root or anything like that. I believe a reset will just wipe the data partition ( maybe dakvik and cache as well).
Sent from my VZW HTC One (M8)
dottat said:
If you are simply stock and rooted... you can factory reset using CWM without any issue.
Worst case scenario if you are backed up...
http://forum.xda-developers.com/showthread.php?p=52115727
Click to expand...
Click to collapse
Thanks! Just curious, I'm trying to learn as fast as I can , how does CWM reset differ from the the stock one?
And do you think that the CWM reset could help with the issues?
Dragbike Racer said:
Thanks! Just curious, I'm trying to learn as fast as I can , how does CWM reset differ from the the stock one?
Click to expand...
Click to collapse
They both typically wipe the same partitions however the stock recover also resets some radio elements which is why you will always see me suggest to someone with radio issues to do a factory reset from stock recovery.
Sent from my HTC6525LVW using Tapatalk
I used the reset in CWM and I'm going through the setup now, I guess we'll see if this helps. Thanks guys!!!
Well the alarm is staying on so far and I'm not getting the email login failure but I think I lost my CWM, guess I'd better reload it.
Interesting, I can't seem to get into my hboot mode? hmmmm
nevermind, I'm a dolt, forgot to turn off fast boot and I Still have CWM but when I select reboot I get a message "Root access possibly lost. Fix?" Anyone know what this could mean? Should I Pick "Yes - Fix Root" . I'd assume so, what the heck lets see what happens. lol

[Q] Nandroid Backup Stuck on Boot Screen

Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Did you try wiping everything before restoring your backup?
Sent from my HTC6525LVW using Tapatalk
I had the same, exact issue. Absolutely no reason why it shouldn't have worked. I made sure the Nandroid copied the necessary partitions/directories and also performed a full wipe before restoring the backup. Same issue. I was on TWRP and I'm pretty sure there is some issue with TWRP.
I haven't attempted to make a backup or restore a Nandroid since, so I don't know whether its still an issue.
ChuckFinley1992 said:
Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Click to expand...
Click to collapse
I tried wiping everything yes. I did a factory reset data wipe first, and then tried installing the backup. I don't know why it did not work. I was eventually able to get out of the boot screen with an volume up and power key combination, but it was more frustrating not knowing why this issue was happening. If anyone knows why this is occurring, I would gladly like to know.

Categories

Resources