Related
I have just bought an 8GB card and need to swop everything across from my 4GB. I'm rooted with apps2sd and MCR ROM installed.
Now the questions are:
What is the best way of doing this the right way?
Do i need to partition the new card, or does MCR do this i cant remember!
If i drag and drop everything from my 4GB to my 8GB will it work?
Will it pick
Anyone else had to do this?
Any help will be very much apreciated...
Just been thinking if i install the modded recovery image on my new card will i be able to create partitions with that?
I take it no one has done this then?
are you using windows or linux? for windows, make a backup of your apps with some app on your phone. mcr3.0 contains "backup", which should do the job. after that copy everything from the old sdcard to the new one, which you already partitioned according to your needs. it is probably best to do this from recovery image or in an external card reader. after that restore your apps and you're done.
if you are using linux you can skip the backing up of apps, just copy everything from the two partitions you have on your sdcard (one ext2/3/4, one fat32) to the according partitions on the new card and you're done.
Cool thank you i will try that.
kendong2 said:
are you using windows or linux? for windows, make a backup of your apps with some app on your phone. mcr3.0 contains "backup", which should do the job. after that copy everything from the old sdcard to the new one, which you already partitioned according to your needs. it is probably best to do this from recovery image or in an external card reader. after that restore your apps and you're done.
if you are using linux you can skip the backing up of apps, just copy everything from the two partitions you have on your sdcard (one ext2/3/4, one fat32) to the according partitions on the new card and you're done.
Click to expand...
Click to collapse
Where is backup on MCR3.0?
Goose247 said:
Where is backup on MCR3.0?
Click to expand...
Click to collapse
in the menu?
kendong2 said:
in the menu?
Click to expand...
Click to collapse
I can't see anything in menu/apps or anything else that looks like backup
Goose247 said:
I can't see anything in menu/apps or anything else that looks like backup
Click to expand...
Click to collapse
ok, i am seriously confused now. there was this app called "backup for root users". my understanding was, that it was renamed "backup" on paul's request, and was then included in modaco's custom rom. so far i can not find it in the zip of 3.0... so i guess i got something mixed up there, i apologise.
anyway, you can download it from the market.
edit: phew, i am not crazy
http://android.modaco.com/content-p...-featuring-wavesecure/page/1520/#entry1089440
Every time I try to update su or backup by nandroid, they all say Md5sum fail
Idk what's wrong
Sent from my SGH-T989 with Cyanogenmod 7.
Either your memory card or device is damaged (i.e. has bad blocks), or your recovery has a bug. I would ask in the thread/forum for your specific device, to see if anyone else using the same version/type of recovery also has the problem.
if you are an advanced user, I could suggest a zero-fill on the NAND using dd. E.g:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 conv=fsync
...make sure you use the correct blockname for your device/partition though otherwise you could brick. And I don't know what buffersize the device can handle, halve it to 8 if it crashes out. Still, don't know if it's a problem with internal NAND or microSD. Or if your device even uses microSD. Again, best posting in your device forum.
Yes I got a new microsdcard 16 gb SanDisk today from best buy, could this be it?
Sent from my SGH-T989 with Cyanogenmod 7.
ArcticFish said:
Yes I got a new microsdcard 16 gb SanDisk today from best buy, could this be it?
Sent from my SGH-T989 with Cyanogenmod 7.
Click to expand...
Click to collapse
It could be, do you have an older or different microSD just to test on? Maybe you just need to format the SD. But trying a different one will help to single-out the problem. Sometimes microSD cards get errors and you can't avoid it, especially if you pull the battery out while using the phone or the phone crashes/reboots.
Well I have my old one I used, 256 mb SanDisk microsdcard, but it never had enough memory to back up completly
Could it be maybe some necessary memory was in it? Also I never formated the new microsdcard so ill do that
Sent from my SGH-T989 with Cyanogenmod 7.
ArcticFish said:
Well I have my old one I used, 256 mb SanDisk microsdcard, but it never had enough memory to back up completly
Click to expand...
Click to collapse
Fair enough. Does your recovery have an "advanced backup" option? That way you could just chose to backup "cache" which should fit, then try restoring it.
ArcticFish said:
Could it be maybe some necessary memory was in it? Also I never formated the new microsdcard so ill do that
Click to expand...
Click to collapse
It shouldn't, no. Usually the included memory card just has some included photo's and maybe some maps, nothing important.
Make sure you format it as FAT32, it should be the default. If you are formatting in the computer anyway.
What if I format my new sd card in Cwm how do I do that?
Also if I wanted to do the advanced back up for my old sd card, I just restore the cache or back up and then restore
Srry I'm a noob at this but in trying to learn all this
Sent from my SGH-T989 with Cyanogenmod 7.
I was thinking about just factory reseting phone to get the ics update and then rerooting, would this fix it
I'm also gonna backup the apps and the data using titanium backup
Sent from my SGH-T989 with Cyanogenmod 7.
ArcticFish said:
I was thinking about just factory reseting phone to get the ics update and then rerooting, would this fix it
I'm also gonna backup the apps and the data using titanium backup
Sent from my SGH-T989 with Cyanogenmod 7.
Click to expand...
Click to collapse
Maybe just try re-rooting. You are getting this error in Recovery, yes? It might be a bug with recovery, or a damaged sdCard I really don't know.
Ok ill try that, thx for ur help
Sent from my SGH-T989 with Cyanogenmod 7.
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.
Yesterday night I was running the Viper ROM and decided to switch and try out a Sense 5 port. I booted to TWRP and wiped cache, dalvik cache, data, and system. I then tried to flash the Sense 5 port which failed. I tried to restore a backup and it failed. And now my sdcard/internal is not mounting so I'm at a complete loss. Any ideas on how I could get my phone back to a functional state?
At least it isn't 'bricked' if you can still get to recovery which is good. Bricked is 100% dead which yours doesn't sound like it is. If you are able to get to recovery, are you jus notable to get to the external SD? Can you access the SD directly from a PC? If so, maybe copy what you can, format and copy back..try to mount again..
dc.wash95 said:
Yesterday night I was running the Viper ROM and decided to switch and try out a Sense 5 port. I booted to TWRP and wiped cache, dalvik cache, data, and system. I then tried to flash the Sense 5 port which failed. I tried to restore a backup and it failed. And now my sdcard/internal is not mounting so I'm at a complete loss. Any ideas on how I could get my phone back to a functional state?
Click to expand...
Click to collapse
What version of TWRP are you on?
Sent from my EVO using xda premium
FinZ28 said:
What version of TWRP are you on?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I'm running 2.5.0.0
dc.wash95 said:
I'm running 2.5.0.0
Click to expand...
Click to collapse
Take a look at this:
http://forum.xda-developers.com/showthread.php?t=2354029
If you're on Hboot 1.12 or you're S-off you can disregard flashing the boot.img (kernel) separately.
I've never run across the issue where storage wouldn't mount, but the fix posted in the thread above seems to have worked for at least one person. Just make sure you back everything up to your computer before you start formatting anything.
Sent from my EVO using xda premium
Well, I could'nt access any storage on my phone through twrp or usb mounting and was getting the errors that this guy is showing here
http://forum.xda-developers.com/showthread.php?t=2354029
I just wiped internal storage and was able to get a ROM to successfully flash so I lost all my photos/vids but at least my phones working now...
Do you know why this error might have come up in the first place?
dc.wash95 said:
Well, I could'nt access any storage on my phone through twrp or usb mounting and was getting the errors that this guy is showing here
http://forum.xda-developers.com/showthread.php?t=2354029
I just wiped internal storage and was able to get a ROM to successfully flash so I lost all my photos/vids but at least my phones working now...
Do you know why this error might have come up in the first place?
Click to expand...
Click to collapse
Honestly, I've never run across the problem myself but I see it fairly regularly in these forums. I don't know what causes it, either. It's at least part of the reason I keep things like TWRP backups, ROM's, photos and so on stored on my external SD card. If there is ever an issue I can remove the card from my phone and copy files over to my computer, if the need arises (I also keep at least one recent Nandroid on my computer in case I run into problems along the way).
Sent from my EVO using xda premium
FinZ28 said:
Honestly, I've never run across the problem myself but I see it fairly regularly in these forums. I don't know what causes it, either. It's at least part of the reason I keep things like TWRP backups, ROM's, photos and so on stored on my external SD card. If there is ever an issue I can remove the card from my phone and copy files over to my computer, if the need arises (I also keep at least one recent Nandroid on my computer in case I run into problems along the way).
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This is great advice and good practice^
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
FinZ28 said:
Honestly, I've never run across the problem myself but I see it fairly regularly in these forums. I don't know what causes it, either. It's at least part of the reason I keep things like TWRP backups, ROM's, photos and so on stored on my external SD card. If there is ever an issue I can remove the card from my phone and copy files over to my computer, if the need arises (I also keep at least one recent Nandroid on my computer in case I run into problems along the way).
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Well I'll be adopting your gameplan as insurance if this thing happens again...thanks for the help everyone!
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