Hey folks sorry for my poor english
Well I woke up yesterday morning and my MotoG2013 went crazy asking for "backup account", and when I clicked on the notification asking for it, that simply crashed. Everything crashed, even android.phone and system processes. I rebooted the device hoping it was just some "normal" bug, since I rooted it never stopped bugging. But it simply reboots->keeps crashing->black screen.
Unfortunately it wasn't in debug mode when it died so I can't even use logcat. Anyway if I go bootloader->recovery it says /cache/* partitions are unreadable (???). Despite it all I tried with format, wipes, factory resets but nothing changes. Recovery is way buggy but it's impossibile to flash a new one. I tried TWRP, new Clockwork versions, Stock Recovery, nada de nada nothing. "Mismatched partition size" and old CWM still there, without even working. I can't reboot recovery, bootloader or even power my phone on.
At this point I was enough pissed off and tried desperate stuff like flashing stock rom, using "erase" commands from fastboot (well, I think my IMEI is gone.......) but none of this worked. MotoBoot simply WON'T flash. I tried fastboot, mfastboot, rsd lite, everything. I thought EMMC might be dead too....I don't know anymore
Sorry for long post and poor english, but does anybody have a hint about what the heck is going on with my phone? Every help would be appreciated
Bye
*Edit: I forgot that when I try flashing, the error is "Preflash validation fail"
Help pls
cyberpunkers92 said:
Help pls
Click to expand...
Click to collapse
what does bootloader say?
fastboot version and other details?
sd_shadow said:
what does bootloader say?
fastboot version and other details?
Click to expand...
Click to collapse
It doesn't help me much. Says my phone is unlocked (code 3)
Fastboot version 41.18, eMMC model, CPU and Ram models, transfer mode: USB connected. Also, my computer can recognize phone when I'm on bootloader but not in "normal" poweroff, because I disabled debugging a few days ago.
Bootloader just reports errors when I try flashing recovery (mismatched partition size), motoboot (preflash validation fail), gpt (it reports "downgrade" even though I had 4.4 and I tried to flash 5.1) and other random errors.
fastboot getvar info in spoiler
INFOversion: 0.5
INFOversion-bootloader: 4118
INFOproduct: falcon
INFOsecure: yes
INFOhwrev: 0x83C0
INFOradio: 0x1
INFOemmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
INFOram: 1024MB Hynix S4 SDRAM DIE=4Gb
INFOcpu: MSM8226 CS
INFOserialno: TA9290CNH4
INFOcid: 0x0007
INFOchannelid: 0x00
INFOuid: 0DEBC7020F000000000000000000
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmot_sst: 3
INFOmax-download-size: 536870912
INFOreason: Volume down key pressed
INFOimei:
INFOmeid:
INFOdate:
INFOsku:
INFOiccid:
INFOcust_md5:
INFOmax-sparse-size: 268435456
INFOcurrent-time: "Sun Aug 7 22:39:26 UTC 2016"
INFOro.build.fingerprint[0]: motorola/falcon_vfgbsl/falcon_umts
INFOro.build.fingerprint[1]: :5.0.2/LXB22.46-28.1/1:user/releas
INFOro.build.fingerprint[2]: e-keys
INFOro.build.version.full[0]: Blur_Version.220.27.1.falcon_umts
INFOro.build.version.full[1]: .VodafoneSL.en.GB
INFOro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
INFOro.build.version.qcom[1]: .04.04.02.048.045
INFOversion-baseband: MSM8626BP_1032.3105.93.00R VFGB_CUST
INFOkernel.version[0]: Linux version 3.4.42-gdd242b0 ([email protected]
INFOkernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
INFOkernel.version[2]: MP PREEMPT Thu Jan 22 16:15:51 CST 2015
INFOsdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
INFOsbl1.git: git=MBM-NG-V41.18-0-g5742832
INFOrpm.git: git=MBM-NG-V41.18-0-gcecd6e9
INFOtz.git: git=MBM-NG-V41.18-0-g99c1a7c
INFOaboot.git: git=MBM-NG-V41.18-0-g99084d5
INFOqe: qe 1/1
INFOro.carrier: unknown
all: listed above
finished. total time: 0.078s
Recovery doesn't work anymore, it doesn't even reboot itself or reboot in bootloader mode. I can access Recovery only from bootloader->Recovery or fastboot reboot-recovery
Unmountable partitions are /cache and /persist. Sdext is not recognized
A random CWM error
"E: can't open /cache/recovery/last_install
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed. Invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache (File Exists)
W: can't unlink /cache/recovery/command"
Then, trying with wipe/factory reset
"E: unknown volume for path [/sd-ext]"
What the.....??? Why? Root issues? Flash memory gone? I seriously have no clue.....
cyberpunkers92 said:
It doesn't help me much. Says my phone is unlocked (code 3)
Fastboot version 41.18, eMMC model, CPU and Ram models, transfer mode: USB connected. Also, my computer can recognize phone when I'm on bootloader but not in "normal" poweroff, because I disabled debugging a few days ago.
Bootloader just reports errors when I try flashing recovery (mismatched partition size), motoboot (preflash validation fail), gpt (it reports "downgrade" even though I had 4.4 and I tried to flash 5.1) and other random errors.
fastboot getvar info in spoiler
INFOversion: 0.5
INFOversion-bootloader: 4118
INFOproduct: falcon
INFOsecure: yes
INFOhwrev: 0x83C0
INFOradio: 0x1
INFOemmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
INFOram: 1024MB Hynix S4 SDRAM DIE=4Gb
INFOcpu: MSM8226 CS
INFOserialno: TA9290CNH4
INFOcid: 0x0007
INFOchannelid: 0x00
INFOuid: 0DEBC7020F000000000000000000
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmot_sst: 3
INFOmax-download-size: 536870912
INFOreason: Volume down key pressed
INFOimei:
INFOmeid:
INFOdate:
INFOsku:
INFOiccid:
INFOcust_md5:
INFOmax-sparse-size: 268435456
INFOcurrent-time: "Sun Aug 7 22:39:26 UTC 2016"
INFOro.build.fingerprint[0]: motorola/falcon_vfgbsl/falcon_umts
INFOro.build.fingerprint[1]: :5.0.2/LXB22.46-28.1/1:user/releas
INFOro.build.fingerprint[2]: e-keys
INFOro.build.version.full[0]: Blur_Version.220.27.1.falcon_umts
INFOro.build.version.full[1]: .VodafoneSL.en.GB
INFOro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
INFOro.build.version.qcom[1]: .04.04.02.048.045
INFOversion-baseband: MSM8626BP_1032.3105.93.00R VFGB_CUST
INFOkernel.version[0]: Linux version 3.4.42-gdd242b0 ([email protected]
INFOkernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
INFOkernel.version[2]: MP PREEMPT Thu Jan 22 16:15:51 CST 2015
INFOsdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
INFOsbl1.git: git=MBM-NG-V41.18-0-g5742832
INFOrpm.git: git=MBM-NG-V41.18-0-gcecd6e9
INFOtz.git: git=MBM-NG-V41.18-0-g99c1a7c
INFOaboot.git: git=MBM-NG-V41.18-0-g99084d5
INFOqe: qe 1/1
INFOro.carrier: unknown
all: listed above
finished. total time: 0.078s
Recovery doesn't work anymore, it doesn't even reboot itself or reboot in bootloader mode. I can access Recovery only from bootloader->Recovery or fastboot reboot-recovery
Unmountable partitions are /cache and /persist. Sdext is not recognized
A random CWM error
"E: can't open /cache/recovery/last_install
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed. Invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache (File Exists)
W: can't unlink /cache/recovery/command"
Then, trying with wipe/factory reset
"E: unknown volume for path [/sd-ext]"
What the.....??? Why? Root issues? Flash memory gone? I seriously have no clue.....
Click to expand...
Click to collapse
which model #?
which firmware versions are you using?
Can you flash TWRP? There are many twrp Versions to try
I got "mismatched part size" too, but twrp works perfect.
sd_shadow said:
which model #?
which firmware versions are you using?
Click to expand...
Click to collapse
Where can I see firmware version? I got no other access to phone info...only bootloader and fastboot getvar all...I don't
Model SM3767AE7B5 (or maybe 785, the label on the box is a little fuzzy)
Mattwmaster58 said:
Can you flash TWRP? There are many twrp Versions to try
I got "mismatched part size" too, but twrp works perfect.
Click to expand...
Click to collapse
I tried 5-6 TWRP versions and a few CWM too...nothing seems to change....I even tried double flash (flash recovery *recovery*, reboot bootloader, flash again), tried to flash once and directly go to recovery but nothing, there is always the same CWM version, a little "shaky" on the screen...
Strange thing is that fastboot says "OKAY" when I write it... I thought maybe I did wrong erasing recovery from fastboot, but it said the same even before and it was a desperate try...I had tried to change recovery (because mine isn't great) time few months ago and even if my phone was ok I NEVER managed to change it.
There's a sum of weird things and the phone seems totally unresponsive.
Additional error: I tried back flashing stock firmware and got "hab check fail" message from fastboot. What's this?
Thanks a lot to everyone that's trying to help, I'm not english native and sometimes I can't explain clearly where the problem is...
http://pastebin.com/UG8YQXFA
Ok this is what I get trying to flash all
cyberpunkers92 said:
Where can I see firmware version? I got no other access to phone info...only bootloader and fastboot getvar all...I don't
Model SM3767AE7B5 (or maybe 785, the label on the box is a little fuzzy)
I tried 5-6 TWRP versions and a few CWM too...nothing seems to change....I even tried double flash (flash recovery *recovery*, reboot bootloader, flash again), tried to flash once and directly go to recovery but nothing, there is always the same CWM version, a little "shaky" on the screen...
Strange thing is that fastboot says "OKAY" when I write it... I thought maybe I did wrong erasing recovery from fastboot, but it said the same even before and it was a desperate try...I had tried to change recovery (because mine isn't great) time few months ago and even if my phone was ok I NEVER managed to change it.
There's a sum of weird things and the phone seems totally unresponsive.
Additional error: I tried back flashing stock firmware and got "hab check fail" message from fastboot. What's this?
Thanks a lot to everyone that's trying to help, I'm not english native and sometimes I can't explain clearly where the problem is...
Click to expand...
Click to collapse
model # should be on the back cover towards the bottom of the phone
what is the firmware file name you are trying to flash
Sent from my XT1254 using XDA Labs
sd_shadow said:
model # should be on the back cover towards the bottom of the phone
what is the firmware file name you are trying to flash
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
Oh you meant Falcon XT1032 maybe
I tried several firmware, GPE_XT1032_KOTH49, GPE_51_XT1032_M005, well at least 6 versions, but always stock firmware for XT1032
Have you got any clue about what's going on? I tried pretty everything and I'm desperate
You can try the oneclick TWRP/5.1 GPE installer which can be found here: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
Just boot into bootloader and run the batch files and hope that your Moto G gets revived.
I flashed it. Motoboot went right and when I rebooted my phone it seemed to work but.......same wallpaper than before and when I opened "Settings" everything started crashing like before.
So....after all erases formats and stuff + flashings, it didn't even lose custom wallpaper???? There's something wrong here how is this possible?
I was thinking about "forcing" hard brick and trying to revive, the phone is completely unresponsive whatever I do/flash, it keeps going with same old recovery and same old screen. It's the weirdest hardware/software I ever had, it really seems like the phone didn't give a damn about what I put into, it doesn't even brick or stuff
What I get trying to wipe from CWM (recovery I had, that stays there EVEN AFTER "fastboot erase recovery"). I really don't know what to do...
In advanced options
cyberpunkers92 said:
I flashed it. Motoboot went right and when I rebooted my phone it seemed to work but.......same wallpaper than before and when I opened "Settings" everything started crashing like before.
So....after all erases formats and stuff + flashings, it didn't even lose custom wallpaper???? There's something wrong here how is this possible?
I was thinking about "forcing" hard brick and trying to revive, the phone is completely unresponsive whatever I do/flash, it keeps going with same old recovery and same old screen. It's the weirdest hardware/software I ever had, it really seems like the phone didn't give a damn about what I put into, it doesn't even brick or stuff
What I get trying to wipe from CWM (recovery I had, that stays there EVEN AFTER "fastboot erase recovery"). I really don't know what to do...
In advanced options
Click to expand...
Click to collapse
did factory reset in twrp?
Sent from my XT1060 using XDA Labs
sd_shadow said:
did factory reset in twrp?
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
Sd_shadow...ok I'm not the finest english speaker but I said from beginning and in almost every post that I'm totally unable to change recovery. I flash it and it says OKAY but when I reboot I got CWM like before, I tried ERASE RECOVERY too and when I reboot in recovery there's CWM.......formatted cache, erased recovery, reflashed everything and, after more or less 10 different firmwares and recoveries flashed with fastboot and with mfastboot + no less than 100 wipes/erases/formats all I got is:
OLD recovery CWM
Classical motorola logo boot
Screen with my OLD wallpaper
****load of error messages like "Motorola Contextual Services stopped working"
After a variable time (from 1 to n error messages we could say) the screen goes blank and I got to reboot.
As I said before the phone seems completely unresponsive to every kind of try...maybe it's hardware failure.
http://forum.xda-developers.com/moto-g/help/bricked-moto-g-emmc-failure-t2815499 I found this thread googling desperately and unfortunately my phone's issues are exactly those (though I have XT1032)
EDIT: this is my phone's status. When it died I had this wallpaper and I was in "only priority" mode because I set that up before sleep. The processes that crash are pretty randomic but often phone system or googlesomething or motorola contextual services. In this case, "phone" and "system" keep crashing in loop and the screen doesn't even go blank. In my last try (after the solution proposed by Dnlz) it crashed more slowly so I was able to set back notifications but it's back AGAIN to the "last snapshot" before death.
Images below
cyberpunkers92 said:
Sd_shadow...ok I'm not the finest english speaker but I said from beginning and in almost every post that I'm totally unable to change recovery. I flash it and it says OKAY but when I reboot I got CWM like before, I tried ERASE RECOVERY too and when I reboot in recovery there's CWM.......formatted cache, erased recovery, reflashed everything and, after more or less 10 different firmwares and recoveries flashed with fastboot and with mfastboot + no less than 100 wipes/erases/formats all I got is:
OLD recovery CWM
Classical motorola logo boot
Screen with my OLD wallpaper
****load of error messages like "Motorola Contextual Services stopped working"
After a variable time (from 1 to n error messages we could say) the screen goes blank and I got to reboot.
As I said before the phone seems completely unresponsive to every kind of try...maybe it's hardware failure.
http://forum.xda-developers.com/moto-g/help/bricked-moto-g-emmc-failure-t2815499 I found this thread googling desperately and unfortunately my phone's issues are exactly those (though I have XT1032)
EDIT: this is my phone's status. When it died I had this wallpaper and I was in "only priority" mode because I set that up before sleep. The processes that crash are pretty randomic but often phone system or googlesomething or motorola contextual services. In this case, "phone" and "system" keep crashing in loop and the screen doesn't even go blank. In my last try (after the solution proposed by Dnlz) it crashed more slowly so I was able to set back notifications but it's back AGAIN to the "last snapshot" before death.
Images below
Click to expand...
Click to collapse
You can try to boot TWRP using fastboot boot, this won't flash the image.
Erasing every partition on your phone was not very smart. Stop making choices without doing research.
Use mfastboot only.
Flash the latest XT1032 5.1 Retail US firmware image - it doesn't matter what firmware you had originally.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide logs of flashing process. Rename sparsechunks correctly, do not blindly follow tutorial commands.
Thanks a lot for "fastboot boot" hint. Hadn't seen it listed in commands, I didn't think I could! Anyway TWRP is unable to access /cache partition too...and wipe went apparently well (no errors) but, in fact, it DIDN'T wipe again
lost101 said:
Erasing every partition on your phone was not very smart. Stop making choices without doing research.
Use mfastboot only.
Flash the latest XT1032 5.1 Retail US firmware image - it doesn't matter what firmware you had originally.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide logs of flashing process. Rename sparsechunks correctly, do not blindly follow tutorial commands.
Click to expand...
Click to collapse
Tried right now. This time I've been able to boot the phone but the wallpaper and old settings stayed there. I was also able (between an error and another) to "enable" usb debugging but with no response from pc, I mean, it simply allowed me to tick the box with no effect. Because of "Settings" working apparently properly, I tried to do factory reset from phone. It's a blank button, I click and click on "erase all" but it simply doesn't.
That's absolutely weird...it's not THAT broken to say "yeah ok faulty hardware" but even after every kind of wipe it doesn't wipe.
I was thinking...motog has one only internal storage and no sd slot. Is it possible that this is a snapshot of last working system (shadow copy? sort of cache? I don't know) but memory has failed? Some files are apparently staying on memory (pics etc), I see them from TWRP file manager, and this is absolutely impossible because I destroyed that partition at least 100 times.
@cyberpunkers92 - There is nothing unusual about anything you have described. I read threads about it multiple times a week. It's classic emmc corruption symptomatology. Now stop talking about how strange it all is and do what I tell you to do.
@lost101 as I said, I did it and it didn't work. Nothing in logfiles, everything okay but I reboot and that's the same. I wipe by recovery and it doesn't wipe. Did you tell me to do more than this?
cyberpunkers92 said:
@lost101 as I said, I did it and it didn't work. Nothing in logfiles, everything okay but I reboot and that's the same. I wipe by recovery and it doesn't wipe. Did you tell me to do more than this?
Click to expand...
Click to collapse
I asked to see a log of the mfastboot flashing process. I want you to clearly state what happens; saying "it doesn't work" is not helpful.
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 have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
dominolapin said:
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Flashalot said:
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
"STOCK" recovery. I think you have tried with CUSTOM recovery.
Here is the link for stock recovery. The second download link is the stock recovery image
Flash stock recovery, then relock boot loader and then follow the above procedure :good:
Actually I did flash the stock recovery I just typed custom by mistake. Sorry about that. The one I flashed even came from the same link .
I searched on the forums and I might not have flashed the right ruu.
But i can't seam to find the right one, because strangely "fastboot getvar version-main" gives a blank result.
Hboot 1.14.0002
radio 1.08es.50.02.16
CID HTC_247
Hello Guys, I need your help.
I got this INSPIRE 4G from a friend. When he gave it to me, he said it needed to be flashed.
The thing is, When you press the power button, it boots straight up into Fastboot.
Here Is my Hboot Info
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
Emmc-boot
Apr 12 2011,00:55:45
In Fastboot, i can move around with the volume buttons and power buttons(so that means the phone booting straight into Fastboot isnt a result of one of the volume buttons being stuck.)
When i try to access recovery from the Bootloader, It vibrates 6 to 8 times then the screen becomes black,it stays that way until i do a battery pull.
When i select factory reset from the bootloader, it does nothing.
WHen i select Image CRC from the Bootloader,These is what is printed on the screen.
OSBL: 0xC2C4DD79
AMSS: 0x6CC260EB
HBOOT: 0xF9E06F63
BOOT: 0x0
RECOVERY: 0x0
SYSTEM: 0x0
As the digit are displayed, the first three look okay,but the last three which are BOOT RECOVERY and SYSTEM seem to have no digits, Which kinda looks like its empty.
THESE ARE THE SOLUTIONS I HAVE TRIED.
1. I tried flashing a recovery from Fastboot, but it gives an error like this:
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT0BFRX06133 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3704 KB)...
OKAY [ 0.664s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.672s
I get the same errors when i try to flash,erase or format the rest of the partitions(BOOT,SYSTEM).
2. I have also tried the HTC RUU, it finds the device and then gets stuck when it tries to boot into Android.
I have also tried the HTC RUU Hboot update but it also fails like the RUU ROm update.
3. I have also tried to flash the STock rom as PD98IMG.zip via bootloader, but when it finds the file, it asks me to press volume up to start update, when i press volume up, it loads the file and when its suppose to flash it, it sort of skips it and move to the next. It does that until its done the asks me to press power to reboot. Since it skips the files it stays the same after reboot.
3.I have Also tried flashing Eng-Hboot as PD98IMG.zip, But it skips that also.
4. I also tried to use this command Fastboot oem boot
And this is what i get:
C:\Program Files\Minimal ADB and Fastboot>Fastboot oem boot
...
(bootloader) Error status=0x400008
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) DATA_TIMEOUT
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 13
(bootloader) [ERR] boot image does not exist!!!
OKAY [ 1.418s]
finished. total time: 1.418s
I am begining to think that some how the partitions are corrupt or something.
PLEASE HELP ME OUT!!
@krook6023 The reason why i posted there also was because i wasnt sure what device it is wether its a DHD or INSPIRE 4G since it doesnt boot up and is stuck in bootloader,thats why i posted there also.Hope you understand and open the other thread incase someone over there has the answer to my problem.
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
spokanite said:
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
Click to expand...
Click to collapse
Thanks for your reply.But i tried 2. and made sure android-info.txt was appropriate, it just wouldnt flash. Looked like the partitions were corrupt thats why it wouldnt flash.
This is how it usually acts.
It finds the file, Loads the file on the upper right side of the bootloader with a green loading bar, after that, when its time for it to flash, normally shows up in red loading bar. It just moves as if it was flashing a 1kilobyte file. Then asks me to reboot.
After reboot nothing happens. Stays the same way.
But Right now, its even worse. After installing QHSUSB_DLOAD drivers, its refused to boot into bootloader ever since. but shows up as QHSUSB_DLOAD when connected to my pc.
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
bananagranola said:
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
Click to expand...
Click to collapse
I tried flashing CWM,TWRP,STOCK.... but non of them worked.
But as i said, after installing some drivers i found for QHSUSB_DLOAD, it no longer boots into bootloader.
But when i connect the device to a computer it only shows up as QHSUSB_DLOAD.
Any Help On that?
Nope, no idea. What drivers? From where?
bananagranola said:
Nope, no idea. What drivers? From where?
Click to expand...
Click to collapse
I found it on one of the threads.
at first, when the phone is connected to the pc, the charge light turns on and shows up as QHSUSB_DLOAD, but now no light or bootloader, just QHSUSB_DLOAD
Was it a DHD thread?
bananagranola said:
Was it a DHD thread?
Click to expand...
Click to collapse
Yea i guess so.
After the driver stopped the device from booting into bootloader, i read the README file that came with the driver and found out that it was for Some sort of Qualcomm Modem Device.
I guess thats why it bricked the device.
What thread?
bananagranola said:
What thread?
Click to expand...
Click to collapse
I cant seem to remember what thread it is. Cause I downloaded lost of the drivers from different threads. So I cant tell which one is from which thread.
Yeah, I don't think I can help you then.
Is it actually fully bricked yet? What exactly happen when you power on the device unplugged usb?
I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?
megamonkey said:
I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?
Click to expand...
Click to collapse
You probably have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
You'll need to unlock your bootloader, which will wipe your device, but it's the only way. I have a guide here that explains how to unlock it (also how to install adb/fastboot and the drivers). Once you've unlocked your bootloader, put the persist file in your fastboot folder, open a command prompt from within your fastboot folder (shift + right click, then select open command prompt here), and issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
Once it's done flashing you can try rebooting your phone. If it still doesn't boot you'll have to go back to my guide and follow the instructions in section 8 to flash the stock images.
There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!
megamonkey said:
There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!
Click to expand...
Click to collapse
Unfortunately not if you can't boot into the OS.
I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?
megamonkey said:
I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?
Click to expand...
Click to collapse
Yeah, this happens sometimes. I can only suggest you try again in the hope that it works, without the bootloader unlocked there's gonna be nothing you can really do.
So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...
megamonkey said:
So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...
Click to expand...
Click to collapse
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.
Heisenberg said:
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.
Click to expand...
Click to collapse
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?
megamonkey said:
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?
Click to expand...
Click to collapse
I'm pretty sure others in similar situations to you have used it, I could be wrong.
Heisenberg said:
I'm pretty sure others in similar situations to you have used it, I could be wrong.
Click to expand...
Click to collapse
I tried using the method but I'm not sure why it isn't working. I ran the program and it gave me a few problems letting me know what's wrong with my phone:
userdata_64G.img: FAILED
boot.img: FAILED
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
I'm running near the end where nothing is going my way and I may need to either ask someone to attempt to fix it or buy a new phone...
Hello. Today, my wife's phone stopped responding to anything out of blue. I did a forced reboot (Vol down + power) and it rebooted and worked fine for a bit. Seeing as Android 10 was out, I dled fota file and flashed it via recovery from SD card, like I usually do. It flashed successfully and then rebooted. Once it booted, after a few seconds it hanged and became unresponsive again. Forced reboot once again, except this time it booted into a fastboot mode on its own and here lies there problem:
- going through an option to get into recovery mode doesn't help as it goes back into fastboot mode again
- rebooting through cmd doesn't help either
- pressing start just returns to fastboot mode
- shutting it down through an option in fastboot and then turning it on still yields the same result.
Basically, whenever phone turns on, it goes into a fastboot mode whether you want it or not.
Has this happened to anyone else? Any idea how to fix it?
Upd:
Code:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
Seems like update failed to flash into slot B and it's not bootable
Okay, so I fixed it.
I flashed service/raw fw through fastboot, commenting out userdata formatting part of the flashall_aft script (fastboot -w). After this, I was able to access recovery mode. In recovery mode, I flashed build 16.1220.1909.194 and then 17.1810.1910.63 from my SD card and phone came alive, while retaining all the data.
Perhaps, this information will help someone who will encounter the same situation.
can u provide links for service /raw fw and how did u flashed it.
My Asus ZS630KL is stuck at fastboot mode neither rebooting to recovery works nor flashing custom boot or stock boot works. how to flash back stock rom in fastboot mode.
DAMONDARK said:
can u provide links for service /raw fw and how did u flashed it.
My Asus ZS630KL is stuck at fastboot mode neither rebooting to recovery works nor flashing custom boot or stock boot works. how to flash back stock rom in fastboot mode.
Click to expand...
Click to collapse
Sure. You can get RAW one here. Unzip, cd to the folder and launch flashall_aft script in cmd. There a bash script in the folder in case you have a Unix system. Script will output "Download_PASS" when it's done. Do not disconnect your phone before then.
Note, by default, this will wipe your userdata partition. You can prevent that my commenting out/removing line 264 in the script. However, note, if you don't wipe userdata partition, until you upgrade to the firmware that you currently have, the phone won't boot.
If your final firmware is latest one, with Android 10 (build 17.1810.1910.63), you will have to first update to 16.1220.1909.194. Links to both are in my previous post. I advice to flash desired firmware through Recovery -> Install update from SD card, though adb sideload should work just as well.
I'm thinking that "service/raw fw" is what is called a "fastboot rom" with Xiaomi?
Asus does not provide these themselves somewhere?
Or only for internal use?
Now I don't have a problem with my Z6 currently, but like to be prepared, like a good Boy Scout.
DAMONDARK, I wrote a more detailed guide if you need it. Click
cobben, ASUS does not provide those RAW firmwares to the public themselves. My guess is they are distributed internally for the use by service centers and alike and some ASUS workers upload them for public use. It's basically a set of tools along with signed images of all partitions to flash a full firmware to a specific device.
Images being signed (unlike images extracted via payload_dumper), device will accept them even without unlocked bootloader.
Not sure what this kind of firmware is called for Xiaomi
Ok, that is basically the same as the fastboot ROM with Xiaomi.
Xiaomi provides these publicly for anyone to use.
They have a Windows tool for this.
Requires unlocked bootloader, but bootloader can be relocked with no consequences.
Then there are other traps with Xiaomi, ARB primarily.
An incremental upgrade to a new major Android version is bound to cause some problems for some users, at best.
There should be a publically available way to restore the device to a known state.
cobben said:
Ok, that is basically the same as the fastboot ROM with Xiaomi.
Xiaomi provides these publicly for anyone to use.
They have a Windows tool for this.
Requires unlocked bootloader, but bootloader can be relocked with no consequences.
Then there are other traps with Xiaomi, ARB primarily.
An incremental upgrade to a new major Android version is bound to cause some problems for some users, at best.
There should be a publically available way to restore the device to a known state.
Click to expand...
Click to collapse
They did provide a zip to go back to latest Android 9 build which is WW-16.1220.1909.194. It can be found here
In most cases, the above should be enough. If your bootloader is unlocked, you don't really need service fw, you can just flash images dumped by payload_dumper from any zip of a build from ASUS website.
Additionally, service firmware does provide a lock script, which supposedly locks the bootloader but erases userdata. I have not tested if it actually re-locks bootloader.