Good Morning All...
I'll try to provide as much relevant information as possible while being concise. That being said, let me know if I need to provide addition information.
Basics
Computer OS: Mac + Windows 7 VM and a Windows 7 dedicated machine.
Phone: HTC EVO 4G LTE
Carrier: Sprint
Current ROM: CM10-20120904-NIGHTLY-jewel
Goal
To restore "normal" flashing functionality (detailed below) so I can restore to stock.
Details
My first issue with this phone started on the 4.0.x version of Android that came with the phone. The phone would frequently reboot, at which point it would indicate an error report could be sent to HTC. I sent these faithfully for several weeks. Then an update for the phone was released and I updated OTA. This did not solve the rebooting issue.
At that point, I grew frustrated and decided I would root the phone and install CM10 in the hopes the rebooting issue would be resolved. I rooted the phone with S-ON using the method outlined on HTVEVOHacks.
I was able to push TWRP to the phone and then proceeded to download and install CM10 via Clockwork. After installing Clockwork, I installed Clockwork recovery (I had worked with it previously on my EVO 4G, and wasn't familiar with TWRP) and tried to install CM10. This failed and I pushed TWRP once more and booted into the phone.
I then installed GooManager, at which point I downloaded and successfully installed CM10. This is essentially where I'm at now.
Issues
I've had several issues with CM10, including the phone rebooting (still), and have decided I would like to restore to stock. The issues outlined below comprise all of the trouble I've experienced and is currently impeding my progress:
If I flash a ROM other than the CM10 backup I have, or MIUI, it sits in boot spinning indefinitely (>25-minutes). I've cleared the fastboot cache, as well as the dalvik/cache in an attempt to boot it properly. I've tried MeanROM and a few other Sense-based ROMS (inc. stock-rooted ROMs).
If I try to run the RUU (I've tried several versions), it gets to the point where the HTC logo appears in silver, and then the RUU tells me I have the wrong version.
MIUI proved to be a very poor choice, as I was inundated with error after error (com.phone.android).
If I restore the stock recovery, and perform an oemlock, the bootloader shows 'Tampered - Relocked - Security Warning'.
When in TWRP, any time I try to wipe cache/factory reset, it gives an error: "E:failed to mount /sdcard (Invalid argument)". This appears numerous times throughout the TWRP log (which I can copy to SD, but I can't mount to USB).
At this point, I'd like to be able to take it back to Sprint as I believe the rebooting to be an issue with the phone, but I need to be able to restore back to stock, if possible.
I know this is a long post, but being an engineer, I like to make sure I do as much footwork as possible prior to asking for help. If there are any steps I haven't taken that I should have, please tell me and I'll be happy to do it.
Any help that can be provided is welcome.
Regards,
JadoJodo
Sounds like you need to fast boot flash a sense kernel before flashing a sense ROM.
I'll admit I didn't read all your post but you should check out the thread named " don't panic"
All your answers should be there
Sent from my EVO using xda app-developers app
corcgaigh said:
Sounds like you need to fast boot flash a sense kernel before flashing a sense ROM.
I'll admit I didn't read all your post but you should check out the thread named " don't panic"
All your answers should be there
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I had taken a look at that yesterday and didn't see a guide that matched my issues specifically, but having looked at it again today, I see some relevant info. My question: Where do I get a Sense-based kernel to flash? Is there a specific one I should flash?
JadoJodo
Having reviewed the "Don't Panic" guide by om4, I attempted to solve the sdcard mount issue by reformatting in TWRP. I get the following error:
Code:
* Verifying filesystems...
* Verifying partition sizes...
E:failed to mount /sdcard (Invalid argument)
E:failed to mount /sdcard (Invalid argument)
E:failed to mount /sdcard (Invalid argument)
E:Unable to open ums lunfule 'sys/class/android_usb/android0/f_mass_sto
Using rm -rf on '/dev/block/mmcblk0p38'
E: tw_format_rmfr: unable to locate volume for device "/dev/block/mmcblk0
Mount twrp to pc and reformat
om4 said:
Mount twrp to pc and reformat
Click to expand...
Click to collapse
Thanks for the reply, om4!
I was able to mount the Internal Storage to my PC and format. Once this was done, I found it could be mounted in TWRP, however, using the 'Wipe' function in TWRP to wipe 'Internal Storage' still fails. I am unsure if this functionality is normal, but I can access the Internal Storage when mounted via Windows now.
I am reformatting System, Cache, Dalvik, and reinstalling CM10 once more to test functionality...
Related
Hoping for some assistance in troubleshooting here, successfully rooted my phone and attempted to flash voodoo using the methods described in the following thread:
HOW TO: Root, Install Clockwork, Safely Remove Bloatware, Integrate Google
To my knowledge everything worked as described until I attempted to install voodoo. Upon doing so the phone booted very quickly back into what appeared to be the stock kernel/system. I lost my superuser.apk application but still retained the su and busybox files on my sd card. I have cwmod installed and can access it but the voodoo install appeared to have failed.
My problem is that I believe the device is still rooted, because when I launch adb shell it presents a # prompt, but when I attempt to perform a factory reset (I would like to start the whole process over) the procedure errors out with the message that partitioning failed and E:Can't mount /dev/block/mmcblk0p1 (Invalid argument).
I've tried the fix permissions and format SD card options within CW recovery without any luck (the only result is that now I don't seem able to install any apps; the phone believes there is no space). I also attempted to use Odin to restore factory kernel/system status but the problem persists. My goal right now is to get everything back to factory and start all over, any advice would be much appreciated.
Voodoo definitely failed and your MBR is messed up now. (Invalid argument)
Please use the voodoo uninstall in the OP of this thread to remove the damage.
You can then make another attempt at installing the voodoo kernel if you wish.
Will do so shortly, appreciate the quick response
This corrected my problem. Thank you for the referral PhoenixPath, and thank you adrynalyne for taking the time to put this together for us mouth breathers
help.
wont boot past cwm recovery window on the internal card
reflashing to the cm-7-team-b-beta1-signed.zip does not remedy it
recovery window has errors
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
should i try the unbuntu fix ?
i know nothing about adb and or drivers for android devices btw... so unless the guide is VERY detailed im boned
maxxcool7421 said:
help.
wont boot past cwm recovery window on the internal card
reflashing to the cm-7-team-b-beta1-signed.zip does not remedy it
recovery window has errors
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
should i try the unbuntu fix ?
i know nothing about adb and or drivers for android devices btw... so unless the guide is VERY detailed im boned
Click to expand...
Click to collapse
Thats how my tablet got fixed, use the ubuntu method and let me know if you have troubles flashing it I'll be glad to help you, I've done it 3 times lol
megaghostgamer said:
Thats how my tablet got fixed, use the ubuntu method and let me know if you have troubles flashing it I'll be glad to help you, I've done it 3 times lol
Click to expand...
Click to collapse
No dice, hangs on "writting zeros's to ml0" ... i see a alternative method that does the same thing... guess i will try it..
maxxcool7421 said:
No dice, hangs on "writting zeros's to ml0" ... i see a alternative method that does the same thing... guess i will try it..
Click to expand...
Click to collapse
What SD Card do you have and what class? Sorry I fell asleep but im back on. Also what GB Tablet do you have and what are you running? Can you still boot up and is there anywhere you can get to factory reset ( clear data ) cause thats whats looking like your problem. I had that problem on my HTC Hero CDMA I freaked and then I cleared data and rebooted back into recovery and error was gone
megaghostgamer said:
What SD Card do you have and what class? Sorry I fell asleep but im back on. Also what GB Tablet do you have and what are you running? Can you still boot up and is there anywhere you can get to factory reset ( clear data ) cause thats whats looking like your problem. I had that problem on my HTC Hero CDMA I freaked and then I cleared data and rebooted back into recovery and error was gone
Click to expand...
Click to collapse
I did the exact same thing with rom manager on the NT. :< There should be big flashing warning signs that say "DONT DO THIS IF YOU'RE TIRED"
I wound up having to ADB to the device, completely wipe the partition table with gdisk, then rebuild it. However, the scripts to acutally format it werent avaliable anymore (Dropbox account was banned) so I then had to use the Ubuntu restore method to go from there.
I did loose the ability to run the B&N Factory ROM (wont pass registration anymore)
but at least the tablet is useable.
Dont give up, from what I understand, unless you physically BREAK the tablet in some way, its nearly always recoverable!
lag0matic said:
I did the exact same thing with rom manager on the NT. :< There should be big flashing warning signs that say "DONT DO THIS IF YOU'RE TIRED"
I wound up having to ADB to the device, completely wipe the partition table with gdisk, then rebuild it. However, the scripts to acutally format it werent avaliable anymore (Dropbox account was banned) so I then had to use the Ubuntu restore method to go from there.
I did loose the ability to run the B&N Factory ROM (wont pass registration anymore)
but at least the tablet is useable.
Dont give up, from what I understand, unless you physically BREAK the tablet in some way, its nearly always recoverable!
Click to expand...
Click to collapse
Yup true! To pass sign up, http://www.youtube.com/watch?v=sAASnHPn4PM&feature=youtu.be by albert wertz.
megaghostgamer said:
What SD Card do you have and what class? Sorry I fell asleep but im back on. Also what GB Tablet do you have and what are you running? Can you still boot up and is there anywhere you can get to factory reset ( clear data ) cause thats whats looking like your problem. I had that problem on my HTC Hero CDMA I freaked and then I cleared data and rebooted back into recovery and error was gone
Click to expand...
Click to collapse
Ha! maybe im not that dumb after all. although the ubunut failed, the tool here worked http://forum.xda-developers.com/showthread.php?t=1663836 but /slap! forhead/ i still have the cym recovery img on the unit ... so i think i will try this:
go back and set up the SD cm7 alpah boot that worked to boot the SD
boot in and update rom manager
install stock recovery img
then try the new link again!
as for the stick:
Sandisk - its pretty generic and came with my htc glacier...
16 bg nook table
it came with 1.4.1 image
put on cm-7-b-teamb-signed
installed few apps, *tried* to start installing gapps to get gplay and the google framework
then i got a splat
then i flashed it back again
seemed ok
it wasnt
it locked up
powered down
reboot = duuurp
after that i did not READ... booted into recovery and selected (wait for it) reset.. and cleared the user data.
after that i swore enough to get people to come to my office and look concerned... took advil... read.... cried... threatened...
now im here
maxxcool7421 said:
Ha! maybe im not that dumb after all. although the ubunut failed, the tool here worked http://forum.xda-developers.com/showthread.php?t=1663836 but /slap! forhead/ i still have the cym recovery img on the unit ... so i think i will try this:
go back and set up the SD cm7 alpah boot that worked to boot the SD
boot in and update rom manager
install stock recovery img
then try the new link again!
as for the stick:
Sandisk - its pretty generic and came with my htc glacier...
16 bg nook table
it came with 1.4.1 image
put on cm-7-b-teamb-signed
installed few apps, *tried* to start installing gapps to get gplay and the google framework
then i got a splat
then i flashed it back again
seemed ok
it wasnt
it locked up
powered down
reboot = duuurp
after that i did not READ... booted into recovery and selected (wait for it) reset.. and cleared the user data.
after that i swore enough to get people to come to my office and look concerned... took advil... read.... cried... threatened...
now im here
Click to expand...
Click to collapse
Personally. I wouldnt mess with Rom Manager. That's what bricked my tablet, too.
Just make an SD card with the CWM bootables (I posted a link in your other post about noob questions) and install roms/etc from there.
I think that's what's killing my gnex!
*This Jedi master be a Ninj-ESS*
hrm i missed it? (the other thead link to bootable cym)? i did try to repartition once on another bootable build but the cym did not like it... even after reinserting it
i had that problem before because i accidently formatted the 1gb user partition while in cm7...
this link saved me. try it out!
http://forum.xda-developers.com/showthread.php?t=1513583
still bricked. *tried* to use rom manager to install the "stock recovery" but it still boots to a "cardboard box".......
starting to think the partitions are whacked...
what is the best partition recovery guide ??
looking at this link...
http://forum.xda-developers.com/showpost.php?p=22157605&postcount=25
but the bootable cwm is not loading...grr
If I am correct you are still trying all of this from inside a bootable cm7 card, right?
Instead, try this http://forum.xda-developers.com/showthread.php?p=25786947
With that hopefully you can get a bootable cwm recovery image.
From there you should be able to install CM7.
I CANNOT STRESS ENOUGH. DO NOT USE ROM MANAGER.
I honestly think it is most of your problems
Sent from my Nook Tablet using xda app-developers app
lag0matic said:
If I am correct you are still trying all of this from inside a bootable cm7 card, right?
Instead, try this http://forum.xda-developers.com/showthread.php?p=25786947
With that hopefully you can get a bootable cwm recovery image.
From there you should be able to install CM7.
I CANNOT STRESS ENOUGH. DO NOT USE ROM MANAGER.
I honestly think it is most of your problems
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
i think i am ready to agree about rom manager... will try the link in a sec.. thanks
not to sound entirely stupid... should i use the 8-16gig recovery? or the 16gig recovery? :silly::silly::silly:
16 gig. Assuming you have a 16gig NT!
Sent from my Nook Tablet using xda app-developers app
maxxcool7421 said:
not to sound entirely stupid... should i use the 8-16gig recovery? or the 16gig recovery? :silly::silly::silly:
Click to expand...
Click to collapse
meh, balls out, lets go 8-16 1st
!!! ok got into recovery console ....
maxxcool7421 said:
!!! ok got into recovery console ....
Click to expand...
Click to collapse
now looking up how to use then connect via adb and run these commands... http://forum.xda-developers.com/showpost.php?p=22157605&postcount=25
Hi guys,
As the title said, Galaxy Player 5.0 Wifi got soft-bricked during the flash process. Now, it stucks at the loading screen with the samsung text only. I can still get to the Recevery and Downloading mode but up till now I have tried flash many stock ROM, factory reset without hope. I believe that it's the software conflicting problem or problem with the bootloader
Please help me with this, my friend ask me to flash it to Cyanogen Mod 9 and I bricked his player. That's really bad for both of us. Before any thingies, it run on Froyo and on the back cover, it said YP-G70CW/ Made in CHina
Please help me with this soon ( any suggestion is appreciated
Hello my friend!I will say again:
ALWAYS WHATEVER IS HAPPENING,BEFORE FLASHING A NEW ROM YOU MUST BACKUP THE CURRENT SYSTEM FROM CWM!!!
If you have this,you may go to back-up and restore in CWM,restore and vouala you have again your current rom.
If you have not made a system Back-Up (also Nandroid backup) you will have to download a new rom,send it to your device in downloading mode and then install this.
I can suggest you the ROM CM9 that I use because its just awesome.Just a little prob with the preloaded microSD card.
What device do you have?INTL or USA?
Actually, I'm having the .zip file of CM9 from this topic as well : http://forum.xda-developers.com/showthread.php?t=1679957
However, even though I can connect my phone to the computer, use ODIN to root it and flash the .zip file after factory reset, etc. , the situation is still the same :-< It stay stuck at the samsung logo like forever
I believe I'm using an Intl one because it has hot physical home button. However, the back cover read: YP-G70CW Made in China. Therefore, I don't know which ROM should I flash??
do you follow ALL the instructions from this thread?
baladev said:
do you follow ALL the instructions from this thread?
Click to expand...
Click to collapse
I did. I did the factory reset and deleted cache, etc. before installing the .zip file. :-<
did you do this in CMR:
Wipe data/factory reset
wipe cache and wipe dalvik cache
?
To wipe dalvic cache go to advanced section in CWM
dimosthenisK said:
To wipe dalvic cache go to advanced section in CWM
Click to expand...
Click to collapse
yes, i meant CWM, mistyped it..
I did them all too. However, for the Dalivik cache, it does not show up text at all, just a little flash nothing changes. What seems to be wrong here is that every time I finish an action, it show up 4 line of errors like: can't mount to cache/..../recovery.log. Is that the problem??
Yes thats the problem.You may have locked the internal SD...Try formatting you external SD and then pass your zip again,this may fix the problem
If system can't mount it's files,there is no way it will load.
I took the external SD card out, formatted it and flashed the CM9 again. No luck
The four lines of error read like below, they keep appearing every time I do something:
E:Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
tranvutk said:
I did them all too. However, for the Dalivik cache, it does not show up text at all, just a little flash nothing changes. What seems to be wrong here is that every time I finish an action, it show up 4 line of errors like: can't mount to cache/..../recovery.log. Is that the problem??
Click to expand...
Click to collapse
Those errors are common within using CWM for the Galaxy Player 5. If you rebooted the device, it will most likely go away. There is no need for concern.
When I'm on the old CM10.1 ROM, my Rezound detects and connects to my house's wifi and other wifi sources with [seemingly] no problem, and I can access the web pages on chrome when I'm connected to wifi on the old CM10.1 ROM. However, when I flashed to CM10.1.2, and I'm on the starting set up page, trying to connect to a wifi, no wifi source ever pops up, even when my house's wifi is on and there are usually 1-2 other wifi sources in my area that should also pop up. I wait for over 10 minutes, and still no wifi source appears on the starting set up page for cm10.1.2. Additionally, now, when I'm on the old CM10.1 ROM, I can't download any updates or new apps from the play store at all. I was able to download google drive on my rezound only a week ago.
Anyways, the recovery I use is AMON RA-VIGOR-v3.16, and I noticed in amon ra that when I try "Wipe ALL data/factory reset", I get this:
Wipe ALL userdata
Press Power to confirm,
any other key to about.
Formatting DATA:...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
Skipping format of /sd-ext.
Userdata wipe complete!
And that's it. What does this mean? just a couple days ago was the first time I flashed a new ROM on my Rezound for a month, and I think this "error mounting internal_sdcard/.android_secure" started when I flashed the first new ROM in a month. Is there anyway to fix this error and problem? I would really like to keep my Rezound and not have to buy a new phone... I would be happy to provide additional information if it would help solve this problem.
urstinky said:
When I'm on the old CM10.1 ROM, my Rezound detects and connects to my house's wifi and other wifi sources with [seemingly] no problem, and I can access the web pages on chrome when I'm connected to wifi on the old CM10.1 ROM. However, when I flashed to CM10.1.2, and I'm on the starting set up page, trying to connect to a wifi, no wifi source ever pops up, even when my house's wifi is on and there are usually 1-2 other wifi sources in my area that should also pop up. I wait for over 10 minutes, and still no wifi source appears on the starting set up page for cm10.1.2. Additionally, now, when I'm on the old CM10.1 ROM, I can't download any updates or new apps from the play store at all. I was able to download google drive on my rezound only a week ago.
Anyways, the recovery I use is AMON RA-VIGOR-v3.16, and I noticed in amon ra that when I try "Wipe ALL data/factory reset", I get this:
Wipe ALL userdata
Press Power to confirm,
any other key to about.
Formatting DATA:...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
Skipping format of /sd-ext.
Userdata wipe complete!
And that's it. What does this mean? just a couple days ago was the first time I flashed a new ROM on my Rezound for a month, and I think this "error mounting internal_sdcard/.android_secure" started when I flashed the first new ROM in a month. Is there anyway to fix this error and problem? I would really like to keep my Rezound and not have to buy a new phone... I would be happy to provide additional information if it would help solve this problem.
Click to expand...
Click to collapse
try switching to twrp and erasing in that recovery, you can switch back to amon ra right after that if you want to http://forum.xda-developers.com/showthread.php?t=1902381
most mounting errors are fixed by either switching to a different recovery to reformat/partition the partitions (amon ra is a bit outdated, i used it in the past and and got mounting errors to. mostly after RUU and tried to install a ROM right away)
they can be fixed by running the RUU again, if you still get mounting error in amon ra after the RUU than all you have to do is reboot into the stock ROM and unmount and erase the sdcard in the storage settings than go back to recovery and it should be fixed
bunchies said:
try switching to twrp and erasing in that recovery, you can switch back to amon ra right after that if you want to http://forum.xda-developers.com/showthread.php?t=1902381
most mounting errors are fixed by either switching to a different recovery to reformat/partition the partitions (amon ra is a bit outdated, i used it in the past and and got mounting errors to. mostly after RUU and tried to install a ROM right away)
they can be fixed by running the RUU again, if you still get mounting error in amon ra after the RUU than all you have to do is reboot into the stock ROM and unmount and erase the sdcard in the storage settings than go back to recovery and it should be fixed
Click to expand...
Click to collapse
Thank you, bunchies. I never heard of TWRP prior to your response, so I appreciate it. I flashed TWRP version 2.6.0.0 with no problem and did the standard wipe first, which gave me an error and said it failed to wipe. So I went to the advanced settings in wipe and checked all tick boxes except the 'wipe ext sd' check box, and it was successful! I did it 2 more times to try to make sure it was successful. I decided to try to install the July 12 2013 build of CM10.1.2, and then the GSM patch and gapps, but it came out with the same problem of not recognizing any wifi sources within the vicinity like 2 days ago. When I downloaded CM10.1.2 2 days ago, I made sure to check its md5 sum, and it was equal to the one provided. Then I modified it by replacing its mms.apk, copied the resulting ROM to my rezound's root, and checked each others md5 sums, which where again equal. So I flashed amon ra v3.16 again and wiped everything and this time I didn't encounter ANY mounting error. I NAND restored my old back up of cm10.1 and tried to download google drive from google play....but it didn't work again...The error message I get in google play is this:
"Google Drive" could not be downloaded due to an error. (Error retrieving information from server. [RPC:S-5:AEC-0])
When I try to download Rezound Prox Sensor Calibrator, the same exact error message pops up (except inside the quotation marks in Rezound Prox Sensor Calibrator). And still, browsing the web on google chrome works like it should.... what can I do next to try to fix my rezound?
*edit* nevermind about the google play store problem. I went to settings>apps>all, cleared the cache of "google play store" and force stopped it, and cleared the data of both "google play services" and "google services framework" and force stopped both (though I've read that I probably don't have to do all that to google play services). I rebooted and for some reason, I can download and update from google play again. The problem of wifi not ever being recognized for me after I flash to the July 12 2013 build of CM10.1.2 still exists, though.
urstinky said:
So I flashed amon ra v3.16 again and wiped everything and this time I didn't encounter ANY mounting error. I NAND restored my old back up of cm10.1
Click to expand...
Click to collapse
Was this nand backup made during the time of mounting error, or during the time of the wifi problem?
the DATA folder may be corrupted in some way, i have had an issue before where i had a problem with my current rom than did a nand backup of just my data folder because the data folder holds things like apps/setting and other stuff which i didnt want to loose in my new flash but something in there can be corrupted. but after i would re-install the rom and did a nand restore of the DATA folder i would get the same issue in the new flash.
so if you did something like that it could be messing with your wifi
if you did something like that and you have time maybe just do a Nand backup of what you have now. than factory reset/wipe boot/data/system/caches and install the rom again without restoring anything and see if the wifi works as intended
if that makes any sense.. :silly:
bunchies said:
Was this nand backup made during the time of mounting error, or during the time of the wifi problem?
the DATA folder may be corrupted in some way, i have had an issue before where i had a problem with my current rom than did a nand backup of just my data folder because the data folder holds things like apps/setting and other stuff which i didnt want to loose in my new flash but something in there can be corrupted. but after i would re-install the rom and did a nand restore of the DATA folder i would get the same issue in the new flash.
so if you did something like that it could be messing with your wifi
if you did something like that and you have time maybe just do a Nand backup of what you have now. than factory reset/wipe boot/data/system/caches and install the rom again without restoring anything and see if the wifi works as intended
if that makes any sense.. :silly:
Click to expand...
Click to collapse
The nand backup I'm using right now was a backup I saved over a month ago (in June 6). The nand backup I made 2 days ago I think was corrupted (though i don't remember what it did anymore...I didn't think it was important at the time...), so I deleted it. In any case, every time I flashed the new rom, I never nand restored the "DATA" part. I didn't even know you can do that! Is DATA also where all text messages are saved? Anyways...nope, I haven't been nand restoring DATA after flashing the new ROM. I even tried flashing CM10.1.2 by itself without the gapps and gsm patch, but it still didn't recognize any wifi in the area.
urstinky said:
The nand backup I'm using right now was a backup I saved over a month ago (in June 6). The nand backup I made 2 days ago I think was corrupted (though i don't remember what it did anymore...I didn't think it was important at the time...), so I deleted it. In any case, every time I flashed the new rom, I never nand restored the "DATA" part. I didn't even know you can do that! Is DATA also where all text messages are saved? Anyways...nope, I haven't been nand restoring DATA after flashing the new ROM. I even tried flashing CM10.1.2 by itself without the gapps and gsm patch, but it still didn't recognize any wifi in the area.
Click to expand...
Click to collapse
Yeah data holds just about everything user end. this guy is having WiFi problems on 10.1.2 to http://forum.xda-developers.com/showthread.php?p=43605690
Just an observation
Edit: if a clean flash of ROM/gapps didn't work it could either be the ROM has a broken driver or hardware. Could be something els to but not sure, you can keep an eye on that thread to see if he gets his problem fixed if you want
Sent from my ADR6425LVW using xda app-developers app
Was the problem pinned down or resolved? I'm on an SIII, but experiencing a very similar problem.
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
alexounet2 said:
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
Click to expand...
Click to collapse
Hey i had this issue and finally pinned it down to the TWRP I was using. It turns Official TWRP has this issue. This can easily be resolved if u flash Squid's TWRP
Download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
That was the problem apparently. Thank you!
Thank you! I was having this problem as well and that fixed it.
Thanks very much for your help!!!
I was scared of loosing my phone...
Thanks.
I have a US Cellular XT1526 and was unable to install GApps on CM13 without this. CM13 installed fine, and GApps looked like it installed, but on reboot nothing was there; GApps failed to install. Using Squid's TWRP fixed it; thanks!
ayush rao said:
hey i had this issue and finally pinned it down to the twrp i was using. It turns official twrp has this issue. This can easily be resolved if u flash squid's twrp
download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Click to expand...
Click to collapse
thank you so much :d
thank you buddy.....
my mother is using Motorola E 2nd gen LTE and i flashed it with cyanogenmod 13 used officialTWRP recovery... and i faced the same problem. thank you very much for your answer and also the other guy for asking the question.
Should I select boot or recovery as partition when flashing this img
cannot restore system mounted read only