A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Altom85 said:
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Click to expand...
Click to collapse
Try using the TWRP found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my Nexus 5 using XDA Premium 4 mobile app
download this twrp http://d-h.st/7Cr
name it properly and fastboot flash it. after that mount your device to you pc and transfer a rom zip to storage.
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Altom85 said:
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Click to expand...
Click to collapse
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
FesterCluck said:
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
Click to expand...
Click to collapse
Ok it's not stuck anymore, I can get into recovery and bootloader, so I'm not in a panic anymore at least However, my computer is not detecting my phone, nor is VipeRUU. If I try to mount to the computer via TWRP, nothing comes up. BTW my recovery is 2.7.8.0b now. Still no OS, still gets stuck on the HTC screen until I boot to recovery or bootloader
Edit: Now the computer tries to install drivers for my phone whenever I plug it in. It pops up as HTC MTP Device, always fails to install, then has a warning in the device manager. So I uninstalled the drivers, uninstalled HTC Sync, reinstalled HTC Sync. Didn't help. This is beyond frustrating...
Edit 2: After scouring the internet someone said to lock the bootloader and that'll allow my PC to see my phone. Well, now i have a RELOCKED (that's what it says on top) bootloader and I'm no closer to the solution methinks. I'm ready to just throw this phone out the window.
Edit 3: I actually discovered ViperRUU has a way to bypass the initial screen so I can use it in bootloader. Great, except now it's stuck on "Flashing..." and has been for half an hour. I really might throw this phone out the window.
5th and final edit: VipeRUU just would not work at all, so I had to go back to an older stock RUU, which sucks but at least my phone is working now Thanks for your help guys!
Related
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
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
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.
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
OK, no one is helping....ive tried some things, learned a few but this seems to be over my head....can anyone really help ? I managed to get past the white HTC screen by fastboot flashing a new recovery (philz then dees troy version of twrp)....I got a bootable commotio build....I also flashbooted 2.22.401.5, i thought it had fixed everything but in recovery i am getting the following errors.....
unable to mount /cache
failed to wipe dalvik
did I somehow mess up my partitions ? I need to wipe dalvik cache and cache in order to get a working rom on this damn phone.....
The issue has been fixed....
jxcorex28 said:
The issue has been fixed....
Click to expand...
Click to collapse
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
redpoint73 said:
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
Click to expand...
Click to collapse
Im not exactly sure what went wrong in the first place. I never pulled a logcat (from an app or through adp) since the problem no longer exists it looks like I never will unless I go through another similar thing. I wish I did know because it's killing me to know. I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
I have flashed atleast 500 times over a 8 year period on 4 different android phones, and Ive never once experienced the problem I had 2 days ago. Ive had 2 HTC phones, although, the experience with basebands were similar they were actually very different in every aspect. I had a TMO HTC G1 back in the day ( I had to learn how to do everything back when scripts or programs werent doing the grunt work (root)...
I had a TWRP backup of beanstalk saved (so kiddies, do your backups) that is what saved my ass. I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
I actually had to repartition my computer's hard-drive and reinstall windows 7 home edition, so I had to start over with practically everything...Im not going to use toolkits anymore. As you said earlier, it's just the easy way out. You wont learn anything about how to use ADB or Fastboot (although I applaud the one's who make the scripts or toolkits for those of us on the go).....
P.S.......If I can ever manage to break away from my dueling school schedule and my other priorities in life I plan on learning more about starting from the ground up and building roms, and not just throwing a few things together in the kitchen.....
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
jxcorex28 said:
I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
Click to expand...
Click to collapse
Yeah, I'm going to pull back on my previous statement that "3.28 will likely cause reception issues on AT&T's network" to instead say "may cause issues". And feel free to try it at your own discretion.
Reason being, I've seen maybe 3 reports now of this firmware working ok on AT&T, and no reports to the contrary so far.
Although, when folks tried the 2.22.401 "international" firmware on AT&T, there were several (even numerous reports) of signal issues, even NO SIGNAL. No reports of this so far on 3.28, so I'll be cautiously optimistic for the time being (until I see reports otherwise). Haven't personally tried it, and not sure I will as I don't really have time ATM to mess around with the possibility of signal issues or no signal.
jxcorex28 said:
I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
Click to expand...
Click to collapse
Did you try fastboot erase cache before trying to re-install recovery, or a different recovery? I've seen this simple step alleviate some pretty drastic issues with recovery.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
jxcorex28 said:
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
Click to expand...
Click to collapse
I can't speak personally, I'm not a Linux PC person. But my friends that are, seem to split among various distros: Ubuntu, Kubuntu, and Arch. One friend that is a particular Linux aficionado is on Arch, and said he was very happy with it.
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
jxcorex28 said:
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
Click to expand...
Click to collapse
Id highly rrecommend Linux Mint 17 Qiana MATE Edition .I use it with Windows 7. It is my favorite Linux OS. Not to mention that its perfect for Linux beginners.
That info would of been great a few days ago, but my laptop is screwed up now. Earlier I tried logging on,and couldn't because of some kind of remote error near the password field box on win7 HE...So I tried a system restore,and it failed so I f8 into recovery options and try using HP Recovery..everything went smooth into the first boot. I ended up getting a recovery installation incomplete and a 205 UIA failed 3 times. I believe my laptops recovery partition is corrupt,and I don't have a HP recovery disk, a win7 recovery DVD / Win7 recovery USB stick... I found what I need on HPs website, but its 30 bucks...BestBuy GS wants to charge me $69.99 for a diagnostics test and a retail version of win7 cost like 130
Its a 2011 HP Pavilion G-series laptop with windows 7 Home edition. What makes matters worse is I just partitioned the system a few weeks ago by using the recovery option HP makes for their devices...
Everything was great til about 10pm tonight...FML...now I actually gotta go to school to do my damn school work
jxcorex28 said:
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
Click to expand...
Click to collapse
I had that exact same issue yesterday... Twrp couldn't wipe anything and eventually kept rebooting after 20 or 30 sec in recovery.
I had to download the 1.58 RUU and run that, then flash Twrp back, reroot, then restore one of my backups from earlier in the day.
As far as fw goes, I had updated to 2.22.401.4, had that for a couple days, then updated to the 3.xx fw to install arhd 20.3. I liked it, but decided I love my dirty unicorns rom so decided to go back to the 2.xx fw. I tried to flash renovate 4.5.0, and that's when all the issues in twrp started. From what you're saying, it sounds like the issue could be caused from the fw updates.
How did you end up restoring your backup when they issue happened? I tried to restore mine with fastboot, but it was compressed and I couldn't extract the img files from the win files
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
jxcorex28 said:
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
Click to expand...
Click to collapse
I got it from skulldreamz thread on flashing fw by renaming it and putting it on root of ext SD card
Did you look into the contents of that zip to see if there was a recovery.img or boot.img file ? Those files usually overwrite the custom recovery (ie...TWRP or CWM). There are two ways to correct those red error messages you get in TWRP...
1. by flashing partition-fixer.zip (I have a copy if you need it)
2. By using a terminal emulator,and typing this command...
mke2fs /dev/block/mmcblk0p46
I believe this command is essentially what's included in the flashable partition fixer ( I haven't actually taken a look in that zip,so I could be wrong)...
I haven't had any problems as of late...either I'm starting to get back in the hang of dealing with HTC devices or I'm just lucky...
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
jxcorex28 said:
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
Click to expand...
Click to collapse
With the ones I got from skulldreamz' thread, I believe they were modified bc I didn't have to flash a custom recovery again after I flashed the fw. I never fastboot flashed them, I've always just renamed it 0P6BIMG.zip and put it on the root of the ext SD card
That's probably because skull removes those 2 files before uploading for download. I'm not sure if he does that for every zip....
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.