Database Users

Acer Iconia A500 stuck in boot loop or bricked?

Ok, I looked in some of the threads already posted, but didn't really see the problem that I am having.
My A500 gets stuck in boot loop. I can access the recovery and wipe data, flash etc... however, none of that is working. After I have wiped EVERYTHING and reflashed the Thor ROM 14.2 I get stuck in boot loop again with the little blue android with the spinning gears... That's it. I'm spent, I have no idea what I should do next. I only paid $260 for this bad boy, so I'm not sending it to ACER to charge me money to fix it... Any ideas?

Have you tried to format your sd card and place a fresh download of the rom you wish to flash on the sd and tried again.. It sounds like there is something corrupt.
This would my first thing to try from what i understand about your Question . If you try the above and still have issues. post back all the details that caused you to end up in this situation. from rom version you were on at first and recovery your using as well as details on how you flashed.
Good Luck.

I'll try that, but skeptical about it. Since I last posted, I have tried a nandroid restore, flashing a different rom, a couple more complete data wipe/factory data resets, no luck on that. I am formatting the SD card now, in hopes I can get a good clean flash?
Edit: I just realized all the wipedata/factory rests I've been doing haven't worked as they never complete. They say 'error formatting...' and before I can read what all it says it cannot format, it disappears. I guess at first I just thought it was wiping really fast...
edit: formatting the sd card, did not work. im still stuck in bootloop.
Edit: I think I found my solution here: http://forum.xda-developers.com/showthread.php?p=23246074#post23246074
so far it seems to be working...

So that link got you up and running? I'm always afraid of the boot loop and like to prepare for the worst
Sent from my A500 using Tapatalk

Re
Do you get an error message when you try to wipe data factory reset? If you do then your data partition is corrupt, happened to me yesterday. the way you fix this is go into recovery>backup/restore> toggle backup and restore of internal storage (/data/media) so it says enabled>mounts and storage>format data. Then you should be good to go. This REALLY formats the data partition so EVERYTHING will be deleted on it.

first,sorry for my bad english. I've been able to light up my acer a500 but I got stuck in airplane mode on email section.any one can help me?

it fixed mine
keegWag said:
Do you get an error message when you try to wipe data factory reset? If you do then your data partition is corrupt, happened to me yesterday. the way you fix this is go into recovery>backup/restore> toggle backup and restore of internal storage (/data/media) so it says enabled>mounts and storage>format data. Then you should be good to go. This REALLY formats the data partition so EVERYTHING will be deleted on it.
Click to expand...
Click to collapse
thanks for the input keegWag.... got my tablet going again.

[Q] A2SD problems.

Here is a story about me and my phone:
I'm using this rom for about 2-3 months and it's great!! http://forum.xda-developers.com/showthread.php?t=1817793
But when I was updating some apps with the Play Store I got error 492.
Googled it and I found a thread on XDA and it said that I had to clear some caches.
So I did that and a Dalvik Cache wipe and I fixed permissions.
But it ended in an endless boot. So wiped everything and I did as an extra a Task 29. I flashed my rom installed INT2EXT+. The first boot after I flashed INT2EXT+ something weird happened: The WiFi just didn't turn on. I just turned it on but the slider bounced back after 5 seconds. Reflashed still that problem. So here comes the question how can I fix it?

Wi-Fi issues are sometimes connected to too small system partition. Perhaps caused by bad blocks. Make sure your system partition is bigger than needed. I usually add 10/15 mb above what the rom requires

samsamuel said:
Wi-Fi issues are sometimes connected to too small system partition. Perhaps caused by bad blocks. Make sure your system partition is bigger than needed. I usually add 10/15 mb above what the rom requires
Click to expand...
Click to collapse
Did what you said but when I let it start up I just see just a FC of Settings that's it. :crying::crying:
I rebooted it several times en every time it boots up I see ''Android is Upgrading''.

did you do a 'wipe data' because although the partitioning will clear out all teh nand, there may be stuff on the sd-ext/fat that are left over. a wipe data / factory reset clears those out too.

samsamuel said:
did you do a 'wipe data' because although the partitioning will clear out all teh nand, there may be stuff on the sd-ext/fat that are left over. a wipe data / factory reset clears those out too.
Click to expand...
Click to collapse
Did that still no progress..... :crying::crying::crying::crying:

Does anyone else have an idea?

sorry for using your thread for another Qstn.
is it possible to get an app that the files which will be downloaded from the store will donwload it directly to the sd card?

M3lloW1 said:
sorry for using your thread for another Qstn.
is it possible to get an app that the files which will be downloaded from the store will donwload it directly to the sd card?
Click to expand...
Click to collapse
Yes, it's called A2SD you will have to flash something trough CWM and partition sd card. http://forum.xda-developers.com/showthread.php?t=1716124

elias2204 said:
Yes, it's called A2SD you will have to flash something trough CWM and partition sd card. http://forum.xda-developers.com/showthread.php?t=1716124
Click to expand...
Click to collapse
But let's get on topic again what can I do to make A2SD work back again?

Please Please help me!!!! I'm turning pretty desparate by now!

just saying but:
Funnydwarf said:
That's because int2ex need its own script for wiping dalvik, using the one provided with CWM will cause bootloops: both of you can find the right one on the first post of croniccorey's thread. Just search for "Dalvik-Cache Wipe Tool" then make it run from install zip from sdcard entry.
Click to expand...
Click to collapse
If you have int2ex installed then download and run that zip because if you use normal CWM wipe-cache-dalvik, you'll get a bootloop. this may help you?
Sent from space..

[Q] Unbricking with Heimdall: not working...

Hey guys,
My Galaxy S was running Cyanogen 7 (stable release) for ages (installed by a friend), then started giving me grief with apps constantly shutting down. I flashed it with a nightly build of CM9 and things were all good for a while (except Clock kept shutting down), but then a week or two ago the phone started dropping it's mobile network connection quite often when I was using mobile data. Then it started turning off at random. Eventually it wouldn't start up, and just boot looped at the Samsung Galaxy S screen (the screen would flash occasionally). Then it stopped booting altogether, but would still enter download mode.
I'm pretty ignorant to how all this stuff works (as I didn't root/flash it in the first place), but I've managed to figure things out to the point where I've used Heimdall to flash it back to stock as explained in this thread: http://forum.xda-developers.com/showthread.php?t=1886393
However, the phone still won't boot. When I flash it using Heimdall the terminal window (Win7) tells me everything's successfully uploaded to the phone and reboots it. When the phone boots it goes to the 'Android system recovery' screen and says the following:
Successfully copied meida files.
-- Deleting files....
E:failed to mount /data (Invalid argument)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI menu for format and reboot actions.
-- Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished.
Successfully updated filesystem.
--- Wiping cache...
Formatting /cache...
E:format_volume: rfs failed on /dev/block/stl11
Cache wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TEL/system/'.
Succesasfully applied Multi-CSC.
If I use the menu option to reboot from this screen, the phone still refuses to boot. It usually gets stuck looping at the Samsung animation, but often won't even get that far.
I'm completely lost and any help would be awesome.
Thanks!

FalconOfDoom said:
E:format_volume: rfs failed on /dev/block/stl11
Cache wipe failed.
Click to expand...
Click to collapse
Flash cache.rfs from My Android Solutions

xsenman said:
Flash cache.rfs from My Android Solutions
Click to expand...
Click to collapse
I tried that and got the following...
Installing update...
Successfully installed package.
-- Copying media files...
Successfully copied media files.
-- Wiping data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data Wipe Failed
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TEL/system/'.
Succesasfully applied Multi-CSC.
Thanks for the help.

each of those errors has a different solution, Did you by any chance had had lag FIX or your system converted to ext 4 format?

xsenman said:
each of those errors has a different solution, Did you by any chance had had lag FIX or your system converted to ext 4 format?
Click to expand...
Click to collapse
Yeah I think maybe Lag Fix. No idea about ext 4 format.

FalconOfDoom said:
Yeah I think maybe Lag Fix. No idea about ext 4 format.
Click to expand...
Click to collapse
well lag fix is conversion to ext 4 format ( one and the same thing) , and not undoing it before flashing anything or factory reset can give you serious problems...you will loose your internal SD card function, unless you can reconvert it back to rfs (the original samsung format) .
What did you use to do the lagfix?

xsenman said:
well lag fix is conversion to ext 4 format ( one and the same thing) , and not undoing it before flashing anything or factory reset can give you serious problems...you will loose your internal SD card function, unless you can reconvert it back to rfs (the original samsung format) .
What did you use to do the lagfix?
Click to expand...
Click to collapse
Not sure what was used to do it. I'll try find out.

FalconOfDoom said:
Not sure what was used to do it. I'll try find out.
Click to expand...
Click to collapse
yup , do that and use that to undo the lag fix, cause anything you flash will not be able to undo lag fix, IF you have CWM recovery on your phone you should keep it, as it may come in handy in trying to format your partitions back to rfs, (if possible as last resort)

xsenman said:
yup , do that and use that to undo the lag fix, cause anything you flash will not be able to undo lag fix, IF you have CWM recovery on your phone you should keep it, as it may come in handy in trying to format your partitions back to rfs, (if possible as last resort)
Click to expand...
Click to collapse
I can't get into any recovery mode, only download mode. I've done a data wipe/factory reset as well. Is that going to screw me over?
Cheers, appreciate the help.

FalconOfDoom said:
I can't get into any recovery mode, only download mode. I've done a data wipe/factory reset as well. Is that going to screw me over?
Cheers, appreciate the help.
Click to expand...
Click to collapse
yup, thats the problem, cause when you did factory reset, it would have tried to install the previous version and that would cause this problems as your orginal would be in rfs format and when you did lagfix ( depending on what sort) you would have change the system and data to ext 4 or even swapped the data with the system ...this is why so many people end up trying to use a two partition EXT SD card to get the phone to function, losing the Internal SD card altogether

xsenman said:
yup, thats the problem, cause when you did factory reset, it would have tried to install the previous version and that would cause this problems as your orginal would be in rfs format and when you did lagfix ( depending on what sort) you would have change the system and data to ext 4 or even swapped the data with the system ...this is why so many people end up trying to use a two partition EXT SD card to get the phone to function, losing the Internal SD card altogether
Click to expand...
Click to collapse
Ah ok. I guess I was screwed from the start though, as with no access to recovery mode in the first place, I had no option to do anything but flash it?
But anyway, will finding out what was used for the lag fix determine what the end solution will be?

FalconOfDoom said:
Ah ok. I guess I was screwed from the start though, as with no access to recovery mode in the first place, I had no option to do anything but flash it?
But anyway, will finding out what was used for the lag fix determine what the end solution will be?
Click to expand...
Click to collapse
yup, too many have got into this due to Lag Fix and no solution in sight as flashing with odin /heimdall does not format partitions

Apparently it was done with Voodoo Lag Fix. Does that change anything? What are my options? Cheers heaps.

FalconOfDoom said:
Apparently it was done with Voodoo Lag Fix. Does that change anything? What are my options? Cheers heaps.
Click to expand...
Click to collapse
well, I am not too sure it will work, but you need to try using the undo lag fix in that kernel, meaning try flashing that kernel and use that kernel manger to undo the lag fix, best to read about vodoo kernel more, to see how it can be done

xsenman said:
well, I am not too sure it will work, but you need to try using the undo lag fix in that kernel, meaning try flashing that kernel and use that kernel manger to undo the lag fix, best to read about vodoo kernel more, to see how it can be done
Click to expand...
Click to collapse
Cool, cheers. My mate who rooted it in the first place is going to help me suss it out, so fingers crossed we can get it working. Thanks again.

xsenman said:
yup, too many have got into this due to Lag Fix and no solution in sight as flashing with odin /heimdall does not format partitions
Click to expand...
Click to collapse
Are you sure about this? Because, when you check the "Re-partition" option in Odin, it should erase and create the partitions again. And then they should have to be formatted. So I'm thinking that flashing an original Samsung ROM with re-partition checked should do the trick (at least, it has worked for me in the past, no matter where I came from).

tarbos00 said:
Are you sure about this? Because, when you check the "Re-partition" option in Odin, it should erase and create the partitions again. And then they should have to be formatted. So I'm thinking that flashing an original Samsung ROM with re-partition checked should do the trick (at least, it has worked for me in the past, no matter where I came from).
Click to expand...
Click to collapse
yup, very sure, as I know of too many , who had done practically everything and still cannot format their internal partitions back to rfs. And their final solution was to partition the Ext SD cards into two to get it to act like an Internal SD card

[Q] Freezing, rebooting, and can't flash stock rom (reverts to previous state)

Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?

Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM

Same problem here....

Flash factory image

USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.

Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok

Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!

Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash

USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.

violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader

USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?

violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer

Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.

violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary

USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?

violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem

USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.

violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it

USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064

violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.

Nexus 10 soft bricked, can't mount cache etc

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.