Related
I took hboot 0.76.2000 from toast's root nand unlock part2 and put it in a new PC36IMG, so that those who installed unrevoked forever can get the extended fastboot commands back.
NOTE: This is only for unrevoked forever users.
Tested to work if flashed from hboot (bootloader)
Not tested in recovery.
NOTE 2: Make a nandroid backup.
Place file on root of sdcard, power off your phone, then power on your phone by holding volume+down and pressing+holding the power button until the white bootloader appears. Press volume up once asked to install the bootloader.
NOTE 3: For those experiencing being stuck in bootloader, you can boot into recovery, flash your current ROM again, (without data wiping) OR just restore a nandroid backup. Flashing a custom kernel will also get you out of the loop. I'm going to go ahead and assume flashing anything other than hboot iwll get you out of the loop.
This will NOT wipe your device, however, backing up is always recommended.
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Here's the recovery flashable version that I made a while ago
Calkulin said:
Here's the recovery flashable version that I made a while ago
Click to expand...
Click to collapse
Nice. had no idea you made it
Guess I should have searched last night lol.
freeza said:
Nice. had no idea you made it
Guess I should have searched last night lol.
Click to expand...
Click to collapse
Well I made it but never posted it as there was no way of flashing it unless you had the ENG hboot to begin with
anyway of having 79.00 with the commands?
I'm sorry op but its surely going to be asked so might as get it out quickly lol
Exactly what commands are missing?
rjmjr69 said:
anyway of having 79.00 with the commands?
I'm sorry op but its surely going to be asked so might as get it out quickly lol
Exactly what commands are missing?
Click to expand...
Click to collapse
He's talking about the fastboot commands, the commands you run when you reboot your phone and set your as "fastboot". Here's some commands you've probably seen if you've tried flashing a custom kernel:
Code:
fastboot flash zimage zImage
fastboot reboot
pseudoremora said:
He's talking about the fastboot commands, the commands you run when you reboot your phone and set your as "fastboot". Here's some commands you've probably seen if you've tried flashing a custom kernel:
Code:
fastboot flash zimage zImage
fastboot reboot
Click to expand...
Click to collapse
Adding on to this, you probably only need fastboot commands if you're planning on doing some serious rom development.
sk63 said:
Adding on to this, you probably only need fastboot commands if you're planning on doing some serious rom development.
Click to expand...
Click to collapse
Thanks for answering
one slight thing I am confused on now with unrevoked forever available.
Is it possible to flash the ENG boot without changing the PRI ?
for example:
- stock 2.1 evo / 1.40 pri
- unrevoked 3 + unrevoked forever
- still on 1.40 pri
- flash ENG boot without 1.34 pri, leaving the 1.40 pri
?
I would like to know the same thing.
-frank
Sent from my PC36100 using XDA App
TeknoJnky said:
one slight thing I am confused on now with unrevoked forever available.
Is it possible to flash the ENG boot without changing the PRI ?
for example:
- stock 2.1 evo / 1.40 pri
- unrevoked 3 + unrevoked forever
- still on 1.40 pri
- flash ENG boot without 1.34 pri, leaving the 1.40 pri
?
Click to expand...
Click to collapse
kaediil said:
I would like to know the same thing.
-frank
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yes, it is.
Can this be reversed? Do you have the 79.00 to flash back?
rjmjr69 said:
Can this be reversed? Do you have the 79.00 to flash back?
Click to expand...
Click to collapse
I can extract it from an official RUU.
freeza said:
I can extract it from an official RUU.
Click to expand...
Click to collapse
Ok but will the phone still be unlocked via unrevokedforever?
rjmjr69 said:
Ok but will the phone still be unlocked via unrevokedforever?
Click to expand...
Click to collapse
yes, it will.
freeza said:
yes, it will.
Click to expand...
Click to collapse
Cool I would like that very much please thanks sir
rjmjr69 said:
Cool I would like that very much please thanks sir
Click to expand...
Click to collapse
here you go.
freeza said:
here you go.
Click to expand...
Click to collapse
You seem in the know, so I'm asking you... I ran unrevoked forever, it said it was successful, but my HBOOT stayed as ENG HBOOT .76. Is that correct or did I screw up unrevoked somehow?
Thanks for this. I flashed the wrong damned pc36img.zip (thought I was flashing the one that had rooted 1.47) to get back to a sense rom from cm6 to do the pri hackery and had upgraded hboot.
Now that my pri's fixed I'd rather have S-OFF and the engineering hboot than sit here and reset my phone another 20ish times to get 1.40 pri back after re-flashing the engineering image!
freeza said:
here you go.
Click to expand...
Click to collapse
So this is the same file that it ends up with when you run unrevokedforever?
Does it say s-on or off?
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 .
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)
Okay, so I decided to do something stupid and forget to backup my HTC One S while rooting. I installed CM10, and it got stuck in a bootloop, so stupid me decided to also do a factory reset and basically delete everything I needed to get out of it. I've tried numerous things, including ADB sideloading a ROM, but whenever I do that, it also gets stuck in a boot loop. I have no idea how to use RUU's, and if anybody could help me to fix my phone, that'd be really really helpful. I'm also kindof a n00b towards this stuff, so step-by-step instructions would be much appriciated Thanks.
~MuZiiX
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
CuzCrostyPwns said:
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
Click to expand...
Click to collapse
I think my device is s-off...i used the HTC One S all in one toolkit, and I have no idea what supercid is :s I've tried a couple RUU's before (don't know if i used them correctly, but i did relock the bootloader when i did it) but none of them helped. It just stayed at a black screen with "htc" in the middle. No error triangles or anything.
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
CuzCrostyPwns said:
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
Click to expand...
Click to collapse
Yeah, the RUU's were .exe's with my phone connected through USB. I can get into recovery, I have CWM installed.
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
CuzCrostyPwns said:
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
Click to expand...
Click to collapse
Well thats what I've been trying to do with the ADB sideloading, because it wont let me mount my sd card. It just says 'ERROR MOUNTING SD CARD" and when I've tryed flashing a new ROM from ADB sideloading, it just gets stuck in a bootloop again.
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
CuzCrostyPwns said:
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
Click to expand...
Click to collapse
I've tried running multiple RUU files, and I have no idea what one to use. The phone when I got it was unlocked, and the android version was ICS I'm pretty sure.
I dunno how to find my stock settings because I cant get past the loading screen.
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
did you flash boot.img? most of roms will bootloop without it
Roundtableprez said:
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
the boot.img is located in the zip you downloaded from get.cm
NQNH said:
the boot.img is located in the zip you downloaded from get.cm
Click to expand...
Click to collapse
So what command would I use while flashing the boot.IMG file? (again sorry for not getting this, I just wanna get my phone working again)
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Download or build from source
Download gapps
wipe unless you're upgrading from an earlier CM10 ROM
flash rom in recovery
flash gapps in recovery
unless you have s-off fastboot flash boot boot.img
Click to expand...
Click to collapse
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
dc211 said:
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
Click to expand...
Click to collapse
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
MuZiiX said:
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
Click to expand...
Click to collapse
It not really a big deal. Your problem is the most common one we see in Q&A. Also, once you finish flashing the boot.img keep in mind that CM10 can take a few minutes to boot the first time.
Also, just a heads up while the toolkits are helpful learning the command yourself actually lets do you a lot more things a lot faster.
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
MuZiiX said:
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
Click to expand...
Click to collapse
Nope, just gotta do it one of the three ways mentioned. If debugging isn't enabled use option 1.
This can either be done via
1 powering off and keeping volume up & the power-button pressed
2 the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
3 via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Click to expand...
Click to collapse
I made a custom splash screen (kernel screen, 1st boot img etc.) That works seamlessly with the google pixel boot animation.
Splash - https://drive.google.com/open?id=0B8in4PEF59ENeHF1V2RNRURYV0E (move to sd card and flash through download mode)
Boot animation - https://drive.google.com/open?id=0B8in4PEF59ENRk1QZEhzRVdZWFk (flash through custom recovery)
--------------------------------------------------------------------------------------------------------------------------------------------------------
You can also make your own using Splash Flasher, All credit to TrueBlue_Drew, Put a 1080x1920 image in and run the program.
Splash Flasher - https://drive.google.com/open?id=0B8in4PEF59ENWjRGSm1MVklBdTQ
select an option to convert image to IMG file, then go to Splash flasher>place-image-here and rename your new image file to "splash1.nb0" Next, download this: https://drive.google.com/open?id=0B8in4PEF59ENVmRvUlE1UzIwd28. Lastly, move Your splash1.nbo file and your android-info.txt into a zip file and rename it to 2PQ9IMG. Flash through download as normal
This works for usa unlocked but you can change it. Simply edit the android-info.txt to your mid/cid. SuperCID works.
Is this limited to just the One A9? I'm running a One M8 that has the same 1080p resolution
Sent from my Pixel using Tapatalk
Yes but s-off is required. this is totally possible, go to your download mode and get the Cid and mid, and also at the bottom get the name of the file that it wants you to flash. Next, change the android-info.txt to have matching mid/Cid of your device and follow the rest of the steps above, and once you have made your flash able zip, name it to the one your download mode says.
Looks great thanks for sharing.
You just killing. now I dunno my phone is HTC or Pixel anymore lol
anunknwon said:
You just killing. now I dunno my phone is HTC or Pixel anymore lol
Click to expand...
Click to collapse
???
Thanks for the post.. very useful.
One thing I wanted to ask, would it be possible to flash the boot-animation by any means other than custom recovery?
I did have TWRP installed but am now on stock recovery, TWRP was overwritten when flashing the stock RUU in order to get OTA updates.
If I have to re-flash TWRP then fine, I can re-run the RUU after but I would prefer to spend as little time as possible messing about in recovery etc..
t3xtid said:
Thanks for the post.. very useful.
One thing I wanted to ask, would it be possible to flash the boot-animation by any means other than custom recovery?
I did have TWRP installed but am now on stock recovery, TWRP was overwritten when flashing the stock RUU in order to get OTA updates.
If I have to re-flash TWRP then fine, I can re-run the RUU after but I would prefer to spend as little time as possible messing about in recovery etc..
Click to expand...
Click to collapse
For the boot animation, you can use flash fire, or extract boot animation.zip and move it to system/media
The_scam said:
For the boot animation, you can use flash fire, or extract boot animation.zip and move it to system/media
Click to expand...
Click to collapse
Thanks, that helps.
t3xtid said:
Thanks, that helps.
Click to expand...
Click to collapse
No problem
Have your phone have a red message when you boot up? I little bit pi** off to flash this file because I was hard brick my m9 to get off this message.
anunknwon said:
Have your phone have a red message when you boot up? I little bit pi** off to flash this file because I was hard brick my m9 to get off this message.
Click to expand...
Click to collapse
I cant really understand this message, but from what i can tell, you want to remove the red message, which hboot checks for. There are sucsessfull ways to remove this on most htc deviced, just not for the One A9, DO NOT ATTEMPT TO FLASH A MODIFIED hboot file. unless it is confirmed working. also, there is already a thread about this. Just dont do it.
The_scam said:
I cant really understand this message, but from what i can tell, you want to remove the red message, which hboot checks for. There are sucsessfull ways to remove this on most htc deviced, just not for the One A9, DO NOT ATTEMPT TO FLASH A MODIFIED hboot file. unless it is confirmed working. also, there is already a thread about this. Just dont do it.
Click to expand...
Click to collapse
Yay you get me right. lucky I didnt try
Thanks:fingers-crossed: