Related
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
Hello people!
First of all - Happy New Year!
Okay, my problem is this:
I gave my phone to a person who knows what he's doing, to change my ROM (switched from stock ROM to CM10).I wasn't there and didn't know what he did but I was glad that he did it. The ROM was still a beta (not sure how is it called for the ROMs) version and I had some problems with the camera, chrome and messanger were closing even if I didn't want them and many other problems which i dont remember now. This was the reason I wanted to change this CM10 to another ROM , but I had some problems with changing it. Took me like 4 hours (eventho my phone was unlocked) and i almost gave up when I tried for last time to install CM again and it worked! I don't know what I did because It was long ago. Anyways to my main problem:
Before 2 days I told myself ok now is the time to change the ROM (New Year - new ROM ). I started doing everything that the post I found says ( I can't give you link, but it's for dummies). All I did wrong was not downloading the whole folder with the boot.img (which I still don't have) ,but only the file boot.img from 2shared. I had to do the last step, because the device entered a Bootloop. Since then I Power ON my phone ,but all it does is to show the "HTC quitely brilliant logo. I tried to reinstall the Viper ROM , but nothing changed. I panicked. I had Trickdroid 6.0 on my device so I tried to install it too, but still the ending result was the same... The last choice I had was to install the CM ROM again, so I did it. Still nothing. I think it all came from the boot.img file i downloaded , but I'm not sure. I started to search forums for this kind of issue but I didn't find anything similar to this, or atleast I didn't search for the right thing. Anyways, I thought of doing a factory reset from the Fastboot mode, and after 2 hours of searching the forums I did a factory reset. The phone restarted and entered in the Recovery menu again. I didn't know what was I supposed to do there + I had NOTHING in the phone (which I knew it was going to happened) but I didnt think that the ROMs will be deleted too. So I tried to connect my phone with the USB ,but as usual it needs a full boot up to connect with the USB, so I can upload some files to it. Now all I can do is enter in the Recovery/Fastboot menu. Can anyone help me or does anyone have an idea what should I do?
P.S. Sorry for the long post. I'm desperate.
Can you sideload a zip through recovery? Because boot.img files are only a kernel, so you're going to need a complete kernel.
Sent from my Nexus 4 using Tapatalk
SMillerNL said:
Can you sideload a zip through recovery? Because boot.img files are only a kernel, so you're going to need a complete kernel.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I cannot connect to the computer. I don't have anything on my phone and I can't upload anything to the device. Except if there is a option to 'allow" something via fastboot from the computer. Since that is the only connection I have with the phone.
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.
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.
While trying to load a rom, I got a failed message, damn cat ran across the desk and it rebooted, I was to the point I should of flashed the overlay, did NOT make it that far. It boots up to the welcome screen, but I have no access to hit "start" as my touch screen is not working. Is it done for? I cant see it any longer in adb devices, so I cant continue where I left off. Linux cant see it at all. Windows knows its there. So it did not make a complete fash, it tried to reboot into stock i assume, looks stock. What can I do at this point? Any help would be great.
deleted
I got in. I can not enter fastbootd, and do not know where its saved. Can some one help me get my recovery back? I flashed a recovery backup, but it comes up witht he little dead andriod and no command error. I need to get to fastbootd. Any help would be wonderful.
If you can get into fastboot, isn't there a tool, LMSA rescue to bring back bricked device? wipes all data though.
Were you trying a custom ROM or stock? try booting to fastboot mode, power + vol-down, and fastboot flash the stock boot.img, can be found here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
hope this helps. I just got the phone yesterday, soft bricked trying to flash magisk, flashed stock boot and was back in business. I was not using any type of custom rom though.
I was able to find stock boot and recovery images, which allowed me to just start over. Here is an screen shot of what would happen when flashing any ROM.
That's two different attempts. With two different errors.
On a crazy note, I ordered and got in the exact same phone off eBay, has lineage os, magisk, twrp. Now from what I've read, twrp can't be used to install ROMs yet. I've actually tried it on the problem phone we are working on here, but can't swipe with it. The screen is not correctly responsive. Yet this eBay phone, works great... Not sure how he did it. Id love to figure this out, I can't let it beat me.
klloyd said:
I was able to find stock boot and recovery images, which allowed me to just start over. Here is an screen shot of what would happen when flashing any ROM.
That's two different attempts. With two different errors.
On a crazy note, I ordered and got in the exact same phone off eBay, has lineage os, magisk, twrp. Now from what I've read, twrp can't be used to install ROMs yet. I've actually tried it on the problem phone we are working on here, but can't swipe with it. The screen is not correctly responsive. Yet this eBay phone, works great... Not sure how he did it. Id love to figure this out, I can't let it beat me.
Click to expand...
Click to collapse
I would try this next: https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa