As of today 6th May 2011 the Eee Pad is pretty much cracked. We can flash boot and recovery and have a working root and unsecure boot and koush's Clockworkmod recovery.
The one thing we can't do is use nvflash to try custom bootloaders etc. This is because APX has been locked with a SBK and we have currently no method to get around that. Thus nvflash will fail with the error
Code:
rcm version 0X4
Command send failed (usb write failed)
It is interesting to note that the ASUS German blog claims that the bootloader and root privileges are both openly accessible, which (at the moment) is not true.
Here a few key combinations for anyone interested:
VOL_DOWN + POWER (continue holding VOL_DOWN when it starts booting until you get a prompt) = Bootloader which offers two prompted options: (1) Recovery if you press VOL_UP within 5 seconds or (2) Data wipe if you press VOL_UP later. None of these seem to offer any USB devices like fastboot etc.
VOL_UP + POWER or VOL_DOWN + VOL_UP + PLUG IN USB = NVFlash mode. It clearly is the NVFlash APX device that we see appearing, but it barfs as soon as we run any sort of nvflash on it (Many Windows and Linux versions have been tried). Please note that in this mode the screen stays completely blank and the only way to get out of it is the following option:
Hold POWER for ~10s = Forced power off. This always helps if you are stuck in some weird mode and nothing on the screen
I'll repost this in here then, as it adds a bit more info to the post above:
-Volume down button + power button for 5 secs = Life surges into the pad
Eee Pad logo + Asus logo ... keep holding buttons for 1 more sec = New screen with:
Android_WWeeepad-user bootloader < e> released by ww_epad-8.2.2.6.1-20110325".
Checking for android ota recovery
Checking for RCK... Press key <VOLUME_UP> in 5 secs to enter RCK
-Pressing up = next screen below
Booting recovery Kernal Image
Image in middle of screen and some sort of loading bar
(then goes straight to)
Exclamation mark (!) + android logo on screen
-Not touching any other buttons = screen then goes to:
Press <VOL_UP> to execute or <VOL_DOWN> to cancel wiping data (with a pulsing "Wipe data" icon in middle of screen)
-Pressing volume up = well... I didnt do that for obvious reasons.
-Pressing volume down = boots linux... and back into honeycomb normally.
-Volume up + power button dont seem to do anything.
-Power button for 5 secs = normal boot up.
-An 8-9 second hold down of the power button seems to switch it off from any screen.
'Rooting / Flashing'
I was expecting to see an HD link to some video's from spankwire
Maybe a stupid question but we do not need the dock to get an adb shell isnt it?
Great find
Need to learn about Android now, I'll chuck this in the reference thread (When i make one )
Thanks
Cpasjuste said:
Maybe a stupid question but we do not need the dock to get an adb shell isnt it?
Click to expand...
Click to collapse
No, adb works fine without the dock. Now we just want to change that $ to a #
stridger said:
No, adb works fine without the dock. Now we just want to change that $ to a #
Click to expand...
Click to collapse
Hehe thats great, just ordered one an should get it around the 5 april
The # will be easy to get and will be available very soon believe me. Ill also make an oc/uv kernel !
The root from me and paul should be out late this week early next week
its not perfect but it will do for now
Thanks.
Apache14 said:
The root from me and paul should be out late this week early next week
its not perfect but it will do for now
Click to expand...
Click to collapse
Great work
I'll create a Sticky / Rollup thread later this week.
Badwolve1
Can some one run fastboot and type...
"fastboot getvar secure"
"fastboot getvar all"
zambezy said:
Can some one run fastboot and type...
"fastboot getvar secure"
"fastboot getvar all"
Click to expand...
Click to collapse
We cannot activate fastboot on this device until we have the right nvflash tool... Once we have nvflash there shouldn't be any further obstacles.
What NVFlash commands have you tried... can you even run these?
nvflash --bl fastboot.bin --go -w
nvflash --bl fastboot.stock.bin --go -w
You would need those files in your directory... Its like booting image with fastboot without writing....
zambezy said:
What NVFlash commands have you tried... can you even run these?
nvflash --bl fastboot.bin --go -w
nvflash --bl fastboot.stock.bin --go -w
You would need those files in your directory... Its like booting image with fastboot without writing....
Click to expand...
Click to collapse
As I said, nvflash doesn't work. Not a single command.
So it doesn't seem that open after all. Nvflash has not changed this much. Have you only ran those commands in Nvflash mode.
Is the device recognised when you boot in recovery.
Sent from my ADR6400L using XDA App
zambezy said:
So it doesn't seem that open after all. Nvflash has not changed this much.
Click to expand...
Click to collapse
yes, it's either locked, or as simple as a new revision of nvflash is required.
Have you only ran those commands in Nvflash mode.
Is the device recognised when you boot in recovery.
Click to expand...
Click to collapse
Recovery and normal boot both offer ADB. We get the right device in NVFlash mode, it's just the software we have cannot talk to it after the first few bytes...
Thanks
Enviado desde mi Desire HD usando Tapatalk
My current root method will be out today
p.s. its nothing special .... in fact stupidly simple
Apache14 said:
My current root method will be out today
p.s. its nothing special .... in fact stupidly simple
Click to expand...
Click to collapse
Sweet Jesus!!!
I know Apache14 has already said this but Paul's just posted on twitter "Transformer ClockworkMod Beta and MCR Beta online this afternoon... @BumbleDroid is posting root too. ".
Very fast well done guys!
Related
Not sure what happened exactly, but while flashing the newest update for a particular persons JB ROM (he will remain unnamed) everything went fubar. Bad. Wasn't recognizing my sd drive, couldn't flash a back-up, tried one of the solutions here on XDA.....now I am without recovery. The tab will boot up, but it gets to a password screen. I have no clue what the password is.
Though I can't pay a fortune, I am willing to pay someone to fix the tab. It's all based on trust since I will send you the tablet and trust that you will return it. Of course, I will pay for return shipping also. I love my tab, but it's useless to me currently.
Please PM me if you want to take on this task. Thanks.
replied to your 'other' post but i guess it should go here
from this thread here
a hard reset wipe userdata and cache
a manual hard reset will do the same thing if you do not have the unlocked bootloader
fastboot erase if you do have the unlocked bootloader
also a stock acer update.zip but I guess you've tried that, maybe a stock ics update.zip would work
I'd be happy to take a look at your tab for free, but being on the other side of the world doesnt make that feasible unfortunately!!
however I'm sure someone else closer to you will be more than willing to help
good luck with it m8
rgds
dibb
edit:
and this from here
For anyone still having this problem, I don't see a fix on this page and I managed to figure it out for myself despite being a total noob to this stuff. To be clear, this is what happened to me: I wanted to roll back to 3.0.1 and needed to start by doing a factory reset. To do that, I followed some instructions in the A500 forum that said to do the following:
1. Power Down
2. Make sure the Screen orientation is off (slide to left while landscape mode)
3. Hold down the right volume key (Volume up (+)).
4. Hold down the Power Button.
5. When it buzzes let go of the power but keep hold of the volume up button (+)
rock the screen orientation switch quickly back and forth once.
6. Should say :
Erasing Userdata....
Erasing Cache...
After doing those steps, after I got the Erasing Userdata message I then got an error about an invalid boot file. Then when it powered back up it asked me for a password and it wasn't taking the password I previously had on the device. I was freaked out that I bricked my tablet in my very first attempt at moving to a custom ROM so I frantically searched the Internet to no avail. But then I stumbled into a help topic on the Acer UK website when doing a Google search. When I watched the video in the help topic (click here to see it) I found that this may have happened because the steps are slightly different in the video than what I was given. I used the steps below instead and successfully performed the factory reset (differences bolded):
1. Power Down
2. Make sure the Screen orientation is ON (slide to right in landscape mode so orange is showing)
3. Hold down the right volume key (Volume up (+)).
4. Hold down the Power Button.
5. When it buzzes let go of the power but keep hold of the volume up button (+)
rock the screen orientation switch quickly to the off position and leave it off (don't toggle it like the instructions above say to do).
6. Should say :
Erasing Userdata....
Erasing Cache...
This worked for me anyway; I got the Erasing Userdata then Erasing Cache instead of the error message and then a password request. I just wanted to document the solution in case anyone ever needs it again.
No luck. Doing any of these things always brings me to Skrilax's bootmenu mode, but selecting Boot Recovery just brings up Android with an exclamation point in it.
Damn.
Sent from my SGH-T999 using xda app-developers app
TFordham said:
No luck. Doing any of these things always brings me to Skrilax's bootmenu mode, but selecting Boot Recovery just brings up Android with an exclamation point in it.
Damn.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
u flashed the 3.2 stock so stock recovery,
normally u lose v8 too??
having v8 means no button combo wipe!
next test _ boot to fastboot mode and see if u can erase userdata and cache
Sent from my GT-I9300 using Tapatalk 2
TFordham said:
No luck. Doing any of these things always brings me to Skrilax's bootmenu mode, but selecting Boot Recovery just brings up Android with an exclamation point in it.
Damn.
Click to expand...
Click to collapse
And no luck with Fastboot? --Larry
Nothing. When I choose fastboot, it just shows "fastboot mode“ at the top of the screen, but just sits there.
Sent from my SGH-T999 using xda app-developers app
TFordham said:
Nothing. When I choose fastboot, it just shows "fastboot mode“ at the top of the screen, but just sits there.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
go to skrilaxcz bl thread u need to issue commands via PC. instructions for this in his op
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
go to skrilaxcz bl thread u need to issue commands via PC. instructions for this in his op
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Went there, and I'm screwed. Way to complicated for my little brain.
This sucks.
TFordham said:
Went there, and I'm screwed. Way to complicated for my little brain.
This sucks.
Click to expand...
Click to collapse
Have faith grasshopper!!!! Its just like running adb commands
Boot to fastboot mode
connect yr cable to PC
open cmd prompt from fastboot.exe folder (which is included in the sdk with adb.exe)
type in "fastboot devices"
it should return a ? - this means you're all good!
type in:
fastboot erase userdata
fastboot erase cache
fastboot reboot
to flash a recovery - u will need a recovery.img - I just used one out of civs nvFlash package
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
so now you should be fully wiped and have a recovery installed...if you get the dead android again, we'll head to the next step....and we'll need to know what rom you're actually running!!
dibb_nz said:
Have faith grasshopper!!!! Its just like running adb commands
Boot to fastboot mode
connect yr cable to PC
open cmd prompt from fastboot.exe folder (which is included in the sdk with adb.exe)
type in "fastboot devices"
it should return a ? - this means you're all good!
type in:
fastboot erase userdata
fastboot erase cache
fastboot reboot
to flash a recovery - u will need a recovery.img - I just used one out of civs nvFlash package
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
so now you should be fully wiped and have a recovery installed...if you get the dead android again, we'll head to the next step....and we'll need to know what rom you're actually running!!
Click to expand...
Click to collapse
I'm with you until "open cmd prompt from fastboot.exe folder (which is included in the sdk with adb.exe)" lol
Where do I find that folder?
When I plug in the cable to the PC, it just sits there in "fastboot mode".
You should have it if you have flashed the patched bootloader if not then see attachment:
extract the zip to say, C:\android (good idea to keep all yr flashing stuff in a folder like this)
dont actually open the folder where fastboot.exe is located, you want to press down
"shift" & right click on the folder itself to open cmd prompt -
dibb_nz said:
You should have it if you have flashed the patched bootloader if not then see attachment:
extract the zip to say, C:\android (good idea to keep all yr flashing stuff in a folder like this)
dont actually open the folder where fastboot.exe is located, you want to press down
"shift" & right click on the folder itself to open cmd prompt -
Click to expand...
Click to collapse
You my friend, are a FREAKIN' genius!!!!
I love you! (Well, you know what I mean)
That did it! I may not ever flash a ROM again now since I'm flash-scared.
It's currently downloading the official updates from Acer.
I can not thank you enough!
TFordham said:
You my friend, are a FREAKIN' genius!!!!
Click to expand...
Click to collapse
no not me m8 just spent lots of time 'unbricking' and reading everything on here
The real geniuses are the devs who made fastboot possible for us in the first place. I hate to name names cos you invariably miss someone out but posts by Skrilax_CZ, vache, strra, civato, drellisdee, waydownsouth, yaworski - have all helped me to learn more about what our tabs can actually do....as you found yourself the really hard part is understanding the language these dudes use!!!! it hardly seems 'english' at all, lol
I love you! (Well, you know what I mean)
Click to expand...
Click to collapse
aww shucks!!!! and yeh i know what u mean!!!
That did it! I may not ever flash a ROM again now since I'm flash-scared.
Click to expand...
Click to collapse
i give you a day or two before the bug strikes...
It's currently downloading the official ICS from Acer.
Click to expand...
Click to collapse
darn, make sure you can get your cpuid, see the cpuid OP in my sig - method 7 - do it as soon as you're set up.
If u need root use blackthund3rs ICSRoot-link is in that post too.
I can not thank you enough!
Click to expand...
Click to collapse
you're more than welcome, I must say its easier to help when you can be "on-call" so to speak - just pleased I got rained off from work today so I could help
I'm trying to unlock bootloader.
After command "fastboot oem unlock", I get the error:
Code:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (unknown error code))
finished. total time: 7.981s
Drivers installed. Device is new. Bought yesterday.
How to solve this problem? Thanks in advance.
What bootloader version?
Try this:
- Power off
- Power on into bootloader/fastboot mode
- on the PC: fastboot reboot-bootloader
- now try again
this usually fixes those kinds of problems for me.
HellcatDroid said:
What bootloader version?
Try this:
- Power off
- Power on into bootloader/fastboot mode
- on the PC: fastboot reboot-bootloader
- now try again
this usually fixes those kinds of problems for me.
Click to expand...
Click to collapse
Bootloader version 3.34.
fastboot reboot-bootloader did not help(( displays the same error.
I haven a friend with a new N7 delivered with 4.1.2 on that same bootloader, 3.34. He cannot update to 4.2 OTA. I even tried to sideload it for him with no luck. All I can deduce from this is that that JB version should not exist with that version of bootloader. Something seems borked.
Sent from my MB860 using xda app-developers app
How to enable debugging mode in fastboot or recovery mode? I think, that I cant unlock bootloader because debugging mode turned off. I cant turn on my device, it hangs on boot animation(like letter X).
Yesterday I download file via uTorrent. My device freezes. I turned him off. And he refused to boot(hanging on boot animation).
I've booted my device in APX mode.. How to flash bootloader on my device with NvFlash?
Edited
Sent from my SPH-D710 using Tapatalk 2
Try updating the bootloader and then trying to unlock.
Sent from my Nexus 7
Chillwood said:
How to enable debugging mode in fastboot or recovery mode? I think, that I cant unlock bootloader because debugging mode turned off. I cant turn on my device, it hangs on boot animation(like letter X).
Click to expand...
Click to collapse
Go to recovery and try a fctory reset/wipe.
Chillwood said:
I've booted my device in APX mode.. How to flash bootloader on my device with NvFlash?
Click to expand...
Click to collapse
No way to do that so far.
HellcatDroid said:
Go to recovery and try a fctory reset/wipe.
Click to expand...
Click to collapse
When I go into recovery, all I see - this is the android icon with a red exclamation mark. Nothing more..
Chillwood said:
When I go into recovery, all I see - this is the android icon with a red exclamation mark. Nothing more..
Click to expand...
Click to collapse
Hold VolumeUp and press the Power button - or something like that - and the menu will show up.
HellcatDroid said:
Hold VolumeUp and press the Power button - or something like that - and the menu will show up.
Click to expand...
Click to collapse
By this combination I go in APX mode...
I meant while the android with the red "!" shows, not while powering on.
When I'm using this combination when red !, apx mode is loading too.
Chillwood said:
When I'm using this combination when red !, apx mode is loading too.
Click to expand...
Click to collapse
Are you forgetting to release the buttons again, maybe?
HellcatDroid said:
Are you forgetting to release the buttons again, maybe?
Click to expand...
Click to collapse
Sorry for my english, I don't ynderstand you.
I did so:
Connected my device to PC.
Booted into fastboot by pressing all keys.
Selected recovery mode. Displayed "android with !".
I holded "volume up" and "power" button for 15 seconds. And then apx mode booted
Don't hold the buttons like forever.
Press them and release them again, also try some other combinations if that one doesn't work.
If you keep torturing the powerbutton, of course the device eventually reboots.
Be creative.
Use common sense.
HellcatDroid said:
Don't hold the buttons like forever.
Press them and release them again, also try some other combinations if that one doesn't work.
If you keep torturing the powerbutton, of course the device eventually reboots.
Be creative.
Use common sense.
Click to expand...
Click to collapse
Thanks... but when I'm using "wipe data/factory reset" - my device freezes, and when I restart him there is no changes, and I also can not unlock my bootloader.
I think that to unlock bootloader needs debugging mode. In recovery mode there is menu item "apply update from ADB". So I can enable adb. How to unlock bootloader or flash by this way?
veeman said:
Try updating the bootloader and then trying to unlock.
Sent from my Nexus 7
Click to expand...
Click to collapse
I can't update him, because he is locked.
I was given an a500 tablet that has a password it on that is unknown. The person that gave it to me said that there was a nag stating that an update was available and to reboot. Before the update there was not a password to his knowledge. After rebooting, the OS loads to a point where a password is required to continue.
The tablet is not rooted and usb debugging is not enabled.
I have tried downloading several full rom packages from this thread
http://forum.xda-developers.com/showthread.php?t=1816560
After downloading the rom package i rename to update.zip and transfer to a sd card and boot up the tablet holding volume up and power. When the tablet boots it displays
Erasing Cache Before SD Update....
SD update cme:recovery
--update_package=sdcard: update.zip
secure boot: image SOS checksum fail!
I then searched some more forums and was able to get my CPUID and SKB from within Ubuntu and those are
CPUID=288424342c0a217
SKB=0xDF1A0000 0x83A50301 0xBB86E703 0x7C302103
I tried using that with an EUU from above link but that does not work either.
Ultimately I would like to have root, custom recovery and custom ROM. But for right now if someone can just help me reset this to factory defaults so i can use the tablet that would be much appreciate.
jggrnaut said:
I was given an a500 tablet that has a password it on that is unknown. The person that gave it to me said that there was a nag stating that an update was available and to reboot. Before the update there was not a password to his knowledge. After rebooting, the OS loads to a point where a password is required to continue.
The tablet is not rooted and usb debugging is not enabled.
I have tried downloading several full rom packages from this thread
http://forum.xda-developers.com/showthread.php?t=1816560
After downloading the rom package i rename to update.zip and transfer to a sd card and boot up the tablet holding volume up and power. When the tablet boots it displays
Erasing Cache Before SD Update....
SD update cme:recovery
--update_package=sdcard: update.zip
secure boot: image SOS checksum fail!
I then searched some more forums and was able to get my CPUID and SKB from within Ubuntu and those are
CPUID=288424342c0a217
SKB=0xDF1A0000 0x83A50301 0xBB86E703 0x7C302103
I tried using that with an EUU from above link but that does not work either.
Ultimately I would like to have root, custom recovery and custom ROM. But for right now if someone can just help me reset this to factory defaults so i can use the tablet that would be much appreciate.
Click to expand...
Click to collapse
did you try a factory reset...volume - plus power?
The password can only be removed by wiping your tab.
To do this manually using the buttons:
1) Turn off your tablet,
2) Rotation lock to your left;
3) Press Vol+ (which is closest to the rotation lock) and power on simultaneously
4) As soon as the tablet vibrates you can release the power button and you should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
Hi gears177 and dibb_nz, thanks for responding.
gears177 before i had read dibb_nz response i would have said yes i tried a factory reset but after reading it I now know I was not doing it correctly.
That being said, I tried doing a factory reset and still have not had any luck.
This is what I see doing a normal boot of pressing the power button until the unit vibrates. The screen turns on and says 'acer' in the middle for three minutes and 18 seconds. After that it says 'android' with like a scrolling light across it for an additional 40 seconds (is this the bootanimation?) and then pops up the password screen that I cannot get past.
I then turned the unit off and attempted a factory reset. I held down the Vol+ button and the power button until the unit vibrated. I let go of the power button and continued to hold the Vol+ button while toggling the screen lock switch. The unit displayed 'acer' in the center of the screen again and then in the upper right corner said 'erasing user data' followed by 'erasing cache' I continued holding the Vol+ key the entire time. After 3 minutes and 18 seconds the word 'android' came on again and after another 40 seconds i was back at the password screen.
I then tried holding the power button with the Vol+ button until the unit vibrates. I then let go of the pwr button and began to toggle the screen lock switch until 'erasing user data' followed by 'erasing cache' was displayed. I then let go of all buttons to see what would happen and it sat on the screen with 'acer' in the middle and 'erasing user data' followed by 'erasing cache' in the upper right hand corner for well over an hour until I turned the tablet off.
Am i still not doing something correctly? Thanks again for taking the time to help.
Weird....you did everything right, not sure what the problem might be.
Think best bet may be to use the unbrick tools to reset the tab
The simplest one to start with is an update.zip. put on yr ext sd
and flash. There's one in the root guide in my sig along with lots of other
useful info.
The other way is an EUU...this requires your cupid, which you probably
don't have...it can be retrieved but involves a fair bit of detective work!
If you have any other questions about the process then ask away.
Edit: just reread thread. ...what part of the EUU failed??
The other option is to flash the unlocked bootloader, civato has a sticky
in the dev forum
In regards to the EUU method, I have downloaded this file from the Acer Stock Firmwares thread: EUUs_SBK_Acer_A500_1.016.05_COM_GEN1.
I extracted the file and then ran the PBJ20upgrade.exe file. Because I cannot turn on USB debugging I let the program time out and then when the window stating the program cannot detect an Iconia Tab Imanually put the tablet in APX mode with a paperclip pressing the reset button and power button. When the power button on the tablet lights up white i plug in the usb cable click yes to continue and enter my CPUID on the next screen. I click next and see upgrade is underway displayed. The tablet then vibrates, displays 'acer' in the center of the screen and 'entering acer download mode' in the upper right hand corner of the screen. When this happens the program immediatly displays We are Sorry! The upgrade process failed. Please follow the instructions for recovery. I have tried following the steps and clicking retry but the outcome is always the same.
I have not had time to the try the upgrade.zip you mentioned or flashing the unlocked bootloader. When I do I will report back.
The only other thing I could suggest is to run the nvflash unlocked bootloader, see sticky in dev. Try running via ubuntu, this has been known to work when windows throws a tantrum..sometimes it's a matter of perseverance with all the methods until finally it will just 'work'
Sent from my GT-I9300 using Tapatalk 2
Well I have struck out again. Trying to install the unlocked bootloader and I get some errors. I tried following your guide How to - Manual nvFlash and Civatos guide V8-UNL-ICS-HC-bootloader-MULTI-cwm. I tried with both Ubuntu and Windows and the errors I saw were the same. Running the v8.bat in windows and choosing option 1 I was presented with the following information.
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0288424342c0a217
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
Click to expand...
Click to collapse
After that did not work I then tried executing the following command in linux with root permissions. I should note that I have limited experience in Ubuntu
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xDF1A0000 0x83A50301 0xBB86E703 0x7C302103 --sync
Click to expand...
Click to collapse
The terminal spit back the exact same info I copied above.This was ran from the V8-UNL-ICS-HC-bootloader-MULTI-cwm folder. Googling NvError 0x120002 I came across this thread http://forum.xda-developers.com/showthread.php?t=1765222 but I dont feel it is the same issue because mine says bct write failed and not partition table is invalid.
Any ideas?
Bct errors - u must dump, save and then use yr own bct...how??? Run blackthund3rs apxflash tool, it has an option to dump yr bct...fingers crossed u shld be all good after doing that
Sent from my GT-I9300 using Tapatalk 2
Have you tried using a paper clip or something small to factory reset the Tablet? I know there is a small hole somewhere which should work. Good Luck!
THANKS
Thanks. This was exactly what i needed. I appreciate it.
dibb_nz said:
the password can only be removed by wiping your tab.
To do this manually using the buttons:
1) turn off your tablet,
2) rotation lock to your left;
3) press vol+ (which is closest to the rotation lock) and power on simultaneously
4) as soon as the tablet vibrates you can release the power button and you should start to switch rotation lock left and right till you see
erasing userdata...
Erasing cache...
Vol+ is still pressed;
5) the tablet starts to format
6) your tablet will be as clean as it can be.
Click to expand...
Click to collapse
I was fiddling with my device (not rooted) and I gave the wrong command in fastboot:
Code:
fastboot erase cache
.
I then gave
Code:
fastboot continue
This was surely a **** up but I don't understand why erasing the cache partition seems to have broken the recovery/fastboot mechanism (I understand why it probably broke android though).
My device is now stuck, whenever I turn it on it goes directly in the recovery 'splash screen' showing 'no command'.
My understanding is that from the recovery 'splash screen' I'm supposed to press some keys combination to get to the recovery menu, but none seem to work.
Pressing both volume up and down for like 10 second reboots the device, so I assume it's not an hardware button problem.
Pressing power + volume up with the device powered off does not go to fastboot (but I'm quite sure it did before).
Neither adb devices or fastboot devices detect the device when connect to my linux pc by usb.
Any suggestion?
Any solution?
I have done exactly the same as you, and am now stuck on the 'no command' screen with the dead android icon flashing every 5 or so seconds. Did you manage to find anyway out of this. I have tried numerous button combinations and I cannot get to either fastboot or recovery, so my tablet is basically bricked. Any help would be immensely welcome.
LordCik said:
I was fiddling with my device (not rooted) and I gave the wrong command in fastboot:
Code:
fastboot erase cache
.
I then gave
Code:
fastboot continue
This was surely a **** up but I don't understand why erasing the cache partition seems to have broken the recovery/fastboot mechanism (I understand why it probably broke android though).
My device is now stuck, whenever I turn it on it goes directly in the recovery 'splash screen' showing 'no command'.
My understanding is that from the recovery 'splash screen' I'm supposed to press some keys combination to get to the recovery menu, but none seem to work.
Pressing both volume up and down for like 10 second reboots the device, so I assume it's not an hardware button problem.
Pressing power + volume up with the device powered off does not go to fastboot (but I'm quite sure it did before).
Neither adb devices or fastboot devices detect the device when connect to my linux pc by usb.
Any suggestion?
Click to expand...
Click to collapse
Sadly, no
I never managed to solve this. I tried everything without luck. I even contacted Asus, and they confirmed me that the right button combination for this device is the following: press and keep pressing the power button with volume up for 3 seconds, then let the volume button go and keep pressing the power one. A recovery menu should appear at that point, but never did for me.
I still don't understand how deleting that partition could break the recovery mechanism, but this seems to be the case.
If you (or anyone else for that matter) ever manage to solve this, I would appreciate if you could write about it here: my device is currently gathering dust in its box
Thanks
Thanks for that. I'll let you know, if I have any luck.
Did you try using the SP Flash tool at all? I have tried this, but it claims the scatter file is invalid and I can't find a way around that.
StevePC said:
Thanks for that. I'll let you know, if I have any luck.
Did you try using the SP Flash tool at all? I have tried this, but it claims the scatter file is invalid and I can't find a way around that.
Click to expand...
Click to collapse
I will have to look into it, since I'm not familiar with this tool. Where did you get the scatter file?
Sadly right now I don't have the tablet with me, and I won't for several days. When I will, I'll give this a try and report back.
LordCik said:
I will have to look into it, since I'm not familiar with this tool. Where did you get the scatter file?
Sadly right now I don't have the tablet with me, and I won't for several days. When I will, I'll give this a try and report back.
Click to expand...
Click to collapse
You can get this tool here https://spflashtool.com/
As I understand, the scatter file is in the zip of a ton. So, I downloaded this: ASUS ZenPad 3S 10 (Z500M) FOTA WW_V14.0210.1806.33, unzipped it and used the scatter file from that, but it comes up as invalid. This may be because this isn't the right sort of Ron file, I'm not sure. So, at the moment, I'm stuck.
Still trying
I've used information from the following sites, but have still not solved. Let me know if you have any luck.
http://flash-tool.com/instruction.html
https://firmwarex.net/asus-zenpad-3s-10-z500kl-z500m-official-firmware/
http://bbs.tecno-mobile.com/forum/rom/97373-how-to-unbrick-soft-and-hard-bricked-mediatek-mtk-android-phone
https://devsjournal.com/how-to-unbrick-mediatek-device.html
have u find any solution? i have the same problem
LordCik said:
I was fiddling with my device (not rooted) and I gave the wrong command in fastboot:
Code:
fastboot erase cache
.
I then gave
Code:
fastboot continue
This was surely a **** up but I don't understand why erasing the cache partition seems to have broken the recovery/fastboot mechanism (I understand why it probably broke android though).
My device is now stuck, whenever I turn it on it goes directly in the recovery 'splash screen' showing 'no command'.
My understanding is that from the recovery 'splash screen' I'm supposed to press some keys combination to get to the recovery menu, but none seem to work.
Pressing both volume up and down for like 10 second reboots the device, so I assume it's not an hardware button problem.
Pressing power + volume up with the device powered off does not go to fastboot (but I'm quite sure it did before).
Neither adb devices or fastboot devices detect the device when connect to my linux pc by usb.
Any suggestion?
Click to expand...
Click to collapse
email me if any solution .
thx have anice day
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Damn, that's a bit unlucky, this March update said it would make recovery from a loop after OTA update easier to recover from, which might just have helped you. Sorry not sure how to help fix at present.
you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images
harpoon said:
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
Click to expand...
Click to collapse
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.
kt-Froggy said:
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.
Click to expand...
Click to collapse
Thanks for your response.
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
=============
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
=============
yenkoPR said:
you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images
Click to expand...
Click to collapse
Will this work even though I cannot see the device via adb? AND the device state is "locked".
harpoon said:
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
Click to expand...
Click to collapse
Dang... :\ Yeah, the last error means you don't have OEM unlock enabled. So, you can't flash the bts image via fastboot. One last thing I could think of is trying to get to recovery by the button combo. Although, if you are correct in saying you don't have USB debug enabled, it won't do much good, i.e. you won't be able to flash an OTA... :\
While device is OFF, press and hold Volume-Up button while pushing Power button to boot.
Your device will now be in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time to see the recovery menu.
can you try this command on bootloader:
fastboot OEM unlock
harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)
Rudter said:
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)
Click to expand...
Click to collapse
Nothing ! ..
my ph-1 still into the drawer ! .