Related
Hey, guys
I've been lurking for a few days now, and decided to register and start a thread since I couldn't find any solution for my problem.
Anways, I'll start explaining.
I'm using a Xoom 2, mz608 running on Android 3.2.2. I've rooted my device and tried installing this: http://forum.xda-developers.com/showthread.php?t=1520476
After it tried rebooting, it ran into a bootloop. The motorola logo was animating, this was going on and on.
Then, I got into the recovery mode, since I couldn't unlock it. I selected wipe data/factory reset, "Yes, all user data". Tried rebooting failed again.
I've tried installing the MZ609 official fastboot files, it came to a stage where it seemed like it was installing it, however ended up with the android logo and a exclamation mark in it.
Then I tried installing this package: http://sbf.droid-developers.org/xoom2/list.php
That totally messed it up, now I'm getting these in fastboot:
Code:
AP Fastboot Flash Mode(S)(Boot Failure)
0A.8GB(sha-748ae9e-dirty, 2011-12-14 16:18:49)
eMMC Info: Size 16G
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG HAB(cg: mbr, status: 0x0056)
Now, I've lookup on other forums too, it seems many people are having this kind of issues.
Is there a way to solve this? Has anybody else that encountered this and managed to fix it?
Thanks in advance!
Semih91 said:
Hey, guys
I've been lurking for a few days now, and decided to register and start a thread since I couldn't find any solution for my problem.
Anways, I'll start explaining.
I'm using a Xoom 2, mz608 running on Android 3.2.2. I've rooted my device and tried installing this: http://forum.xda-developers.com/showthread.php?t=1520476
After it tried rebooting, it ran into a bootloop. The motorola logo was animating, this was going on and on.
Then, I got into the recovery mode, since I couldn't unlock it. I selected wipe data/factory reset, "Yes, all user data". Tried rebooting failed again.
I've tried installing the MZ609 official fastboot files, it came to a stage where it seemed like it was installing it, however ended up with the android logo and a exclamation mark in it.
Then I tried installing this package: http://sbf.droid-developers.org/xoom2/list.php
That totally messed it up, now I'm getting these in fastboot:
Code:
AP Fastboot Flash Mode(S)(Boot Failure)
0A.8GB(sha-748ae9e-dirty, 2011-12-14 16:18:49)
eMMC Info: Size 16G
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG HAB(cg: mbr, status: 0x0056)
Now, I've lookup on other forums too, it seems many people are having this kind of issues.
Is there a way to solve this? Has anybody else that encountered this and managed to fix it?
Thanks in advance!
Click to expand...
Click to collapse
I hope that you are trying to flash the mz608 official fastbootfiles
I think I went wrong with the flash of the fastboot files.(do you have the latin america edition? -latem stands for latin america)
Otherwise you could probably have fixed it with pushing the original framework-res.apk.
I have the same model, if you need something, let me know.
Motorola mz608 bricked
Semih91 said:
Hey, guys
I've been lurking for a few days now, and decided to register and start a thread since I couldn't find any solution for my problem.
Anways, I'll start explaining.
I'm using a Xoom 2, mz608 running on Android 3.2.2. I've rooted my device and tried installing this: http://forum.xda-developers.com/showthread.php?t=1520476
After it tried rebooting, it ran into a bootloop. The motorola logo was animating, this was going on and on.
Then, I got into the recovery mode, since I couldn't unlock it. I selected wipe data/factory reset, "Yes, all user data". Tried rebooting failed again.
I've tried installing the MZ609 official fastboot files, it came to a stage where it seemed like it was installing it, however ended up with the android logo and a exclamation mark in it.
Then I tried installing this package: http://sbf.droid-developers.org/xoom2/list.php
That totally messed it up, now I'm getting these in fastboot:
Code:
AP Fastboot Flash Mode(S)(Boot Failure)
0A.8GB(sha-748ae9e-dirty, 2011-12-14 16:18:49)
eMMC Info: Size 16G
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG HAB(cg: mbr, status: 0x0056)
Now, I've lookup on other forums too, it seems many people are having this kind of issues.
Is there a way to solve this? Has anybody else that encountered this and managed to fix it?
Thanks in advance!
Click to expand...
Click to collapse
Hi folks,
I have exactly the same problem.
after installing the http://sbf.droid-developers.org/xoom2/list.php the tablet shows the error above.
Looking into the output of the console shows, that only the motoboot.bin - file could be installed, the other failed.
But this was the problem, I guess wrong version of the "motoboot.bin" - I read to late that it is the "latin American" one.
Does anybody know where to get the version of the file, that fits to the mz608 bought in germany?
a crate of beer (good german beer) for the correct file
one Idea: bying another one, and pulling the image: is it possible?
cheers
Michael
thanks for every answer...
mbuttenschoen said:
Hi folks,
I have exactly the same problem.
after installing the http://sbf.droid-developers.org/xoom2/list.php the tablet shows the error above.
Looking into the output of the console shows, that only the motoboot.bin - file could be installed, the other failed.
But this was the problem, I guess wrong version of the "motoboot.bin" - I read to late that it is the "latin American" one.
Does anybody know where to get the version of the file, that fits to the mz608 bought in germany?
a crate of beer (good german beer) for the correct file
one Idea: bying another one, and pulling the image: is it possible?
cheers
Michael
thanks for every answer...
Click to expand...
Click to collapse
If we would know the partition layout this could be possible.
i have one from belgium, so it could be the same model.
I don't know if the partition layout is the same as the 10".
The problem could be the fact that we have a locked bootloader
Hey guys, thanks for replying. I have a friend who also bought the tablet the same day and place I did. He's is still working. Do you think I could recovery it with his tablet? However, this european (Belgian) model, is locked and not able to be unlocked, so I think it's not possible..
mbuttenschoen said:
Hi folks,
I have exactly the same problem.
after installing the http://sbf.droid-developers.org/xoom2/list.php the tablet shows the error above.
Looking into the output of the console shows, that only the motoboot.bin - file could be installed, the other failed.
But this was the problem, I guess wrong version of the "motoboot.bin" - I read to late that it is the "latin American" one.
Does anybody know where to get the version of the file, that fits to the mz608 bought in germany?
a crate of beer (good german beer) for the correct file
one Idea: bying another one, and pulling the image: is it possible?
cheers
Michael
thanks for every answer...
Click to expand...
Click to collapse
BTW do you still have the output somewhere of the installation?
another thing we could try is:
wait for the update that will arrive in Q3, try to extract the files from there and try to fastboot flash them;
yelti said:
I hope that you are trying to flash the mz608 official fastbootfiles
I think I went wrong with the flash of the fastboot files.(do you have the latin america edition? -latem stands for latin america)
Otherwise you could probably have fixed it with pushing the original framework-res.apk.
I have the same model, if you need something, let me know.
Click to expand...
Click to collapse
Hi,
which ARE the official fastbootfiles?
I only found the files from sbf.droid-developers.org
and there, of course, i used the mz608 version.
cheers
Michael
---------- Post added at 02:32 PM ---------- Previous post was at 02:23 PM ----------
yelti said:
BTW do you still have the output somewhere of the installation?
another thing we could try is:
wait for the update that will arrive in Q3, try to extract the files from there and try to fastboot flash them;
Click to expand...
Click to collapse
Hi,
yes, I have the output of running the "flash_fastboot.bat" at home, in the moment I'm at work.
But I remember: only the line "fastboot flash motoboot motoboot.bin" came back with "OK,
all other lines "verification error" or something else, I can write it down exactly this evening.
extracting the update is a good idea, too, if it comes... But Q3 is not ended yet
cheers
Michael
mbuttenschoen said:
Hi,
which ARE the official fastbootfiles?
I only found the files from sbf.droid-developers.org
and there, of course, i used the mz608 version.
cheers
Michael
---------- Post added at 02:32 PM ---------- Previous post was at 02:23 PM ----------
Hi,
yes, I have the output of running the "flash_fastboot.bat" at home, in the moment I'm at work.
But I remember: only the line "fastboot flash motoboot motoboot.bin" came back with "OK,
all other lines "verification error" or something else, I can write it down exactly this evening.
extracting the update is a good idea, too, if it comes... But Q3 is not ended yet
cheers
Michael
Click to expand...
Click to collapse
Its is hard to find the flash files, ik think we need emea instead of latam.
It think it would be possible to flash the hboot from a working model if you know which partition it is.
Semih91 said:
Hey guys, thanks for replying. I have a friend who also bought the tablet the same day and place I did. He's is still working. Do you think I could recovery it with his tablet? However, this european (Belgian) model, is locked and not able to be unlocked, so I think it's not possible..
Click to expand...
Click to collapse
I think i have something:
From ad shell dmesg > log.txt you can get the partition layout.
You have mbmloader mbm and mbmbackup.
One of these is the boot loader.
So try to dump these files and fast boot flash hboot hboot.img could work.
Dd if=/dev/mmcblkp0px of=/someplacewhereyoucanwrite/St.img
Could you provide me the system image somehow?
What does the "about" in system prefs says on the working device?
I bricked mine too unfortunately, but maybe I can get away with a system reflash.
Edit: corrected the partition name
a dmesg from my device
The partition layout
p1 (mbmloader)
p2 (mbm)
p3 (mbmbackup)
p4 (cdt.bin)
p5 (pds)
p6 (utags)
p7 (logo.bin)
p8 (sp)
p9 (devtree)
p10 (devtree_backup)
p11 (boot)
p12 (recovery)
p13 (cdrom)
p14 (misc)
p15 (cid)
p16 (kpanic)
p17 (system)
p18 (cache)
p19 (preinstall)
p20 (userdata)
yelti said:
a dmesg from my device
The partition layout
p1 (mbmloader)
p2 (mbm)
p3 (mbmbackup)
p4 (cdt.bin)
p5 (pds)
p6 (utags)
p7 (logo.bin)
p8 (sp)
p9 (devtree)
p10 (devtree_backup)
p11 (boot)
p12 (recovery)
p13 (cdrom)
p14 (misc)
p15 (cid)
p16 (kpanic)
p17 (system)
p18 (cache)
p19 (preinstall)
p20 (userdata)
Click to expand...
Click to collapse
Hi,
may be these partitions are there after booting.
in the 1.6.0M-272.12_MZ608_p2HW_BlurRegion02_CFC1FF_fastboot_signed_latam.xml fire it tried to flash these partitions:
fastboot flash boot boot_signed failed
fastboot flash motoboot motoboot.bin ok
fastboot reboot-bootloader
fastboot flash devtree devtree_signed failed
fastboot flash recovery recovery_signed failed
fastboot flash system system_signed failed
fastboot flash cdrom cdrom_signed failed
fastboot flash preinstall preinstall flashed
fastboot flash radio radio.img flashed
fastboot reboot
these are the files:
13.01.2012 22:29 8.388.608 boot_signed
13.01.2012 22:29 222.035.968 cdrom_signed
13.01.2012 22:30 524.288 devtree_signed
13.01.2012 22:34 2.622.464 motoboot.bin
13.01.2012 12:23 734.003.200 preinstall
13.01.2012 22:28 33.554.432 radio.img
13.01.2012 22:29 9.437.184 recovery_signed
13.01.2012 22:33 628.883.456 system_signed
maybe someone can find, which partition in the running device fits to "motoboot".
thanks
Michael
mbuttenschoen said:
Hi,
may be these partitions are there after booting.
in the 1.6.0M-272.12_MZ608_p2HW_BlurRegion02_CFC1FF_fastboot_signed_latam.xml fire it tried to flash these partitions:
fastboot flash boot boot_signed failed
fastboot flash motoboot motoboot.bin ok
fastboot reboot-bootloader
fastboot flash devtree devtree_signed failed
fastboot flash recovery recovery_signed failed
fastboot flash system system_signed failed
fastboot flash cdrom cdrom_signed failed
fastboot flash preinstall preinstall flashed
fastboot flash radio radio.img flashed
fastboot reboot
these are the files:
13.01.2012 22:29 8.388.608 boot_signed
13.01.2012 22:29 222.035.968 cdrom_signed
13.01.2012 22:30 524.288 devtree_signed
13.01.2012 22:34 2.622.464 motoboot.bin
13.01.2012 12:23 734.003.200 preinstall
13.01.2012 22:28 33.554.432 radio.img
13.01.2012 22:29 9.437.184 recovery_signed
13.01.2012 22:33 628.883.456 system_signed
maybe someone can find, which partition in the running device fits to "motoboot".
thanks
Michael
Click to expand...
Click to collapse
I see it has faild to flash the boot_signed.
Can you try to flash it manualy?
just put the boot_signed.img in your fastboor directory and fastboot flash boot boot_signed.img
See if that helps?
the motoboot can be only 2 partitions:
mbm or mbmloader.
I would thing mbmloader?
yelti said:
I see it has faild to flash the boot_signed.
Can you try to flash it manualy?
just put the boot_signed.img in your fastboor directory and fastboot flash boot boot_signed.img
See if that helps?
the motoboot can be only 2 partitions:
mbm or mbmloader.
I would thing mbmloader?
Click to expand...
Click to collapse
Hi,
i had first to wait that the battery is full, i cannot switch it off in fastboot mode, so it was empty after over last night.
now:
fastboot.exe flash boot boot_signed
sending 'boot' (8192 KB)...
OKAY [ 0.361s]
writing 'boot'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.924s
anybody who can extract it from his mz608?
size and other files in my last posts
thankyou all.
cheers
Michael
mbuttenschoen said:
Hi,
i had first to wait that the battery is full, i cannot switch it off in fastboot mode, so it was empty after over last night.
now:
fastboot.exe flash boot boot_signed
sending 'boot' (8192 KB)...
OKAY [ 0.361s]
writing 'boot'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.924s
anybody who can extract it from his mz608?
size and other files in my last posts
thankyou all.
cheers
Michael
Click to expand...
Click to collapse
I'm affraid that it won't work :crying:
We need a signed image to be able to flash.
I think a dump won't contain the sig, but I hope I'm wrong.
I think I have to send mine back to motorola
Do you have backlight bleeding at yours?
I have a spot where the light is bleeding from
yelti said:
I'm affraid that it won't work :crying:
We need a signed image to be able to flash.
I think a dump won't contain the sig, but I hope I'm wrong.
I think I have to send mine back to motorola
Do you have backlight bleeding at yours?
I have a spot where the light is bleeding from
Click to expand...
Click to collapse
Hi,
I've sent the Tablet to Motorola's Service, they have repaired it.
And - they didn't want to have any money
It has not yet arrived, but I have already a tracking number.
cheers
Michael
mbuttenschoen said:
Hi,
I've sent the Tablet to Motorola's Service, they have repaired it.
And - they didn't want to have any money
It has not yet arrived, but I have already a tracking number.
cheers
Michael
Click to expand...
Click to collapse
Nice they fixed m for free.
If you have him back, can you dump the system partition ( if it is still on Honycomb)
I would like to try to flash it to mine, if this fails, i'll return it too.
yelti said:
Nice they fixed m for free.
If you have him back, can you dump the system partition ( if it is still on Honycomb)
I would like to try to flash it to mine, if this fails, i'll return it too.
Click to expand...
Click to collapse
Hi,
it is still on 3.22 (3rd Q has not ended yet).
But: any idea how to do this without rooting?
Rooting (by using Root Method for Motorola Xoom 2/Xyboard Honeycomb By Dan Rosenberg) was the beginning of the desaster.
The rooting procedure was OK, but it was a 1-way-route.
Trying to flash back to stock (may be with the wrong tools/software/firmware) made the device unusable.
And I will not send it again to motorola's service, I think they wouldn't repair it again for nothing.
If you have an idea to read the system partition without rooting - I will do it, of course.
But how? reading may be possible, but there is no dd, no busybox without root.
So I think it will not work.
And, there is another point: I will sell the tablet and bye another one (Samsung P5100 I guess).
2 reasons: the display of the Xoom is ok, but: I think I am too old - a 10" device is a little bigger
And I want to have a tablet without a locked bootloader. Cyanogenmod 9 or 10 will be my friend, instead of waiting for Motorola.
I use CM9 on my little Samsung I9000 smartphone, and its OK. Much better than the stock 2.3.4. And it is available.
cheers
Michael
Without root I don't think it will be possible.
Unrooting is doable.
In Dan's script you can use the first 2 stages to make /system rw(I don't remember if I had to do a remount)
Then you can remove the Superuser.apk and busybox and your system is unrooted.
Next execute fase 3 and your back to stock.
If you don't want to do it, I understand.
Just let me know what you think, otherwise I will send mine back too.
mbuttenschoen said:
Hi,
it is still on 3.22 (3rd Q has not ended yet).
But: any idea how to do this without rooting?
Rooting (by using Root Method for Motorola Xoom 2/Xyboard Honeycomb By Dan Rosenberg) was the beginning of the desaster.
The rooting procedure was OK, but it was a 1-way-route.
Trying to flash back to stock (may be with the wrong tools/software/firmware) made the device unusable.
And I will not send it again to motorola's service, I think they wouldn't repair it again for nothing.
If you have an idea to read the system partition without rooting - I will do it, of course.
But how? reading may be possible, but there is no dd, no busybox without root.
So I think it will not work.
And, there is another point: I will sell the tablet and bye another one (Samsung P5100 I guess).
2 reasons: the display of the Xoom is ok, but: I think I am too old - a 10" device is a little bigger
And I want to have a tablet without a locked bootloader. Cyanogenmod 9 or 10 will be my friend, instead of waiting for Motorola.
I use CM9 on my little Samsung I9000 smartphone, and its OK. Much better than the stock 2.3.4. And it is available.
cheers
Michael
Click to expand...
Click to collapse
yelti said:
Without root I don't think it will be possible.
Unrooting is doable.
In Dan's script you can use the first 2 stages to make /system rw(I don't remember if I had to do a remount)
Then you can remove the Superuser.apk and busybox and your system is unrooted.
Next execute fase 3 and your back to stock.
If you don't want to do it, I understand.
Just let me know what you think, otherwise I will send mine back too.
Click to expand...
Click to collapse
Hi,
removing su and busybox I understand.
But what is this little programm "xyz phase x" doing?
where do you have this unrooting receipt from?
i am really afraid of ending in the same boot loop as before.
And I think, sending to service and waiting some days will be a good thing for you, too.
thank you, that you understand my situation.
cheers
Michael
mbuttenschoen said:
Hi,
removing su and busybox I understand.
But what is this little programm "xyz phase x" doing?
where do you have this unrooting receipt from?
i am really afraid of ending in the same boot loop as before.
And I think, sending to service and waiting some days will be a good thing for you, too.
thank you, that you understand my situation.
cheers
Michael
Click to expand...
Click to collapse
You didn't brick it by rooting it.
I think you bricked it when you changed the framework.apk.( I'm in the same situation )
Next you flashed the sbf which caused your bootloader problem.
The xyz finds a way to get a rootshell. Next it mounts the system RW and pushes the superuser.apk and busybox.
To unroot, it is the other way arround.
Maybe if you can mount your system rw, I think you can just remove the superuser.apk and execute busybox --uninstall.
With the next reboot you have your system back to read only.
You can find out how the xyz works in general by analysing the commands in run.bat.
Have fun with the samsung tablet.
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....
Hi all, first post here.
I have a bricked XT925 which I'm trying to recover.
It will go into fastboot and I can access it with ADB/Fastboot/mFastbootv2/RazorHDToolkit5.0/RSD lite etc, but none of these will write a new recovery to flash.
I was able to unlock the bootloader using the Motorola website and the phone will talk to the PC software, but it's as though the internal flash memory is trashed.
In fact lots of commands to the flash result in a "fastboot max download size 30mb" error.
Can anyone help?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8.6.0-xt925.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (9154 KB)...
OKAY [ 0.730s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.871s
Click to expand...
Click to collapse
I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.
I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Click to expand...
Click to collapse
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.
Click to expand...
Click to collapse
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.
ddichiera said:
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.
Click to expand...
Click to collapse
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.
palmbeach05 said:
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.
Click to expand...
Click to collapse
Any image would be welcome, GDrive is fine.
ddichiera said:
Any image would be welcome, GDrive is fine.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B52pkPIFU2dRWFRXOU9UQlhHZ3c
Thanks for that, unfortunately my situation has become worse.
Whilst the phone was connected and in fastboot mode, I deleted the ADB driver in Device Manager and now the PC, or more specifically ADB and Fastboot wont talk to the phone. Grrrrr.
Oh, and the other handset has decided to die as well.
One thing at a time. Anyone know how to restore the driver/get-the-phone-talking-to-ADB/Fastboot again?
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
It seems that your partitions are corrupt.
I had the same issue and solved it by restoreing completley to stock Rom. There must be a thread for this anywhere out, if not download a fastboot image from cyanogen support site extract it and try to flash it.
That is what I was leaning towards, but in every solution to restore the stock ROM I have to use fastboot and fastboot just fails to write anything. I can't even get TWRP to stick, fails to write every time. I tried the OnePlusRestoreTool but the driver installs ok but the tool can't find the phone, tried 2 different PCs. I was hoping for another solution other than fastboot or the OnePlusRestoreTool, I searched but could not find another method, I was hoping someone could point me in the right direction.
Thanks
newpop1_android said:
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
Click to expand...
Click to collapse
Try this
geowolf1000 said:
Try this
Click to expand...
Click to collapse
So I tried the link but also their method uses FastBoot and FastBoot fails to write to the OPO every time no matter what, see below. I can put TWRP in memory but can't write to the SD I guess. Any tool that can reformat the storage and put it back together since FastBoot and ADB can't write to it?
Thx
target reported max download size of 1073741824 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.137s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.208s
Has a second method from terminal
Run command from twrp rerminal
Στάλθηκε από το A0001 μου χρησιμοποιώντας Tapatalk
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
He tried that one, but as the PC doesn't detect his phone that ain't gonna work...
@newpop1_android could you sent me a PM, I'll try to resolve your issue in a teamviewer session.
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
Hello, so I managed to get an older PC to do all this in as well and tried another PC anyway. I ran the color.zip install, drivers installed OK and phone is detected, I ran the Msm8974DownloadTool.exe and it found the phone in COM3, I see a progress bar in one file, the image file and then it reboots the phone but it comes back to the Cyanogen splash screen and it does not go anywhere, so I reboot it again manually power+VUp and the tool finds it again and tries to send the *same* file again, and then I tried this loop at least 10 times.
I conclude that it is unable to write the image to the cell, same symptom I encountered with Fastboot flash boot img. Does this mean that the cell is bricked since nothing can write to the SD?
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
If only one image file is "flashed", check if your color.zip is downloaded correctly
Hope this helps
Flo9818 said:
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
Hope this helps
Click to expand...
Click to collapse
Hello, not really, it does one file and then I see progress bar move on the first file, progress bar finished and then the phone boots to the cyanogen screen again, then i tried again, it still shows the same file again. It does not save the file, fails to write pretty much, same thing as fastboot.
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Have you restarted your PC?
Flo9818 said:
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Click to expand...
Click to collapse
I actually did that and tried one plus one as well, I also tried the other unbrick toll as well with other drivers. The phone is recognized no problem, but nothing can write to it, just like fastbook flash , write denied every time.
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Flo9818 said:
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Click to expand...
Click to collapse
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
MrPowerGamerBR said:
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
Click to expand...
Click to collapse
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Yes, I did.
I also tried that tool before, same issue.
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
MrPowerGamerBR said:
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
Click to expand...
Click to collapse
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Flo9818 said:
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Click to expand...
Click to collapse
Windows 7, but Windows 7 also needs to disable driver verification.
I don't use any antivirus.
No, but I ran the tool as administrator.
I already tried that, I tried with the original cable that came with the device and my Moto G 2014 cable, same issue on both.
It isn't a missing driver issue tho, Qualcomm drivers are installed and working because the ColorOS flash tool detects the device.
Anyway, thanks for helping
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
You can get to fastboot but not recovery?
Yeah if you can get to fastboot then unlock the bootloader and flash the factory image
Tulsadiver said:
You can get to fastboot but not recovery?
Click to expand...
Click to collapse
I can enter fastboot, but when I press to enter Recovery Mode the screen goes black and that's it, nothing happens, same when I press Start.
I can't unlock it because I get an error: failed (remote: 'flashing unlock is not allowed')
Was it 100% stock when you relocked it?
Sent from my crosshatch using XDA Labs
I would open the stock recovery on the PC and try flashing the factory image from there.
ridobe said:
Was it 100% stock when you relocked it?
Click to expand...
Click to collapse
It was 100% stock when I relocked it.
krabman said:
I would open the stock recovery on the PC and try flashing the factory image from there.
Click to expand...
Click to collapse
I tried that but this is what returns to me:
flash-all.bat
Sending 'bootloader_a' (8489 KB) OKAY [ 0.310s]
Writing 'bootloader_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 0.867s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
Sending 'radio_a' (71148 KB) OKAY [ 1.834s]
Writing 'radio_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 2.084s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-4852902
Baseband Version.....: g845-00010-180619-B-4850223
Serial Number........: **********
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
I seem to remember from my Pixel (original) days that there was some trick to re-locking the bootloader or you would encounter issues.
You might consider searching the original Pixel's subforum here at XDA for that thread and see if the suggestions in it apply to you.
I think this might be the thread.
Read through it to see if anything can help you.
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Click to expand...
Click to collapse
A friend of mine bought this phone from a website similar to eBay.
The software was stock.
pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.
Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk
lucky_strike33 said:
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.
Click to expand...
Click to collapse
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?
superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Click to expand...
Click to collapse
People have already done this on working Pixel 3 XL's and all it did was returned an error.
I've gota a vague recollection of needing to format before flashing the image in this situation. Anyone confirm our deny?
MArtyChubbs said:
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?
Click to expand...
Click to collapse
True, that didn't occur to me. But since it was unlocked prior it may still be unlockable.
bp328i said:
People have already done this on working Pixel 3 XL's and all it did was returned an error.
Click to expand...
Click to collapse
Being a possible dev unit it might not error out with said command. At least that was my thought process. Doesn't hurt to try anyway? If it fails, it fails. Can't hurt to try.
Sent from my Pixel 3 XL using Tapatalk
I just soft bricked my PXL3; this means access only to fastboot ( is under warranty ) and you can get it back with fastboot flashing unlock critical then flash the factory image i don't get it why you can't
I thought flashing unlock critical was p2xl and not applicable to p3xl? And was your bootloader relocked prior to softbrick?
Sent from my Pixel 3 XL using Tapatalk
Update your adb tools on your computer and try flashing stock images again. Then reboot.
Help, i'm dealing with an issue too, everything was working fine, rooted with magisk , turned off my phone to charge, it reached 100% turned it back on, and it won't boot up, I see the G logo with a grey loading bar white background screen it does this for a few minutes and it reboots and gives me a screen that says "can't load android system. Your data may be corrupt. If you continue to get this message you may need to perform a factory data reset and erase all user data stored on this device" . I don't want to do a factory reset? WTH is going on here.
The last major change i did is install greenify4magisk but i didn't enable it (unchecked in magisk screen)
Help!
Edit: How do i do rescue OTA?