I was on GPe so today i changed CID to SuperCID and my model is 0P6B13000,installed new firmware by given method in convertion post,installed TWRP and had no problem,but during factory reset i get Failed to mount /system (Invalid argument).Btw,after that i was able to boot in LineageOS,but was unable to boot into S-ROM,which i tried before flashing LineageOS.Also,i was unable to flash Stock Backup.Any ideas what's going on?
Fixed it.you can delete this
No idea if the comversion post is still valid for current firmware as I don't know which one you refered to.
It' a simple process - (after SuperCID done)
1. Install 6.xx firmware
2. Install latest TWRP 3.x
3. Boot to recovery (TWRP) - select wipe, advance, select format data - type yes. Then main menu select reboot - recovery
4. Once in recovery again you can install any ROM that you like.
To revert to Gpe, same process but using Gpe firmware for no. 1 and follow the rest
ckpv5 said:
No idea if the comversion post is still valid for current firmware as I don't know which one you refered to.
It' a simple process - (after SuperCID done)
1. Install 6.xx firmware
2. Install latest TWRP 3.x
3. Boot to recovery (TWRP) - select wipe, advance, select format data - type yes. Then main menu select reboot - recovery
4. Once in recovery again you can install any ROM that you like.
To revert to Gpe, same process but using Gpe firmware for no. 1 and follow the rest
Click to expand...
Click to collapse
Well i used just the Instructions,not the old firmware.I flashed 6.xx firmware(From your collection) . Did it all but can't install S-ROM(only this one).I guess it's just ROM problem.Don't know.Btw i got stock twrp backup from your collection,but twrp doesnt recognize it(i have it on my ExSDCard,yes).Any ideas about that?
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
In other thread you mentioned to convert it to tmob us.. why don't just use RUU ?
ckpv5 said:
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
Click to expand...
Click to collapse
http://imgur.com/a/uNK34
I forgot making backup of only boot and then pasting your stock backup.I'll try it now .btw thats my bootloader
ckpv5 said:
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
In other thread you mentioned to convert it to tmob us.. why don't just use RUU ?
Click to expand...
Click to collapse
Another error occured during restoration. extractTarFor() process ended with ERROR:255
Which version TWRP that you installed ?
Used to get that error due to wrong version.
You can try 2.8.7.0 but don't accept any root offered by twrp.
Also you can try RUU - http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will usually fix all errors unless it's hardware problem
Another thing .. you do not answer my previous question .. did you do no. 3 when doing conversion ?
ckpv5 said:
Which version TWRP that you installed ?
Used to get that error due to wrong version.
You can try 2.8.7.0 but don't accept any root offered by twrp.
Also you can try RUU - http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will usually fix all errors unless it's hardware problem
Click to expand...
Click to collapse
Version is the newest one(3.1.1.0).I'll give a try with other version.
And about the question,yes i did step 3
I'm downloading RUU now.I guess everything will be OK.
RaZaR1998 said:
To use RUU bootloader needs to be relocked,right?
Click to expand...
Click to collapse
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
ckpv5 said:
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
Click to expand...
Click to collapse
Thanks a lot,again
ckpv5 said:
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
Click to expand...
Click to collapse
I've just run RUU and ERROR occured around 50%.Now i'm left without everything ... Any way to get at least the stock recovery and stuff so i can get back to bootloader?
What error that you have ?
To get back to bootloader, press & hold both power & vol up buttons. When it turns black, release both buttons & press and hold vol down button only.
Also you can try to run command fastboot reboot-bootloader
Once on bootloader try to flash firmware again. (Your current bootloader has modified dsp which I believe comes from S.ROM)
I don't remember what was the number of error,but now i get htc logo with four exclamation marks(one in each corner)... when i fastboot reboot bootloader this screen appears.I ran RUU twice,same happend both times...
When you said this
but during factory reset i get Failed to mount /system (Invalid argument)
Did you do factory reset on bootloader while TWRP was installed instead of stock recovery ? AFAIK you're not supposed to factory reset on bootloader with TWRP installed unless it is stock recovery
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
RaZaR1998 said:
I don't remember what was the number of error,but now i get htc logo with four exclamation marks(one in each corner)... when i fastboot reboot bootloader this screen appears.I ran RUU twice,same happend both times...
Click to expand...
Click to collapse
That's RUU mode .. try the buttons press & hold method to get back to bootloader
I did Factory Reset before flashing TWRP.Now as you told me i flashed firmware again.Now my bootloader seems fine.I still dont get why RUU doesn't work.I'm S-OFF with unlocked Bootloader and as you said,re-locking is not needed.I don't get what's going on here ;d
Your first post made me understand that you factory reset after TWRP was installed .. because your problem always related to that.
Maybe try a different RUU, try the Developer Edition RUU.
Before that can you try to restore nandroid backup again using twrp 2.8.7.0 and see the error 255 still there.
Also you mentioned you can install LineageOS ?
How about installing other Sense ROM (other than S.ROM), try that too.
ckpv5 said:
Your first post made me understand that you factory reset after TWRP was installed .. because your problem always related to that.
Maybe try a different RUU, try the Developer Edition RUU.
Before that can you try to restore nandroid backup again usin twrp 2.8.7.0 and see the error 255 still there.
Also you mentioned you can install LineageOS ?
Click to expand...
Click to collapse
Well yes i could install LineageOS and RessurectionRemix (honestly i dont like them).I'll try stock backup with an older TWRP.
Now i got new TWRP but it doesnt show internal storage.is this normal?
RaZaR1998 said:
I'll try stock backup with an older TWRP.
Now i got new TWRP but it doesnt show internal storage.is this normal?
Click to expand...
Click to collapse
That's not normal. This is where you need to format data in twrp then reboot to recovery again. You should see internal storage
Related
Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself
Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.
noodlez04 said:
Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.
Click to expand...
Click to collapse
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...
chaun1308 said:
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...
Click to expand...
Click to collapse
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.
noodlez04 said:
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.
Click to expand...
Click to collapse
Correction . You will have to relock the bootloader again . And since you've rootedd your phone , use Titanium Backup or MyBackup .
This video will guide you to complete stock .
Relocking bootloader is not necessary for OTA updates, but you need stock recovery.
You have to find a stock recovery and then flash it via Fastboot.
Tutorials over here: http://forum.xda-developers.com/showthread.php?t=1832891
Agree with webpatrick
you only need stock recovery to install OTA updates, just find your original rom(or extract from ruu) and flash it in bootloader fastboot flash recovery path_to_recovery_signed.img
not sure if it requires locking the bootloader or not, after that you can reinstall CWM the way you did before and make a backup.
There are 2 options
1:
Flash the non-rooted stock rom with stock boot.img and stock recovery. Bootloader can stay UNLOCKED.
2:
Flash the right RUU, only LOCKING the bootloader is needed. The ruu will flash the stock recovery and boot.img.
Just to be clear
Verstuurd van mijn HTC One X
Need some clearing up here:
1. Can my phone stay rooted? if not - how do I remove SuperSU? tried to remove it from ES by removing the SU file and the app from system/app but that didn't work. - EDIT: Managed to remove root from my device using HTC Quick Root, though it says I need to install secure boot.img to entirely remove root.
2. I tried to flash a recovery file I found in a guide, but the recovery doesn't really work...when I try to access the recovery I got the error screen (the one with the red triangle and exclamation mark), so can someone refer me to a working recovery? attached my software information.
3. Do I need to relock my bootloader or not?
Thanks alot guys, I'm pretty much of a newbie in this whole business
Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it
zainalabididn.syed said:
Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it
Click to expand...
Click to collapse
now I've got a few problems with that:
first of all, my version is 2.18 and there is no RUU for that version for my HTC (which is TWM-TW) yet. and I don't wanna go back to stock ROM, it is the one I have. I just want to set my phone straight so it can get the OTA JB update.
The problem I think I've got now is that my recovery is malfunctioning. I think I don't have the right recovery, since when I try to go into recovery mode I get the red triangle and exclamation mark.
When I tried to install the update, it downloaded it, went into recovery, started doing the process (the green bar was progressing) and then out of the blue - error screen (red triangle and exclamation mark)...
Any ideas?
I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.
jeyml said:
I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.
Click to expand...
Click to collapse
Well, I rooted my phone and installed CWM. so I did the unroot (as far as I know) and got the stock recovery, so what else could it be? :S
No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.
jeyml said:
No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.
Click to expand...
Click to collapse
Thanks for making it all clear I'll check if I've got a backup from when I formatted my phone (does root affect this process?)
And from what I understand, I can only install RUU that is the same as my phone's version or higher. right now I got 2.18, the TWM-TW version of the phone. know by any chance if there is an RUU for it?
The root should not affect the backup/restore proces as far as i know.Yes,the RUU must be the same as phone version or higher.Honestly i don't know any RUU for that,try searching for the new JB RUU.
EDIT:
Check you'r CID and download one of the stock nandroid backups here:
http://forum.xda-developers.com/showthread.php?t=1975140
Thanks for the nandroid, It will be my last resort if restoring a clean image won't help
and about the root - I meant if it's supposed to interfere with the update.
Thanks.
So let me get this straight. You don't have the RUU for your version at all?? and what recovery is installed right now???
No problem,if there are any other problems just ask.
@zainalabididn - I made a recovery image when i first rooted the phone (not when I first got it), but it still won't let me update over it - maybe because of the root. the recovery I'm using right now is CWM 5.8.4
@jeyml - I tried to install the nandroid in the link you gave me, but it wouldn't let me flash the hboot on my device, so after flashing the boot and nandroid it just went into loops of trying to start up, getting stuck and rebooting. got any idea why that happens? (notice: I don't have S-off, if that's what causing the problem)
I tried to update my TWRP because the touch screen in Aroma installers isnt working. The update failed and now I don't have a recovery. What should I do?
Not nearly enough detail for any of us to help.
What is your current version TWRP?
What TWRP version did you try to update to?
How did you try to update it (fastboot, app, etc)?
Any specific error messages on failure?
Current software and firmware versions?
Hboot number?
Do a fastboot getvar all, and post the output being sure to delete IMEI and serial number)
Bootloader unlocked?
If You have root, try https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
I have a sprint htc one m8 rooted, running Marshmallow Google play edition. I tried to flash the 3 most recent updates and it gave me an error saying I might already have it installed or something went wrong. At the moment I don't have a recovery because the app deleted it. So when I try to go into recovery it never starts and I have to restart the phone. I tried flashing them via fastboot and it says it was successful but it didn't actually work.
You try to install recovery by fastboot?
Yea it was successful but when I try to reboot into recovery in never does.
spencer311 said:
I At the moment I don't have a recovery because the app deleted it.
Click to expand...
Click to collapse
What app?
spencer311 said:
when I try to go into recovery it never starts and I have to restart the phone. I tried flashing them via fastboot and it says it was successful but it didn't actually work.
Click to expand...
Click to collapse
Try fastboot erase cache, and fastboot flash TWRP again. This alone clears up a lot of issues with TWRP not flashing properly.
What version TWRP did you try?
Difficult to help, since you failed to provide hardly any of the info I requested.
spencer311 said:
Yea it was successful but when I try to reboot into recovery in never does.
Click to expand...
Click to collapse
Or use RUU, and try again.
Hello there! thanks for your time.
I swear that I tried everything.
I received my HTC 10 like 1 almost 2 weeks ago.
I unlocked the bootloader, flashed the recovery, supersu, everything just fine. Everything works. Except that when I boot into the recovery TWRP ask for the password to decrypt /data. I put my pin = password failed. I tried to resetting the pin, tried putting a password, leaving it blank (tested default_password too) but I cant make TWRP work mounting /data. It always says that password is incorrect.
I even tried factory reset 2 times.
the version is: 3.0.2-2
Any ideas?
Thanks again guys! have a great day!
Anytime its asked me for a password I just press cancel.
My understanding is that the HTC 10 in encrypted by a proprietary HTC code.
Yep - just hit Cancel on that screen.
See the TWRP thread here - http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
"NOTE: TWRP CANNOT decrypt HTC Sense ROMs!!"
And this in the second post
"5. My storage is encrypted, and TWRP can't decrypt it. How am I supposed to flash anything?
First, hit the "Cancel" button at the decryption prompt to continue to the TWRP Main Menu. Storage doesn't need to be decrypted to root the device or flash custom ROMs. If storage is decrypted on this device, mobile network will stop working.
6. Is it possible to retain encryption AND make a data partition backup in TWRP?
No. TWRP cannot currently decrypt /data on this device. That is due to HTC's use of proprietary encryption. Until someone figures out a way around that, the only way to access /data in TWRP is to unencrypt using the "Format Data" option in TWRP and disabling the forceencrypt flag in the ramdisk (which will break mobile network in Android)."
Hey! thanks!
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
well thanks again guys!!
deftoner said:
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
Click to expand...
Click to collapse
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.
btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now
iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
deftoner said:
btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now
Click to expand...
Click to collapse
If you're US unlocked variant, you can follow my guide, here:
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
If you're another variant, reply in the above thread and I can help you find the versions of the files you need to flash.
deftoner said:
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.
Click to expand...
Click to collapse
Reboot download
Make sure your mid matches the US one (I had super cid for mine but apparently if the mid doesn't match it will give error as well)
fastboot getvar all
will tell you
then once it was all set
fastboot flash zip nameof_file.zip
DO IT TWICE!
Then reboot your download to see if the changes took place
You then have to reflash your TWRP recovery because the zip will flash stock recovery
if you are still getting the password box, click cancel for TWRP, wipe > advance and wipe data
good luck
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
Are you asking for help?
jollywhitefoot said:
Are you asking for help?
Click to expand...
Click to collapse
No... I'm just complaining.
Orch4rd said:
No... I'm just complaining.
Click to expand...
Click to collapse
OK cool. Carry on then.
Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
you could...i do it often before flashing new build....
Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.
CryptoJones said:
Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.
Click to expand...
Click to collapse
hay I really need help as in phones setting in security tap is says "encrypt phone - phone is encrypted".
is that a good thing? I want my phone to be "data" unlocked if u know what I mean? help
also I got my phone about 3 weeks and unlocked the bootloader but S-on and I live in Europe.
I try the rom with f2fs support and always when I try to boot the rom with "data" and "cache" formatted as f2fs it doesen´t boot and I try to boot the compatible rom and kernel with ext4 first and when I got a full boot I go to recovery to format cache and data as f2fs but this time when it boots "data" reverts back to ext4 and cache stays as f2fs?
any idea!
I use disk info app and is it because my phone is encrypted data never stays as f2fs or something else as I don´t know much about "decrypt or uncrypt" and the other...
thnx!
TWRP not PIN Pattern
Moved this post to main TWRP
Hello All
I am the textbook Long-Time-Lurker First-Time-Poster. I apologise for some very clueless questions, but I am largely self-taught when it comes to ROM flashing etc on Android.
I have a Taiwan HTC 10 (currently with software version 1.55.709.5). I have flashed TWRP recovery and SuperSU Free 2.72. I have backed up the System and the Sytem Image (two separate backups) on to my external sdCard (I think I should have done that prior to flashing the SuperSU - my bad I guess).
I now want to revert back to stock recovery so I can recieve the new 1.80.709.1 update and so I know how to do this in the future. Because I have the Taiwan version there is no RUU for me to be able to easily flash back to stock, so I think I have to flash both the TWRP Backup and the Stock Recovery for 1.55.709.5 from the Stock Collection page. I assume that I would do it in this order:
1. Flash the TWRP Backup first using the standard method in TWRP and perform the standard TWRP wipes. I assume that I should also let the phone do a full system reboot before going to the next step.
2. Then I would flash the Stock Recovery - but I am not totally sure how to do this. Is there a method to do it using TWRP itself or should I do it from fastboot using the command "fastboot flash recovery 1.55.709.5_rec.img"? Is there something else I will have to do after that (e.g. wiping caches) and, if so, how do I do that?
Am I correct in my thinking?
To explain my cluelessness I have come from using Galaxy devices for the past few years where I just wanted to get away from TouchWiz as fast as possible - so I have never reverted a device back to stock. I also have used ClockworkMod as my recovery (because it was what I learnt with my Nexus One back in the day).
I thank you in advance for your help, and if you need me to post other information about my phone, please remember I may be tardy in replying due to timezones - I am in New Zealand.
Restore your stock system image and boot if you made one before modifying sytem. If not grab the one in the stock thread for your phone. Then boot to download mode and flash stock recovery with fastboot. Reboot to system and take ota
Sent from my HTC 10 using XDA-Developers mobile app
No need to wipe anything.
Just restore System img (already SU? Then Download one from the other Thread here on xda) and you can also restore recovery in TWRP simply Switch to img files instead of zip at the bottom of installing files.
All in one go, Reboot system take OTA and fastboot Flash twrp again.
If you Flash Systemless SU in the future you can still take OTAs
Thank you both for your help. I have been able to restore back to stock pretty much following your suggestions. For others who may be in the situation as I here are the steps I went through:
1. I "system image" backed up my setup - just in case.
2. using TWRP, I flashed the stock image for current software (1.55.709.15) from the [STOCK] Guides and Stock Backups/Recovery/OTA/RUU thread.
3. I had to do the standard three wipes in TWRP to get it back to stock as well - this was the only way that I could get rid of the SuperSU app and I had to go through the first-time-starting setup again. This made me confident that I was back to a pure stock installation.
4. I booted into download mode and used fastboot to flash the stock recovery for 1.55.709.15 (from the same thread as above).
5. Restarted the system and from there downloaded and installed the update - and after 10-15 minutes it successfully rebooted and gave me the message that it had worked.
Thanks again.
hi
are u htc cidnum HTC__621 ?
now can u OTA update ?
because my htc10 rom ver 1.55.709.1 .
now i cant ota update.
htcppadol said:
are u htc cidnum HTC__621 ?
now can u OTA update ?
because my htc10 rom ver 1.55.709.1 .
now i cant ota update.
Click to expand...
Click to collapse
Yes that is my CID, and yes I have updated. Did you change your recovery or system? Because that is what I did, and the process I describe above is how I got it back to stock so I could get the latest OTA update.
Hello,
I've a Taiwanese HTC 10 converted to USA (CID and MID) and flashed with official Nougat RUU. It's working quite good however I wanted to return it to default Taiwanese version and I couldn't.
What I had done:
1) Flashed latest version of TWRP
2) I changed CID and MID to default settings
3) I restored the backup of Taiwanese version downloaded from a thread here using TWRP.
4) I restored original recovery downloaded from a thread here
Following these steps my phone was unable to boot again and a boot loop occurred. To fix the phone I changed CID and MID to USA and thankfully the RUU restored my device to a working state.
I think I'm missing some procedure in TWRP. I only restored a backup using TWRP. It took about a minute or less to complete "successfully".
Do I need to do an extra procedure? Apparently the phone never recognized the Taiwanese version as in download mode the device shown the version of USA ROM even with the backup restored using TWRP.
I'm s-off (Sunshine) with bootloader locked. I think this shouldn't affect as TWRP installed properly and I'm s-off.
Thank you.
markthirteen said:
Thank you both for your help. I have been able to restore back to stock pretty much following your suggestions. For others who may be in the situation as I here are the steps I went through:
1. I "system image" backed up my setup - just in case.
2. using TWRP, I flashed the stock image for current software (1.55.709.15) from the [STOCK] Guides and Stock Backups/Recovery/OTA/RUU thread.
3. I had to do the standard three wipes in TWRP to get it back to stock as well - this was the only way that I could get rid of the SuperSU app and I had to go through the first-time-starting setup again. This made me confident that I was back to a pure stock installation.
4. I booted into download mode and used fastboot to flash the stock recovery for 1.55.709.15 (from the same thread as above).
5. Restarted the system and from there downloaded and installed the update - and after 10-15 minutes it successfully rebooted and gave me the message that it had worked.
Thanks again.
Click to expand...
Click to collapse