T Mobile HTC One M8 has No OS, Please HELP!!!!!! - One (M7) Q&A, Help & Troubleshooting

Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I have no idea how to fix it
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.

Related

[Q] Whats wrong with my HTC hero?

So I used to have CyanogenMod running on my phone, but it was messing up so I decided to flash the FroYo rom. My hero is sprint and the rom was for sprint phones. But when I flashed the rom my phone wouldn't start up. It just stays on the big "HTC" screen. Ive tryed everything. Any help?http://media.xda-developers.com/images/smilies/frown.gif
Did you wipe (everything!) before flashing the other ROM?
As andythegreenguy asked, did you wipe everything prior to flashing?
Also, how long has it stayed on the HTC screen? Booting a new ROM for the first time can take as long as 15 minutes...
How to wipe?
c00ller said:
As andythegreenguy asked, did you wipe everything prior to flashing?
Also, how long has it stayed on the HTC screen? Booting a new ROM for the first time can take as long as 15 minutes...
Click to expand...
Click to collapse
What is the correct procedure to wipe everything off? If I plan to reinstall the same ROM?
mumbaiyya said:
What is the correct procedure to wipe everything off? If I plan to reinstall the same ROM?
Click to expand...
Click to collapse
Boot into recovery, and do a full factory wipe
Getting stuck there is a bootloop.
It's usually caused from not wiping the cache(s).
New Rom:
(Boot into Recovery)
Wipe Data/Factory Reset
Wipe Cache
Wipe Dalvik
I like to wipe Batt Stats but you don't really need to.
Just Factory Reset, wipe both caches.
I assume the recovery is similar to the evo's, I've never seen the hero's recovery so it might be different.
A new rom will take a little longer than usual because it needs to rebuild the caches while its on the HTC screen.
xNotta said:
Getting stuck there is a bootloop.
It's usually caused from not wiping the cache(s).
New Rom:
(Boot into Recovery)
Wipe Data/Factory Reset
Wipe Cache
Wipe Dalvik
I like to wipe Batt Stats but you don't really need to.
Just Factory Reset, wipe both caches.
I assume the recovery is similar to the evo's, I've never seen the hero's recovery so it might be different.
A new rom will take a little longer than usual because it needs to rebuild the caches while its on the HTC screen.
Click to expand...
Click to collapse
That's correct

Problems after factory reset

I've majorly screwed up. I'm using a samsung galaxy ace s5830. After partioning my sd card I found that I couldn't root my phone since cwm was not allowing it. So I got frustrated and did a factory reset. Now my phone will not get passed the samsung intro and the blinking samsung sign. Please help
Reflash a rom with odin, it will wipe anything wrong (just remember to wipe data, wipe cache, and wipe dalvik cache)
Thanks will do so. can you shed some light as to how a simple factory reset got me into a boot loop
sjg2797 said:
Thanks will do so. can you shed some light as to how a simple factory reset got me into a boot loop
Click to expand...
Click to collapse
After wipe data/factory reset, bootloops can be solved by wiping cache and dalvik cache.
If something got messed in the kernel while trying to flash the root zip, then wiping everything will still keep an error, maybe that's what caused the bootloop, this is fixed with a fresh odin flash.
Check that your root zip is compatible and thay you use the correct recovery to flash it (sometimes it must be done through stock recovery, sometimes through cwm)

Can't access Recovery and can't boot to android.

I undusted my N1 to sell it and it was working before. I'm on BlackRose with stock values. Even if I flash any recovery, I'm still stuck at X. I can't boot to android or anything. Updated to original RUU (PASSIMG) but doesn't change anything. Wiped cache/userdata from fastboot too...
PLease help me.
Thanks
The battery has been left removed from the phone for few minutes while searching for a fix to my problem then I tried again to boot to recovery and it did... Just did factory reset, wipe cache, wipe dalvik and battery stats.
Will update if end with something working.

[Q] help please asap!!!!

hi i recently just rooted and flashed the dark raider rom on my vivid with being s-off. the problem im having is my phone keeps force closing every 2 seconds! is there a fix? or am i screwed i cant even set an apn due to it force closing so fast please help thanks!!!!!!
Try and reflash the Rom , the flash the kernel and make sure to do all the wipes.
Should fix it.
Yep, bad flash. You MUST do the two wipes (cache and dalvik cache).
If you're moving from a different ROM, you really should do a FULL wipe (system, data, boot). It really does make a difference.
ess.boyer said:
Yep, bad flash. You MUST do the two wipes (cache and dalvik cache).
If you're moving from a different ROM, you really should do a FULL wipe (system, data, boot). It really does make a difference.
Click to expand...
Click to collapse
k I flashed and cleared everything but problem still there......i started this problem with the ics upgrade my hboot shows no image if thats means anything ive installed dark raider hoping to solve problem but didn't work my service is always switching from 4g to no service and then phone force closes....the only time it stops force closing is when i put in airplane mode please any suggestions would be great..thanks everyone for the help i also installed the ruu rom to to see if it fixes it but still same problem the dark raider rom works great minus the phone
Which kernel do you have installed?

[Q] Help Stuck in CWM bootloop after formatting system

Hey guys sorry if this has already been posted. I tried to search through the other threads but couldn't find anything with my exact problem. I am a noob when it comes to this stuff so please bear with me. I was trying to reinstall my ROM when I made the dumb mistake to format system, When I was in recovery I wiped data/factory reset, wiped the cache partition, wiped Dalvik cache, and then for some reason went to format system. After I did that and went to reboot the phone it asked me to fix root. I did this and it started the CWM bootloop. Does anyone have any ideas what I can do to fix it?
exitrecovery.zip will stop the boot loop.
Sent from my Nexus 10 using Tapatalk 2
chadsky92 said:
Hey guys sorry if this has already been posted. I tried to search through the other threads but couldn't find anything with my exact problem. I am a noob when it comes to this stuff so please bear with me. I was trying to reinstall my ROM when I made the dumb mistake to format system, When I was in recovery I wiped data/factory reset, wiped the cache partition, wiped Dalvik cache, and then for some reason went to format system. After I did that and went to reboot the phone it asked me to fix root. I did this and it started the CWM bootloop. Does anyone have any ideas what I can do to fix it?
Click to expand...
Click to collapse
Also try this...
Pull battery..
Count to 10.
Replace battery.
Press and hold Volume Down and power until the Factory Reset screen comes up..
Hit the power button twice, once to start and the second to confirm.
This should put you into your recovery mode... There you should be able to install the ROM again..
At least this is what has always worked for me...

Categories

Resources