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)
I have recently unlocked my bootloader using sunshing, and installed twrp 2.8.0.1 as my custom recovery. I do not have any problems flashing stock based roms but when I try to flash cm11(or other) based roms I'm always met with:
Code:
This package is for "xt1052, ghost, xt1053, ghost_retail, xt1055, ghost_usc, xt1056, ghost_sprint, xt1058, ghost_att, ghost_rcica xt1060, ghost_verizon" devices; this is a " ",
Code:
E:Error executing updater binary in zip 'location-of-rom.zip' :
These are roms from the Moto x xda forum I'm trying to flash. Any help is appreciated as ive searched for hours for a fix or someone having the same problem on my device with no luck.
I tried to RSD back to 4.4.2 19.5.3 stock where i started, and took all the ota updates, flashed twrp 2.8.0.1 through fastboot. Tried flashing a cm11 rom from the moto x "crdroid" and same errors as usual. Can anyone offer any assistance? The only roms that are flashing correctly are based off stock. Is there something in the rom zip i need to modify for my phone?
Having Similar issues
I am running into the same issue, I loaded the eclipse rom on to my phone and it does not matter which version or location I download it from the rom boots minus the red filter and is terribly unstable. I am in the process of trying to Fastboot Venom, but so for nothing else is recognized.
You have to modify the met.inf file to flash these roms.
Kuatous said:
I am running into the same issue, I loaded the eclipse rom on to my phone and it does not matter which version or location I download it from the rom boots minus the red filter and is terribly unstable. I am in the process of trying to Fastboot Venom, but so for nothing else is recognized.
Click to expand...
Click to collapse
But how?
Archangel said:
You have to modify the met.inf file to flash these roms.
Click to expand...
Click to collapse
What would you recommend as a how to do so? I have been researching and I am finding the folder but not what part to modify.
Could you elaborate a little Archangel? What do I need to change specifically in the file? And where can I find it?
Sorry didnt see the response,,,you need to the Team Gummy thread in this area
http://forum.xda-developers.com/showthread.php?t=2676291&page=9
and follow the directions I asked another user. It involves unzipping and modding the meta.inf file and take out some file numbers so the install will not look for specific phones.
slikerhael said:
Could you elaborate a little Archangel? What do I need to change specifically in the file? And where can I find it?
Click to expand...
Click to collapse
I'd like to install something like this "[S6 G920F/S6 Edge G925F] [6.0.1] [3DPBK] [05/03] [v3.2] Pure Stock ExtraLite Rom" but if I wipe everything I can't seem to get the ROM onto the device to flash via recovery. I believe there are two ways potentially adb push and adb sideload but I've no experience with them. I either get a sideload error about "cannot read" for the filename or I get an error closed with push.
I'm happy to continue trying to work out how to do it but am I on the right path with these or is there a better way to get the zip onto the device?
thanks
andyjg247 said:
I'd like to install something like this "[S6 G920F/S6 Edge G925F] [6.0.1] [3DPBK] [05/03] [v3.2] Pure Stock ExtraLite Rom" but if I wipe everything I can't seem to get the ROM onto the device to flash via recovery. I believe there are two ways potentially adb push and adb sideload but I've no experience with them. I either get a sideload error about "cannot read" for the filename or I get an error closed with push.
I'm happy to continue trying to work out how to do it but am I on the right path with these or is there a better way to get the zip onto the device?
thanks
Click to expand...
Click to collapse
Why not put your phone into download mode and flash via Odin if you have a pc
Envoyé de mon SM-G928F en utilisant Tapatalk
Charging the 4-piece Firmware Download with SamFirm.
You need the new boot loader if you come from 5.1.1.
Thanks guys. The ROM isn't available as a file that can be flashed through ODIN. My issue is if I wipe the device I can't get the file on there to flash it through recovery. I thought adb may be the way but I can't get it to work
Long live the separate sd card in my old S4...
andyjg247 said:
Thanks guys. The ROM isn't available as a file that can be flashed through ODIN. My issue is if I wipe the device I can't get the file on there to flash it through recovery. I thought adb may be the way but I can't get it to work
Long live the separate sd card in my old S4...
Click to expand...
Click to collapse
I can however load a standard rom, flash recovery and then flash the zip. Aroma gives the ability to wipe data so that's as good as I can get it.
thanks for the help guys,.
Somebody should please help me, if I'm posting wrongly or in the wrong section, I do not know, I am new here and I need help. I have searched and read countless posts on here but I still can't get a solution.
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
I downloaded this officially from the HTC website
RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.10
when I run the file, it will start then disappear into thin air (I use windows 8.1 on my computer).
so I decided to go in the way of custom roms, phone is already S-OFF and Bootloader UNLOCKED. I installed adb & fastboot, I flashed TWRP and was able to boot into twrp recovery.
I downloaded the first custom rom (can't remember from where I downloaded that) and from the instructions, I was told to rename it to 2PQ9IMG.zip which I did and in attempt to flash it, got this error code,
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
Error flashng zip '/sdcard/2PQ9IMG.zip'
I had to go download another custom rom with the below file name
OTA_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.1-1.57.617.60_release_493556mv4q5xb4fbi8qvyk
and in attempt to install this as well, I got the errors below
Checking for MD5file...
Skipping MD5 check: no MD5 file found
N70QCT.01.000.004
E:unknown command [set_err_msg]
E3004: This package is for "htc_hiaeul" devices; this is a "htc_hiaewhl"
E:Updater process ended with ERROR=7
Error flashing zip '/sdcard/OTA....................
then this fourth rom again.
Sprint-A9-1.57.651.1
which I believed should work perfectly after a lot of research and in attempt to install this rom, I got this error
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
I am now totally fed up, I have been having a bad phone for 4 days now and I need my phone back ASAP. Somebody should please help me as a noob with the simplest well understood instructions, I will show gratitude.
mneynaire said:
Somebody should please help me, if I'm posting wrongly or in the wrong section, I do not know, I am new here and I need help. I have searched and read countless posts on here but I still can't get a solution.
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
I downloaded this officially from the HTC website
RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.10
when I run the file, it will start then disappear into thin air (I use windows 8.1 on my computer).
so I decided to go in the way of custom roms, phone is already S-OFF and Bootloader UNLOCKED. I installed adb & fastboot, I flashed TWRP and was able to boot into twrp recovery.
I downloaded the first custom rom (can't remember from where I downloaded that) and from the instructions, I was told to rename it to 2PQ9IMG.zip which I did and in attempt to flash it, got this error code,
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
Error flashng zip '/sdcard/2PQ9IMG.zip'
I had to go download another custom rom with the below file name
OTA_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.1-1.57.617.60_release_493556mv4q5xb4fbi8qvyk
and in attempt to install this as well, I got the errors below
Checking for MD5file...
Skipping MD5 check: no MD5 file found
N70QCT.01.000.004
E:unknown command [set_err_msg]
E3004: This package is for "htc_hiaeul" devices; this is a "htc_hiaewhl"
E:Updater process ended with ERROR=7
Error flashing zip '/sdcard/OTA....................
then this fourth rom again.
Sprint-A9-1.57.651.1
which I believed should work perfectly after a lot of research and in attempt to install this rom, I got this error
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
I am now totally fed up, I have been having a bad phone for 4 days now and I need my phone back ASAP. Somebody should please help me as a noob with the simplest well understood instructions, I will show gratitude.
Click to expand...
Click to collapse
File name starting with "OTA" are ota updates (patches) not full rom and can't be used to restore a phone. Renaming files "2PQ9IMG.zip" is used only when flashing RUU.zip or Firmware.zip in bootloader mode using the sdcard, not for flashing custom rom in TWRP. TWRP can't be used to flash RUU.zip or Firmware.zip. If your phone is a whl variant (Sprint) use the Sprint RUU or follow the guide to convert to Us Unlocked. Good information about RUU in the ruu collection thread at post #2. If you need more help tell us your CID, MID and version-main and what your goal is (re-flash the sprint RUU or convert to US Unlocked).
mneynaire said:
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
Click to expand...
Click to collapse
How are you rooted? If you can, boot into TWRP, pull your data off it, and then I'd say your easiest option is to start fresh using an RUU. Download and run the full RUU.exe for your Sprint phone following the instructions from the RUU thread.