[Q] Soft Brick - One (M8) Q&A, Help & Troubleshooting

Well after searching, reading, and trying a few different guides on how to fix the issue. I have spent the last 5 hours pulling my hair out and really didn't get anywhere.
I have a HTC M8 from sprint. I used the All-In-One to root and flash the custom recovery ( Clockwork Mod Sprint)
I left s-on and just wanted to try the stock rom out for a few days. After about a week it started and never ending reboot. It would boot up and load the OS like normal and after about 2 to 5 min it would reboot again. Tried clearing the cache and that resolved the issue for about a day. It then started same thing again. At this point i decided to try ardh. After reading thru arhd post and downloading I made a bone headed mistake of NOT running a backup. I used the "Clean to install a new rom" option and then went to install the rom from the external sd card. it got to about 70% and failed out. I re download and tried again and got the same results. I then tried Viper one, Redbulled, and a few others. No matter what rom i tried it would fail.
Now at this point I realized what a dumb move it was to not run a backup. Started searching here and the great interwebz for how to fix this.
I tried to sideload the roms and they tanked.
Does anyone have a few pointers or ideas on how to fix this.

I would say, see if you can find a rooted stock ROM. Place it in your backups folder. Try to restore it. I've been there, did that and it worked for me on a previous HTC.
Sent from my HTC One M8 Google Play Edition. S-OFF.

Don't sideload. They usually fail. Just push. Load twrp. Don't do anything. adb push Rom.zip /sdcard/
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Related

[Q] Please Help! Looping

Ok... here's the deal. I just decided to switch roms finally to see what is new out there. I had been running an old version of Uber Kingdom. Here is the problem I am having. It is boot looping. Relatively simple problem to fix usually. But wait, there's more! It is boot looping in every single rom I install. Sometimes it won't boot to clockwork properly either and I have to pull the battery. Is there someway I can fix this? Or is this a hardware problem (which I kind of doubt)? I just don't understand what the heck is going on. I have been flashing different roms left and right for the past few hours trying to get this thing to stabilize. Sometimes it will boot up into the rom, I will get mostly through the google accounts setup, and then it will restart, and then loop. Other times it won't even get past the white incredible screen, and then sometimes it will make it into the rom splash screen. I have attempted to install CM7 nightly, Uber kingdom, and Synergy so far. I can flash the new rom, I can mount the SD card in clockwork, but then it begins to loop again as soon as I leave clockwork.
Let me know if you need any other information.
Is there a way to just completely redo EVERYTHING, clockwork, rom, everything, just to make sure I have a nice clean slate?
Thanks a ton for reading through this novel. I am extremely frustrated.
~Will
PS, I may not get back to this thread until morning. I have to get to sleep for work. Sorry if I don't respond right away to information requests. Thanks again!
If you can mount the SD card, download the stock RUU from www.dougpiston.com, put it on the root of the SD card named exactly PB31IMG.zip, and boot into hboot to install it. Your phone should be restored to stock, a clean slate.
Tried a different SD?
Sent from my ADR6300 using XDA Premium App
How are you downloading and flashing the ROM? I had this problem when trying to do everything through Rom Manager. Even trying to flash in recovery with a ROM downloaded through ROM Manager would loop.
Update
Well, I was just getting ready to flash the original RUU when I tried one last time to restore my old Uber rom setup and it worked (whereas the last 3 times of doing exactly the same process didn't). It stopped looping at least, even though I am still running the same rom I was before. I think tonight I am still going to attempt to flash the RUU anyway and start over anew.
To answer the questions before, No, I did not try a different SD. I didn't know it could make that much difference. Still on the original one that came with the phone.
As the downloading and flashing process goes, I was downloading direct from the XDA forums on my laptop, then transferring the files via USB. I have never really liked using the Rom Manager. It cuts me out of the XDA loop and I don't get to see all the bleeding edge discussions, etc...
So I will try to flash everything new tonight, and then post my results for anyone who is curious. Thanks for the help guys!

[Q] DINC Problems

Hello,
I've searched high and low for a solution to my problem. I have a refurbished incredible. I rooted it with unrevoked 3 about six months ago. I was using CM7 for a while and just recently (7/25/11) was getting numerous force closes on almost every app I used. I decided to flash a new rom but couldn't get into recovery and ROM manager was force closing. I read else where that people who had issues with recovery was solved by reinstalling PB31IMG. I did that and my phone was reset back to a fresh CM7 but everything was still force closing and I still couldn't get into recovery. I do have nanodroid backups on my computer and a complete copy of the my sd card along with a spare. In addition to my phone force closing and not being able to access recovery, it is now stuck in a boot loop. Does anyone have any advice or do I know have a very nice looking paperweight? Please Help.
Jason
No genius here, but have you tried to download Rom manager to your desktop, and reinstall it? If that works, flash a a new recovery from there. Sorry I can't help more.
Sent from my ADR6300 using Tapatalk
Manually flash the recovery:
http://dougpiston.com/?page_id=85
For SLCD: use v3.0.0.8
For AMOLED: use v3.0.0.7
If you have to, try going back to stock from the PB31IMG on his site as well (to fix bootloops): http://dougpiston.com/?page_id=108

[Q] should i risk another rom?

Hi all, iv only been flashing for a week (lol never thought id say that), anyway i thought id have a go at mildwild. I downloaded the file with my phone and then went into bootloader and flash cm7r2 and went back into recovery to wipe factory, cache, dalvik.
but when i went to install mildwild it wasnt there, i went into every folder but nothing so i went back into bootloader flashed stock hboot and back to recovery. 4ext said to wipe system caus its in safe mode so i did.......45 minutes later it hadnt passed the first part so i felt i had to battery pull.
Ithen went to restore my backup but again this never passed the first stage so i had to do another battery pull.
Luckily i had the zip folder from when i first downloaded it and that worked. Do you think im safe to try another rom or am i heading for a brick?
i have a new sd card ordered because i think its borked the phone doesn't recognise it sometimes, could this be my problem?
I have to say its really addictive and exciting trying different roms but at the same time its also very scary!!!!
Once you start you can't stop. It's glorious.
Sent from my HTC Desire using xda app-developers app
Oooh,when i sent a new zip file from PC use 4EXT Mass storage to instead an old one, it seemed to never be rereaded, and when i flash it, i showed it was the old one.
OK so i didnt really get a reply i was hoping for so being a little impatient i decided to have another go.
I couldnt open the mildwild for some reason, i think it was because the file had a (2) at the end, i must have downloaded this before.
Could this be the reason 4ext said it was a bad file?
On the up side all the problems i had before are gone, everything restored perfectly. It seems to be when i change a hboot things seem to go a little weird.
------------------------------------------EDIT------------------------------------------------------------------------------------------------------------------------------------------------- changed it back to what it was originally called and it still says 'error installing (bad)'
playforth said:
OK so i didnt really get a reply i was hoping for so being a little impatient i decided to have another go.
I couldnt open the mildwild for some reason, i think it was because the file had a (2) at the end, i must have downloaded this before.
Could this be the reason 4ext said it was a bad file?
On the up side all the problems i had before are gone, everything restored perfectly. It seems to be when i change a hboot things seem to go a little weird
Click to expand...
Click to collapse
I have already written about problems with hboot. I recommend formatting all partitions (except sd card) from 4ext recovery before hboot change, and so after the change. Problem with file that's not opening is probably because the file is corrupted, so try to download it again.
Ok thanks for the reply. I will try it
Sent from my HTC Desire using Tapatalk 2

[Solved] MiuiV4 CDMA will not boot

All right this problem has now been solved! Thank goes to khamsakamal48 for posting the solution for the problem. The problem is solved by replacing the updater-script with the one that is used in the GSM version the of Rom. Then Using the latest 4ext recovery, wipe everything and install. Thank you to everyone that have participated in trying to get this solved. This might also work with other recoveries, but has not yet been confirmed.
Updater-Script: http://db.tt/sUfk5p8E
Latest 4ext recovery: http://db.tt/sP5o7HhJ
only thing i could think of is try a different recovery .I haven't had any trouble at all booting miui an i use cwm touch version.
Alright I'll have to give it a try. Was trying to avoid that but oh well. Thanks!
Sent from my Incredible 2
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
kylesag21 said:
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
Click to expand...
Click to collapse
Can you give us a little more background on your phone setup? Have you flashed roms successfully before or is this a first time? Are you s-off?
Sorry bout that. I am S-off and I am able to flash all of the other roms available. But when it comes to this one it just won't flash.
Sent from my Incredible 2 using Tapatalk 2
I have been having this same problem. I am going to try to go through everything I have done to see if I can get more info.
I had MIUI V4 (2.9.29 CDMA) running shortly after rooting this phone (maybe 1 week ago). I installed it from the latest TWRP, so that isn't our problem. I loved it and everything was great. I am unsure what radio I was on at the time, and I think that may be where my problems came in.
I successfully installed ViperINC 1.0.0 after doing a factory reset, wiping cache, dalvik from my WORKING MIUI V4. It booted and I played with it for a few hours, but wanted to go back to MIUI. At this point I was on the firmware from nitsuj17's thread. When I tried to factory reset and install MIUI clean again I started having the same trouble as OP. Since then I have tried every radio I could get my hands on, and may have even been a bit sloppy about what firmware I flashed (the only one I'm unsure of is CondemnedSoul's Return to stock as I am unsure what all it included other than radio and stock rom). After a lot of different attempts, I used CondemnedSoul's PG32IMG and went back to stock where I had everything working fine (for stock). I got an OTA update, but wasn't satisfied so I kept trying different radios from the pinned post on the Development thread (really only .0312 and .0320 as well as the first leaked firmware I linked from nitsuj17). So far nothing has worked to get me any further than the OP unless I just use a different rom. Had this rom never worked I would just talk to the developer, but as I had it working before and no idea what changed I'm at a loss.
I don't have enough posts to get something on the Development forum, but if anyone here can help, I'd really appreciate it.
I've been scouring these forums looking for someone who has made progress on this issue. I'm going to make a list here of posts by people having similar problems, if not the exact same. I have yet to see anyone successfully address them.
One of a few people on the MIUI V4 thread who have had the same issue. I had this rom running at one point, though, so I'm not sure what change caused it to stop. I definitely get further with the TWRP recovery (freezes on "android" splash screen) than the 4ext recovery (reboots to recovery).
I don't believe the JB issues are directly related, but similar problems.
Similar to the Jellybean issue above. More similar to my own situation since I also only started having trouble after flashing ViperINC, but I have formatted, wiped and reverted (even to S-ON and unroot Froyo) so much that I can't see how it would have changed anything that I have not removed. This thread has 3+ people with the same sort of issues. Last report one of them installed ViperINC with all defaults and let it run for a few minutes then wiped and re-installed CM10 with success. I may try this, only with MIUI. I have no idea what settings would be slipping through.
And the cdma miui is one of the only roms that boots for me. Running it now. I think Zelmo is right, there's something sticking around with that Aroma script. I've flashed aosp roms over sense roms and vice versa without even wiping and never had issues like these. I've basically wiped this thing with steel wool and always the same thing. It's gone atleast 15 mins with it's bootloop/freezing max cpu process. It ain't gonna boot! I was up until 2am last night ****ing with it. I'm done.
I'm nearly there. Had I never been able to run MIUI, I would probably have dumped it by now, but it's like an itch I can't reach at this point. There is just something there that I can't see or imagine that is hanging in through every wipe I can find. I just formatted my SD card and did a bunch of wipes (I know that has been tried) and I'm going to try VenomINC with all defaults like Zelmo88 had some success with. If I don't have any luck getting to MIUI from there I'll probably go back to my dinc or buy a new phone soon. This one was really an experiment anyway.
Will follow up if I can figure out anything else.
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
stoicwood said:
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
Click to expand...
Click to collapse
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
grunt9800 said:
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
Click to expand...
Click to collapse
I think most of us first noticed these problems around the time we flashed Viper, but I have nuked this thing so hard from so many different directions since the last time I ran Viper that I can't imagine anything surviving. Still, a little too coincidental.
Running the GSM version didn't last long, either. I played around with trying to get it to use my sim, but as soon as I changed some of my network settings it went into a bootloop tailspin and somewhere along the way corrupted my /system. That took a little work to get around, so now I'm back to aeroevan's CM10 which runs OK... other than what doesn't.
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
[SOLVED]
khamsakamal48 said:
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Worked perfectly first try! Now running CDMA version without problem. I don't know why it works, but it works. Everyone thank khamsakamal48!
I'm not seeing a meta-inf folder. Is there another place it could be?
Sent from my vivow using xda premium
I believe it is in meta-inf>com>google>android
Updater-script should be located there.
Sent from my HTC Incredible 2 using Tapatalk 2
Nope, no meta-inf. Back to Google
Sent from my vivow using xda premium
Are you using 7zip to open up the zip file?
Sent from my HTC Incredible 2 using Tapatalk 2
I'm too embarrassed to tell you what I was trying got it now, thanks again
Sent from my vivow using xda premium

wildfire s not booting

ok guys i have htc one x and my nephew just got a wildfire s and tried to root and rom it.
so heres where im at. ive flashed this rom but im stuck at the htc logo.
he installed the latest CWM for this phone 5.0.2.8. then full wipe and installed a few roms but none worked and then i got here.
with my one x i have to flash boot.img but as far as i can see thats not the issue here??
can anyone help?
It's a gsm wfs with a sim slot. I'm assuming the next step is to install the correct RUU for the phone right?
the phone is stuck at the htc logo
Can someone possibly point me to the correct RUU? Its a UK phone that was on Tesco/o2 mobile and I cant find the right RUU.
Any help is greatly appreciated
Nothing??
Sent from my HTC One X using Tapatalk 4
Seriously no help at all????
Sent from my HTC One X using Tapatalk 4
Oh well
Sent from my HTC One X using Tapatalk 4
So I get told of four posting in a rom thread and get told to post here and I get zero help. Ffs
Sent from my HTC One X using Tapatalk 4
Usually when you're stuck on the HTC logo it's because the ROM you are trying to flash also needs the kernel flashed, which you have to be S-off to do and the developer you got the ROM(s) from should have provided it. You were very general, but I presume a full wipe was cache, dalvik-cache, data/factory reset, and (optional), battery stats? Are you just plain stuck, can't do a factory reset and/or didn't make a backup before trying the ROMs? I was going to flash this ROM at one time and he gives some pretty good instructions to follow...sounds like it might work for you. Better than staring at the HTC logo, eh?!
http://forum.xda-developers.com/sho...ht=what+files+can+i+remove+from+my+wildfire+s
Thanks for the reply. I can get to recovery but I can't install anything as recovery can't seem to find the internal storage.
Sent from my HTC One X using Tapatalk 4
Most recoveries are going to look on the external storage, the actual sd card. Can you move your ROM to that and give it a try? Just to save time, I'll say I'm figurin' the sd card is formatted (FAT 32) and if there's a problem seeing that you might have to go into, "Mounts and Storage" and mount the sd card. I'm in the middle of a movie and will get back after, if you have another question I can help with. Hope it works.
ok so i finally got CWM to see the sdcard and i installed a rom and flashed the boot.img.
now the phone just reboots into recovery. what the hell is wrong with this dam phone????!?!?!
So far we've been successful with the, "One step back and two steps forward" approach so:
You extracted the boot.img file from the ROM zip to your PC for use after and then installed the ROM, rebooted the phone into recovery>>fastboot, hooked up to the PC in a command prompt and changed directory to where you have the boot.img and the adb/fastboot command files and at the command prompt typed: fastboot flash boot boot.img
Typically you would then type: fastboot erase cache, or back in recovery wipe the cache and reboot to find the ROM (slowly) booting for the 1st time.
I'm a one step at a time person (so I know what worked). So if all that's true, and it's still stuck in a recovery loop then I'd try wiping cache again and dalvik-cache and rebooting.
If that doesn't work I'd suggest one of two things:
1. Start over and I don't mean at htcdev, but wiping cache, dalvik, and data...install ROM, flash boot.img, wipe cache reboot...or
2. We can go over all the steps (as briefly as possible for both our sakes) and I'll say why: one time I was writing a macro and it just wouldn't work, after 3 days of spending too much time on it each day I asked someone else to look at it and he found I had missed a slash or used a comma instead of a semi-colon or some one simple thing. So it wouldn't hurt to see if there was one little thing skipped.
Lastly for now - if you post again, whatever you post, just for my curiosity tell me which (compatible with the Wildfire S) ROM your wanting to use.
First of all I just want to thank you for trying to help.
I did those steps perfectly and they've always worked with my HTC one x but no dice with this wildfire.
http://forum.xda-developers.com/showthread.php?t=2206780
That's the ROM I'm trying to get to boot.
I really want to fix this phone for my nephew but its not looking good.
Sent from my Nexus 7 using Tapatalk 2
I know how it is...we all get fixed on wanting one thing and then intent on making it work.
I did a quick look at the page for your intended ROM and first thought, aha...in the instructions to install, the wipe file he provides seems to indicate for a marvelc in the name, so does it wipe all it should on a gsm WFS; but, then he's got that link to the ROM for a marvel c(dma); anyway I did a quick search of the thread (there are 119 pages!) for, "Reboots into recovery" and found this (among others):
http://forum.xda-developers.com/showthread.php?t=2206780&highlight=reboots+into+recovery&page=102
I do see where there was a rebooting into recovery problem with this ROM and a fix was applied in July 2013. I think the link above is to the, "fixed" ROM (hopefully for GSM WFS) but I'm not going to claim that as fact; again, I just took a quick look between my morning news readings and did not read around the problem or, about Lizards patch.
We could go deeper like formatting partitions, but since he has provided a wipe script and there's so much info there...well, I'm not dumping you, but I am thinking researching there might get you more specific results since we've pretty much been going through the generic version of flashing ROMS. What do you think?
ok i read the entire thread and flashed all the fixes etc but no dice. however i did flash a different rom altogether and now everything seems to be working fine!!!!!
dont know why that never occurred to me before!
i must say thank you for all your help. it is very much appreciated
now for some strange reason the original rom now works !!!!!!!!!
For as long as I"ve been fooling around with electronic devices, it often still just seems like, "PFM" sometimes; and, I don't know how many times I've done the right thing over and over and over and then just given up and set it aside only to pick it up again a day or two later and then everything goes like it should...and not doing anything different!
I'm glad you got everything going again, and I'm sure you just want to get back to enjoying it, but I'm curious to know (along with anyone else that might be following) what ROM finally worked, and then you ended up going back to which, "Original" ROM, stock?
I hear you on that. So many times I've had to work on systems for hours then magically I'll do something and it works.
What I did was flash another custom ROM which was unofficial cm10.2 it's on the main page made by owl. That booted up fine but I wasn't happy with that ROM so I flashed the one that I've been trying to flash, marvellous cm10, the one you helped me with.
The only thing I did differently was flash the boot. IMG after I flashed the ROM , I usually flash the boot image first on my one x.
And that's about it.
Sent from my Nexus 7 using Tapatalk 4
I clicked a thanks (and thank you for yours). I enjoyed the exchange and glad you've got it going. The Wildfire S is a great phone, especially for me (although I have my SIM in another phone now) and hopefully your nephew, because it needs to be managed, tuned, tweaked, etc. which is what I love to do and hopefully your nephew will too and keep at it now that you got him off to a good start.
good start yes, but i have to fix the mistakes!! lol
Do you know where u can get int2ext?
Sent from my HTC One X using Tapatalk 4
You caught me right at the end of a movie I was watching!
I've always been happy with Link2SD, but you can't beat moving all of data to SD.
Try this:
http://forum.xda-developers.com/showthread.php?t=1716124
also, this is an easy way to get init.d if you don't have that...I think it's needed for int2ext:
http://forum.xda-developers.com/showthread.php?t=1710980
Have fun!

Categories

Resources