Related
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
http://www.filefactory.com/file/c0f....00_11.16.3504.20_2_release_227956_signed.zip
Click to expand...
Click to collapse
Download the CWM recovery image:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-doubleshot.img
Click to expand...
Click to collapse
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Here's a pointer to restoring your phone to stock, courtesy of blue:
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!
xzuhto said:
So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!
Click to expand...
Click to collapse
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.
Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
the doubleshot img downloads painfully slow, do you have another link?
edit: also i think you missed somthing here"
[*]Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
"
ac3theone said:
the doubleshot img downloads painfully slow, do you have another link?
...
Click to expand...
Click to collapse
Well, where football is hosting the new PG59IMG.zip file is the only place we have it - i just found it yesterday and we haven't had time to up it anywhere else yet.
We are working on making mirrors for it now - give us some time to get set up with our new data.
---------- Post added at 01:38 AM ---------- Previous post was at 01:33 AM ----------
jonnycat26 said:
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.
Click to expand...
Click to collapse
No, you can't go back to retail factory if you are S-ON. This new PG59IMG.zip I found is the furthest back you can go completely.
With S-ON you cannot replace hboot, or radio - those two are a big deal - i'm still working on an S-OFF solution for S-ON people with hboot 1.45.0013.
With S-OFF I can swap out hboots on a whim, and thrice43 even flashed a Sensation hboot to his doubleshot and it worked out for him - but with S-ON you cannot do this. (and if you could, you would brick)
S-OFF is very much preferable to S-ON UNLOCKED.
I've also had problems flashing OTA updates through stock recovery manually when S-ON where I had no trouble doing so while S-OFF.
There are still a lot of things you can't do with your device while S-ON.
EDIT:
also, all the PG59IMG.zip files I made for people to flash recoveries, hboots, and so on in the dev reference sticky cannot be used by anyone S-ON because they fail the signature checks. My custom PG59IMG.zip files don't have an HTC signature which you must have for an S-ON device to load the PG59IMG.zip file.
...so there are a number of reasons why S-OFF is something to get.
xzuhto said:
Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.
Click to expand...
Click to collapse
You must flash a kernel if you want to flash an ICS ROM or any GB ROM with a modified kernel.
Also:
Here's a faster mirror, hopefully: http://www.4shared.com/zip/vVHQuid0/PG59IMG_Doubleshot_TMOUS_15553.html
I see the downsides to s-on but I'm happy to have root and cwm. I will however be excited to get this thing fully unlocked. I won't be messing with custom roms till then. lol
Sent from my myTouch_4G_Slide using Tapatalk
I managed to host it on my Dropbox
Edit:
Oh sorry Lime, I didn't see that you were already hosting it...
this might deserve a sticky?
If anyone is going to mirror it please keep the original filename - we have more then one PG59IMG.zip file with an HTC signature (retail launch and this one).
If they are not named including the software version and radio then people may be confused on what they are getting - thanks guys!
it worked, now to get su. thanks for the guide
delete post
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet
Scondrel said:
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet
Click to expand...
Click to collapse
You need to transfer the recovery image to the directory with your fastboot.exe file.
You would then need to rename it to recovery.img
Then you boot your phone into fastboot mode, and plug it into the computer.
Open a command prompt, and navigate to the directory with fastboot.exe and run the command:
fastboot flash recovery recovery.img
Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Scondrel said:
Thanks got it now.Appreciate the help
Click to expand...
Click to collapse
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?
Scondrel said:
Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?
Click to expand...
Click to collapse
You are using the trackpad to "select" within CWM, not the power button, right?
jonnycat26 said:
You are using the trackpad to "select" within CWM, not the power button, right?
Click to expand...
Click to collapse
Thanks it was 'nt that. There wasn't enough space on the memory card and I didn't have USB debugging on.Got it solved now .Thanks for the speedy responses.Truly appreciated .Feels so good to be a part of this community.
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
These instructions worked perfectly! Can not believe it worked. This should be stickied! Thank you.
tbalden said:
this might deserve a sticky?
Click to expand...
Click to collapse
revo420 said:
This should be stickied!
Click to expand...
Click to collapse
Eh, why not. Done .
Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!
TheEmpyre said:
Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!
Click to expand...
Click to collapse
I second this request. I feel like there are loads of helpful threads but after searching for a long time I don't see anything that leads someone new to Android rooting from stock 2.2 to having something like CM10 on their device. All of the write-ups I've found assume more experience than I have. Is there a general guide somewhere that I'm missing? Maybe something that explains rooting, backing up, flashing, etc. from start to finish where we can replace "this is where you root your device" with the new rooting method? I'm assuming it's out there but I can't seem to find it anywhere.
TheEmpyre said:
I have searched the above linked thread and cannot determine how to generate a custom recovery partition
Click to expand...
Click to collapse
You don't need to "generate" anything, not sure where you got that terminology from. Just install Goomanager from the Play Store and use that to install TWRP recovery.
---------- Post added at 09:20 AM ---------- Previous post was at 09:12 AM ----------
TheEmpyre said:
Furthermore, I do not know what "Superuser and su" is referencing.
Click to expand...
Click to collapse
In plain terms a superuser = a root user. But when discussed here, it usually references the app that manages what other apps have root access.
Superuser is required to perform root functions.
You can obtain the app various ways, all discussed here: http://forum.xda-developers.com/showthread.php?t=1954361
TheEmpyre said:
Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!
Click to expand...
Click to collapse
ctennenh said:
I second this request. I feel like there are loads of helpful threads but after searching for a long time I don't see anything that leads someone new to Android rooting from stock 2.2 to having something like CM10 on their device. All of the write-ups I've found assume more experience than I have. Is there a general guide somewhere that I'm missing? Maybe something that explains rooting, backing up, flashing, etc. from start to finish where we can replace "this is where you root your device" with the new rooting method? I'm assuming it's out there but I can't seem to find it anywhere.
Click to expand...
Click to collapse
They are many simple tutorials for rooting but do not know why you guys having hard time. Ok here is
1) You got Android SDK from google + Platform-tools + Google USB Driver -
2) Only for windows - Download htc sync ( It will install necessary htc drivers) - Link
3) Just to check if htc drivers installed properly , open "C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists).
4) In command window type " adb devices" and see output - If you get output then htc drivers installed properly.
You can skip step 3 and step 4 - These steps are only for verification
5) Goto [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit and follow the instructions there.
6) Once you successfully root your device using above exploit then goto - [How To] Flash Custom recovery and ROMS after 2.20 root complete the steps to flash custom recovery and if you want to flash ROMS
7) To unlock BOOT LOADER use this link - [INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up , follow the instructions under " BOOTLOADER UNLOCK, SUPER CID, AND S-OFF"
You can also goto this link - [ROOT][2.20] One XL Bootloader unlock & Root guide By XsMagical - Very nice tutorial, if you find above links difficult to follow
Note* : During exploit or flashing recovery they talk about using fastboot commands, In order to execute them you need goto C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists) and then execute the commands ..
Advice - Do not flash any roms apart from xda
Thank you, abhipati. I haven't seen any simple tutorials that are complete. Everything seems to assume the user knows how to do something mentioned in another thread, which in turn seems to assume something else. Your post seems like a very clear start-to-finish explanation. Maybe it should be made into a stickie in Q&A. I can surely handle step 1 but maybe that could be explained (or at least a link added to an appropriate thread).
If all this is out there somewhere already then I certainly didn't know where to find it. I appreciate your help.
ctennenh said:
Thank you, abhipati. I haven't seen any simple tutorials that are complete. Everything seems to assume the user knows how to do something mentioned in another thread, which in turn seems to assume something else. Your post seems like a very clear start-to-finish explanation. Maybe it should be made into a stickie in Q&A. I can surely handle step 1 but maybe that could be explained (or at least a link added to an appropriate thread).
If all this is out there somewhere already then I certainly didn't know where to find it. I appreciate your help.
Click to expand...
Click to collapse
No problem.
Regarding step 1)
1) Download Android SDK from here {For Windows}
2) Download java you need it - here
Thank you all for helping gather some resources for me that I know are up to date etc. - Thankfully I do know a few unix commands so that I can navigate the command prompt aspects...I'm sure these threads get annoying so thank you very much for getting a new-to-root user up and running. I'll try this all later this evening and throw an update to let you all know how it goes -- hopefully no "bricked my phone" thread in the future
Excellent I have successfully unlocked my bootloader and achieved perm-root! Now on to flashing roms and I have some questions:
1) I have read GuyIncognito's instructions here (http://forum.xda-developers.com/showthread.php?t=1952076) on Flashing ROMs and how to go about doing that and i fully understand the process but I want to confirm (Yes I Have TWRP recovery installed and running) I only need to extract the boot.img out of the winRAR file of the ROM that I downloaded? (CM10 seems to be popular so I'm starting with that as my first ROM) There are so many other files in the package and I'm wondering why do you only need the boot.img file to be present with your adb and fastboot files from the google dev SDK -- the boot.img is only 5 MB and I can hardly believe that it constitutes the whole OS?
2) How do I go about installing gapps after I have flashed my ROM? I have downloaded Gapps so I have the file...do I place it in my SD Card and then enter recovery to install it? or Do have to use adb to flash it
Edit: I also have Superuser app on my stock ROM right now
Any further help is much appreciated, thank you very much.
Boot.img is technically just the kernel, it's the heart of the OS you are installing. Once extracted, rezip rom. Flash boot.img first using fastboot command prompt. Then flash the Rom itself that you rezipped through twrp
You can easily just flash gapps through twrp.
Sent from my HTC One XL using xda premium
InflatedTitan said:
Boot.img is technically just the kernel, it's the heart of the OS you are installing. Once extracted, rezip rom. Flash boot.img first using fastboot command prompt. Then flash the Rom itself that you rezipped through twrp
You can easily just flash gapps through twrp.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the reply, the community on XDA kicks a$$, doing some additional reading just plz tell me if I understand this correctly...
1) Copy CM10 zip and Gapps zip into phone storage
2) Follow GuyIncognito's instructions on flashing boot.img
3) Boot into recovery AFTER Flashing boot.img
4) Select "Install" in TWRP
5) Install CM10 zip First
6) Install Gapps zip next
7) Reboot
8) profit?
TheEmpyre said:
Excellent I have successfully unlocked my bootloader and achieved perm-root! Now on to flashing roms and I have some questions:
1) I have read GuyIncognito's instructions here (http://forum.xda-developers.com/showthread.php?t=1952076) on Flashing ROMs and how to go about doing that and i fully understand the process but I want to confirm (Yes I Have TWRP recovery installed and running) I only need to extract the boot.img out of the winRAR file of the ROM that I downloaded? (CM10 seems to be popular so I'm starting with that as my first ROM) There are so many other files in the package and I'm wondering why do you only need the boot.img file to be present with your adb and fastboot files from the google dev SDK -- the boot.img is only 5 MB and I can hardly believe that it constitutes the whole OS?
2) How do I go about installing gapps after I have flashed my ROM? I have downloaded Gapps so I have the file...do I place it in my SD Card and then enter recovery to install it? or Do have to use adb to flash it
Edit: I also have Superuser app on my stock ROM right now
Any further help is much appreciated, thank you very much.
Click to expand...
Click to collapse
follow his instructions and you'll be fine
flash the boot.img in flashboot, reboot in recovery, flash your nameofrom.zip, flash your gapps pkg just like the rom (on your sd card), enjoy...
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
TheEmpyre said:
Thanks for the reply, the community on XDA kicks a$$, doing some additional reading just plz tell me if I understand this correctly...
1) Copy CM10 zip and Gapps zip into phone storage
2) Follow GuyIncognito's instructions on flashing boot.img
3) Boot into recovery AFTER Flashing boot.img
4) Select "Install" in TWRP
5) Install CM10 zip First
6) Install Gapps zip next
7) Reboot
8) profit?
Click to expand...
Click to collapse
yes that;s correct you may wanna backup your sd card 1st as well and do a full wipe before flashing the rom.
Just in case your not familiar with fastboot, the command is fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
Crappyvate said:
follow his instructions and you'll be fine
flash the boot.img in flashboot, reboot in recovery, flash your nameofrom.zip, flash your gapps pkg just like the rom (on your sd card), enjoy...
Click to expand...
Click to collapse
By Flash do you mean using TWRP recovery "install" feature and selecting the CM10.zip I have in my SD Card, and gapps? Just making sure I dont have to do it via command prompt cuz then I may have to do some additional reading
Edit: Just saw you all beat me to it, thanks all, will get back to you after I am running a ROM *crossfingers*
TheEmpyre said:
By Flash do you mean using TWRP recovery "install" feature and selecting the CM10.zip I have in my SD Card, and gapps? Just making sure I dont have to do it via command prompt cuz then I may have to do some additional reading
Click to expand...
Click to collapse
yes install. you dont need to do it from command prompt, additional reading is always good
even though it was put together a while back this http://forum.xda-developers.com/showthread.php?t=1678308 is a very good guide and covers a lot of things of course you should absolutely start here in redpoint indispensable guide to all the resources available to one xl http://forum.xda-developers.com/showthread.php?t=1671237
happy flashing
Alright Looks like I successfully flashed CM10! I flashed gapps with it at the same time but I have run into a problem -- It keeps telling me that all these gapps processes have failed and I have no access to a keyboard! Do I have to reflash gapps?
Hmm ok I think I messed up here....
My phone was essentially non-functional with CM10 -- Nothing worked and it took me a while to navigate to enable USB Debugging on the given mod. One I enabled USB Debugging in CM10 I ran the following:
adb reboot recovery
Once I was in recovery, I Restored a backup of my device that I made BEFORE I obtained permanent root via the toolkit as it was recommended during this time to make a recovery.
Recovery worked successfully, now after reboot it hangs on the HTC screen and then goes black, then reboots again, and again, and again...
I haven't been able to use the volume down + power button to even get back into the bootloader.....hopefully I am not screwed here...Any suggestions?
TheEmpyre said:
Hmm ok I think I messed up here....
My phone was essentially non-functional with CM10 -- Nothing worked and it took me a while to navigate to enable USB Debugging on the given mod. One I enabled USB Debugging in CM10 I ran the following:
adb reboot recovery
Once I was in recovery, I Restored a backup of my device that I made BEFORE I obtained permanent root via the toolkit as it was recommended during this time to make a recovery.
Recovery worked successfully, now after reboot it hangs on the HTC screen and then goes black, then reboots again, and again, and again...
I haven't been able to use the volume down + power button to even get back into the bootloader.....hopefully I am not screwed here...Any suggestions?
Click to expand...
Click to collapse
I think u need to flash that backups boot IMG
omario8484 said:
I think u need to flash that backups boot IMG
Click to expand...
Click to collapse
Yes that would make sense, but the problem is A) How do I access that backup's .img file? B) How can I enter bootloader again? It won't let me using Power+Vol Down, no matter how long I hold it for --- unless I need to hold it longer?
You have to hold it till the buttons flash and goes black... Hold for about 2-3 more seconds and release the power button, but keep the volume down held until you get to a white hboot screen. (it'll have three skating droids)
Sent from my HTC One XL using xda premium
InflatedTitan said:
You have to hold it till the buttons flash and goes black... Hold for about 2-3 more seconds and release the power button, but keep the volume down held until you get to a white hboot screen. (it'll have three skating droids)
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok got it, did a factory reset then re-flashed CM10 boot.img...Flashed CM10 BY ITSELF this time, without doing gapps at the same time, rebooted into recovery after CM10 rolled up, then flashed gapps alone, everything is working smoothly! Now, time to restore my apps
Panicked momentarily, but now I'm back at it.
THANK YOU EVERYONE! Huge ups to all of you for helping a noob find his way
First of all I decided to install CM10 without making a backup on TWRP 2 (clever Kyle). Then when it was stuck on the bootanimation for about an hour, I got annoyed and looked through the forums for help. "Factory reset, clear caches before installing etc" So I deleted the ROM, factory reset via TWRP, deleted both cache and then tried to install CM10. Failed.
Then I tried to mount the SD card to my computer to try to find other ROMS to install. Viper and Energy both failed. I then tried CM10, Viper and Energy with CWM 5.8, and the installation of all gets aborted almost instantly, which I am guessing means that it failed on there as well. I then tried ADB, and pushing keeps failing. Does anybody have any ideas at all on how to get just any ROM onto the phone so that I can get the official 4.1 update again (my phone was on 4.1 before trying CM10, so the HBOOT is most likely 4.1 as well). Any advice would be greatly appreciated, because having a £350 paperweight is not what I particularly want, especially considering I have another 9 months contract to run and no spare phone on the same network as my current contract.
kylepont said:
Any advice would be greatly appreciated
Click to expand...
Click to collapse
When you say that installing ROMs fails and adb pushing fails, you should tell us what error messages you get.
If you can still get into bootloader, you're probably going to be fine.
First, check that you can mount your sdcard in recovery. I don't mean mount onto your PC over USB, but just mount the sdcard partition onto the root filesystem.
If you can not get into recovery, re-flash one.
If recovery can not mount the sdcard, then you have to go to the sticky on how to fix unmountable sdcard. It involves flashing a stock recovery and then clearing storage from bootloader.
If your recovery is good and your sdcard is mountable, adb pushing should work. If it doesn't, post error messages. Make sure your sdcard is mounted before you try to push fils to it.
In recovery, format system, data, cache, but not sdcard. Then flash a zip. Then boot back into bootloader/fastboot and fastboot flash the boot image that comes with the rom. (Did you do this last step when flashing other roms?)
If this does not work not for you, describe in detail what you do and what you see. If it does work out, I suggest you make a nandroid backup so you can get back to this state, and S-off the device.
-Jobo
touch of jobo said:
If this does not work not for you, describe in detail what you do and what you see.
Click to expand...
Click to collapse
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Click to expand...
Click to collapse
Have you flashed the boot.img?
fastboot flash boot boot.img
Sent from my One S using Tapatalk 2
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img
Click to expand...
Click to collapse
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
kylepont said:
Sometimes a print screen can speak louder than words.
Click to expand...
Click to collapse
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Edit:
kylepont said:
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
The flashing instructions for your ROM will likely state that you have to 'flash the boot image (or boot.img or kernel) in fastboot before booting into the rom.
You can find a file named 'boot.img' inside your rom zip. You have to flash that in fastboot. You can do it before or after flashing the rom, but you must do it before booting into the rom.
kylepont said:
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img/QUOTE]
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
Extract the boot.img file from the ROM. Place it in your adb folder. Boot into bootloader, select fastboot and connect to PC. Type command fastboot flash boot boot img
Click to expand...
Click to collapse
touch of jobo said:
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Click to expand...
Click to collapse
All the boxes are ticked on the TWRP Mount screen, including System and SD card. And yes, I did make sure that it is:
1) in the same folder as the adb
2) called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
And usaff22, does that involve unzipping the ROM that I am using?
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
kylepont said:
I did make sure that it is [...] called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
Click to expand...
Click to collapse
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
kylepont said:
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
Click to expand...
Click to collapse
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Also, does it say anything interesting when it fails?
Before flashing the zip, did you format your system, data, cache partitions?
EDIT: After repeatedly trying to adb push, I finally got CM10.zip.zip onto the phone. Flashing took a bit longer than last time, but booting took no time at all. Thank you touch of jobo and usaff22, your advice was a lot of help.
touch of jobo said:
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
Click to expand...
Click to collapse
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
touch of jobo said:
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Click to expand...
Click to collapse
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
touch of jobo said:
Before flashing the zip, did you format your system, data, cache partitions?
Click to expand...
Click to collapse
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
kylepont said:
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
Click to expand...
Click to collapse
I can't help with that adb error. Never seen it. Try searching the forums for it. Sorry. Also, I don't use Windows, so I don't know about driver versions and things.
kylepont said:
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
Click to expand...
Click to collapse
TWRP and CWM are both fine for flashing ROMs, just not this specific version of TWRP. Since I dont use it myself, I dont know the exact version numbers, but read around a bit and you'll find what worked for others.
Maybe flashing a different recovery will even get rid of your protocol error.
If you've made nandroid backups (I guess you havent or we wouldnt be here.. sorry) you should stay with the same recovery (same 'brand', not same version) or you can't restore them.
kylepont said:
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
Click to expand...
Click to collapse
The CM10.zip should be on your sdcard, not your system partition. You dont need the boot img at all on your device. You need it on your PC in order to fastboot flash it.
Before flashing a ROM you should wipe your 'system', 'data', and 'cache' partitions, but not your 'sdcard' partition. Only if you flash (a newer version of) the same ROM you have operational, then you can sometimes flash without wiping. This is called 'dirty flashing'. But this does not apply in your case.
Successful flash of CyanogenMod, thanks for the help.
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Click to expand...
Click to collapse
I would rename the zip to something else like sense.zip, place it on the desktop and do adb push C:\Users\username\Desktop\sense.zip /sdcard/
Make sure you use backward slashes for the PC file location, and forward slashes for the phone paste location.
This way we are also providing the full path on the PC.
Also make sure you use the latest adb from the SDK website. You don't need the whole thing, just the platform-tools bit, and replace the files in the new folder with the old one.
Sent from my One S using Tapatalk 2
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
kylepont said:
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
Click to expand...
Click to collapse
You might be able to find an RUU lying around on one of the websites which give RUUs such as androidfiles.org/ruu
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
kylepont said:
the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required)
Click to expand...
Click to collapse
You can extract the recovery image from any RUU or OTA. Recoveries do not depend on carrier.
But .. if you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
touch of jobo said:
If you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
Click to expand...
Click to collapse
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
usaff22 said:
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
Click to expand...
Click to collapse
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
kylepont said:
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
Click to expand...
Click to collapse
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
kylepont said:
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
Click to expand...
Click to collapse
This is the thread: http://forum.xda-developers.com/showthread.php?t=1671643
It involves extracting, hex-editing, and flashing a critical part of your device. If you make the slightest mistake you have a brick. However, if you read carefully and double check every step, it's not difficult. Many have done it. Read the thread.
Once you have supercid, you may as well get s-off as well. (This is the thread: http://forum.xda-developers.com/showthread.php?t=2155135 ) That way you can always flash anything.
Whatever you decide to do, before you start on anything, read all the instructions to the end, so that you're sure you can complete the process before you start. Also, before you start any process, try to understand what each step does and why it is necessary. That may involve a lot of reading and searching, but that is a Good Thing in the end.
touch of jobo said:
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
Click to expand...
Click to collapse
It is unmountable. I tried CWM and TWRP to no avail. Also, I have HBOOT version 2.15 which I heard is a bugger to work with. Also, I got the ZIP file for the stock 4.1, and I read that the stock recovery is in the firmware folder, but I cannot access it. (https://www.dropbox.com/s/kyn9sb5x7gpd7fr/Picture2.png) Then, I tried to get to the CID, following the instructions that you gave me, and I didn't get very far (https://www.dropbox.com/s/g6ik0i3los7unde/Picture3.png)
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
I successfully rooted and achieved an unlocked bootloader with S-OFF on my Verizon HTC One M8 and also flashed TWRP 2.7.0.2. I downloaded a rom (without an SD card). I booted into recovery and i made a backup (not noticing that one of the lines read "unable to mount '/system". I then wiped and attempted to flash the rom only to find out that i can't find it in my file system. So i put the rom on an SD card and mounted it and tried to flash it, i get this message:
E: Unable to mount '/system'
E: Unable to open zip file.
Error Flashing zip '/external_sd/Roms?ViperOneM*_1.2.0.zip'
Updating partition details...
E: Unable to mount '/system'
So i'm stuck with a boot loader, an unmountable file system, and unable to flash a rom.
I've tried Fix permissions, I've tried mounting the "system" but all that mounts is 'cache' 'data' and 'micro SDcard'.
I hope my nerves are getting the best of me and i can't see something that's right in front of me!
Edit: Flashed CWM Recovery. Trying to install ROM from SD Card results in "Installation Aborted". When i try to side load it hangs at 81%.
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
dsEVOlve said:
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
Click to expand...
Click to collapse
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
First of all you aren't bricked. Have you tried using side load to flash the ROM? Try flashing another recovery too.
Sent from my HTC6525LVW using Tapatalk
SimplyNando said:
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
Click to expand...
Click to collapse
The above suggestion to try and Sideload the ROM install is a good idea. Basically, put the ROM zip file in your platform-tools folder of adb. Then boot to TWRP recovery, choose "sideload" and then issue the command "adb sideload [filename.zip]" (Instructions are found HERE.)
If that doesn't work, have you tried flashing Clockwork Recovery? You may have better luck with that in regards to mounts and/or flashing the ROM...
There's always USB OTG as well
Sent from my HTC6525LVW using Tapatalk
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
WorldOfJohnboy said:
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
Click to expand...
Click to collapse
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
SimplyNando said:
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
Click to expand...
Click to collapse
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
123421342 said:
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
Click to expand...
Click to collapse
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
SimplyNando said:
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
Click to expand...
Click to collapse
no because it is not a flashable zip. Factory image or RUU means the bootloader will literally write the partition. Recovery will mount the partition and write information to it. It cannot create the partition itself which I think is your issue.
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
bakemcbride21 said:
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
Click to expand...
Click to collapse
Yep. You have a bad download. Download a new ROM on your computer...boot to recovery and do a adb sideload or push
Sent from my HTC One M8
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
WorldOfJohnboy said:
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
Click to expand...
Click to collapse
Kernel runs inside the rom and the system becomes writeable in the ROM so that won't do anything. I'm pretty convinced he is missing the partition.
Sent from my HTC6525LVW using Tapatalk
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
jerico9 said:
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
Click to expand...
Click to collapse
did you try formatting internal yet?
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
jerico9 said:
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
Click to expand...
Click to collapse
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
dottat said:
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
Click to expand...
Click to collapse
I mean the device memory was low, so couldn't flash as no room on the device