I was trying to root the M7, but after flashing SuperSU, it didn't do anything, the binary didn't get installed and when I tried to install SuperSU manually from play it says the binary isn't there but I didn't get any error messages.
So I am trying to flash a rom that is already rooted to get root, but for some reason my TWRP only shows me having 471 MB Free, and because of that I can't even push the rom to flash.
Can anyone please help me? I've never been so frustrated trying to do what is supposed to be a simple thing before
This is for the Sprint black version with firmware 1.29.651.7
EDIT: Figured out what was wrong, had the wrong TWRP version for my phone, apparently sprint has its own special version just because.. For future reference.
The only thing I can think of to possibly fix the storage error would be to factory reset. So if there's any content you'd like to keep, be sure to transfer it to your computer so that you'll be able to transfer it back to the phone afterwards.
KidCarter93 said:
The only thing I can think of to possibly fix the storage error would be to factory reset. So if there's any content you'd like to keep, be sure to transfer it to your computer so that you'll be able to transfer it back to the phone afterwards.
Click to expand...
Click to collapse
I did the factory reset, gave me 1.8gb just enough to push the files on, but the rom wouldn't flash. I wiped system and cache to try to get rid of the unable to mount E: /system and E: /cache errors, but now I screwed up somewhere because I can't boot now, it goes straight to the bootloader and neither can I flash any roms via recovery.
I really hope I didn't just make the phone a paperweight..
Related
Can someone help me out? I’m what you might call a noob. I’ve root my phone. I have s-on because my radio is 2.42.02.10.29 and I don’t think unrevoked caries that yet. But as far as I understand, that shouldn’t be a big deal since this is signed. I just have to flash manually. So I rename aospCMod-20110201-signed.zip to update.zip and save it into the root of the sd card. I start in recovery. I first Wipe data/factory reset, I then Wipe cache and I finally update. But after trying to update for a couple of seconds I get an error that says signature verification failed. I tried downloading it twice and the same thing happened both times, so I’m pretty sure it’s not a corrupted file.
Someone please help.
-thanks
also, when I enter the Android system recovery I have the error E:Can't open /cache/recovery/command
I'm not sure what that means.
Flash the recovery in the op of the thread, and leave the rom filename alone.
stayclean said:
Flash the recovery in the op of the thread, and leave the rom filename alone.
Click to expand...
Click to collapse
But if it's not called update.zip the phone won't recognize it as something to flash. At least as far as I can tell.
Thanks for your help. I figured it out. I wasn't in the clockwork recovery because it just wasn't loading. When I switched to amon_ra, it worked fine. And I understand now that I don't need it to be named upgrade if you're in one of the fancy (clockwork/amon_ra) recoveries.
Hi everybody! I recently installed safestrap 3.72 and installed a couple KitKat roms, everything worked great until I tried to install AzureRom it said E: Unable to mount ' /system'. After that it can no longer mount the system partition... I've tried multiple things and I can't find anything that will work including wiping, formatting, and fix permissions. I also cant flash any roms because of this. I figured out how to use ROM-Slot-1 and able to boot SlimNote but it is very, very buggy and I have zero memory whats so ever. I tried to uninstall Safestrap through the apk but it did nothing. Please help and give me any ideas!!! Thank you so much for all your help!!
antnyhills said:
Hi everybody! I recently installed safestrap 3.72 and installed a couple KitKat roms, everything worked great until I tried to install AzureRom it said E: Unable to mount ' /system'. After that it can no longer mount the system partition... I've tried multiple things and I can't find anything that will work including wiping, formatting, and fix permissions. I also cant flash any roms because of this. I figured out how to use ROM-Slot-1 and able to boot SlimNote but it is very, very buggy and I have zero memory whats so ever. I tried to uninstall Safestrap through the apk but it did nothing. Please help and give me any ideas!!! Thank you so much for all your help!!
Click to expand...
Click to collapse
Because azurerom is 4.3 and you are on 4.4. Boot to slimnote on your slot and try to load up a 4.4 rom on your sd or internal memory. Boot to ss then go to stock slot and advanced wipe and wipe everything EXCEPT sd card then flash the 4.4 rom you loaded.
Last time I checked I wasn't able to flash roms, even after wiping but I'll try it. Thank you
antnyhills said:
Last time I checked I wasn't able to flash roms, even after wiping but I'll try it. Thank you
Click to expand...
Click to collapse
Hope you get it figured out, if anything you can restore to mj5 and start out fresh.
posersk8r said:
Hope you get it figured out, if anything you can restore to mj5 and start out fresh.
Click to expand...
Click to collapse
How can I do that? Odin?
http://forum.xda-developers.com/showthread.php?t=2559715
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
mrmead2 said:
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
Click to expand...
Click to collapse
Are you on jb? Kk? What rom you trying to flash?
i Have no rom installed now...I was running Dynamic Kat 3.0
I have safestrap 3.72...
was trying to install URDroid
mrmead2 said:
i Have no rom installed now...I was running Dynamic Kat 3.0
I have safestrap 3.72...
was trying to install URDroid
Click to expand...
Click to collapse
That's weird, never had that mounting error before. If you can boot to ss 3.72 try doing a full wipe EXCEPT sd or ex sd. If you still have urdroid saved or kk backup try to flash or restore for kk backup. If it still doesn't work, read 4 posts up.
mrmead2 said:
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
Click to expand...
Click to collapse
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
If nothing else works, go back to MJ5 (link on page 1).
If that fails, bring the phone to an AT&T Device Support Center. What will most likely happen is that they'll try to reflash it, fail and replace the phone. (If evilpotatoman's MJ5 restore fails, it's usually a bad motherboard.)
isharted said:
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
Click to expand...
Click to collapse
I have the same problem! I achieved root yesterday (finally) and tried to install the Firenote rom. It wouldn't take, so I restored my backup to try again. But when I tried again, it wouldn't mount E:. It wouldn't even allow me to restore backup. It failed to mount every time in stock slot. Eventually, it wouldn't even let me create a slot at all!
Out of desperation, I entered recovery and wiped data, and when I booted into safestrap again, I was able to create a slot, where I installed Alliance KK to have a functioning phone. Wifi works, although it's buggy (wifi doesn't work on Dynamic 3.2). So I'm stuck.
I tried downloading safestrap again and uninstalling/installing it, hoping that would work, but it didn't. The only thing I can think of that I did wrong was that I took the micro SD card out a few times while in safestrap without properly ejecting it, but I'm not sure if that had anything to do with it.
CPT Crunch said:
I have the same problem! I achieved root yesterday (finally) and tried to install the Firenote rom. It wouldn't take, so I restored my backup to try again. But when I tried again, it wouldn't mount E:. It wouldn't even allow me to restore backup. It failed to mount every time in stock slot. Eventually, it wouldn't even let me create a slot at all!
Out of desperation, I entered recovery and wiped data, and when I booted into safestrap again, I was able to create a slot, where I installed Alliance KK to have a functioning phone. Wifi works, although it's buggy (wifi doesn't work on Dynamic 3.2). So I'm stuck.
I tried downloading safestrap again and uninstalling/installing it, hoping that would work, but it didn't. The only thing I can think of that I did wrong was that I took the micro SD card out a few times while in safestrap without properly ejecting it, but I'm not sure if that had anything to do with it.
Click to expand...
Click to collapse
Yo fire rom is mj5, read up before you go flash happy. You can't go back to 4.3 once you are on 4.4 with the 4.4 bootloader...
Sent from my SM-N900A using XDA Free mobile app
tylerholbrook said:
Yo fire rom is mj5, read up before you go flash happy. You can't go back to 4.3 once you are on 4.4 with the 4.4 bootloader...
Sent from my SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Doh! Sorry! That explains a lot.Would that have screwed up my stock slot in safestrap?
isharted said:
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
Click to expand...
Click to collapse
I had this same problem until yesterday, I followed the instructions found here . I was able to restore my phone back to KK goodness, root, install busybox and safestrap, then flash a rom to my (previously untouchable) root slot. It worked perfectly
Soft brick after CM installer
Hi guys, I could really need some help here. I tried the Cyanogenmod installer and everything went fine, except my phone was stuck in
bootscreen for too long time (never booted).
In CWM recovery I did a factory reset/wipe, reboot, but to no avail; still stucked on CM bootscreen.
I then tried to flash CM11 by recovery sideloader. This goes to 100% and recovery says "Installing update", but nothing happens.
Is it supposed to install and finally reboot by itself, or should I do something?
I tried to installed zip from SD-card, but got "E:Can't mount /sdcard". I guess that means that I can't push the .zip over ADB to /sdcard
either.
What else can I try?
Edit: I wiped /data and then I could suddenly push the .zip to /data/media and the, finally flash the .zip from sdcard!
Why on earth the installer didn't wipe everything from the beginning, I don't get...
Did I miss anything obvious about the wiping thing?
A factory reset should do the trick normally. But if you ever get a message that you can't mount something you have to wipe that partition in recovery. I haven't used CWM in a long time. I prefer twrp as a recovery these days
Sent from my HTC One using XDA Premium 4 mobile app
Thanks, I'll remember that, should it ever happen again. What's the benefit for TWRP over CWM?
in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.
Ayman.y88 said:
in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.
Click to expand...
Click to collapse
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!
sblar said:
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!
Click to expand...
Click to collapse
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL
Ayman.y88 said:
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL
Click to expand...
Click to collapse
Post 2 implies op was able to flash the zip successfully after wiping /data.
Correct, and I could probably also have sideloaded after wiping /data...
I can't imagine what I'm doing wrong here. Steps I'm taking (rather circuitously I might add):
1) Odin back to stock 4.4.2
2) Root
3) Install SuperSU, Busybox, & SS 3.75
4) Reboot to recovery
5) Backup stock software
6) Reboot to recovery
7) Flash rom according to instructions
What happens is that it writes the data section, but not the system. So I'm left w/ no OS on the phone and have to Odin again to get it back up. After the initial backup (or even if I skip the backup), I get an error in SS "unable to mount /system"
I've searched high an low through the SS thread and so far have not been able to glean anything close to the problem I'm having. Is there something I'm doing wrong?
Could iy be your sd card?
janderfu said:
I can't imagine what I'm doing wrong here. Steps I'm taking (rather circuitously I might add):
1) Odin back to stock 4.4.2
2) Root
3) Install SuperSU, Busybox, & SS 3.75
4) Reboot to recovery
5) Backup stock software
6) Reboot to recovery
7) Flash rom according to instructions
What happens is that it writes the data section, but not the system. So I'm left w/ no OS on the phone and have to Odin again to get it back up. After the initial backup (or even if I skip the backup), I get an error in SS "unable to mount /system"
I've searched high an low through the SS thread and so far have not been able to glean anything close to the problem I'm having. Is there something I'm doing wrong?
Click to expand...
Click to collapse
I don't know if this would help but have you tried the process with a different SD card? I was having problems and thought it was something I did wrong but found out my scan disk 64gb micro SD card was the problem. Hope you get it working, good luck Janderfu
I tried that last night. Same result. For some reason I can read from the system partition, but not write to it.
some have reported issues where if you wipe system, it messes up the sd... if you are able to odin just fine, then when in SS, just do the factory data reset option to wipe and dont do the advance and wipe system.. then see if you are able to flash this way.. just make sure to do the factory reset like 3x to be safe and then flash..
see if that works.. also what version of SSare you using and what version are you on as in JB or KK... i see you say 3.75 up top, but to be sure you are on NC2/KK?
From my Fired-up Note Pro 12.2!
I'll give that a shot.
When I go back and Odin, it's going to NC2/KK. And yeah, the SS is 3.75.
janderfu said:
I tried that last night. Same result. For some reason I can read from the system partition, but not write to it.
Click to expand...
Click to collapse
I get a similar issue in trying to run init.d scripts. Several times a "can't mount root as read/write" error is shown. I'm interested to know if this is similar and how to approach as well. Thanks.
~Sent from my AT&T Samsung Galaxy Note 3 Badass~
janderfu said:
I'll give that a shot.
When I go back and Odin, it's going to NC2/KK. And yeah, the SS is 3.75.
Click to expand...
Click to collapse
Did it work with the factory rest without wiping the system in advanced wipe? If not than just to make sure that you are flashing the custom rom in one of the rom slots and not on the stock rom partition (just making sure because sometimes we make small mistakes as a noob).
Hi, I was running a MM rom for awhile and want to go back to 4.25.654.18 but I'm having issues. Flashing a stock rooted rom, the progress on the flash is really quick like it wasnt successful but it say it was and then wont boot. Is there something special needed for downgrading?
Edit: so I did an rug and system kept ferrying, some parts failed. Did boot though but with constant play services crashing. Had to disable. Tried sense 7 mm Rom, so t boot. Tried stock rooted Rom, won't boot. Is something wrong with the system partition somehow?
clavin78 said:
Hi, I was running a MM rom for awhile and want to go back to 4.25.654.18 but I'm having issues. Flashing a stock rooted rom, the progress on the flash is really quick like it wasnt successful but it say it was and then wont boot. Is there something special needed for downgrading?
Edit: so I did an rug and system kept ferrying, some parts failed. Did boot though but with constant play services crashing. Had to disable. Tried sense 7 mm Rom, so t boot. Tried stock rooted Rom, won't boot. Is something wrong with the system partition somehow?
Click to expand...
Click to collapse
Make a backup of your user apps ( titanium backup is fine), wipe system, boot, data and then install any rom.
If you still have problems, flash a RUU from fastboot(it will wipe entire memory)
RUU via zip wasnt restoring properly, though it could boot. Kept getting crashing on google apps and store and file managers couldnt find the internal storage. I ended up getting it back to GPE rom after awhile. I can't flash anything else and get it working. Not sure why.
clavin78 said:
RUU via zip wasnt restoring properly, though it could boot. Kept getting crashing on google apps and store and file managers couldnt find the internal storage. I ended up getting it back to GPE rom after awhile. I can't flash anything else and get it working. Not sure why.
Click to expand...
Click to collapse
What you mean RUU wasn't restoring properly? Did it give any errors?