HOX+ flashing rom issue - HTC One X+

Hello,
I have an AT&T HTC One X+ (plus). Currently, I have unlocked the bootloader, rooted, and now have the TWRP recovery on my phone. I will admit I am a n00b at Android, but some help on the following issue will be greatly appreciated. I believe I got the proper cyanogenmod and gapps files, and I then push them to my device via Terminal (Mac). However, when I go to install them, they come back as failed. It says "E:Unable to open zip file." If someone could tell me what the issue is, that would be great. I feel that I am very close to flashing a new rom, but I am in desperate need of assistance. If you could possibly link proper gapps and cyanogenmod (or other custom rom) files, I would really appreciate it.
Thanks,
JCarrot

JohnCarrot said:
Hello,
I have an AT&T HTC One X+ (plus). Currently, I have unlocked the bootloader, rooted, and now have the TWRP recovery on my phone. I will admit I am a n00b at Android, but some help on the following issue will be greatly appreciated. I believe I got the proper cyanogenmod and gapps files, and I then push them to my device via Terminal (Mac). However, when I go to install them, they come back as failed. It says "E:Unable to open zip file." If someone could tell me what the issue is, that would be great. I feel that I am very close to flashing a new rom, but I am in desperate need of assistance. If you could possibly link proper gapps and cyanogenmod (or other custom rom) files, I would really appreciate it.
Thanks,
JCarrot
Click to expand...
Click to collapse
First try re-downloading the zip file to rule out a bad download

Jonnibravo said:
First try re-downloading the zip file to rule out a bad download
Click to expand...
Click to collapse
If I download it and it decompresses and becomes a folder, should i compress it? Could the file not be compatible with Macs?

JohnCarrot said:
If I download it and it decompresses and becomes a folder, should i compress it? Could the file not be compatible with Macs?
Click to expand...
Click to collapse
You MUST NOT uncompress the zip file you have downloaded.
Check the MD5 checksum, as said by the previous user, it might be a bad download.
I hope you have taken care of moving all your data to the 0 folder...
Also, before trying non Sense ROMs on ATT - see the thread carefully (I have heard there are isues.. but I am not sure the truth because I don't own one )

Addicted2xda said:
You MUST NOT uncompress the zip file you have downloaded.
Check the MD5 checksum, as said by the previous user, it might be a bad download.
I hope you have taken care of moving all your data to the 0 folder...
Also, before trying non Sense ROMs on ATT - see the thread carefully (I have heard there are isues.. but I am not sure the truth because I don't own one )
Click to expand...
Click to collapse
I was able to get the file uncompressed. Then, I used adb push to put the file on my phone. I wiped the phone. When I tried to install the .zip file, it fails. Any suggestions?

If I do "adb push" for the files I want on my phone and I boot into recovery before it show something like "1309 KB/s (1050533 bytes in 0.783s)," the files may not have fully loaded onto the phone. Should I just wait a until they display something like that? Could this the source of my issues (that the files are not fully loaded)?

JohnCarrot said:
If I do "adb push" for the files I want on my phone and I boot into recovery before it show something like "1309 KB/s (1050533 bytes in 0.783s)," the files may not have fully loaded onto the phone. Should I just wait a until they display something like that? Could this the source of my issues (that the files are not fully loaded)?
Click to expand...
Click to collapse
I am assuming you have TWRP? Use adb sideload and not adb push. Since you want to install CM - I am assuming you have downloaded a file called CM10.1xxxxxxxxxxxxxxxxxx.zip (may be cm-10.1-20130607-UNOFFICIAL-enrc2b).
Use adb sideload to copy this zip file to your pone
Now use adb side load the ROM, the file should be renamed sideload.zip when it is copied on your phone.

Addicted2xda said:
I am assuming you have TWRP? Use adb sideload and not adb push. Since you want to install CM - I am assuming you have downloaded a file called CM10.1xxxxxxxxxxxxxxxxxx.zip (may be cm-10.1-20130607-UNOFFICIAL-enrc2b).
Use adb sideload to copy this zip file to your pone
Now use adb side load the ROM, the file should be renamed sideload.zip when it is copied on your phone.
Click to expand...
Click to collapse
I was able to get cm to work using advice push. I am using TWRP. Could it be possible that cm is really buggy because I used adb push. Sorry question mark not working. CM literally ceases and reboots every five minutes. It is practically not usable.

JohnCarrot said:
I was able to get cm to work using advice push. I am using TWRP. Could it be possible that cm is really buggy because I used adb push. Sorry question mark not working. CM literally ceases and reboots every five minutes. It is practically not usable.
Click to expand...
Click to collapse
nope, it's just super unstable right now. Not by any means a daily driver. Most of the other issues are not really being looked at currently until the devs manage to fix the current lack of call audio.

NasaGeek said:
nope, it's just super unstable right now. Not by any means a daily driver. Most of the other issues are not really being looked at currently until the devs manage to fix the current lack of call audio.
Click to expand...
Click to collapse
Are there devs still working on it? I thought they abandoned the HTC One X+.

There is certainly still work being done, as evidenced by this thread, though it is slow going. Lloir in particular should be commended for doing as much work on AT&T HOX+ as he does considering he doesn't even use the phone. All of that being said, from the looks of it our hopes of call audio being fixed (among other things) are slim

NasaGeek said:
There is certainly still work being done, as evidenced by this thread, though it is slow going. Lloir in particular should be commended for doing as much work on AT&T HOX+ as he does considering he doesn't even use the phone. All of that being said, from the looks of it our hopes of call audio being fixed (among other things) are slim
Click to expand...
Click to collapse
Could my issue of CM being so buggy and rebooting every 5 minutes be because I did not change the kernel? I am somewhat of an Android n00b, but I did get CM working on my HOX+ and unlock the bootloader. I just don't entirely understand why I need to change the kernel. Thanks for responding btw.

It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.

NasaGeek said:
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
Click to expand...
Click to collapse
Oh...I've already done that. I got my CM from lloir.com and I downloaded the boot.img along with the rom. I didn't know what the fastboot flash boot boot.img did. I just knew that I had to do it. I didn't know that was the kernel.

Different HOX+ ROM
NasaGeek said:
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
Click to expand...
Click to collapse
Do you know of any different roms (AOKP/Paranoid/others) that are less glitchy for the AT&T HOX+? The CM10.1 that is currently on my phone just is not daily driver material by any stretch of the imagination. I want a somewhat stable (it can reboot like twice a day but not every 5 minutes) kind of stock rom because Sense 4+ is killing me. Well, I've been using CM, but that constant rebooting is killing me, as well.

JohnCarrot said:
Do you know of any different roms (AOKP/Paranoid/others) that are less glitchy for the AT&T HOX+? The CM10.1 that is currently on my phone just is not daily driver material by any stretch of the imagination. I want a somewhat stable (it can reboot like twice a day but not every 5 minutes) kind of stock rom because Sense 4+ is killing me. Well, I've been using CM, but that constant rebooting is killing me, as well.
Click to expand...
Click to collapse
AFAIK all non Sense ROM are little unstable in ATT

I have CM 10.1 on the HOX+ International and it works just fine. no random reboots and pretty smooth. excellent battery life. Snappier than Viper, which I was on before this.

surfatwork said:
I have CM 10.1 on the HOX+ International and it works just fine. no random reboots and pretty smooth. excellent battery life. Snappier than Viper, which I was on before this.
Click to expand...
Click to collapse
The problem is with the ATT version...
We are lucky

Related

CWM 5.0.2.7 for the Vigor/Rezound

Just a heads up (and maybe I'm just late to the game) but I was looking through download.clockworkmod.com/recoveries and searched for "vigor" out of curiosity and saw a version of CWM built for it with an upload date of January 14th. I am not suggesting that anyone try it (I'm awaiting a response from Koush regarding the state of the code and it's stability) but wanted to let people know it's there. Once I get a response from Koush via twitter I'll update the post.
All credit to Koush/ClockWorkMod devs for their work - I take no credit at all. If you flash this linked file I assume no responsibility for damages incurred (if any). Flash at your own risk.
Link to the actual recovery .img:
Edit: Removed because I tried the image and is not functional. Does not boot into recovery after install.
I might look at it later, but I have been happy with AmonRa so far. A safe way to test it without making it "permanent" is fastboot boot cwmrecovery.img
con247 said:
I might look at it later, but I have been happy with AmonRa so far. A safe way to test it without making it "permanent" is fastboot boot cwmrecovery.img
Click to expand...
Click to collapse
Ah thanks con, that command is new to me (although it really shouldn't be at this point lol). I'll give it a try later as well. AmonRa works nicely for me too, but if we can get some of these ROMs uploaded to Rom Manager servers that'd be nice.
The image I originally supplied does not work, so I removed the link. A mod may close this thread at their discretion or keep it open for future updates regarding official CWM releases for the Vigor.
ok thanks for the heads up.
Nice to know Koush et al are at least trying lol...
There are 2 images in there for the Vigor, as well as the md5sum.
AtLemacks said:
There are 2 images in there for the Vigor, as well as the md5sum.
Click to expand...
Click to collapse
Well if you look at the MD5 checksum .txt for either file you'll note that it indicates "Froyo" in part of the build directory so clearly something is amiss. I tried the larger of the two .img files available but I'll venture to say that neither is functional.
Another heads up - RomManager is adding support for "unsupported" devices in the coming update so Devs should be able to upload Roms to Koush's servers soonish. Look to the clockworkmod official twitter page for links/info.
Sent from my ADR6425LVW using xda premium
Deathbyfugu said:
Well if you look at the MD5 checksum .txt for either file you'll note that it indicates "Froyo" in part of the build directory so clearly something is amiss. I tried the larger of the two .img files available but I'll venture to say that neither is functional.
Click to expand...
Click to collapse
Wonder why he would build it for Froyo, considering the phone came with GB.
Several of the various recent images built the same way. Maybe they've been in a rush to release things and messed up the build parameters.
Sent from my ADR6425LVW using xda premium
But I haven't seen, or heard an official release. Our 5.5.0.4 port works just fine as is. It is working for me from ICS ROM's also, so I wonder if we just port an official from the Nexus?
Edit: Nevermind, the official on my girlfriend's Nexus is 5.5.0.4 also.
I wish I had seen this before I flashed CWM for the Rezound, when the option showed up on my phone. I'm stuck in reboots and have to start all over.
Darn.
******
Okay..I thought this would be an easy task... flashing AmonRa back onto the phone, but it's not...or I'm doing something incorrect.
I access HBOOT and have the image on the SD card, but to no avail.
******
Fixed it!! This was the key, from this thread: http://forum.xda-developers.com/showpost.php?p=21870383&postcount=255
adb reboot bootloader
fastboot flash recovery recovery.img
Had to start from scratch and thankfully Titanium Backup Pro restored everything and I mean everything.. Folders and icon settings too.
(sidebar) On a reboot, I got the process.com.htc.android mail 'is not working' error. And since it was after the BAMF screen, that started a do-loop as well. Luckily, an app didn't install completely, so I was able to access and open TB via Market, and DELETE htc.android mail. Problem solved!

[S-OFF Only!!!] Install OTA Update and Maintain Root Access

UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs
bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium
Thanks for taking the time to do a write-up OP!
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.
Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.
Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.

[Q] New to Thunderbolt, Root, and Roms

I've recently purchased a Thunderbolt from eBay (which I know is always a bit sketchy, and that the device is getting a bit older) but so far it's been a relatively good little phone. I'm definitely enjoying the LTE over the 3G my iPhone 4 had before I accidentally murdered it. I have the HTC Dev unlock on this phone, but the stock ICS rom pushed out by Verizon and HTC feels bloated and slow to me, having come from the iPhone 4 running a jailbroken iOS 6.1.2.
Would someone be so kind as to point me towards a fast, stable ICS or Jellybean ROM and instructions on how to install it and a proper recovery on my phone? I'm not all that picky about appearances, and I wouldn't mind running stock Android either if someone can tell me how to get it running on this phone. Currently I'm running all of the latest updates courtesy of the previous owner (I'm up to HBOOT 1.08, ICS 4.0.4, software version 7.02.605.10 710RD).
Thanks in advance for any help you can provide.
EDIT: After much more tinkering, I have managed to get Clockwork Mod Recovery running on my phone, but I would still very much appreciate if someone had a suggestion for a ROM that runs quickly and efficiently.
Look through the Development forum here and head over to Infected Roms. Lots of answers to your questions in both places. Just takes a little time go through the threads to find what you need.
Sent from my ADR6400L using Tapatalk 4
Raddatzjos said:
I've recently purchased a Thunderbolt from eBay (which I know is always a bit sketchy, and that the device is getting a bit older) but so far it's been a relatively good little phone. I'm definitely enjoying the LTE over the 3G my iPhone 4 had before I accidentally murdered it. I have the HTC Dev unlock on this phone, but the stock ICS rom pushed out by Verizon and HTC feels bloated and slow to me, having come from the iPhone 4 running a jailbroken iOS 6.1.2.
Would someone be so kind as to point me towards a fast, stable ICS or Jellybean ROM and instructions on how to install it and a proper recovery on my phone? I'm not all that picky about appearances, and I wouldn't mind running stock Android either if someone can tell me how to get it running on this phone. Currently I'm running all of the latest updates courtesy of the previous owner (I'm up to HBOOT 1.08, ICS 4.0.4, software version 7.02.605.10 710RD).
Thanks in advance for any help you can provide.
EDIT: After much more tinkering, I have managed to get Clockwork Mod Recovery running on my phone, but I would still very much appreciate if someone had a suggestion for a ROM that runs quickly and efficiently.
Click to expand...
Click to collapse
I just mashed my Rezound, so I'm back on the TBolt as well and had to go through the same thing. Before I go all out on this, I can tell you that the process to get this done isn't that bad considering I will compile all the instructions here, but you have to flash a patch through HBOOT then relock the phone, take it back to an older ROM, run revolutionary on it for s-off, load radios, then back to ICS lol. If you think it will be worth it to you, let me know an I will post the links. It's just a bunch of back and forth and I took me about a week to find all the pieces.
FirePsych said:
Look through the Development forum here and head over to Infected Roms. Lots of answers to your questions in both places. Just takes a little time go through the threads to find what you need.
Sent from my ADR6400L using Tapatalk 4
Click to expand...
Click to collapse
Yeah, there's a lot of pages to go through, and apparently I'm not searching for something the right way.
DiaboliqAngel said:
I just mashed my Rezound, so I'm back on the TBolt as well and had to go through the same thing. Before I go all out on this, I can tell you that the process to get this done isn't that bad considering I will compile all the instructions here, but you have to flash a patch through HBOOT then relock the phone, take it back to an older ROM, run revolutionary on it for s-off, load radios, then back to ICS lol. If you think it will be worth it to you, let me know an I will post the links. It's just a bunch of back and forth and I took me about a week to find all the pieces.
Click to expand...
Click to collapse
Hey, works for me! I really want to like Android, but Verizon's firmware is so bloated and slow it makes it hard to do. I'm willing to go through the work if it means I can get a phone that runs the way I want.
My cousin keeps telling me I need to run pure Android, and honestly, that's what I'd like to do if at all possible, but any ROM that runs efficiently is good for me.
Raddatzjos said:
Yeah, there's a lot of pages to go through, and apparently I'm not searching for something the right way.
Hey, works for me! I really want to like Android, but Verizon's firmware is so bloated and slow it makes it hard to do. I'm willing to go through the work if it means I can get a phone that runs the way I want.
My cousin keeps telling me I need to run pure Android, and honestly, that's what I'd like to do if at all possible, but any ROM that runs efficiently is good for me.
Click to expand...
Click to collapse
Go to this page to start the journey http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/8695-guide-how-gain-root-s-off-after-taking-ics-ota.html and just FYI, I use 4ext recovery now and love it, but you have to be s-off and rooted to get it. use the QR code found here http://forum.xda-developers.com/showthread.php?p=31966447 It will download and app to your SD card (typically) under "Downloads" and you will need a file manager or root explorer to install it, and I had to download "4EXT Recovery Touch v1.0.0.5 RC5" twice before it took.
Then once you have gone through those steps (I had TWRP recovery and it worked) you will be on GB. To save some time, go to http://forums.infectedrom.com/ and create an account. I doesn't have to be verified by the admin to download. Once your account is created, go to http://forums.infectedrom.com/showthread.php/1912-ROM-Official-Thunderbolt-ICS-Rooted-Deodexed-Stock?p=67120&viewfull=1#post67120 and download the radio and flash it, then download the ROM of your choice. I used the "DEBLOATED Rom Deodexed version: 7.02.605.10 710RD". It's stock with all of the VZW crap pulled out and deodexed. I'm haveing to revert back to a custom GB ROM because the new ICS kernel doesn't have the built-in support for the 2-way call recording feature, but everything else works like a dream. I agree, that for the TB, staying close to stock on ICS is a good idea since development has dwindling for this device. Cheers and let me know if you need any help with this. just reply here
DiaboliqAngel said:
Go to this page to start the journey http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/8695-guide-how-gain-root-s-off-after-taking-ics-ota.html and just FYI, I use 4ext recovery now and love it, but you have to be s-off and rooted to get it. use the QR code found here http://forum.xda-developers.com/showthread.php?p=31966447 It will download and app to your SD card (typically) under "Downloads" and you will need a file manager or root explorer to install it, and I had to download "4EXT Recovery Touch v1.0.0.5 RC5" twice before it took.
Then once you have gone through those steps (I had TWRP recovery and it worked) you will be on GB. To save some time, go to http://forums.infectedrom.com/ and create an account. I doesn't have to be verified by the admin to download. Once your account is created, go to http://forums.infectedrom.com/showthread.php/1912-ROM-Official-Thunderbolt-ICS-Rooted-Deodexed-Stock?p=67120&viewfull=1#post67120 and download the radio and flash it, then download the ROM of your choice. I used the "DEBLOATED Rom Deodexed version: 7.02.605.10 710RD". It's stock with all of the VZW crap pulled out and deodexed. I'm haveing to revert back to a custom GB ROM because the new ICS kernel doesn't have the built-in support for the 2-way call recording feature, but everything else works like a dream. I agree, that for the TB, staying close to stock on ICS is a good idea since development has dwindling for this device. Cheers and let me know if you need any help with this. just reply here
Click to expand...
Click to collapse
Excellent! Thank you for this. I guess I know what my project is for tonight.
Raddatzjos said:
Excellent! Thank you for this. I guess I know what my project is for tonight.
Click to expand...
Click to collapse
No problem, and if you need any help or it's unclear, just let me know. Oh, and if I helped you out, please hit the "Thank" button on that post Cheers
Yeah, I strongly recommend ditching clockwork mod for 4ext.
Sent from my ADR6400L using Tapatalk 2
Shadow Death said:
Yeah, I strongly recommend ditching clockwork mod for 4ext.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I've been attempting to do just that, and every time I try to load my recovery, I keep getting ClockworkMod. 4ext fails to install, despite the app saying it was successful.
Raddatzjos said:
I've been attempting to do just that, and every time I try to load my recovery, I keep getting ClockworkMod. 4ext fails to install, despite the app saying it was successful.
Click to expand...
Click to collapse
Email the Dev. He's extremely responsive and very helpful.
Sent from my ADR6400L using Tapatalk 2
Raddatzjos said:
I've been attempting to do just that, and every time I try to load my recovery, I keep getting ClockworkMod. 4ext fails to install, despite the app saying it was successful.
Click to expand...
Click to collapse
I don't quite remember how I got to the end result of 4ext actually working but I remeber I had to download it twice from the installer app, and told the app to wipe cache + dalvik... but just to make sure, check these steps:
1) make sure you're rooted with s-off and have SU and busy box installed.
2) download the updater app file from the link provided in the QR code (from previous post).
3) make sure "unknown sources" is enabled in settings so you can install the updater app, then find the app in your download folder on your SD card and install it.
4) open the updater app and give it SU permissions, then run the install/update option and select the proper file. This will also be stored on your SD card (in a 4ext folder I think...don't quote me on that though).
after install you should be good, but I believe you can push via ADB as well. Attached is a PDF from the Dev on this as well.
---------- Post added at 12:32 PM ---------- Previous post was at 12:26 PM ----------
Sorry, I guess the PDF was too large. just remove the "http://forum.xda-developers.com/" out of the link and replace it with "http://www.". http://forum.xda-developers.com/4ext.net/install.pdf I can't post external links yet.
Now that I am thinking about it. Did you update super user or super su after getting root? The app itself probably needs it and the binary as well. You can update the binary by opening the app. It should prompt you to update it.
Sent from my ADR6400L using Tapatalk 2

Stock Recovery Needed For ZTE Avail 2 (Z992 - AT&T)

I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex, ​
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app

Wiped OS on HTC One X+

So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.

Categories

Resources