Related
Ok, I have a rezound, unlocked and rooted with Amon Ra with the superuser binaries updated, all after installing the Global ICS RUU. I've been running this way pretty much since a few days after the Global RUU came out. Never had any problems or issues. Love this phone (except battery life but whatever). This morning before taking it off the charger I had it reboot (which I normally do every few days) and it did not reboot. It got stuck on the white HTC screen. The screen would come on, and then blink for a sec only to stay stuck on the HTC screen. No beats audio boot animation. I'm S-ON by the way. I use Mac so I was never able to get a windows computer to S-off, but I haven't wanted to flash any Roms since my days on the Dinc. I didn't have time to mess with it this morning so I just pulled the battery to shut it off. Now that I have a few minutes, I tried to see if it would boot, and same thing. Pulled the battery again, and powered up into the boot loader. Tried to enter recovery from there, and it just went blank. Pulled battery again, and tried it again. Same blank screen with no response from power button or anything. Now it is completely dead. Won't even go into bootloader. Won't even light up on the charger. SOME times when plugging it in it will light up for 5 seconds, but then turn off. Tried it with the battery out and pluggin it in to get into bootloader that way and nothing.
Is it completely fried? I bought it from VZW last April so it should be still under the 1 year manufacturer warranty. I'm hoping to find a fix as I haven't backed up in a while, but if not, hopefully they will replace it.
Even though I have a mac, it is set up to run adb commands, but everytime I try reboot or anything it just says "waiting for device". Clearly as it is not powered on.
Any ideas or help????
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
I just tried to do that and I can't get into the RUU zip file. I attached the kernel from the nandroid I made right after I ran the global RUU (4.03.605.2). If that's the version you are on you can try flashing this kernel and see if that does it.
Ugh... having trouble uploading it. If you have a nandroid from your global RUU you can pull the boot.img from that and flash it.
feralicious said:
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't know how to do that. I am not a newbie, but there is a lot I don't know. I follow directions well (being able to do the adb stuff with a mac) but pulling the kernel out of an RUU is not something I've ever read about doing.
I've read many threads about charging issues and what not, but I have the stock battery and the extended with a Seidio external charger so I know they both have plenty of juice in them. I know VZW will replace the thing, but I have stuff I'd rather not lose if I can fix it. If you could walk me through pulling the kernel out of the RUU.
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Once you have the kernel, pull the battery and put it back then boot into bootloader and put phone in fastboot. Attach to Mac, then use fastboot and this command:
fastboot flash boot boot.img (I named the one I'm trying to upload to ruuglobal_boot.img, you can either rename it or just flash using that name instead of boot.img)
feralicious said:
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Click to expand...
Click to collapse
I hopefully have a nandroid backup on the SD card, but I will tell you it's been a long time since I installed the RUU. I've been out of the rom'ing rooting/ fiddling game for a long time. I haven't had the time recently and apparently it ain't like riding a bike. I've had to read a ton today to refresh myself.
My dinc was so easy, you didn't have to know a whole lot. Just download a zip, check the MD5, and flash it. Rezound was more complicated with the S-on, so I didn't even bother getting started....just the RUU to ICS before it was official, and then the RUU to Global. So yes, I am running the RUU you listed.
Anyway, I don't have a way of reading the SD card until I get home to find the nandroid.....and I've never looked at a nandroid made with Amon Ra....I only was used to CWM on the Dinc.
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
feralicious said:
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
Click to expand...
Click to collapse
Was there an OTA recently?
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now. (Mine had a cracked screen so I couldn't get it replaced under warranty and had no insurance.)
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
feralicious said:
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now.
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
Click to expand...
Click to collapse
DAMN. Oh well. They will replace it most likely, and it seems like the easiest route to take. My wife's bootloader fried itself on here Moto D2 last year and it was LONG passed warranty and they replaced it......It was completely stock, but they had no way of knowing, so I'm sure they will send me a replacement phone. I just hope they still have Rezounds to send. I don't want to get stuck with something they determine for me because there are no more rezounds.
My wife's rezound is completely stock, never unlocked so I'll see if she got the update.
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
318sugarhill said:
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
Click to expand...
Click to collapse
Ok, I loaded the boot.img and no dice. Still stuck at the white HTC screen. This is frustrating now. Now I do NOT want to go to the VZW store as my bootloader says tampered unlock. I guess I can always try to run the RUU again.
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
Well, if I can get into the bootloader I can relock to run the RUU correct? I hate to have to lose everything, but I do need the phone, and if it was toasted, I would have to start over with a replacement anyway. Nothing on there can't be replaced except some pictures, but it won't kill me. Just a hastle. Should I try to relock and run the RUU? or should I try to load a Rom like Nils business sense for S-ON? I was considering trying it.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
I gave up bro. This sounds way over my head. I relocked and am running the Global RUU again. I will unlock again and load amon ra, and run the su binary zip I have again. Not worth this much time. My 3 year old is tearing up the place while I bury my face in my computer.
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
feralicious said:
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
Click to expand...
Click to collapse
I tried pushing the recovery again, I tried the boot (all three that were in the nandroid backup) and some other things on here I saw. Nothing worked. Just stayed at the white HTC screen. Relocking and running the RUU made the phone usable again. Thanks for your help, but my stuff is gone. After spending what feels like forever setting up the phone to make it usable again, it will all be gone when I unlock again. Don't have time to do that tonight, but this weekend I'll get to it.
Not everything is gone. I do have titanium but I haven't backed up in a while, so they will be old backups, but still backups. Lesson learned....schedule backups more frequently.....reset my dropbox to auto upload pics again. Turned it off Christmas day, and never turned it back on. The cloud is there for a reason right?
Hey there.
To preface, I'm not new to flashing, just new to Samsung and Odin. (former CrackFlasher from the original D1 and Bionic/Razr days)
I got my S4 a couple months ago, rooted it and installed TWRP immediately and it had been running great ever since. I'm still on MDK and have not taken the ME7 update.
Got the bug again and decided to give Hyperdrive RL7 a shot. Downloaded it, rebooted into TWRP, flashed it, rebooted and let it sit for a few hours last night.
Opened it up this morning, everything worked GREAT! I know how these things work - new ROM, coming from stock, so I started from a clean slate and didn't use my TiBu backup to restore, I literally went and redownloaded every single app I use direct from Google Play Store.
I have to say the ROM was perfect - fast, smooth and awesome functionality and even some customization that gives previous Razr AOKP a run!
That's where the fun ends though - I rebooted the phone and ended up on the Samsung Unlocked with an unlocked padlock, and it wouldn't budge.
So, no problem, boot into TWRP, wipe and install Hyperdrive again.
NOPE. So I read that some people were having problems with TWRP, so I decided to give the older 2.5 version a try - Odin'd it to the phone and FAIL.
So someone else had mentioned they had luck with OUDHS. Odin'd it to the phone, but it wouldn't take it, so I found a download for OUDHS that's flashable from within "recovery" and flashed it from within TWRP, fully believing that's what it was meant for. THAT was a horrible idea that resulted in a boot that shows yellow text that states that there is software that isn't Verizon verified and to take my phone into the local Verizon store.
I had a feeling about flashing a new recovery from within a recovery, but I also thought it was pretty straightforward to flash back to stock... that's not been the case so far - the VRUAMDK_No Wipe file doesn't want to do anything because it's a .tar inside a .zip, opening the .zip in WinRAR, 7Zip and even WinZip doesn't open anything... so I can't even flash to stock.
Now I have NO recovery (no TWRP), and everything I've tried to push to the phone via Odin fails - with the exception of \SCH-I545_MD2_423399_Kernel.tar.tar which is what was used to root the phone to being with, and that only gets me back to the Samsung Custom unlocked padlock screen.
PLEASE HELP!
(thanks in advance for all input)
***EDIT:
I redownloaded the VRUAMDK_No flash 2 more times and got one that opened with WinRAR (still wouldn't open with 7z or WinZip, and after pushing it with Odin 4 times, the last time it finally went through.
I know a bad download was part of the first problem with not being able to open the original zip file to extract the md5 from within, but there was NO difference whatsoever in the 4 times I kept poking it with Odin when it finally took.
I successfully booted to stock, then rooted, then flashed TWRP 2.5, then installed Hyperdrive RLS8 successfully.
For anyone that's reading this that may have the same or similar problem, first try to download the ROM again and again (and again if necessary) - until you can open it with 7z or WinRAR, you don't have a valid, good download of it.
Second, keep poking it with Odin. It was my 4th try when it finally worked. --literally no changes in between, nothing changed at all, it just worked out of random on the 4th try.
/thread
Hope that helps someone. Glad I wasn't in more of a hurry!
Psychlone said:
Hey there.
To preface, I'm not new to flashing, just new to Samsung and Odin. (former CrackFlasher from the original D1 and Bionic/Razr days)
I got my S4 a couple months ago, rooted it and installed TWRP immediately and it had been running great ever since. I'm still on MDK and have not taken the ME7 update.
Got the bug again and decided to give Hyperdrive RL7 a shot. Downloaded it, rebooted into TWRP, flashed it, rebooted and let it sit for a few hours last night.
Opened it up this morning, everything worked GREAT! I know how these things work - new ROM, coming from stock, so I started from a clean slate and didn't use my TiBu backup to restore, I literally went and redownloaded every single app I use direct from Google Play Store.
I have to say the ROM was perfect - fast, smooth and awesome functionality and even some customization that gives previous Razr AOKP a run!
That's where the fun ends though - I rebooted the phone and ended up on the Samsung Unlocked with an unlocked padlock, and it wouldn't budge.
So, no problem, boot into TWRP, wipe and install Hyperdrive again.
NOPE. So I read that some people were having problems with TWRP, so I decided to give the older 2.5 version a try - Odin'd it to the phone and FAIL.
So someone else had mentioned they had luck with OUDHS. Odin'd it to the phone, but it wouldn't take it, so I found a download for OUDHS that's flashable from within "recovery" and flashed it from within TWRP, fully believing that's what it was meant for. THAT was a horrible idea that resulted in a boot that shows yellow text that states that there is software that isn't Verizon verified and to take my phone into the local Verizon store.
I had a feeling about flashing a new recovery from within a recovery, but I also thought it was pretty straightforward to flash back to stock... that's not been the case so far - the VRUAMDK_No Wipe file doesn't want to do anything because it's a .tar inside a .zip, opening the .zip in WinRAR, 7Zip and even WinZip doesn't open anything... so I can't even flash to stock.
Now I have NO recovery (no TWRP), and everything I've tried to push to the phone via Odin fails - with the exception of \SCH-I545_MD2_423399_Kernel.tar.tar which is what was used to root the phone to being with, and that only gets me back to the Samsung Custom unlocked padlock screen.
PLEASE HELP!
(thanks in advance for all input)
***EDIT:
I redownloaded the VRUAMDK_No flash 2 more times and got one that opened with WinRAR (still wouldn't open with 7z or WinZip, and after pushing it with Odin 4 times, the last time it finally went through.
I know a bad download was part of the first problem with not being able to open the original zip file to extract the md5 from within, but there was NO difference whatsoever in the 4 times I kept poking it with Odin when it finally took.
I successfully booted to stock, then rooted, then flashed TWRP 2.5, then installed Hyperdrive RLS8 successfully.
For anyone that's reading this that may have the same or similar problem, first try to download the ROM again and again (and again if necessary) - until you can open it with 7z or WinRAR, you don't have a valid, good download of it.
Second, keep poking it with Odin. It was my 4th try when it finally worked. --literally no changes in between, nothing changed at all, it just worked out of random on the 4th try.
/thread
Hope that helps someone. Glad I wasn't in more of a hurry!
Click to expand...
Click to collapse
Hyperdrive for me was fast and good and all, but i found it to be a tad unstable, just like you experienced. Beans and Bonestock are very stable tho.
Ok, I had carbon rom on my DNA (Verizon). It was getting buggy on me so I decided to return to ViperDNA. However TWRP continuosly failed to flash the file. No matter what I tried. Eventually I formatted my phone thinking that would help me install it. Well no luck. Now however I still cannot flash any of the roms I have tried and my phone boots straight into recovery. Any ideas on how to fix my phone?
EDIT:
Well, I cannot seem to figure out how to delete this post. However I ended up downloading CM 10.2 through my pc and put it on a usb. Then flashed it from the usb and it worked. I must have had corrupted files
EvolutionXJ said:
Ok, I had carbon rom on my DNA (Verizon). It was getting buggy on me so I decided to return to ViperDNA. However TWRP continuosly failed to flash the file. No matter what I tried. Eventually I formatted my phone thinking that would help me install it. Well no luck. Now however I still cannot flash any of the roms I have tried and my phone boots straight into recovery. Any ideas on how to fix my phone?
EDIT:
Well, I cannot seem to figure out how to delete this post. However I ended up downloading CM 10.2 through my pc and put it on a usb. Then flashed it from the usb and it worked. I must have had corrupted files
Click to expand...
Click to collapse
Are you trying to flash sense 4 viper or sense 5 viper?
Hello people!
First of all - Happy New Year!
Okay, my problem is this:
I gave my phone to a person who knows what he's doing, to change my ROM (switched from stock ROM to CM10).I wasn't there and didn't know what he did but I was glad that he did it. The ROM was still a beta (not sure how is it called for the ROMs) version and I had some problems with the camera, chrome and messanger were closing even if I didn't want them and many other problems which i dont remember now. This was the reason I wanted to change this CM10 to another ROM , but I had some problems with changing it. Took me like 4 hours (eventho my phone was unlocked) and i almost gave up when I tried for last time to install CM again and it worked! I don't know what I did because It was long ago. Anyways to my main problem:
Before 2 days I told myself ok now is the time to change the ROM (New Year - new ROM ). I started doing everything that the post I found says ( I can't give you link, but it's for dummies). All I did wrong was not downloading the whole folder with the boot.img (which I still don't have) ,but only the file boot.img from 2shared. I had to do the last step, because the device entered a Bootloop. Since then I Power ON my phone ,but all it does is to show the "HTC quitely brilliant logo. I tried to reinstall the Viper ROM , but nothing changed. I panicked. I had Trickdroid 6.0 on my device so I tried to install it too, but still the ending result was the same... The last choice I had was to install the CM ROM again, so I did it. Still nothing. I think it all came from the boot.img file i downloaded , but I'm not sure. I started to search forums for this kind of issue but I didn't find anything similar to this, or atleast I didn't search for the right thing. Anyways, I thought of doing a factory reset from the Fastboot mode, and after 2 hours of searching the forums I did a factory reset. The phone restarted and entered in the Recovery menu again. I didn't know what was I supposed to do there + I had NOTHING in the phone (which I knew it was going to happened) but I didnt think that the ROMs will be deleted too. So I tried to connect my phone with the USB ,but as usual it needs a full boot up to connect with the USB, so I can upload some files to it. Now all I can do is enter in the Recovery/Fastboot menu. Can anyone help me or does anyone have an idea what should I do?
P.S. Sorry for the long post. I'm desperate.
Can you sideload a zip through recovery? Because boot.img files are only a kernel, so you're going to need a complete kernel.
Sent from my Nexus 4 using Tapatalk
SMillerNL said:
Can you sideload a zip through recovery? Because boot.img files are only a kernel, so you're going to need a complete kernel.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I cannot connect to the computer. I don't have anything on my phone and I can't upload anything to the device. Except if there is a option to 'allow" something via fastboot from the computer. Since that is the only connection I have with the phone.
Hey there,
I recently rooted my HTC one and loaded up Cyanogenmod. I loaded the most recent version yesterday, the nightly from 2/1 and it caused the phone to go into a bootcycle. I updated via CyanDelta, so it was a small file that was downloaded, and I dirty flashed using CWM. The issue is that my phone now is stuck in a bootcycle. Because I used CyanDelta, I do not have any full versions of CyanogenMod. Infact the only zips on the my phone are the update to the 1/31 nightly and the update to the 2/1 nightly.
Somehow my phone has its usb debugging turned off now, meaning I can not see it on my computer. I am wondering if there is anyway to reconcile this with my phone, since it is basically a brick right now.
I know there is Odin for samsungs, but it does not work for HTC? Is there something like Odin that does work from HTC?
Thank you all for the help.
Sounds like you need to push a ROM onto your sdcard and flash it, then go from there. This may help you out:
http://forum.xda-developers.com/showthread.php?t=1667929
raczoliver said:
Sounds like you need to push a ROM onto your sdcard and flash it, then go from there. This may help you out:
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
Thank you for the suggestion, however my phone does not have an sdcard, and if I try doing this with any of filepaths I do have show up in CWM I get a message no device found. my /sdcard path is apparantly /data/media but nothing works to push to my phone. I have also tried to sideload and again it does not work. any other ideas?
Fixed It
OK, so I figured out how to fix it.
I flashed the update file (about 4mb) from my phones memory of the 1/31 version, then gapps4.4. Once that was done I got into the phone and enabled USB debugging and after doing so, I loaded up the new full version of Cyanogen, the nightly from today (2/2) and installed it, along with gapps, and the radio update.
Thanks for the help guys.