Hi everyone, i get desire s yesterday .
I dont know what to do i only see this on screen when I go to bootloader. it hasn't a rom, only 1-2 sec a video like demo. I hear that this phone was promotial in market and dont have system.
What can I do? I know to download, a custom rom and install form TWRP because i use HTC One S but is it all i must to do on this desire S?
Look at the picture
Use fastboot to flash a recovery then flash ROM through new recovery
Sent from my Nexus 4 using Tapatalk 2
Is it all I need to do?
Go to htcdev.com and unlock your bootloader. Then flash a recovery using fastboot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:31 PM ----------
Can you access your system?
wuksha said:
Is it all I need to do?
Click to expand...
Click to collapse
Cant say for sure as all you can tell me is you got a phone and it doesnt boot, this would be the first step in troubleshooting though
vhngu930 said:
Go to htcdev.com and unlock your bootloader. Then flash a recovery using fastboot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:31 PM ----------
Can you access your system?
Click to expand...
Click to collapse
The phone is s-off, unlocking the bootloader with htcdev would be a step backwards
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Cant say for sure as all you can tell me is you got a phone and it doesnt boot, this would be the first step in troubleshooting though
The phone is s-off, unlocking the bootloader with htcdev would be a step backwards
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
What is s-off?
The top line on the pic, he has an engineering bootloader with radio secure flags removed (s-off)
Sent from my Nexus 4 using Tapatalk 2
Thanks guys,
i will record video tomorrow what I can see on phone and i hope it will bi enought to establish the diagnosis of a problem.
Hi again,
i flash recovery (there were only "!" in red triangle when I access recovery) , I try TWRP but touch function didn't work so i flash clockwork and i installed custom ROM but when i try to reboot only appear white screen with green text "htc" and it is all, i change ROMs several times but problem is the same. I dont know what to do now.
Look at the picture, near the touch there is "fail".
How did you install the ROM?
When in recovery make sure you do a full wipe, even better do this from fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery
Now boot to your new recovery again, wipe all, install a common stable ROM for your phone (like cyanogen) then before your reboot go to advance and copy recovery log, now reboot
If you still get stuck at splash post your recovery log
Sent from my Nexus 4 using Tapatalk 2
I flash clockwork recovery from fastboot and put rom on sd card and install from recovery.
i dont know what to do next, I changed hboot to ver 7.00.1002. and again only
appear.
Same again
Thanks demkantor, i tried that and problem didn't disappear. Only change is that after 10seconds phone turn off and again the same thing appear but this time forever. I notice that when I enter hboot i have this on screen on 1s look at the picture with green words. (I captured that earlier, now hboot ver is 7.00).
the second picture is about log I captured .
From the bootloader choose image CRC, it takes about 5 minuets capture but get it and then compare before and after flashing ROMs, if it changes its at least flashing to the right partition. And double check that the recovery your using is meant for your phone, also if you pull the full recovery logs onto SD card and then look at them you can check what partitions its trying to flash to
Sent from my Nexus 4 using Tapatalk 2
here is a pictures with old rom, when enter commands you give me at the botoom of this page, when i enter recovery, when instalation completed (I use this time ViperSaga2.2.0), and image CRC after installing ROM and Log after all of this.
Theres something missing and off hand I'm just not sure what, it sounds as if you are doing everything correctly.
I see you flashed a ROM with aroma installer, can you flash again only this time save the log at the end (from within aroma) and upload it?
Sent from my Nexus 4 using Tapatalk 2
I'm poor guy, i installed this and after that i can't access recovery and boot, now after every 10 seconds phone restart. look at the video in the link, I'm stupid now i dont know how to go step back.
Now the phone is boot only in bootloader. unlucky I...
VIDEO
There is probably a PG88IMG.zip that may help, but being I've never used your device before I would suggest asking your questions in your device's forum as someone there is sure to at least know what is going on. Probably should link this thread too in your new one.
There may be a common problem/solution for your phone that those in that forum will know, and being I'm on mobile its hard for me to search the forums to help without spending a huge amount of time
Best of luck and hopefully you can find your answer!
Sent from my Nexus 4 using Tapatalk 2
Related
I have really tried, spent 4 hours searching the web but my phine has been stuck at the htc logo upon booting, I can acess the bootloader and CWM and have the recovery etc. but cant figured out how to "unbrick" my phone, HELP! please!
htatw said:
I have really tried, spent 4 hours searching the web but my phine has been stuck at the htc logo upon booting, I can acess the bootloader and CWM and have the recovery etc. but cant figured out how to "unbrick" my phone, HELP! please!
Click to expand...
Click to collapse
Hey I´m at the same Problem. Can you connect your Phone to your PC?
Then search for a RUU for your Device... and run it... I have the hope that this works at mine htc but the battery is lower then 30% and i have no idea why it doesnt charge... maybe yours is over that...
muhhh351 said:
Hey I´m at the same Problem. Can you connect your Phone to your PC?
Then search for a RUU for your Device... and run it... I have the hope that this works at mine htc but the battery is lower then 30% and i have no idea why it doesnt charge... maybe yours is over that...
Click to expand...
Click to collapse
I plugged it in and yes, it charged! but I am gonna try the RUU now, ill tell you the results, really never encountered this before ;(
May I ask why you want to relock your bootloader?
If your phone is not charging, it's probably because your Recovery is not the latest to date.
@muhhh351
You should flash a Recovery known working on charging mode, the first releases were lacking this mode, but this is resolved now. Click on Frequently Asked Questions in my signature everything is there for you to find about HOX+ and their recoveries.
Lucky Thirteen said:
May I ask why you want to relock your bootloader?
If your phone is not charging, it's probably because your Recovery is not the latest to date.
@muhhh351
You should flash a Recovery known working on charging mode, the first releases were lacking this mode, but this is resolved now. Click on Frequently Asked Questions in my signature everything is there for you to find about HOX+ and their recoveries.
Click to expand...
Click to collapse
hey, I already have CWM, is that enough? I also have the respective RUU,
htatw said:
hey, I already have CWM, is that enough? I also have the respective RUU,
Click to expand...
Click to collapse
TWRP is more complete and a rigourously tested recovery. CWM was modded to work on the HOX+.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Lucky Thirteen said:
TWRP is more complete and a rigourously tested recovery. CWM was modded to work on the HOX+.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Click to expand...
Click to collapse
CWM wasn't "modded" it's just crap.
Lloir said:
CWM wasn't "modded" it's just crap.
Click to expand...
Click to collapse
I tried to be polite (anyway I am not allowed to talk like that, I never developed any sort of app, neither a ROM or kernel so I am not very qualified to judge others work), I'm sure you understood what I meant.
And yes I agree everything is way more complicated and unstable with CWM.
Please help. I'm having same problem. I can get into bootloader and fastboot and even successfully installed recovery but I can't get into recovery bc I always go to that white htc screen and no idea what to do next. Please please help me. I am on 1.15 software and 1.32 hboot and 4.1.1 Android version
Thank u
Sent from my VZW-I535 using xda premium
Reboot your phone in Bootloader mode (fastboot) you should have this 4 choices :
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
leave HBOOT highlighted then press the power button once, a new menu will appear :
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
From there with the Volume control (up & down) simply select RECOVERY and press Power button one time, your phone should Reboot in Recovery mode.
When in Recovery mode the VERY FIRST thing you will do, is a complete backup of your actual ROM and you will keep it as long as you gonna own the phone, so put this backup in a safe place on your computer and make sure to never delete it.
Thank you but the thing is.. I put twrp on it and version 2.3.3.0 and it won't boot in it. Any ideas why? Then I looked for a more recent recovery and I wasn't sure if this is evita?? So, basically I'm still unable to get into recovery and it goes to that htc white screen.
Btw. Your instructions are excellent
Ty
Sent from my VZW-I535 using xda premium
All right, do you have some time ahead of you?
Yes I am available
Sent from my VZW-I535 using xda premium
OK can you confirm me which phone version you do own
Second line in bootloader
EVITARE_UL (AT&T or TELUS)
or
ENRC2B (INTERNATIONAL)
It is the at&t version
Sent from my VZW-I535 using xda premium
Is your SDK/ADB Tool correctly installed?
Link in my signature...
Yes and I use windows 7 and open my command prompt within platform tools. My drivers say MY HTC. Yes. Ty
Sent from my VZW-I535 using xda premium
OK I will give you a trick...
Navigate to platform-tools of your SDK folder.
Right click and create a New text document
In the new text paste this : c:\windows\system32\cmd.exe
Save it with this name : StartADB.bat (important to save it with .bat extension and overwrite the warning)
Now right click again on your new bat file, and create a shortcut to your desktop.
Now try to adb devices your phone via your new desktop shortcut.
Type this command with your phone plugged : adb devices
You should have your serial in return
OK I am doing that. Please give me a few MIN. Ty
Sent from my VZW-I535 using xda premium
Sure! During that time please download one of these ROMs I will help you installing this ROM because I know them well, then once you'll be up and running you'll decide which ROM will suit more to your need.
Download Elegancia for HTC One X + by clicking HERE
..
Really noone can help? I am really worried, i know that i shouldnt do something which i dont completly understand, i am stupid. I really just want my phone back, even without root. As i mentioned before, I have PhillZ Touch 5 (CWM v6.0.3.7) recovery and acces to bootloader. My CID is T-Mob009.
Could you please tell me at least if this is fixable? Can i go to my local phone service and they will fix it for me? Or can i do something at home?
jeryh160 said:
Really noone can help? I am really worried, i know that i shouldnt do something which i dont completly understand, i am stupid. I really just want my phone back, even without root. As i mentioned before, I have PhillZ Touch 5 (CWM v6.0.3.7) recovery and acces to bootloader. My CID is T-Mob009.
Could you please tell me at least if this is fixable? Can i go to my local phone service and they will fix it for me? Or can i do something at home?
Click to expand...
Click to collapse
it's still can be fix it, not a big problem
maybe you can try reinstall the stock rom
Don't go to local phone service, they can't help
Just find a ROM specific for your phone (search xda for desire x) and put it on sdcard. Either with an external SD reader or through recovery. Then wipe all in recovery, then flash ROM and gapps if needed
Then reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
jeryh160 said:
Long story short: I think i bricked my HTC Desire X. After rooting (succesful) i tried to remove stock T-Mobile apps. They were re-installing after reboot. I did some research and found many solutions, one of them was to install custom kernel. So, i grabbed neXusKERNELv3 and using WinDroid HTC Desire X Toolkit (Fastboot Commands > Flash > System Image) i flashed .img file to my phone. After rebooting nothing happens - HTC quietly brilliant logo, vibration and blank black screen.
One of the solutions of this problem i found in the internet was to install custom rom, but to do so, i have to acces my sd card, which i cant.
I have acces to bootloader and recovery (phillaz touch 5).
Anyone can help me? I'm noob, i just wanted to get rid of those annoying T-Mobile apps!
Thanks in advance and sorry for my bad English, im not native english speaker.
Update: I turned on the phone and left it alone for some time - after HTC logo and black screen nothing happens for some time and then htc logo appears again, and there is black screen again.
Click to expand...
Click to collapse
Dude one thing, your phone isin't bricked and you said you have Phiz touch recovery right? You can mount your SD card from there (I believe) then...
Before you do any of these make sure you have an unlocked phone (I know you said it. Rooted and unlocked bootloader), java and hansoon 2000's toolkir (optional, if you don't want to use CMD.) and an updated phone (you should have the 1.25 Hboot by now.)
1. Download a ROM and extract the boot.img to the folder where you have "fastboot.exe"
2. Boot your phone to recovery then mount your SD card from there.
3. Copy the ROM on to your SD card. (Oh you know that.)
4. Reboot back to bootloader and select fastboot
5. Plug your phone to your computer using a USB cable and open a command prompt window (CMD)
6. Type the following codes...
Code:
fastboot devices
Then
Code:
fastboot erase cache
And finally
Code:
fastboot flash boot (name_of_image).img
7. BACK UP YOUR STOCK ROM
8. Do a wipe data/factory reset
9. Wipe dalvik cache.
10. Flash the ROM that you placed in your SD card.
I hope it worked lol. Goodluck bro!
In addition if you don't have card reader
1. Flash TWRP or CWM recovery
2. From recovery open "ADB Sideload"
3. Flash the rom.zip with ADB sideload
For more info: http ://android-revolution-hd.blogspot.com.tr/2013/12/ow-to-use-adb-sideload.html
4. Flash kernel (boot.img) via fastboot
Done
I cant believe i was such a dumbass and i didnt think about THAT simple solution earlier! Anyway, my phone's working again thanks to you. IDK why flashing a kernel through that tool i mentioned in 1st post didnt work, but nevermind. Thank you again and have a good day!
jeryh160 said:
I cant believe i was such a dumbass and i didnt think about THAT simple solution earlier! Anyway, my phone's working again thanks to you. IDK why flashing a kernel through that tool i mentioned in 1st post didnt work, but nevermind. Thank you again and have a good day!
Click to expand...
Click to collapse
Friend,
can you tell me what should I exactly do. My problem is as same as you!
Where can I download flashable zip?
---------- Post added at 09:28 AM ---------- Previous post was at 09:02 AM ----------
jeryh160 said:
I cant believe i was such a dumbass and i didnt think about THAT simple solution earlier! Anyway, my phone's working again thanks to you. IDK why flashing a kernel through that tool i mentioned in 1st post didnt work, but nevermind. Thank you again and have a good day!
Click to expand...
Click to collapse
Friend,
please let me know where can I download ROM and boot.img files. Then I can execute same steps ..
thanks for advance
anybody there to help me?
veerusayz said:
anybody there to help me?
Click to expand...
Click to collapse
Just choose a ROM from Android General Section and download it; also you can choose a kernel from Original Android development.
i don't know which ROM to download. can you pls share me the trusted ROM link so that I can download
Why people having problems when they flash kernel through toolkits? Any reason?
Sent from my HTC Desire X using xda app-developers app
veerusayz said:
i don't know which ROM to download. can you pls share me the trusted ROM link so that I can download
Click to expand...
Click to collapse
Download any jb Rom u like. See the screenshots of every rom & download the one which u want.
veerusayz said:
i don't know which ROM to download. can you pls share me the trusted ROM link so that I can download
Click to expand...
Click to collapse
Go to android development section where you can find various roms like this
http://forum.xda-developers.com/sho...ENSE-dx5 1.02 (04-01-2014) JB 4.1.2 | Sense 5
Sent from my HTC Desire X using xda app-developers app
Thanks
I tried to install following
http://d-h.st/Jk5
I got installation aborted error..what is the issue?
---------- Post added at 05:02 AM ---------- Previous post was at 04:21 AM ----------
Anybody there to help me...pls give quick replies..
veerusayz said:
Thanks
I tried to install following
http://d-h.st/Jk5
I got installation aborted error..what is the issue?
---------- Post added at 05:02 AM ---------- Previous post was at 04:21 AM ----------
Anybody there to help me...pls give quick replies..
Click to expand...
Click to collapse
What device do you have? Boot into bootloader and write down everything on that screen here
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
What device do you have? Boot into bootloader and write down everything on that screen here
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hi Im using htc desire x...
what do you mean by Boot into bootloader and write down everything on that screen here...sorry for my ignorance..im new to this
Read this thread thoroughly and this will explain you everything..
http://forum.xda-developers.com/sho..., custom roms installing, going back to stock
And there is a thanks button hit it if you want to give thanks
Sent from my HTC Desire X using xda app-developers app
Volume down while powering on, there will be a bunch of information about your phone. Write down all line for line
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for all your help.
I've flashed boot.img from fastboot command. It worked..To be frank, I dont know how it worked..but it worked :laugh:
Hello XDA! this is my first post here. Though i have been reading it for a long time and and i am very helpful to this site for all help it provides.
this is first time i have to post because i couldn't find any solution after two days of searching around.
I have a sony xperia Z2 (D6502) and i was trying to root that thing. i unlocked the bootloader using Sony's official guide. But i can't root it. i consulted a guide at android.gs which told me to just download superSU.zip and boot into recovery, and install zip from there.however i just can't boot into recovery.
All the guides for booting Z2 into recovery say that -
1) Switch off the phone
2) Switch on, when notification led lights up, press volume up or down a few times.
But -
when switching on, notification lights of my phone never light up.it just shows a Sony logo, followed by a Xperia Logo and boot animation.
even the adb boot recovery method does not work. phone just does a complete restart. thats it.
Do i even have a recovery installed on my phone? i got no idea.
Yeah You have to flash recovery first. Maybe it is better to flash DoomKernel, he is explaining how in his post. So it should not be to difficult
Sent from my D6503
---------- Post added at 10:23 PM ---------- Previous post was at 10:18 PM ----------
P.S Don't forget to check your build and use right kernel. It won't boot if you flash wrong one.
Sent from my D6503
well, i have certainly tried that.
i downloaded all of files but when i put in first code in command prompt
"fastboot flash boot boot.img"
all it says is <waiting for device>
and the wait never ends,
Follow these steps and try
Flash the custom recovery again using odin and when the reset button appears in odin window at the same time press the volume up and down both and hold till it get to the recovery menue
Sent from my GT-N7105 using XDA Free mobile app
daxperienced1 said:
well, i have certainly tried that.
i downloaded all of files but when i put in first code in command prompt
"fastboot flash boot boot.img"
all it says is <waiting for device>
and the wait never ends,
Click to expand...
Click to collapse
Haven't you forget to turn on USB Debug? Not kidding you.I've done it before.
Sent from my D6503
@dfire86 That's Samsung territory, doesn't work that way with Sony.
---------- Post added at 01:53 PM ---------- Previous post was at 01:41 PM ----------
CenteaOSD said:
Haven't you forget to turn on USB Debug? Not kidding you.I've done it before.
Sent from my D6503
Click to expand...
Click to collapse
Maybe not booting the phone in fastboot mode?
OP, if you haven't already you should install flashtool, link here that I used last night https://docs.google.com/file/d/0ByK8JL7P6wDTMXRvcTdjMzVuNFk/edit
You'll need the drivers to go with it, here http://forum.xda-developers.com/showthread.php?t=2635830
I went through all this last night. Unlocked bootloader fine. Used fastboot to install DooM's adv stock kernel but the rom I was on was stock 255 and kernel was for 402 so I was getting a black screen. I think the easiest thing for me would have been to fastboot on the 255 kernel but I wasn't thinking straight, used flashmode to put on a stock 402 rom and then used fastboot to put on the 402 kernel, finally got into recovery.
Man, this is much more work than doing a Samsung phone!
It might be the point! OP try what he said!
Sent from my D6503
Well, I have turned on USB debugging. I tried rooting through flashtool too,but failed. just clicked the root button. also, how do i flash the kernel using flash tool.
dang, i remember this being much easier on my nexus.
Sent from my D6502 using XDA Free mobile app
daxperienced1 said:
Well, I have turned on USB debugging. I tried rooting through flashtool too,but failed.
Sent from my D6502 using XDA Free mobile app
Click to expand...
Click to collapse
You can't root through flashtool, you only need it to get the kernel w/recovery on it. Then install supersu from recovery.
daxperienced1 said:
Well, I have turned on USB debugging. I tried rooting through flashtool too,but failed. just clicked the root button. also, how do i flash the kernel using flash tool.
dang, i remember this being much easier on my nexus.
Sent from my D6502 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure that your bootloader is unlocked successfully ? Some career is not allowing you to unlock the bootloader. Can't think about other reason. Maybe try reinstall driver... Or maybe another method is avaliable for D6502
OFcourse. Nexus is easier... As it is made for development.
Sent from my D6503
well, im in india, and here, thankfully, carriers don't bother with locking bootloader and stuff.
And thanks to fatguy666. booting into fastboot mode was genius.
i booted into it and flashed kernel using flashtool.
and then phone went into recovery using normal given methods.
everything is done and dusted now. my xperia z2 is rooted! yay!
i love XDA. and thanks to fatguy:good::good::good::good::good::good:
Gratz! enjoy!
Sent from my D6503 using XDA Free mobile app
Aww thanks!
Seriously, I struggled with this for a couple of hours last night. And here I was thinking Sony loved devs!
daxperienced1 said:
Hello XDA! this is my first post here. Though i have been reading it for a long time and and i am very helpful to this site for all help it provides.
this is first time i have to post because i couldn't find any solution after two days of searching around.
I have a sony xperia Z2 (D6502) and i was trying to root that thing. i unlocked the bootloader using Sony's official guide. But i can't root it. i consulted a guide at android.gs which told me to just download superSU.zip and boot into recovery, and install zip from there.however i just can't boot into recovery.
All the guides for booting Z2 into recovery say that -
1) Switch off the phone
2) Switch on, when notification led lights up, press volume up or down a few times.
But -
when switching on, notification lights of my phone never light up.it just shows a Sony logo, followed by a Xperia Logo and boot animation.
even the adb boot recovery method does not work. phone just does a complete restart. thats it.
Do i even have a recovery installed on my phone? i got no idea.
Click to expand...
Click to collapse
Same here .. am too facing the same situation in India. It is not possible to go into Recovery Mode with any procedure i.e. tried Keys Combination and also through ADB method but didn't succeeded.
Is it mandatory to unlock the Bootloader before entering Recovery Mode? Please help.
Regards!
Arvind Jain said:
Same here .. am too facing the same situation in India. It is not possible to go into Recovery Mode with any procedure i.e. tried Keys Combination and also through ADB method but didn't succeeded.
Is it mandatory to unlock the Bootloader before entering Recovery Mode? Please help.
Regards!
Click to expand...
Click to collapse
my bl is locked and my recovery worked fine until after x amount of restarts and now it will not let me back in.
Hi all, there are a few poeple on here with the same problem. The link is for the dual recovery thread. I assume everybody is on .314 and that is what everybody has? The problem is being looked into. I'm also looking for a solution. I did have it installed before updating to .314 so I'm gonna wait till a solution is found before re-installing. Apart from clean installing .314 and re-installing dual recovery I can't think of a solution off the top of my head. I was posting back and forward with someone last night who had tried re-installing dual recovery, but to no avail. Hence the reason I'm gonna wait. Hope this helps a bit peeps:fingers-crossed:
Yes on 314. I was thinking of.flashing a old fw onto phone before.dual recovery again but this issue has been around for months and I really need to update my rom
All I want is to be in recovery mode on stock fw 314.
When I turn my phone off and start it and waiting for the lightbar to show up for me to press either volume up or volume down several times to get into recovery mode, but my lightbar never light up and the sony loggo comes up and the phone starts normal.
I have also tried to go into recovery mode through my PC with USB debugging and ADB on on my phone and using an script and the phone just starts normal.
I have also tried an app called Quick Boot from Google Play but the phone starts normal.
My Phone:
Bootloader unlocked.
Rooted: Yes
FW: Stock 314. (I dont want any other than stock FW)
ok I fixed mine, recovery did not support partition upon boot hence why it did not load
I'm facing the same problems on .438 with an unlocked BL. Button presses doesn't work and the LED doesn't glow during boot anyway.
EDIT: Stupid question but is recovery lost after a FTF flash? Anyway, I solved my problem by running the XZDualRecovery installer.
Hello everybody! I thought that given the relative complexity of this task and the difficulty that some users have been experiencing with the process, I'd write up a small step-by-step guide on the matter.
Requirements:
VZW HTC 10 with s-off and unlocked bootloader
Computer running adb/fastboot
This guide also assumes that you have the latest TWRP already installed on your device.
Before we begin, I'll go ahead and insert the standard disclaimer. By utilizing this guide, YOU are choosing to modify your phone. By continuing to read this thread, YOU acknowledge that I am not responsible for any adverse effects that may come about as a result of your following this guide.
Okay, now that the unpleasantness is out of the way, let's get started shall we?
Step #1
Download your preferred AOSP Rom & MM Gapps and place on your external SDCARD. This process shouldn't wipe your internal storage but I'd put them here anyway to be safe.
Link to CM13 thread: http://forum.xda-developers.com/htc-10/development/alpha-cyanogenmod-13-0-unofficial-t3465667
Note: A few users have commented in the Validus Thread, saying that it doesn't boot on VZW devices even with unlocked firmware. I'd recommend going with a different AOSP rom to start with.
Step #2
Download latest US Unlocked firmware package. I'd recommend the NoWipe option so you don't lose data on internal storage.
Link to thread: http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Step #3
Modify firmware package content. Extract the package using latest 7zip. Inside there should be a large number of .img files. Delete the following files from the archive:
cradio.img
radio.img
recovery.img
**NOTE -> I am recommending 7zip and notepad++ for windows users because users have reported success with these tools. For what it's worth, I had no issues doing any of this with Xubuntu Linux's built-in file extractor and notepad application.**
Step #4 Change CIDs so that the CID in the firmware matches the one on the phone. There are two ways to do this. Either A). change your phone's CID to superCID or US Unlocked CID, or B). Change the CID in the firmware to match Verizon's CID.
Method A.
Reboot phone into download mode and plug it into your computer.
Open a fastboot prompt on your computer and type: "fastboot oem readcid" without the quotes - this command will tell you your phone's current CID. Write this down and store someplace safe. Assuming you've never changed it, it should be VZW__001.
Then type "fastboot oem writecid 22222222" without the quotes to write supercid, or look up the US Unlocked CID and change to that instead - this information should be available easily on xda, though realistically supercid is likely your best bet because it allows you to flash firmware from any region/variant without ever having to edit it again.
**Make sure you enter the CIDs perfectly. Ex. supercid should be "22222222" without quotes - that's eight 2's.
Method B.
In the firmware zip file you downloaded, you can open android-info.txt and find the CID in there and edit that instead.
Change it to "VZW__001" without the quotes and save.
Step #6
Rezip the firmware package and rename to 2PS6IMG.zip
Open the firmware package zip again to make sure it is structured correctly. All of the .img files and android-info.txt should be located in the root of the archive. If they are inside a folder, fix this or the package won't work.
Put the package on the root of your external SDCARD.
Step #7 Reboot phone to download mode. The update process should automatically proceed. When done, reboot to TWRP and perform a full wipe. Then, install your AOSP Rom and gapps from external SDCARD. Reboot to system & Viola! Running AOSP!
Some issues you may run into:
1. Can't get through setup because it keeps looping through the same screens.
Solution: enable airplane mode from the power menu. This allowed me to skip through the options and get to homescreen. I haven't heard of anyone else besides me having this problem though, so you'll probably be okay.
2. No signal/service/data
Solution: Go under cellular network settings and change access point to VZWINTERNET, cycle preferred network type between CDMA + LTE/EVDO and CDMA/EVDO/GSM/WCDMA once or twice should fix it. Your network mode should be CDMA + LTE/EVDO when you are finished.
3. Carrier label reads 3107
Solution: Deal with it or download an xposed module to change it. Also, I think one or two of the roms have an option to change this baked in.
4. Rom appears to bootloop
Solution: If the boot animation just disappeared, don't worry. It will come back. Be patient.
5. I can't get into recovery after this process to install new rom and old one isn't booting.
Solution: Remove external SDCARD. Boot to Download mode. Then choose reboot bootloader option. From there choose reboot recovery and you should enter recovery.
Happy flashing!
Thank you very much for this write up. I am now starting to feel slightly more comfortable about using my phone outside stock roms.
From here on out then, we should be able to update our firmware with the latest using your method of removing .img's from the package?
Thank you !!!
ufkal said:
Thank you very much for this write up. I am now starting to feel slightly more comfortable about using my phone outside stock roms.
From here on out then, we should be able to update our firmware with the latest using your method of removing .img's from the package?
Thank you !!!
Click to expand...
Click to collapse
Your quite welcome, my friend. To answer your question, yes. Should you perform this process and be running the US unlocked firmware and an update for the US unlocked devices comes out, simply following the process detailed above regarding the firmware modifications will allow you to update to that firmware.
Sent from my HTC 10 using Tapatalk
Furthermore, should you wish to revert to VZW firmware, doing the same process (except without modifying the firmware by removing .img files) will do the trick.
Sent from my HTC 10 using Tapatalk
misterk267 said:
Furthermore, should you wish to revert to VZW firmware, doing the same process (except without modifying the firmware by removing .img files and changing the .txt file) will do the trick.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Btw, you don't need to edit the text file. Those lines only apply if the image file is flashed. If the image isn't present it skips that line. It's like the old -w switch when fastboot flashing an image. Just tells the phone if I flash this partition wipe it first.
Sent from my HTC6545LVW using Tapatalk
dottat said:
Btw, you don't need to edit the text file. Those lines only apply if the image file is flashed. If the image isn't present it skips that line. It's like the old -w switch when fastboot flashing an image. Just tells the phone if I flash this partition wipe it first.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thanks for the info, post(s) updated.
Sent from my HTC 10 using Tapatalk
I get a decryption unsuccessful screen when I boot into CM? How do I fix this, TWRP won't let me factory reset
---------- Post added at 02:45 PM ---------- Previous post was at 02:11 PM ----------
@misterk267 @dottat any ideas..? :/
lancespahr said:
I get a decryption unsuccessful screen when I boot into CM? How do I fix this, TWRP won't let me factory reset
---------- Post added at 02:45 PM ---------- Previous post was at 02:11 PM ----------
@misterk267 @dottat any ideas..? :/
Click to expand...
Click to collapse
Newest version of twrp?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Newest version of twrp?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
yea, whenever I try to reset it says unable to mount preload, storage, data, "data/media/TWRP/.twrps".. I can't make it mount data or preload either.. it says invalid argument
---------- Post added at 03:26 PM ---------- Previous post was at 02:49 PM ----------
should I try to RUU back to stock? Or would that help anything?
lancespahr said:
I get a decryption unsuccessful screen when I boot into CM? How do I fix this, TWRP won't let me factory reset
---------- Post added at 02:45 PM ---------- Previous post was at 02:11 PM ----------
@misterk267 @dottat any ideas..? :/
Click to expand...
Click to collapse
Can you give some more info? What is the situation? Did you just run the conversion or did it just do this out of the blue? Ever have it happen before? It's hard for me to really be able to troubleshoot if I only have a fraction of the info.
Sent from my HTC 10 using Tapatalk
misterk267 said:
Can you give some more info? What is the situation? Did you just run the conversion or did it just do this out of the blue? Ever have it happen before? It's hard for me to really be able to troubleshoot if I only have a fraction of the info.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
OK, so here's what I have done with issues included since last post.
1) flashed verizon htc 10 RUU
2) flashed us unlocked firmware via 2PS6IMG.zip in download mode
3) tried to reboot into system, didn't work (should've assumed)
4) installed twrp
5) tried to full wipe (system, data, cache, etc.. not internal storage)
6) got the unable to mount /system due to invalid argument (not sure what it is) same thing with /preload
7) flashed cm and gapps
8) currently waiting for it to boot... looks promising as it didn't give me data encryption unsuccessful screen and is optimizing apps
did I miss any crucial information? I haven't tried to do this before, first time converting and flashing linked cyanogenmod 13 rom. didn't change CID on phone, only in firmware (also removed radio and recovery imgs because it said to). Thanks so much
EDIT:: nevermind, it seems to be working flawlessly now, must have been a corruption in the system of my phone and just needed reset. thanks for the help anyway!
I tried all of this, to no avail. I thought I had everything working well and CM loaded. Had "Verizon Wireless" for about 30 seconds when I got into the setup menu and I couldn't get past that menu because the verification text couldn't get through. Also, in recovery, I have a consistent "Failed to mount '/preload' (Invalid Argument)" red error line. I reflashed 1.85.x firmware but kept "22222222" SuperCID and Viper10 is working fine. I just don't get why my phone cannot get a CM ROM flashed! The US Unlocked Firmware must have been either 1. bad download 2. incompatible 3. user error 4. throw my phone and see if it works? Does anyone have any ideas?
Edit: Thought I'd add that when I go into "download mode" I see a line for "CRADIO: Error"
I edited the firmware package per the instructions to remove CRADIO.img along with the other two img files
rhodyvik said:
I tried all of this, to no avail. I thought I had everything working well and CM loaded. Had "Verizon Wireless" for about 30 seconds when I got into the setup menu and I couldn't get past that menu because the verification text couldn't get through. Also, in recovery, I have a consistent "Failed to mount '/preload' (Invalid Argument)" red error line. I reflashed 1.85.x firmware but kept "22222222" SuperCID and Viper10 is working fine. I just don't get why my phone cannot get a CM ROM flashed! The US Unlocked Firmware must have been either 1. bad download 2. incompatible 3. user error 4. throw my phone and see if it works? Does anyone have any ideas?
Edit: Thought I'd add that when I go into "download mode" I see a line for "CRADIO: Error"
I edited the firmware package per the instructions to remove CRADIO.img along with the other two img files
Click to expand...
Click to collapse
The /preload error is nothing to be worried about, you can just ignore that. If you can't get through setup, enable airplane mode and skip everything. I'm not sure what you mean by verification message, is that some new way of activating?
Sent from my HTC6545LVW using Tapatalk
If that doesn't work, redownload the Unlocked firmware and try again. You shouldn't be seeing an error for cradio when the firmware is updating, but if you see it under system info while in download mode that shouldn't be an issue because mine says the same thing and works fine.
Sent from my HTC6545LVW using Tapatalk
misterk267 said:
If that doesn't work, redownload the Unlocked firmware and try again. You shouldn't be seeing an error for cradio.
Click to expand...
Click to collapse
Okay thanks. The verification I'm talking about is when I put my Google Email address into CM right when it loads. It can't get past the Google Verification page that the email address belongs to me, do you know what I mean? When you type in your google email address, it "verifies" it as you know. During that time, it can't receive a signal. Should I install without gapps first?
rhodyvik said:
Okay thanks. The verification I'm talking about is when I put my Google Email address into CM right when it loads. It can't get past the Google Verification page that the email address belongs to me, do you know what I mean? When you type in your google email address, it "verifies" it as you know. During that time, it can't receive a signal. Should I install without gapps first?
Click to expand...
Click to collapse
Oh, yes I get what you're saying now. I had the same issue. If you enable airplane mode (you may have to play around a bit with which screen to enable it on) you can skip everything and get to the homescreen. Then launch play store or whatever to get signed in to your account.
Sent from my HTC6545LVW using Tapatalk
misterk267 said:
Oh, yes I get what you're saying now. I had the same issue. If you enable airplane mode (you may have to play around a bit with which screen to enable it on) you can skip everything and get to the homescreen. Then launch play store or whatever to get signed in to your account.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Installing without Google apps package might also work.
Sent from my HTC6545LVW using Tapatalk
misterk267 said:
Oh, yes I get what you're saying now. I had the same issue. If you enable airplane mode (you may have to play around a bit with which screen to enable it on) you can skip everything and get to the homescreen. Then launch play store or whatever to get signed in to your account.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Ohhh...I need to be able to "pull down" from the status bar and enable airplane mode is what you're saying correct? It's one of the screens after booting, correct?
rhodyvik said:
Ohhh...I need to be able to "pull down" from the status bar and enable airplane mode is what you're saying correct? It's one of the screens after booting, correct?
Click to expand...
Click to collapse
No, hold down the power button and the option should be available in the menu that pops up.
Sent from my HTC6545LVW using Tapatalk
misterk267 said:
No, hold down the power button and the option should be available in the menu that pops up.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I tried that but the only two options are "power" and "reboot"
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
p̶h̶o̶n̶e̶ ̶n̶o̶w̶ ̶s̶t̶u̶c̶k̶ ̶i̶n̶ ̶R̶U̶U̶ ̶m̶o̶d̶e̶ ̶w̶i̶t̶h̶
S̶E̶C̶U̶R̶I̶T̶Y̶ ̶F̶A̶I̶L̶!̶ ̶
R̶U̶U̶ ̶ ̶
h̶a̶v̶n̶t̶ ̶b̶e̶e̶n̶ ̶a̶b̶l̶e̶ ̶t̶o̶ ̶r̶e̶s̶t̶a̶r̶t̶ ̶i̶t̶ ̶y̶e̶t̶ ̶h̶a̶v̶e̶ ̶t̶o̶ ̶w̶a̶i̶t̶ ̶u̶n̶t̶i̶l̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶d̶i̶e̶s̶ ̶(̶t̶h̶a̶n̶k̶s̶)̶ ̶d̶o̶n̶t̶ ̶h̶a̶v̶e̶ ̶s̶c̶r̶e̶w̶d̶r̶i̶v̶e̶r̶ ̶t̶o̶ ̶t̶a̶k̶e̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶o̶u̶t̶,̶ ̶o̶t̶h̶e̶r̶s̶ ̶h̶a̶v̶e̶ ̶s̶a̶i̶d̶ ̶r̶e̶s̶t̶a̶r̶t̶i̶n̶g̶ ̶w̶o̶n̶t̶ ̶f̶i̶x̶ ̶i̶t̶
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do this??
update: can get back into TWRP not sure what i can do from here as i dont have an SD card reader to transfer files just a usb and a phone with no OS
Swaaz said:
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
phone now stuck in RUU mode with
SECURITY FAIL!
RUU
havnt been able to restart it yet have to wait until battery dies (thanks) dont have screwdriver to take battery out, others have said restarting wont fix it
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do any of this when my phone is stuck in RUU mode??
Click to expand...
Click to collapse
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
this worked, i must of given up at exactly 7 seconds lol
dumb question but with all these programs ive downloaded tonight ive just about given up
if i factory reset my phone in android recovery mode (not TWRP, the one with the 4 androids) on a phone that doesnt have an OS installed there isnt some miracle chance it would revert to stock rom would it? the only thing on my phone is TWRP and i was using CM12 before everything spiraled out of control
update - phone can access TWRP so im back to square one, i tried RUU i tried adb sideload and i also tried the folliwing programs
sdkmanager
SP flash tool (cant be used with htc)
windroid toolkit
USDDeview
ODIN
i just want to start over and try again but i cant seem to fix this
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
Hope you can figure it out
Sent from my Z988 using Tapatalk
---------- Post added at 06:37 AM ---------- Previous post was at 06:23 AM ----------
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
I don't really know adb very much as I haven't really had much experience with it.
Will probably be picking up a nexus 6 and rooting it since those are 100% stock Android and are easy to root and unbrick etc I will definitely be getting more experience with adb and root
Sent from my Z988 using Tapatalk
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Swaaz said:
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Click to expand...
Click to collapse
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Swaaz said:
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Click to expand...
Click to collapse
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
unfortunately nintendo apps have decided to label anyone with a bootloader unlocked as a filthy hacker and block access to their games
god forbid i upgrade my stock rom
That's why I try to have multiple devices to use
Sent from my Z988 using Tapatalk
bump
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Swaaz said:
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Click to expand...
Click to collapse
I don't think so...
Sent from my Z988 using Tapatalk
back to square one, new magisk update came out today which claims to not brick phones... still bricks mine
i guess thread closed. nobody here and every 2 hours i come into a different problem so ill just keep toying with it
if anyone cares, my current issue is that i cannot flash the current TWRP it always results in a bootloop im currently using an older build and ive been told that i need the newest TWRP for the newest magisk build