Bricked acer a100 - General Questions and Answers

Respected friends,
About a week ago my tablet got bricked , after a little research i was able to understand that the update.zip method which sadly didnt work for me. Here i would like to explain how i tried it ,
1/ download from a foreign website about 300 mb file
2/format sdcard(fat32) then operate the microsd card using mobile phone slot-transfer via usb port
3/ copy paste the file as update.zip (name shows as 'update' only)
4/put it in the tablet
5/press vol+ & power i see 'erasing cache before sd update'; and then nothing different occurred just a dead android sign
under android system recovery 3e: i get few options but none show up with results. ( in blue)
and a bunch of errors in yellow:
E: cant open/dev/block/mmcblk0p5
(no such file or directory)
e: failed to moun / cache ( no such file or directory)
e:cant mount / cache/recovery/command
e; failed to mount /cache ( no such file or directory)
e: can mount /cache/recovery/last_log
e;cant open /cache/reoery/last_log
e failed to mount / cache( no such file or directory)
e cant mount /cache/reovery/last_install
e; cant open / cache/recovery/last_install
e: cant open/dev/block/mmclk0p5
(no such file or directory)
e: failed to moun/ cache ( no such file or directory)
so that's the errors i get also very importantly i would like to share:
as you see this method obliviously seems that it didnt work and so i hadn't touchd the tablet for like a week. But a day before my first retry seemed somewhat successful: the method was same but instead it showed me a bar loading and the dead android (now the bar loading seemed some sort of progress which i m unable to achieve again and i wasn't able to put it on charge during that period of time)
Now i know there are alot of ways out there to achieve the required state but i just wasnt sure which one to follow and how ... and i hope i will be guided properly here
Regards
F22archrer

Related

Update issue

Hi folks
I tried update my android system from 3.1 to 3.2 through settings - info about tablet - system update
tablet download update and asks me to install, ive choice to install it and after that I get the Android guy with a little warning triangle on his chest , any one have a solution how to update my xoom ?
My xoom is unlocked have bootloader and its rooted.
Thanks in advice
edit:
now is worse ive took memory card out and try update again ... now xoom startsup to desktop then turning off ... turning on into recovery mode and showing erros
e: cant open /dev/block/mmcblk1p3
(no such file or directory)
e: cant mount /cache/recovery/ command
e: cant mount /cache/recovery/ log
e: cant open /cache/recovery/ log
e: cant mount /cache/recovery/ last_log
when restart thats keep looping...
ok ive sort the problem but still cant update system... the update its called 65.3.17.en.uk ... still getting android guy with triangle...
zinqzinq said:
Hi folks
I tried update my android system from 3.1 to 3.2 through settings - info about tablet - system update
tablet download update and asks me to install, ive choice to install it and after that I get the Android guy with a little warning triangle on his chest , any one have a solution how to update my xoom ?
My xoom is unlocked have bootloader and its rooted.
Thanks in advice
edit:
now is worse ive took memory card out and try update again ... now xoom startsup to desktop then turning off ... turning on into recovery mode and showing erros
e: cant open /dev/block/mmcblk1p3
(no such file or directory)
e: cant mount /cache/recovery/ command
e: cant mount /cache/recovery/ log
e: cant open /cache/recovery/ log
e: cant mount /cache/recovery/ last_log
when restart thats keep looping...
ok ive sort the problem but still cant update system... the update its called 65.3.17.en.uk ... still getting android guy with triangle...
Click to expand...
Click to collapse
You have to be stock unrooted to accept OTA update. Otherwise...well, you know.

Bootloop! & Can't mount SDCARD

I have a Glaxaxy S SCL i9003 from Spain and after flashing KPE via Odin it booted into recovery and it showed a few errors in red. Then I rebooted the phone and now it shows the first static logo (that says Samsung Galaxy S i9003) and then it loops in the second boot screen (the one with the animated samsung logo)
Booting into recovery shows this:
Code:
E:failed to mount /data (No such file or directory)
-- Copying media files...
E:failed to mount /sdcard (File exists)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
Media files copy failed
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEC/system/'
Successfully applied multi-CSC
EDIT: I've now flashed a Froyo ROM. Same problem but different errors in recovery:
Code:
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
lfs pass open fail
-- movi_checking undone!...
update media, please wait...
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.
¿Any solutions?
ktix007 said:
I have a Glaxaxy S SCL i9003 from Spain and after flashing KPE via Odin it booted into recovery and it showed a few errors in red. Then I rebooted the phone and now it shows the first static logo (that says Samsung Galaxy S i9003) and then it loops in the second boot screen (the one with the animated samsung logo)
Booting into recovery shows this:
Code:
E:failed to mount /data (No such file or directory)
-- Copying media files...
E:failed to mount /sdcard (File exists)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
Media files copy failed
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEC/system/'
Successfully applied multi-CSC
EDIT: I've now flashed a Froyo ROM. Same problem but different errors in recovery:
Code:
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
lfs pass open fail
-- movi_checking undone!...
update media, please wait...
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.
¿Any solutions?
Click to expand...
Click to collapse
Flash cf root and try to entr into cwm recovery and wipe data.
The try to flash xxkpe twice and xxkpq. Factory reset after each flash.
Sent from my GT-I9003
sirilpta said:
Flash cf root and try to entr into cwm recovery and wipe data.
The try to flash xxkpe twice and xxkpq. Factory reset after each flash.
Sent from my GT-I9003
Click to expand...
Click to collapse
I managed to get into CWM and wipe data. But after flashing kpe and kpq it does the same thing again.
assuming u done every thing right
then this will be hardware problem
take the hand st to sumsung support after flashing original firm
internal sndisk sd memory corrupted. rehot or replace.
getting boot loop in my galaxy GT-I9003
i was trying to upload android from odin, but my system os maybe corrupt. evrytime its rebooting( boot loop). samsun galxy symbol again reboot. even USB port is also not detected by PC. so kindly help me how can i restore to old or to update with new os.
kindly provide the help in this regard and also support files if any.

[Q] Need PIT File for P6210 Model US WIFI

Hello,
I need a PIT file for the Galaxy Tab Plus 7.0 US WIFI P6210 model. I'm soft bricked and reflash of the PDA file with Odin has not corrected my boot lockup. I've found and downloaded a copy of a PIT file for the P6200, but I'm afraid to load it in the event I screw the unit up worse (arguably, what could be worse than a tablet that won't run).
Any assistance would be appreciated.
Right after flashing the ODIN package, try booting into the "stock recovery" before actually booting your tab up. Clear cache and data, then try rebooting your tablet again.
Sent from my SPH-D700 using xda premium
Unless you misused a PIT when flashing before, you shouldn't have a need for a PIT to fix.
OK, I tried reflashing the Odin package (three files boot, CSC and PDA) using Odin 1.8.5 It appears to run to completion. Then when rebooting I get E: failed to mount /cache (No suchfile or directory)
E: Can't mount /cache/recovery/command
*manual Mode*
--Updating application--
E: failed to mount /efs (no such file or directory)
install application for customer: Can't mount /efs
copy application failed.
--Applying Multi-CSC--
E:failed to mount /efs (no such file or directory)
E:multi_csc:Can't mount efs
Multi-csc applied failed.
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (no such file or directory)
E:can't mount /cache/recovery/last_log
E:can't open cache/recovery/last_log
E: failed to mount /cache (no such file or directory)
Then from menu I select wipe cache partition and get
--Wiping cache...
Formatting cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p7
Cache wipe complete.
E:failed to mount /cache (no such file or directory)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:failed to mount /cache (no such file or directory)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (no such file or directory)
Then I
wipe data/factory reset
Select - YES- Delete all user data
Get the following messages:
--Wiping data..
Formatting data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
Formatting... /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p7
Data wipe complete.
E:failed to mount /cache (no such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E: failed to mount /cache (no such file or directory)
e: Can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:failed to mount /cache (no such file or directory)
E:can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E: failed to mount /cache (no such file or directory)
Then I select reboot system now
Then I get about 5-6 more red "can't mount", failed to mount" messages that go by too fast to copy, it reboots and gets to the Samsung Galaxy Tab 7.0 Plus screen and it just freezes at this point.
In a different post I stated that how the Tab became locked up was I started getting SOD Screen of Death spontaneous reboots and heated battery symptoms, sometimes on the charger, sometimes not. I could always reboot it and it would then act normally for a while (1-2 days), then start with the reboots and warm battery again. About a week ago, I woke up and found the Tab (on the charger), stuck on the Galaxy Tab startup screen. Repeated reboots kept getting back to a lockup on the startup screen. Since then, I did some reading, found a copy of Odin and loaded two different PDA files, both for the P6210 supposedly, they each mounted successfully per Odin and then kept getting similar error messages like the above and a lockup on startup at the end. After trying loading the PDA files by themselves, I then tried loading the CSC and bootloader files to an Odin run with the PDA file that came in the zip file with the CSC and bootloader files. I don't know much about Android but know a little about programming, windows and DOS. It seems like I am either missing a bunch of files or the directory structure is missing a bunch of folders, which is why I could only see that the PIT file with a repartition may be the only thing to get me out of this (assuming the repartition also loads a directory structure onto the Tab - don't know if this is the case or not). The other possibility I suppose is that there may be an electronic problem with the unit, but usually you get a complete failure and not a reboot lockup.
Just so I'm clear on the above post, as soon as I flashed the package, I unplugged the Tab from the PC and held power + sound up, got into stock recovery and cleared cache and then cleared data. The error messages above were what I got doing these things.
Same Problem
Did you ever get it out of the boot loop?
I did the same as you but to no effect - anyone know if samsung will replace these "defective" units? Clearly there is something very wrong given the thousands of hits that have the same problem.
K
i got same problem with my p6200 tab 3 month ago,
i solved with pit file
u should find pit file to solve this problem
as i saw you can get the .pit file by opening and extracting the firmware(md5 file) with winrar.
just my 2 cents
Where is the PIT file?
tzacapaca said:
as i saw you can get the .pit file by opening and extracting the firmware(md5 file) with winrar.
just my 2 cents
Click to expand...
Click to collapse
I extracted all the files - nothing with PIT. Do I need to open the img files too?
thanks,
K
Got a PIT - flashed - now can't mount system
Otherwise the cache is now there and I get an updating message right after reboot - tried the clear cache and reset - which works (no failure notices).
But...get a failed to mount /system (invalid argument) for both updating app and applying multi-CSC now and of course still in the logo boot loop.
Ideas?
Thanks!
K
Any luck on this?
Any luck?
submicron said:
Hello,
I need a PIT file for the Galaxy Tab Plus 7.0 US WIFI P6210 model. I'm soft bricked and reflash of the PDA file with Odin has not corrected my boot lockup. I've found and downloaded a copy of a PIT file for the P6200, but I'm afraid to load it in the event I screw the unit up worse (arguably, what could be worse than a tablet that won't run).
Any assistance would be appreciated.
Click to expand...
Click to collapse
Hi Submicron,
I'm on the same situation. After flashing 4.0.4, wifi became unstable. Someone said that I should flash a pit file, I did and now I'm bricked. Did you solved, or found a working pit file for the P6210? Thanks in advance.
I'm also having troubles with wifi on ICS (but not on HC, strange)... Unfortunately I own a P6200 and my .pit file won't help you.
Submicron, do NOT use a P6200 pit file, it will render you tab unusable, as I've read they have different partition layouts.
And I know it already is unusable, but anyways... ;P
I bet someone will pop here with a PIT file for P6210 soon enough, so hang in there :good:
Pit file end of 1st post
http://forum.xda-developers.com/showthread.php?t=1667886
acuratlsfan said:
Pit file end of 1st post
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
I found some.
Here
http://www.droidevelopers.com/f363/11722-[download]-ops-pit-files.html

[Q] Celkon A119Q - MT6589 CWM:E: Error Cant open Cache/Recovery Log - Possible Brick?

Hello Developers
Yesterday, i tried to do a CWM back up of my ROM and it stopped in the middle with below errors
E:Can't open/cache/recovery/log
E:Can't open /cache/recovery/log
[Read Only File System
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I Know there are many threads with this question, however mine is litte different; How?
1. I am able to mount my SD CARDs to PC
2. ADB works fine
3. Format Cache - Works fine
4. Wipe / Factory Data Reset - Works fine
5. Format System Works Fine
6. Wipe Dalvik Cache - Exits without any error
When the system reboots, I get a message "ENCRYPTION UNSUCCESSFUL" Reset phone, when clicked on Reset, phone reboots into Recovery.
ADB works fine, but i am not able to use Flash_image - Error Message file not found [it was placed in root of the memory card]
Tried to flash recovery through SP flash tools, i get an error Message - SDA SDMMC write failed
MTK Root tool does not recognize phone.
Please let me know if this is a permanent brick or is there any work around to resolve this.
My phone is only 6 months old, but cannot claim warranty because of CWM and Boot logo changed

[Q] * [Discussion : Inputs from Android Experts] *Topic: BOOTLOOP / NAND WRITE FAIL*

Hello XDA community,
I am proposing this thread as a common knowledge base on
Rampant Nand Write Fail issue.
Having searched through numerous forums here & on Internet, i concluded no working solution on it.
Many have accepted fate of their devices - Dead .. and put them in storerooms.
For rest frantic people out there eating into *help me* lines , they will soon accept the same.
So, the purpose of this thread is to Analyze why did it happen, than to expect a Resurrection .
Having been a victim of NAND WRITE Fail, here are my Final thoughts :
Characteristics of problem :
1. BootLoop
2. Typical of Kitkat OS
3. Download mode available
4. Recovery mode unavailable
- flashes open-stomach android logo for split second , BootLoop again.
5. Happened in devices that initially did not come with KNOX,
but were upgraded to Kitkat with KNOX.
Observations :
1. Changing System / USB 2.0 port - did not solve.
2. Changing versions of ODIN - did not solve
3. Re-flashing of Stock 4.4.2 ROM - Failed [NAND Write Fail]
4. Flashing of older Stock ROMs - Failed [NAND Write Fail]
- also gathered info : You can not downgrade since Kitkat Bootloader wont allow.
5. With ONLY Download mode accessible,
- Not a single tar was successfully Flashed onto device.
- All recovery tar files fail to flash [NAND Write Fail]
Conclusion to Discuss with Experts :
1. Write to NAND memory is being blocked by something [Boot Loader ? ]
2. NAND memory itself is damaged.
- Unlikely seeing the wide scale of this problem.
3. Why is Download mode accessible,
and what causes a flash-second opening into Recovery mode... then Reboot.
4. What role has KNOX to play here [Trying to root tampered with WHAT PART OF KNOX Rule] ?
5. What do we know about bootloader in this context ?
thanks for opening this thread.
I have the same problem with my M480W.
However I am able to enter recovery mode, yet nothing works ...
Code:
E: failed to mount / system (Invalid argument)
can't mount '/system' (invalid argument)
E: failed to mount / system (Invalid argument)
E: File Open error '/cache/recovery/log'
E: can't open /cache/recovery/log
E: File Open error '/cache/recovery/last_log'
E: can't open /cache/recovery/last_log
E: File Open error '/cache/recovery/last_install;'
E: can't open /cache/recovery/last_install
I havent yet tried to repartition, cause I cannot find the correct pit file for my model.
Megatronicalite said:
thanks for opening this thread.
I have the same problem with my M480W.
However I am able to enter recovery mode, yet nothing works ...
Code:
E: failed to mount / system (Invalid argument)
can't mount '/system' (invalid argument)
E: failed to mount / system (Invalid argument)
E: File Open error '/cache/recovery/log'
E: can't open /cache/recovery/log
E: File Open error '/cache/recovery/last_log'
E: can't open /cache/recovery/last_log
E: File Open error '/cache/recovery/last_install;'
E: can't open /cache/recovery/last_install
I havent yet tried to repartition, cause I cannot find the correct pit file for my model.
Click to expand...
Click to collapse
PIT Has not solved this problem on any device i know...
Per my knowledge from various posts, they all ended up finally making it a 'Paper Weight' .
Has anyone found a solution?

Categories

Resources