Hi, first the details
S-Off via dirtyracun
HBoot 1.19.2222
Radio 1.12.11.1210
TWRP 2.4.4.0
Latest Viper ROM
Weird issues I have;
-Can not install any ROM other than Viper.
-Can not perform backup, it creates a backup successfully and while still in recovery you can locate the backup file, but if the card is pulled out or the phone is booted, the file disappears.
-ROM feels buggy and laggy recently (I'm pushing power right now & it takes the phone about 30 seconds to wake up) this is the most annoying issue and it's becoming consistent.
-Images taken with phone camera are all corrupt files afterwards and can not be viewed.
The phone worked PERFECT with absolutely no flaws after first installing viper when I achieved S-off & rooted the phone. These problems started when I tried to install a different ROM, after multiple failed attempts I gave up & went back to Viper. I checked everything that I know of and have no clue what to do to remedy these issues.
Now the phone works OK with Viper ROM but it's getting annoying that Viper is my only option and it's not even working as smoothly as it first did (even after wiping cache etc.)
I guess I could return the phone back to stock & start all over again but I refuse to since it took too much time unbricking & troubleshooting when I went through dirtyracun's S-Off procedure, I absolutely can not go through that ever again.
Any help would be appreciated :good:
does no one have any ideas? I tried to start over but now I have locked bootloader and the message "tampered" I'm pretty much stuck at this point and not sure what to try to get ROMs to successfully flash. Still rooted & still have Viper ROM running.
oceanisbleu said:
does no one have any ideas? I tried to start over but now I have locked bootloader and the message "tampered" I'm pretty much stuck at this point and not sure what to try to get ROMs to successfully flash. Still rooted & still have Viper ROM running.
Click to expand...
Click to collapse
Haven't been around as much as I use to so I'm behind the times a bit. If you are rooted and S-Off then bootloader should not say locked. Can you fix permissions from recovery? You have root access with SU and are htc dev unlocked? Is the rom zip or backup on sd or sd2? Can you read either when booted with a file explorer?
I went through the htc dev unlock process now bootloader says "Tampered" & "Unlocked" after that I did fix permissions in recovery and flashed sinister V10 successfully BUT I can't flash a Kernel, I tried to flash Arc-Reactor and failed.
Thanks for the help getting another ROM flashed
oceanisbleu said:
I went through the htc dev unlock process now bootloader says "Tampered" & "Unlocked" after that I did fix permissions in recovery and flashed sinister V10 successfully BUT I can't flash a Kernel, I tried to flash Arc-Reactor and failed.
Thanks for the help getting another ROM flashed
Click to expand...
Click to collapse
Have you tried flash booting the kernel boot.img prior to flashing the kernel ?
Sent from my EVO using xda premium
so I tried Bulletproof Kernel and that installed fine...
as far as flash booting the kernel boot.img no I'm not sure how to do that!
What wipe process r u using? I had issues similar to this on my og EVO and it came down to I wasn't fully wiping and getting a dirty install.
I'm having a similar problem. My phone is really, really laggy since I recently moved from MeanRom to Viper. I ran Viper previously with no issues that I can remember. In terms of my phone, I have TWRP 2.5, wiped using TWRP to clear cache, dalvik cache, and data. I didn't wipe system or internal/external sd.
SmallPsych said:
I'm having a similar problem. My phone is really, really laggy since I recently moved from MeanRom to Viper. I ran Viper previously with no issues that I can remember. In terms of my phone, I have TWRP 2.5, wiped using TWRP to clear cache, dalvik cache, and data. I didn't wipe system or internal/external sd.
Click to expand...
Click to collapse
You should always wipe Cache/dalvik cache/data/system going to a different rom so that might be why viper is laggy.
Try a new install using the wipe method above or use the superwipe zip attached below
I usually do a full wipe cache/dalvic/system etc. in TWRP before flashing, I actually managed to flash several different roms and ironically enough I ended up back on Viper, it just seems to have all the tools I like to use and work smoothly enough to keep me happy. It works as smooth as it originally did when I first installed it, I'm not sure what I did that fixed the issue
Though for some reason I still can't flash most kernels, currently I'm using whatever kernel that comes with Viper
Related
I tried to run a kernel tweaking script and ended up screwing the phone up. I have wiped and re-flashed several times but I keep getting Android layer restart loops and I have to pull the battery. Is there any way to actually wipe the phone and get a truly "clean" install?
I read some stuff posted by bftb0 but I'm not sure if any of it applies to my situation. Can I use the ErisMTDNuke zip if I have never used Clockwork?
I have RA Recovery and the S-Off bootloader (1.49.2000). I can get into recovery with no problem it's just that flashing the ROM again is not fixing the problem for whatever reason.
PieceKeepr said:
I tried to run a kernel tweaking script and ended up screwing the phone up. I have wiped and re-flashed several times but I keep getting Android layer restart loops and I have to pull the battery. Is there any way to actually wipe the phone and get a truly "clean" install?
I read some stuff posted by bftb0 but I'm not sure if any of it applies to my situation. Can I use the ErisMTDNuke zip if I have never used Clockwork?
I have RA Recovery and the S-Off bootloader (1.49.2000). I can get into recovery with no problem it's just that flashing the ROM again is not fixing the problem for whatever reason.
Click to expand...
Click to collapse
Try Wiping Everything, then Boot up your phone Without the Sdcard!
How far does the phone get before it loops back? Are you able to use adb to get a logcat of what's going on?
Some things to think about trying if you haven't already:
* Flashable Stock ROM - March 2011 OTA - keeps custom recovery
* Flashback21 v2 - March 2011 OTA - reverts to stock recovery
* Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP - April 2010 - rename to PB00IMG.zip, flash with bootloader
PMGRANDS said:
Try Wiping Everything, then Boot up your phone Without the Sdcard!
Click to expand...
Click to collapse
I have wiped everything that Recovery will allow me to wipe. I have not pulled the SD card though.
MongooseHelix said:
How far does the phone get before it loops back? Are you able to use adb to get a logcat of what's going on?
Some things to think about trying if you haven't already:
* Flashable Stock ROM - March 2011 OTA - keeps custom recovery
* Flashback21 v2 - March 2011 OTA - reverts to stock recovery
* Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP - April 2010 - rename to PB00IMG.zip, flash with bootloader
Click to expand...
Click to collapse
It varies actually. Sometimes it will boot all the way but when I do a function or two, say bring up the keyboard, it will reboot. Other times it will boot to the lockscreen, but then reboot and go into a loop. And sometimes it will never make it past the boot animation before looping.
I did try flashing another ROM I had on the SD card, xtrROM, then wiped cache and data before flashing GSB again, but no joy because it still happens. I'll try these and see what happens.
PieceKeepr,
It sounds to me like you might be overclocked too high...we have seen some phones in the past that used to run okay at higher speeds but no longer do...
If you can get to the overclocking / setCPU settings, try backing your clock-speed down from where ever the phone is booting-up or running at.
You could also test this by flashing the stock ROM that I see a link that MongooseHelix posted above since that should run at 528MHz (i.e., the one that retains custom recovery).
Worth a shot anyway (make a Nandroid backup, then wipe and flash the stock ROM and see how that behaves for a little bit...might shed some light on if overclocking is the issue).
Cheers!
It definitely was not an overclocking problem.
Tentatively I think I have it fixed. I flashed the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP then rooted again. Wiped dalvik and data and flashed xtrROM to see if it booted OK and it did. Wiped dalvik, wiped data and deleted the android.secure folder and flashed GSB. Everything seems to be working great.
The only downside is I lost my S-Off bootloader but I can fix that later. The upside is that my phone has not been this responsive and snappy in quite a while. I don't know if the IMG file is responsible for that or if it's the fact that when xtrROM loads it says it formats boot, system and cache.
I noticed the performance increase briefly the first time I flashed xtrROM then GSB but it crashed and started looping when I tried to install and set up an app from the SD card. After the process outlined above I again installed the app (Swiftkey) but when I tried to configure it the setup started looping. This was a problem encountered by many a while back and was determined to be a corrupt file. So I uninstalled the app and installed the newest version from the market even though I don't like it as much as the older version.
I'm gonna leave this open until I'm comfortable that it's fixed. Thank you all for the input and a huge THANK YOU to MongooseHelix!
As a side note I followed these instructions to get the S-Off bootloader... http://forum.xda-developers.com/showthread.php?t=725047 ... and I'm wondering if I actually have to do the whole thing again. Can I flash the PB00IMG.zip and get the S-Off bootloader again or should I do the whole thing?
Two days and not a single problem, so I thinks it's safe to say it's fixed. Thanks again for the help.
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
You really should s-off that puppy. It is pretty easy, and will get you out of messes.
Sent from my ADR6425LVW using Tapatalk 2
Jason L said:
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
Click to expand...
Click to collapse
I assume you're always wiping data and cache.
Have to tried Fix Permissions? I don't know if this rom has it in it's settings, but using others I've corrected some weirdness by wiping the cache and then running fix permissions.
Were you seeing the same thing with the stock rom? Or just using clean rom? Might try a different rom for a bit to see if the issues follow you there.
S-OFF isn't going to help you with this. It's perfectly fine to flash your boot image outside of Aman-Ra. I do it all the time.
Are you wiping everything between flashes?
I recommend using this - http://forum.xda-developers.com/showthread.php?t=1562176&highlight=clean
Flash it first and it wipes the needed partitions clean.
If you're still on the GB firmware, you need to flash the old firmware patch after the rom install also to get SD card access.
If none of the above helps and you're still on the GB firmware, set the phone back to stock using the GB RUU, otherwise you will have to s-off it so you can do the same.
Yep full wipes between flashes. I didn't keep the stock Rom for more than about 20 mins.
I didn't see a way with the debloated stock New leak to fix permissions. But with the 4.5 clean Rom I did that and it made no difference.
Delete
Sent from my ADR6425LVW using Tapatalk 2
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
I've been searching all morning to find another thread to see if this has been answered before. I was trying to install a GSM Rom onto my Rezound. The install failed at around 2 %. I'm almost positive I thought I was on the correct ICS firmware, when apparently I wasn't. So instead of trying to fight installing the rom over and over again. I had a back up rom that I installed instead. My problem I think is that I didn't go back and re wipe everything after the failed install.
Which I could slap myself for, but my problem is this. The phone can go into Hboot, which gives me hope not all is lost. But I can't go into recovery or boot up. The phone will only load the white HTC screen then just reboots over and over again. I've seen where it tries to load recovery but then just reboots. I'm not sure if I have to reload the RUU or what I have to do. If anyone has had this problem or knows of a thread on how to fix it I would greatly appreciate it.
Edit: Just a little about my phone if it helps.
Vigor Pvt S-OFF RL
HBOOT - 2.25.0000
Radio - 1.22.10.0421r/1.22.10.0424r
OpenDSP- v13.6.0.7611.00.0104
eMMC-boot
Since you can't get to recovery it might be time to just put an RUU on you card and let hboot install it. Then you can install a recovery and then one of your backups.
Or just reinstall recovery
Sent from my Vivid 4G using Tapatalk 2
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
I prefer CWM touch myself but the one from here not the official
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
mjones73 said:
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
Click to expand...
Click to collapse
Well I started off as I normally would, wiping data, wiping cache, wiping davlik, then installing. I tried one of the new JB roms Tron. But I couldn't get the GPS to work at all. So I stumbled across a GSM rom and went to install, it booted into it's own installation touch screen. I kept it simple not choosing many extras, then the last option was. Are you on ICS firmware? Which to my noobness, I've been running ICS roms since I acheived S-OFF. So I was pretty positive that I upgraded my firmware whenever I did that. So I chose Yes and it started to install, got to 2% and said it was done. Again I assumed the install had just failed and after having tried installing a GSM rom once before I had to go through and do it multiple times. I was tired and didn't feel like messing with it. So instead of rebooting, I went back into recovery and flashed another rom I had set on my SD card in case I didn't like the GSM. To which I think that my mistake came when I didn't either
A) Re-wipe my data, cache, davlik.
or
B) Restore my previous Rom from before.
So after the new rom installed and looked as everything went smooth. I selected reboot, the HTC white screen came up and the phone shut off. Then would power back up and display the HTC white screen and shut off again. So far the only thing I've been able to get it to do is the power cycle with the white screen and boot up in Hboot. But none of the options will work as the only thing it will do is power cycle. That's pretty much where I'm at until I can try reinstalling the RUU and flash the new(same) recovery.
The problem is nothing you've done there should have touched the recovery, that's why I find it weird.
I'd assume the rom asked which firmware you were on so it could installed the old firmware patch if needed.
Anyway, hopefully the RUU should straighten it out.
Well good news, re-installing the RUU fixed the phone. It re-locked my hboot, so I just finished unlocking that and re-flashing recovery. Thanks a bunch for all of your help. I greatly appreciate it !
So im fairly new to unlocking, flashing, etc. I have a HTC One M8 for AT&T that im trying to unlock to use with different carriers. After reading a bit I realized that I had to unlock my bootloader, root, install s-off before I could achieve my goal. I used htc-one.wonderhowto. com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444 to root and unlock my bootloader. Followed the guide to a T and all was fine. Then I was going for S-Off and here's where I encounters my problems. I used htc-one.wonderhowto. com/how-to/get-s-off-your-htc-one-m8-install-custom-firmware-mods-0154461 guide and this is where I believe I fudged up bad. Step one says to download InsertCoin from insertcoin-roms. org/category/devices/onem8 this link. I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM and that's why im having this problem but im not sure. I followed each step with the exception to Step 3 which is also where I fudged up. I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything. At step 5 my life changed forever..lol.. but when I flashed it , it said failure. I tried to follow the steps again but it kept failing to flash. So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. Which says ***unnlocked*** and ***tampered*** at the top and im stuck. Please someone help me and tell me what to do.
I recently deleted my OS by my stupidity. I fixed the issue by side loading a stock Rom via adb/twrp sideload. Saved me. There are tutorials on how to do this. Just Google search. You could also put a stock Rom on an external sd and flash that way. Don't have a link to the stock Rom I used, but it's in the resources thread in general section. Hope this works for ya
Sent from my HTC One_M8 using XDA Free mobile app
vansslamcityjam said:
I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM
Click to expand...
Click to collapse
The file you downloaded is if you were already on InsertCoin 4.0.6, and updating to version 4.0.7, which was not the case for you. You should have downloaded the full ROM, and that is likely why the flash failed.
If you ever have any doubt about what you are flashing, this should be a red flag to STOP and either read and research some more, or come on here and ask.
vansslamcityjam said:
I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything.
Click to expand...
Click to collapse
That is why you make a TWRP backup before wiping anything.
vansslamcityjam said:
So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. .
Click to expand...
Click to collapse
Did you specifically wipe system in TWRP? If so, that is where the OS is stored, so of course wiping it means you have no OS.
I do not advocate wiping system when flashing ROM, especially if you are new to this. Reason being, it already gets wiped when you flash a ROM anyway (so its redundant). Also, if the ROM fails to flash, you will still have a working OS if you did not wipe system manually. As stated on the wipe screen in TWRP, the default wipe (data, cache, and Dalvik) is all that is usually needed. It says this for good reason.
All you need to do is download a ROM to your computer, and either adb push to the phone, sideload flash, or copy it to a removeable MicroSD card using a USB card reader. Then flash in TWRP.