About a month ago I rooted a HTC EVO 4G LTE, installed the recovery with touch screen and Cyanogenmod nighties.
It worked great, including tethering on Sprint.
Last week an update to latest Cyanogenmod was made. Phone worked normally, until today when screen stopped responding completely (physical buttons were working), including after rebooting. On a second reboot phone was stuck on a boot loop.
Went into bootloader mode and tried to go to recovery. It would boot loop again. Noted that it said UNLOCKED S-ON (I thought it was supposed to be S-OFF). I tried flashing the boot.img from latest Cyanogenmod. Nothing. Tried reseting from the menu. Tried more things. Nothing worked. So I downloaded and used the latest version of RUU after fastboot oem lock. RUU was successful (no error, phone no longer displays HTC developer message), however it's still stuck on the boot loop. I thought RUU would restore it completely.
What am I missing?
Read here
http://forum.xda-developers.com/showthread.php?t=2084633
And here
http://forum.xda-developers.com/showthread.php?t=2097150
#Root-Hack_Mod*Always=SG3
I followed the instructions.
Then I tried all RUU that I had and always got Error 140.
Finally, found in a rooting pack RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe which worked to restore.
However, the phone is still in the same state. What do I do?
How long did you give the phone to boot.? Also did you flash the firmware zip after you relocked your boot loader?
#Root-Hack_Mod*Always=SG3
Phone is RELOCKED.
What I did:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
Then used that RUU to restore. After this I left the phone without touching it for about ten minutes, but it keeps restarting (never passes booting stage).
Try this. Remove your sd. Then back up all your data. Then format it threw your PC and return it to factory defaults. Then put it back in your phone and redo the steps. Also were did you get the ruu your using from ?? Also if that fails to work look here
http://forum.xda-developers.com/showthread.php?t=2045935
And try the firmware zip with the stock recovery. Then run the ruu. Hope this helps.
#Root-Hack_Mod*Always=SG3
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Same result after trying without SD card. Also I did flashboot flash zip
Code:
PJ75IMG_3.15.651.6-firmware.zip
from the link you provided without help.
PepeJones said:
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Click to expand...
Click to collapse
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
laie1472 said:
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
PepeJones said:
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
Click to expand...
Click to collapse
You can't flash a PJ75IMG.zip unless you are S-OFF and the file you posted above is not an RUU it's just the updated firmware
It didn't work.
So I followed the steps from this link.
After using HTCDev to unlock the phone and I try to open RabiesShot, it reboots the phone but it's not able to connect. Sometimes the phone goes in a loop, sometimes the phone boots (it did boot twice). However, even when it booted, the screen didn't work at all, which is the original problem.
Right now the phone is ON but the only thing that works is the power and volume buttons (screen and soft buttons do not work). I've also noticed the phone reboots alone.
Any ideas left?
(This is my friend's phone. Anyway, I'll convince anyone to stay away from HTC. Nexus is so much better than this...)
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
laie1472 said:
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
Not hacked itself, just not working. At least, that's what I've been told. Right now I'm trying to make it stock, but since what you proposed didn't work I tried different things such as obtaining S-OFF (no success).
The comment regarding HTC wasn't necessarily related to this case but in general. Just look how miserably is the process to just obtain root and unlock the bootloader. And in many cases is not even possible until some exploit is found. Why...? HTC used to be great.
I'm just trying to get this phone work again. Initial idea was to go stock, since it seems logical that it should be straight forward.
So I tried everything you have posted, including the last instructions you left me (backup everything off SD, deleted everything and inserted SD in the phone, then repeated the process).
Thanks for your help.
I understand your frustration about the issues with the phone in its current state. However if done correctly gaining root/s-off can be achieved in less that an hour. I do realize the fact that even if guides are followed to the exact directions that issues still occur. But that's the risk you take when you modify you phone. Your aware of this I'm sure. However that's why xda is a great website. Not only can you get the software to modify your phone, you can also get help in case the process didn't go the way it should have. You can't dispute the fact that there are more than a few members with the evo-lte who had no problems at all with gaining root or s-off. As far as the steps I suggested there was no guarantee that they would work its just the process of trouble shooting to see what will work. If you don't mind can you post the exacts steps you took before you tried to achieve s-off ? Also can you post the links to the exact ruu and firmware you last used as well.? Also if the phone is on try powering it down and attempt to boot into the boot loader. If your successful then try factory reset.
#Root-Hack_Mod*Always=SG3
Related
Hi all. i'm having trouble finding a specific thread to help me solve my problem. (I'm not too good with rooting, and should have not messed with it in the first place!)
Anyways let's get to my problems:
So I needed to take my phone to the Verizon Store, and without thinking went straight to the Factory Reset thing. Now everytime I try booting up my phone it gets stuck on the custom bootup screen and freezes during part of the animation and just stays there.
I have read things that say try going into hboot and doing recovery, but all's it asks me to do is update, then has me reboot. It doesn't update anything as it still does the same exact thing.
My question is, can someone please help guide me through the process of returning my Thunderbolt back to STOCK. I really am unsure of what I need to download, and where I need to put things, and what I need to name them etc: Clearly I need to think twice before rooting my phone again.
Also when I go to plug my Thunderbolt into my computer via USB my computer cannot recognize the device, any suggestions why?
Thanks so much! Really really need help!
First off all it sounds like you have a pg05img.zip file on the root of the sdcard. Only way to remove it now is pulling the sdcard out and putting it in a conputer and deleting that file. Then you should be able to boot and/or get into recovery.
If that's not the case then i don't know what's preventing you from getting into recovery. Although, just a factory reset should not have caused this anyway.
Sent from my ADR6400L using Tapatalk
mini2215 said:
Hi all. i'm having trouble finding a specific thread to help me solve my problem. (I'm not too good with rooting, and should have not messed with it in the first place!)
Anyways let's get to my problems:
So I needed to take my phone to the Verizon Store, and without thinking went straight to the Factory Reset thing. Now everytime I try booting up my phone it gets stuck on the custom bootup screen and freezes during part of the animation and just stays there.
I have read things that say try going into hboot and doing recovery, but all's it asks me to do is update, then has me reboot. It doesn't update anything as it still does the same exact thing.
My question is, can someone please help guide me through the process of returning my Thunderbolt back to STOCK. I really am unsure of what I need to download, and where I need to put things, and what I need to name them etc: Clearly I need to think twice before rooting my phone again.
Also when I go to plug my Thunderbolt into my computer via USB my computer cannot recognize the device, any suggestions why?
Thanks so much! Really really need help!
Click to expand...
Click to collapse
How did you initially Root your device? I assume revo since so many have now. Like mentioned above make sure you check your sdcard and ensure there is no PG05IMG.zip on it. After you have checked your sdcard for that file and deleted it, or maybe it is not there try to get into recovery.
Pull your battery out and then hold Volume down + power. Where does that get you? Hopefully you made a nandroid of your device after you rooted. If you followed a guide that was most definitely recommended. If this takes you to recovery just do a restore.
If you get restored there are some very good guides that Google will lead you to on how to unroot and return to stock.
1Sorry for the super late response, I'm going to try everyone's advice now, thanks so much for the help!
a factory reset will not unroot the phone. If your going back to stock, you have to unroot it. If you bring it to verizon rooted, they may deny you service...
as stated above, just search google or here for instructions how to return to full stock
I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!
I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.
older radios? Im still new to this so I applogize...
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
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?
Daughter handed me her phone today and said it "turned off and would not turn back on"... I could use some help figuring out what went wrong and how to fix it. I have flashed many roms, built a few from source, installed recoveries, rooted devices, etc. Though not a complete noob, I do have no formal training on this stuff and consider myself a novice compared to many here at XDA.
The phone was unlocked and rooted using Hasoon2000's HTC Rezound All In One Tool Kit about 1 month ago...
The rom that was fully functional for the past month, until today, is Liquidsmooth JB v2.9 Official vigor. It has worked exceptionally for her, until today. AT this point, if you pull the battery and then put it back in - it will boot to a white HTC screen for a few seconds and then go BSOD indefinitely. The only way to get any action after that is to pull the battery and try again... You can use the power & volume down to get into fastboot (if I pull out the external sd card) or into recovery (if I leave the external sd card in place).
Here's what the status on the fastboot screen shows:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Here's where I'm stuck at trying to get it back up and running - I do not think it is hard bricked:
1) I can boot into recovery and was able to open TWRP 2.5.0.0 and move around in it. However, it seemed to be saying there is no internal memory on the phone (cant mount or open) cache, data, system, sdcard (internal), NO ROM. I can not wipe any of the above partitions or format either...but it does see everything on the external sd card, though you can't flash anything to the internal sdcard or system, etc... Therefore, I decided to try another recovery, so...
2) Eventually I figured out how to fastboot flash a new recovery (after lots of reading here on several forums) and managed to get CWM Touch v6.0.3.6 Installed... it also does not see the system, cache, data, sdcard (internal)... but it does see my external sd card, as did TWRP. Again, no flashing to internal memory or formatting of the aforementioned partitions...
3) I have tried to fastboot flash boot.img from the aforementioned rom - fastboot flash boot boot.img - which appears to work, yet there is no change in status after rebooting or pulling the battery. Same problems exist...
4) I have tried fastboot flashing the RUU - fastboot flash ruu radio.img - appeared to do something, but still no change in status...
5) I have tried fastboot flashing the system image - fastboot flash img Liquid.zip (I changed the name of the file in an act of desperation trying various methods I read about online) - appeared to do something, but still no change in status...
6) If I boot into recovery, ADB can see the device and shows it in recovery mode. I have tried to ADB INSTALL the rom and boot.img - no luck there either (though I could be doing something wrong)...
7) If I boot into recovery, my windows 8 computer sees the external sd card of the device if I mount it as a USB MASS STORAGE device, but does not see the internal sdcard.
8) I have tried using Hasoon2000's tool to do various things and had no luck with making any more progress than using fastboot or adb.
9) I have tried to fastboot boot several different recoveries, but could not get any of them to boot up... though the process looked like it was working and rebooted - and just stuck at the white HTC screen...
I have been hacking away at this phone for about 7 hours now, reading forums, trying many things (some of which are listed above), and I've run out of ideas...
If anyone has any experience with this situation and knows of a positive solution that does not involve me flushing this thing down the toilet, I'd be really appreciative of your detailed advice. Though I have some basic experience, I can get lost quickly if you skip the details in any suggested solutions.
I appreciate any help or advice you may have to offer. I'm not thinking it's bricked - I just don't know enough to have the solution and have been reading for hours... getting a bit delirious at this point.
Thanks for you time...
It honestly sounds like some partitions are corrupt or damaged. Try using amon ra and see if it can see the internal partitions, if it can, format ext3 then ext4. Fstrim can corrupt the partition and amon ra can fix that.
If that doesn't work, you might be SOL as there is no full ruu for global OTA at the moment which may be your last resort. If you are on the recent OTA, which by your hboot, sound like it, you'd need S-off to RUU.
Sent from my Infected Rezound using xda app-developers app
Its deffinately not bricked...being able to boot to bootloader is a good thing...But as Uzephi said your best bet is to S-Off to make any further progress...that way it makes it easier to do things...fstrim especially used by LagFix app has caused this error in the past and what Uzephi said i will second to...in recovery you can try converting from ext4 to ext3 and back to ext4 and try wiping the internal within the recovery and that may fix it...if it doesnt there is a few fastboot and adb command tricks for formatting...however with s-off downgrading or upgrading the ruu is possible which may fix it also...i ran into this error once actually shortly after i modded my rezound the first time while it still only had sense...luckily i s-offed and was able to throw a few tricks at it
Guys, THANK YOU both for throwing some ideas at me... I will try as you both suggested and give an update once I'm done.
I will see if I can figure out how to s-off this thing... Then,
I will fastboot flash amonra and see if I can reformat internal with it.
If neither work, I will research adb and fastboot reformatting the internal memory.
Thanks again... This give me some more things to work on today. I will keep you posted.
Sent from my GT-I9505G using xda premium
still stuck...
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
dandroid7 said:
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
Click to expand...
Click to collapse
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
REV3NT3CH said:
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
Click to expand...
Click to collapse
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
dandroid7 said:
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
Click to expand...
Click to collapse
juopuntubears s-off method is meant for windows...for the latest ruu all you need to do is make sure it looks like PH98IMG.zip and place it to the root of your external sd card then run in bootloader and it will go through the process of install from there. I havent seen the other all in one kit in action but juopuntubears method is what i used....im pretty sure its somethjing very simple but i would load the ruu first n see where we go from there....my guess is your internal sd card was either in the middle of a reformat and was interrupted or if lagfix was used it caused the error or files were improperly deleted or the possibility of someone trying an s-off method on the s-on device....ive gotten the tampered message before and that usually means a improper hboot flash method was used
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
dandroid7 said:
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Ya that may of done it...it is a possibility....again if all else fails someone can work on it for you....me personally id do it for you free of charge and you can trust me...i hate seeing people without and to be honest mine was completely hard bricked to no return and Neo has done me a great deed of help so im passing along the karma...but by the sounds of it yours isnt hard bricked which i know is fixable
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
dandroid7 said:
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
well your internal memory is borked but phone isnt bricked...hard bricked is when your phone wont even boot to the bootloader but reads as a certain different device in device manager...ill look into many other ways to fix this for you and i do hear you on being stubborn...im the same way when it comes to this sorta stuff and push myself to learn more....great devs learn and come from that same influence and drive to do so
Can you restore your partitions? Or can you not because you can't format them? If you can't, I suggest just flashing a stock RUU from you bootloader, being very careful though, you don't wanna get bricked. From there you can just flash your recovery and restore what you can, hopefully. Do you want a link to the RUU?
Sent from my ADR6425LVW running EclipticRezRavampedV9 (Lunar Kernel) using xda app-developers app.
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
if your on hboot 2.28 that is the most recent up to date leaked radios...however the most up to date full ruu comes with 2.27...if you are s-off its kind of hard...a user posted in the threads earlier that he completely removed his external card and his windows was able to detect the 2 internal partitions...and he formatted the 10.5 gb fartition and worked flawless...if all else fails...how well do you know about using linux and or a linux based rescue disk for partitions
Holy cow - its alive!!!
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
dandroid7 said:
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
Click to expand...
Click to collapse
Use CWM or TWRP for flashing. Amon ra is known to have flashing/wiping issues. And did you clean wipe? Even though you have RUU you still need to wipe.
Sent from my Infected Rezound using xda app-developers app
Thanks for the info... I never used amon ra before, I read about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with amon ra, then fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Thanks for the info... I never used amon ra before, I red about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with am on ra, the fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Hey i may have found a fix...another user had the same issue and fixed it by using TWRP and wiping emmc first. Once he did that he wiped the internal sd card. Should then work... Format afterwards just to be safe.
K good to know. Have a great night... I will give it a rip tomorrow... I'm pretty stoked to have gotten this far today.
Sent from my GT-I9505G using xda premium