Hi
I recently bought a used HTC One M8.
The previous owner already rooted the phone, and had Viper 1.5 installed.
Now, trying to update the Viper, I found out there is a problem with the phone recovery (which currently appears to be stock).
Every time I need to complete an action through recovery, like updating the ROm or just changing the boot logo, it gives me the red triangle almost instantly. The explanation it gives me is:
"Mount SDCard failed 1 times
Mount SDCard failed 2 times
Mount SDCard failed 3 times
Mount SDCard failed 4 times
Mount SDCard failed 5 times
Can not mount SD Card. (No such file or directory)
I:Write host_mod: 0 done"
When trying to "Apply from phone storage", it writes:
"Check cid failed!
--invalid operation--"
(My CID is "HTC_002" by the way).
Anybody got any idea to what is wrong with the recovery?
MXSteel said:
Hi
I recently bought a used HTC One M8.
The previous owner already rooted the phone, and had Viper 1.5 installed.
Now, trying to update the Viper, I found out there is a problem with the phone recovery (which currently appears to be stock).
Every time I need to complete an action through recovery, like updating the ROm or just changing the boot logo, it gives me the red triangle almost instantly. The explanation it gives me is:
"Mount SDCard failed 1 times
Mount SDCard failed 2 times
Mount SDCard failed 3 times
Mount SDCard failed 4 times
Mount SDCard failed 5 times
Can not mount SD Card. (No such file or directory)
I:Write host_mod: 0 done"
When trying to "Apply from phone storage", it writes:
"Check cid failed!
--invalid operation--"
(My CID is "HTC_002" by the way).
Anybody got any idea to what is wrong with the recovery?
Click to expand...
Click to collapse
Try reflashing recovery through hboot
exocetdj said:
Try reflashing recovery through hboot
Click to expand...
Click to collapse
Just finished flashing TWRP through the computer. I'll see if it worked and edit the resault.
Edit:
Now it no longer even enters recovery. Just shows that screen with the red legal warning at the bottom and "Entering recovery" at the top, and.. reboots, and boots straight to the OS.
That's from TWRP 2.7.1 for [m8].
Edit #2:
Nvm, I flashed TWRP 2.7.0.1 by accident.
Now flashed 2.7.1, and it at least entered it the first time. Gonna see if I can install my ROM updates through it
Edit #3:
Seems good. Thanks.
Yes, red triangle is stock recovery. Any idea how you got back to that?
Did you factory reset in bootloader, by any chance?
redpoint73 said:
Yes, red triangle is stock recovery. Any idea how you got back to that?
Did you factory reset in bootloader, by any chance?
Click to expand...
Click to collapse
That's how the last owner left it. Considering it didn't even work, I doubt you'd want to get back to that, not to mention TWRP is way better.
I assume if you factory reset all the phone, it'll probably return you to stock recovery mode as well.
MXSteel said:
That's how the last owner left it. Considering it didn't even work, I doubt you'd want to get back to that, not to mention TWRP is way better.
Click to expand...
Click to collapse
You are misunderstanding. The issue is not that stock recovery is "not working". Stock recovery is working as it should. Stock recovery is not for flashing custom ROMs and mods; it only works to flash specific items, such as official OTAs.
But the fact that the previous owner has a custom ROM installed, but stock recovery is a bit odd. Previous owner must have had custom recovery installed at one point, then installed stock recovery back to the device. Might be a botched attempt to return to stock before selling/trading with you.
MXSteel said:
I assume if you factory reset all the phone, it'll probably return you to stock recovery mode as well.
Click to expand...
Click to collapse
That assumption would be incorrect. "Factory reset" is a bit of a misnomer, all it does is delete the user data (/data) partition and cache. ROM, recovery, and everything else is actually untouched.
Also, the reason I ask is that factory reset in bootloader should never be done on a modded phone. There is a bug which corrupts the internal memory if you do so. If you want/need to ever do a factory reset, then do so either within the OS (in Settings) or in recovery. Reason I ask if this was done, was to try to troubleshoot your error message (mount SD failed), but as the phone apparently was placed in its current state by the previous owner, we don't really have a way of knowing.
What is the status of the phone as given in bootloader? Is the bootloader unlocked, relocked or locked? S-on or S-off?
redpoint73 said:
You are misunderstanding. The issue is not that stock recovery is "not working". Stock recovery is working as it should. Stock recovery is not for flashing custom ROMs and mods; it only works to flash specific items, such as official OTAs.
But the fact that the previous owner has a custom ROM installed, but stock recovery is a bit odd. Previous owner must have had custom recovery installed at one point, then installed stock recovery back to the device. Might be a botched attempt to return to stock before selling/trading with you.
That assumption would be incorrect. "Factory reset" is a bit of a misnomer, all it does is delete the user data (/data) partition and cache. ROM, recovery, and everything else is actually untouched.
Also, the reason I ask is that factory reset in bootloader should never be done on a modded phone. There is a bug which corrupts the internal memory if you do so. If you want/need to ever do a factory reset, then do so either within the OS (in Settings) or in recovery. Reason I ask if this was done, was to try to troubleshoot your error message (mount SD failed), but as the phone apparently was placed in its current state by the previous owner, we don't really have a way of knowing.
What is the status of the phone as given in bootloader? Is the bootloader unlocked, relocked or locked? S-on or S-off?
Click to expand...
Click to collapse
The bootloader was unlocked (and "Tempered"),and it's currently S-On, and I dont have any reason to change that. And of course, I wouldn't do a factory reset from bootloader or anywhere else, certainly not after all the trouble I went through installing TWRP and all the android SDK stuff to flash it.
MXSteel said:
And of course, I wouldn't do a factory reset from bootloader or anywhere else, certainly not after all the trouble I went through installing TWRP and all the android SDK stuff to flash it.
Click to expand...
Click to collapse
Again, you are misunderstanding what factory reset does. It only wipes the /data partition (user data) and doesn't even touch the other partitions including recovery.
redpoint73 said:
Yes, red triangle is stock recovery. Any idea how you got back to that?
Did you factory reset in bootloader, by any chance?
Click to expand...
Click to collapse
if you can still boot up into the phone i would download the newest full rom from viper. which is now 1.7.1. then i would restart into recovery run the viper install and just start from scratch. since you bought the phone used who knows whats still left on there. in the aroma there should be an option to wipe the phone before install. that will ensure a clean install and then you can OTA to the new 1.8.0. for some odd reason he has produced a full 1.8.0 rom but its not that big of a deal.
syaoran68 said:
in the aroma there should be an option to wipe the phone before install. that will ensure a clean install
Click to expand...
Click to collapse
Full wipe options are also available in custom recovery. Data, cache and Dalvik is usually all that is needed to be wiped.
Related
hi, recently i decieded to install CM11 on my samsung galaxy nexus, i downloded it and then i reset facotry my phone, but when i wanted to install it from Bootloader i got an error, then i thohgt it cause of old bootloader so i wanted to update it but THE problem showed up, i cant come into my android it wont be come, please help me out
If all you did was a normal factory reset, it should boot up fine. If you did something like wiped system, then you need to get to a computer and use ADB. If you wiped system then you have nothing to boot to
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
the error is: set_metadata_recursive: some change failed
E:erro in /sdcard/0/0/cm-11-20131130-UNOFFFICAL0maguro.zip
(stat7)
insstalation aborted.
the.farbod said:
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
If you have a backup though, why cant you just restore the backup? Can you not get into the recovery anymore?
kinda curious, OP why didnt you just wipe everything in recovery mode and flash it??
1) adb reboot bootloader
2) fastboot flash recovery ***recovery.img*** (i like to rename the image to "recovery" for the ease of my own useage)
3) press vol rocker to recovery mode and flash away!
I personally use TWRP, but a lot of people prefer CWM, they are both amazingly easy to use.
worst case, you flash the stock 4.3 image from google to get everything back on track.
tl:dr I've been trying to flash the stock firmware using Odin but nothing seems to change after I reboot.
SGH-T889
TWRP v2.6.3.1
Devil Kernel
Jedi X Rom (20)
I had this setup for a few months until this morning when my phone had shut off on its own some time while I was sleeping. Turning on the phone would only load up to the Devil Kernel Splash screen. I can get into TWRP but it asks me for a password that I never set. After some searching, I'm assuming that this is because my data partition has possibly been corrupted.
I've tried doing a factory reset in TWRP, it says it's successful but practically there is no change. The console states that it is unable to mount /efs, /cache, and /system.
I tried using 'Format Data', but choosing this options only seems to reset TWRP because I see the TWRP splash screen and then am asked for a password again. From my understanding, shouldn't formatting the data should remove any encryption?
I tried to just reflash the stock firmware to reset everything but every time I finish flashing in Odin, Odin states that everything is fine but there is no change on my phone. I still only see the kernel splash screen on boot.
I've tried doing an Emergency Firmware Recovery through Kies but Kies is unable to do anything after it detects my device version.
kyang321 said:
tl:dr I've been trying to flash the stock firmware using Odin but nothing seems to change after I reboot.
SGH-T889
TWRP v2.6.3.1
Devil Kernel
Jedi X Rom (20)
I had this setup for a few months until this morning when my phone had shut off on its own some time while I was sleeping. Turning on the phone would only load up to the Devil Kernel Splash screen. I can get into TWRP but it asks me for a password that I never set. After some searching, I'm assuming that this is because my data partition has possibly been corrupted.
I've tried doing a factory reset in TWRP, it says it's successful but practically there is no change. The console states that it is unable to mount /efs, /cache, and /system.
I tried using 'Format Data', but choosing this options only seems to reset TWRP because I see the TWRP splash screen and then am asked for a password again. From my understanding, shouldn't formatting the data should remove any encryption?
I tried to just reflash the stock firmware to reset everything but every time I finish flashing in Odin, Odin states that everything is fine but there is no change on my phone. I still only see the kernel splash screen on boot.
I've tried doing an Emergency Firmware Recovery through Kies but Kies is unable to do anything after it detects my device version.
Click to expand...
Click to collapse
Odin the UVALJ1 ROM (i use the Mr. Robinson rooted version). I have been down that road before. I had to flash 2x before it fixed my devices file system.
Then install the current TWRP recovery as 2.6.3.1 is not the best option. From there you should be able to get started again.
Coug76 said:
Odin the UVALJ1 ROM (i use the Mr. Robinson rooted version). I have been down that road before. I had to flash 2x before it fixed my devices file system.
Then install the current TWRP recovery as 2.6.3.1 is not the best option. From there you should be able to get started again.
Click to expand...
Click to collapse
I tracked down the ROM that you're referring to by mrRobinson but after trying another 4 times I'm still getting the same results.
Can you clarify your second line about TWRP recovery? I tried seeing if TWRP was the problem since I could not format data but I cannot flash any new recoveries (stock, CWM, or older versions of TWRP). Does anyone know of any alternate means other than flashing through Odin?
Thanks for the reply though, hearing that other people have had similar problems gives me some hope.
kyang321 said:
I tracked down the ROM that you're referring to by mrRobinson but after trying another 4 times I'm still getting the same results.
Can you clarify your second line about TWRP recovery? I tried seeing if TWRP was the problem since I could not format data but I cannot flash any new recoveries (stock, CWM, or older versions of TWRP). Does anyone know of any alternate means other than flashing through Odin?
Thanks for the reply though, hearing that other people have had similar problems gives me some hope.
Click to expand...
Click to collapse
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Coug76 said:
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Click to expand...
Click to collapse
Thanks again for the response! Flashing recoveries in Odin isn't giving me any results so I'll try getting an external sd card and flashing version 2.7.2.0 from within TWRP.
kyang321 said:
Thanks again for the response! Flashing recoveries in Odin isn't giving me any results so I'll try getting an external sd card and flashing version 2.7.2.0 from within TWRP.
Click to expand...
Click to collapse
Coug76 said:
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Click to expand...
Click to collapse
So I can't seem to change my recovery. Odin will supposedly pass but the version stays the same in my phone. Within TWRP I cannot mount my external sd card so I can't flash from there either.
I tried to see if I could do something with ADB but TWRP won't let me go into ADB side load because it cannot mount /cache.
Any ideas?
Download the ODIN flashable version of TWRP and flash from within ODIN. That will get you at least a new recovery. From there you can restore/etc. I had a similar issue a few weeks back. My partitions got corrupted and doing the standard full ODIN, regardless of which ODINversion/firmware combo I used, resulted in me having a stock recovery with literally nothing else. System, cache, data....nothing would mount. I thought I was permanently soft bricked. Each ODIN flash seemed to go well, but upon booting up, the phone would immediately go into stock recovery with those mounting errors. I used the ATT version of twrp 2.7.2.2...or whatever the latest version was because it had the partition repair option that the TMO version hasn't been updated to yet.
Install the recovery from ODIN.
Boot into recovery.
Click the wipe tab. Then do the advanced wipe...select one partition at a time then click on the 'repair partition' option. I think only cache, system and data can be repaired. The others won't let you repair. Will give an error saying failed or not repairable or something like that.
That's what helped me get out of my dilemma. Fortunately, I had a stock backup on an SD card I was able to restore at that point. If you don't, flash a new ROM, log in, then download Mobile ODIN from the market. You can then flash full firmwares from within the phone itself and get back to 100% stock, minus boot loader. But if you're already on the 4.3 bootloader then there won't be any problems.
I'll check back to see if you had any success. It worked for me, but I offer no guarantees.
Good luck.
carlz28 said:
Download the ODIN flashable version of TWRP and flash from within ODIN. That will get you at least a new recovery. From there you can restore/etc. I had a similar issue a few weeks back. My partitions got corrupted and doing the standard full ODIN, regardless of which ODINversion/firmware combo I used, resulted in me having a stock recovery with literally nothing else. System, cache, data....nothing would mount. I thought I was permanently soft bricked. Each ODIN flash seemed to go well, but upon booting up, the phone would immediately go into stock recovery with those mounting errors. I used the ATT version of twrp 2.7.2.2...or whatever the latest version was because it had the partition repair option that the TMO version hasn't been updated to yet.
Install the recovery from ODIN.
Boot into recovery.
Click the wipe tab. Then do the advanced wipe...select one partition at a time then click on the 'repair partition' option. I think only cache, system and data can be repaired. The others won't let you repair. Will give an error saying failed or not repairable or something like that.
That's what helped me get out of my dilemma. Fortunately, I had a stock backup on an SD card I was able to restore at that point. If you don't, flash a new ROM, log in, then download Mobile ODIN from the market. You can then flash full firmwares from within the phone itself and get back to 100% stock, minus boot loader. But if you're already on the 4.3 bootloader then there won't be any problems.
I'll check back to see if you had any success. It worked for me, but I offer no guarantees.
Good luck.
Click to expand...
Click to collapse
I already have TWRP 2.6.3.1. In trying to see if that version is a problem, I've tried flashing a different version through Odin but it doesn't have any effect (the version will always stay as 2.6.3.1 regardless of what I flash through Odin).
So it's been a week since my issue started and I haven't gotten any further since I started.
I've tried flashing a new pit file to no avail (stuck on get pit file mapping). I've also tried doing a nand rewrite but I get a nondescript error.
As of this point I've given up and am just going to use an old phone lying around until my contract is up. If you've found this thread because you've had similar issues I wish you better luck than I had.
I wanted to flash a RUU, re-root and flash a ROM, but apparently my device didn't like that.
OK, so here's exactly what I did, in this order. (with an unlocked bootloader)
Flashed stock recovery
Booted into stock recovery and wiped data and cache
Locked Bootloader (Becasue If I lock bootloader first I can't get into recovery)
Let hboot flash the RUU file on the SD card without being plugged into PC
Tried to reboot to system and recovery, it brings me back to hboot
After all that^^ I unlock the bootloader, and when trying to boot to system it gets past the HTC screen, then stuck at the CM logo (the ROM I was using before any issue happened) which is why I'm assuming the RUU didn't even flash at all.
Also, if I try to flash CWM, if I wipe data I'm getting
Formatting /data...
Error mounting /data!
Skipping format...
Same with /.android_secure.
Any help would be extremely appreciated, because right now I feel like I'm working with a pretty hard brick.
FoxyDrew said:
I wanted to flash a RUU, re-root and flash a ROM, but apparently my device didn't like that.
OK, so here's exactly what I did, in this order. (with an unlocked bootloader)
Flashed stock recovery
Booted into stock recovery and wiped data and cache
Locked Bootloader (Becasue If I lock bootloader first I can't get into recovery)
Let hboot flash the RUU file on the SD card without being plugged into PC
Tried to reboot to system and recovery, it brings me back to hboot
After all that^^ I unlock the bootloader, and when trying to boot to system it gets past the HTC screen, then stuck at the CM logo (the ROM I was using before any issue happened) which is why I'm assuming the RUU didn't even flash at all.
Also, if I try to flash CWM, if I wipe data I'm getting
Formatting /data...
Error mounting /data!
Skipping format...
Same with /.android_secure.
Any help would be extremely appreciated, because right now I feel like I'm working with a pretty hard brick.
Click to expand...
Click to collapse
Hold on, you said you were able to select factory restore inside of the stock recovery and it went through smoothly correct?
So have the bootloader unlocked
Flash stock recovery
factory restore to wipe that side of the partition
Go into the bootloader again flash CWM or TWRP or Philz Recovery.
Wipe/Factory restore now.
If this works this should fix the error on /data.
Then flash CM again.
It is because the RUU just writes the partition to stock. It doesn't clear anything extra that's there. CM has its own partition called "0" on the /sdcard aka the "root" folder.
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Hold on, you said you were able to select factory restore inside of the stock recovery and it went through smoothly correct?
So have the bootloader unlocked
Flash stock recovery
factory restore to wipe that side of the partition
Go into the bootloader again flash CWM or TWRP or Philz Recovery.
Wipe/Factory restore now.
If this works this should fix the error on /data.
Then flash CM again.
It is because the RUU just writes the partition to stock. It doesn't clear anything extra that's there. CM has its own partition called "0" on the /sdcard aka the "root" folder.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I literally love you. All that, not being able to use my phone for days, and it takes 3 seconds to fix. I almost **** my pants thinking I had to buy a new one. THANK YOU!
FoxyDrew said:
I literally love you. All that, not being able to use my phone for days, and it takes 3 seconds to fix. I almost **** my pants thinking I had to buy a new one. THANK YOU!
Click to expand...
Click to collapse
Love for everybody :thumbup::thumbup:
Sent from my 710C using XDA Free mobile app
So I attempted to root my HTC Desire 816 dual sim. I managed to get it to work following instructions I found from this site. I then went on to try and install Cyanongenmod onto my device, I can't remember where the site was that I was following but I had to, within CMW recovery, wipe data/factory reset, wipe dalvik cashe, format system and format partition.
I did all this then tried to flash this ROM but it said it was the wrong ROM for my device and it said my device was htc_a5dug. which I've had no luck finding anywhere.
Now the phone will only boot into CMW recovery, I can install superSU but any other ROMs I've tried it has aborted automatically, if i restart the system from CMW, it comes up saying there is no root access, root missing /system/xbin/su ( see one of the attached pictures)
I've managed to get it restarted to the bootloader page twice (happens randomly when I select restart to bootloader from CMW) (pictures of bootloader in attatchments showing no OS)
I have a feeling I've totally stuffed my phone when i formatted the system and partition
If anyone has any idea how I can get this fixed I would be so greatful.
PS I'm feeling quite noobish right now
Download cwm backup for your device and restore it in cwm if you don't have your own backup
drummer1839 said:
Download cwm backup for your device and restore it in cwm if you don't have your own backup
Click to expand...
Click to collapse
where do I get a cwm backup from?
[edit] OK I flashed a recovery stock.img file, then I got a red triangle, the phone rebooted and now its stuck on the htc android startup screen and I can't turn the phone off. so Ill have to wait till the battery runs flat.
In the mean time more suggestions and guidance would be super.
drummer1839 said:
Download cwm backup for your device and restore it in cwm if you don't have your own backup
Click to expand...
Click to collapse
Found a backup and my phone is now working again, Thank you very much for helping.
Remember there is a golden rule always make a backup when you want to flash something new
Has anyone seen the OP3 automatically revert back to stock recovery no matter how many times TWRP is successfully installed via fastboot?
At first I thought it was the "Advanced reboot" enabled causing it since when "recovery" is selected from within the OS power button menu, a "factory data reset" message appears prior to reboot....BUT I tried cycling the phone with "Advanced reboot" disabled and a clean install of TWRP working - and it still didn't stick. Regardless, whenever I enter the OS and then either turn the phone OFF or manually reboot it, the stock recovery gets automatically rewritten.
Could that annoying "device unlocked" pre-boot warning message be the cause? Do I need to relock the bootloader and/or disable "OEM unlocking"?
To confirm, I currently have the OP3 bootloader unlocked and NOT rooted (need Android Pay). The same issue occurs with the OP3 running OOS 3.1.2, 3.1.3, and 3.2.0.
I never had this issue with my OnePlus 1 so I am a little bewildered why this keeps happening.
Scott-
Which developers TWRP are you using? I had that happen, I forget which one I was on. Grarak 's TWRP works great and doesn't revert back to stock recovery.
marcjames513 said:
Which developers TWRP are you using? I had that happen, I forget which one I was on. Grarak 's TWRP works great and doesn't revert back to stock recovery.
Click to expand...
Click to collapse
Yes, TWRP by Grarak. I have not tried the "official" TWRP yet.
To confirm, all you do is:
1. Enable USB debugging, OEM unlock, and Advanced reboot...
2. Reboot in to the bootloader and decrypt user data via "fastboot format user data" (not required{??})
3. Allow the phone to wipe and re-establish itself...
4. Set the phone up again....enabling USB debugging, OEM unlock, and Advanced reboot...
5 Reboot in to the bootloader and unlock the bootloader via fastboot oem unlock...
6. Allow the phone to wipe and re-establish itself...
7. Set the phone up again....enabling USB debugging, OEM unlock, and Advanced reboot....
8. Go back in to the bootloader and Install TWRP via "fastboot flash recovery <TWRP.img>...
That is it, yes?
It seems relocking the bootloader doesn't do anything for me. Also, even though I decrypted the user data partition, it still shows the "encrypt phone" being "encrypted" within the Security & fingerprint menu. Maybe something related is blocking the recovery image from sticking past a reboot.
Thanks,
Scott-
I also had this problem with one of the other unofficial TWRPs. Grarak's TWRP worked in the end.
You need to allow TWRP to modify the system partition. If you said to leave it read-only on first boot, it will revert to stock recovery.
The problem is if you flash TWRP now, it wont give you that option again. To find it, reflash, boot into TWRP, go to Mount and change it towards the bottom where it says Mount system partition read-only.
karthikrr said:
You need to allow TWRP to modify the system partition. If you said to leave it read-only on first boot, it will revert to stock recovery.
The problem is if you flash TWRP now, it wont give you that option again. To find it, reflash, boot into TWRP, go to Mount and change it towards the bottom where it says Mount system partition read-only.
Click to expand...
Click to collapse
Still doesn't help. Keeps reverting to stock. I'm on OB35 TWRP 3.2.1. Need to flash a rom. I dont need root. Any ideas guys?
Rony John said:
Still doesn't help. Keeps reverting to stock. I'm on OB35 TWRP 3.2.1. Need to flash a rom. I dont need root. Any ideas guys?
Click to expand...
Click to collapse
Needing root and having root are two different things. Flashing Magisk immediately after flashing TWRP will solve the issue. If you don't want root at all, I don't know of any other method to solve this.
tnsmani said:
Needing root and having root are two different things. Flashing Magisk immediately after flashing TWRP will solve the issue. If you don't want root at all, I don't know of any other method to solve this.
Click to expand...
Click to collapse
Already flashed the rom and the problem is solved. Now im in search for a good rom for battery and relatively good camera. Any suggestions. RR seems to be draining so quickly. I ll just wait till 3-4 charge cycle.