Hi everyone!
Okay, so here is my problem. I've been rooted/unlocked for a while now with TWRP recovery. I've never had a ROM on this phone yet (coming from GNex). I attempted to install Android Revolution HD. I flashed the boot.img from the thread, but forgot to 'fastboot erase cache' afterwards. Rebooted the phone, and now is stuck at HTC logo screen.
Here is what I tried:
1.) Wiped everything, flashed Android Revolution HD anyway afterwards, however after done installing, when I reboot TWRP claims I have no OS installed????
2.) Use RUU to reinstall the stock img's and then RUU, however, when I load the RUU wizard to get the rom.zip, its always corrupted and I can never open it???
I got the RUU from the RUU the thread posted in this forum by EvitaRE
At this point, I don't know what to do. Unless someone has a copy of the rom.zip.
I was also thinking of flashing another boot.img/ROM combo to see if that helps.
Is your phone an International (ENCR2B) model or North American (EVITARE) model?
Android Revolution HD is only compatible with the Global/International version of the HTC ONE X+
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
Hi,
if Desire X EMMC is bricked and phone stuck on htc boot logo screen.
so via CWM can we partition our external SD as EMMC and boot the phone.
Regards
Bluffmaster
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
vogonpoetlaureate said:
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
I think maybe is a guide not an help thread from his post..
xpirt
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
bluffmaster said:
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
Click to expand...
Click to collapse
Find the decrypted rom.zip somewhere and extract the boot.img. Flash that. Then flash Desire X 1.18 stock rooted rom to give them root and deodex. Tell your customer they're rooted and that everything should work fine...
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
bluffmaster said:
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
Click to expand...
Click to collapse
Yes!
Dear Stereo 8,
I Just Follow all you instruction , but i got black screen after htc sound ?
any suggestion
Weird... I'm clueless...
Flowed from my HTC branded muffin...
Hi,
Riff box release new DLL, so after resurrection with new dll i flash with stock ruu but phone stuck at boot screen and also not go to recovery.
from old dll it stuck on boot screen but can go to recovery so i can flash CWM but after new dll no recovery ?
What can i do .. confused
Fastboot flash recovery if you can go to fastboot.
Flowed from my HTC branded muffin...
i can boot to fast boot and i install CWM Recovery via fastboot.
but when i go to recovery its stuck at htc logo then restart it
Well, it's probably dead if you can't boot it whatever you flash....
Flowed from my HTC branded muffin...
You are wrong, Riff box restores the EMMC to stock plus if you get successful Resurrection with Riff it should be fine this means the problem is NOT EMMC which leads me to believe the device has a hardware fault but then you say if you install rom to Sd-ext the phone boots although unstable it atleast boots up. Which now leads me to think the device may have a unstable EMMC which means it needs the chip replacing. what you need to do is go to fastboot mode and open up a new CMD window and cd into your fastboot dir and type fastboot oem lock. Then run the Stock RUU and let it reboot into android. if that still dont help then PM me and send me your logs of resurrection from riff box and ill take a look at them see what the errors are thanks
I got my DNA back in December, unlocked with S-ON, rooted, and flashed a lightly modified stock ROM. It's been super stable, so I figured I wouldn't mess with it, and I've been running it since.
Yesterday, I was trying to free up some space on my device by integrating updates of system apps through Titanium Backup, and it jacked stuff up pretty royally. I figured, this is a great chance to install a new Sense 5 ROM.
I went through TWRP, installed the new ROM, cleared data, and when it restarted, it hung at the white HTC screen. Undeterred, I tried again through recovery. Then through sideloading a different ROM. Then by restoring a backup, downloading a new ROM and trying through recovery. Then installing CWM instead of TWRP and trying that way. Then by sideloading through CWM.
Every single method by which I've tried to install a new ROM has resulted in the phone hanging indefinitely at the white HTC screen.
I have obviously searched repeatedly for a fix for the white screen issue, and while I can restore an old backup and get the phone running, I can't seem to find a solution that gets me up and running on a new ROM. I'd hate to go through all the work (my phone's been unusable since around 8 PM last night) and not come out of it with a new ROM.
Am I missing something? Maybe I should be installing a new kernel before installing the ROM?
you are s-on you must flash the kernel boot.img via fastboot then flash kernel modules via recovery
copy boot.img from rom.zip
in command prompt goto folder with boot.img and enter
fastboot flash boot boot.img
then create a flashable module.zip and flash via recovery or adb eacxh module into system folder or just s-off your device and re flash rom.zip
The best way to fix ur phone now is to go through RUU, first relock the bootloader through fastboot, then enter RUU again through fastboot nd run the RUU from ur pc, ur good to go.
The reason it's getting stuck thr is becoz the system partition isn't getting mounted
As soon as I typed "S-On" in that original post, I started getting suspicious that might be the problem, but none of the ROMs I was trying specifically mentioned the need to be S-Off. But that does make sense.
So I spent the afternoon getting it S-Off, which was a bit of a hassle, and now in about three minutes, I see if I can indeed flash a ROM. I feel pretty optimistic, though.
Update: Success. I am now a very happy person.
congrats hope you enjoy
now no need for anything special to flash roms or kernels.
Hi Everyone!
I am new in this forum, so please be nice. i have problemwith my htc desire x. I have unlocked bootloader, installed CWM 6.0.3.2, and when i made S-off by rumrunner I can't start any rom. i tried stock with stock kernel; stock with nexus kernel; miui with nexus kernel;miui; myONEdx+;mySENSEdx+ and anyone of them can't start. i can open recovery, hboot, fastboot etc. but i can't start any rom
On the bootloaderscreen: which HBoot version do you have and what text is on top of that screen (text starts probably with PROTOU).
CWM: take a different recovery. Tutorials and links can be found on this link.
i have hboot-1.25.0002
radio-1.15.40.04
PROTO PVT SHIP S-OFF RL
CID-T-MOB009
I tried older cwm and two versions of twrp before and none of them let me install sucessfully an os.
Maybe this thread is of any help? Looks like the same problem. Install TWRP 2.7.1., format boot partition. If you already installed TWRP 2.7.1: what happens?
i think it is another problem because i have message from twrp "no os installed". today i discovered that twrp and cwm can't write anything on /system. it only made "bin folder which is empty. i tried to repair and changing filesystem from recovery but it didn't helped.
Are you able to format the partitions? Maybe one of the guru's can join in this thread
sometimes i can but sometimes can't even mount it.
i talk today with my friend and told that might be important information: i made s-off without root.
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks