Develop Bugs

HELP LG G4 Bootloop issue

Recently after trying to upgrade my LG G4 to android 6.0 by flashing the zips in recovery, I encountered a boot loop. I have tried many thing like using the LG Flash Tool, I also tried booting into recovery and restoring a backup I made, but none of this made any difference. Please I need help.
LG G4 H815 android 5.1.1 or 6.0 (not sure) I'm not sure because I tried to flash the zips fro android 6.0 via recovery and didn't work, then I restored my phone and tried to boot up but that failed to work as well.

Try to use the LG bridge tool.
Start lg bridge.
Connect your device while off with your usb cable.
It will start - nevermind, just keep it going.
Use the "solve update issue" option in the bottom right corner of the software update screen in lg bridge.
It will reinstall 6.0 without data loss.

TheReino said:
Try to use the LG bridge tool.
Start lg bridge.
Connect your device while off with your usb cable.
It will start - nevermind, just keep it going.
Use the "solve update issue" option in the bottom right corner of the software update screen in lg bridge.
It will reinstall 6.0 without data loss.
Click to expand...
Click to collapse
It does not detect that the device is connected, even when it is.

Takes some time to detect. Worked for me an hour ago...

TheReino said:
Takes some time to detect. Worked for me an hour ago...
Click to expand...
Click to collapse
I might have fixed it using a different method.

Wich method?

I have the same issue.. I send my phone to the repair center of amazon. Let´s look what they can do.

Not necessary, in bootloop, just connect usb and start lgup, when it detect it, (and it will as unknown mode device) tap com port it was found on and ui will open, then click on phone info, it will connect and establish a valid usb connection to phone and open new prompt with phone info...... Then start adb command prompt and enter 'adb reboot recovery' and bingo you're in recovery.... Solves every bootloop!

spoonymoon said:
Not necessary, in bootloop, just connect usb and start lgup, when it detect it, (and it will as unknown mode device) tap com port it was found on and ui will open, then click on phone info, it will connect and establish a valid usb connection to phone and open new prompt with phone info...... Then start adb command prompt and enter 'adb reboot recovery' and bingo you're in recovery.... Solves every bootloop!
Click to expand...
Click to collapse
If the phone in bootloop, such phone does not see any one program
This phone can be started only in the DM

spoonymoon said:
Not necessary, in bootloop, just connect usb and start lgup, when it detect it, (and it will as unknown mode device) tap com port it was found on and ui will open, then click on phone info, it will connect and establish a valid usb connection to phone and open new prompt with phone info...... Then start adb command prompt and enter 'adb reboot recovery' and bingo you're in recovery.... Solves every bootloop!
Click to expand...
Click to collapse
How do you mean ?
tap com port it was found on
Click to expand...
Click to collapse

Brick lg g3 After update recovery bump help!

Good evening everyone my name mirko. Help me! I have a problem with my smartphone lg g3 32 Gb italian. I upgraded the recovery bumped .... when I rebooted the screen remains black and there are no signs of life. Do not even enter into download mode. the PC recognizes a sound hardware and wrote LGE Android net usb serial Com Port 7. know a way to help me? thank you

mirko0 said:
Good evening everyone my name mirko. Help me! I have a problem with my smartphone lg g3 32 Gb italian. I upgraded the recovery bumped .... when I rebooted the screen remains black and there are no signs of life. Do not even enter into download mode. the PC recognizes a sound hardware and wrote LGE Android net usb serial Com Port 7. know a way to help me? thank you
Click to expand...
Click to collapse
You have to use unbrick method....find in the forum...also what model you have and what the version of android?

My model is d855 and The android installed is lollipop fw d85520h
Inviato dal mio GT-I9505 utilizzando Tapatalk

1. You need to do is to check the latest version for your phone here by entering your phone's IMEI code.
2. Keep in mind the version and country and download the KDZ file you need.
3. Install LG drivers on your PC.
4. Go to this thread and from the section How to flash ROM KDZ Method start from the 3rd step.
This video shows how to get into Download Mode.
Then you have to root your phone again.
good luck

sharp3r said:
1. You need to do is to check the latest version for your phone here by entering your phone's IMEI code.
2. Keep in mind the version and country and download the KDZ file you need.
3. Install LG drivers on your PC.
4. Go to this thread and from the section How to flash ROM KDZ Method start from the 3rd step.
This video shows how to get into Download Mode.
Then you have to root your phone again.
good luck
Click to expand...
Click to collapse
Ok thanks, but unfortunately the problem of my phone and 'who does not enter the mode' download mode "the screen once connected and hold the volume button is all black and does nothing.
[emoji24] [emoji24]

mirko0 said:
Ok thanks, but unfortunately the problem of my phone and 'who does not enter the mode' download mode "the screen once connected and hold the volume button is all black and does nothing.
[emoji24] [emoji24]
Click to expand...
Click to collapse
You have unbrick your phone with board diag search lg g3 board diag you will find all the procedure and file....if any hekp needed we all are here for helping you....

mirko0 said:
Good evening everyone my name mirko. Help me! I have a problem with my smartphone lg g3 32 Gb italian. I upgraded the recovery bumped .... when I rebooted the screen remains black and there are no signs of life. Do not even enter into download mode. the PC recognizes a sound hardware and wrote LGE Android net usb serial Com Port 7. know a way to help me? thank you
Click to expand...
Click to collapse
Hi, mirko0. We have the same problem and we need to do the same procedures to find the solution.
As seen in the following links:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://arena4g.com/forum/threads/unbrick-hard-unbrick-d855.7/ (Brazilian portuguese tutorial)
http://open-freax.fr/guide-unbrick-your-lg-g3/
You'll have to open up your phone (seriously) and make a short circuit in the board. Than, your PC will recognize as Qualcomm 9008.
Do not forget:
Install the x32 or x64 drives
If x64, do not forget to disable drive check
If windows 10, do not forget to reboot in advanced mode and disable drivers check
Everytime the phone reboot, you'll need to make the short circuit. I know, a pain in the ass.
You'll need the MBN folder of the Lollipop or Marshmallow. This is our actual problem
I haven't found the MBN folder of 6.0(v30) or 5.0 (v20), just v10. We'll need those files to proceed.

I finally had to send my phone for repair and I have repaired under warranty, soon expected to return repaired

Locked bootloader by mistake, can't use the phone now

Hey all,
I just got a OnePlus 5T and because I needed a specific system language I decided to flash a custom ROM. I unlocked the bootloader, flashed Derpfest on it and it was all good until I made a mistake. From the Developers options I unchecked "OEM Unlocking" and then when I restarted into the bootloader I did a fastboot oem lock
Now the phone says it's corrupted and it won't boot. Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!

Emo113 said:
Hey all,
Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!
Click to expand...
Click to collapse
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps

sn809 said:
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps
Click to expand...
Click to collapse
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.

Emo113 said:
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.
Click to expand...
Click to collapse
That is superb. If you could do the other bit I would really appreciate it.
Thanks

sn809 said:
That is superb. If you could do the other bit I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Hey there, sorry I totally mis-read the last part of your original post as something that I should do and I didn't see that you need that. Since I used the MDM tool I didn't bother to try your way first and since the phone wasn't mine to keep I already gave it to the owner so I don't have access to it anymore.
Again, very sorry about that.

No dramas. I also got it from some one else who was kind enough to lend it to me and let me root it and wipe it clean and then get the file and start using his phone again.
Thanks

emmc error? Suddenly black screen

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.

slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)

150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.

slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

Post SS of the device manager after connecting the phone to the PC

150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.

@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...

Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722

slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode

150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.

nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.

150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?

nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.

150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.

Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?

slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?

Recover moto G5 with broken power button

Hello, everyone.
I have this moto G5 which power button doesn’t seem to work and it doesn’t let me enter fast boot mode (I think). Using adb in Linux, is there a way I can do it? I attached pictures of it when powering it on through USB and after pressing volume down.
Thank you in advance!

Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go

PhotonIce said:
Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go
Click to expand...
Click to collapse
I tried, but it didn’t work. The software, on windows (the Lenovo/motorola recovery tool) said it didn’t recognized it and asked to enter in fast boot, which takes me to what I said in my first post.

Haven't you entered fastboot in the second image?

My first answer would be yes, but whe recovery tool doesn’t recognize the phone on windows and it’s also not listed on Linux with the adb command, so my last answer is I’m really not sure.

try installing the correct drivers and checking that your cable does indeed support data transfer

PhotonIce said:
Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go
Click to expand...
Click to collapse
Hello again.
I tried checking the cable, like you suggested, and then I was able to go a step further: the cell phone communicates with the computer. But I’ve got an error message from the restore tool (it’s in Portuguese) when I try to recover that, briefly, says my models name is all “0”, what doesn’t seem normal.
Any ideas about where I can go from here? Thank you!

did you say that your device is a motorola? why are you using a lenovo tool?

PhotonIce said:
did you say that your device is a motorola? why are you using a lenovo tool?
Click to expand...
Click to collapse
Leneovo own Motorola