Man, I've been out of the Android loop like never before. Probably since right when kit-kat builds started hitting. Anyways, I've been running Venom for months, and just last night my phone started crashing like crazy. Every time it would turn on, just the smallest bit of interaction would make it restart. At some point I must have deleted the ROMs off my storage, because I finally got into TWRP and wiped my data. But couldn't find any ROMs, so LUCKILY I was able to flash through ADB Sideload. Thank god I set up the SDK on this new computer months ago. Anyways, I was able to flash an old SlimBean I had on my hard drive. The DNA is still having issues. Its not restarting every time I do something like last night, but close to it. Any time I get a phone call, I'm able to pick up and talk for 5 seconds, then it restarts. Can anyone help me out here? I thought about wiping internal storage but I'm not sure what problems that will cause. I'm still on JB with an old version of TWRP. The phone is not messing up while in recovery, so I was thinking about flashing new version of TWRP and installing a newer ROM. I don't know if that will help, anyone got any ideas?
ALSO, I no longer have insurance on my device and my screen is cracked. However, it has been less than 12 months since I purchased, so I may still have the one-year warranty, but unless I could get back to stock really easy, I doubt I could pass it off for a warranty replacement.
Does anyone know how I can get fastboot to work? I don't mean in general, I have never had a problem really using fastboot, but when I get into fastboot and check with devices, I'm returning nothing, and I want to flash a new recovery. I know on some ROMs there is a way to turn fastboot on and off, but I'm not seeing anything in this ROM (slimbean-dlx)
Also, just now updating this, but adb won't return a device ID either. I'm not sure why. I believe in recovery it recognizes the device. it did last night. that's how I was able to flash a ROM
lemonoid said:
Does anyone know how I can get fastboot to work? I don't mean in general, I have never had a problem really using fastboot, but when I get into fastboot and check with devices, I'm returning nothing, and I want to flash a new recovery. I know on some ROMs there is a way to turn fastboot on and off, but I'm not seeing anything in this ROM (slimbean-dlx)
Also, just now updating this, but adb won't return a device ID either. I'm not sure why. I believe in recovery it recognizes the device. it did last night. that's how I was able to flash a ROM
Click to expand...
Click to collapse
I would suggest ruu the device back to stock and then try. But I never get my device to show in fastboot and I send recoveries to it all the time. So just flash one at and if it goes you should be able to boot into it and then flash rom.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thanks I'll try it. Even though it wouldn't show my device in fastboot yesterday, i tried flashing the newest TWRP but it didn't do anything. However, the phone has become somewhat stable. It is still rebooting on phone calls, and the UI is REALLY weird. I've never seen it before, the entire UI is really small and zoomed out. Everything operates like normal, but EVERYTHING is about 1/10 the size its supposed to be. I've flashed two different old ROMs and re-flashed the one I am using now (Beanstalk)
lemonoid said:
thanks I'll try it. Even though it wouldn't show my device in fastboot yesterday, i tried flashing the newest TWRP but it didn't do anything. However, the phone has become somewhat stable. It is still rebooting on phone calls, and the UI is REALLY weird. I've never seen it before, the entire UI is really small and zoomed out. Everything operates like normal, but EVERYTHING is about 1/10 the size its supposed to be. I've flashed two different old ROMs and re-flashed the one I am using now (Beanstalk)
Click to expand...
Click to collapse
Hopefully performing the ruu will fix that. Sounds like a system file may have become corrupted.
Sent from my Droid DNA. If I have helped you in any way please press the thanks button.
I have never had to RUU before. The DNA was my first HTC since Eris, and I've never really messed up to the point of RUU'ing. Should I just download the most recent RUU and run that? Or would I need to flash anything else with it? such as hboot or recovery?? I have the 3.06 radio/recovery/hboot's downloaded. my brain still operates in samsung and moto modes. I have only managed to irreversibly brick one device out of at least 30 and I would not want that to be my daily driver
Maybe the cracked screen is messing with the digitizer and then causes ROM havoc?
---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------
What Windows version are you using?
maybe, I mean, the screen has been cracked for at least 8 months. I'm using 8.1. unfortunately. I didn't realize when I bought this computer how hard it would be for me to get back to Ubuntu which is my preferred. It is so much easier to do anything with Android on Ubuntu IMO.
Am I correct in reading a comment somewhere that Fastboot drivers don't work on Windows 8.1??? Does this mean I can't RUU?
I think there's some way to get it working on Windows 8, but you would have to search. Most people just find a W7 computer and get it done.
orangechoochoo said:
I think there's some way to get it working on Windows 8, but you would have to search. Most people just find a W7 computer and get it done.
Click to expand...
Click to collapse
yeah I have W7 downstairs I guess I'll just use that. Thanks tho.
Related
hey, first post. ever. lurked for about a year though. really appreciate all that everybody here does, for free no less. so thank you for that.
so i have an issue.
the micro usb port on my evo3d seems to be broken. like maybe detached from the motherboard? the piece that you normally see in usb ports is there, but i cant charge and i cant connect to my laptop. i could deal with the not being able to charge as i have extra batteries and a seperate charger, but if i cant connect to a computer i cant use fastboot, which i need to use because im using hboot 1.5 s-on.
ill be eligible for an upgrade this coming friday, but id rather hold out for the gs3 and see what thats all about.
so my question is, is there a way to use fastboot over wifi? ive searched a bit but cant really find anything.
any help would be greatly appreciated.
If you already have root there's an app called flashimg GUI. It can help with flashing recoveries and kernels. I suggest trying it and seeing if it helps with doing whatever it is that you need to achieve.
Sorry for the vague answer but if you add what it is exactly you are trying to do with fastboot it would also be helpful
Sent from my HTC EVO 3D X515m using Tapatalk 2
I can recommend for you to use 4ext Recovery. It lets you flash Kernels and ROM's without Fastboot commands.
fastboot is needed so i can flash roms. hboot1.5 s-on doenst allow me to flash a kernel unless i use fastboot to enter recovery.
ive use flashimage gui before, and last night i was able to use it just as was mentioned before. im fully aware of how to do this, but what im wondering about is this: i really dont like to "dirty" flash (as in not wiping the phone via superwipe or some other tool). so if i flash the kernel with flashimage then enter recovery and use superwipe, will the kernel that i just flashed with flashimage still be there so that i can safely flash the rom that goes with it and have no issues?
regarding touch recovery with smartflash, i should have installed this weeks ago, but cwm has never given me an issue since i rooted this phone in november. if i were using touch recovery none of this would be an issue. but the fact remains that i need be able to connect to a computer in order to initially flash the new recovery. right? im asking really, because thats how i understand the process but im not 100% sure.
again, thanks for the input guys. any help is appreciated.
smwhr23 said:
fastboot is needed so i can flash roms. hboot1.5 s-on doenst allow me to flash a kernel unless i use fastboot to enter recovery.
ive use flashimage gui before, and last night i was able to use it just as was mentioned before. im fully aware of how to do this, but what im wondering about is this: i really dont like to "dirty" flash (as in not wiping the phone via superwipe or some other tool). so if i flash the kernel with flashimage then enter recovery and use superwipe, will the kernel that i just flashed with flashimage still be there so that i can safely flash the rom that goes with it and have no issues?
regarding touch recovery with smartflash, i should have installed this weeks ago, but cwm has never given me an issue since i rooted this phone in november. if i were using touch recovery none of this would be an issue. but the fact remains that i need be able to connect to a computer in order to initially flash the new recovery. right? im asking really, because thats how i understand the process but im not 100% sure.
again, thanks for the input guys. any help is appreciated.
Click to expand...
Click to collapse
First of all. If you use Flash Image GUI the Kernel will remain there even with a superwipe. and second i recommend 4ext, you don't need a PC to install the new recovery. Just download it from HERE, install it as a normal apk and you are ready to go. Just make sure when the app asks if you are S-ON select yes. Don't forget to download latest version.
just wondering, is the connector loose?
If you open it up and look with magnification, can you see the solder connections separated?
I'm just thinking that with a very thin soldering iron, magnification and a little skill, you can probably repair the connector.
I would at least take the phone apart and give it a good look and see if its possible to fix.
excellent. thanks for the quick response. im gonna dl the ext4 and give it a shot later. ill report back, but im sure the results are predictable (that it will work). also good to know about the figui/kernel/superwipe situation. that info could also come in usefull.
im not new to this, as i used to own a samsung moment and the only to make that thing usable was to root it. but there are just certain things that im not 100% on (or even 50% really, the work these devs do is amazing to me). so i really appreciate the help. hopefully this will keep me going for a few months.
zcink said:
just wondering, is the connector loose?
If you open it up and look with magnification, can you see the solder connections separated?
I'm just thinking that with a very thin soldering iron, magnification and a little skill, you can probably repair the connector.
I would at least take the phone apart and give it a good look and see if its possible to fix.
Click to expand...
Click to collapse
i thought about doing that, as i know my way around a soldering iron, but im really trying to avoid doing that, just because of the potential to screw the phone up completely.
to answer you question though, yeah, it is loose. the usb plug moves way too freely in there, and if i mess with it long enough i can get the red light for a split second, but it wont stay. so that tells me its loose. and ive found others on google with the same exact issue. i guess it was a common problem with these phones, but ive had the thing since launch day so i would have expected this to happen sooner.
smwhr23 said:
excellent. thanks for the quick response. im gonna dl the ext4 and give it a shot later. ill report back, but im sure the results are predictable (that it will work). also good to know about the figui/kernel/superwipe situation. that info could also come in usefull.
im not new to this, as i used to own a samsung moment and the only to make that thing usable was to root it. but there are just certain things that im not 100% on (or even 50% really, the work these devs do is amazing to me). so i really appreciate the help. hopefully this will keep me going for a few months.
Click to expand...
Click to collapse
No problem man. Remember that even the most experienced player may need help sometimes. Also i recommend to fix the USB, maybe a bad flash. Who knows...
HTC Reseller said:
Also i recommend to fix the USB, maybe a bad flash. Who knows...
Click to expand...
Click to collapse
i thought about that, so i used flashimage and dirty-flashed a different rom. still no charge or connect capability.
I have searched the forums for a few hours and have not found a problem close to mine. here's the story:
phone was charged to just about 100% when this happened.
HTC Rezound, with Amon Ra recovery, unlocked, rooted, S-ON flashed with Sensless Chaos Red 2.0 and it was working fine.
So I wanted to flash a different kernel. This is where I may have made a mistake. Flashed Rezound Cubed ICS Kernel 2.3.9 and rebooted, it worked but WIFI didnt and the governors weren't available so obviously the kernel wasnt fully installed. Rebooted to fastboot, used fastboot to flash the boot.img for the kernel. This also seemed to work. Phone restarted, went into ROM no problem. Was messing with governors and the phone just shut off. Now it will not turn on, will not charge, won't do squat. Can't get adb to recognize it, nothing. ANY HELP WOULD BE APPRICATED and all replies will be thanked!
First, take the battery out. Let it sit for about 10 minutes.
Put the battery back in and press the volume down and power button until you see the hboot screen. If you get there then go to recovery, wipe and reflash your ROM.
GrayTheWolf said:
First, take the battery out. Let it sit for about 10 minutes.
Put the battery back in and press the volume down and power button until you see the hboot screen. If you get there then go to recovery, wipe and reflash your ROM.
Click to expand...
Click to collapse
did that. let it sit forever. tried to get to hboot. nothing. tried different battery in my phone, no luck.tried different charger. nope. tried my battery in a different phone and it worked fine. took to verizon and they are swapping. new one in the mail. lets hope they don't find out about the whole unlocking, tampering, rooting, flashing business lol.
Thats very odd especially since your s-on and its nearly impossible to brick your phone. Here are some links to 2 ways to unbrick your phone, I have never bricked before and so i have never tried them however. http://forum.xda-developers.com/showthread.php?t=1833530&highlight=unbrick
and http://forum.xda-developers.com/showthread.php?t=1711408 I hope these help. From what i know about S-ON it protects the essential partitions and files that allow the phone to boot such as the bootloader, radios, etc. so that the system doesnt become corrupted and fail to boot. So the only way i can think of your phone bricking is something in the hardware could have died for some odd reason. If you cant get it unbricked your gonna have to take it to verizon to get a replacement.
jon7701 said:
Thats very odd especially since your s-on and its nearly impossible to brick your phone. Here are some links to 2 ways to unbrick your phone, I have never bricked before and so i have never tried them however. http://forum.xda-developers.com/showthread.php?t=1833530&highlight=unbrick
and http://forum.xda-developers.com/showthread.php?t=1711408 I hope these help. From what i know about S-ON it protects the essential partitions and files that allow the phone to boot such as the bootloader, radios, etc. so that the system doesnt become corrupted and fail to boot. So the only way i can think of your phone bricking is something in the hardware could have died for some odd reason. If you cant get it unbricked your gonna have to take it to verizon to get a replacement.
Click to expand...
Click to collapse
i know exactly what you're saying. i think the phone just fried as in hardware malfunction not software. already took it in to verizon and they sent it off. waiting for new one in the mail
techblitz said:
i know exactly what you're saying. i think the phone just fried as in hardware malfunction not software. already took it in to verizon and they sent it off. waiting for new one in the mail
Click to expand...
Click to collapse
Lol i just looked and i didnt see on your post above my previous one that you said you had already taken it to verizon. :silly:
jon7701 said:
Lol i just looked and i didnt see on your post above my previous one that you said you had already taken it to verizon. :silly:
Click to expand...
Click to collapse
it's all good. i already got my replacement.
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 have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Jussi31 said:
I have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Click to expand...
Click to collapse
I don't know if this is too obvious.. but have you flashed the recovery again??
When you run the RUU, it is overwritten. You need to download a recovery and flash it through fastboot:
fastboot flash recovery recovery.img
Actually, around six or seven times now, with no luck. Now when attempting to get into Recovery, it hangs on the white screen. The thing is, I successfully had TWRP 2.5.0.0 on it. (Long story.) I am now trying to figure out how to root it through Fastboot, if that's even possible. Otherwise, I am out of ideas.
Through trial-and-error, I finally was able to get it rooted. However, no matter how many times I try flashing TWRP-Touch (various versions), it maintains its inability to boot into Recovery Mode. Go figure.
I use twrp venom without any issues, maybe try that one?
http://forum.xda-developers.com/showthread.php?p=37300312
Sent from my Viper One X+
Oh wow, it actually worked! God love you. Thanks much.
No problem
Sent from my Viper One X+
When you were hanging on the white screen, did it say anything on the screen?
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Update
00mpollard said:
No problem
Sent from my Viper One X+
Click to expand...
Click to collapse
Hey 00mpollard, I just wanted to thank you for both recommending a working Recovery IMG (that works great) for my HTC One+, and as well as introducing me to the corresponding Viper One X+ ROM, that I also decided to install, and I couldn't be happier. Thanks again.
No problem, glad i could help!
I love Viper rom, very stable & lots of customizations Can't go wrong!
Jussi31 said:
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Click to expand...
Click to collapse
I was just curious because if it said something about waiting on SD card or SDdata, something along those lines, I get that issue when the phone is plugged in. Unplugging the cable allowed me to enter hboot with no issues.
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.