Database Users

[ROM] Stock rooted 3.2.1 a501_4.483.01_EMEA_TMPL 20-01-12

A Present from Moscow!
Acer Stock HC 3.2.1 Acer_A501_4.483.01_EMEA_TMPL
Rooted
Busybox
Superuser
Data/app folder added with a couple of apps to check root
All stock ACER apps included
You know the procedure for flashing. If not, here they are again, as it seems some people don't know.
You MUST do the wipes and formats.
Installation:
Due to issues with Version 1.7 of recovery, you may get stuck at the boot animation. Highly advise you to downgrade your recovery back to Version 1.5. It seems that some things do not get wiped and formatted correctly.
1. Wipe User Data
2. Wipe Cache
3. Wipe DalviK
4. Wipe Battery Stats
Note: Optional Formatting.
If you really want to remove EVERYTHING in Internal Memory, at this point, go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
If you want to save all the things like downloaded files, apps, pdf's etc, then DO NOT enable this toggle, and just proceed to the Format steps.
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
Select Go Back and select Install from Zip File (for those of you who refuse to update their recovery, select Install zip from SD)
Link Re-established.
DOWNLOAD
Alternate Server
DOWNLOAD
MD5 df253e3f8825197c08a1f0a0b8c24a81

Doesn't work for my tablet, can't get past boot animation.
Did a full wipe, cache, dalvik and battery stats and flashed it now a second time - all i get is only the boot animation.
Any suggestions?
Sent from my GT-I9100 using XDA App

Thanks! I will give it a try either tonight or this weekend and see how it goes for me.
Mucho appreciated!

DerTeufel said:
Doesn't work for my tablet, can't get past boot animation.
Did a full wipe, cache, dalvik and battery stats and flashed it now a second time - all i get is only the boot animation.
Any suggestions?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Not sure what your definition is of a "full wipe", but instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1390860
I can guarantee you that if all you can get is to the boot animation that the problem is "pilot error".

DerTeufel said:
Doesn't work for my tablet, can't get past boot animation.
Did a full wipe, cache, dalvik and battery stats and flashed it now a second time - all i get is only the boot animation.
Any suggestions?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Try downloading the ROM again. It might be a bad download.

DerTeufel said:
Doesn't work for my tablet, can't get past boot animation.
Did a full wipe, cache, dalvik and battery stats and flashed it now a second time - all i get is only the boot animation.
Any suggestions?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Well, here's what I suggest. Look in my original post. I added the full instructions from my other rom.
It seems now days, the old 3 wipes just don't do a good enough job, you also have to do the formats as well.
(I thought I would be lazy and do only the 3 wipes last night, guess what? Stuck at boot animation) Did the full wipe and format, and it works as advertised.
EDIT: Guess what? This morning, I cannot flash anything, or I should say "hit and miss". Not even my daily driver. Connected to Recovery I believe.

Link re-established. Nothing wrong with the download.
If you have issues, downgrade your recovery back to version 1.5.
The issue with version 1.7 is "hit and miss". Sometimes it works, sometimes it doesn't.

Acer_A501_4.483.01_EMEA_TMPL Differences from A501_4.031.24_4.066.29_COM_GEN1?

STASMK said:
Acer_A501_4.483.01_EMEA_TMPL Differences from A501_4.031.24_4.066.29_COM_GEN1?
Click to expand...
Click to collapse
Well, I haven't checked the comgen1 yet (had to figure out the recovery problem first). Will root it and check it in a bit.
But, so far, I see 4 or 5 language supports are missing from the TMPL. Arabic and Aisian mostly. Also, on install the default is Polish (not a biggie as you can change it).
Other that that, it has a few extra files when compared to 3.2.
It seems I can get 1 or 2 extra sat's on gps when comparing to HC 3.2. But maybe because it's a clear day here.
Also, Acer included a couple new apps. One of them some 3d photo browser that force closes the first time you use it. Then it works normally, sort of. Seems it loses it's images off and on. Nice job acer. And, it's butt ugly. Wonder who the rocket scientist was that chose that app?
I'm not going to mod this one, but I will with the comgen1. Overall it runs good I think.

STASMK said:
Acer_A501_4.483.01_EMEA_TMPL Differences from A501_4.031.24_4.066.29_COM_GEN1?
Click to expand...
Click to collapse
What is that A501_4.031.24_4.066.29_COM_GEN1 build ?
I am only aware of that Acer_A501_4.066.29_COM_GEN1 posted by Vache, but how did you figure 4.031.24 is upgraded to that one ?

Sorry. My Bad
I was thinking about the a501_4.510.01_Com_Gen1H that was leaked out yesterday.
I already rooted it and such, but it seems to be a "Demo" version from a couple of months ago. Not only does it have a strange installer script, but a strange directory structure also. 3g also is partly working.
So basically it's of little use.

Moscow Desire said:
Sorry. My Bad
I was thinking about the a501_4.510.01_Com_Gen1H that was leaked out yesterday.
I already rooted it and such, but it seems to be a "Demo" version from a couple of months ago. Not only does it have a strange installer script, but a strange directory structure also. 3g also is partly working.
So basically it's of little use.
Click to expand...
Click to collapse
Could You provide the MD5 just to check if the download is correct (it is very slow)?
Thanks

v11lemans said:
Could You provide the MD5 just to check if the download is correct (it is very slow)?
Thanks
Click to expand...
Click to collapse
I get one in a few minutes.
The issue, is the U.S. is shutting down all the file servers due to piracy. MegaUpload, MultiUpload (server end) Now all that's left are the slow ones. Took me 45 minutes to download today.
MD5 df253e3f8825197c08a1f0a0b8c24a81

Yeah, its a pain in the bum alright, some of the slower ones already have "removed or taken down because of copyrighted material" messages coming up (deposit files)... A couple have the servers offline - upload king and upload here.
This is gonna be a major pain in the bum if the close down or lock file sharing sites, and the sites themselves may end up locking things down and removing anything they see as copyrighted material, even if its not....
Took me 10 minutes to download an 8mb kernel... I'm gonna end up a bald man before I get this rom....
And then the download stuffs up and I have start ALL OVER AGAIN.... Then to add insult to injury I have to wait 20 minutes.....

ultramag69 said:
Took me 10 minutes to download an 8mb kernel... I'm gonna end up a bald man before I get this rom....
.
Click to expand...
Click to collapse
I'm not quite that bad off (still have all my hair)!
I'm going to look around for some Russian servers. Or something. I noticed one other place, but I have to find it again. They'll probably shut it down also soon.
Next thing you know, they'll shut down GitHub, and all dev comes to a standstill.
Also, I noticed today, XDA is almost at a complete stop. And I can guess who's responsible for THAT!

It's running now, needed to format it to make it work.
Didn't have to format when i was installing v3.2.
Thanks for the help
Sent from my GT-I9100 using XDA App

I think there's going to be a "knee jerk" re-action to the mega upload affair.... Be a REAL pain if we can't continue doing what we want with our devices...
Shame too, just getting good with the new A501 roms coming out...
Hate I might need to revert to stock to pick up ICS upgrade because the chefs can't share their flavours...
Chefs are great for sharing these awesome roms....

ultramag69 said:
I think there's going to be a "knee jerk" re-action to the mega upload affair.... Be a REAL pain if we can't continue doing what we want with our devices...
Shame too, just getting good with the new A501 roms coming out...
Hate I might need to revert to stock to pick up ICS upgrade because the chefs can't share their flavours...
Chefs are great for sharing these awesome roms....
Click to expand...
Click to collapse
Well, I just know enough to make me screw things up
I found another place. 30 min download, But you have to give your e-mail for the link. Not really an issue. 3 more servers went down today.
Seems all that's left, is the small file hosts, and they're starting to limit file size.
I suspect, some serious **** will hit the fan in the next coming week, The US can't keep going on this crusade forever. Otherwise, there won;t be a site left except "foxnews" and Facebook.

IS there a Kernel i can use for overclocking?
Using CPU Master i can only choose 1000MHz, had it overclocked to 1.4GHz with the previous ROM.
Sent from my A501 using XDA App

DerTeufel said:
It's running now, needed to format it to make it work.
Didn't have to format when i was installing v3.2.
Thanks for the help
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
No problem and glad it's running.
Not sure what is going on, but in past 6 months, it seems like we now have to format things. I didn't in the past, but now I must.
Well, it is 2012, so things change.
If you have issues with the Rom, it is pure stock HC 3.2.1. I changed nothing in it. Only SU and busybox and removal of the bootloader blob and recovery. So if a game doesn't run, there is nothing I can do about it. It's an Acer deal.
However, I do have one on my notebook, that has "0" acer stuff in it.

[Q] Evo started rebooting randomly

Over the past couple of weeks, my Evo has started to reboot at random times. Sometimes it will go for a few days, other times, it will reboot several times a day. I've had it happen in the middle of using the phone, and in the middle of the night. Nothing has changed on the phone from an app standpoint besides updating the ones I have installed already.
I do have my phone rooted, running a stock ROM from XDA that has apps2sd enabled on it, however, I have been running in this manner for almost a year with no hiccup. I've tried looking at the log files, but they seem to be stored in volatile memory and blanked out/overwritten when the device reboots, so finding an exception or problem on the device after a reboot doesn't seem possible (or is it, and if so, how?).
Anyone with any thoughts/suggestions, please chime in. I have had my Evo for over 2 years, and am loving it still now as much as the day I got it (yes, I do have GS3 envy from my wife's phone, but the Evo does what I need it to do, and does it well)...
Thanks in advance for any tips/suggestions.

Not sure which recovery you have, but if it's Amon Ra or Smelkus, go to recovery, and do Fix Permissions (Under Others) and Repair EXT (Under Partition)
If it were me,and that didn't work, I'd do a backup of all my apps, data, messages, etc and the a complete wipe and reflash the ROM.Basically start over.
I've run a lot of ROMS that seemed to deteriorate over time and a fresh flash fixes it every time.

Are you still running it on stock battery that came with the phone? Could be that its nearly dead and you need a replacement.
Also you're rooted, apart from a2sd you use any other tweaks/mods?

HipKat said:
Not sure which recovery you have, but if it's Amon Ra or Smelkus, go to recovery, and do Fix Permissions (Under Others) and Repair EXT (Under Partition)
If it were me,and that didn't work, I'd do a backup of all my apps, data, messages, etc and the a complete wipe and reflash the ROM.Basically start over.
I've run a lot of ROMS that seemed to deteriorate over time and a fresh flash fixes it every time.
Click to expand...
Click to collapse
I'm using Amon Ra, will i lose anything from doing fix perms and repair ext? (I will do a full nandroid first, of course).

Robobob1221 said:
Are you still running it on stock battery that came with the phone? Could be that its nearly dead and you need a replacement.
Also you're rooted, apart from a2sd you use any other tweaks/mods?
Click to expand...
Click to collapse
Yes, still on the original stock battery. The most recent reboot happened in the middle of the night last night, while it was charging, though...No other tweaks/mods have been made in the time before this started occurring...the phone had been unchanged (minus app updates) for months.

dmolavi said:
Yes, still on the original stock battery. The most recent reboot happened in the middle of the night last night, while it was charging, though...No other tweaks/mods have been made in the time before this started occurring...the phone had been unchanged (minus app updates) for months.
Click to expand...
Click to collapse
Could be an idea to get a new battery, you can get decent cheap ones on amazon or ebay I think, and see if that stops the reboots.
As for fixing permissions and reparing ext you wont lose any data
Out of curiosity what ROM were/are you running when it started?

Robobob1221 said:
Could be an idea to get a new battery, you can get decent cheap ones on amazon or ebay I think, and see if that stops the reboots.
As for fixing permissions and reparing ext you wont lose any data
Out of curiosity what ROM were/are you running when it started?
Click to expand...
Click to collapse
Hmm...I'm using Amon-RA 2.3 (from http://forum.xda-developers.com/showthread.php?t=705026) and there is no "fix permissions" or "repair ext" under "other"...Is there a newer/better version available?
I am using the stock rooted a2sd ROM from Captain Throwback, have been for ages...

Yes, SmelkusMOD 4.3.
It's based of of RA Recovery, but includes some major improvements to the original. If you don't find it yourself I'll get you a link
Edit: http://forum.xda-developers.com/showthread.php?t=1661543
Here's link to the thread.
All the different types are just themes all have the same function
An enviousOG

dmolavi said:
I'm using Amon Ra, will i lose anything from doing fix perms and repair ext? (I will do a full nandroid first, of course).
Click to expand...
Click to collapse
No, EXT Repair and Permissions do not delete anything from your SD Card. It's kind've like running a disk check on your computer
---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------
dmolavi said:
Hmm...I'm using Amon-RA 2.3 (from http://forum.xda-developers.com/showthread.php?t=705026) and there is no "fix permissions" or "repair ext" under "other"...Is there a newer/better version available?
I am using the stock rooted a2sd ROM from Captain Throwback, have been for ages...
Click to expand...
Click to collapse
EXT Repair is under Partition SD Card.
Fix Permissions should be under Others or something similar and yeah, Smelkus is the way to go

Discussion - Stuck at Sammy Logo Issue on Official Jellybean ROMs - Discussion

Mates, the problem is there, we should admit that, had it on Galactus rom twice ( reflashed the rom again after full wipes to make sure ), and had it also on the stock LSZ with its stock kernel, and also on Cassie's rom.
Nothing solves the problem apart from wiping data.
Is it the preload ? the kernel ? defective JB from Samsung ? I really don't know.
The only thing I would really like to mention is that on Cassie's rom, had the issue surprisingly occuring on odd restarts not the even ones ! the first restart gets stuck, the other goes on !
Tried all the tricks in the book (restart to recovery, reinstalling bootloader, overinstalling the same rom, wiping everything keeping data, nothing worked.
Unless data gets wiped, the problem persists.
BTW, I had the same problem on all the previous leaked versions before the official ones.
Back to ICS while discussing here.....

i have no bootloop on the LSZ. been on it for couple of days and many reboots later....no issue.
i flashed the .md5 file from samfirmware link via odin ...let it boot and settle....then flashed philz LM5 4.35 kernel for root...
then i changed my build.prop for lcd density and installed the xposed installer and xposed app settings etc...
no lag and no bootloop.
also uninstalled a couple of the german apps that came with the firmware.
looks good!!

I (luckily) resolved it by
pressing POWER BUTTON for about 5 seconds while on samsung splash screen bootloop...
or
reboot to recovery>>advance>>reboot to recovery(again)>>>reboot system now..
or
making nandroid backup and restoring it
Recognized Distributor™

I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis

I think bootlops are caused by the use of /preload partition for some .apk since JB rom like xxls7 that didn't use preload like RRv3 aren't affected by them.

Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2

zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Exactly, especially the 7 sec power button restart, almost 100% bootloop state.
Sent from my GT-N7000 using Tapatalk 2

pbirdas said:
I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis
Click to expand...
Click to collapse
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2

jaguaralani said:
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ohh...I see.. This is what is keeping me away of flashing the official ROM.. i will just wait for the issue to be found before i flash it.. Thanks for the info!!

Official JB is quite stable.. on XLSC (ultimate rom) my phone face sudden bootloop while it on my pocket, longest use on XLSC is 2 or 3 days before it bootloop by it self...only can be solve by restoring nandroid backup, something happen when I make force reboot or force shutdown...
But on XLSZ I only got bootloop on 1st reboot (after force reboot & force shutdown)....on 2nd reboot my phone will reboot normally..and never face suddent bootloop.. But yes bootloop bug is still there..
My XLSZ now is on:
+stock kernel
+rooted
+odexed/stock official
+some system apps is on preload partition
+no system/data restored by TB..
Sent from my GT-N7000 using Tapatalk 2

Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium

zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ok....so I tried both your methods of getting a boot loop.
1. After holding down power button till it came to the Sammy screen, it stuck there. I held power button down until screen went blank and let go....within a second phone came back on and rebooted normal.
2. Same as what happened in 1.
But this happened before where it would sometime get stuck at Sammy logo..in other versions of android and even inn my i9000 before....but it boot up fine after so no problems here.
Sent from my GT-N7000 using Tapatalk 2

ssss69 said:
Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for the info mate, this clearly shows that it is a Samsung problem.
Sent from my GT-N7000 using Tapatalk 2

Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Sent from my GT-N7000 using Tapatalk 2

jaguaralani said:
Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Click to expand...
Click to collapse
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.

I've never had bootlop with LS7 and LSA and LSZ only few bootlops with lsc but i do wipeing cash and dalvik and works again
Verstuurd van mijn GT-N7000 met Tapatalk

kopitalk said:
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.
Click to expand...
Click to collapse
Thanks for the info mate...

today I'm updating my friend phone from stock ICS DXLR5 to XLSZ (free of chrge) using PC ODIN..while on stock XLSZ kernel I make a force reboot on my friend phone and its stuck on N7000 logo and boot find after second reboot (without any wipe or restore) , same things happen to my phone to...after that flash new Philz XLSZ kernel on my phone & my phone too from stock recovery...and what is surprise me is my friend phone survive when I make a force reboot but my phone not...maybe its time to reflash, will report again..

I have faced this problem many times before and the only cure sometimes was to make a nandroid backup and restore it
but if the backup failed at the data partition that means the data is corrupted and you must wipe your data ...
but one solution for sure worked for me with all roms I've tried ... do not use the preload partition ....
I do not use it at all ... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.

Super Prince said:
... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.
Click to expand...
Click to collapse
Care to share how to do this?

[Q] Is it ok to restart your phone if nandroid restore is taking WAY too long?

I'm on GS4 i9505, cm10.2 and twrp 2.6.0.3
tl;dr at the bottom of this post!
Ok so this is what happened. I flashed cm10.2 on my S4 i9505 2 days ago. Today, there was an update. So I updated it through goo manager. But things didn't go that smoothly. When goo manager rebooted into recovery for me, it said something openrecovereyscript, installing zip. Halfway through the installation, it would restart into recovery again, and the same 'openrecovery blah blah installing zip' came up. This happened for like 5 times before the installation was done. So I rebooted. Then, I realised that the update had some bugs where the back button only works on certain apps. So I rebooted into recovery manually. First attempt at restoring backed up cm10.2, it said 'unable to mount /system' then I tried several times, finally, the restore was going fine. But towards the end, the phone shutdowns on its own... So I rebooted the phone, but it was stuck at the Samsung boot screen, so I rebooted into recovery. This time, it was stuck at teamwin blue splash screen for about 5 mins, but I got into recovery at the end. Then the same thing happened. It shutdowns towards the end... So I rebooted into recovery again. I waited about 3 mins at the teamwin splash screen before the ui loaded up. Then I went straight into restoring. Restoring boot usually takes 1 seconds, but it took 204 seconds. Now I'm on 'Restoring system' and it has taken more than 30 minutes... It usually takes 1-5mins. Should I do a battery plug then attempt to restore again? Would I risk bricking my phone? Please help...
TL;DR: I'M HAVING PROBLEMS RESTORING, I'M ON MY 5TH ATTEMPT RESTORING A BACKED UP CYANOGENMOD 10.2, ITS OVER 30 MINUTES NOW AND I'M STILL ON 'RESTORING SYSTEM'. NO THE PHONE IS NO HANGED, I CAN LOCK/UNLOCK AND SCROLL THROUGH THE LOG.

Try restoring it through odin by flashing stock rom then doing nandroid backup if u want....
Sent from my A500 using xda app-developers app

ok It just said restore failed probably while I was typing this thread(I took like 5 mins to type it). What might be causing this fail? So far I've gotten 'unable to mount system' and 'unable to mount cache' errors. MIGHT have gotten others but I just didn't' read the log... HELP PLEASE!

Better u downgrade to u r previous version else flash the stock rom of that version. .....
Then try rooting again and then update. It could be because of writing files in a wrong manner.
Sent from my Xperia U using xda app-developers app

hamsam said:
Try restoring it through odin by flashing stock rom then doing nandroid backup if u want....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Is it possible to just restore that cm10.2? I actually have stock rom backed up but haven't tried restoring because it's outdated(last week). And also because I just tried restoring cm10.2 again. It failed to restore system because of 2 errors: unable to mount /system and unable to locate partition by back up name : "preload". I did change my back up name prior to restoring from the default(date) to "cm10.2". Could this have caused it? Anyway, restoring boot too 212 seconds again, I'm sure restoring system would be a fail but I'd have to wait another 40 mins before the fail to restore error comes up, can I just do a battery plug without risking a brick?

GUYS! You are missing the point! The main question here is, I am currently in the middle of restoring. I KNOW it's gonna fail when it reaches restoring system and say 'Unable to mount /system' and Unable to locate partition by back up name: 'preload' '. But it will only say this 40-50 mins into the restoration, ofcourse, I want to know if you had similar experience, causes, solutions. But right NOW the most important thing is, Can I restart my phone WHILE it is restoring?

Ok, turns out, you CAN. Now my only problem is why can't you mount /system... I can't tick the box under 'Mount' on TWRP!

Well i have pulled battery many time while restoring backup but i have different phone than you......i think you can pull the battery by the way your phone is already soft bricked if you are getting bootloop
Sent from my A500 using xda app-developers app
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
Try changing to cwm recovery
Sent from my A500 using xda app-developers app

hamsam said:
Well i have pulled battery many time while restoring backup but i have different phone than you......i think you can pull the battery by the way your phone is already soft bricked if you are getting bootloop
Sent from my A500 using xda app-developers app
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
Try changing to cwm recovery
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
That is counted as a soft brick? wtf? I can't boot because the phone messed up during restore and the system doesn't contain any files(when I go to back up it says system is 0MB). I went into advanced wipe and wiped system. Now I've got something inside(51MB) I THINK it is able to mount /system now, but my phone's screen is empty but not offed while restoring. It doesn't wake up to any buttons...

Android is starting... Optimising app xx of xx on every boot

Hi all,
Have had my Nexus 10 with a few years now and rooted it not long after I got it, stuck with stock rom though.
All was fine until I updated to the latest LMY49H Build using NRT (Nexus Root Toolkit) which I always do and it has never let me down.
But with this update I get the swirling balls, Android boot screen then about 10 minutes of "Android is starting... Optimising app xx of xx". I have wiped via settings, via recovery (TWRP and stock), Flash Stock and Unroot (NRT), Root (NRT which wipes data), cleared cache, dalvik, data using TWRP but every time I end up with this optimising apps screen.
I have tried restoring previous versions at setup (apps, wallpapers etc.) and I have skipped all setup options for a clean fresh copy but always with the same result.
I have been looking around but didn't find someone running stock rom with the same problem, If I missed it then I'm sorry.
Please someone help me as I'm going on a trip soon and will need my tablet!

Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk

psiphi said:
Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk

mr.natural said:
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.
Click to expand...
Click to collapse
Sorry, I know what flash memory is, I mean I didn't know what he meant by copy using TWRP.
I may try flash the previous LMY49H ROM then
psiphi said:
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK cool, thanks for clearing that up..
This literally just started when I updated to the new ROM (LMY49J). I have done a full wipe already so hard reset shouldn't be a problem, nothing left on it now anyway. Think I may have done it already tho
Before the update I had a full TV series and a few movies saved into it and it had no problems playing/saving anything. Think I may try stock flash & unroot with LMY49H and see how that goes.. I'm away from it at the moment so hopefully will try tomorrow.
I have a feeling it is saving files though, displayed my old wallpaper when I restored from previous tablet option on setup. Must be saving this picture somewhere after initial download at setup. It is booting up eventually like, just after it optimizes the apps, maybe 5-10min.
What other issues could I be having?

You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk

psiphi said:
You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again

fado5ster said:
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again
Click to expand...
Click to collapse
You have to copy something in recovery mode with twrp. From a different directory (or usb stick to your device) and then reboot to see if it is still there.