Database Info

[Q] flash system img through fastboot fails with FAILED (remote: 00120003))

Hi,
Device: Xoom 3g EU T-mobile
I somehow soft-bricked my xoom (bootloop at the dualcore-screen). I have adb and fastboot access, but whatever type of image (Stock EU / Stock Germany T-Mobile) i try to flash, i always get the following error when i try to flash the system img (no issues with the other images)
Code:
./fastboot flash system /home/lxk/MZ601_H.6.1-38-5_TMO_Germany/system.img
sending 'system' (262144 KB)...
FAILED (remote: (00120003))
finished. total time: 170.654s
Couldn't find anything on the web about this error on the xoom.
I tried the Stock EU and Stock Germany T-Mobile from Motodev as well as the Tiamat Rom via CWM as well as via fastboot. Tried it with fully charged battery and from different OSes.(Fedora16 / Win7 64bit). I Can install and use CWM recovery without a hassle.
Does anybody know something about the error or how i can recovery my xoom?
Any help will be much appreciated!

fastboot reboot-bootloader
I've been trying to unbrick my xoom and every so often it will give me a connection error, not the same as yours though (0x120000). I just did fastboot reboot-bootloader and rebooted from adb back into bootloader support, tried again, and it accepted it.
edit: Sorry, had to do a manual reset after it went into rsd mode 3 and hold down the volume down button to go into fastboot mode and as soon as it did it sent fine.

Hi
thanks for the reply.
I tried this already, but will give it another try.
I also have to suitable .sbf file but rsd lite can't flash because of an INI file error (Unable to retrieve initialization values from INI file).
Does anybody know how to resolv this? Or where I get the INI file. I've read that this may relate to a broken code in the bootloader where the ini file is normaly stored. Is there a way to recover my xoom?

I'm not well versed enough to comment on that. Hopefully someone else can help you there. I've seen similar messages trying to push an update.zip from adb which I know people usually don't recommend.
Good luck.

ok i solved it
i tried to flasha gain on a 32bit system and e voila - it flashed without problems, reboot and now my xoom is running again !

Hi,
I have quite the same problem except my xoom is a Wifi FR model (MZ604).
I tried to flash it with US firmware from motodev website :
I can flash boot, userdata and recovery, but each time I try to flash the sytem.img, it gets stuck for a long time, displaying this on my PC:
$ fastboot flash system system.img
sending 'system' (262144 KB)...
And nothing on my xoom, until finally it times out and the xomm display in red:
Failed to process command error (0x120003)
Probelm is I cannot boot anymore my xoom : I get stuck on the Dual Core screen.
I cannot power off it either.
If I hold voulme up + power 5 s. I arrive on the RSD sccren (RSD 3)
So my brand new xoom is bricked!
First time I used ubuntu 64 to flash, after that I tried using Windows 7 64, then Windows XP 32 in a VM. Always the same problem; I can flash everything except system.
What can I do more?
---------- Post added at 03:08 PM ---------- Previous post was at 02:42 PM ----------
I looked for a solution for days before to post here. But I found nothing I finally wrote this post... and a few minutes later I found the solution here: http://forum.xda-developers.com/showthread.php?t=1275819&page=2
I was using a samsung cable on my front usb ports.
I tried the Motorola stock cable on one of my back USB ports, with Ubuntu x64 and it worked!
So if ever somebody have strange flashing issues like this : try other cables and ports, not other OS. I guess when lxbert changed of OS it changed of hardware too...

Freaken Cable
cable is a cable, right? Apparently the answer is no. Switched to the moto cable and it worked first time. I wish i would have tried it an hour ago.

[fixed] Did I brick it?

Hi there. I was fooling around with my TF300T (I was foolish at some point, probably) and managed to install Jellybean using this method. It started working fine. So it did that I restored my files using Titanium Backup Pro, installed from the App store right after the first boot. The apps/data I restored with Titanium Backup, as far as I can remember, were mostly games and Dolphin stuff, nothing directly related to system, as far as I know.
After this backup restoration, I used the tablet a little more, played the games to check if my progress was not lost and all that. It worked, Angry Birds at least had all the levels I completed before yet marked as completed after restore the procedure.
So far so goo... no! For some reason I can't remember I restarted the tablet, at least I tried! It got stuck on the loading screen (the white Asus, not the shiny one). So, after that I tried to restore it again, and then I probably did something completely stupid and I can't even remember what.
I even tried superwipe on it, but that didn't work neither.
At this point my tablet let me flash recovery image, CWM and TWRP. I can use adb shell with CWM but not with TWRP.
For some reason, I don't know, when I use CWM it doesn't mount /sdcard, TWRP seem to be mounting it, but go figure, I can only access the /sdcard that TWRP mounts using TWRP, if I change the recovery to CWM for some bizarre (or obvious to you guys) reason, I can't mount it.
And no matter what recovery I use, I can't flash any ROM. Both recovery tells me it was flashed, no error message (at least not at the screen) but every time it reboots to finish the installation, I see the Asus logo with a progress bar that goes from 0% to 100% in less then one second, and once it's filled, the tablet reboots itself and show me the regular boot screen with the Asus logo (again, the white one, not the silver-shiny).
So, resuming my problem, I can fastboot and adb shell it (adb only with ClockWorkMod Touch), but flashing doesn't seem to work. And I believe the internal memory/storage structure have been compromised.
How do I fix this?
Here is what I did to fix it
brbjr said:
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Click to expand...
Click to collapse
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.

Man you saved my life. Thank you very much!

When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?

Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.

Itege said:
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Click to expand...
Click to collapse
You're welcome!
Now click thank you so you can help me
I recommend you to use the CleanROM 2.5, it's stable and fast! Really fast! Faster then the ASUS Stock ROMs. I'm really enjoying it.

Still can't flash ROMs
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page

poisondminds said:
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
Click to expand...
Click to collapse
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work

allram said:
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
Click to expand...
Click to collapse
For CleanROM he'll need a specific TWRP version. It's better give CleanROM thread a read before install it.

allram said:
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...

Guticb said:
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Click to expand...
Click to collapse
1. Please, make sure the Tablet is the only one Android device connected to your computer
2. The bootloader is unlocked, right?
3. It's not the matter (almost impossible to be the case), but what are you using as recovery, TWRP or CWM?
4. Are you trying to flash the Official ROM?
- Sent from the Future, using my Delorean
- Enviado do Futuro, usando meu Delorean

mizifih said:
Originally Posted by brbjr View Post
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Quote:
Originally Posted by manegonzalez View Post
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
This is an awesome fix, thought I was buggered with a tablet that couldnt mount anything, couldn't get into download mode, recovery was fubared.. and then I stumbled on this
THANK YOU

[Q] [FIXED] HELP! Possible Brick on Xoom MZ607 WIFI

Hey! I need all your help, please. Yesterday, I saw that Motorola reveled a tool to unlock the bootloader of our tablet (I know, late). I read all the information about the process, and I could do this on my mz607 wifi. I downloaded all that I need, drivers and android sdk. After that, I rebooted the xoom on bootloader using adb command but....I can't do anything on this!!
I looked for some information about this, and I found in all forums that I can unlock bootloader with "fastboot oem unlock" command. It's false, I cant do nothing!! I rebooted my tablet and now, always run on bootloader and not boot system.
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
I found a germany forum with the same problem (I think) but I don't understand how they solved this.This the link
After this, I looked for other solutions and I found a tool of Motorola, RSDLite. I downloaded the correct file for my model, and when it flashing (7 step for the tool) not flash the boot.img! It's flash correctly other file packages (recovery.img, fastboot, etc) but it can't flash boot.img
Now, when I do "vol up+vol down+power" and select "Normal Boot", It doesn't do anything, the system would be missing!
I think it's can be a soft brick....or no, I dont know. I'm very worried about this and I would appreciate all your help.
Thanks. I'm waiting your answer.

Anybody can help me????

Ok, Anybody wants to help me!
Bye.

Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Joshbone said:
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.

runandhide05 said:
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
Click to expand...
Click to collapse
So I have to find the same files for my MZ607? boot, recovery and system?

runandhide05 said:
You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Click to expand...
Click to collapse
Joshbone said:
So I have to find the same files for my MZ607? boot, recovery and system?
Click to expand...
Click to collapse

Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Mjamocha said:
Click to expand...
Click to collapse
What??

Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Anybody more??

Joshbone said:
Anybody more??
Click to expand...
Click to collapse
Runandhide told you everything you need to know. You need to find the right regioned fastboot file for your mz607 and flash it. And that ypur bootloader is not unlockable. Any tutorial you were reading to unlock it would have to have been for the original xoom, not xoom2.

HELP! Possible Brick on Xoom MZ607 WIFI
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)

As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.

f5bud said:
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
Click to expand...
Click to collapse
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you

Like the genius I am I've bricked mine too. It's a UK MZ607 that's been updated to JB from the US MZ609. I managed to delete the stock browser whilst trying to install a CyanogenMOD browser (long story) so figured I'd just repeat the steps that I used to flash the US MZ609 firmware. What I'd forgotten is that the first stage is to flash the US MZ609 ICS ROM then do an update to JB meaning I was effectively trying to downgrade. Everything flashes successfully except the boot partition which gives an error that it doesn't exist. Any ideas out there? I tried what I believe to be the original Fastboot file but no luck

Joshbone said:
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Click to expand...
Click to collapse
Also tried this and it fails when flashing the boot partition. I just ordered a factory cable to see if it can bring it back to life...

Is this zip still available?

alecbond said:
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
Click to expand...
Click to collapse
anybody who still has the mz607 files for a restore? The possible stock files link doesn't work any more...
http://sbf.droid-developers.org/xoom2/list.php

[SOLVED] Issues Booting on a XT925 - Unlocked device

Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.

Here some more infos I got while using DroidHD Utility Deluxe :
The command "fastboot flash aboot file.mbn" leads to a "error: cannot load 'folder/file.mbn'"

I managed to get a functional Driod Razr XT925 OS working by using the tool I mentioned before : DriodHD Utility Deluxe
Everything works well except those :
I can't read any backups made with TWRP before that (I mean the backups which were functionnal but that I couldnt manage to get back on).
I can't make my SIM work anymore, it says, unknown sim, and no network available when I'm trying to use my phone with GSM functions.

Managed to get my backups work again. The folder was under another name, which is why TWPR couldnt find it.
One last problem, my /efs partition has left me You already see the problem ? No IMEI around !
So I managed to find my IMEI number again and trying to use that http://forum.xda-developers.com/showthread.php?t=1960918 to write it back on my phone.
But...cause there's a but, I cant seem to use my USB drivers when I boot up in "BP Tools".
So impossible to access the phone, and impossible to write that "recovered" IMEI...
Anyone has a solution roaming around ?

Well at least I can feel like not being a total dumb ^^ Managed to install manually the driver for QC Diag Port, by selecting "Motorola" > "Motorola QC Diag Port" manually.
So, the BP tools mode can now be accessed from my computer, but here is another problem, I can communicate with the phone and even write my IMEI, but not on the phone Sounds like the entry 555 (which was totally absent) is in read-only mode :/
Here is the error given by RF NV Manager :
NvManager::writeToPhone(comPort, nvItems, throwException) -Unable to write 'NV_UE_IMEI_I' to the phone. (Parameter is write-protected and thus read only)
A clue ? Anyone ? Before I find it alone again, I think I'll soon be bald considering how I tear my hair since some hours...
Edit :
Ok so I tryed the QPST thing on a 32bits XP computer. Same problem.
I also tryed flashing my ROM into the stock one with RSD Lite, which is called like that :
9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC
Found it here : http://forum.xda-developers.com/showthread.php?t=2032284
Under that name :
Branding: Retail France/Retail Central Europe
Version: 9.8.2Q-8-XT925_VQU-22 FULL
Android Version: 4.1.2
Bootloader Version: N/A
Requires RSD Lite 6.0
Click to expand...
Click to collapse
And got an error (even after removing the getvar command) which is :
Failed flashing process. 2/22 flash partition "partition_signed"->Phone returned FAIL
Click to expand...
Click to collapse
Here is what the fastboot screen says :
Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
Final Edit (#Request lock) :
Ok so I finally got out of trouble.
Flashed to the stock rom with that rom : 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P 007_A004_CFC
Found it here : http://forum.xda-developers.com/show....php?t=2032284
And applyed that homemade script (which gets rid of the cache memory problem before system flash) :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen bcomes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot reboot
Then when I came back on my phone, my IMEI was back itself like a big one
4 days of SMS came back at that time, I'm saved

Hybris95 said:
Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.
Click to expand...
Click to collapse
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
Click to expand...
Click to collapse
i realy need your help

arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
i realy need your help
Click to expand...
Click to collapse
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.

Hybris95 said:
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.
Click to expand...
Click to collapse
i dont understand where and how should i start for the homemade script...
where can i find the firmware?

arinata1983 said:
i dont understand where and how should i start for the homemade script...
where can i find the firmware?
Click to expand...
Click to collapse
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.

Hybris95 said:
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.
Click to expand...
Click to collapse
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??

arinata1983 said:
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??
Click to expand...
Click to collapse
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.

fixed
Hybris95 said:
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.
Click to expand...
Click to collapse
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..

arinata1983 said:
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..
Click to expand...
Click to collapse
You're welcome, I had been stuck like you which is why I made that homemade script

TF700 stuck in Boot loop ... have access to bootloader

Hi,
I've posted on this topic on transformerforums website but have not had any success (despite valiant attempts from the guys on the forums).
I am unable to post the link here, please PM me for a link to my original post.
Basically my TF700T got stuck in a bootloop. I have unlocked the bootloader but have not flashed it so it's on stock ROM. I have not been able to flash a recovery ROM and am at a dead end as to what to do.
I am able to get to bootloader and I when I run
Code:
fastboot devices
I get the following output
Code:
015d2a506733f618 fastboot
Which all seems correct. I have access to the tablet when connected to my pc.
When I try to flash the recovery rom, it takes a very short amount of time and on my tablet the device hangs (i.e the RCK icon is no longer flashing). I have checked the blob, it is the correct one and the MD5 hash is correct.
Code:
C:\androidsdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp-2.7.1.1-tf700t.blob
sending 'recovery' (6894 KB)...
OKAY [ 0.868s]
writing 'recovery'...
OKAY [ 0.089s]
finished. total time: 0.958s
I can get back into the bootloader if I restart again but attempting to flash it results in a hang.
I have tried to insert an sd with the stock ROM and boot in RCK mode but this has not worked either.
Has anyone any suggestions as to what to do?
The tablet is 2 years old now so not under warranty.
thanks in advance.

anyone have any suggestions?
I'm going on holidays on Thursday and would really love to get this resolved before I go.

deleted

Shameless bump .... are my only options to return this to the manufacturer?
Anyone any suggestions, do you need more info from me?

What you did looks correct, only the short time for "writing" looks suspicious. Try the fastboot command again, but replace "recovery" with "staging", maybe that works better. At the next reboot you should see a blue progress bar on the boot screen for a few seconds and it should reboot again.

Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?

I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?

knoxor said:
I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?
Click to expand...
Click to collapse
When blobs are written to the staging partition, on next boot. the bootloader flashes the contents to the relevant partitions (i.e., kernel, system, bootloader)

knoxor said:
Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?
Click to expand...
Click to collapse
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul

knoxor said:
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul
Click to expand...
Click to collapse
Well shoot me a PM, Lets see if we can find a solution to your issue ...
Thx Josh

bump again.
Is there anyone there who can help me on this please ?

knoxor said:
Is there anyone there who can help me on this please ?
Click to expand...
Click to collapse
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.

_that said:
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.
Click to expand...
Click to collapse
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks

knoxor said:
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks
Click to expand...
Click to collapse
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....

berndblb said:
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....
Click to expand...
Click to collapse
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??

knoxor said:
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??
Click to expand...
Click to collapse
If you got the charger from anywhere else but Asus - yes, that could be the issue. And the only one left I can think of....