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.
Related
I am a relative noob at flashing roms and rooting phones, but last night I ran into an issue. My phone was having all sorts of problems so I was going to put it back to factory, then start from scratch. I then decided to just flash a different rom. here is what happened.
I deleted SuperSU - this was done as part of the process to unroot and put back to factory, after this step I decided to flash a different rom
Put new ROM on phones internal memory as well as SD card
Wipe data
wipe cache and delvic cache
install new rom
Black screen
In an attempt to unbrick I relocked my bootloader.
Now, my phone can power on (Give white screen and HTC logo), then go black, and I can access Recovery mode. That is all.
I have plugged the phone to my computer and tried running the RUU, but the RUU will not recognize the phone.
I am not sure what to do to unbrick my phone and get it working again. Any and all help would be most appreciated!
Sorry I can't be more eloquent with my words, but I'm at work. I will be responding throughout the day, though.
thanks again so much to anyone that can help!
Try running it straight from bootloader
I loaded into Bootloader, selected Fastboot(USB), ran the .exe and it still won't recognize the phone. However, I did get recovery unlocked again. So I can get into recovery mode, flash all the ROMs I want, mount and unmount, yet still everytime I flash a new ROM it still boots to a black screen. Am I doing this right?
Try a Rom with kernel installer
Thanks! Since I am still a little new could you tell me how I would spot a ROM with kernel installer or could you point me to any one that could work? From then, it's the same process as flashing any other ROM? Do I need to do something with the kernel?
Meanbean and stock with goodies are the 2 that I'm certain of. Meanbean needs to be flashed twice the first time
Thanks so much for your help, I will post my results soon!
Failed
Here's what it says. Sorry for the blurry picture. I followed directions closely.
What version of recovery are you using? You may need to update it. Assuming you have a pc, try mounting the internal memory to pc through twrp. Windows will automatically tell you to format if its damaged
2.1 Updating now
omg it finally worked! Updated TWRP using fastboot and flashed MeanBean. Thank you so much!!!
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. :|
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
ronin_rone said:
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot.img?
gleggie said:
Have you tried fastboot flashing the boot.img?
Click to expand...
Click to collapse
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
ronin_rone said:
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
Click to expand...
Click to collapse
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
dragonstalker said:
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
Click to expand...
Click to collapse
I kinda understand what you are saying, but the other problem I have is.... When running adb my phone is not listed in the adb devices, although it is listed in the usb devices. Not sure what to do about that.
Are you in charge only mode on the phone?
Is usb debugging enabled?
USB debugging was selected prior to this incident and it was on charge only as well. It was not connected as a usb drive. I cannot get into the settings of the phone to find out what it is now or if its changed.
I would suggest going S-Off, it will make flashing a whole lot easier. As for getting back to a usable state, you should be able to flash a PH98IMG in bootloader. If anything, flash an RUU and go from there.
I could use some advice on any options I have for trying to salvage this Rezound. Here is what I know:
The Symptoms:
-Was completely stock and actively used phone
-Charging port began misbehaving. I believe it may be loose/damaged. It will only charge reliably on one particular USB cable (an Amazon Basics, but only one of my dozen or so of those)
-Started randomly rebooting
-Did a factory reset, seemed to help for a while, then it started rebooting again
-It started getting stuck in a bootloop. HTC screen up ~2s -> black ~0.2s -> HTC screen up ~28s -> black ~5s -> repeat. Does this for a variable amount of time, sometimes minutes, sometimes hours before it will actually boot all the way into the OS
-If it does boot, it usually does not last long before it reboots and will typically get stuck again
The Facts:
-I can into bootloader with no issues
-Because I can get into bootloader, I went ahead and unlocked and flashed TWRP 2.6.3.0
-I can get into TWRP and use all of it's functions reliably
-I decided to try wiping data and cache then system several times, flashing a custom ROM (Global_OTA_RED_DESENSED-v1.0) in TWRP and then flashed boot.img with fastboot, but the new ROM has the same issue. In fact I've yet to boot all the way into the ROM
-Does the same thing with the SD card and SIM card removed
My Guesses:
Based on the fact that it is rock solid in the bootloader and in recovery, I thought that it was possibly corruption on system or boot, which is why I tried to install a custom ROM. Now I'm leaning towards bad memory, either where system or boot reside, possibly data or even RAM, perhaps caused by electrical damage from the charge port issues. I just don't understand why I've not seen any sort of read/write errors while doing anything with fastboot or recovery.
At this point I don't know what to do beyond throwing it out. If anyone has any fresh ideas for salvaging this thing, I'd appreciate it.
If not, any ideas for replacing are also appreciated. A new phone isn't really in the budget at the moment, particularly because I desperately want to get away from Verizon (most likely will lose unlimited data if we I start swapping and don't really have $600-$700 to throw around at the moment. I have 4 lines to move and the Rezound line is on contract, so I'm sort of feeling the rock one side and a hard place on the other.
Thanks in advance, folks!
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
acejavelin said:
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
Click to expand...
Click to collapse
Thanks for the suggestion. I had let the phone sit turned off all afternoon to charge and tried this after work. I grabbed Amon Ra from http://forum.xda-developers.com/showthread.php?p=37362226, made sure to wipe boot in excess and installed the ROM you linked. It booted up on the first try unlike the last ROM, and I've been able to load some things on it and delete some bloat for a bit with no reboots. I've even powered off and went back into recovery to do a backup, and had a successful reboot afterwards. I don't know if it was wiping boot that did it, but I hope it holds. I'll keep you posted, and either way, thanks again.
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
"Haus" said:
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
Click to expand...
Click to collapse
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
acejavelin said:
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
Click to expand...
Click to collapse
I'm still on the stock ROM. Unfortunately it quit booting again.
"Haus" said:
I'm still on the stock ROM. Unfortunately it quit booting again.
Click to expand...
Click to collapse
Hmm... Honestly looking like a hardware issue... Sorry bro
Sent from my Nexus 4 using Tapatalk