Related
Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?
It's ok, no need to panic
Download ROM to PC. Make doubly sure it's for this device, I think the error you experienced the first time was because you tried to flash an International One X ROM. Only get your ROMs from here, or here.
Boot into recovery.
Connect the phone to the PC.
Mount your sd/internal storage from your TWRP menu.
Copy ROM from PC to phone.
Wipe cache/dalvik/factory reset/system.
Flash ROM.
Reboot.
Enjoy.
Sent from my Evita
Alright, no problem, the error you got in TWRP was because you needed to have HBOOT 2.14 or above to install CM10.1 because of the kernel it uses. Never wipe /sdcard because it won't do you any good. Now, what you're gonna wanna do is, mount USB Storage in TWRP (under mount menu) when it's connected to your PC, download a ROM (not CM10.1 for now, we'll get to that soon enough) and make sure it's for this phone, drag and drop it to your phone from the PC, and flash it. Once you do that, if you still want to get CM10.1, we can help you with that too.
Edit: @timmaaa he won't be able to use CM10.1 because he's on hboot 1.09.
Your main problem, is that you are deleting/formatting things without having any clue what they are. This is an invitation for disaster. Your backups are deleted because your deleted the SD card, not because you deleted /data or /system.
/system = current ROM
/data = user data (phone storage), formatting is the same as factory reset
The only things that really need to be deleted when flashing a new ROM is /data (factory reset) and cache. Formatting /system is not necessary, as flashing a new ROM does this by default before installing the new ROM.
Connect the phone to your computer, mount USB in TWRP, and move the new ROM zip to the SD card, and flash from TWRP.
Its also a good idea to copy a backup to your computer or Dropbox. But that is probably not something that will help you at the moment. Just a bit of advice moving forward.
While in twrp, plug into your pc then go to mounts > mount usb storage. Then put whatever Rom on there. Make sure you get the right Rom for this device.
EDIT:
Oh wow just realized I was beat by like 3 people before I hit post lol
Sent from my HTC One X using xda premium
dragancla said:
Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?
Click to expand...
Click to collapse
First off flash twrp 2.3.3.1 or 2.6 all others have issues.
Then mount usb storage from twrp
Copy Rom to sd card
Wipe cache and dalvik
If you're not s-off depending on hboot version the boot image will need to be flashed via fastboot.
Boot into rom.
Good luck.
Edit: just saw your on 1.09 no need to flash boot image first.
Sent from my HTC One XL using xda premium
Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Sent from my Evita
timmaaa said:
Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Click to expand...
Click to collapse
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).
Lol. All together now.
Sent from my Evita
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
redpoint73 said:
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).
Click to expand...
Click to collapse
Yeah I've heard it's working well, I'm gonna give it a spin hopefully in the next few days. I just thought it'd be best to suggest something we know for sure is solid for right now.
Sent from my Evita
Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S
Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?
dragancla said:
Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S
Click to expand...
Click to collapse
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita
dragancla said:
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked.
Click to expand...
Click to collapse
You didn't do a factory reset from bootloader did you?
RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
Looks like he did. Instructions given above.
Sent from my Evita
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
dragancla said:
Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?
Click to expand...
Click to collapse
You can flash pretty much any Sense ROM, and most aosp ROMs (just not the ones with the 3.4 kernel).
Sent from my Evita
RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
I did :S Thought it would help...
timmaaa said:
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita
Click to expand...
Click to collapse
Thanks, it worked! I can mount sdcard now!
What's the next step?
dragancla said:
I did :S Thought it would help...
Yeah, never do that...
Thanks, it worked! I can mount sdcard now!
What's the next step?
Click to expand...
Click to collapse
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.
The next step after what? What exactly have you achieved so far?
Sent from my Evita
RollTribe said:
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.
Click to expand...
Click to collapse
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?
dragancla said:
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?
Click to expand...
Click to collapse
Yeah, that would work. It's a little outdated, but it should work just fine.
timmaaa said:
The next step after what? What exactly have you achieved so far?
Sent from my Evita
Click to expand...
Click to collapse
Well, I can now access the sdcard/internal storage on my PC when I connect the cable in TWRP Recovery. I just need a ROM.
Hi -
I have an HTC One S (unlocked and rooted - t-mobile) running cm-10.0.0-ville - This is the last stable CyanogenMod ROM.
I would greatly appreciate it if someone could walk me through the steps on how to upgrade this to another ROM (of your choice) that will give me Android 4.3 - There are some features in 4.3 OS that I would love to have (very practical)...
I have heard that I would have to flash boot.img manually using adb if I were to install another ROM. I am worried I will miss a step and soft or hard brick my phone during the process.... I am familiar with Samsungs but HTC from my experience is a hit or miss when it comes to upgrading ROMS or flashing new ones...
Please help so I dont end up with 'unable to mount sdcard' type errors
DroidLuvver said:
Hi -
I have an HTC One S (unlocked and rooted - t-mobile) running cm-10.0.0-ville - This is the last stable CyanogenMod ROM.
I would greatly appreciate it if someone could walk me through the steps on how to upgrade this to another ROM (of your choice) that will give me Android 4.3 - There are some features in 4.3 OS that I would love to have (very practical)...
I have heard that I would have to flash boot.img manually using adb if I were to install another ROM. I am worried I will miss a step and soft or hard brick my phone during the process.... I am familiar with Samsungs but HTC from my experience is a hit or miss when it comes to upgrading ROMS or flashing new ones...
Please help so I dont end up with 'unable to mount sdcard' type errors
Click to expand...
Click to collapse
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
khan.orak said:
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
Click to expand...
Click to collapse
Thanks - complete/informative/precise response. Exactly what I was looking for.
My phone isn't S-OFF (meaning, it is S-ON) so I will follow your directions to update to Android 4.3 - will try the ROMs you suggested. Before I do anything, I will make a backup of existing CM rom though of course.... My concern, and the reason why I posted here, was that last time when I made a backup of existing ROM, then tried to restore from it, I got "unable to mount sd/card' message that I was not able to fix myself (had to pay someone to get that one fixed) .. I dont want to get burned again so needed precise instructions to be able to go back and forth (to a new ROM as u suggested, then go back to my existing one using backup)
DroidLuvver said:
Thanks - complete/informative/precise response. Exactly what I was looking for.
My phone isn't S-OFF (meaning, it is S-ON) so I will follow your directions to update to Android 4.3 - will try the ROMs you suggested. Before I do anything, I will make a backup of existing CM rom though of course.... My concern, and the reason why I posted here, was that last time when I made a backup of existing ROM, then tried to restore from it, I got "unable to mount sd/card' message that I was not able to fix myself (had to pay someone to get that one fixed) .. I dont want to get burned again so needed precise instructions to be able to go back and forth (to a new ROM as u suggested, then go back to my existing one using backup)
Click to expand...
Click to collapse
SD not being able to mount is the result of formatting it using anything other than stock recovery.
If you happen to face that error again, flash a stock recovery, wipe SD from bootloader and it's good to go.
You can then reflash custom recoveries.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
SD not being able to mount is the result of formatting it using anything other than stock recovery.
If you happen to face that error again, flash a stock recovery, wipe SD from bootloader and it's good to go.
You can then reflash custom recoveries.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Ok - so three questions...
1) flash a stock recovery -- pointers on downloading stock recovery for Tmobile/unlocked HTC One S (s4) ?
2) flash a stock recovery - once I have the recovery files, I use adb to push the recovery to the phone or TWRP ? I couldnt use TWRP or clockwork because it didnt even see sd-card...
3) wipe SD from bootloader - do you mean, using adb, issue a command that formats SD card? If so, what is the command?
DroidLuvver said:
Ok - so three questions...
1) flash a stock recovery -- pointers on downloading stock recovery for Tmobile/unlocked HTC One S (s4) ?
2) flash a stock recovery - once I have the recovery files, I use adb to push the recovery to the phone or TWRP ? I couldnt use TWRP or clockwork because it didnt even see sd-card...
3) wipe SD from bootloader - do you mean, using adb, issue a command that formats SD card? If so, what is the command?
Click to expand...
Click to collapse
1. Stock recovery can be found in the forums. It can also be extracted from any Jellybean OTA.zip for any region but intended for S4 device and not an OTA.zip for One S S3. It can be found in Ota.zip\firmware.zip\recovery.img
2. You put the phone in FASTBOOT mode from bootloader and connect to PC, place recovery inside adb folder and issue this command.
Code:
fastboot flash recovery recovery.img
Pretty much similar to boot.img method.
Similarly you can flash custom recoveries
3. When you flash stock recovery, go to bootloader and select CLEAR STORAGE and then FACTORY RESET. That does the job.
Sent from my Nexus 7 using Tapatalk HD
Here is the info on my phone ... (below) - I have an older kernel and in order to upgrade to Android 4.3 (Odyssey or PAC), I will have to upgrade kernel right??
cw v6.0.3.1
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
OpenDSP-v31.1.0.45.0015
eMMC-boot
Apr 20 2012, 15:14:18
Can anyone please confirm this method?
This looks great, but I'm wary that no one has confirmed success.
My phone:
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
TWRP 2.4.1.0
Currently running CyanogenMod:10.1-20130304-Experimental-ville-M2
(On of the last of the 10.1 ROMs before the updated kernel requirement?)
So is this a good (confirmed) method for me? Other ideas? Thanks.
khan.orak said:
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
Click to expand...
Click to collapse
jeremybagai said:
This looks great, but I'm wary that no one has confirmed success.
My phone:
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
TWRP 2.4.1.0
Currently running CyanogenMod:10.1-20130304-Experimental-ville-M2
(On of the last of the 10.1 ROMs before the updated kernel requirement?)
So is this a good (confirmed) method for me? Other ideas? Thanks.
Click to expand...
Click to collapse
Unrelated to what you asked but can you tell me that if you are running "10.1-20130304-Experimental-ville-M2" do you have 4G/3G connection ?
DroidLuvver said:
Unrelated to what you asked but can you tell me that if you are running "10.1-20130304-Experimental-ville-M2" do you have 4G/3G connection ?
Click to expand...
Click to collapse
4g works, no problem. I have some issue with Widget Locker that makes me reboot every day or so, but other than that it's a nice build.
jeremybagai said:
4g works, no problem. I have some issue with Widget Locker that makes me reboot every day or so, but other than that it's a nice build.
Click to expand...
Click to collapse
Can you tell me what radio you have got?
Sent from my HTC One S using xda app-developers app
DroidLuvver said:
Can you tell me what radio you have got?
1.13.50.05.25
So it sounds like I'm helping you get to an Experimental Cyanogen 10.1 rom without updating your firmware. It should work. Enjoy.
But I wish someone would comment more on your original question -- how best to upgrade firmware and explore the newer 10.1 and 10.2 roms?
Can anyone confirm what method they used?
Jeremy
Click to expand...
Click to collapse
jeremybagai said:
DroidLuvver said:
Can you tell me what radio you have got?
1.13.50.05.25
So it sounds like I'm helping you get to an Experimental Cyanogen 10.1 rom without updating your firmware. It should work. Enjoy.
But I wish someone would comment more on your original question -- how best to upgrade firmware and explore the newer 10.1 and 10.2 roms?
Can anyone confirm what method they used?
Jeremy
Click to expand...
Click to collapse
So my radio is 1-13.50.05.31 - I wonder if I should find and flash 11.13.50.05.25 to get my 4G back ? You got 1.13 HBOOT ?
Click to expand...
Click to collapse
Hi All,
I know this might sound like a redundant topic to you all (since there are many discussions about this on here) but after having gone to MANY threads on forums, MANY different websites and trying MANY different things to correct this, to no avail, i'm still stuck!!! :crying:
I am on Evita...running:
S-ON
HBoot-1.14.0002
Radio-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
AT&T Stock RUU 2.20
I've relocked the device, flashed stock RUU (via fastboot), erased the cache, factory reset, wiping from TWRP recovery.....NOTHING is working!
All the phone does is boot to the "HTC quietly brilliant" screen, hang for a few moments then restart.
Any help someone can provide, would be greatly appreciated! This is my kid's phone and he's bugging about wanting to get it back. Thanks!:good:
Start with rooting step first.....http://forum.xda-developers.com/showthread.php?t=1952038
And for further guide.... http://forum.xda-developers.com/showthread.php?t=1671237
Swyped from T3DRO1CS RedHoXence
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
timmaaa said:
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
Click to expand...
Click to collapse
Thanks so much for taking your time to reply, guys.
Sorry, I didn't give full details. Yes, the phone has been rooted, unlocked and running CM10.1 fine for several months. All of a sudden, it got into this weird bootloop. So, I tried doing some of the tricks that people have posted about relocking the bootloader and flashing the stock rom via fastboot. That didn't work so I tried running the RUU...that didn't work. I went back in and tried a factory reset from the bootloader...nothing. I did a erase cache from fastboot and fastboot flashing the boot.img...still doing it. I went into TWRP recovery and wiping Delvik, Cache and Factory Reset....again, still stuck in bootloop.
Sorry to be lengthy but I'm trying to retrace as many steps as possible for you guys.
Ok, just to be clear, you ran the full RUU exe file?
Sent from my Evita
Stupid question.....
I just had a thought. I have the same exact HOX as my son. It's rooted, unlocked and running same CM10.1 rom as his was and it's running fine. Could I try backing up from my phone's clean nandroid file? So, it ends up just acting as a mirror of my phone?
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
timmaaa said:
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I do. I always keep a copy of the rom on my phone for emergencies. Now, the other question is, my phone is running 1.85. The messed up phone is running 2.20 (both S-ON). Will it not work or...coming from a nandroid backup, does that not matter? Never tried doing a mirror before...
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
timmaaa said:
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
Click to expand...
Click to collapse
So, I need to just make sure the phone is back to being rooted, unlocked and running TWRP, then mount it and load the nandroid to the SD card. Should I do backup from fastboot or TWRP?
Do you think it will throw it out of that bootloop? I've spent two days on this and I'm ready to be done!
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
timmaaa said:
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, well..here goes nothing. I will report back the progress! I really appreciate the time for your advice. :good:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
timmaaa said:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
Click to expand...
Click to collapse
Well, I've got the phone loading into TWRP 2.5.0.0 and when I try to do a wipe Delvik, Cache and Factory Reset...it's telling me it can't find the SD Card.
"E: Unable to mount '/sdcard'
E: Unable to mount storage"
Phone says it's still CID: 11111111
Bootloader: Unlocked.
Any clue how to get the phone to read/write to the SD Card so I can back up to a nandroid?
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
timmaaa said:
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
Click to expand...
Click to collapse
I did! Thanks for remembering. :good:
Any special way I should format the sd card when I do it on Windows? Thanks for the tip on 2.6!
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
timmaaa said:
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
Click to expand...
Click to collapse
Got it! Flashed 2.6 in getting ready to back up from my phone's nandroid. Fingers crossed!:fingers-crossed:
After I back up from my nandroid in TWRP, should I flash the boot.img from fastboot?
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
timmaaa said:
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
Click to expand...
Click to collapse
How can I get it to see my nandroid backup? I have it installed inside the TWRP folder just like it would be on my phone but when I go to Restore, it shows nothing on my sd card. wtf?? I think I'm getting one step closer and another hurdle arrises!! ugh...
Thanks for your help btw, timmaaa!! :good:
Sensation info
***UNLOCKED***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
I have 4EXT recovery 1.0.0.6 RC3 Testing build 8
When I try to install Sultan's cm11 dated 20140725 (with full wipe), I get this
set_metadata_recursive: some changes failed.
E:Error in /sdcard/cm11-20140725-Sultan-pyramid.zip. (Status 7)
Installation aborted.
Of course now I have no working rom, only acces to recovery and fastboot usb works ok.
I read through several pyramid threads here describing similar situations, but their error was Status 0.
Any help and advice please?
014916 said:
Sensation info
***UNLOCKED***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
I have 4EXT recovery 1.0.0.6 RC3 Testing build 8
When I try to install Sultan's cm11 dated 20140725 (with full wipe), I get this
set_metadata_recursive: some changes failed.
E:Error in /sdcard/cm11-20140725-Sultan-pyramid.zip. (Status 7)
Installation aborted.
Of course now I have no working rom, only acces to recovery and fastboot usb works ok.
I read through several pyramid threads here describing similar situations, but their error was Status 0.
Any help and advice please?
Click to expand...
Click to collapse
redownload the rom or try a different one
Could you try the latest Slimkat for instance? I am on Slimkat 7.9 and had no issues installing it. Bootloader is the one you have as well.
rzr86 said:
redownload the rom or try a different one
Click to expand...
Click to collapse
I tried to install Albinoman's cm 10.1 20130806 (I had it before on this phone) using different sd card, rom and gapps flashed OK without error messages, but after reboot phone stops at htc start logo, green on white. Recovery and fastboot usb still work though.
I saved recovery log to sdcard, can it help?
wieman01 said:
Could you try the latest Slimkat for instance? I am on Slimkat 7.9 and had no issues installing it. Bootloader is the one you have as well.
Click to expand...
Click to collapse
I'll try that too. Thanks.
014916 said:
I saved recovery log to sdcard, can it help?
Click to expand...
Click to collapse
post it here to see so we can see if there is anything wrong
You have to be a little patient though, the HTC Logo stays in for a little while before you get to see the actual startup screen. So give it a few minutes...
recovery log
rzr86 said:
post it here to see so we can see if there is anything wrong
Click to expand...
Click to collapse
recovery.log attached in zip
OK, this may be a wild guess, but perhaps Albino's ROM is not compatible with 4EXT? The mounting oft system partitions dies not seem to work if I read this correctly.
014916 said:
recovery.log attached in zip
Click to expand...
Click to collapse
wieman01 said:
OK, this may be a wild guess, but perhaps Albino's ROM is not compatible with 4EXT? The mounting oft system partitions dies not seem to work if I read this correctly.
Click to expand...
Click to collapse
from a quick look 4ext can't mount some blocks in your emmc
i think your emmc is corrupted
4ext was your only recovery or did you have other one previously?
rzr86 said:
from a quick look 4ext can't mount some blocks in your emmc
i think your emmc is corrupted
4ext was your only recovery or did you have other one previously?
Click to expand...
Click to collapse
Previous recovery was TWRP 2.6.3? or 2.7.0.0, downloaded from xda, I believe it was shantur's, not sure though. I replaced it because in Sultan's thread about cm11 it was said that only 4ext can install kitkat rom on pyramid. I used it (TWRP) without problems to install Albinoman's cm 10.
By corrupted do you mean bad sectors or errors in partition table? (I don't know much about android partitioning, pardon if I sound like blowing it out).
Is it possible to "repartition" this emmc and assign labels via fastboot usb? Is it like using fdisk or parted? (Sure hope so!)
014916 said:
Previous recovery was TWRP 2.6.3? or 2.7.0.0, downloaded from xda, I believe it was shantur's, not sure though. I replaced it because in Sultan's thread about cm11 it was said that only 4ext can install kitkat rom on pyramid. I used it (TWRP) without problems to install Albinoman's cm 10.
By corrupted do you mean bad sectors or errors in partition table? (I don't know much about android partitioning, pardon if I sound like blowing it out).
Is it possible to "repartition" this emmc and assign labels via fastboot usb? Is it like using fdisk or parted? (Sure hope so!)
Click to expand...
Click to collapse
some sectors i think because 4ext couldn't mount mmcblk0p21, mmcblk0p23, mmcblkp024 if i remember well
did you ever perform any wipe from TWRP?
if yes then probably TWRP caused that
latest versions of TWRP caused a lot of issues to many users
read this thread too
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
rzr86 said:
some sectors i think because 4ext couldn't mount mmcblk0p21, mmcblk0p23, mmcblkp024 if i remember well
did you ever perform any wipe from TWRP?
if yes then probably TWRP caused that
latest versions of TWRP caused a lot of issues to many users
read this thread too
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
Click to expand...
Click to collapse
Yes, I did perform full wipe with TWRP at least twice, before installing Abinoman's cm10 and one of the old Vipers. But they both worked...
014916 said:
Yes, I did perform full wipe with TWRP at least twice, before installing Abinoman's cm10 and one of the old Vipers. But they both worked...
Click to expand...
Click to collapse
ok but unfortunately now you have corrupted emmc
from the thread i gave you check the last post
rzr86 said:
ok but unfortunately now you have corrupted emmc
from the thread i gave you check the last post
Click to expand...
Click to collapse
Reading it right now thanks.
That'll be quite a procedure.
rzr86 said:
ok but unfortunately now you have corrupted emmc
from the thread i gave you check the last post
Click to expand...
Click to collapse
Followed rmann's instructions regarding rom install to sd. Pyramid boots, telephony, wifi and sound work. No problems so far.
It's mmmagic.
Thanks!
Hi, guys
I think I have the same problem (eMMC), but I am not sure...
One mounth ago I install new ROM without any problems, and my phone works perfectly all this time. But today I format all from 4EXT recovery, than I try to install new ROM but my installation process aborted with "Status 0" error.
After that I change recovery several times as well as firmware, I lock and unlock my phone twice (i was a bit panicked), so finally the error persists as well as was.
And when I read this thread my heart was beating faster.
So please can anyone see my .log file? And if it is a eMMC problem, can I do a modified ROM for myself? Oh I am sorry, right question is: how I can patch ROM?
alexezeder said:
Hi, guys
I think I have the same problem (eMMC), but I am not sure...
One mounth ago I install new ROM without any problems, and my phone works perfectly all this time. But today I format all from 4EXT recovery, than I try to install new ROM but my installation process aborted with "Status 0" error.
After that I change recovery several times as well as firmware, I lock and unlock my phone twice (i was a bit panicked), so finally the error persists as well as was.
And when I read this thread my heart was beating faster.
So please can anyone see my .log file? And if it is a eMMC problem, can I do a modified ROM for myself? Oh I am sorry, right question is: how I can patch ROM?
Click to expand...
Click to collapse
no you don't have eMMC problem , you just need to update your 4EXT recovery to lattest one 1.0.0.6 RC3
the latest version of 4ext recovery touch
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
fastboot flash recovery recovery.img
Mile_zdr said:
no you don't have eMMC problem , you just need to update your 4EXT recovery to lattest one 1.0.0.6 RC3
Click to expand...
Click to collapse
rzr86 said:
the latest version of 4ext recovery touch
link_was_here
extract the recovery.img and flash it via fastboot command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you, now my phone work well. But why I can't install my previous ROM, which I install a month earlier with the same recovery?
I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance
radster12795 said:
I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance
Click to expand...
Click to collapse
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490
jollywhitefoot said:
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490
Click to expand...
Click to collapse
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?
radster12795 said:
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?
Click to expand...
Click to collapse
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22
jollywhitefoot said:
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22
Click to expand...
Click to collapse
Finally made it work, went to sdcard installed the zip it said successful then i rebooted it but it is still stuck in the booting screen -_-
and when i opened the bootloading screen it still says no OS
TAMPERED
UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.27.40e.00.11
OpenDSP-v19.2.0268.0927
OS-
eMMC-boot 1024mb
i think my phone doesnt have the firmware cause it said successful but it also said cant moutn /system at the end, any idea?
Thank you very much btw, for helping me, learned so much stuff
followed the other comments to install the sense6 firmware, my phone needs to be S-OF and superCID, finished superCID but i cant run rumrunner cause my phone dont have OS, is there a way to run rumrunner thourgh fastboot or recovery?
Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again
jollywhitefoot said:
Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again
Click to expand...
Click to collapse
oaky, i have installed twrp 2.7.1.1 and now adb pushing the rom and ill try to recovery install the rom again
Finished the zip install
Updating partition details...
E:Unable to mount '/system'
Full SELinux support is present.
Installing 'sdcard/Stock_Sense6M4_Deodexed-Rooted.zip'...
Checking for MD5 file..
Skipping MD5 check: no MD5 file found
->Mounting System & Data
->Extracting System
->Extracting Data
->Creating toolbox symlinks
->Creating additional symlinks
->Installing busybox
->Setting permissions
->Extracting kernel
Updating partition detail...
E: Unable to mount '/system'
It said successful but still no OS installed
sorry the problems just keep coming and coming
First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903
jollywhitefoot said:
First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903
Click to expand...
Click to collapse
Thank you for the past 2 days of helping, i have finally fixed it :highfive:
radster12795 said:
Thank you for the past 2 days of helping, i have finally fixed it :highfive:
Click to expand...
Click to collapse
No problem. Did flashing the ROM in post 8 work?
jollywhitefoot said:
No problem. Did flashing the ROM in post 8 work?
Click to expand...
Click to collapse
YES!! it worked perfectly, Thank you very much
thinking about upgrading to sense 6 now