Related
Hey all,
I've got a SL101 with a sku of c10. I know that for most things the slider is pretty similar to the TF101. I've tried
out a few of the posts around here involving flashing a stock rom via nvflash to get rid of this annoying encryption.
Yes, I know, it's terrible, but the job I was at required it regardless. Problem I'm having is that non of the tools/advice
I've been able to find have had any useful results. I searched around for a working method for the slider, but I wasn't
able to find much. The slider goes into apx mode fine, pc knows its there (using the naked drivers posted here on xda),
but any time I try to send a command via nvflash it disconnects the slider and fails out with the 0x4 code. Maybe I'm
just missing it here on the forums, but does anyone have any clear information on how to go about this for the slider?
Appreciate any help.
IIRC NVFlash does not work for the Slider.
A factory reset should get rid of the encryption.
CWM cannot mount /data to do a wipe, if I pass up recovery and attempt to do the wipe with the factory wipe it also fails, which is why
I was hoping for an nvflash method. Does the stock recovery have the ability to access /data while it is encrypted? Thanks for the quick
reply also.
faustus1005 said:
CWM cannot mount /data to do a wipe, if I pass up recovery and attempt to do the wipe with the factory wipe it also fails, which is why
I was hoping for an nvflash method. Does the stock recovery have the ability to access /data while it is encrypted? Thanks for the quick
reply also.
Click to expand...
Click to collapse
Try a different recovery. Some peoples who have the can't mount sd card problems use a different recovery and it's fine. You can use PERI tool to install a new recovery and see what happen.
I've tried rogue and twrp, rogue couldnt mount /data either, and twrp wasn't functional at all on the slider... any suggestions for a custom recovery?
I had the same issue, of absolutely nothing being able to mount or read /data. I could use easyflasher (nvflash) to force a repartition and flash of stock asus ics, but it wouldn't be able to boot it. Turned out it's bad blocks on the internal EMMC, and the flash translation layer on these devices is too ****ty to properly map them out and report them to the system. So now my tablet is a giant, useless paperweight.
I've asked people for help as to how to flash a rom to an external sd card, and boot from that, but nobody has helped me. If I find anything out I'll be sure to PM you.
Good luck!
Sounds like you have even more of a problem than I do, I still have a working/functional OS. Its just
that none of these recoveries seem to be able to read the encryption. I'm perfectly able to use it
otherwise.
I hope so for your sake!
If it truly is just encryption, this superwipe script should be able to format it and remove encryption. flash it in recovery
Keep in mind it's a superwipe, so you will lose ALL your data, including the rom you have installed etc. You will retain whatever recovery you have flashed
http://goo.gl/YBW9H
If using super wipe, make sure you have a recovery that read external sd card or ADB to push a ROM top internal sd.
Ah, this worked perfectly. Just out of curiosity, is there a source available for superwipe? I would like to see how
it did it, for future reference.
faustus1005 said:
Ah, this worked perfectly. Just out of curiosity, is there a source available for superwipe? I would like to see how
it did it, for future reference.
Click to expand...
Click to collapse
I believed "Superwipe" script is a work of mike1986. See if he has any source in this link.
http://forum.xda-developers.com/showthread.php?t=1245892
open the zip on your computer, then navigate to meta-inf>com>google>android
then open updater-script with a text editor. You'll see how simple it is, it simply formats /data, /cache, and /system
you can do this with any flashable zip
P6800 running Zeta
I was browsing facebook the other night when... shaboom - everything froze. No biggie I thought, I'll just do a little reset (I was getting a few FCs here and there anyway lately) and I'll be good to go...
NOPE. It started bootlooping at the initial Samsung Galaxy Tab 7.7 screen. I'm able to enter CWM recovery and even wipe the cache and flash ZIP files, but when I try to wipe data/factory reset, wipe the Dalvik cache or restore a Nandroid backupI get a System Error. It doesn't look good.
Is there a way to fix my seemingly funked /system without losing all my internal SD card data (where my Titanium backups reside) or to recover it before a full Odin flash?
Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop
Do you dare to wipe the system folder and follow by flashing another ROM?
Sent from my GT-P6800 using xda app-developers app
iena said:
Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop
Click to expand...
Click to collapse
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data
Thread moved to Q & A section, post in the relevant section next time.
edan1979 said:
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data
Click to expand...
Click to collapse
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.
yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294
iena said:
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.
Click to expand...
Click to collapse
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
edan1979 said:
yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294
Click to expand...
Click to collapse
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.
Just reading the 1st post of the ZETA rom thread.
He says he is using stock Kernel.
He says every 5 lines, that you should full wipe...
without giving any sort of warning that it will eventually brick your device.
friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
Tried that one, but it won't mount unfortunately. The external will no problem, but when I try with the internal it just... well it does nothing. It's a bummer cause all my most recent backups are on the internal. Any other way of retrieving my data short of extracting the chip?
Giving it back to Samsung sounds like the best option, but I'm worried cause it has a custom ROM and it's rooted. Anyone has experience doing that?
Also I thought full wipes were good, but you're saying they eventually brick the device? How come? I thought having a custom recovery meant it would be virtually impossible to brick my device... and the weird thing is that it happened during normal usage, not while flashing.
Anyway, my priority is obviously to get my tab working again, but retrieving my internal data is second highest. Isn't there a flashable ZIP that would copy the contents of the internal SD into an external SD card? Surely this has happened to someone before me?
Thanks for all the answers, really appreciated!
bruce16878 said:
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.
Click to expand...
Click to collapse
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.
Oh I see, Thanks for the explanation. Learn something new today.
Sent from my LT18i using xda app-developers app
friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
edan1979 said:
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.
Click to expand...
Click to collapse
Gotcha! Will try that one and post result - thanks!
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
Thanks for that. I haven't tried anything yet as I'm away till Weds, but I will then and let you know. So you're saying by flashing stock HC via Odin and wiping/resetting everything through stock recovery I won't lose my internal storage data?
that's what i experienced..but i could not guarantee that it will be the same for your device
i noticed that because old folder are not deleted when i rebooted, but i haven't checked if the system folders are cleared
to have a clean reflash i also format/sdcard on recovery..but don't do this on stocl ICS recovery since you might risk increasing the damage
try to format via odin the Honeycomb fw first [don't put PIT file neither enable Repartion, just normal flash]
then force it to enter recovery mode when it bootloops after reset
you might fix your device this way if it has softbrick
just resort to using PIT/repartition as your last option
Again I would not recommend repartition when tab still under warranty. Repartition the last resort only if the tab is without warranty after failing all other alternatives.
JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck
al128 said:
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck
Click to expand...
Click to collapse
Ok I'm gonna do it. There are dozens of versions of HC for the 6800 though, can I just pick any or do I need to find out what it was running out of the box? Mine came from Singapore.
Hello all,
I would like to reflash CROMi-X and the MAX kernel but this time I want to do it as cleanly as possible. What are the steps to do this. I see it referenced all over that it is best to do a clean install but I can't find out exactly how to do it.
Sorry if this is a stupid question or if it is detailed somewhere that I could not find it but I want a good procedure that I can use whenever flashing new ROMS and kernels to be sure there is nothing hanging around that would cause variability in the install.
Thanks in advance for any help
Jeff
gixxer340 said:
Hello all,
I would like to reflash CROMi-X and the MAX kernel but this time I want to do it as cleanly as possible. What are the steps to do this. I see it referenced all over that it is best to do a clean install but I can't find out exactly how to do it.
Sorry if this is a stupid question or if it is detailed somewhere that I could not find it but I want a good procedure that I can use whenever flashing new ROMS and kernels to be sure there is nothing hanging around that would cause variability in the install.
Thanks in advance for any help
Jeff
Click to expand...
Click to collapse
Depends on which recovery you have installed -- the most often recommended sequence seems to be "wipe data/factory reset, wipe cache, wipe Dalvik cache, reinstall". Obviously, you may need to remove some apps' data folders from /sdcard by hand.
The opinions are divided as far as wiping the caches is concerned -- some do, some don't.
MartyHulskemper said:
Depends on which recovery you have installed -- the most often recommended sequence seems to be "wipe data/factory reset, wipe cache, wipe Dalvik cache, reinstall". Obviously, you may need to remove some apps' data folders from /sdcard by hand.
The opinions are divided as far as wiping the caches is concerned -- some do, some don't.
Click to expand...
Click to collapse
I have TWRP 2.5 installed. Is the above the process for TWRP
Thanks
Jeff
gixxer340 said:
I have TWRP 2.5 installed. Is the above the process for TWRP
Thanks
Jeff
Click to expand...
Click to collapse
In TWRP select 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
[Q=berndblb;43602193]In TWRP MI lect 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD[/QUOTE]
I dont seem to be able to see my microSD card from TWRP. It is formatted as ntfs, I wonder if that is the issue. What should it be formatted as?
Thanks
Jeff
gixxer340 said:
[Q=berndblb;43602193]In TWRP MI lect 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I dont seem to be able to see my microSD card from TWRP. It is formatted as ntfs, I wonder if that is the issue. What should it be formatted as?
Thanks
Jeff[/QUOTE]
Yeah, it has to be FAT32. Actually exFAT seems to work too. Just tried it, and TWRP sees the nandroid on a 8gb exFAT fine. Didn't try to restore though...
Sent from my DROID4 using Tapatalk 2
berndblb said:
I dont seem to be able to see my microSD card from TWRP. It is formatted as ntfs, I wonder if that is the issue. What should it be formatted as?
Thanks
Jeff
Click to expand...
Click to collapse
Yeah, it has to be FAT32. Actually exFAT seems to work too. Just tried it, and TWRP sees the nandroid on a 8gb exFAT fine. Didn't try to restore though...
Sent from my DROID4 using Tapatalk 2[/QUOTE]
Reformatting exFAT right now. Hopefully that will work.
Thanks again,
Jeff
berndblb said:
In TWRP select 'Wipe > Advanced' and then select everything except the external microSD. That'll give you a nice and clean installation.
Just make sure you have the Rom you want to flash afterwards on that microSD, not on the internal where it may get wiped
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Hi, without hijacking this thread - i've installed Cromix and everything is running great, but i can still see folders and files i had created when my 700 was stock. Am i doing something wrong here? I would have thought that wiping everything except for the microsd card would have given me a blank slate to start with but it seems there is a fair amount of data left over after the ROM flash.
Actually as i'm typing this i've just had a thought, is it a case that the documents, pics, wallpapers etc are on a separate partition (for want of a better definition) and they're just visible after the installation?
thanks,
sean
2Droidswalking said:
Hi, without hijacking this thread - i've installed Cromix and everything is running great, but i can still see folders and files i had created when my 700 was stock. Am i doing something wrong here? I would have thought that wiping everything except for the microsd card would have given me a blank slate to start with but it seems there is a fair amount of data left over after the ROM flash.
Actually as i'm typing this i've just had a thought, is it a case that the documents, pics, wallpapers etc are on a separate partition (for want of a better definition) and they're just visible after the installation?
thanks,
sean
Click to expand...
Click to collapse
I have noticed that problems a while back when I am using TWRP 2.5.0.0. Therefore, I always prefer to use Format instead of Wipe.
2Droidswalking said:
Hi, without hijacking this thread - i've installed Cromix and everything is running great, but i can still see folders and files i had created when my 700 was stock. Am i doing something wrong here? I would have thought that wiping everything except for the microsd card would have given me a blank slate to start with but it seems there is a fair amount of data left over after the ROM flash.
Actually as i'm typing this i've just had a thought, is it a case that the documents, pics, wallpapers etc are on a separate partition (for want of a better definition) and they're just visible after the installation?
thanks,
sean
Click to expand...
Click to collapse
If you wipe or factory reset in TWRP, it erases everything except the /data/media folder, and that is where your data lives.... You have to manually erase those files if you want to get rid of them.
Interestingly, you'll find symlinks to the contents of /data/media in 4!! locations:
/sdcard
/storage/sdcard0
/storage /emulated/0
/storage /emulated /legacy
This crazy structure is due to the multi user support in JB 4.2. I still have a hard time to get my head around it....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
If you wipe or factory reset in TWRP, it erases everything except the /data/media folder, and that is where your data lives.... You have to manually erase those files if you want to get rid of them.
Interestingly, you'll find symlinks to the contents of /data/media in 4!! locations:
/sdcard
/storage/sdcard0
/storage /emulated/0
/storage /emulated /legacy
This crazy structure is due to the multi user support in JB 4.2. I still have a hard time to get my head around it....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
:good: Thanks, it is good to know.
berndblb said:
If you wipe or factory reset in TWRP, it erases everything except the /data/media folder, and that is where your data lives.... You have to manually erase those files if you want to get rid of them.
Interestingly, you'll find symlinks to the contents of /data/media in 4!! locations:
/sdcard
/storage/sdcard0
/storage /emulated/0
/storage /emulated /legacy
This crazy structure is due to the multi user support in JB 4.2. I still have a hard time to get my head around it....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
How incredibly bizarre....but interesting nonetheless. 23 years in IT and it's time to start learning again. I kept going back to Settings>About and could see that the ROM was flashed, but the sight of the old files was making me think 'maybe it just reinstalled over the top of the stock ROM without deleting any data'....sort of like when windoze does a repair and keeps the data. Now that i understand user data is stored in a separate place away from the ROM itself, it makes it easier to upgrade and mess around. Backups are important, but it's nice to know you don't have to constantly relocate data and files when you're doing an upgrade.
Thanks for the info.....these forums are an absolute boon for people willing to ask questions and i'm amazed at the knowledge base that's been accumulated and is being shared - for the first time in a long time, tech toys are fun again. Now to choose a Kernel!!!!
The rom gets flashed to it's own partition: /system/...
If you watch the script when flashing CromiX, the installer formats the system partition automatically before flashing the rom. So you did not install over the old rom. The Data partition is different.
I'm now backing up data/media and then I will use the "Format Data" option in TWRP. Wanna know what exactly happens
Sent from my DROID4 using Tapatalk 2
Just an update...i haven't changed kernels at all and i'm not going to be. This thing is faster and more stable than i could have wished for. Since the ROM was flashed i've stopped messing around with it and it just runs like a dream. It never reboots unless i tell it to, doesn't hang when i have multiple apps open and the battery life is fantastic.
Thanks for the advice berndblb :good:
2Droidswalking said:
Just an update...i haven't changed kernels at all and i'm not going to be. This thing is faster and more stable than i could have wished for. Since the ROM was flashed i've stopped messing around with it and it just runs like a dream. It never reboots unless i tell it to, doesn't hang when i have multiple apps open and the battery life is fantastic.
Thanks for the advice berndblb :good:
Click to expand...
Click to collapse
:GOOD:
Glad I could help.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Does the data partition formatted to F2FS cause random reboots? I cant seem to narrow it down to anything else. Every nougat rom i tried so far seems to random reboot 3-4 times a day with clean installs. What file format is recommended for custom roms on this phone?
you need a custom kernel for that i think, i thin firekernel has support.
idk tho i dont have experience with it
I believe that ext4 is the stock filesystem type for the data partition, I've never changed it.
Actually, the stock ROM has the data partition formatted as F2FS. It's one of the factors in making the lower end processor seem as fast and snappy as it is.
You can check it in TWRP recovery. Go to advanced wipe and check the formatting for the data partition.
Sent from my MotoG3 using Tapatalk
riggerman0421 said:
Actually, the stock ROM has the data partition formatted as F2FS. It's one of the factors in making the lower end processor seem as fast and snappy as it is.
You can check it in TWRP recovery. Go to advanced wipe and check the formatting for the data partition.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hmm... Your right, a quick look at mount in the terminal confirms that. Sorry, my bad.
Now that we know that, I guess the F2FS file system type is probably not the cause of your issues.
acejavelin said:
Hmm... Your right, a quick look at mount in the terminal confirms that. Sorry, my bad.
Now that we know that, I guess the F2FS file system type is probably not the cause of your issues.
Click to expand...
Click to collapse
Yes. I've tried different combinations of partitions formatted to f2fs and it would only work using data as F2FS. Im using the newest aosp extended. Maybe this rom will fix my reboot problems. I am new to this phone coming from a falcon. I know one thing, i am not enjoying moto display. The screen seems to turn on when you dont want it to all the time. I miss my notification LED.
Hello all, when I updated my shield k1 to v5.0 I ran across a problem. First, when i first updated the system did not recognize my adopted storage(128gb sandisk micro sd) and I had to reformat it as internal. after that, I had to reflash TWRP and SuperSU. After that, I can no longer access my data from within twrp and receive a message along the lines of "unable to mound decrypted storage device" this is a big problem because I can only flash things if i move them to a usb or the root folder of my device. I have done some searching on the internet but have not been able to find any solutions. If anyone else is having or had this problem, it would be great to know how to fix it. Thanks for the help ahead of time. I would be happy to provide any additional information needed or wanted to assist with this problem.
I'm having the same issue on the original Nvidia Shield Tablet.
you encrypted your internal sd?
and it is not "default_password"?
if you have another SD card try it with it.
what you want to do. If there are no data you will backup you can try to format (not wipe) data and boot Android again.
reboot to TWRP and try again if it will mount.
But here are a TWRP thread where you could ask these questions.
I dont know what happened here but I had the same thing. If anyone comes here via Google or Search, flashing this TWRP Version fixed my issue https://forum.xda-developers.com/showpost.php?p=71877863&postcount=427
I dont know what exactly is happening but the Stock Recovery cant mount the Card either. I can only assume it is a Bug somehow?
D-m-x said:
I dont know what happened here but I had the same thing. If anyone comes here via Google or Search, flashing this TWRP Version fixed my issue https://forum.xda-developers.com/showpost.php?p=71877863&postcount=427
I dont know what exactly is happening but the Stock Recovery cant mount the Card either. I can only assume it is a Bug somehow?
Click to expand...
Click to collapse
Good catch! I was running TWRP 3.1.1.0 and it wouldn't detect my adopted storage at all. I test booted the twrp you linked (fastboot boot recovery.img) and it worked fine, even though it's an older version of TWRP. So then I went ahead and flash it. Thanks!