Related
For some reason unknown to me, CWM only see's my internal storage. Also, when I try to Wipe Dalvik Cache, it gives an error:
E: unknown volume for path [/sd-ext].
I am wondering if maybe this is maybe causing some sort of issue even though I wipe everything three times...
Yarbo said:
For some reason unknown to me, CWM only see's my internal storage. Also, when I try to Wipe Dalvik Cache, it gives an error:
E: unknown volume for path [/sd-ext].
I am wondering if maybe this is maybe causing some sort of issue even though I wipe everything three times...
Click to expand...
Click to collapse
ive had this same "issue" with it only seeing internal storage not sure what caused this all of a sudden, if anyone can clarify it would be much appreciated from the both of us.
Projectdwnshft said:
ive had this same "issue" with it only seeing internal storage not sure what caused this all of a sudden, if anyone can clarify it would be much appreciated from the both of us.
Click to expand...
Click to collapse
I am starting to think this causes some serious issues with roms that I install - cause I am betting that it is not properly wiping the internal storage....
Yarbo said:
I am starting to think this causes some serious issues with roms that I install - cause I am betting that it is not properly wiping the internal storage....
Click to expand...
Click to collapse
I wouldn't sweat it. I've had this issue as long as I can remember flashing on my note (a whole two months) and it hasn't caused any issues that I've noticed. If it's a good release, mine works the same as everyone's. Same with a buggy release, same bugs as everyone else. The sd-ext issue when formatting dalvik cache hasn't caused any (extra) bugs for me.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I would use TWRP instead of CWM.
Did you try to fix permissions though in CWM?
I did try to fix permissions, and it said it succeeded, but still hasn't resolved the problem.
I'm not sure if it's an issue per se, based on one of the above posters. But it is annoying none-the-less, so if someone knows a way to fix this I'd be much obliged.
Also, what is TWRP?
Yarbo said:
I did try to fix permissions, and it said it succeeded, but still hasn't resolved the problem.
I'm not sure if it's an issue per se, based on one of the above posters. But it is annoying none-the-less, so if someone knows a way to fix this I'd be much obliged.
Also, what is TWRP?
Click to expand...
Click to collapse
The best way I can think of twrp is its cwm except for a lot more functionality with a more friendly user interface. You can flash it via goo manager app in play store which will overwrite your cwm as your active recovery.
As far as the card is concerned, I would start by...
Backing up w/e before starting
Plug into PC via in phone or memory card reader. All that is important is that your PC can see it.
Use the windows built in diskpart utility to clean it partition it and format it.
Let me know if you need the diskpart syntax, its from command line.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
lmike6453 said:
The best way I can think of twrp is its cwm except for a lot more functionality with a more friendly user interface. You can flash it via goo manager app in play store which will overwrite your cwm as your active recovery.
As far as the card is concerned, I would start by...
Backing up w/e before starting
Plug into PC via in phone or memory card reader. All that is important is that your PC can see it.
Use the windows built in diskpart utility to clean it partition it and format it.
Let me know if you need the diskpart syntax, its from command line.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I can't just select the internal storage from Windows explorer, right click on it and select "Format"?
Yarbo said:
I can't just select the internal storage from Windows explorer, right click on it and select "Format"?
Click to expand...
Click to collapse
You can try, that might do the trick but if not try diskpart.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
lmike6453 said:
You can try, that might do the trick but if not try diskpart.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I assume that doing this will leave CWM so that I can re-install CM10?
Is CWM stored on some other storage then internal storage? Some other memory chip or something?
I'm having this issue with CWM too, it's kind of driving me nuts cause it used to see both cards just fine before, and I don't like filling up my internal card with all my roms & radios. I'm kind of scared to use TWRP again though after what happened with my GSII. In short- I have reason to believe TWRP bricked my phone. I had just gotten my Note & was getting my GSII ready to sell(clearing data, formatting storage, etc). I booted into TWRP(which I'd been using for months, so it wasn't user error) & did a factory reset there too just to be safe. It seemed to work fine & gave me the "rebooting" message, and then.... nothing. Black screen. No boot, no recovery, no download mode, no signs of life whatsoever. I had to send it to Samsung to be fixed.
Now, it could have just been coincidental timing, but I'm now understandably hesitant to use TWRP again. Has this happened to anyone else? Sorry to hijack the thread.
In CWM, have you guys tried to mount sd card.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
There's an issue with the External SD listing coming up under the root emmc folder, rather than under Internal. Have y'all checked there for your External SD? This applies to CWM and TWRP.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I was about to post this issue, and I'm glad you beat me to it.
Was getting ready to Nandroid and flash a new ROM, but now got a new issue to deal with.
There's an issue with the External SD listing coming up under the root emmc folder, rather than under Internal. Have y'all checked there for your External SD? This applies to CWM and TWRP.
Click to expand...
Click to collapse
Nope, it comes up under "Internal".
Hello everyone,
I had previously rooted my original evo a while back and recently got the new evo lte, and thought "Oh I can root this all by myself." Big mistake
Okay, so, I made sure to unlock it using the HTC dev. Then downloaded Rom Manager and tried to put the new cm10 rom but for some reason it was coming up with sd errors. So, I looked up what could possibly be the cause behind that, which I thought was the previous Rom Manager data from the old evo. So I deleted it and well had the same problem. I also made sure to do the Hboot fastboot thing too.
Then I download the TWRP recovery and things took a turn for the worst. Now my external/internal storage is unreadable to twrp, ironically so, I can still use the USB for the sd.
I tried other roms, but it won't load them
Now, my os is gone and I just don't know what to do. At very least I can still use fastboot, but I really just unsure how I can well make it work.
so stat wise it says
tampered/unlocked
S-ON RL
Hboot 1.15
Radio 1.05.11.0606
OpenDSP-v25. 1.032.0405
I am also running a mac.
So, if anyone can set me in the right direction, that would be super.
For one reason or another some users have problems flashing cmx and corrupting internal. Boot to twrp and mount as USB then format it in OSX.
om4 said:
For one reason or another some users have problems flashing cmx and corrupting internal. Boot to twrp and mount as USB then format it in OSX.
Click to expand...
Click to collapse
Thank you for replying. So I want to mount the internal storage and format it in Fat32?
Also, when I go to the mounting menu, it will not let me press "Mount Internal".
However, I can mount internal storage using USB storage method, I don't get it...
Selecting mount as usb storage is all you need to do, at the very least you should be able to do that, then format, fat 32 is the default so there is no need to specify fat 32
Format the top one, correct?
Sorry for the late reply, that should be it
No, Thank you.
So, I did reformat. It still cannot find the internal storage/SD storage.
So, can I push RUU through fastboot to return it to a functional state. All this for Jellybean, haha
I had almost the same thing happen to me over the weekend for the first time. I was about to reformat it in twrp and that worked great for me. So give that a try before you run a ruu
Sent from my EVO running cm10
ewalk4866 said:
I had almost the same thing happen to me over the weekend for the first time. I was about to reformat it in twrp and that worked great for me. So give that a try before you run a ruu
Sent from my EVO running cm10
Click to expand...
Click to collapse
I already reformat the internal and it made no different. I also cannot reformat within twrp, it just says cannot find and fails.
I think I've misunderstood, if you reformatted and can not access memory from aosp Rom try flashing the sd rewrite fix
swap internal/external links
om4 said:
I think I've misunderstood, if you reformatted and can not access memory from aosp Rom try flashing the sd rewrite fix
swap internal/external links
Click to expand...
Click to collapse
No no, I apologize. This is all terribly confusing.
So I will just fastboot it through terminal
/fastboot-mac flash zip blablah.zip
right?
No this is flashed through recovery
arts aaverse
om4 said:
No this is flashed through recovery
Click to expand...
Click to collapse
I don't know exactly know how I am going to do that, since the recovery does not recognized the internal/external storage. When I mounted via USB and put the zip on there, I cannot find it within the recovery.
Odd, after reformatting you should be able to use the internal again
om4 said:
Odd, after reformatting you should be able to use the internal again
Click to expand...
Click to collapse
Yes. Sadly I don't think reformatting did anything. At this point, I am unsure what to do. Can I even still flash a RUU?
rentiyl said:
Yes. Sadly I don't think reformatting did anything. At this point, I am unsure what to do. Can I even still flash a RUU?
Click to expand...
Click to collapse
I'm coming into this late but I recently experienced corrupted internal storage while running cmx as well. While I could not choose to mount the external storage, I somehow was able to select that bubble when in the restore menu. I restored an old meanrom and it rebuilt the internal storage despite losing the data. Not sure if this info will help you at all, but figured I would share. Good luck.
Sent from my EVO using xda premium
gmugrad04 said:
I'm coming into this late but I recently experienced corrupted internal storage while running cmx as well. While I could not choose to mount the external storage, I somehow was able to select that bubble when in the restore menu. I restored an old meanrom and it rebuilt the internal storage despite losing the data. Not sure if this info will help you at all, but figured I would share. Good luck.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No, thank you for input. Sadly, since this a very new phone, I have nothing to restore it to. As, I was unable to make a back up for this all happened. But I am sure if I did have one it would get me out of this rut.
rentiyl said:
No, thank you for input. Sadly, since this a very new phone, I have nothing to restore it to. As, I was unable to make a back up for this all happened. But I am sure if I did have one it would get me out of this rut.
Click to expand...
Click to collapse
So when you flash a new rom from twrp, what happens? Are you flashing the kernel beforehand too since you are s-on?
Sent from my EVO using xda premium
gmugrad04 said:
So when you flash a new rom from twrp, what happens? Are you flashing the kernel beforehand too since you are s-on?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
When I was able to flash a new rom [as I am now unable to really access my sd card] it would install it, however, it would boot past the the splash screen and would go black. I didn't think I had to flash the kernel before hand, perhaps that was my problem.
I just returned my phone to stock using ODIN and Entropy's method. I was previously running SHOStock3v.1.3.5 and was having problems creating a viable backup via CWM; not sure why, I've backed up many times before. What changed recently is that I set the default backup format to "TAR" from "DUP" as mentioned here. After that, my backups went from around 17MB to 1.6GB. At some point, possibly even with that first backup, the process would hang while generating the .md5. I left it for about 1.5 hours one time and still it wouldn't finish; I got around this by holding the power button to reboot. I reset the default format back to "DUP" and my backup size went back to about 17MB, but still wouldn't finish generating the .md5. All of these backups seemed to be causing System Media Storage some severe heartburn, filling up the internal memory. Deleting the backups solved this issue, but I was left with a phone that I could not backup.
Finally, this morning I (regrettably) used ROM Manager to try backing up, not having seen the numerous posts about never using ROM Manager. So my phone became a brick, stuck in a bootloop at the Samsung logo. So now I'm at the point where I've returned the phone to stock w/root as mentioned above. I've also reflashed recovery-clockwork-5.0.2.3-galaxys2att.tar via ODIN. BUT, when I try to flash a new ROM I get an error message saying "E:Can't mount /emmc/".
I've looked at some similar threads like this one and this one, but they don't seem to contain the answers I need. I am about to attempt to wipe the sdcard using the dialer code *2767*3855# found in this post. Before I do that I want to verify that there isn't something less drastic that I could try first. Anybody know what's going on?
Eh sounds like you may have gotten the emmc brick.
Sent from my SGH-I777 using xda app-developers app
Shawn said:
Eh sounds like you may have gotten the emmc brick.
Click to expand...
Click to collapse
Yuck. I did some research on that and it sounds mostly like what I've got (I have the ICS kernel - version 2.6.35.7). The difference between my situation and the one in a post I found is that my phone boots and acts normal, for the most part. I ran GotBrickbug? v1.2 and it verified that my eMMC chip is known to have the bug. I found a discussion thread for the Epic 4G on the subject which points to this fix, but it seems to be for those whose phones are really bricked... mine is not, do you have any suggestions on what I might try?
Well, the problem that caused it was in Samsung kernel source for ICS. Flash a custom kernel known not to have it and see what you get afterwards. Also, DO NOT do any memory wipes while on the stock kernel because then you will for sure get the bug, that's what causes it.
Sent from my SGH-I777 using xda app-developers app
I resolved my issue, though it wasn't what I thought out was. For some reason when I selected "Choose zip from internal sdcard", CWM was trying to access the external sdcard, which I had pulled. The opposite was true as well. If my external card was in its slot I would have realized the switch around right away. My phone its back in business, I now have SHOstock3 installed and it's running just fine. Thanks for the help, really glad my emmc wasn't mangled!
Sent from my SGH-I777 using xda app-developers app
Hmm, not sure why it would try and read from external. Anyway, glad you got it up and running again!
Sent from my SGH-I777 using xda app-developers app
Shawn said:
Hmm, not sure why it would try and read from external. Anyway, glad you got it up and running again!
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Because he didn't coat the one that said internal
Sent from Zanpakuto using Getsuga Tensho!
If it happens again flash the latest siyah kernel. I've had that happen to me many times and I like cried the first time because I thought I destroyed my phone and would have to use my halfway broken captivate again haha siyah is my lifesaver
Sent from my SGH-I777 using xda app-developers app
Thanks. Yeah, I downloaded Ktoonsez NEAK kernel, but decided to flash a jelly bean rom/kernel instead. After I flashed I was able to data wipe and factory reset and reflash for a clean install.
Sent from my SGH-I777 using xda app-developers app
Thanks!!!
Just downloaded and will give it a test drive!!!
i777
bellino13 said:
I resolved my issue, though it wasn't what I thought out was. For some reason when I selected "Choose zip from internal sdcard", CWM was trying to access the external sdcard, which I had pulled. The opposite was true as well. If my external card was in its slot I would have realized the switch around right away. My phone its back in business, I now have SHOstock3 installed and it's running just fine. Thanks for the help, really glad my emmc wasn't mangled!
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Same to my Phone
So if want to solve this problem, you must have one external SD card which conten Zip file. Right?
hoanvnu said:
Same to my Phone
So if want to solve this problem, you must have one external SD card which conten Zip file. Right?
Click to expand...
Click to collapse
Not necessarily. You can put the zip file on the internal card, then you have to choose external card from within CWM. You may have to have an external card installed for that option to show up though. Or, if you put the zip on the external card, then you choose internal in CWM.
I have a T-mobile HTC Amaze running Android Revolution with 4ext recovery. Recently my phone lost cell signal and would not pick it up again. I tried wiping data/cache/dalvik and reinstalling the Android Revolution ROM but the problem is still there. After reinstalling the ROM twice the wifi won't turn on and just says ERROR. I tried going back into 4ext and now it started to give me an error "can't mount /internal_sdcard" when trying to choose zip from sdcard.
Anyone has any idea what's going on?
Thanks
AwayFromReality said:
I have a T-mobile HTC Amaze running Android Revolution with 4ext recovery. Recently my phone lost cell signal and would not pick it up again. I tried wiping data/cache/dalvik and reinstalling the Android Revolution ROM but the problem is still there. After reinstalling the ROM twice the wifi won't turn on and just says ERROR. I tried going back into 4ext and now it started to give me an error "can't mount /internal_sdcard" when trying to choose zip from sdcard.
Anyone has any idea what's going on?
Thanks
Click to expand...
Click to collapse
Ok dude I think I know what's going on, then outlook doesn't look too bright either. It looks like your internal sd became corrupted and now it can't mount. So back up your internal sd, reformat, and put your stuff back in and see if it helps.
If that doesn't help I guess you just had a bad luck Brian moment. This internal sd problem happened to me twice already.
For the wifi error, that's probably because you dirty flashed ARHD over a perfectly fond ARHD. You should have just airplane mod'd it for a while or rebooted. When you wipe the cache don't dirty flash the entire rom for one simple problem. When you reboot after you wipe the cache, it just takes a minute to rebuild the 'blocks. '
Sent from my HTC_Amaze_4G using Tapatalk 2
SuperAfnan said:
Ok dude I think I know what's going on, then outlook doesn't look too bright either. It looks like your internal sd became corrupted and now it can't mount. So back up your internal sd, reformat, and put your stuff back in and see if it helps.
If that doesn't help I guess you just had a bad luck Brian moment. This internal sd problem happened to me twice already.
For the wifi error, that's probably because you dirty flashed ARHD over a perfectly fond ARHD. You should have just airplane mod'd it for a while or rebooted. When you wipe the cache don't dirty flash the entire rom for one simple problem. When you reboot after you wipe the cache, it just takes a minute to rebuild the 'blocks. '
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Well when I connect the phone via usb, it shows up on my computer but none of the files I had show up in the drive, including the zip for the ROM. I most likely lost all my stuff but that's okay. How do I reformat my internal sd at this point?
I tried to do a clean install of ARHD by doing a complete format inside 4ext, maybe something went wrong along the way. So If I can get my internal sd to work, can I format data/cache/dalvik and reinstall the rom? will that fix the problem?
Thanks for your help
AwayFromReality said:
Well when I connect the phone via usb, it shows up on my computer but none of the files I had show up in the drive, including the zip for the ROM. I most likely lost all my stuff but that's okay. How do I reformat my internal sd at this point?
I tried to do a clean install of ARHD by doing a complete format inside 4ext, maybe something went wrong along the way. So If I can get my internal sd to work, can I format data/cache/dalvik and reinstall the rom? will that fix the problem?
Thanks for your help
Click to expand...
Click to collapse
Ok the way to format the internal sd is in 4ext. I remember it being somewhere in the wipe section. Choose format sd then internal sd.
Here's a tip when flashing, use format all partitions except sd. This is better than wiping cache then dalvik then data. This method clears of everything but it doesn't touch your sd. This is how to comoletely clean install roms without errors in flashing.
And if after you flash it and see no bars, T-mobile is probably having a bad connection or doing renovations to their towers or something.
Sent from my HTC_Amaze_4G using Tapatalk 2
SuperAfnan said:
Ok the way to format the internal sd is in 4ext. I remember it being somewhere in the wipe section. Choose format sd then internal sd.
Here's a tip when flashing, use format all partitions except sd. This is better than wiping cache then dalvik then data. This method clears of everything but it doesn't touch your sd. This is how to comoletely clean install roms without errors in flashing.
And if after you flash it and see no bars, T-mobile is probably having a bad connection or doing renovations to their towers or something.
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot for your help man. Formatting the internal sd worked. Installed ARHD and everything works perfectly. I'll remember to format all partitions except sd from now on.
AwayFromReality said:
Thanks a lot for your help man. Formatting the internal sd worked. Installed ARHD and everything works perfectly. I'll remember to format all partitions except sd from now on.
Click to expand...
Click to collapse
I'm glad I could help! And I appreciate you pressing thanks, :thumbup: more people need to stop being arrogant and actually use it, because many people WILL get annoyed and not help people in the future since they gain nothing from it.
Sent from my HTC_Amaze_4G using Tapatalk 2
It will come back, one day. I have a same problem, too
Sent from my HTC One X+ using xda premium
SuperAfnan said:
I'm glad I could help! And I appreciate you pressing thanks, :thumbup: more people need to stop being arrogant and actually use it, because many people WILL get annoyed and not help people in the future since they gain nothing from it.
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Since you're giving out free advice, pressing thanks is the least I could do.
eadrang said:
It will come back, one day. I have a same problem, too
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Do you mean the internal_sd problem will come back? If so what do you think is the root cause?
AwayFromReality said:
Since you're giving out free advice, pressing thanks is the least I could do.
Do you mean the internal_sd problem will come back? If so what do you think is the root cause?
Click to expand...
Click to collapse
No, i don't. I think the cause is the quality of internal not good, and during use that fone, i format it so much.
Sent from my HTC One X+ using xda premium
eadrang said:
No, i don't. I think the cause is the quality of internal not good, and during use that fone, i format it so much.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
The amaze has a wacky internal sd I think, in general. Mine got corrupted twice in its life in my ownership. Who knows what journeys my Amaze had been through with the previous owner(s).
Sent from my HTC_Amaze_4G using Tapatalk 2
I was trying to flash jellybomb rom and keep getting this error in
twrp recovery
Unable to mount '/usbstorage
Any one have a solution?
im getting the same issue with trying to bump up from m13 to m15 wont change baseband version or software version.
onemanruler said:
im getting the same issue with trying to bump up from m13 to m15 wont change baseband version or software version.
Click to expand...
Click to collapse
Same here with any rom it seems, even when doing a wipe of any kind.
Im going to try a older version of TWRP, smells like the recovery isnt right in some way, not the roms.
svghost said:
Same here with any rom it seems, even when doing a wipe of any kind.
Im going to try a older version of TWRP, smells like the recovery isnt right in some way, not the roms.
Click to expand...
Click to collapse
Found the fix for it. I followed one of the posts from chain fire who was referred to this method by someone I believe. (I apologize if I'm not giving credit to who referred)
1.Turn phone off
2. Remove sd card
3. Flash mi5 stock recovery( you can find a link in the general form in the let's figure this out guys forum on page 7 or so)
4. Keep sd card out while you boot the phone back up.
5. Update to new mj4
Hope this helps. I take no credit for this I just sumerized the genius devs of this forum who I have come to love since I found this place on my s3. Thanks devs
Sent from my SM-N900P using xda app-developers app
cocaineblunts said:
I was trying to flash jellybomb rom and keep getting this error in
twrp recovery
Unable to mount '/usbstorage
Any one have a solution?
Click to expand...
Click to collapse
Folks, this is NOT an error. It's support for OTG USB storage. Disregard unless you're using a USB OTG adapter and a USB Thumbdrive. Confirmed with the devs. (Which is where this question should have been posted)
Compusmurf said:
Folks, this is NOT an error. It's support for OTG USB storage. Disregard unless you're using a USB OTG adapter and a USB Thumbdrive. Confirmed with the devs. (Which is where this question should have been posted)
Click to expand...
Click to collapse
No this is an error.. It fails to install the rom and the only explanation at the end of the log is Unable to mount USBSTORAGE.. Whether it has anything to do with usbstorage or not that is the error we are getting. I am also getting this error. I wipe everything, go to install a rom and it fails.. I can nandroid back to my stock but that is about all I can do aside from flash some mods.
And for the record.. he's trying to get help and Troubleshoot which is the topic of this portion of the forum so I think it's perfectly placed..
xsisbest said:
No this is an error.. It fails to install the rom and the only explanation at the end of the log is Unable to mount USBSTORAGE.. Whether it has anything to do with usbstorage or not that is the error we are getting. I am also getting this error. I wipe everything, go to install a rom and it fails.. I can nandroid back to my stock but that is about all I can do aside from flash some mods.
And for the record.. he's trying to get help and Troubleshoot which is the topic of this portion of the forum so I think it's perfectly placed..
Click to expand...
Click to collapse
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
The one thing I haven't done is wipe internal .. I was afraid of losing some stuff on my internal card.. I'll back anything up and give it a go. Thank you so much for your help and recommendation! I'll let you know how it goes.. I gotta download Jellybomb again as I tried moving it to my sdcard in recovery and it seems to have disappeared somehow.. . Thanks again!
xsisbest said:
The one thing I haven't done is wipe internal .. I was afraid of losing some stuff on my internal card.. I'll back anything up and give it a go. Thank you so much for your help and recommendation! I'll let you know how it goes.. I gotta download Jellybomb again as I tried moving it to my sdcard in recovery and it seems to have disappeared somehow.. . Thanks again!
Click to expand...
Click to collapse
Sure thing,if somebody that has MJ4 with passwords sticking can do a factory reset then TWRP back up their system partition and post it I may be able to make a zip that fixes this issue. Of course this is exactly what freeza did I am sure so it may not work but I could give it a try. I will pull system from the girlfriends phone but she is on a plane and gone for the weekend so it may be next week before I can get hers.
ifly4vamerica said:
Sure thing,if somebody that has MJ4 with passwords sticking can do a factory reset then TWRP back up their system partition and post it I may be able to make a zip that fixes this issue. Of course this is exactly what freeza did I am sure so it may not work but I could give it a try. I will pull system from the girlfriends phone but she is on a plane and gone for the weekend so it may be next week before I can get hers.
Click to expand...
Click to collapse
So I put the rom on my card, rebooted, wiped ONLY cache and dalvik and flashed the rom and it worked.. lol. This is what is called a dirty flash coming from the Evo LTE.. I would never have done this lol.. But if it works whatever lol. Thanks again for the recommendation. It actually installs more like a theme than a rom. Always interesting to learn the changes from phone to phone. Excited to see what's to come!
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
thank you kind sir.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
Tried this, still get the error, at least on the Tmobile Note 3.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
Did ya have the backup on your external? If I'm reading this right, you wiped your internal storage. I've yet to successfully get a clean backup onto my external. It sounds like this could come in very handy, I just want to make sure I understand the steps in case I want to use this. Thanks, bro.
Sent from my Nexus 7 using Xparent BlueTapatalk 2
micmars said:
Did ya have the backup on your external? If I'm reading this right, you wiped your internal storage. I've yet to successfully get a clean backup onto my external. It sounds like this could come in very handy, I just want to make sure I understand the steps in case I want to use this. Thanks, bro.
Sent from my Nexus 7 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yep had the backup on external. When this happened to me it was after taking the OTA to MJ4. Basically I had odined to full stock, factory reset and wiped internal. Then I removed external SD. Rebooted and took the MJ4 update. After this I flashed TWRP before CF auto root, this took me to an endless boot loop. I couldn't flash anything and anything I tried to run in Odin failed. So I wiped everything again, formatted system and data, tossed in the external SD and restored a nan droid. Presto I was back in business. I think having twrp flashed before cf auto root may have been the culprit. After I restored the nan droid I reran cf first then twrp. Since then no issues at all. In fact I have restored several nan droids from external and have had no problems.
Those nan droids were only of system, data and boot. I am using the latest TWRP with a scan disk 64gb external. I can't remember if it is formatted NTFS or fat32.... I will have to check that for you if you need the info. I am pretty sure it is NTFS but I did have it formatted fat32 for a while so like I said I will have to check that to be sure.
Break.....
In reply to the other post, if you have a T-Mobile version I would try the efs partition restore. I don't have the link anymore but it is in xda forum somewhere, if you search or ask around somebody is bound to know what thread it is in.
Last thing to try is wiping in recovery first then if the flash fails just reboot back to recovery with the twrp menu. Then don't wipe and try the flash again.
I have kind of jumped around a bit with the explanation and couple more things to try, hopefully it makes sense.
Note 3 or Gear Sent
ifly4vamerica said:
Yep had the backup on external. When this happened to me it was after taking the OTA to MJ4. Basically I had odined to full stock, factory reset and wiped internal. Then I removed external SD. Rebooted and took the MJ4 update. After this I flashed TWRP before CF auto root, this took me to an endless boot loop. I couldn't flash anything and anything I tried to run in Odin failed. So I wiped everything again, formatted system and data, tossed in the external SD and restored a nan droid. Presto I was back in business. I think having twrp flashed before cf auto root may have been the culprit. After I restored the nan droid I reran cf first then twrp. Since then no issues at all. In fact I have restored several nan droids from external and have had no problems.
Those nan droids were only of system, data and boot. I am using the latest TWRP with a scan disk 64gb external. I can't remember if it is formatted NTFS or fat32.... I will have to check that for you if you need the info. I am pretty sure it is NTFS but I did have it formatted fat32 for a while so like I said I will have to check that to be sure.
Break.....
In reply to the other post, if you have a T-Mobile version I would try the efs partition restore. I don't have the link anymore but it is in xda forum somewhere, if you search or ask around somebody is bound to know what thread it is in.
Last thing to try is wiping in recovery first then if the flash fails just reboot back to recovery with the twrp menu. Then don't wipe and try the flash again.
I have kind of jumped around a bit with the explanation and couple more things to try, hopefully it makes sense.
Note 3 or Gear Sent
Click to expand...
Click to collapse
I believe that the T-Mobile efs partition fix works great on this phone, if it's the miracle zip to which you are referring (small zip file labeled brick bootloop fix after restoring backup, or something to that effect).
The external SD card I'm using is only 16 GB (yeah, I know), so definitely not a problem with the way it's formatted (it's the one I had on my E4GT). It just fails on backup. I may try it again sometime, but just got tired of that red fail message.
Your explanation is clear and useful.
FWIW, I believe that boot, system and data comprise a complete backup, unless the efs gets fried. Also, I think that you may be right, that the TWRP then autoroot may have been the culprit, but back in business is way awesome (pain while in the mire, though).
In preparation for KitKat, I think a large external SD card is my next purchase, along with a complete wiping of internal, clean start and all.
Thanks for the info. Very helpful.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I believe that the T-Mobile efs partition fix works great on this phone, if it's the miracle zip to which you are referring (small zip file labeled brick bootloop fix after restoring backup, or something to that effect).
The external SD card I'm using is only 16 GB (yeah, I know), so definitely not a problem with the way it's formatted (it's the one I had on my E4GT). It just fails on backup. I may try it again sometime, but just got tired of that red fail message.
Your explanation is clear and useful.
FWIW, I believe that boot, system and data comprise a complete backup, unless the efs gets fried. Also, I think that you may be right, that the TWRP then autoroot may have been the culprit, but back in business is way awesome (pain while in the mire, though).
In preparation for KitKat, I think a large external SD card is my next purchase, along with a complete wiping of internal, clean start and all.
Thanks for the info. Very helpful.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I'm sure the 64gb cards are much cheaper now. I think I got mine on amazon for like 50 over a year ago.
Every time I want to do a "clean" install I format the internal memory. I usually have backups of apps/data/rom on the sd card which makes using mybackup pro awesome to restore apps/data. But for whatever reason I am having trouble using mybackup with this phone..
So I've kinda been chillen on freezas rom / kernel waiting for development to increase more (it's coming along great)
Sent from my SM-N900P using Tapatalk
tt281gt said:
I'm sure the 64gb cards are much cheaper now. I think I got mine on amazon for like 50 over a year ago.
Every time I want to do a "clean" install I format the internal memory. I usually have backups of apps/data/rom on the sd card which makes using mybackup pro awesome to restore apps/data. But for whatever reason I am having trouble using mybackup with this phone..
So I've kinda been chillen on freezas rom / kernel waiting for development to increase more (it's coming along great)
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Been running that rom for quite a long time.
Yeah, I was looking at prices for 64 GB cards. Prices look quite good.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I have run into this same problem. This is my first time tyring to flash on my note 3 and when I wipe or try to flash the rom I get the error that it is unable to mount usbstorage. I don't fully understand how you fixed this? Is there a stock image I need to flash?
Also a friend of my said that there is an issue with doing restores on the note 3, that it causes a bootloop. Is this true? It's the first I've heard of it
mike208 said:
I have run into this same problem. This is my first time tyring to flash on my note 3 and when I wipe or try to flash the rom I get the error that it is unable to mount usbstorage. I don't fully understand how you fixed this? Is there a stock image I need to flash?
Also a friend of my said that there is an issue with doing restores on the note 3, that it causes a bootloop. Is this true? It's the first I've heard of it
Click to expand...
Click to collapse
I have personally been switching back and forth between maximus ROM and AOSP and have had no issues with restoring backups through TWRP. As far as the unable to mount USB storage error I believe everyone gets that but it has never caused me an issue with flashing a ROM. It is looking for a mass storage device if I am correct. Sometimes after I do a factory reset I rebbot twrp back into recovery before I flash a new ROM and have not had any issues. Someone please chime in if you know better than I.
Hope this helps in some way.
Sent from my SM-N900P using Tapatalk
mhutton said:
I have personally been switching back and forth between maximus ROM and AOSP and have had no issues with restoring backups through TWRP. As far as the unable to mount USB storage error I believe everyone gets that but it has never caused me an issue with flashing a ROM. It is looking for a mass storage device if I am correct. Sometimes after I do a factory reset I rebbot twrp back into recovery before I flash a new ROM and have not had any issues. Someone please chime in if you know better than I.
Hope this helps in some way.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Not sure if it affected the wip or not, but I got that error pretty quick during the flash. I don't see how the rom could have flashed in under 10 seconds, so I do think it is affecting it from flashing and possibly wiping. Thanks for the info about the restore though