Hi, masterminds --
I've got a problem with my AT&T One X+. It will charge when off, and boot into fastboot, but that's as far as I can go. I can use the Terminal (Mac OS X) to send fastboot and adb commands, and flash recoveries, but whenever I reboot into recovery, I get stuck at the HTC logo, with no recourse. It just reboots incessantly to that logo screen.
I've tried the CWM and TWRP .img files, but nothing seems to work.
How can I get back to the bare, stock boot sequence?
What's the best way to flash CM 10.1.0 using adb or fastboot?
what's the best custom recovery to use?
Thanks, all!
esone1ll said:
Hi, masterminds --
I've got a problem with my AT&T One X+. It will charge when off, and boot into fastboot, but that's as far as I can go. I can use the Terminal (Mac OS X) to send fastboot and adb commands, and flash recoveries, but whenever I reboot into recovery, I get stuck at the HTC logo, with no recourse. It just reboots incessantly to that logo screen.
I've tried the CWM and TWRP .img files, but nothing seems to work.
How can I get back to the bare, stock boot sequence?
What's the best way to flash CM 10.1.0 using adb or fastboot?
what's the best custom recovery to use?
Thanks, all!
Click to expand...
Click to collapse
Are you on Stock ? If yes - would suggest you to rush to a hTC service centre, I had the same issue and there is no one to help me out (I was bootloader unlocked).
If you are already bootloader unlocked - you should use TWRP instead of CWM, as TWRP supports sideload.
Before using a 4.2 based ROM, make sure you have created 0 folder on your 'SD Card'
fastboot reboot ?
An HTC RUU should get you back up and running. Pretty sure it will wipe the entire device, though. http://www.androidfiles.org/ruu/?developer=EvitaRE . If you are interested in CM10.1 (or any AOSP-based ROMs for the AT&T HOX+ for that matter) be aware that call audio (and a couple of other things) is currently broken on the AT&T HOX+. Please make sure you are looking at the appropriate threads for your device, as none of the Interational HOX+ ROMs/kernels/recoveries are compatible with your device.
NasaGeek said:
An HTC RUU should get you back up and running. Pretty sure it will wipe the entire device, though. http://www.androidfiles.org/ruu/?developer=EvitaRE . If you are interested in CM10.1 (or any AOSP-based ROMs for the AT&T HOX+ for that matter) be aware that call audio (and a couple of other things) is currently broken on the AT&T HOX+. Please make sure you are looking at the appropriate threads for your device, as none of the Interational HOX+ ROMs/kernels/recoveries are compatible with your device.
Click to expand...
Click to collapse
Thanks for the advice! I'm going to try the RUU .exe file. I'm totally fine with it wiping the entire device.
Thanks, also, for the advice on CM10. Do you use a custom ROM that works well for the HOX+?
esone1ll said:
Thanks for the advice! I'm going to try the RUU .exe file. I'm totally fine with it wiping the entire device.
Thanks, also, for the advice on CM10. Do you use a custom ROM that works well for the HOX+?
Click to expand...
Click to collapse
As per my knowledge the Sense ROMs work just fine on ATT but there are issues with non Sense ROMs... Read the first few posts in the thread and last few before flashing...
The first few will give you the list of known bugs (by the OP) and the last few will give you bugs found by the users
Related
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.
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Htc ONE X+ Help!!
7virage7 said:
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Click to expand...
Click to collapse
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
thacruz said:
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
Click to expand...
Click to collapse
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Htc ONE X+ Help!!
7virage7 said:
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Click to expand...
Click to collapse
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
thacruz said:
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
Click to expand...
Click to collapse
Thanks for ideas, but it still does not work. Phone reverts its state. It's trully magical. Every time it reboots to the moment just after rooting. I have never seen anything like it before. Bootloader is always unlocked and memory chip state cannot be changed.
At least I haven't figure out how to do it yet
Anyone, please help!
EDIT:
A tried ADB sideload today, but after the file is sideloaded it can't be flashed - TWRP considers it corrupted and it vanishes after rebooting - AS EVERY CHANGE
I hope I didn't ruined my phone the first hour I got it, and XDA members could still help me. PLEASE
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
humzaahmed155 said:
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi, I think also it's is the explanation for HOX+ radio lacks, permanent screen locks after the sleep, etc... fails in my AT&T's unlocked HOX+, defective emmc or emmc firmware.. It´s possible?
You also can see it: http://forum.xda-developers.com/showthread.php?t=2404393
Don't really need some special help here, just want the device to function again no matter what way. (Don't care if it's factory reset completely it has nothing on it I was just using it for a bit of experimenting).
So anyway, I have an HTC One x that I tried to install Cyanogenmod mod on but when trying to flash it (I was a bit impatient and just did what I thought would work), it didn't work and I'm stuck on the HTC Boot screen. I can still restart the phone and get to the recovery menus or whatever they're called. But even when doing a factory reset it still just won't get past the boot screen.
I'm just someone who has a good love for android and got given this phone for free so I thought I might experiment with rooting and all that, (I don't want to do this to my main driver, the Z1, for the life of me).
Any help here would be great.
Thanks
MHarris333 said:
Don't really need some special help here, just want the device to function again no matter what way. (Don't care if it's factory reset completely it has nothing on it I was just using it for a bit of experimenting).
So anyway, I have an HTC One x that I tried to install Cyanogenmod mod on but when trying to flash it (I was a bit impatient and just did what I thought would work), it didn't work and I'm stuck on the HTC Boot screen. I can still restart the phone and get to the recovery menus or whatever they're called. But even when doing a factory reset it still just won't get past the boot screen.
I'm just someone who has a good love for android and got given this phone for free so I thought I might experiment with rooting and all that, (I don't want to do this to my main driver, the Z1, for the life of me).
Any help here would be great.
Thanks
Click to expand...
Click to collapse
If you had just used htcdev.com to unlock the bootloader and are still S-On, you need to pull/extract the boot.img from the CyanogenMod zip and install via fastboot.
es0tericcha0s said:
If you had just used htcdev.com to unlock the bootloader and are still S-On, you need to pull/extract the boot.img from the CyanogenMod zip and install via fastboot.
Click to expand...
Click to collapse
She's running all good now, thanks for that
MHarris333 said:
She's running all good now, thanks for that
Click to expand...
Click to collapse
You're welcome. Pretty common issue when people are getting used to how it works for HTCs.
Pro Tip: If you want to simplify the process, you can use this: https://play.google.com/store/apps/details?id=com.cgollner.flashify and install the boot.img with the phone while booted, then boot to recovery and finish the rom install. Recommend doing a nandroid recovery first, just in case the boot,img/rom combo does not work properly, otherwise if you flash it first THEN do a backup, the new boot.img will be matched with the old rom and might cause issues upon restoring if they are not compatible.
Alternative: S-Off. Depending on which hboot you are on, you should be able to do S-Off. It can be a bit of a pain to set up, but once you do, then you can install roms just like normal as the boot.img will be able to be flashed from recovery along with the rom like in most phones.
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....