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 don't know how to fix the phone
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.
mauricioreynoso123 said:
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 don't know how to fix the phone
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.
Click to expand...
Click to collapse
Download a custom rom and adb push it to your internal storage and then flash it from recovery.
Same problem
mauricioreynoso123 said:
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 don't know how to fix the phone
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.
Click to expand...
Click to collapse
In addition to the same problem, when I connect my phone to the PC, it does not show up.
Did you get a fix on the problem ???
ED
riversinc said:
In addition to the same problem, when I connect my phone to the PC, it does not show up.
Did you get a fix on the problem ???
ED
Click to expand...
Click to collapse
Honestly there's a lot of people with no os on bootloader screen.
My os dissapears after unlock recovery s-off and custom Rom.
If your phone is tripping I would just relock and flash ruu in bootloader mode.
First I would verify its not a driver issue and make sure usb debugging is on. If u are on a custom Rom go to there superuser settings and make sure it's set to apps and adb. Then try again.
twinnfamous said:
Honestly there's a lot of people with no os on bootloader screen.
My os dissapears after unlock recovery s-off and custom Rom.
If your phone is tripping I would just relock and flash ruu in bootloader mode.
First I would verify its not a driver issue and make sure usb debugging is on. If u are on a custom Rom go to there superuser settings and make sure it's set to apps and adb. Then try again.
Click to expand...
Click to collapse
i have the same issue on my phone my pc isnt recognizing the phone at all and when i can get into my recovery screen to try to turn phone off it says i need to flash super user and when i do it goes to a white htc android developers screen but thank god i can get back to bootloader screen any help to my problem i really would appreciate an answer
STANC1 said:
i have the same issue on my phone my pc isnt recognizing the phone at all and when i can get into my recovery screen to try to turn phone off it says i need to flash super user and when i do it goes to a white htc android developers screen but thank god i can get back to bootloader screen any help to my problem i really would appreciate an answer
Click to expand...
Click to collapse
boot to recovery, sideload a rom. if use adb is to hard for you then download the toolkit and use that to sideload a rom.
I'm no genius on this stuff, but if I were you I'd throw a ROM on the external SD and wipe everything and flash it.
I'm curious why you were having problems in the first place...your phone shouldn't have been having problems like that. It sort of sounds like a kernel problem. Regardless, I wouldn't necessarily flash whatever ROM you were having problems with. If I were you, I'd grab one that tons of other people who are on your carrier are using. Definitely don't flash one that is newer--get something from a well established dev/group.
As long as you can get to TWRP or whatever custom recovery you have, you should be able to wipe & flash without having to use ADB. Not that using ADB is bad, but if you're new, it can be confusing. Let us know how it works out.
can you help?
i dont even have recovery on mine anymore.So, how can i even flash a new rom?
zerozed99 said:
I'm no genius on this stuff, but if I were you I'd throw a ROM on the external SD and wipe everything and flash it.
I'm curious why you were having problems in the first place...your phone shouldn't have been having problems like that. It sort of sounds like a kernel problem. Regardless, I wouldn't necessarily flash whatever ROM you were having problems with. If I were you, I'd grab one that tons of other people who are on your carrier are using. Definitely don't flash one that is newer--get something from a well established dev/group.
As long as you can get to TWRP or whatever custom recovery you have, you should be able to wipe & flash without having to use ADB. Not that using ADB is bad, but if you're new, it can be confusing. Let us know how it works out.
Click to expand...
Click to collapse
stlsports said:
i dont even have recovery on mine anymore.So, how can i even flash a new rom?
Click to expand...
Click to collapse
you might be able to get the phone in the boot-loader (power and volume key down key) and then via fastboot flash the twrp recovery and then push a backup to the phone and restore.
-brad
Use the toolkit available in the general? section and flash the 4.4.4 RUU. Should return you to complete stock.
Did you get it fixed
mauricioreynoso123 said:
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 don't know how to fix the phone
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.
Click to expand...
Click to collapse
I have the same problem no os but I have everything but no os
Well I fixed my phone
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Related
I'd like to start by apologizing for what is probably the 9,000th "help, I've bricked my phone!" thread. I did some searching, and while I found many, I wasn't able to find one that both dealt with my specific issue, and did so assuming a level of newbishness appropriate for me.
Months ago, I rooted my AT&T Galaxy SIII, and installed CM10. It's been all candy and rainbows since. This morning, I somewhat foolishly decided to update from a nightly I installed in October/November, to the January 7 CM 10.1 nightly, using the built-in updater I had previously used to switch to a nightly.
It worked...sort of. I guess I should have cleared my cache or something ahead of time, because almost all of my GAPPS stopped working. Woops! Figuring that I should probably stop dicking around with my phone until I learned a bit more, I just went back and told the phone to switch back to the nightly I from October/November that I was previously using.
It didn't work. My phone now reaches the CM boot animation and just...sits there. And sits there. And sits there. To complicate the issue, I cannot get the phone to boot into recovery mode (although admittedly, I'm too thick to know what I'm meant to do once I'm there anyway). I CAN get the phone into download mode, but not being sure what I should do there, I thought it best to consult you all on what to do next.
I'm happy to give any additional information needed, and I hope it goes without saying that I am extremely thankful for any help you all can offer.
Try to get it back into recovery by taking the battery out, putting it back in and then holding volume up, home, and power. If you are sure you can't get it into Recovery, but know for sure you can get it into Download, go into Download and flash stock and go from there. These aren't bricks. These are just whoops. Lol.
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Actually, you should always wipe cache and dalvik when flashing the update. If it is a major update like 4.1.2 to 4.2.1, then you should wipe cache, wipe dalvik, Factory Reset, Format System then flash your ROM.
Move important files to SD using twrp file manager. Put rom on SD with gapps. Format internal, wipe caches, format system, factory reset, load ROM, load gapps. Reboot.
Sent from a Horny Pink Pony
smelenchuk said:
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Click to expand...
Click to collapse
I did this, being careful to follow all the instructions provided. Odin seemed to think everything worked, and after about 10 minutes, it rebooted the phone.
However, it still gets stuck. Now, since CM is no longer installed, it just sits at the SAMSUNG logo forever.
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
naporeon said:
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
Click to expand...
Click to collapse
Boot to recovery and clear data and cache.
smelenchuk said:
Boot to recovery and clear data and cache.
Click to expand...
Click to collapse
Worked like a charm, thanks! Can't believe after all that trouble, I didn't think to do that myself. >.<
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl
I'm having this really bizzare issue with my HTC rebooting not in a traditional bootloop per say but the phone will only reboot when i get into the OS itself. Before I explain exactly here is my device details when the event started:
Unlocked Bootloader
TWRP Recovery
Root Access
Stock AT&T Sense 6 Rom Android 4.4.2
So nothing crazy. I was experiencing a slow down in my data speeds so I figured why not just reboot the phone and see if that helps any. After I did I want to say 10 seconds later my phone rebooted. It was strange but i thought nothing of it......until it happened 4 more times and then wouldn't stop. I was able to temporarily stop it but doing a full wipe and flashing a GPE Rom but as soon as i reboot my device it starts again. I've tried just about everything from cache wipe, dalvik cache wipe, and even changing my recovery to Philz but nothing has helped. And since there still isn't a RUU for the M8 yet i cant convert it to stock for warranty because I cannot remove the tamper. Can anyone help me? I'm really trying not to have to pay for another device. Working for AT&T only has its perks from a monthly bill perspective lol
bnicsk8guy said:
I'm having this really bizzare issue with my HTC rebooting not in a traditional bootloop per say but the phone will only reboot when i get into the OS itself. Before I explain exactly here is my device details when the event started:
Unlocked Bootloader
TWRP Recovery
Root Access
Stock AT&T Sense 6 Rom Android 4.4.2
So nothing crazy. I was experiencing a slow down in my data speeds so I figured why not just reboot the phone and see if that helps any. After I did I want to say 10 seconds later my phone rebooted. It was strange but i thought nothing of it......until it happened 4 more times and then wouldn't stop. I was able to temporarily stop it but doing a full wipe and flashing a GPE Rom but as soon as i reboot my device it starts again. I've tried just about everything from cache wipe, dalvik cache wipe, and even changing my recovery to Philz but nothing has helped. And since there still isn't a RUU for the M8 yet i cant convert it to stock for warranty because I cannot remove the tamper. Can anyone help me? I'm really trying not to have to pay for another device. Working for AT&T only has its perks from a monthly bill perspective lol
Click to expand...
Click to collapse
twrp, wipe, dalvik/cache/data/system, flash rom, if you don't wipe system some stuff can find its way over and may be causing issue. Is this an at&t phone? There is an att ruu.
an0ther said:
twrp, wipe, dalvik/cache/data/system, flash rom, if you don't wipe system some stuff can find its way over and may be causing issue. Is this an at&t phone? There is an att ruu.
Click to expand...
Click to collapse
It is an AT&T device. I'm sure I've done a system wipe and like I said sometimes my device will work okay but as soon as i reboot it, its back at it again. And thanks for the info! I wasn't aware the RUU for the AT&T version as available
bnicsk8guy said:
It is an AT&T device. I'm sure I've done a system wipe and like I said sometimes my device will work okay but as soon as i reboot it, its back at it again. And thanks for the info! I wasn't aware the RUU for the AT&T version as available
Click to expand...
Click to collapse
At&t 1.58 RUU
http://forum.xda-developers.com/showthread.php?t=2757462
I'm writing because I found no solution to this or someone to address this. are there not many having this problem?
After 7.0 update my alarm is not ringing and if I go in the settings to change the alarm sound the app fc, also the YouTube app says "something went wrong" when trying to play a video.
After restart the sound is back for some time, then bug repeats.
I activated touch sound so I get a warning when I need to reboot, but the touch sound is not affected, also the music app is working, but no alarm or notification.
Whipped cash, installed Oos 4.0.3 via recovery (stock, locked bl, no root)
Currently on 7.1.1 Oos 4.1.3
Someone please help
Starting to think that I will have to sent the phone back to OnePlus...
get the full 4.1.3 zip, and on stock recovery wipe everything not just cache...
then back to the main menu on recovery and select install via USB (or something liket hat) and sideload the full rom from computer , after sideload boot to system and for good measures do a factory reset.
theduke7 said:
get the full 4.1.3 zip, and on stock recovery wipe everything not just cache...
then back to the main menu on recovery and select install via USB (or something liket hat) and sideload the full rom from computer , after sideload boot to system and for good measures do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply ! - I will try your suggestion tomorrow if I get the time -
Maybe it's a stupid question but: is there ever a need to wipe internal storage? or wipe everything means just system data ?
plus: could the encryption mess things around ?
marius88cc said:
Thanks for the reply ! - I will try your suggestion tomorrow if I get the time -
Maybe it's a stupid question but: is there ever a need to wipe internal storage? or wipe everything means just system data ?
plus: could the encryption mess things around ?
Click to expand...
Click to collapse
Encryption may cause issues, but I don't think your problem is related to that, something in the update process went wrong I think so you got something corrupted on the either the system.or data partition , so Everytime you install a new ROM it does but the issue stays, the only way to know for sure is a clean install, and the easiest way to that is what I told you, it can also be done by fastboot where you wipe everything with fastboot then sideload , but to be safe better stick with the recovery method... I don't thing internal storage could cause an issue, but I personally from 7.0 to 7.1.1 I did wipe it , better safe than sorry, and it elemenates any possibilities so if you can do that it's better
theduke7 said:
Encryption may cause issues, but I don't think your problem is related to that, something in the update process went wrong I think so you got something corrupted on the either the system.or data partition , so Everytime you install a new ROM it does but the issue stays, the only way to know for sure is a clean install, and the easiest way to that is what I told you, it can also be done by fastboot where you wipe everything with fastboot then sideload , but to be safe better stick with the recovery method... I don't thing internal storage could cause an issue, but I personally from 7.0 to 7.1.1 I did wipe it , better safe than sorry, and it elemenates any possibilities so if you can do that it's better
Click to expand...
Click to collapse
Thank you for the reply!
Weirdest thing, I did not get the chance to reinstall the system yet, but since I posted this the bug did not reaper. I suspect an app was misbehaving and it got updated...I will wait and see.
Just sideloaded, will report how it goes if anyone faces the same problem
New OTA Out, should solve this, it seems
So i didnt make a backup of my n100 and well yea i wipe all and now i cant flash stock rom on my device who knew is it maybe possible to get a stock backup of some sort from someone and use it somehow? Also just to be clear i rooted my device without a pc and well yea i installed a bad module from lsxposed and when i reboot my phone GG Boot loop and after i figured id try to factory restet and well i also wipe all data etc etc i tried flashing new rom but i cant apparently its missing key components who knew
milfWolf said:
So i didnt make a backup of my n100 and well yea i wipe all and now i cant flash stock rom on my device who knew is it maybe possible to get a stock backup of some sort from someone and use it somehow? Also just to be clear i rooted my device without a pc and well yea i installed a bad module from lsxposed and when i reboot my phone GG Boot loop and after i figured id try to factory restet and well i also wipe all data etc etc i tried flashing new rom but i cant apparently its missing key components who knew
Click to expand...
Click to collapse
At this point a local update from recovery is probably your best option. Get the latest FULL OTA for your model and push it to /sdcard from adb. Then boot to recovery and do the update. This should sort all your partitions and stuff.
for starters you will need a pc to fix this. now i want you to retrace your steps. what twrp you had, what magisk version, what did you install, what errors it shows, everything you can. the more details you provide the faster we can help you