Database Info

[Q] flashing ROM

Hi, i want to put this ROM in my phone :
http://forum.xda-developers.com/showthread.php?t=1096043
i unlocked the bootloader with HTC DEV and rooted
hboot - 2.00.0002
radio - 3822.10.08.04_M
can u tell me what i need to do to put this rom on my device
and tell me please what is use of RADIO and hboot ?
thanks !

IgorICS said:
Hi, i want to put this ROM in my phone :
http://forum.xda-developers.com/showthread.php?t=1096043
i unlocked the bootloader with HTC DEV and rooted
hboot - 2.00.0002
radio - 3822.10.08.04_M
can u tell me what i need to do to put this rom on my device
and tell me please what is use of RADIO and hboot ?
thanks !
Click to expand...
Click to collapse
1.First download Rom manager from market
2. Rom manager flashes ClockworkMod Recovery
3. Now download that rom and save to sd card
4. Now reboot into recovery from ROM manager
5. Inside recovery navigate to backup and restore. now make backup of your current ROM(Very important) or you can directly make backup from ROM manager
6) When you finish backing up,
7) format data/factory reset
8) From advanced, format data,system,cache
9) Also format cache partition
10) Finally, goto install from zip from SD card
11) Navigate your download rom and confirm by pressing YES
12) Wail till CWM flashes
13) Reboot and wait.........................done....
And never flash radio or hboot if it is not necessary.

i did all you said, and i was stuceked at htc logo for 20 mins...i pulled out battery
and tryed to go in recovery to restore backup, and now i'm sutcked at htc logo again
i have revoluntionary cwm...
what should I do ?

sagarda7 said:
1.First download Rom manager from market
2. Rom manager flashes ClockworkMod Recovery
3. Now download that rom and save to sd card
4. Now reboot into recovery from ROM manager
5. Inside recovery navigate to backup and restore. now make backup of your current ROM(Very important) or you can directly make backup from ROM manager
6) When you finish backing up,
7) format data/factory reset
8) From advanced, format data,system,cache
9) Also format cache partition
10) Finally, goto install from zip from SD card
11) Navigate your download rom and confirm by pressing YES
12) Wail till CWM flashes
13) Reboot and wait.........................done....
And never flash radio or hboot if it is not necessary.
Click to expand...
Click to collapse
@sagarda : You forgot a very important thing... He unlocked his phone using HTC dev site. That means the boot is still locked. So the kernel is still preserved from the old ROM, which is incompatible with the ROM he's flashed now, and this is never going to allow the phone to boot up with this new ROM.
So he has to flash boot.img separately from fastboot. I know you were only trying to help, but it's best to only give advice that you have actually tried yourself, otherwise you may end up bricking someone's phone trying to help him.
As for @igorICS, you need to extract boot.img from the ROM zip, and flash it separately using fastboot if you want to boot up this new ROM. And please learn to do some reading before taking the plunge, rather than later...

i pulled battery again and i enered recovery somehow, and recived message,
''can't mount ...''
and i just restored my backup
and i dont wanna **** around with this thing...

enigmaamit said:
@sagarda : You forgot a very important thing... He unlocked his phone using HTC dev site. That means the boot is still locked. So the kernel is still preserved from the old ROM, which is incompatible with the ROM he's flashed now, and this is never going to allow the phone to boot up with this new ROM.
So he has to flash boot.img separately from fastboot. I know you were only trying to help, but it's best to only give advice that you have actually tried yourself, otherwise you may end up bricking someone's phone trying to help him.
As for @igorICS, you need to extract boot.img from the ROM zip, and flash it separately using fastboot if you want to boot up this new ROM. And please learn to do some reading before taking the plunge, rather than later...
Click to expand...
Click to collapse
Thanks for your advice.why HTC dev released the method to unlock if that Does not let other to enjoy custom ROM?

sagarda7 said:
Thanks for your advice.why HTC dev released the method to unlock if that Does not let other to enjoy custom ROM?
Click to expand...
Click to collapse
Because they are a corporation. And corporations are known for this kind of stupidity.
Heard of Apple? They are the benchmark for all this nonsense!

I flashed CoreDroid room and after that i extracted boot.img from ROM.zip
and in fastboot entered this
C:\Android>fastboot flash C:\Desktop boot.img
sending 'C:\Users\Igor\Desktop' (2194 KB)... OKAY [ 0.374s]
writing 'C:\Users\Igor\Desktop'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.655s
i get FAILED result i dont know whats the problem but I wont try to boot my phone
im afraid getting stucked on htc logo again..
tell me whats wrong
im still S-on
2.00.0002 hboot
3822.10.08.04 radio
im waiting your reply . tnx

Tried to search the error here : http://forum.xda-developers.com/showthread.php?t=1357625
But, wait for other reply here. That may not be the solution to yours.

thats not a problem my bootloader is unlocked i wait other reply.

IgorICS said:
I flashed CoreDroid room and after that i extracted boot.img from ROM.zip
and in fastboot entered this
C:\Android>fastboot flash C:\Desktop boot.img
sending 'C:\Users\Igor\Desktop' (2194 KB)... OKAY [ 0.374s]
writing 'C:\Users\Igor\Desktop'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.655s
i get FAILED result i dont know whats the problem but I wont try to boot my phone
im afraid getting stucked on htc logo again..
tell me whats wrong
im still S-on
2.00.0002 hboot
3822.10.08.04 radio
im waiting your reply . tnx
Click to expand...
Click to collapse
MarlX said:
Tried to search the error here : http://forum.xda-developers.com/showthread.php?t=1357625
But, wait for other reply here. That may not be the solution to yours.
Click to expand...
Click to collapse
The command should be:
fastboot flash boot C:\Users\Igor\Desktop\boot.img

no way bro, maybe I'm retarded but this thing wont flash...i flashed sucsessfuly boot.img and im stucked on htc logo again...doesn't matter ill press thanks button cause you tried to help me.. this thing wont flash.. i dont know why..

IgorICS said:
I flashed CoreDroid room and after that i extracted boot.img from ROM.zip
and in fastboot entered this
C:\Android>fastboot flash C:\Desktop boot.img
sending 'C:\Users\Igor\Desktop' (2194 KB)... OKAY [ 0.374s]
writing 'C:\Users\Igor\Desktop'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.655s
i get FAILED result i dont know whats the problem but I wont try to boot my phone
im afraid getting stucked on htc logo again..
tell me whats wrong
im still S-on
2.00.0002 hboot
3822.10.08.04 radio
im waiting your reply . tnx
Click to expand...
Click to collapse
Just add a \ between Desktop and boot.img!
I try not to use desktop for cmd purposes...
Just to be 100% sure, follow the steps below:
1. Make a new folder in C:\ called boot
2. Now place the boot.img in the folder you created (C:\boot)
3. Now, using fastboot, type the following at the command prompt (for you, i see that it is C:\Android) ----- fastboot flash boot C:\boot\boot.img
4. Once you get a confirmation of a successful flash, type adb reboot
5. That's it. Enjoy your new ROM !

[Q] stuck in bootloop

I have the att one x, rooted, and twrp flashed onto the device. Me being stupid, i flashed viper x 2.6.0 and it worked great. I went to flash another rom and it was stuck in boot loop. now every rom i try to flash gets stuck in bootloop. Is there a way to fix this or just get it back to stock so i can start over again? Please help, ive tryed to run htcs ruu 2.20 to get back to stock but it wouldnt take. any help would be appreciated. thanks

omarh3 said:
I have the att one x, rooted, and twrp flashed onto the device. Me being stupid, i flashed viper x 2.6.0 and it worked great. I went to flash another rom and it was stuck in boot loop. now every rom i try to flash gets stuck in bootloop. Is there a way to fix this or just get it back to stock so i can start over again? Please help, ive tryed to run htcs ruu 2.20 to get back to stock but it wouldnt take. any help would be appreciated. thanks
Click to expand...
Click to collapse
if you're running hboot 1.14 and 2.20, go into recovery and wipe system, data, cache, etc.
flash the ROM you want, reboot bootloader and flash the boot.img via fastboot
"fastboot flash boot boot.img"
"fastboot reboot"
w/o quotes

I did that same thing, Do you have the international version? if so, then do the above.
If not, you may have overwritten your boot partitions. You'll have to run your device specific RUU. There are a few threads on here with different RUUs and links to outside sources to get the device specific RUU.
I say that you may have over written your boot partitions because ViperX 2.6 is for the international version only. My ROM ViperXL 2.1.2 is the one for us.

you should ruu back to stock then use your unlock token. can't believe you flashed an international after being in here for a little while.

I ran stock ruu and then tried to unlock bootloader, it says it was successful but it still says relocked and now when I tried to do it again with another unlock token it gives me an error message in cmd, same error when flashing recovery. It took me to the prompt on my phone asking if I wanted to unlock and I said I did but still says relocked in bootloader. Also won't let me flash recovery from goo so I can root.
Sent from my HTC One X using XDA Premium HD app

Viper X 2.6.0 and TWRP 2.3.1
I'm a newbie that recently rooted the att one x 2.20 firmware. I currently have boot loop problem that I would most appreciate advice on. I have twrp recovery 2.3.1 flashed. I used the backup function first to backup the rooted stock rom and then attempted to install ViperX 2.6.0. Here are my exact steps and problem in sequence.
1. I placed the ViperX zip file into the main phone directory.
2. I extracted the boot.img file from the Viper zip file and placed it into a desktop directory
3. I loaded fastboot usb and ran the command prompts to flash the boot.image. Getting the following message.
C:\android>fastboot flash boot boot.img
sending 'boot' (4302 KB)...
OKAY [ 0.631s]
writing 'boot'...
OKAY [ 1.134s]
finished. total time: 1.765s
4. Then I erased the cache based on instructions from onexroot.com
C"\android>fastboot erase cache
erasing 'cache'...
OKAY [0.121s]
finished. total time: 0.121s
5. Next I went into TWRP and used the wipe menu to do factory reset, wipe cache, and wipe dalvik cache in that order.
6. Go into Install menu and selected ViperX 2.6.0 zip file. Confirmed flash
7. Followed the installation guide - Full installation, non-custom kernel, full wipe.
8. The flash completed. Hit finished button.
9. The phone now boot loops on the HTC Think Brilliant screen with the legal disclaimer. I got back into the TWRP recovery tool and tried to restore my stock rom using the Restore menu. The script runs successfully, but then continues the bootloop at the Think Brilliant screen.
10. I repeated steps 1 to 8 twice but continue to have the bootloop. Am I missing steps to install Viper X or restoring my stock rom?

jzsqrd said:
I'm a newbie that recently rooted the att one x 2.20 firmware. I currently have boot loop problem that I would most appreciate advice on. I have twrp recovery 2.3.1 flashed. I used the backup function first to backup the rooted stock rom and then attempted to install ViperX 2.6.0. Here are my exact steps and problem in sequence.
1. I placed the ViperX zip file into the main phone directory.
2. I extracted the boot.img file from the Viper zip file and placed it into a desktop directory
3. I loaded fastboot usb and ran the command prompts to flash the boot.image. Getting the following message.
C:\android>fastboot flash boot boot.img
sending 'boot' (4302 KB)...
OKAY [ 0.631s]
writing 'boot'...
OKAY [ 1.134s]
finished. total time: 1.765s
4. Then I erased the cache based on instructions from onexroot.com
C"\android>fastboot erase cache
erasing 'cache'...
OKAY [0.121s]
finished. total time: 0.121s
5. Next I went into TWRP and used the wipe menu to do factory reset, wipe cache, and wipe dalvik cache in that order.
6. Go into Install menu and selected ViperX 2.6.0 zip file. Confirmed flash
7. Followed the installation guide - Full installation, non-custom kernel, full wipe.
8. The flash completed. Hit finished button.
9. The phone now boot loops on the HTC Think Brilliant screen with the legal disclaimer. I got back into the TWRP recovery tool and tried to restore my stock rom using the Restore menu. The script runs successfully, but then continues the bootloop at the Think Brilliant screen.
10. I repeated steps 1 to 8 twice but continue to have the bootloop. Am I missing steps to install Viper X or restoring my stock rom?
Click to expand...
Click to collapse
You are missing something. You are flashing a rom that isn't for your phone. ViperX could of killed your phone, you need to flash ViperXL. Try downloading ViperXL and repeat the steps again.
[ROM][OCT 31] Team Venom ViperXL 2.1.2 - Sense 4.1 | Venom Tweaks | OTA Updates

[Q] AT&T HTC One X Bricked and need advice

Hi,
I have an AT&T HTC One X with no OS. I wiped it when I was trying to flash a custom ROM.
I only have access to bootloader and TWRP. Fastboot is working fine but TWRP is not. It does
mount properly, and adb sideload fails as well. I am using a Windows 7 PC and used a USB 2.0 port.
I installed some HTC Drivers from here:
http://forum.xda-developers.com/showthread.php?t=2217396
but it still says "device drivers failed to install" when I boot into recovery.
When I try to mount, it does not let me mount the sdcard. I see an E: drive on my
PC but it is inaccessible.
I have S-On, my bootloader is unlocked, and I have hboot version 2.14 if that info helps.
Does anybody have any suggestions as to what I can try next?

First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita

I helped him over teamviewer so I can clarify the situation. He can't mount in TWRP, it must of been a typo. It seems he cleared everything when he was trying to wipe to flash a rom. I believe it was ViperXL. He has no backup and sideload does not work as well. Hopefully that will clear things up a little bit more. I installed some newer HTC Drivers since the ones he had were old. The only thing that works seems to be fastboot at this point.
Sent from my HTC One X using Tapatalk

timmaaa said:
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
Click to expand...
Click to collapse
Sorry it was a Typo, I was not able to mount at all. The error said "unable to mount /sdcard"
Yes I have tried performing a factory reset from bootloader but the phone restarts and comes back to TWRP and then same thing.
I tried installing the ViperXL ROM but was not successful.
I was not able to flash the ROM and I tried to fix that but meanwhile looks like I wiped all what I had on my Phone, so no but I did try to flash a new boot.img after and it didnt work.
I dont think I have any TWRP backup on my phone, even though I tried flashing new TWRP but all failed.

Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita

timmaaa said:
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
Click to expand...
Click to collapse
So I followed all the above steps as noted; I had TWRP 2.6.3.0 earlier, I flashed the new TWRP 2.6.0.0 from the link you provided.All
successfully done.
-------------------------------------------------------------------------------------------------------
C:\Fastboot>fastboot devices
HT29WW300913 fastboot
C:\Fastboot>fastboot flash recovery "openrecovery-twrp-2.6
.0.0-evita.img"
sending 'recovery' (8000 KB)... OKAY [ 1.530s]
writing 'recovery'... OKAY [ 1.900s]
finished. total time: 3.430s
C:\Fastboot>fastboot erase cache
erasing 'cache'... OKAY [ 0.120s]
finished. total time: 0.120s
C:\Fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.070s]
finished. total time: 0.070s
---------------------------------------------------------------------------------------------------------
I rebooted into recovery, still came up as TWRP 2.6.3.0, then I went to TWRP reboot and chose Recovery, phone rebooted into TWRP 2.6.0.0
Tried mounting (could not select /sd card and /cache(expected as we erased it)) and ADB sideload, got the same errors as before. Unable to mount /sdcard.
Rebooted again and it displayed TWRP 2.6.3.0

Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita

timmaaa said:
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did

And which recovery is currently installed?
Sent from my Evita

timmaaa said:
And which recovery is currently installed?
Sent from my Evita
Click to expand...
Click to collapse
Its 2.6.3.0, but in recovery when I go into option TWRP reboot and chose Recovery button, phone reboots into TWRP 2.6.0.0 and when I reboot it again, its 2.6.3.0

That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita

timmaaa said:
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
Click to expand...
Click to collapse
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?

tapukakababa said:
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
Click to expand...
Click to collapse
Either one should be fine. If you have S-ON and the phone gets stuck on the HTC screen, you have to flash the boot.img. here's how to do it.
1. On your PC in the ViperXL.zip, take out the boot.img and put it in the directory where you have the adb and fastboot files.
2. Boot into fastboot.
3.Open cmd. Change the directory to the folder where you have those files.
4.type "fastboot flash boot boot.img"
5. Reboot the phone.
The phone should boot.
Sent from my One Xl using Tapatalk

Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita

timmaaa said:
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
So I flashed the boot image, then copied ViperXL and installed it through TWRP, it failed.

Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita

timmaaa said:
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
Click to expand...
Click to collapse
No I did not check the MD5, yes I'm on TWRP 2.6.0.0 and the errors it gives are as follows:
unable to mount '/cache'
unable to open zip
Error flashing zip

Always check the md5. It's possibly corrupt.
Sent from my Evita

timmaaa said:
Always check the md5. It's possibly corrupt.
Sent from my Evita
Click to expand...
Click to collapse
Yup redownloaded the file, checked/compared MD5, copied it back to the phone, removed the previous bad copy, flashed ROM successfully..., as per the message but system reboots to recovery.. is that expected?
And I still see both the TWRP's 2.6.3.0 and 2.6.0.0 the phone needs couple reboots in order to get to TWRP 2.6.0.0 but automatic reboot is in TWRP 2.6.3.0 whats the deal here?

I have no idea why your recovery is acting like that. Hopefully someone else can chime in on that.
Sent from my Evita

[Q] Flashed the LPX13D image and now my recovery is gone.

Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?

Try to flash cwm and tell me what happens

Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.

deleted

Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l

Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.

Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.

Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.

Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?

Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.

Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk

Twrp touchscreen not working.

First time trying to root, in order to install magisk and to get the full functionality of Edge sense +.
I was following this guide:
www-DOT-theandroidsoul-DOT-com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
1. I have successfully unlocked bootloader
2. I have installed twrp
After some research, i think i made a mistake here, by installing twrp-3.1.1-0-ocn instead of the 3.2.1.2-ocn.
When booting to recovery mode, TWRP shows up, it asks for a password or to swipe the screen, but the screen is not responsive.
So i tried to flash the newest version of TWRP on top of the old one and i get this error :
PS C:\Users\ilan\Desktop\unlock-bl> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (39676 KB)...
OKAY [ 1.137s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.145s
PS C:\Users\ilan\Desktop\unlock-bl>
How should i proceed?
I thought about going to stock recovery and then try to flash the new version of TWRP, but i didnt do a recovery. I have found that there is a way to recover to stock using something called RRU.
Help will b amazingly appreciated, tnx in advance

U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.

jelive said:
U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.
Click to expand...
Click to collapse
This is partially true. If anyone expierience touch screen not working in TWRP after following this tutorial: "theandroidsoul.com htc-u11-root-twrp-recovery-and-bootloader-unlock" - problem is, that old version of TWRP is linked there. You HAVE to download version 3.2 not 3.1 ->eu.dl.twrp.me/ocn/twrp-3.2.1-2-ocn.img.html
when touch screen is not working, use "adb reboot" and then "fastboot flash recovery twrp3.2.img"
it works for me