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 all,
I have flashed numerous roms onto my TF300 over the months, and decided to have a go at the new Jelly Bean Hydro by seanzscreams. After flashing the US 400mb standard rom from ASUS, I followed the steps and went into fastboot. From there I used Imraans method of copying my fastboot.exe and the others onto a folder called Recovery1 in my Program Files (x86). However, my device does not seem to respond to any files that I am sending through to it..as in on my cmd it is just stuck at the 'sending 'recovery' <7304KB>. After being unable to send anything to my device and it not being able to boot (btw I did not receive any sort of signature flash confirmation) I decided to wipe my data from the bootloader. I was then able to boot into the ASUS JB rom (the US version, my tf300 is WW) , which I am currently using. Now, as twrp goo imanager is not up yet the only way I can flash any recovery is via my cmd..so what can I do? My bootloader is obviously unlocked, as I tap onto the USB icon and hit volume up my computer recognizes the fastboot device..but I am unable to send anything (or flash) into the device from fastboot..(to clarify this is the "fastboot -i 0x0B05 flash recovery twrp.blob" command.) This is most likely something very simple that I have not realized but if anyone can help, please respond!
Thanks in advance.
because Idsera
Von Clausewitz said:
Hi all,
I have flashed numerous roms onto my TF300 over the months, and decided to have a go at the new Jelly Bean Hydro by seanzscreams. After flashing the US 400mb standard rom from ASUS, I followed the steps and went into fastboot. From there I used Imraans method of copying my fastboot.exe and the others onto a folder called Recovery1 in my Program Files (x86). However, my device does not seem to respond to any files that I am sending through to it..as in on my cmd it is just stuck at the 'sending 'recovery' <7304KB>. After being unable to send anything to my device and it not being able to boot (btw I did not receive any sort of signature flash confirmation) I decided to wipe my data from the bootloader. I was then able to boot into the ASUS JB rom (the US version, my tf300 is WW) , which I am currently using. Now, as twrp goo imanager is not up yet the only way I can flash any recovery is via my cmd..so what can I do? My bootloader is obviously unlocked, as I tap onto the USB icon and hit volume up my computer recognizes the fastboot device..but I am unable to send anything (or flash) into the device from fastboot..(to clarify this is the "fastboot -i 0x0B05 flash recovery twrp.blob" command.) This is most likely something very simple that I have not realized but if anyone can help, please respond!
Thanks in advance.
Click to expand...
Click to collapse
EDIT: Seemed to fix it by changing to USB 2.0 port instead of 3.0..not sure why it would do that. In case anyone else had the same issue, try switching to an USB 3.0 Port.
Hey again, so, trying to fix the problem described here: http://forum.xda-developers.com/showthread.php?t=2523194, I decided to go back to stock rom (JellyBean 4.1.2 from LiquidSmooth 2.1). I did it trough fastboot (with a batch file) because I'm on windows 8.1 and can't get RSD to work.
So, fasboot gives me the error several times:
"(bootloader) variable not supported
target reported max download size of 3147280 bytes"
Now a have a phone that won't go past motorola logo. I can get to fastboot mode (but can't use rsd, doesn't recognice my phone) and my have my bootloader unlocked.
How should I proceed to bring it back to life? I've been trying everything I could.
Edit: Well, my phone is working again. I installed TWRP again and CM10.1
But I still not able to install a stock rom. So, I also was going to try with a virtual machine with different os but decided to not take (more?) risks.
If could be of use, I could install windows 7 on my machine.
daro.brussa said:
Hey again, so, trying to fix the problem described here: http://forum.xda-developers.com/showthread.php?t=2523194, I decided to go back to stock rom (JellyBean 4.1.2 from LiquidSmooth 2.1). I did it trough fastboot (with a batch file) because I'm on windows 8.1 and can't get RSD to work.
So, fasboot gives me the error several times:
"(bootloader) variable not supported
target reported max download size of 3147280 bytes"
Now a have a phone that won't go past motorola logo. I can get to fastboot mode (but can't use rsd, doesn't recognice my phone) and my have my bootloader unlocked.
How should I proceed to bring it back to life? I've been trying everything I could.
Edit: Well, my phone is working again. I installed TWRP again and CM10.1
But I still not able to install a stock rom. So, I also was going to try with a virtual machine with different os but decided to not take (more?) risks.
If could be of use, I could install windows 7 on my machine.
Click to expand...
Click to collapse
by "batch script" do you mean you tried this? http://forum.xda-developers.com/showthread.php?t=2474393
shouldn't give errors unless something in your partition table is messed up.
********Edit, i just read the other post and see you are on a 925, do not flash the script i suggested above.
bweN diorD said:
by "batch script" do you mean you tried this? http://forum.xda-developers.com/showthread.php?t=2474393
shouldn't give errors unless something in your partition table is messed up.
********Edit, i just read the other post and see you are on a 925, do not flash the script i suggested above.
Click to expand...
Click to collapse
Hey, I fixed it using this tool http://forum.xda-developers.com/showthread.php?p=38190729.
It installed stock rom by sending big files "in parts", I believe. So I dind't have problems with size. Thanks for your answer though.
Hey,
i was flashing a new ROM, the installation was all completed but when i rebooted the system, its now stuck in fastboot mode.
Tried flashing with KDZ as well as lgmdp but my phone refuses to get detected inspite of me having all the updated drivers. tried in 3 different comps, uninstalling everything n starting over at least 3-4 times in each. the phone just doesn't get detected. in each comp, the first plug-in showed the installation of only 3 drivers instead of the reqd 4 and did not get detected in any of the subsequent attempts.
shed some light here, guys..
[edit]
I just tried Android Flash Recovery. log says,
"fastboot: erase:recovery
fastboot: download:00701000
fastboot: flash:recovery
writing 7344128 bytes to 'recovery'
flash_write_image: out of space"
:-/
also, upon removing and re-attaching the data chord, fastboot says,
"--suspend--
--suspend--
--reset--
EP1/out FAIL nfo=40 pg0=74000
--portchange--
usb_read() transaction failed
fastboot: oops!"
oops??!! wht the F...!!
Morphie said:
Hey,
i was flashing a new ROM, the installation was all completed but when i rebooted the system, its now stuck in fastboot mode.
Tried flashing with KDZ as well as lgmdp but my phone refuses to get detected inspite of me having all the updated drivers. tried in 3 different comps, uninstalling everything n starting over at least 3-4 times in each. the phone just doesn't get detected. in each comp, the first plug-in showed the installation of only 3 drivers instead of the reqd 4 and did not get detected in any of the subsequent attempts.
shed some light here, guys..
[edit]
I just tried Android Flash Recovery. log says,
"fastboot: erase:recovery
fastboot: download:00701000
fastboot: flash:recovery
writing 7344128 bytes to 'recovery'
flash_write_image: out of space"
:-/
also, upon removing and re-attaching the data chord, fastboot says,
"--suspend--
--suspend--
--reset--
EP1/out FAIL nfo=40 pg0=74000
--portchange--
usb_read() transaction failed
fastboot: oops!"
oops??!! wht the F...!!
Click to expand...
Click to collapse
What device do you have? And what ROM did you attempt to install?
I'm guessing the "log" is what got printed on your screen? Unfortunately there's no actual way to log whats happening on the Windows end of fastboot. That's all output from fastboot on the phone. From what I'm seeing in what you posted, you tried to flash a recovery that is too big for the recovery partition. This may be a by-product from flashing with KDZ or the failed ROM you installed.
Try this, open a command-prompt in the \bin folder where Android Flash Recovery ( AFR ) resides on your hard drive. Attach your device to your PC and type 'fastboot devices' ( without the quotes ) and hit Enter. The response should look similar to the following if the device is detected by fastboot.exe ( PC end ):
Code:
list of devices attached
1234567890ABCDEF ????????
If only the 1st line and 2nd blank line are printed and not the 3rd line then fastboot.exe doesn't detect your phone either.
If your phone is detected, then more than likely the ROM you installed messed up your partition tables.
shinobisoft said:
What device do you have? And what ROM did you attempt to install?
I'm guessing the "log" is what got printed on your screen? Unfortunately there's no actual way to log whats happening on the Windows end of fastboot. That's all output from fastboot on the phone. From what I'm seeing in what you posted, you tried to flash a recovery that is too big for the recovery partition. This may be a by-product from flashing with KDZ or the failed ROM you installed.
Try this, open a command-prompt in the \bin folder where Android Flash Recovery ( AFR ) resides on your hard drive. Attach your device to your PC and type 'fastboot devices' ( without the quotes ) and hit Enter. The response should look similar to the following if the device is detected by fastboot.exe ( PC end ):
Code:
list of devices attached
1234567890ABCDEF ????????
If only the 1st line and 2nd blank line are printed and not the 3rd line then fastboot.exe doesn't detect your phone either.
If your phone is detected, then more than likely the ROM you installed messed up your partition tables.
Click to expand...
Click to collapse
I own a LG p500. and yes, i ended up getting it detected in lgmdp. i think we're supposed to connect the phone within a few seconds of entering emergency mode. i was attempting to install AOKP's JB build [aokp_tass_jb 30.05.13] and i guess the build is corrupted cos i got my phone working into a stock ROM, rooted it and installed it all over again, and yes, leaving me stuck in fastboot all over again.
I repaired it back into stock, rooted and flashed an earlier backup of an iCySnap build. however, my phone does not catch any network. i tried rebooting but nothin seems to happen.
Is it because i flashed it directly from froyo? should i try flashing the new baseband? (this thing just occurred to me, i will try it now.)
Morphie said:
I own a LG p500. and yes, i ended up getting it detected in lgmdp. i think we're supposed to connect the phone within a few seconds of entering emergency mode. i was attempting to install AOKP's JB build [aokp_tass_jb 30.05.13] and i guess the build is corrupted cos i got my phone working into a stock ROM, rooted it and installed it all over again, and yes, leaving me stuck in fastboot all over again.
I repaired it back into stock, rooted and flashed an earlier backup of an iCySnap build. however, my phone does not catch any network. i tried rebooting but nothin seems to happen.
Is it because i flashed it directly from froyo? should i try flashing the new baseband? (this thing just occurred to me, i will try it now.)
Click to expand...
Click to collapse
Flash the OldBBfix if you had the old baseband
But remember you have to flash it every time after you flash a newBB ROM (Cyanogen 7.1+ and every other GB+ ROM)
Read this thread by RC @shinobisoft for more information - http://forum.xda-developers.com/showthread.php?t=2149636
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Flash the OldBBfix if you had the old baseband
But remember you have to flash it every time after you flash a newBB ROM (Cyanogen 7.1+ and every other GB+ ROM)
Read this thread by RC @shinobisoft for more information - http://forum.xda-developers.com/showthread.php?t=2149636
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
v10 is the old BB, isnt it? i'd flashed it but it had failed. got it working by flashing a v20 version. anyways, none of this had ever occurred whenever i had rooted earlier, though i usually updated from froyo to gb before rooting and flashing. is that the reason? and is there anything i can do bout it??
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