Related
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'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Bagel Bear said:
I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Click to expand...
Click to collapse
Did u try using fastboot to flash it? Also dont forget to extract the ROM from the downloaded zip file.
I did not realize the ROM .zip file was inside the .zip file...
Thank you installing now. After that I just have to flash an updated recovery and then install an custom ROM, correct. You've been a great help.
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Bagel Bear said:
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Click to expand...
Click to collapse
Did you install the -42 TWRP since you are now on the 4.2 boootloader?
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Bagel Bear said:
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Click to expand...
Click to collapse
Did you mount the correct partition in the settings of TWRP. Try unmounting and then remounting what you need.
Even the log on TWRP says it is unable to mount anything on startup. When I try to exit TWRP it says that I am not rooted and prompts me if it can root for me. Can I do it this way?
Anyone know anything about this?
Bump
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying:
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
I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance
radster12795 said:
I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance
Click to expand...
Click to collapse
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490
jollywhitefoot said:
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490
Click to expand...
Click to collapse
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?
radster12795 said:
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?
Click to expand...
Click to collapse
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22
jollywhitefoot said:
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22
Click to expand...
Click to collapse
Finally made it work, went to sdcard installed the zip it said successful then i rebooted it but it is still stuck in the booting screen -_-
and when i opened the bootloading screen it still says no OS
TAMPERED
UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.27.40e.00.11
OpenDSP-v19.2.0268.0927
OS-
eMMC-boot 1024mb
i think my phone doesnt have the firmware cause it said successful but it also said cant moutn /system at the end, any idea?
Thank you very much btw, for helping me, learned so much stuff
followed the other comments to install the sense6 firmware, my phone needs to be S-OF and superCID, finished superCID but i cant run rumrunner cause my phone dont have OS, is there a way to run rumrunner thourgh fastboot or recovery?
Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again
jollywhitefoot said:
Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again
Click to expand...
Click to collapse
oaky, i have installed twrp 2.7.1.1 and now adb pushing the rom and ill try to recovery install the rom again
Finished the zip install
Updating partition details...
E:Unable to mount '/system'
Full SELinux support is present.
Installing 'sdcard/Stock_Sense6M4_Deodexed-Rooted.zip'...
Checking for MD5 file..
Skipping MD5 check: no MD5 file found
->Mounting System & Data
->Extracting System
->Extracting Data
->Creating toolbox symlinks
->Creating additional symlinks
->Installing busybox
->Setting permissions
->Extracting kernel
Updating partition detail...
E: Unable to mount '/system'
It said successful but still no OS installed
sorry the problems just keep coming and coming
First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903
jollywhitefoot said:
First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903
Click to expand...
Click to collapse
Thank you for the past 2 days of helping, i have finally fixed it :highfive:
radster12795 said:
Thank you for the past 2 days of helping, i have finally fixed it :highfive:
Click to expand...
Click to collapse
No problem. Did flashing the ROM in post 8 work?
jollywhitefoot said:
No problem. Did flashing the ROM in post 8 work?
Click to expand...
Click to collapse
YES!! it worked perfectly, Thank you very much
thinking about upgrading to sense 6 now