E:unknown volume for path [sd-ext] help? - Samsung Galaxy Nexus

every time i go to wipe the dalvik cache this error comes up. its still able to wipe tho. i had aokp flashed and was dling a game when i decided to cancel the download and my phone stopped working. so i restarted it and it bootlooped. so i pulled the battery restarted it and saw this error for the first time. finally got back to my phone, rebooted, still saw it and my phone was acting slow so i restored it using cwm. then i decided to just wipe the phone clean and reflash everything from stock. i still see this error tho. what does it mean?

i would love to know this also, happens to me every time i wipe dalvik.

posted this on reddit and got this answer:
"It's nothing worth getting worried over, and no, you can't fix it. It's a carry-over from older devices (G1 and such) which had insufficient space on /data, so part of their sdcard was formatted using EXT. That space was then mounted as /sd-ext and apps could be installed there, though it was incredibly unstable and not recommended. Newer devices don't need this because they have large /data partitions, and can install apps onto the SD card with Android 2.2 and higher, natively. The /sd-ext wiping is just old code from those days that still exists in ClockworkMod Recovery and its derivatives.
tl;dr, don't worry about it, you can't do anything, it's just old crap from old phones."
so i think its ok, still worried about my phone freezing tho. oh well everythings working fine now if a little slow. but that may be all in my worried, first time flashing head.

Related

[Q] Stuck in recovery :(

Hi, I'm really hoping someone can help me. I've spent the last hour searching on here and although I've found lots of posts addressing similar issues to mine, I've not managed to solve it.
Before things went wrong I was running MoDaCo r5 without any issues. A2SD+ with an ext3 partition on the SD card (but no dalvik to sd). ClockworkMod recovery.
Decided to flash CyanogenMod 6.1.0 RC1 using ROM Manager. Downloaded it to the SD along with the Google apps, backed up my current ROM, wiped cache and data, installed CM... phone booted but then stuck on the CM boot screen for about 10 minutes. Did battery pull, rebooted, same thing. Tried several times more, no luck.
So booted into recovery and tried to restore my previous ROM. It goes through all the usual stuff then says its finished. Reboot. Stuck on the pink circle loading screen.
Wiped data, wiped cache, tried factory reset, clear storage.... Just gets stuck on the pink circle screen every time I reboot.
One thing I noticed - when I first boot into recovery (hboot screen) it briefly flashes up something about SD...Loading... No image (its too quick to read it all). Not sure if that means anything.
Also, at some point (I'm afraid I can't remember exactly when, but it was while I was doing something in recovery) it said something about 'not enough space on device', or something like that.
Sorry that's all a bit muddled - I thought I was more competent at all this stuff than I clearly am! PLEASE can someone help walk me through what I need to do to get things working again.
(I can't use adb with my computer - got into all sorts of problems trying to install/use it in the past, so if there's a solution that doesn't involve that it would be great. I have access to a Linux machine if that helps.)
UPDATE: After trying everything I could think of, I decided to try the nuclear option - Backed up everything on my SD card to my computer, then formatted it, copied the CM 6.1 zip back onto the SD and installed it, and it booted fine. Maybe had something to do with there not being enough space on the SD card? Does the ROM get unzipped onto the SD card during installation? If so I guess that could have been the sticking point as I only had about 250MB free!

Boot Loop - Fixed!

I have some sort of sd-ext error when restoring a nandroid backup. At the moment my phone is stuck at the cyanogen boot loop. I've wiped everything, i tried to format the sd-ext but it will not mount. i've tried fresh installs, everything I can think of but nothing seems to be working.
sd-ext error is normal, that's actually referring to the partition where you would install apps2sd, I get that error all the time because I don't have any as well and no need to have that partition.
In ClockworkMod Recovery, the sd card is just called "sdcard"
SynbiosVyse said:
sd-ext error is normal, that's actually referring to the partition where you would install apps2sd, I get that error all the time because I don't have any as well and no need to have that partition.
In ClockworkMod Recovery, the sd card is just called "sdcard"
Click to expand...
Click to collapse
Okay. So how do I go about getting my phone operational again? As I said i've wiped everything and tried to restore backups and did fresh installs and still am stuck at the looping boot screen.
You're using clockwork mod recovery right? Format your sd card using Windows to FAT32.
Boot into recovery..format all your other partitions. Mount USB storage, put a ROM in there, try stock Virtuous seems to be more stable than CM.
Clear data/factory reset, clear cache, then clear Dalvik cache. Install Virtuous .zip.
You should be able to boot. If you still can't try taking unmounting the sd card after the ROM finishes installing, try taking it out as well.
SynbiosVyse said:
You're using clockwork mod recovery right? Format your sd card using Windows to FAT32.
Boot into recovery..format all your other partitions. Mount USB storage, put a ROM in there, try stock Virtuous seems to be more stable than CM.
Clear data/factory reset, clear cache, then clear Dalvik cache. Install Virtuous .zip.
You should be able to boot. If you still can't try taking unmounting the sd card after the ROM finishes installing, try taking it out as well.
Click to expand...
Click to collapse
I got this error trying to install Virtious:
E:Can't chown/mod /data/app
(Operation not permitted)
E:Failure at line 8:
set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation Aborted.
Click to expand...
Click to collapse
I successfully installed the MIUI ROM however it doesn't even get to the boot screen. It stays on the white background HTC Incredible screen.
I saw this guy had a similar problem:
http://androidforums.com/incredible-all-things-root/181337-backup-problems-ud-cm6.html
He said that Cyanogen Mod seemed to be better for him. But he was also clearing data/cache and Dalvik AFTER he installed the mod.
It's ok to do that after, but you better make sure to do it before. Have you tried clearing both before and after? If it gets stuck on the white incredible screen I am not sure, but if it goes beyond that and then crashes right before the boot is finalized then that might be an SD card problem.
SynbiosVyse said:
I saw this guy had a similar problem:
http://androidforums.com/incredible-all-things-root/181337-backup-problems-ud-cm6.html
He said that Cyanogen Mod seemed to be better for him. But he was also clearing data/cache and Dalvik AFTER he installed the mod.
It's ok to do that after, but you better make sure to do it before. Have you tried clearing both before and after? If it gets stuck on the white incredible screen I am not sure, but if it goes beyond that and then crashes right before the boot is finalized then that might be an SD card problem.
Click to expand...
Click to collapse
Yes i've tried before and after. With cyanogen it loops the boot screen, with MIUI that I installed it doesn't get past the white screen and i cannot install virtuous at all
Anyone? I'd really like to be able to save $300 here
last loop i had with cyanogen was because i had the wrong kernel. make sure u flash a kernel that supports asop. its simple but it slips minds alot i usually use kings kernels (#2)
akawings said:
last loop i had with cyanogen was because i had the wrong kernel. make sure u flash a kernel that supports asop. its simple but it slips minds alot i usually use kings kernels (#2)
Click to expand...
Click to collapse
ive tried kings and ziggy's aosp
The phone is totally screwed up, it wont even accept unrooting and putting the stock ROM back onto it. I have *NO* idea what happened. I just got this phone replaced and did a restore and it was working fine, then it froze so i removed the battery and put it back in and then this.
http://androidforums.com/incredible...16-how-revert-back-earlier-version-hboot.html
try using that to unroot, itll take you back to 2.1 (or you could use a different ruu for whatever version youd like to revert to)
Fixed! I went out and bought a new class 6 SD card and used berserkers method to go back to stock. Thank all of you for your help!

[Q] Boot Loop...after memory card change?......Rooted Dinc

I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.
I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....
I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.
Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.
Worse case scenerio, wipe? and run apply CM from SD card?
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
SynbiosVyse said:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
Click to expand...
Click to collapse
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.
I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
SynbiosVyse said:
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
Click to expand...
Click to collapse
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....
---if worse case----
I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.
Are these steps close:
1. boot to recovery> ClockworkMod
2. select wipe data/factory reset
3. select wipe cache partition
4. select advanced> select wipe Dalvik cache?
5. install zip from SD card > select CM- 6.0.2
6. done?
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
SynbiosVyse said:
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
Click to expand...
Click to collapse
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still
repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still
SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
linuxmotion said:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....
Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.
See I'm not exactly sure that the SD card was what caused the malfunction in the first place.
If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.
You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.
You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
- what apps had you moved to SD card?
Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.
Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.
smtom said:
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
Click to expand...
Click to collapse
Correct.
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
Click to expand...
Click to collapse
I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...
- what apps had you moved to SD card?
Click to expand...
Click to collapse
you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....
------
Status as of 12/06/10 11:18am est.......Things I have done since last posts.
1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.
2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....
3. Tried to repeat step above...same results, now just initial screen, NO bootloop.
4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....
5. Wiped.
6. Installed Hboot 92. (upgraded from 77)
7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....
So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....
Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....
SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:
E: Can't chown/mod /data/app (operation not permitted)
E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation aborted.
I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.
1. I tried Skyraid_333 and had the same results. Locked on initial white screen.
2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html
It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....
3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."
It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....
I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....
I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......
Thanks to everyone who chimed in.
Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.
i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -
How it happened:
I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.
Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.
Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen
Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)
Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?
Here's to hoping.
Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.
I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.
IT'S WORKING!!!!!!!!!!!!!!!
Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.
So glad someone had gone though this before me.
AOSP interacts w/ SD
Handy information to know -
AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.
So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.
hth
i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro
anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason

Corrupted Data Parition

Hi Everyone,
My data partition got corrupted. I can no longer boot into any rom. When I try to factory reset, format data, or wipe internal; I get this error:
E:error opening '/data/media/0/Android/data/com.
E:error: I/O error
I tried manually deleteing the data folder, but I get the same error. Is there a way I can just completely format my internal storage and remove the data. Trying to do it inside TWRP v2.6.0.1 only gives me the above error.
Does anyone have any thoughts, ideas or suggestions?
Thanks
When you tried to format data in TWRP, what did you try?
If I'm not mistaken, mounting system and then formating system should wipe everything on your internal storage.
altimuh said:
When you tried to format data in TWRP, what did you try?
If I'm not mistaken, mounting system and then formating system should wipe everything on your internal storage.
Click to expand...
Click to collapse
I wish I knew earlier that System had to be mounted in order for everything to get wiped lol.
I'm back up and running, but it went through a long, arduous and slightly weird process to get there.
After several failed attempts at wiping my internal storage, I tried doing an Odin flash back to stock along with the sprint pit file for re-partitioning. After that, I could get past the initial boot "Galaxy Note 2" screen, I was able to get into the stock rom boot animation, but my phone would just endlessly reboot into the Sprint/Samsung boot animations. I then Odin'ed back the TWRP recovery. I tried to factory reset once again and surprisingly, I no longer received the I/O errors I was getting before. I decided to reflash Paranoid Android and everything booted up just fine.
The weird thing about all this though is that when I booted into the Rom, Literally everything was intact. I still had all my apps installed, my themes and launcher up, and all of my settings intact.
So after everything happened, nothing got deleted at all apparently. I was thinking of still going back and trying to truly format my internal storage to completely wipe it, but I am concerned that more issues would pop up.
Do you think it would be better for me just to wipe everything and start fresh?
mugenga said:
I wish I knew earlier that System had to be mounted in order for everything to get wiped lol.
I'm back up and running, but it went through a long, arduous and slightly weird process to get there.
After several failed attempts at wiping my internal storage, I tried doing an Odin flash back to stock along with the sprint pit file for re-partitioning. After that, I could get past the initial boot "Galaxy Note 2" screen, I was able to get into the stock rom boot animation, but my phone would just endlessly reboot into the Sprint/Samsung boot animations. I then Odin'ed back the TWRP recovery. I tried to factory reset once again and surprisingly, I no longer received the I/O errors I was getting before. I decided to reflash Paranoid Android and everything booted up just fine.
The weird thing about all this though is that when I booted into the Rom, Literally everything was intact. I still had all my apps installed, my themes and launcher up, and all of my settings intact.
So after everything happened, nothing got deleted at all apparently. I was thinking of still going back and trying to truly format my internal storage to completely wipe it, but I am concerned that more issues would pop up.
Do you think it would be better for me just to wipe everything and start fresh?
Click to expand...
Click to collapse
Back up your internal storage to your computer and then wipe it clean and start over. I always feel that best results come from a clean start.

Two repeating problems and factory reset doesn't solved

Hey,
I was using WanamLite 4.3 ROM with Android 4.3 and MJ5 bootloader. No backups.
And after a friend of mine broke my SD slot (long story), my phone started to reboot and unmount the SD card, then it broke up completely and I can't use a SD card anymore. So, I kept using my phone without it, until one day it rebooted and when it came back I lost all Deezer syncronized musics, Evernote notes, SMS and things like that. The other day, it reboot again and now it was like a factory reset, I lost all configs and just the installed apps and pictures wasn't lost.
But my phone was crazy, home button not working, no notifications, status bar not working and lots of other things, then I opened the Downloads app and I received an error and then everything came back to normal, really strange, but I started to receive two annoying errors:
The process com.google.process.gapps has stopped.
The process android.process.media has stopped
And anything related to Google or media was useable, and they kept appearing while I pressed ok.
So, I did a mega wipe (script found here, can't post links) and installed a 4.4 Rom (PhoeniX ROM), but, guess what, received a "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.", hit "I'm feeling lucky" button and my two friends started to annoy me to hell again.
What can I do? I thought on doing a Kies factory reset but I'm scared of bricking my phone (it tells me to use Kies 3, btw), my phone is unuseable. :crying:
(Edit: Just noticed you said you mega wiped...)
So how about flashing kitkat through odin? Sammobile.com
EmptyArea said:
(Edit: Just noticed you said you mega wiped...)
So how about flashing kitkat through odin? Sammobile.com
Click to expand...
Click to collapse
Yeah, I'll try that, but I don't have much hope, is there a way to do a "deeper" wipe, that totally deletes any ROM, then I install that from nothing.
You'll lose all data but you should wipe
/system, /data (factory reset), /cache and dalvik cache. I have also once found an internal storage (/sdcard) necessary.
What I would do to fix all the problems,
Using TWRP recovery, I format disk and wipe everything can be wiped. (Ofc you'll lose ALL the data on the phone, which might be the problem as you don't have an SD card, unless after wipe you know how to transfer files from PC while in recovery) This is the best wipe you would get IMO. Then install a very stable rom like ARHD or omega rom . Or DN3
Sent from my GT-N7100
Mohammed779 said:
What I would do to fix all the problems,
Using TWRP recovery, I format disk and wipe everything can be wiped. (Ofc you'll lose ALL the data on the phone, which might be the problem as you don't have an SD card, unless after wipe you know how to transfer files from PC while in recovery) This is the best wipe you would get IMO. Then install a very stable rom like ARHD or omega rom . Or DN3
Sent from my GT-N7100
Click to expand...
Click to collapse
THANK YOU!!!!!
It worked, I never used TWRP, really awesome. I was getting errors when trying to format system, so I went to config and select the option to use rm -f instead of formatting, and after that work, I formatted everything and installed DN3. Thanks a lot, really!

Categories

Resources