Related
Ok so a couple days ago in preperation of selling my evo 3d , i flashed a new rom of which i cant remember , i also beleive i flashed silverneedle kernel through the gpl tool app. Ever since no matter what i do , i cant get past the white HTC screen , it just reboots from there . Ive tried the superwipe tool and it seemed like it was going to work , but nothing . Ive also looked over several threads on here and no one seemed to have had an answer, thus im making my own thread. Im currently trying to flash warm 2.3 rom. I even thought maybe it was a bad transfer to the sd card because the sd card was acting funky when the rom was being transfered to it in my galaxy s2 so then i just downloaded it dirtectly from dolphin browers to the root of the sd card right from the galaxy to see if that was the problem. Still nothing , just the htc screen. Anybody have any idea how to fix this? I just want the phone back to stock so i can sell it , ugh. O and im on HBOOT 1.5 with the official HTC unlock and S-on.
I'm in the same boat. Fairly new evo 3d with hboot 1.5 rooted through htc. I've been flashing several roms over the last few days all with success, found I like Xplod XE from team nocturnal the best, nice and fast. What i found was that the kernel never changed, as I had read would happen with s-on. After doing some reseach and trying a few things I ran into your problem. Now no matter what or how i flash i'm stuck in a boot loop at the white HTC screen. The last kernels I've attempted to push were Tiamat_E3D-v1.1.0-Sense and silverneedle-test5. I've tried various combinations of wiping both caches with and without factory reset/system wipe as well as flashing several roms with success, still stuck with the boot loop. Flashed all roms through TeamWin Recovery and pushed kernels through clockwork recovery via fastboot/cmd promt.
Darthdaddy said:
.... and pushed kernels through clockwork recovery via fastboot/cmd promt.
Click to expand...
Click to collapse
Not sure about this.
But when flashing kernels, it happens through fastboot. You shouldnt see clockwork anything.
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
carnivalrejectq said:
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
Click to expand...
Click to collapse
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Followed directions from another site to work through command prompt and get into recovery, pm me for the link. Made sure i had my rom file on my sd card, did a factory reset then manual install of rom via clockwork then rebooted. Went through fine.
tailsthecat3 said:
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Click to expand...
Click to collapse
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
carnivalrejectq said:
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
Click to expand...
Click to collapse
Youll need to have all the necessary files/programs which I imagine are fastboot, adb, device/android drivers...
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
carnivalrejectq said:
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
Click to expand...
Click to collapse
Try this. Watch the vid, download the files.
Frankly, you should be able to run the RUU, so long as youre 'relocked'. Thats how Ive done it, multiple times. Hopefully we can get you back to stock.(Which we can)
Whew , i finally got it! The last part there was my erorr for using an older RUU , i didnt look close enough and i thought i was using 2.08. So i dled the 2.08 one and now its all good to go. Haha literally been doing this since 930 am. Thanks for the help guys , btw.
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
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?
I am rooted and S-Off. I am using the ViperOne custom ROM for my phone.
The end goal is for me to update my firmware, because my phone has an over 10 minutes boot time normally. (Not an exaggeration. I have actually timed it with a timer.) I read that in order to fix this, I should try to update the firmware by going to stock recovery and doing an OTA update.
My TWRP has worked flawlessly for me over the years, but for some reason it won't work anymore. It will hang on the boot screen for over an hour. After that hour, I assumed it's not slowly booting. (As a bit of background, recovery would boot quickly while my phone still had problems with 10 minute boot times).
Another piece of information is that the last time TWRP worked was when I used it to install .zip files from Titanium to get all my apps working. That worked perfectly fine, my apps got updated, and no trouble. I wish I could say what happened between then and now, but from what I can remember, I just used my phone normally, such as using web browsers and games. I don't remember messing with any system files.
I do know that ClockWorkMod recovery DOES work if I flash that, but my nandroids are all on TWRP. I have tried to flash different version of TWRP as well. It doesn't seem to matter which one I flash, my phone reacts exactly the same.
Another thing to note, I'm not sure if it's significant or not, is that when I got into hboot, I get the following message for a split second. I can't read the file names exactly, but I got the extensions. Then I get the normal screen with the vol instructions and choices to go to fastboot, recovery, etc... The message reads:
SD Checking...
Loading [(something).zip]
No Image!
Loading [(something).nbh]
No Image or wrong image!
Loading [(something).zip]
Loading [(something).nbh]
No Image or wrong image!
I hope this is a decent amount of information. I tried to include as much as I could, but if I'm missing any critical details, let me know and I will GREATLY appreciate your help!
have u tried to rewrite the image, download the new TWRP and load it via adb
Bradl79 said:
have u tried to rewrite the image, download the new TWRP and load it via adb
Click to expand...
Click to collapse
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Battletooth said:
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Click to expand...
Click to collapse
Having the exact same issue. Attempted to install twrp-2.8.6.0-m8.img using adb, but TWRP never loads. I can load prior versions but same results. Going to HBOOT I get a bunch of messages related to 0P6BDIAG.zip, 0P6BIMG.zip
and some .nbh. I think it's looking on my SDCARD for those.
If you're looking to update your firmware, you can use an official RUU to change the firmware of your phone. You can read more about it in this stickied thread in the general forum to see if it fits your needs. If you decide to do this, your phone will be completely stock after the RUU finishes running so use fastboot to flash TWRP (or whichever recovery you prefer).
Regarding the messages you see in hboot, it will always check for those files if you have an external sdcard mounted. If they are present, you will be given the option to flash the update. If not, you will get regular hboot access after the check. It is completely normal and nothing to worry about.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.