[MIPAD_1] [APX-MODE] How to Recover. - Xiaomi Mi Pad Questions & Answers

I think my MiPAD is totally bricked. Tried Pad shorting method which is suggested in XDA and other forums. No luck...
No recovery, boot logo or LED while charging (checked battery & its healthy).
Getting detected in MIFLASH tool (as Device "0", but that is enough for job to be done) but flashing ending in an error "Unspecified error(0x80004005; failed execuiting command 17 NvError 0x120002" .. (yeah i have used untouched mocha image).
Yes i tried many times, with different PC, cable and calm mind.
it is getting detected in APX mode (stable connection)....
Flash Log :
[00000BA4]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000BA4]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000BA4]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[00001740]0 0.00 execute C:\FLASH\nvflash_all.bat
[00001740]0 0.16
[00001740]0 0.16 $pushd C:\FLASH\images
[00001740]0 0.16
[00001740]0 0.16 $nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
[00001740]0 2.14 Nvflash 4.13.0000 started
[00001740]0 2.14 chip uid from BR is: 0x34001001740db0c108000000080102c0
[00001740]0 2.14 rcm version 0X400001
[00001740]0 2.14 Skipping BoardID read at miniloader level
[00001740]0 2.14 System Information:
[00001740]0 2.14 chip name: unknown
[00001740]0 2.14 chip id: 0x40 major: 1 minor: 1
[00001740]0 2.14 chip sku: 0x0
[00001740]0 2.14 chip uid: 0x00000000000000000000000000000000
[00001740]0 2.14 macrovision: disabled
[00001740]0 2.16 hdcp: disabled
[00001740]0 2.16 jtag: disabled
[00001740]0 2.16 sbk burned: false
[00001740]0 2.16 board id: 0
[00001740]0 2.16 warranty fuse: 0
[00001740]0 2.16 dk burned: false
[00001740]0 2.16 boot device: emmc
[00001740]0 2.16 operating mode: 3
[00001740]0 2.16 device config strap: 0
[00001740]0 2.16 device config fuse: 0
[00001740]0 2.16 sdram config strap: 0
[00001740]0 2.16
[00001740]0 2.16 RCM communication completed
[00001740]0 2.16 BCT sent successfully
[00001740]0 2.16 odm data: 0x49c000
[00001740]0 2.16 downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
[00001740]0 2.16 sending file: bootloader.bin
[00001740]0 2.16
[00001740]0 2.16 - 1048576/4194304 bytes sent
[00001740]0 2.16 \ 2097152/4194304 bytes sent
[00001740]0 2.16 | 3145728/4194304 bytes sent
[00001740]0 2.16 / 4194304/4194304 bytes sent
[00001740]0 2.16 bootloader.bin sent successfully
[00001740]0 2.16 waiting for bootloader to initialize
[00001740]0 2.16 bootloader downloaded successfully
[00001740]0 2.16 ML execution and Cpu Handover took 1 Secs
[00001740]0 2.16 setting device: 2 3
[00001740]0 2.16 creating partition: BCT
[00001740]0 2.16 failed executing command 17 NvError 0x120002
[00001740]CScriptReport:oWork(420): Unspecified error(0x80004005)
[00001740]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00001740]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
After lot of research i have a doubt that its having a corrupted partition (eMMC) and i need to repartion the corrupted chip.
I tried nvflash commands for partitioning, its returning a unknown partition.
Any help will be appreciated......

matthepro said:
I think my MiPAD is totally bricked. Tried Pad shorting method which is suggested in XDA and other forums. No luck...
No recovery, boot logo or LED while charging (checked battery & its healthy).
Getting detected in MIFLASH tool (as Device "0", but that is enough for job to be done) but flashing ending in an error "Unspecified error(0x80004005; failed execuiting command 17 NvError 0x120002" .. (yeah i have used untouched mocha image).
Yes i tried many times, with different PC, cable and calm mind.
it is getting detected in APX mode (stable connection)....
Flash Log :
[00000BA4]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000BA4]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000BA4]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[00001740]0 0.00 execute C:\FLASH\nvflash_all.bat
[00001740]0 0.16
[00001740]0 0.16 $pushd C:\FLASH\images
[00001740]0 0.16
[00001740]0 0.16 $nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
[00001740]0 2.14 Nvflash 4.13.0000 started
[00001740]0 2.14 chip uid from BR is: 0x34001001740db0c108000000080102c0
[00001740]0 2.14 rcm version 0X400001
[00001740]0 2.14 Skipping BoardID read at miniloader level
[00001740]0 2.14 System Information:
[00001740]0 2.14 chip name: unknown
[00001740]0 2.14 chip id: 0x40 major: 1 minor: 1
[00001740]0 2.14 chip sku: 0x0
[00001740]0 2.14 chip uid: 0x00000000000000000000000000000000
[00001740]0 2.14 macrovision: disabled
[00001740]0 2.16 hdcp: disabled
[00001740]0 2.16 jtag: disabled
[00001740]0 2.16 sbk burned: false
[00001740]0 2.16 board id: 0
[00001740]0 2.16 warranty fuse: 0
[00001740]0 2.16 dk burned: false
[00001740]0 2.16 boot device: emmc
[00001740]0 2.16 operating mode: 3
[00001740]0 2.16 device config strap: 0
[00001740]0 2.16 device config fuse: 0
[00001740]0 2.16 sdram config strap: 0
[00001740]0 2.16
[00001740]0 2.16 RCM communication completed
[00001740]0 2.16 BCT sent successfully
[00001740]0 2.16 odm data: 0x49c000
[00001740]0 2.16 downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
[00001740]0 2.16 sending file: bootloader.bin
[00001740]0 2.16
[00001740]0 2.16 - 1048576/4194304 bytes sent
[00001740]0 2.16 \ 2097152/4194304 bytes sent
[00001740]0 2.16 | 3145728/4194304 bytes sent
[00001740]0 2.16 / 4194304/4194304 bytes sent
[00001740]0 2.16 bootloader.bin sent successfully
[00001740]0 2.16 waiting for bootloader to initialize
[00001740]0 2.16 bootloader downloaded successfully
[00001740]0 2.16 ML execution and Cpu Handover took 1 Secs
[00001740]0 2.16 setting device: 2 3
[00001740]0 2.16 creating partition: BCT
[00001740]0 2.16 failed executing command 17 NvError 0x120002
[00001740]CScriptReport:oWork(420): Unspecified error(0x80004005)
[00001740]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00001740]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
After lot of research i have a doubt that its having a corrupted partition (eMMC) and i need to repartion the corrupted chip.
I tried nvflash commands for partitioning, its returning a unknown partition.
Any help will be appreciated......
Click to expand...
Click to collapse
NO answers ???

matthepro said:
NO answers ???
Click to expand...
Click to collapse
It should be able to flash if its getting detected in the apx mode. Try uninstalling the driver and install the NVIDIA drivers, and use an older version of flash tool as mentioned here.

matthepro said:
NO answers ???
Click to expand...
Click to collapse
I think this https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604 is enough to solve your problem.
But maybe there are something you need to take care:
1. Make sure you keep touching the point with the slot.
2.Choose the path of drive(in the file folder of miflash) and install it.
3.If you can't install it(it always happen on win10), make an advanced reboot and turn off the forced digtal signature.
These are my experience, good luck to you

Same issue
Hi
Did you resolve this issue. If yes, how. I tried everything but facing the same issue
Thanks

matthepro said:
I think my MiPAD is totally bricked. Tried Pad shorting method which is suggested in XDA and other forums. No luck...
No recovery, boot logo or LED while charging (checked battery & its healthy).
Getting detected in MIFLASH tool (as Device "0", but that is enough for job to be done) but flashing ending in an error "Unspecified error(0x80004005; failed execuiting command 17 NvError 0x120002" .. (yeah i have used untouched mocha image).
Yes i tried many times, with different PC, cable and calm mind.
it is getting detected in APX mode (stable connection)....
Flash Log :
[00000BA4]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000BA4]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000BA4]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000BA4]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[00001740]0 0.00 execute C:\FLASH\nvflash_all.bat
[00001740]0 0.16
[00001740]0 0.16 $pushd C:\FLASH\images
[00001740]0 0.16
[00001740]0 0.16 $nvflash --instance 0 --bct mocha_bct.cfg --setbct --odmdata 0x49C000 --configfile mocha_flash.cfg --create --bl bootloader.bin --wait --go
[00001740]0 2.14 Nvflash 4.13.0000 started
[00001740]0 2.14 chip uid from BR is: 0x34001001740db0c108000000080102c0
[00001740]0 2.14 rcm version 0X400001
[00001740]0 2.14 Skipping BoardID read at miniloader level
[00001740]0 2.14 System Information:
[00001740]0 2.14 chip name: unknown
[00001740]0 2.14 chip id: 0x40 major: 1 minor: 1
[00001740]0 2.14 chip sku: 0x0
[00001740]0 2.14 chip uid: 0x00000000000000000000000000000000
[00001740]0 2.14 macrovision: disabled
[00001740]0 2.16 hdcp: disabled
[00001740]0 2.16 jtag: disabled
[00001740]0 2.16 sbk burned: false
[00001740]0 2.16 board id: 0
[00001740]0 2.16 warranty fuse: 0
[00001740]0 2.16 dk burned: false
[00001740]0 2.16 boot device: emmc
[00001740]0 2.16 operating mode: 3
[00001740]0 2.16 device config strap: 0
[00001740]0 2.16 device config fuse: 0
[00001740]0 2.16 sdram config strap: 0
[00001740]0 2.16
[00001740]0 2.16 RCM communication completed
[00001740]0 2.16 BCT sent successfully
[00001740]0 2.16 odm data: 0x49c000
[00001740]0 2.16 downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
[00001740]0 2.16 sending file: bootloader.bin
[00001740]0 2.16
[00001740]0 2.16 - 1048576/4194304 bytes sent
[00001740]0 2.16 \ 2097152/4194304 bytes sent
[00001740]0 2.16 | 3145728/4194304 bytes sent
[00001740]0 2.16 / 4194304/4194304 bytes sent
[00001740]0 2.16 bootloader.bin sent successfully
[00001740]0 2.16 waiting for bootloader to initialize
[00001740]0 2.16 bootloader downloaded successfully
[00001740]0 2.16 ML execution and Cpu Handover took 1 Secs
[00001740]0 2.16 setting device: 2 3
[00001740]0 2.16 creating partition: BCT
[00001740]0 2.16 failed executing command 17 NvError 0x120002
[00001740]CScriptReport:oWork(420): Unspecified error(0x80004005)
[00001740]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00001740]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
After lot of research i have a doubt that its having a corrupted partition (eMMC) and i need to repartion the corrupted chip.
I tried nvflash commands for partitioning, its returning a unknown partition.
Any help will be appreciated......
Click to expand...
Click to collapse
How do you use the nvflash commands for partitioning? I'm facing the same problem, too

Related

is my tablet fried.

everything is working but for some reason i cannot gt it it recovery mode any longer.. was working fine when i got. it.. just hangs with the message "recovery key detected"
so i followed some steps here and tried to flash the recovery img. from the latest stock firmware.. results look fine.. but it still hangs and never gets into recover mode..
double checked the recovery directory is there (i am trying to reflash cwm which obbviously is not working) and the command file is correct pointing to sdcard and the update.zip is int he root of sdcard (from internal cwm)
still just hangs and "recovery key detected"
here is the output when it tried to reflash the recovery partition which i assumed somehow got munged.. but no idea.. any help would be appreciated.
D:\gtab>nvflash.exe --bl bootloader.bin --download 9 recovery.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144043439f4617
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery.img
\ 3522560/3522560 bytes sent
recovery.img sent successfully
D:\gtab>
D:\gtab>
well bit the bullet and reflshing everything to stock and starting over.. will let you know..
ie
D:\gtab>nvflash_gtablet.bat
D:\gtab>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfil
e gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144043439f4617
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:
D:\gtab>
igkahn,
Probably was quicker and less trouble than trying to work through the other.
When you get to the stock, you might want to run Settings/Security/Wipe
Factory Data just to make absolutely sure you're good to go.
Once you get back to stock, you can OTA back up to 3588 and from there you
can go where you want to.
Rev
I am having the same issue
I am having the same issue with not being able to enter the recovery mode. everything is working but for some reason i cannot get it in recovery mode any longer.. was working fine when i got. it.. just hangs with the message "recovery key detected"
I am a newbie to the Android OS would appreciate any help on how to fix this problem.
Were you using stock recovery? ClockworkMod? What ROM did you have installed? Have you recently made any changes? Updates?
How do you expect help if you don't give us any information?

Soft-bricked Galaxy 10.1

Can only run APX mode.. no Odin.
Was running Touchwiz 3.1 when all of a sudden, my tab locked up.
I powered down and it never came back up.
I can get it into APX mode, but get the following when I try to reload the bootloader.
C:\nvflash>nvflash --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x038891c54140XXXX
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
Did some searches here and wasn't able to find something that would work.
Is there any way to use nvflash to repair?
Thanks!

[Q] Did I brick my Tab?

I got my Tab 10.1 (32 GB, white, unlocked) yesterday, and loved it. But it is no more. I was trying to get it into bootloader mode, and the two icons that should appear did for a second, then disappeared. It was the last thing I saw on the screen.
I tried plugging it in to my computer and into the wall. I tried holding the power button down for a looooooonnnnnggg time. I tried holding power and volume up, then power and volume down. I tried holding power and touching the screen. The only info I could get out of it was being able to get it into APX mode and trying nvflash. When I got to step 17 of section 2, this is what my computer told me:
c:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c7107417f60d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
Click to expand...
Click to collapse
Unfortunately, that makes no sense to me. Is it done for good? Anything I can do to revive it?

[Q] Boot Loader Dead (stuck in APX) no birds...

Hello, I have tried everything I can find (many times) ....I had a working gtab with 1.1, have not touched it in years, wanted to load one of the new roms as apparently they are much faster now. Did a few things, 1.1 to 1.2, stock, etc....not really sure of the order or where I messed up, but now I am stuck with APX only. No matter what script I run it always ends with this: "sending file: system.img \ 18743296/125207808 bytes sentdata send failed NvError 0x120002 command failure: create failed (bad data)".
I feel I have messed up the partitions somewhere related to the bct? Tried format, comes up with magic mismatch.
Any ideas on what I can do next, besides use the wife's Ipad?
Thanks.
Here is the full text of the nvflash session:
C:\nvflash>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0270308343a06117
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 945476/945476 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33292288/33292288 bytes sent
part8.img sent successfully
sending file: part9.img
/ 3911680/3911680 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 18743296/125207808 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
"Please close command window. Shut down gTab by holding power button"

Asus Transformer tf101 - not work

hi,
I have asus tf101 , and not work. Non-stop is black screen. I Connected to PC and pc visible my tablet. Okey, i go to nvflash but:
C:\Documents and Settings\klaviu.s\Pulpit\ASUS NFLASH\Win>cd C:\Documents and Se
ttings\klaviu.s\Pulpit\ASUS NFLASH\Win\
C:\Documents and Settings\klaviu.s\Pulpit\ASUS NFLASH\Win>"nvflash.exe" --bct tr
ansformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odm
data 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0380624041ff93d7
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: 2
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
- 1361053/1361053 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
and then do not go. How do I fix this?
If the battery is broken it may be wines that?
This is the TF201 forum. You aren't likely to get help for your device here.

Categories

Resources