Database Users

[Q] Problems Rooting - adb can't find my phone in step2

Hi, sorry for having to ask about this, but I have searched around and haven't found anything which worked for me.
I have an unbranded HTC Legend (bought it sim free)
Legend Unknown Ship S-ON
H-BOOT - 0.43.0001
Firmware version 2.1
Baseband version 47.26.35.04U_7.05.35.26L
Software number 1.31.405.5
Am I right in thinking this means I do not need to downgrade?
And since my phone isn't branded, am I right in thinking this means I do not need a goldcard? I remember reading this in a thread a while ago and it was confirmed by others.
When I try to root the output for the console is
Code:
$ ./step1-linux.sh
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
< waiting for device >
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option.
$ ./step2-linux.sh
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
So step 1 is saying it fails, but I don't know if this is a problem or not? I've read people saying just to continue anyway.
But for step 2 adb cannot find my phone so obviously doesn't work.
I'm on linux btw, so it wont be a window's driver issue.
Thanks for any help, and sorry again for the noobish question.

nope i had the custom id check fail, too.
rooted via xp. had this error in step2, too. sadly i dont know what i made wrong back then (maybe havent waited long enough for the /!\ to appear). but in your case step1 went just fine.

Thanks for the reply. So step 1 is working properly. But I'm still having the problem that adb cannot find my phone during step 2.
adb finds my phone when it's booted normally. USB debugging was enabled before I booted into the bootloader to start the process--I've read that that can affect it too.
Does anybody know why this might be?

easyonthev said:
Thanks for the reply. So step 1 is working properly. But I'm still having the problem that adb cannot find my phone during step 2.
adb finds my phone when it's booted normally. USB debugging was enabled before I booted into the bootloader to start the process--I've read that that can affect it too.
Does anybody know why this might be?
Click to expand...
Click to collapse
Do u have HTC synck installed on your computer? if u do, be shure to close it before u start, i have noticed that adb cant find my phone in recovery when its on..

I do not have htc sync installed, no. I'm using linux, but I have also tried with my friend's mac and gotten the same results.
Thanks anyway!

You really don't need step 2.. Just download the clockworkmod recovery.. (update.zip) and place it in the root of the sd-card.. along with the rooted rom you want to use.. reboot to recovery apply update.zip and install the rooted rom.. that should do the trick..
Sent from my Legend using XDA App

whitetigerdk said:
You really don't need step 2.. Just download the clockworkmod recovery.. (update.zip) and place it in the root of the sd-card.. along with the rooted rom you want to use.. reboot to recovery apply update.zip and install the rooted rom.. that should do the trick..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
You say that you dont need step 2 and just download clockworkmod recovery.. (update.zip) and put it in root.
I did all that but when i click "Apply:update.zip" It says
"E:signature verification failed"
Installation aborted
Any idea's on that?
P.s: I got the FAILED (remote: 42 custom id check fail) error on step 1 but everyone says it's ok.
Please help?
Thanks.

Hello!
Long-shot, but do you have a firewall?
My NOD32 was blocking something first time I tried to do step 2, but after I checked firewall restrictions - it went fine.
If you do have any firewall - disable it!
Hope that helps, cheers!

Ok first of there is so much to find concerning that error.
Google first then ask
Alright what ya want to do is , go here
http://forum.xda-developers.com/showthread.php?t=725430
Ignore the downgrade stuff download the hack file , use it as instructed then try again.
good luck.
EDIT:!
If your phone can't be found in step 2 make sure the port isn't open , I had , and have a huge problem connecting it as it opens so many ports , usualy a reboot of both cell and system fixes it for me. when you got it plugged in try using the netstat command to check if it's still open.

whitetigerdk said:
You really don't need step 2.. Just download the clockworkmod recovery.. (update.zip) and place it in the root of the sd-card.. along with the rooted rom you want to use.. reboot to recovery apply update.zip and install the rooted rom.. that should do the trick..
Click to expand...
Click to collapse
unfortunately didn't work:
Verifying update package...
E:signature verification failed
Installation aborted
dyki said:
If you do have any firewall - disable it!
Click to expand...
Click to collapse
I did have one, but unfortunately disabling it didn't help anything . Thanks anyway!
g0dshead said:
Ignore the downgrade stuff download the hack file , use it as instructed then try again.
Click to expand...
Click to collapse
Hey, Are you sure I need to do the crackin.sh stuff. I don't see how it'll particularly help me out: from what I can see it just pushes busybox and tests if you are okay to downgrade firmware. Please correct me if I'm wrong though!
Either way, it didn't work. adb still couldn't find my phone whilst in recovery
g0dshead said:
If your phone can't be found in step 2 make sure the port isn't open , I had , and have a huge problem connecting it as it opens so many ports , usualy a reboot of both cell and system fixes it for me. when you got it plugged in try using the netstat command to check if it's still open.
Click to expand...
Click to collapse
This sounds potentially like it could be the problem. Would you possibly be able to explain this a bit more in depth. Adb opens a port to connect to my phone yeah? And the reason why it loses my phone in recovery mode is that the port might have been closed?
Thanks for the help everyone.

I'm a newbie to android world but loving the experience so far. Returning to the actual problem i experienced the same issue when i rooted my Lagend but after a continues trying i made it finally. Hope following points may help you
1- Start the process again recrack your device using crackin.bat in hack4"DeviceName"-v5
Make sure it gives you the following line in the end (crwxrwxrwx should match anyways)
crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
If doesnt match do it again till u get the matching. (Though it will let you downgrade anyways even in case of no match it shows some thing like this cr--r--r-- but in rooting process it will create problem)
2- Then Downgrade the OS using Gold Card
3- Make Sure before clicking step-1 process your device is not connected to USB Cable First On it in Fast Boot wait for HBoot to find some update stuff then connect your phone to USB then select BOOT LOADER n run step 1 ( If it gives any error keep running this process again n again till it completes error free) After this plugout your gold card and put in some other sd card preferably formatted one.
4- Make Sure of repeating above in step two phase and keep running the process again n again until it detects your device and completes the process. I faced the same problem as you are facing but connecting USB cable in such mechanism i finally made it.
Important: Do this Using 32-bit OS machine as 64-bit OS machines gives problems.
Hope i could add value, Thanks

Was it any help bro?????

I have root
Hey guys.
thanks to everyone for the help. I've got it to work now by just using a goldcard.
Weird, since I've definitely read that a goldcard is not needed if your phone is unbranded. But apparently that wasn't true in my case.
Step 1 completed successfully with the goldcard. Step 2 did some things but then errored saying "exec '/system/bin/sh' failed: No such file or directory (2)", and just stayed at the ! screen. however, whitetigerdk was absolutely correct: I rebooted my phone to find it had been rooted.
I've downloaded rom manager, installed the custom recovery. I'm flashing cyanogenmod (azure) as we speak.
Thanks again everyone!

Need help repairing bootloader.

anyone know how to repair the partition table on our xperia play r800i?
my phone boots up after 2 days of being bricked.
now my problem is my phone says I've got no more space left as in 100kb-0 left that leads to unusable phone and FC FC and FC :|
factory/data reset wouldn't work. flashing via flashtool doesn't help also.
I get this error when erasing cache
PHP:
(bootloader) Erase operation complete, 2184 bad blocks encountered
OKAY [ 1.513s]
erasing 'cache'...
(bootloader) Erase of partition 'cache' requested
FAILED (remote: Partition not found, or permission denied)
and recovery says can't find /cache/recovery.log or something like that.
EDIT: so it seems that it was a bootloader problem. corrupted.
anyone could help me out please? I miss my phone and I really can't sleep with this broken
tried omnius. but I don't have a testpoint :|

gonemad02 said:
anyone know how to repair the partition table on our xperia play r800i?
my phone boots up after 2 days of being bricked.
now my problem is my phone says I've got no more space left as in 100kb-0 left that leads to unusable phone and FC FC and FC :|
factory/data reset wouldn't work. flashing via flashtool doesn't help also.
I get this error when erasing cache
PHP:
(bootloader) Erase operation complete, 2184 bad blocks encountered
OKAY [ 1.513s]
erasing 'cache'...
(bootloader) Erase of partition 'cache' requested
FAILED (remote: Partition not found, or permission denied)
and recovery says can't find /cache/recovery.log or something like that.
Click to expand...
Click to collapse
That does not look like a corrupt partition table, It looks like a corrupt nand chip.
"2184 bad blocks encountered" means s1 boot knows the correct size of the partition but the blocks are bad/corrupt either way s1 boot is responsible for handling the partition table so ask one of the bootloader unlockers if they can repair bootloader for you, most do it for free

I see. thanks for the response mate
who can help me for free?
will he?
http://forum.xda-developers.com/showthread.php?t=1252038
Click to expand...
Click to collapse

gonemad02 said:
I see. thanks for the response mate
who can help me for free?
will he?
Click to expand...
Click to collapse
Yep Alejandrissimo offers free bootloader repair, you should pm him and ask him for help

pm'd him a while ago. hope he responds soon. anyone else can do it for free? I really need this phone to be fixed adly
thanks alot matey!

gonemad02 said:
pm'd him a while ago. hope he responds soon. anyone else can do it for free? I really need this phone to be fixed adly
thanks alot matey!
Click to expand...
Click to collapse
Afaik he's the only one.
Regards Dousan...

Pm jinx13 he can also help you out!
Sent from my R800i using XDA App

pm'd him. pm'd 3 guys now hopefully someone replies very soon. I'll try to go for repair shops tom :|

Huawei P8 LITE soft bricked

Hello i wanted to install android 6.0 update(beta) to my p8 lite and now its stuck at huawei logo (one you get when you turn on your phone)
i was looking and trying different update.app files to restore it in recovery mode but none worked all gave me an error any ideas how i can sort it out i wanted to try emui website and hisuite but none have firmware for my p8 lite
I have a single sim uk p8 lite

How did you tried to install ?

VladHD said:
How did you tried to install ?
Click to expand...
Click to collapse
i download a update.app file aka firmware i put it in dload folder on my sd card (not internal memory of the phone ) i hold power button and both +- volume buttons and hold till it starts restoring it goes to 5% and fails

VladHD said:
How did you tried to install ?
Click to expand...
Click to collapse
with some UPDATE.app files it didn't even reach 5% it reached 0% and said version check fail

Reflash the system partition. If you lose your imei just upgrade over ota. So take the first rom that was oit for your device (i have dual sim so i don't know your firmware) you probaly took the dual sim software

Lordbannakaffalatta said:
Reflash the system partition. If you lose your imei just upgrade over ota. So take the first rom that was oit for your device (i have dual sim so i don't know your firmware) you probaly took the dual sim software
Click to expand...
Click to collapse
How am i supposed to do that ?

wolfaas12345 said:
How am i supposed to do that ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977/page1
Here you go. Follow this one and welcome in dual sim land :laugh:

Lordbannakaffalatta said:
http://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977/page1
Here you go. Follow this one and welcome in dual sim land :laugh:
Click to expand...
Click to collapse
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 15.264s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 15.269s

wolfaas12345 said:
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 15.264s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 15.269s
Click to expand...
Click to collapse
Is your bootloader unlocked?

Lordbannakaffalatta said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
no

wolfaas12345 said:
no
Click to expand...
Click to collapse
http://forum.xda-developers.com/p8l...unlock-code-huawei-immediately-t3242539/page1
Here you go follow this before you do anything.
Remember, first unlock bootloader than you can flash Roms and get root.
---------- Post added at 01:35 AM ---------- Previous post was at 01:33 AM ----------
wolfaas12345 said:
no
Click to expand...
Click to collapse
Btw are you Sure you're phone is An ALE-L21?

Lordbannakaffalatta said:
http://forum.xda-developers.com/p8l...unlock-code-huawei-immediately-t3242539/page1
Here you go follow this before you do anything.
Remember, first unlock bootloader than you can flash Roms and get root.
---------- Post added at 01:35 AM ---------- Previous post was at 01:33 AM ----------
Btw are you Sure you're phone is An ALE-L21?
Click to expand...
Click to collapse
just lol i tried to unlock it using this method few hours ago but i failed and i just found out why in model number instead of typing in HUAWEI Y300-0000 i was typing in Y300-0000 now its solved

wolfaas12345 said:
just lol i tried to unlock it using this method few hours ago but i failed and i just found out why in model number instead of typing in HUAWEI Y300-0000 i was typing in Y300-0000 now its solved
Click to expand...
Click to collapse
I actually laughed so haard that i waked up the Gf. That's the same thing that would happen to me ????

Lordbannakaffalatta said:
I actually laughed so haard that i waked up the Gf. That's the same thing that would happen to me ????
Click to expand...
Click to collapse
just lol how simple mistakes make such difference im trying to fix it now il keep ya updated

wolfaas12345 said:
just lol how simple mistakes make such difference im trying to fix it now il keep ya updated
Click to expand...
Click to collapse
Good luck.

Lordbannakaffalatta said:
Good luck.
Click to expand...
Click to collapse
ok now i have null imei numbers any ideas on that one ?

wolfaas12345 said:
ok now i have null imei numbers any ideas on that one ?
Click to expand...
Click to collapse
Perfect just update trough ota (settings -> updater)

Lordbannakaffalatta said:
Perfect just update trough ota (settings -> updater)
Click to expand...
Click to collapse
no updates

wolfaas12345 said:
no updates
Click to expand...
Click to collapse
Wich version are you on?

lordbannakaffalatta said:
wich version are you on?
Click to expand...
Click to collapse
ale-l21c432b132

[Solved!] Moto G5 Plus: Hard bricked - recognized as "qhsusb_bulk"

Hello guys, I'm desperated. Tried to install the .67 update and did it wrong. Now I have hard bricked my Moto G5 Plus.
I tried this, but no luck at all...
So, any help will be much appreciated.
LOG:
D:\Flia. Romano\Downloads\Android\Moto G5 Plus\blank-flash\blankflash>.\qboot.ex
e blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 70 (0x46)
[ 0.004] ...cpu.sn = 2491206852 (0x947cccc4)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.009] ...filename = singleimage.pkg.xml
[ 0.013] Loading programmer
[ 0.013] ...filename = programmer.mbn
[ 0.013] Sending programmer
[ 0.228] Handling things over to programmer
[ 0.228] Identifying CPU version
[ 0.230] Waiting for firehose to get ready
[ 11.341] ReadFile() failed, GetLastError()=0
[ 11.396] ReadFile() failed, GetLastError()=0
[ 11.399] ReadFile() failed, GetLastError()=0
[ 21.118] ReadFile() failed, GetLastError()=0
[ 21.173] ReadFile() failed, GetLastError()=0
[ 21.178] ReadFile() failed, GetLastError()=0
[ 60.508] Waiting for firehose to get ready
[ 63.509] WriteFile() failed, GetLastError()=0
[ 68.432] ReadFile() failed, GetLastError()=0
[ 97.252] ReadFile() failed, GetLastError()=0
[120.558] ...MSM8953 unknown
[120.558] Determining target secure state
[120.561] Waiting for firehose to get ready
[125.513] ReadFile() failed, GetLastError()=0
[181.382] ...secure = no
[181.405] Waiting for firehose to get ready
[241.438] Configuring device...
[241.441] Waiting for firehose to get ready
[301.479] Waiting for firehose to get ready
[361.512] Waiting for firehose to get ready
[421.657] Waiting for firehose to get ready
[482.043] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->devic
e_read()->IO error
[482.043] Check qboot_log.txt for more details
[482.043] Total time: 482.044s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffe
r_read()->device_read()->IO error
D:\Flia. Romano\Downloads\Android\Moto G5 Plus\blank-flash\blankflash>pause
Presione una tecla para continuar . . .

hola soy de argentina y tengo el mismo problema con un g5s plus como llo solucionaste?
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
MarckozZ said:
I MADE IT!!!!!! I HAVE MY POTTER BACK!!!!!!!!!!!!!
I'll be making a guide just in case anyone wants to try this... But it will be risky as hell!!! Tomorrow I'll make the guide + story of what I faced after flashing (IMEI = 0)!
Click to expand...
Click to collapse
hola tengo el mismo problema con un moto g5s plus como hiciste para solucionarlo

santiagoeg said:
hola soy de argentina y tengo el mismo problema con un g5s plus como llo solucionaste?
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
hola tengo el mismo problema con un moto g5s plus como hiciste para solucionarlo
Click to expand...
Click to collapse
Please follow XDA rules.
All threads should be in English only.
You can use Google translate to translate in English.

MarckozZ said:
Hello guys, I'm desperated. Tried to install the .67 update and did it wrong. Now I have hard bricked my Moto G5 Plus.
Now, this is my question. Can I unbrick it using the other methods there are to unbrick another Moto phones such as Moto G 2013 or Moto g4 Plus?
Or there are some specific files I must have to make it work?
I read I need some specific files... What should I do?
Click to expand...
Click to collapse
I bricked mine installing the 67 Ota update while rooted.. But wasn't hard bricked (please define hard bricked) as I could still boot to bootloader. I used windows pc program from here the moto g5 plus toolkit flashed stock
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
alevity said:
I bricked mine installing the 67 Ota update while rooted.. But wasn't hard bricked (please define hard bricked) as I could still boot to bootloader. I used windows pc program from here the moto g5 plus toolkit flashed stock
Click to expand...
Click to collapse
I see your a senior member and don't mean to question you when you say hard bricked. Even if you can't get it to boot to bootloader the tool kit may still recognize it as connected

alevity said:
I bricked mine installing the 67 Ota update while rooted.. But wasn't hard bricked (please define hard bricked) as I could still boot to bootloader. I used windows pc program from here the moto g5 plus toolkit flashed stock
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
I see your a senior member and don't mean to question you when you say hard bricked. Even if you can't get it to boot to bootloader the tool kit may still recognize it as connected
Click to expand...
Click to collapse
Well I had a Moto G, Moto G3 and this Moto G5 Plus, so I flashed things a LOT of times on the past two phones but, when I mean hard bricked here is HARD BRICKED!
No response at all, no bootloader screen or whatsoever, plus "qsusb_bulk" when plugging it to my PC: hard brick. I know that one member here made a blankfile to flash this device "potter" but it doesn't work for me... So, I'm pretty much trapped in this situation...

MarckozZ said:
Well I had a Moto G, Moto G3 and this Moto G5 Plus, so I flashed things a LOT of times on the past two phones but, when I mean hard bricked here is HARD BRICKED!
No response at all, no bootloader screen or whatsoever, plus "qsusb_bulk" when plugging it to my PC: hard brick. I know that one member here made a blankfile to flash this device "potter" but it doesn't work for me... So, I'm pretty much trapped in this situation...
Click to expand...
Click to collapse
Damn bro... Hmm.. I've been flashing since donut and I am soo grateful and probably just lucky I have never managed a hard brick.. Thought I did few times. Flashed wrong Rom as well once (luckily Samsung devices are lil easier to recover).. I have soft bricked and panic attacked myself so much over the years I seriously am starting to not want to do it anymore haha. I think we'll need to find a Motorola dev kit. Or possibly open it (not fun with this device video on youtube made me realize I won't be replacing the battery) and reset a jumper on the motherboard if that's even relevant with this device. It may have a soft fuse instead. But pretty much any hardware options are mute due to the low price of replacement....
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
Not suggesting anything... But a hard bricked device is kinda hard to tell you rooted.. Oem unlock does supposedly register you with moto.. But how long ago did you buy and where.. And do you have a young teenage daughter who can go in crying

alevity said:
Damn bro... Hmm.. I've been flashing since donut and I am soo grateful and probably just lucky I have never managed a hard brick.. Thought I did few times. Flashed wrong Rom as well once (luckily Samsung devices are lil easier to recover).. I have soft bricked and panic attacked myself so much over the years I seriously am starting to not want to do it anymore haha. I think we'll need to find a Motorola dev kit. Or possibly open it (not fun with this device video on youtube made me realize I won't be replacing the battery) and reset a jumper on the motherboard if that's even relevant with this device. It may have a soft fuse instead. But pretty much any hardware options are mute due to the low price of replacement....
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
Not suggesting anything... But a hard bricked device is kinda hard to tell you rooted.. Oem unlock does supposedly register you with moto.. But how long ago did you buy and where.. And do you have a young teenage daughter who can go in crying
Click to expand...
Click to collapse
LOL, This device has less than one month old, I unlocked the bootloader today and instantly flashed the LATAM firmware and tried the .67 OTA and it died, And no kids! So, I'm screwed! Great isn't it?
I'll have to save to buy another phone until some solution comes up ( @vache please help!!!)

MarckozZ said:
LOL, This device has less than one month old, I unlocked the bootloader today and instantly flashed the LATAM firmware and tried the .67 OTA and it died, And no kids! So, I'm screwed! Great isn't it?
I'll have to save to buy another phone until some solution comes up ( @vache please help!!!)
Click to expand...
Click to collapse
Did you try with the linux recovery tools?
Probaste con el script en linux?

Cronoss said:
Did you try with the linux recovery tools?
Probaste con el script en linux?
Click to expand...
Click to collapse
No tengo una PC con dual boot y Linux por ahora... Vere si lo puedo mandar a un service.
I don't have a PC with dual boot and Linux at the moment... I'll see if I can send it to a service center.

MarckozZ said:
No tengo una PC con dual boot y Linux por ahora... Vere si lo puedo mandar a un service.
I don't have a PC with dual boot and Linux at the moment... I'll see if I can send it to a service center.
Click to expand...
Click to collapse
Proba con virtualbox que es gratis. Bajate Ubuntu y hacelo desde ahi. No es dificil. Vale la pena probar.
Try installing virtualbox which is free. Download something like Ubuntu and do it from there. It's not hard.

Cronoss said:
Proba con virtualbox que es gratis. Bajate Ubuntu y hacelo desde ahi. No es dificil. Vale la pena probar.
Try installing virtualbox which is free. Download something like Ubuntu and do it from there. It's not hard.
Click to expand...
Click to collapse
I'll try this. The thing is I don't have enough RAM to run a VirtualBox instance, So I'll have to make another partition

Same thing happened to me and I'm visiting another country. What a nightmare.

Tomadock said:
Same thing happened to me and I'm visiting another country. What a nightmare.
Click to expand...
Click to collapse
Yea bro... I'll try to find a way to get this solved!

Cheering for you all

Its been a long while, but I'm pretty sure if it says qusb_bulk when you plug it into USB, then all hope isn't lost. A quick google of "qusb_bulk fix" brings up a lot of results and things to try. Maybe start here. https://www.google.com/amp/s/amp.reddit.com/r/MotoX/comments/4dt59q/qhsusb_bulk_fix/

itslels said:
Its been a long while, but I'm pretty sure if it says qusb_bulk when you plug it into USB, then all hope isn't lost. A quick google of "qusb_bulk fix" brings up a lot of results and things to try. Maybe start here. https://www.google.com/amp/s/amp.reddit.com/r/MotoX/comments/4dt59q/qhsusb_bulk_fix/
Click to expand...
Click to collapse
Thanks for coming bro. Already tried this and it doesn't work! 'll have to live with this until devs come up with new blankflash files to revive this thing!

@MarckozZ
Sorry for the bad english, I'm at fault in this but the google translator too.
Hello Friend, I went through the same situation as you with the .67 update. Although I unlocked the bootloader and invalidated the warranty, I decided to take it to the assistance of the motorola, because I believe that its technicians are trained and because it is a local representative of the motorola, they are also honest ... just to hear from them that I needed to change the Plate and the cost for this is half a new here in Brazil. But after much research, I was convinced that it was not the card, so I opened the device and gave a shock to the battery, do not ask me why I did this, probably the desperation made me do it, but it did not help, the device continued unplugged , It just blinked the led when it was connected and was identified by the PC device manager, so I gave up for a while.
But as I was not happy using my motoE1 I decided to try one more time, it was when I came across this post:
Https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
And tried using the blankflash made available by vache for the potter but did not succeed in any of the countless attempts.
So I concluded that the .67 update should have been upgraded and so it was not possible to go back with the blankflash, but browsing through the tree of vache folders I saw that it had also available for the albus (MotoZ2Play) and I decided to take a risk, and because there A certain similarity between the two devices and this latest one worked out. I know I will be criticized for recommending this to you, but it was the only solution I got, but I can not fail to mention that after doing that things will not be the same anymore.
After having success with the tutorial of the above link using the blankflash of MotoZ2play that you can find here
Http://cloud.vache-android.com/Moto/albus/blankflash/
You have to use bootloader, gpt and addison recovery (MotoZplay)
Https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U
To return to stock rom.
It's important to do this right after the blankflash tutorial here:
Https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Once this is done you can use the Moto.G5.Toolkit available here
Https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
To install NPN25.137-33 / 35, but do not forget to replace bootloader, gpt and recovery in the firmware folder.
Remember, that was the decision I made, so do it at your own risk, although the risk here is to bring it back, I do not know what it will be with future updates.
Good luck!

Paulo Narley said:
@MarckozZ
Sorry for the bad english, I'm at fault in this but the google translator too.
Hello Friend, I went through the same situation as you with the .67 update. Although I unlocked the bootloader and invalidated the warranty, I decided to take it to the assistance of the motorola, because I believe that its technicians are trained and because it is a local representative of the motorola, they are also honest ... just to hear from them that I needed to change the Plate and the cost for this is half a new here in Brazil. But after much research, I was convinced that it was not the card, so I opened the device and gave a shock to the battery, do not ask me why I did this, probably the desperation made me do it, but it did not help, the device continued unplugged , It just blinked the led when it was connected and was identified by the PC device manager, so I gave up for a while.
But as I was not happy using my motoE1 I decided to try one more time, it was when I came across this post:
Https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
And tried using the blankflash made available by vache for the potter but did not succeed in any of the countless attempts.
So I concluded that the .67 update should have been upgraded and so it was not possible to go back with the blankflash, but browsing through the tree of vache folders I saw that it had also available for the albus (MotoZ2Play) and I decided to take a risk, and because there A certain similarity between the two devices and this latest one worked out. I know I will be criticized for recommending this to you, but it was the only solution I got, but I can not fail to mention that after doing that things will not be the same anymore.
After having success with the tutorial of the above link using the blankflash of MotoZ2play that you can find here
Http://cloud.vache-android.com/Moto/albus/blankflash/
You have to use bootloader, gpt and addison recovery (MotoZplay)
Https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U
To return to stock rom.
It's important to do this right after the blankflash tutorial here:
Https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Once this is done you can use the Moto.G5.Toolkit available here
Https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
To install NPN25.137-33 / 35, but do not forget to replace bootloader, gpt and recovery in the firmware folder.
Remember, that was the decision I made, so do it at your own risk, although the risk here is to bring it back, I do not know what it will be with future updates.
Good luck!
Click to expand...
Click to collapse
IT WORKED!!!!
Well at least partially... I can enter bootloader now but, when I flash the firmware (using gpt, bootloader and recovery you gave) it only starts and shows the unlocked bootloader warning and restarts... So, it turns on now but I cant pass that warning screen.
Any suggestions?
What I did was this:
*blankflashed the albus files
*flashed the entire firmware (from US, 135-35)
Restarted but got a bootloop.. then..
*reflashed firmware but replacing bootloader, gpt and recovery from Z play (forgot to do this the first time )..
and still have a bootloop on the warning screen... am I missing something? Did you phone instantly rebooted as usual?
SO, basically what I will have is a Moto G5 Plus with Moto Z Play bootloader, GPT and recovery..

MarckozZ said:
IT WORKED!!!!
Well at least partially... I can enter bootloader now but, when I flash the firmware (using gpt, bootloader and recovery you gave) it only starts and shows the unlocked bootloader warning and restarts... So, it turns on now but I cant pass that warning screen.
Any suggestions?
What I did was this:
*blankflashed the albus files
*flashed the entire firmware (from US, 135-35)
Restarted but got a bootloop.. then..
*reflashed firmware but replacing bootloader, gpt and recovery from Z play (forgot to do this the first time )..
and still have a bootloop on the warning screen... am I missing something? Did you phone instantly rebooted as usual?
SO, basically what I will have is a Moto G5 Plus with Moto Z Play bootloader, GPT and recovery..
Click to expand...
Click to collapse
Super exciting that it's at least getting a boot loaded now.. I wondered if by any chance the issue now is that your trying to flash a stock rom that is a downgrade from the updated 67.. If it even recognized the update before bricking

alevity said:
Super exciting that it's at least getting a boot loaded now.. I wondered if by any chance the issue now is that your trying to flash a stock rom that is a downgrade from the updated 67.. If it even recognized the update before bricking
Click to expand...
Click to collapse
I sideloaded the OTA via adb, and the recovery flashed it without any problems at that moment... So it had the .67 update installed but also a corrupted bootloader.
Now, it doesn't have the .67 update anymore since i flashed the 135.35 US firmware. So the system has the 135.35 version, but with the recovery, partition table and bootloader from Moto Z Play.
After I push the power button it shows the warrning screen and either stays there, bootloops or shows a recovery screen with the circle animation with the word "Erasing" beneath, and then bootloop again.
My guess is that bootloader searchs for a suitable Moto Z Play firmware and, since it has another, it won't boot at all.
Also I'm worried now. Since this phone now has software parts fron another Moto phone, I wonder if I will be able to flash gpt.bin and bootloader.img from the upcoming O firmware. I'll die if now I'm only able to flash things from Moto Z Play instead of potter..

:fingers-crossed:
MarckozZ said:
I sideloaded the OTA via adb, and the recovery flashed it without any problems at that moment... So it had the .67 update installed but also a corrupted bootloader.
Now, it doesn't have the .67 update anymore since i flashed the 135.35 US firmware. So the system has the 135.35 version, but with the recovery, partition table and bootloader from Moto Z Play.
After I push the power button it shows the warrning screen and either stays there, bootloops or shows a recovery screen with the circle animation with the word "Erasing" beneath, and then bootloop again.
My guess is that bootloader searchs for a suitable Moto Z Play firmware and, since it has another, it won't boot at all.
Also I'm worried now. Since this phone now has software parts fron another Moto phone, I wonder if I will be able to flash gpt.bin and bootloader.img from the upcoming O firmware. I'll die if now I'm only able to flash things from Moto Z Play instead of potter..
Click to expand...
Click to collapse
After the albus blankflash you need to install the bootloader and gpt and reboot to the bootloader, then replace in the firmware folder NPN25.137-33 or 35 the bootloader gpt and recovery and then install all the firmware stock using the method you I recommend using Moto.G5.Toolkit to make everything easier, I have re-done the process of installing update .67 only to confirm that I would have the same problem and these steps helped me to solve it again.

This is obvious at this point, but pressing volume down + power does nothing? just shows the warning screen and loops?

I need help with my Moto G4 Plus XT1641 Hard Brick

C:\Users\marti\Desktop\blankflash_athene_8.1.0_OPJ28.72\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM8
[ 0.002] Detecting device
[ 0.003] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 43884472 (0x29d9fb8)
[ 0.003] Opening singleimage
[ 0.004] Loading package
[ 0.005] ...filename = singleimage.pkg.xml
[ 0.006] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.228] Handling things over to programmer
[ 0.229] Identifying CPU version
[ 0.230] Waiting for firehose to get ready
[ 60.320] Waiting for firehose to get ready
[120.413] ...MSM8952 unknown
[120.413] Determining target secure state
[120.415] Waiting for firehose to get ready
[180.501] ...secure = no
[180.508] Flashing GPT...
[180.508] Flashing partition:0 with gpt_main0.bin
[180.508] Initializing storage
[180.511] Waiting for firehose to get ready
[240.605] Configuring device...
[240.606] Waiting for firehose to get ready
[300.699] Waiting for firehose to get ready
[360.788] Waiting for firehose to get ready
[420.878] Waiting for firehose to get ready
[480.964] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[480.965] Check qboot_log.txt for more details
[480.966] Total time: 480.967s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
Click to expand...
Click to collapse
I tried with all the blankflash but anyone serves, please i need help.

How did your device hard brick? Was it by downgrading and then OTA updates?
Have you tried this blankflash https://forum.xda-developers.com/showpost.php?p=79012833&postcount=1012

echo92 said:
How did your device hard brick? Was it by downgrading and then OTA updates?
Have you tried this blankflash https://forum.xda-developers.com/showpost.php?p=79012833&postcount=1012
Click to expand...
Click to collapse
The hard brick was when i unlocked the bootloader to downgrade version Oreo (idk exactly but i remember that) and i installing Nougat 7.0 update.
I tried with that blankflash and the quote on the post is that blankflash did.

tsppx said:
The hard brick was when i unlocked the bootloader to downgrade version Oreo (idk exactly but i remember that) and i installing Nougat 7.0 update.
I tried with that blankflash and the quote on the post is that blankflash did.
Click to expand...
Click to collapse
Ah, you've hard bricked your device in a way we cannot rescue at the moment. Seems you've downgraded with fastboot? If so, your bootloader would not be downgraded. Using a Nougat OTA would then corrupt your Oreo bootloader.
Currently, we do not know if we'll ever get a newer blankflash (the OPJ28.72 blankflash was the last resort). Your options are to pay for a JTAG repair or motherboard replacement, or purchase a new device. I'm sorry, we've got no other options.

echo92 said:
Ah, you've hard bricked your device in a way we cannot rescue at the moment. Seems you've downgraded with fastboot? If so, your bootloader would not be downgraded. Using a Nougat OTA would then corrupt your Oreo bootloader.
Currently, we do not know if we'll ever get a newer blankflash (the OPJ28.72 blankflash was the last resort). Your options are to pay for a JTAG repair or motherboard replacement, or purchase a new device. I'm sorry, we've got no other options.
Click to expand...
Click to collapse
Anything at this moment?

tsppx said:
Anything at this moment?
Click to expand...
Click to collapse
No new news, currently only options require paying (for a new motherboard/repair or a new device).

echo92 said:
No new news, currently only options require paying (for a new motherboard/repair or a new device).
Click to expand...
Click to collapse
i´ve the same problem ;(

a1theros said:
i´ve the same problem ;(
Click to expand...
Click to collapse
Did you find anyone with a JTAG service who would be willing to try a repair?
Either way, you'd have to pay and use this as an expensive lesson in being careful whilst downgrading stock firmware.

echo92 said:
Did you find anyone with a JTAG service who would be willing to try a repair?
Either way, you'd have to pay and use this as an expensive lesson in being careful whilst downgrading stock firmware.
Click to expand...
Click to collapse
2 places with jtag service wont solved bro ;(, i going to buy an new motherboard

Any answer yet?

tsppx said:
Any answer yet?
Click to expand...
Click to collapse
There appears to be a paid service that has a working blankflash (think it's about $10 USD). As paid links aren't allowed on XDA, I would ask you to look through this page and the following pages: https://forum.xda-developers.com/mo...4-plus-hardbrick-solved-guide-t3657761/page67 You'll want to find members who have unbricked their device, please PM them to find out details on the service they used.