Last night with the assistance of a friend I was able to load Newt's ROM onto my phone 'successfully,' at least, that's what we thought. Initially it wouldn't allow the use of Wifi and we were able to discern that was because we flashed the wrong link for the patch, so it was an older boot.img. After we corrected that mistake, I was able to leave the MikMik bootup screen and the WiFi was working perfectly. After waking up from that, I restarted the phone twice throughout the day with no problem, it booted up fine, as if the phone wasn't rooted at all. Since it was working 'properly' I made a nandroid of the file, and that's when it all went downhill. After making the nandorid (I only used the default four boxes), the phone wouldn't reboot; it stayed stagnant on the Mik-Mik boot-up screen. We tried clearing the cache and Dal-vik Cache; re-flashing his ROM completely (flashed it twice to make sure the WiFi would stick) with the 3.2.1 patch and then rebooting the phone. It still won't leave the Mik-Mik boot-up screen. It puzzles me because it was working fine until I made the nandroid. :l Recap: Tried clearing Cache and Dal-Vik Cache, resetting permissions to ensure it wasn't trying to pull ID from stock, re-flashed ROM with 3.2.1 patch. Any ideas? Much appreciated.
Edit: Forgot to mention I'm S-On
Edit two: Just cleared off the SD card and started fresh with no luck. I flashed the ROM twice, then the 3.2.1.v2 patch, and then did "fastboot boot boot.img" in my commands prompt to start the phone, but it still gets stuck on the Mik-Mik loading screen (Before flashing the ROM I cleared the cache and Dilvik Cache). :l
Kelton Rivas said:
Last night with the assistance of a friend I was able to load Newt's ROM onto my phone 'successfully,' at least, that's what we thought. Initially it wouldn't allow the use of Wifi and we were able to discern that was because we flashed the wrong link for the patch, so it was an older boot.img. After we corrected that mistake, I was able to leave the MikMik bootup screen and the WiFi was working perfectly. After waking up from that, I restarted the phone twice throughout the day with no problem, it booted up fine, as if the phone wasn't rooted at all. Since it was working 'properly' I made a nandroid of the file, and that's when it all went downhill. After making the nandorid (I only used the default four boxes), the phone wouldn't reboot; it stayed stagnant on the Mik-Mik boot-up screen. We tried clearing the cache and Dal-vik Cache; re-flashing his ROM completely (flashed it twice to make sure the WiFi would stick) with the 3.2.1 patch and then rebooting the phone. It still won't leave the Mik-Mik boot-up screen. It puzzles me because it was working fine until I made the nandroid. :l Recap: Tried clearing Cache and Dal-Vik Cache, resetting permissions to ensure it wasn't trying to pull ID from stock, re-flashed ROM with 3.2.1 patch. Any ideas? Much appreciated.
Edit: Forgot to mention I'm S-On
Edit two: Just cleared off the SD card and started fresh with no luck. I flashed the ROM twice, then the 3.2.1.v2 patch, and then did "fastboot boot boot.img" in my commands prompt to start the phone, but it still gets stuck on the Mik-Mik loading screen (Before flashing the ROM I cleared the cache and Dilvik Cache). :l
Click to expand...
Click to collapse
First...are you on GB Firmware or ICS firmware???
Look at the hboot screen and tell me what you have for hboot and radios, please.
topgun1953 said:
First...are you on GB Firmware or ICS firmware???
Look at the hboot screen and tell me what you have for hboot and radios, please.
Click to expand...
Click to collapse
Hboot: 2.21.0000
Radio: 1.22.10.0310r/1.22.10.0308r
Kelton Rivas said:
Edit two: Just cleared off the SD card and started fresh with no luck. I flashed the ROM twice, then the 3.2.1.v2 patch, and then did "fastboot boot boot.img" in my commands prompt to start the phone, but it still gets stuck on the Mik-Mik loading screen (Before flashing the ROM I cleared the cache and Dilvik Cache). :l
Click to expand...
Click to collapse
its supposed to be
Code:
fastboot [I][B]flash[/B][/I] boot boot.img
AshtonTS said:
its supposed to be
Code:
fastboot [I][B]flash[/B][/I] boot boot.img
Click to expand...
Click to collapse
I've tried doing "fastboot flash boot boot.img," but it still perpetuates on the mik-mik screen.
Kelton Rivas said:
Hboot: 2.21.0000
Radio: 1.22.10.0310r/1.22.10.0308r
Click to expand...
Click to collapse
All right...that is ICS firmware. Not the 'latest', but still ICS firmware. That may be the source of the problem as I believe the flashable boot.img is based on later firmware.
JUst to make sure..you flashed the 3.2.1 Rom, THEN the RLS 2+ boot.img, and then finally the 3.2.1 patch ? The order might make a difference.
If this is what you've done, then I'd recommend flashing the latest leaked RUU so you'd have the latest firmware and then it should work. If you do that, be sure to do a FACTORY RESET in hboot immediately after running the RUU. Failure to do so, might result in data probs.:crying:
topgun1953 said:
All right...that is ICS firmware. Not the 'latest', but still ICS firmware. That may be the source of the problem as I believe the flashable boot.img is based on later firmware.
JUst to make sure..you flashed the 3.2.1 Rom, THEN the RLS 2+ boot.img, and then finally the 3.2.1 patch ? The order might make a difference.
If this is what you've done, then I'd recommend flashing the latest leaked RUU so you'd have the latest firmware and then it should work. If you do that, be sure to do a FACTORY RESET in hboot immediately after running the RUU. Failure to do so, might result in data probs.:crying:
Click to expand...
Click to collapse
I didn't realize I was on expired firmware, can you send me the instructions and link(s) for flashing it? I'm still somewhat new to this flashing business, I only started last night. Uhm, no, for order I went: Newt's ROM(x2), 3.2.1.v2 patch, then RLS2+ Boot.img. I have to do the boot.img last because I'm forced to shut down the phone and then go to that setting where "fastboot USB" is in red.
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.
OK, so I got a little "cocky" and flashed to another ROM. Apparently it wasn't capability with Rezound as it didn't boot. When I tried to boot into recovery, only could select Hboot. That lead to a loop. Took out the memory card, the SIM chip, battery, cover all to no avail. I finally got Scott's rom that was working back on the phone. But still having issues, the phone constantly reboots. I get to the home screen and/or lock screen it works but then freezes and resets. I no longer have the ability to boot into recovery. When I connect to the MAC (or PC) it says charging only.
When able tried a factory reset but that didn't do anything, I can no longer get to that screen. Did a nandroid backup before playing around with the new ROM but can't figure out how to get to it.
HELP... need your help pretty please
Did you just do a factory reset before you flashed Scott's rom or did you wipe /system as well? Also make sure debugging is enabled as well. Have you tried to boot to recovery with adb?
Sent from my ADR6425LVW using Tapatalk 2
DOOD YOUR PHONE IS TOTALLY BORKED. PANIC!
Kidding
in all seriousness. What firmware are you on. ICS or GB firmware?
I.E. have you run an RUU, are you s-off or s-on
if you are unsure, just type out like the first 5 lines in HBOOT.
Did you just do a factory reset before you flashed Scott's rom or did you wipe /system as well? Also make sure debugging is enabled as well. Have you tried to boot to recovery with adb?
Click to expand...
Click to collapse
When I was able to select something other than HBOOT I did a factory restore but didn't notice anything different. Also manually deleted. However now when I try to go into recovery mode, only HBOOT is selected and the up/down button doesn't work.
Not sure how to boot to recovery with adp.
Appreciate your wisdom
What firmware are you on. ICS or GB firmware?
I.E. have you run an RUU, are you s-off or s-on
if you are unsure, just type out like the first 5 lines in HBOOT.
Click to expand...
Click to collapse
The last time the phone worked, was running Scott's Clean Rom 4.5, Android 4.0.3
Kernel ver: 3.0.16-g8fa42b5
I believe it's s-off but it's fighting me to get back to the recovery screen
Sadly I'm not sure about RUU
What ROM was it if you don't mind me asking? I mean was it at least for the Rezound if so then it shouldn't be that bad..
I didn't do anything different this morning than last nite, but the phone came back to life. I restored the nadroid backup and it appears to be working. Though getting an error about the SIM card after a reboot.
Don't know what I did wrong when trying to flash or if the ROM just wasn't compatible.
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 !
Hey all,
Running CM 10.1 Wild For The Night and I noticed my WiFi had disconnected. When I went to the WiFi settings, the toggle was greyed out and the screen was stuck on 'turning Wifi on'. I rebooted and the screen was still stuck. I wiped Dalvik and cache, and when I rebooted, WiFi was off. I tried turning it back on and the same situation happened. Completely wiped and reflashed, same problem. Today I flashed a new ROM (MiUi 3.2.8), same problems persist. Im on HBOOT 1.5 S-ON (I know, I know). WiFi did work before with the ROM for at least a week. Is it possible the WiFi chip is borked?
a7nachmb said:
Hey all,
Running CM 10.1 Wild For The Night and I noticed my WiFi had disconnected. When I went to the WiFi settings, the toggle was greyed out and the screen was stuck on 'turning Wifi on'. I rebooted and the screen was still stuck. I wiped Dalvik and cache, and when I rebooted, WiFi was off. I tried turning it back on and the same situation happened. Completely wiped and reflashed, same problem. Today I flashed a new ROM (MiUi 3.2.8), same problems persist. Im on HBOOT 1.5 S-ON (I know, I know). WiFi did work before with the ROM for at least a week. Is it possible the WiFi chip is borked?
Click to expand...
Click to collapse
Your kernel isn't flashing properly so the WiFi driver doesn't match.
To get things back in sync start your recovery with the following fastboot command:
fastboot boot recovery.img
Click to expand...
Click to collapse
Once booted into recovery wipe all partitions except SD card and make sure SmartFlash (S-ON) is disabled in the tools menu if using 4EXT. Then flash the entire ROM as you normally would, except this time the boot partition (kernel) will be flashed from recovery because of the way it was started.
ramjet73
ramjet73 said:
Your kernel isn't flashing properly so the WiFi driver doesn't match.
To get things back in sync start your recovery with the following fastboot command:
Once booted into recovery wipe all partitions except SD card and make sure SmartFlash (S-ON) is disabled in the tools menu if using 4EXT. Then flash the entire ROM as you normally would, except this time the boot partition (kernel) will be flashed from recovery because of the way it was started.
ramjet73
Click to expand...
Click to collapse
Thanks for the reply! Just tried it. It's been a long time since I've messed with ADB and fastboot. I booted the device into whatever the white screen thing that isn't recovery is called (ha ha), performed the fastboot command from the folder I saved it in on my computer, ran the command, and it booted into the 4ext. I disabled Smartflash, wiped everything, and flashed, and now its hanging on the boot screen.
a7nachmb said:
Thanks for the reply! Just tried it. It's been a long time since I've messed with ADB and fastboot. I booted the device into whatever the white screen thing that isn't recovery is called (ha ha), performed the fastboot command from the folder I saved it in on my computer, ran the command, and it booted into the 4ext. I disabled Smartflash, wiped everything, and flashed, and now its hanging on the boot screen.
Click to expand...
Click to collapse
What ROM are you flashing? Some people had problems booting ICS Sense ROM's with hboot 1.5 and S-ON. I never had that problem myself, but if you want to stay on hboot 1.5 and not go for S-OFF it might be worth it to relock your bootloader and flash the 2.17.651.5 RUU to make sure everything is in sync. Flashing the stock ROM will also let you confirm whether your Wi-Fi is working or not.
You'd really be better off going for S-OFF and I have a guide that can help here.
ramjet73
Ah, okay I got MIUI 3.2.8 to bot using the fastboot recovery method. Still having the WiFi issue. I've never messed with logcats before, how would I go about posting the relevant bit of text from this enormous jumble that happened when I ran adb logcat?
a7nachmb said:
Ah, okay I got MIUI 3.2.8 to bot using the fastboot recovery method. Still having the WiFi issue. I've never messed with logcats before, how would I go about posting the relevant bit of text from this enormous jumble that happened when I ran adb logcat?
Click to expand...
Click to collapse
I think that ROM might be having WiFi issues per this post by DH.
You could try flashing the Sense version of the Mac kernel after the ROM is flashed and that might fix it.
ramjet73
ramjet73 said:
I think that ROM might be having WiFi issues per this post by DH.
You could try flashing the Sense version of the Mac kernel after the ROM is flashed and that might fix it.
ramjet73
Click to expand...
Click to collapse
Hm. I had terrible data connectivity on MIUI so I'm back on CM10.1. The things that lead me to believe the problems are deeper than kernel/ROM are
1. The issue happened abruptly. After using CM10.1 for a week or so with no wifi issues, suddenly this happened. Not even after a reboot, it just happened.
2. Its happening on multiple ROMs with full wipes and stuff in between.
Would a logcat not be helpful in diagnosing the issue? I just don't know much about them. Do I need to connect my phone via USB and then attempt to recreate the problem in order for the correct info to be in the log? As I said before, I can't get my wifi to turn off without wiping cache and dalvik, even after a reboot its still giving me the 'turning wifi on' message.
a7nachmb said:
Hm. I had terrible data connectivity on MIUI so I'm back on CM10.1. The things that lead me to believe the problems are deeper than kernel/ROM are
1. The issue happened abruptly. After using CM10.1 for a week or so with no wifi issues, suddenly this happened. Not even after a reboot, it just happened.
2. Its happening on multiple ROMs with full wipes and stuff in between.
Would a logcat not be helpful in diagnosing the issue? I just don't know much about them. Do I need to connect my phone via USB and then attempt to recreate the problem in order for the correct info to be in the log? As I said before, I can't get my wifi to turn off without wiping cache and dalvik, even after a reboot its still giving me the 'turning wifi on' message.
Click to expand...
Click to collapse
You're best bet is probably to flash the 2.17.651.5 GB RUU at this point and check your WiFi in a stock configuration since not everyone is having these problems. You will need to relock your bootloader before flashing the RUU, then unlock and re-flash your recovery afterwards, but you can use the unlock .bin file you have already.
ramjet73
ramjet73 said:
You're best bet is probably to flash the 2.17.651.5 GB RUU at this point and check your WiFi in a stock configuration since not everyone is having these problems. You will need to relock your bootloader before flashing the RUU, then unlock and re-flash your recovery afterwards, but you can use the unlock .bin file you have already.
ramjet73
Click to expand...
Click to collapse
Willing to give this a go. Is there info on how to relock and unlock with the unlock .bin? Thanks again for the quick replies
a7nachmb said:
Willing to give this a go. Is there info on how to relock and unlock with the unlock .bin? Thanks again for the quick replies
Click to expand...
Click to collapse
Everything you need should be in mpgrimm2's guide.
Once you relock and flash the RUU you can boot into the stock ROM and test WiFi. If everything checks out you can root your phone the way you did the first time, or take it to Sprint for a replacement if it doesn't work.
ramjet73
ramjet73 said:
Everything you need should be in mpgrimm2's guide.
Once you relock and flash the RUU you can boot into the stock ROM and test WiFi. If everything checks out you can root your phone the way you did the first time, or take it to Sprint for a replacement if it doesn't work.
ramjet73
Click to expand...
Click to collapse
Awesome, thanks!
dude, just make it easy on you ...
flash any ics sense 3.6 rom from fastboot and it is going to get your wifi going.
you'd be stuck here until you are s-off ... so no fancy roms for you, sorry~
I can confirm
I'm using the same rom, miui walking dead ICS... Tried to flash it a couple of times.
Seems when turning the wifi toggle off, the whole networking in android locks up. It'll do this on it's own if you have wifi set to disable on sleep. I am running S-OFF Hboot 1.58, and what's really interesting is dropping to terminal and running, netcfg, you get nothing. It locks up as well, and trying to run ifconfig wlan0 down/up gives you nothing. Ctrl-C to cancel doesn't respond either. I don't see anything in logcat, so I think it's a kernel issue.
Normally, you can drop to terminal and su, then 'shutdown -h now' and have the phone shut off within a second or two, but once the wifi locks, it won't shut down, restart, anything. You have to pull the battery. Once the battery is pulled, and you boot back up, wifi will be toggled off, and you can toggle it back on fine, at least in my experience so far.
I'd really be interested in what digitalhigh says, but I can't post on the developer forum yet. :|
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