Related
I encrypted my 10.1 yesterday without thinking all the way though. I found out that I could no longer flash kernels while the tablet is encrypted, since the SD card is not accessible in CWR.
I've tried doing a factory reset on my tab and each time, it boots up like nothing happened. I've also tried removing the pin that I put on it and the option to remove it is grayed out.
Do any of you know of a way to do a full wipe on the 10.1? Or could I reflash it using ODIN?
Thanks in advance.
id like to know this as well
still nothing? im starting to think this is an easy fix that nobody has posted about yet
there has to be something that im missing
try post # 6 in the linked thread, restore with unmodified vanilla version image from second link provided in the post, after booting from fastboot into recovery with clockworkmod recovery img; pushing it into the device sd with adb commandline, check the post for modifications and the link for details.
http://forum.xda-developers.com/showthread.php?t=1161325
whenever i try to reset to factory defaults, it just reboots like nothing happened
re-flash a stock firmware via odin as tar or fastboot/nandroid as img (backup restore)
Ones the tab is encrypted, there's no way to un do it. Unless you do what mughalgxt suggested. Good luck
Thanks guys, I went through some of these steps and found some other good tutorials to get me back up and running. All i wanted was to try the new kernel/bonsai rom out and I'm now able to do that
**** encryption, put a lockscreen password and be done with it.
I'm still struggling with this, as well: off to read some of the linked threads, because even with flashing a stock image with ODIN I'm still not able to recover the device. At least I managed to proceed past the boot loop I WAS in (when attempting to flash from CWM) - but now, I can get to the point where the device prompts me for the decryption key (meaning, it's clearly not yet restored to factory defaults) - but can't get it boot to completion. I also note that I've still got CWM Recovery, not stock.
It seems, at some point, encryption-key be damned, right? Meaning, if I don't care about recovering the contents of the encrypted partition - surely these low-level tools have the ability to simply format the partitions? Perhaps not - at least, not CWM - as attempts to format /data continue to fail.
Off to review the linked threads to try to gain some additional insight.
I ran into this same issue a long while back. As I recall (and it's been a while), you won't be able to wipe from CWM, but you can wipe from Settings / Privacy / Factory Data Reset. I could be wrong, but I know that I didn't have to do any adb pushing or anything with special images.
Hi SacTilt-
Thanks for the reply - and agreed: Had I actively started the effort from a functioning device, I think I could have selected that option.
As it turns out - I ran CWM, rebooted into recovery, and... next thing I knew, I was in boot loop hell.
I've tried flashing a variety of files via ODIN: Some at least allow the device to boot to the point where I get the initial password prompt - which I can provide, and proceed past... but then the device just 'goes blank'.
What I'm looking for is a 'start-from-scratch', no concern for data loss, delete the dang encrypted /data folder already, will ya?... approach.
As I've mentioned, a variety of ODIN files from a myriad of sources haven't seemed to quite do the trick. I feel like I'm missing something obvious - but can't find the right angle to spot it.
Perhaps fastboot might be what I'm looking for?
FWIW: the device was rooted when I started, so I've got full Titanium backups, with which I can restore, once I recover the actual device / OS.
Thanks for any insight.
Hey guys...if anybody finds a solution to this, please let me know...I am stuck with this same damn experimental ROM I've had from day one...it's getting really old. All I want is to get rid of this stupid encryption. Thanks for any help. Tried ODIN flashing, wiping data from security screen, wiping from CMR, etc.
Have you tried formatting the sd? Whenever i had my ns4g i accidentially did the same thing and i wiped the SD and it removed the encryption.
Sent from my GT-P7510 using XDA Premium HD app
If you did Soft-Brick your new Nexus 7 2013 and you cannot access your Nexus 7 from your computer or a Factory Reset does not help please follow this guide. :crying:
(This is way different than the 0 Internal Storage bug. Go here: http://forum.xda-developers.com/showthread.php?t=2380913 )
Step 1: Download and install Wugs toolkit from here: http://www.wugfresh.com/nrt/
Step 2: Let it download the files it needs and choose what device your have EXACTLY what you have.
Step 3: Install the universal drivers by finding the Initial Setup part which is the big bar at the top. Go to the Step 2 tab and install the Universal Drivers and then let that install. It installs ADB so you can access ADB even in recovery if you could not before.
Step 4: Launch the Advanced Utilities in the bottom left and you will need a new ROM. Go here to get one: http://forum.xda-developers.com/forumdisplay.php?f=2411
gApps: http://goo.im/gapps
Step 5: Once you have those two things go to Flash Zips at the top right and tell it that the file is on the computer. Go to add files and add the ROM then GAPPS and enable to the left that it is a ROM but disable the nandroid backup because you really don't need it at the moment. Also have Wipe Dalvik, Cache, and Data on at the bottom.
Step 6: Confirm it and let it flash. Done! It will take about 5 minutes. Go eat or do something while waiting. It might take less but if you want to be on the safe side just let it run until your device powers on. :victory:
I AM NOT RESPONSIBLE FOR ANYTHING THAT YOU DO WRONG.
If you have any questions or comments please leave some.:good:
So, use a toolkit to install a ROM. How is this some magical fix?
khaytsus said:
So, use a toolkit to install a ROM. How is this some magical fix?
Click to expand...
Click to collapse
I never meant for it to be a "magical" fix. It is just a fix for a soft-bricked Nexus which had a rogue ROM and a Factory Reset would not fix nor was ADB working. Maybe someone has this happen and if you have a Backup from lets say Titanium Backup you kind of don't want to Format Data. So if you could just appreciate if I made a tutorial for the less fortunate in Android I am sorry. Skip the thread next time please
WeRSpecialPeople said:
Also have Wipe Dalvik, Cache, and Data on at the bottom.
Click to expand...
Click to collapse
You say here to wipe data.
WeRSpecialPeople said:
Maybe someone has this happen and if you have a Backup from lets say Titanium Backup you kind of don't want to Format Data.
Click to expand...
Click to collapse
And here not to format data. Though wipe and format are not the same, the end result to the user is still that the data is gone. So I'm not sure whether you mean for the data gone or not.
WeRSpecialPeople said:
If you have any questions or comments please leave some.:good:
Click to expand...
Click to collapse
1. Usually, the better option is to find the most similar ROM to the one that the data partition was populated with, so there will be a smaller likelihood of problems. For example, an older working nightly of the same ROM. Dirty flashing a random ROM is less likely to be problem-free.
2. Out of curiosity, why a toolkit, especially when flashing a ROM zip from recovery (not even ADB or fastboot) would work just as well?
bananagranola said:
You say here to wipe data.
And here not to format data. Though wipe and format are not the same, the end result to the user is still that the data is gone. So I'm not sure whether you mean for the data gone or not.
1. Usually, the better option is to find the most similar ROM to the one that the data partition was populated with, so there will be a smaller likelihood of problems. For example, an older working nightly of the same ROM. Dirty flashing a random ROM is less likely to be problem-free.
2. Out of curiosity, why a toolkit, especially when flashing a ROM zip from recovery (not even ADB or fastboot) would work just as well?
Click to expand...
Click to collapse
Alright Formatting Data wipes the whole device usually. Wiping the data gets rid of the users apps. Lets say you have a backup in storage/emulated/legacy. It will still be there after you wipe the data.
1. Yes but that is the users choice. I couldn't find a definite stock ROM to the device so I will just let them pick.
2. If you want me too I could make a tutorial using ADB if you really want me too. This was just a 5 minute tutorial on a toolkit and I understand that most people here do not like toolkits but it is a really easy way. Just tell me if you do want me to add ADB tutorial as well and I will. :silly:
WeRSpecialPeople said:
Alright Formatting Data wipes the whole device usually. Wiping the data gets rid of the users apps. Lets say you have a backup in storage/emulated/legacy. It will still be there after you wipe the data.
...
Just tell me if you do want me to add ADB tutorial as well and I will. :silly:
Click to expand...
Click to collapse
I don't think formatting data wipes the whole device...just the data partition. Same as wiping data. The kernel and ROM in the boot and system partitions respectively stay. Wiping data wipes all user data as well, not just apps. In either case, I don't think sdcard gets wiped.
Since I won't be using it, I personally don't mind what you do with the toolkit, but users need to be aware that it's not the most problem-free method.
bananagranola said:
I don't think formatting data wipes the whole device...just the data partition. Same as wiping data. The kernel and ROM in the boot and system partitions respectively stay. Wiping data wipes all user data as well, not just apps. In either case, I don't think sdcard gets wiped.
Since I won't be using it, I personally don't mind what you do with the toolkit, but users need to be aware that it's not the most problem-free method.
Click to expand...
Click to collapse
Sdcard is on /data so if you wipe data (including factory reset) the sdcard is 'formatted'.
khaytsus said:
Sdcard is on /data so if you wipe data (including factory reset) the sdcard is 'formatted'.
Click to expand...
Click to collapse
Does it now...how odd. Has it always worked like that on every device? On my Galaxy Nexus, TWRP specifically ignores the sdcard mount point.
EDIT: okay, I think I understand the confusion. I meant that wiping data/factory resetting from recovery doesn't wipe sdcard. I know that doing so from Android does.
My Nexus 7 2012 (Grouper) is really show, sometimes unusable and I have to Power off and on again.
I had Stock 4.4 installed when I first noticed the problem, them Android 5 came up and I downloaded from google, cleaned all partitions with TWRP and installed Android L with ADB. But unfortunately it got even worse. then I cleaned all partitions again, /data, /system, /cache, I marked all options on TWRP and installed Android 5 again but it was still slow (sometimes it seems in normal speed, but more often is slow).
So I installed Cyanogem mod, currently version is 11-20141206-NIGHTLY-grouper
It is faster with CM, but I still get speed problems sometimes like switching between apps, unlocking the tablet, etc...
I really want to stay in Stock Android 5, but it is too slow, sometimes impossible to use.
Can someone give me any suggestions on what to do ?
I don't care if I have to reset, reinstall, clear, etc
If you want any more informations I can give.
JuniorBR790 said:
Can someone give me any suggestions on what to do ?
I don't care if I have to reset, reinstall, clear, etc.
Click to expand...
Click to collapse
Have you tried to format it to F2FS? That's a file system optimised for flash storage which usually helps a lot with speed issues.
Short how-to (there are longer versions around, search for them if necessary):
You need the latest TWRP (2.8.2.0, I think) and a F2FS-compatible rom (and maybe a kernel), look for the latter in the forums. I use this version of a 5.0-Rom which has been modified for F2FS: http://forum.xda-developers.com/showpost.php?p=56813573&postcount=491 (it includes a f2fs-compatible kernel)
Then make a backup of ALL your data (including /sdcard) to an external device (PC, usb storage, or whatever), otherwise you'll lose it. Save the rom on this external device, too.
In TWRP go to advanced wipe, there you can select the partitions system, data and cache one after the other to format & repair them. Or see this post for a longer explanation.
Afterwards you can copy your stuff back from the backup and flash the rom & gapps as always.
luckyrumo said:
Have you tried to format it to F2FS? That's a file system optimised for flash storage which usually helps a lot with speed issues.
Short how-to (there are longer versions around, search for them if necessary):
You need the latest TWRP (2.8.2.0, I think) and a F2FS-compatible rom (and maybe a kernel), look for the latter in the forums. I use this version of a 5.0-Rom which has been modified for F2FS: http://forum.xda-developers.com/showpost.php?p=56813573&postcount=491 (it includes a f2fs-compatible kernel)
Then make a backup of ALL your data (including /sdcard) to an external device (PC, usb storage, or whatever), otherwise you'll lose it. Save the rom on this external device, too.
In TWRP go to advanced wipe, there you can select the partitions system, data and cache one after the other to format & repair them. Or see this post for a longer explanation.
Afterwards you can copy your stuff back from the backup and flash the rom & gapps as always.
Click to expand...
Click to collapse
I am going to give it a try. actually I have tried it already but couldn't do many testing yet.
Which ROM you think is best for f2fs support and is Android 5 ?
I wanted to do my own, get the original rom, install in f2fs and change the kernel to a compatible one, but I couldn't figure out how to install the original image without it formatting back to ext4. I guess it might not be as easy as just this right ?
I would like to modify it by myself because I wanted a rom with f2fs with as few modifications as possible.
I don't like roms that have everythng stipped out
have tried ubuntu touch too, but it is frequently freezing the tablet, the screen gets flickering. I think Ubuntu touch does not support grouper.
JuniorBR790 said:
I am going to give it a try. actually I have tried it already but couldn't do many testing yet.
Which ROM you think is best for f2fs support and is Android 5 ?
Click to expand...
Click to collapse
I don't know. As I'm quite busy at the moment and the one I use (see link in m previous post) is running fine, I stick with it. But these two look promising, too: Rastapop, SlimLP
JuniorBR790 said:
I wanted to do my own, get the original rom, install in f2fs and change the kernel to a compatible one, but I couldn't figure out how to install the original image without it formatting back to ext4. I guess it might not be as easy as just this right ?
Click to expand...
Click to collapse
You need to do a bit more than changing the kernel. I've never done it, better ask someone else, maybe the guy who converted BSZAosp and Rastapop (links here and in my previous post). He wrote about it in those threads.
JuniorBR790 said:
I would like to modify it by myself because I wanted a rom with f2fs with as few modifications as possible.
I don't like roms that have everythng stipped out
Click to expand...
Click to collapse
This BSZAosp I use is very close to stock.
JuniorBR790 said:
have tried ubuntu touch too, but it is frequently freezing the tablet, the screen gets flickering. I think Ubuntu touch does not support grouper.
Click to expand...
Click to collapse
Yes, at least not officially.
Mine started to have problems on kitkat. It would freeze, I could not turn it on when in standby and it would take forever to switch between users (have 3 users). I updated it to Lollipop (OTA sideload) and it became even worst. I tried factory reset and it didn't help. Next morning it would not start - there just was Android on screen and it would stay like that forever. I tried to unlock bootloader to sideload factory image but it didn't work. Luckily, I had warranty (it's 2 years here) so I took it to shop. They changed motherboard and it came with 4.2 installed from shop. OTA came to 4.4.4 and I sideloaded 5.0 again. It still was slow, especially when I added two more users. So I disabled system apps I don't use (on all user accounts), turned off location and forced gpu rendering in developer options and now it works great...
Hello guys,
I ran the latest oxygen OS and TWRP recovery. Today I saw that the new official Oreo OTA is out so I downloaded the full zip and tried to dirty flash it in TWRP. It did not work out and i got an error, and people suggested to use twrp blu_spark for flashing the oreo build.
So I flashed twrp blu_spark in fastboot, booted into recovery and installed the oreo zip. Before I did that, TWRP always asked to type in my password to decrypt the files.
After flashing oreo my phone wouldn't boot into Android, it just stayed at a black screen while the LED was shining. I realized I had to **** up somewhere so I booted back into recovery, but TWRP doesn't ask for my password to decrypt my data and now everything in my internal storage has weird file names (which I suppose come from the decryption) and I don't know how I can decrypt my data again. I also flashed the normal TWRP but it didn't ask to decrypt my data either.
Can somebody please help me? I can't do anything at all at the moment and I don't want to wipe my system as I unfortunately don't have a backup (I have one, but that's a TWRP backup and in internal storage which is encrypted...).
Thank you so much in advance, you are my last hope
I think my problem is that I don't have a PIN setup in android, because it's actually bricked (had to flash the wrong oreo probably or so). Do you think TWRP will ask for a password again if I somehow manage to install the old oxygen os and setup a lock screen PIN again?
Same Issue here... Searching for a solution
I ended up wiping everything except internal storage. I then pushed the old oxygen os to the internal directory and flashed it (in hope it wouldn't change anything in my internal storage/sd card). Looks like I was wrong. After flashing it also apparently wiped my complete internal /sdcard.
All data gone. Nothing I can do now anyway. If somebody would have known a better way to decrypt my data again with a broken android, feel free to comment - feeling really bad now, so many photos etc. on it. At least learned my lession to always take a back up, but normally I'm super careful and not flashing anything that would wipe/brick something on my device. This freaking oreo update is making me crazy.
Sieth said:
Same Issue here... Searching for a solution
Click to expand...
Click to collapse
If you have broken your android/system like I (it didn't want to boot into the system anymore after flashing) I think there's almost no chance. Atleast my device is clean now and I can't do anything at all and my data is forever gone now. But I learned my lesson and you probably too - always take a backup.
I mean okay, after I thought about it it's not too bad as I didn't have a lot of important photos on it and I fortunately backed up my whatsapp to google drive before playing around so yeah, atleast a clean device now and will look for a nice oreo ROM.
If you think you can find a solution good luck, but I think the only way to get TWRP to decrypt the internal storage partition again is to set up the display lock in your ROM again - and if you have a bricked ROM and flashing a new one it will wipe /sdcard completely like in my case...
test it this twrp
https://androidfilehost.com/?fid=745849072291696652
jahidinbedod said:
test it this twrp
https://androidfilehost.com/?fid=745849072291696652
Click to expand...
Click to collapse
sorry, too late, wiped it already. why should this twrp work? I tried normal one and blu_spark, none of them asked me to decrypt my data.
jahidinbedod said:
test it this twrp
https://androidfilehost.com/?fid=745849072291696652
Click to expand...
Click to collapse
Done and nothing happened, still not asking me to enter a pattern\pin. Is there a way to force it? maybe a line or a terminal code? I remember my pattern ofc
Vanniman said:
Done and nothing happened, still not asking me to enter a pattern\pin. Is there a way to force it? maybe a line or a terminal code? I remember my pattern ofc
Click to expand...
Click to collapse
I don't think there's much chance. I was able to see all those weird filenames in internal storage when connected to my PC, but I could not copy or change files to internal storage. If this would have worked, there might be a chance to decrypt the data manually on your PC if you find how to do it/if it's even possible.
I seriously think there's no good solution for our problem. :/
Michael1200 said:
I don't think there's much chance. I was able to see all those weird filenames in internal storage when connected to my PC, but I could not copy or change files to internal storage. If this would have worked, there might be a chance to decrypt the data manually on your PC if you find how to do it/if it's even possible.
I seriously think there's no good solution for our problem. :/
Click to expand...
Click to collapse
All deleted now... I know that feel
So I wiped the whole device. Adb sideloaded the new rom. Working flawless.
Now installed Magisk 14.0 and device stuck at boot with blue light.
So the rooting is to blame... (In my case...)
So I adbd again the rom.zip and got it working again. But no root for now
Update: flashed Magisk beta v14.6 (1468) and now ist's working.
Vanniman said:
All deleted now... I know that feel
Click to expand...
Click to collapse
RIP our data.. :/ atleast starting with a super clean device now. lesson learned ^^
Hi all.
i was in the same boat as all of you. screwed up somewhere and then lost everything and did a side load. but now the problem is whenever i boot with twrp it still keeps showing my internal storage as 0. so am not able to root it. how do i go about solving this?
---------- Post added at 07:54 PM ---------- Previous post was at 07:54 PM ----------
Sieth said:
So I wiped the whole device. Adb sideloaded the new rom. Working flawless.
Now installed Magisk 14.0 and device stuck at boot with blue light.
So the rooting is to blame... (In my case...)
So I adbd again the rom.zip and got it working again. But no root for now
Update: flashed Magisk beta v14.6 (1468) and now ist's working.
Click to expand...
Click to collapse
How did you flash magisk beta? in my case twrp says that my internal storage is 0
What I did was format not wipe.
ADB sideload rom.zip
Install latest beta from magisk.
So now I have a clean device with working root
Sieth said:
What I did was format not wipe.
ADB sideload rom.zip
Install latest beta from magisk.
So now I have a clean device with working root
Click to expand...
Click to collapse
Nice, data lost as in my case but clean device is great too atleast. ^^
f***, same happenned to me. I did a back-up with twrp before but i left it in my internal memory.
I do have a month old back up on my laptop. How can i push this over to the phone? Can i restore a backup from bootloader ??
I gotta try everything to save my data, too many important things for work on there. I was too ****ing eager to get oreo
I've done the exact same thing. Problem now is that TWRP isn't seeing anything on the phone, there is nothing there. So I can't root with Magisk or install custom recovery.
Edit...had to use blu_spark twrp instead
Bigred065 said:
f***, same happenned to me. I did a back-up with twrp before but i left it in my internal memory.
I do have a month old back up on my laptop. How can i push this over to the phone? Can i restore a backup from bootloader ??
I gotta try everything to save my data, too many important things for work on there. I was too ****ing eager to get oreo
Click to expand...
Click to collapse
Not much chance to get back the data if you can't boot into android at all. You can wipe everything completely and then copy your old backup to your internal storage which will work again once wiped/decrypted. I haven't found a solution to save the data without wiping, I tried different twrp versions like the normal one or blu_spark but none asked to decrypt data and in my internal storage my files were left all encrypted with those weird long file names.
Are you trying to say that all my data is lost even tho I know decryption key? All I did was update to Android O and I had backup and TWRP is showing that my internal storage is full but the files are all encrypted it wont ask me for decryption key. What can I do
SPyxOff said:
Are you trying to say that all my data is lost even tho I know decryption key? All I did was update to Android O and I had backup and TWRP is showing that my internal storage is full but the files are all encrypted it wont ask me for decryption key. What can I do
Click to expand...
Click to collapse
Exactly. That's the weird problem. If I'm right we had to **** up something badly so that TWRP doesn't even know that our internal storage is encrypted and displaying the (encrypted) files just how they are. The problem in my case was that I couldn't even copy the encrypted files from internal storage to my PC or moving files from my PC to my device. The whole partition was just locked, I couldn't do anything on it, neither adb push or whatever else. Tried different TWRP versions but none asked me to decrypt.
I think the mistake is that if you install a new OS version which is somehow not backward/dirty flash compatible (like in my case the new oreo update) your pin/pattern will get deleted and because of that TWRP does not ask you to decrypt as the ROM is telling that you don't have a password set up! But the problem is when you install a new ROM, it wipes /sdcard so the data is lost if you don't find a way to somehow decrypt your internal storage. :/
Really bad to know you can't do anything at all even tho you know your decryption key - I hope someone finds a solution. I for myself wiped because I don't have so much time to look for a solution.
Hi everyone,
I've been scouring the forums for days and it's been really helpful but I just can't crack my problem.
My parent's Nexus 10 was having problems but due to the lockdown I couldn't go to help them out, my mum messed around and a factory reset went wrong.
At the moment, the tablet boots only as far as the Google logo. I can get into the bootloader, have unlocked it and tried flashing various stock Roms including the newest one (lmy49j) I'd get this message:
Erase successful, but not automatically formatting.
File system type raw not supported.
Boot up only as far as the Google logo still.
I tried using the flash-all.bat and manually line by line which seemed to give less errors but still no luck.
I've now been messing around with the Nexus Root toolkit v2.1.9 which allows me to boot into twrp and I can push files onto the sdcard. The problem is I can't mount the cache/data/storage so it still fails. I tried changing the file system to EX2 but it won't let me do that. They all show as 0mb. I can't wipe Data or Cache for the same reason, Davlik won't wipe either.
This link is my most promising lead left but I'm running out of ideas, I could be running a c:\Smash fist through tablet.bat command soon lol.
[HOWTO] [GUIDE] Repairing corrupted /data partition
I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited...
forum.xda-developers.com
Any help/ideas would be most appreciated,
Cheers
Did you ever fix this? I've the same problem.
I was able to get mine working again. One of the partitions had been corrupted. When in TWRP I looked under 'mounting' and the one that wouldn't mount was the problem. So I deleted then recreated that partition using the instructions and version of twrp found here.
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com
While in parted, display sector values for partitions. Then when you delete that partition recreate it using the same values, reformat it as described in the same post above, and your device should be ready for an installation.
Hope this helps.
Melogibbo said:
Hi everyone,
I've been scouring the forums for days and it's been really helpful but I just can't crack my problem.
My parent's Nexus 10 was having problems but due to the lockdown I couldn't go to help them out, my mum messed around and a factory reset went wrong.
At the moment, the tablet boots only as far as the Google logo. I can get into the bootloader, have unlocked it and tried flashing various stock Roms including the newest one (lmy49j) I'd get this message:
Erase successful, but not automatically formatting.
File system type raw not supported.
Boot up only as far as the Google logo still.
I tried using the flash-all.bat and manually line by line which seemed to give less errors but still no luck.
I've now been messing around with the Nexus Root toolkit v2.1.9 which allows me to boot into twrp and I can push files onto the sdcard. The problem is I can't mount the cache/data/storage so it still fails. I tried changing the file system to EX2 but it won't let me do that. They all show as 0mb. I can't wipe Data or Cache for the same reason, Davlik won't wipe either.
This link is my most promising lead left but I'm running out of ideas, I could be running a c:\Smash fist through tablet.bat command soon lol.
[HOWTO] [GUIDE] Repairing corrupted /data partition
I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited...
forum.xda-developers.com
Any help/ideas would be most appreciated,
Cheers
Click to expand...
Click to collapse
GhostMachine7 said:
I was able to get mine working again. One of the partitions had been corrupted. When in TWRP I looked under 'mounting' and the one that wouldn't mount was the problem. So I deleted then recreated that partition using the instructions and version of twrp found here.
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com
While in parted, display sector values for partitions. Then when you delete that partition recreate it using the same values, reformat it as described in the same post above, and your device should be ready for an installation.
Hope this helps.
Click to expand...
Click to collapse
Thanks man, I will give it a go!
Melogibbo said:
Thanks man, I will give it a go!
Click to expand...
Click to collapse
Do you have a stock PIT file for the manta available? I want to go back to stock but I repartitioned mine for a custom install and didn't get the PIT beforehand as I didn't expect to be going back. I like the newer version, but it's too slow for many uses. I know the stock image doesn't have security updates, but since I use it only on my LAN and sometimes for streaming sites, I don't see it being a big risk and it should be a lot more responsive.
Thanks
GhostMachine7 said:
Do you have a stock PIT file for the manta available? I want to go back to stock but I repartitioned mine for a custom install and didn't get the PIT beforehand as I didn't expect to be going back. I like the newer version, but it's too slow for many uses. I know the stock image doesn't have security updates, but since I use it only on my LAN and sometimes for streaming sites, I don't see it being a big risk and it should be a lot more responsive.
Thanks
Click to expand...
Click to collapse
Hey, no I don't sorry. I'm still having trouble even loading up the version of twrp mentioned in the thread let alone flashing a rom onto it. I can only get into twrp if I use the nexus root toolkit otherwise it just gives me errors relating to not being able to mount cache, very frustrating.
I can only look at it now and again as it sucks all my time up and pisses me off, I'll have another stab at it next week maybe.