Database Info

Help with fixing my phone (Please help)

I am going to give you the complete situation so you guys can help with the best of your ability. Over the summer I was at my Grandmas house with my cousins and we were playing Minecraft on the iPod and iPad. I knew that they had it in the Android market and tried to get it. No luck because it was not compatible with my device (Motorola Fire XT 530). I read up on a tutorial to get any app in the store and that was to change the build.prop settings to nexus x or something so I could get it. I rooted my phone and tried it but it screwed up my keyboard and an error occured on screen. So I went into this program I had and completely deleted the file(build.prop, still have a back up though). I tried to turn on the phone but it was stuck in a boot loop . So it is still in the boot loop and I cant turn on my phone.
Things I have tried so far:
1. Plugging it into my computer (wont show up)
2. Clearing my memory and cache in recovery mode (still wont turn on)
3. ADB (wont show up, not even in recovery mode)
4. Using this tutorial http://forum.xda-developers.com/showthread.php?t=1920446 (Was able to get into the flash mode but MSM Flash 7227 wont install correctly for some reason (have updated drivers))
5. Cant use ODIN because my phone cant go into download mode
6. Using default recovery (not clockwork, dont think I can get it because I cant turn on phone) to update the file (didnt work because apparently Motorola locks there bootloader)
I dont think I left anything else out and am looking for a solution. I also have default recovery which may be an issue.
Thanks a lot for reading
FroggyWoggy25

Edit: Disregard my post

Froggywoggy25 said:
I am going to give you the complete situation so you guys can help with the best of your ability. Over the summer I was at my Grandmas house with my cousins and we were playing Minecraft on the iPod and iPad. I knew that they had it in the Android market and tried to get it. No luck because it was not compatible with my device (Motorola Fire XT 530). I read up on a tutorial to get any app in the store and that was to change the build.prop settings to nexus x or something so I could get it. I rooted my phone and tried it but it screwed up my keyboard and an error occured on screen. So I went into this program I had and completely deleted the file(build.prop, still have a back up though). I tried to turn on the phone but it was stuck in a boot loop . So it is still in the boot loop and I cant turn on my phone.
Things I have tried so far:
1. Plugging it into my computer (wont show up)
2. Clearing my memory and cache in recovery mode (still wont turn on)
3. ADB (wont show up, not even in recovery mode)
4. Using this tutorial http://forum.xda-developers.com/showthread.php?t=1920446 (Was able to get into the flash mode but MSM Flash 7227 wont install correctly for some reason (have updated drivers))
5. Cant use ODIN because my phone cant go into download mode
6. Using default recovery (not clockwork, dont think I can get it because I cant turn on phone) to update the file (didnt work because apparently Motorola locks there bootloader)
I dont think I left anything else out and am looking for a solution. I also have default recovery which may be an issue.
Thanks a lot for reading
FroggyWoggy25
Click to expand...
Click to collapse
First of all you cant use Odin to flash Motorola Devices because it is meant for Samsung phones.
Secondly answer these questions:
1. In PC which OS are you using?
2. Have you tried reinstalling RSD lite then rebooting?
Having stock recovery is no issue because you can't get any other in this phone.
It is easy to get it back working.
I suggest you to try some other PC.
OR
Follow these steps as in order.
1. Uninstall RSD lite.
2. Uninstall Motorola Drivers.
3. Now first install Motorola Drivers the RSD lite.
I think this may work for you.

I am using windows 7 on a laptop which may be the problem because it may be a hub not directly connected to the mother board. Thank you and I will try your suggestion.
Btw thanks for all your help over the last couple days.
I also used this on two other laptops but the MSM Flash still wont install for some unknown reason. So I dont think using RSD lite is the problem.

Here's the solution
I found the solution to your problem.
Download the attachment.
Extract it.
Copy the file in the extracted folder and paste it in C:/windows/system32/drivers
Reboot your PC
And yes you must connect it directly without any hub or something.
Actually these are the RSD lite drivers which I think your PC was unable to install correctly.

Okay I will try this when I get home from school. If this doesnt work could you try sending me the MSM Flash7227 driver?

Froggywoggy25 said:
Okay I will try this when I get home from school. If this doesnt work could you try sending me the MSM Flash7227 driver?
Click to expand...
Click to collapse
It is that one only.
Sent from my XT530 using xda app-developers app

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my problem after I plugged in my phone in flash mode

Froggywoggy25 said:
This is my problem after I plugged in my phone in flash mode
Click to expand...
Click to collapse
So locate that to C:/windows/system32/drivers/the-file-i-gave-you
It will install its drivers.
OR
Alternate way is to install Motorola Software Update from here
It will install drivers automatically as it also needs phone to be switched in flash mode(i.e. through flash drivers) to update phone software.

aweosomeabhijeet said:
So locate that to C:/windows/system32/drivers/the-file-i-gave-you
It will install its drivers.
OR
Alternate way is to install Motorola Software Update from here
It will install drivers automatically as it also needs phone to be switched in flash mode(i.e. through flash drivers) to update phone software.
Click to expand...
Click to collapse
This didnt work because to update drivers my computer has to recognize the phone which it cant. I would need the driver Flash MSM7227 for it to work. If you could find that EXACT file on your computer and send it to me that would be great. I tried the two things you stated but it says the phone is not connected so I cant download the updates.
This must be very frustrating for you but thanks for your help.

Sorry to say, but you kill boatloader of your phone. That mean msm7227 device.
Sent from my XT530 using xda app-developers app

If any one wants to send me the download of the drivers use this to find them.
http://www.youtube.com/watch?v=jv60G3wH1N8

Froggywoggy25 said:
This didnt work because to update drivers my computer has to recognize the phone which it cant. I would need the driver Flash MSM7227 for it to work. If you could find that EXACT file on your computer and send it to me that would be great. I tried the two things you stated but it says the phone is not connected so I cant download the updates.
This must be very frustrating for you but thanks for your help.
Click to expand...
Click to collapse
Don't know about the problem.
Maybe 64-bit system.
And don't download moto update. Download and install only Moto software update "tool".
I sent you the same drivers. But I think the problem is my 32-bit system or your 64-bit.
No, I am not frustrated, don't worry. :laugh:
Sent from my XT530 using xda app-developers app
---------- Post added at 04:45 AM ---------- Previous post was at 04:42 AM ----------
nesham said:
Sorry to say, but you kill boatloader of your phone. That mean msm7227 device.
Sent from my XT530 using xda app-developers app
Click to expand...
Click to collapse
Is it so?
I don't think so.
Have you experienced the same?
Sent from my XT530 using xda app-developers app

Check the link how to obtain the right files for the drivers. Second post from the top of page 2
And its unfortunate we are in very different time zones so its one to two posts per day and we have to wait
And Ive been frustrated since July because I still cant believe I deleted that file xD

Froggywoggy25 said:
Check the link how to obtain the right files for the drivers. Second post from the top of page 2
And its unfortunate we are in very different time zones so its one to two posts per day and we have to wait
And Ive been frustrated since July because I still cant believe I deleted that file xD
Click to expand...
Click to collapse
I know that I have given you the same file.
Don't know why it isn't working.
Sent from my XT530 using xda app-developers app

Are you sure? Because a lot of my things had two different files. Mind quickly checking again?

Froggywoggy25 said:
Are you sure? Because a lot of my things had two different files. Mind quickly checking again?
Click to expand...
Click to collapse
See yourself.
This is when my phone is connected in flash mode.

Okay well thanks for checking

Im thinking about getting another phone because this one is bust.
Im thinking about getting this phone again or getting the mytouch 4g non-slide.
Which one would be better?

Froggywoggy25 said:
Im thinking about getting another phone because this one is bust.
Im thinking about getting this phone again or getting the mytouch 4g non-slide.
Which one would be better?
Click to expand...
Click to collapse
Don't buy this crap again
Sent from my XT530 using xda app-developers app

[Q] HELP! LG Optimus 3D won't start (HARD BRICKED)

Hi! Got major problem. Recently I tried putting TWRP to my ICS 4.0.4 LG P920. I installed it (don't remember the TWRP version) but not quite correctly. If I try any ROM to install I always get in to statuts 7 error. If I try to run into reovery from ROM manager I get lying down Android with red triangle and a exclamation mark. I only managed to get in to recovery by POWER + VOLUME DOWN. But it still won't allowed me to install other ROM's such as Jellybean etc. Cache cleaning and Dalvik didn't helped. So I thought I will try this program http://theunlockr.com/2012/11/07/how-to-install-clockworkmod-recovery-on-the-lg-optimus-3d/ because it looked the easy way.
THE PROBLEM:
So I ran the program and chose to install LG Stock Recovery. It showed installation was successful. But now when I try to turn on the phone it goes in to restart loop (when on cord). Shows LG logo and restarts other and other and other. . . Can't even get into recovery. If plugged off and pressing power it shows logo and turn off.
Any advice would be VERY appreciated.

Tried this http://forum.xda-developers.com/showthread.php?t=2246001
Fastboot runs successfully but at the end my phone just vibrates but no LG logo shows up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anyone?

Try flashing 4.0.4 using the flashtool, then use OS-Hackings tool to install cwm recovery and wkparks bootloader if you want.
Sent from my LG-D620 using XDA Free mobile app
---------- Post added at 19:46 ---------- Previous post was at 19:36 ----------
Here is flashtool guide,
http://forum.xda-developers.com/showthread.php?t=1244490.
And here is OS-Hacking aio tool for recovery and bootloader, http://forum.xda-developers.com/showthread.php?t=2144738
Sent from my LG-D620 using XDA Free mobile app

Hi! I will try, but not sure if could do it with some missing images of instructions. Also, tried soldering 4 and 5 pins with 910 Kohm (it supposed to turn Lg phone in download mode), nothing happened.

Coolguy981 said:
Hi! I will try, but not sure if could do it with some missing images of instructions. Also, tried soldering 4 and 5 pins with 910 Kohm (it supposed to turn Lg phone in download mode), nothing happened.
Click to expand...
Click to collapse
If you are able to get into recovery, and get status 7 error, it usually means that the recovery is not compatible. If you want to install ics again just use the aio tool the last version is easy to use. And flash another recovery. Then flash rom.
Sent from my LG-D620 using XDA Free mobile app

shaqfu786 said:
If you are able to get into recovery, and get status 7 error, it usually means that the recovery is not compatible. If you want to install ics again just use the aio tool the last version is easy to use. And flash another recovery. Then flash rom.
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
Actually, I was able to get into recovery before using http://theunlockr.com/2012/11/07/how...lg-optimus-3d/ . Now I can't basically do anything: can't get into recovery, download mode or turn on.
https://vid.me/M21i

Ok, so I did everything in the instruction as http://forum.xda-developers.com/showthread.php?t=2268268 . Got the GREEN SOFTWARE DOWNLOAD mode, changed port to 41 etc. I managed to run SmartFlashTool_3D, cheched the port (41) Put the LGP920_110622.dll and LGP920_30A_AP.bin with LGP920_30A_CP.fls. An I've stucked with TimeOut error (my phone turn off durring this proccess even with full battery). Every single time I try. Any advice how to fix that?

Also tried different Flash tools. Tried B_SmartFlashTool_3D which showed the TimeOut error above in my post. Also tried LG Flash Tool. Problem is I never make it to the part it says Ready in the PORT1. Did everything on the instruction. Changed to port 41 when selected port 1 and it leaves me with :

When you get to that screen, press the arrow button, then it will show ready. Thereafter unplug usb and plug in again, it will then start flashing automatically.
Sent from my LG-D620 using XDA Free mobile app

Yes, I pressed the arrow, but it didn't change anything. Maybe I need different USB cable because I saw other people complaining about that. Also keep in mind that in the program there it says MODEL, it keeps blank space. Should it be so? In couple of Youtube videos I noticed that other people's smartphones were detected...

Coolguy981 said:
Yes, I pressed the arrow, but it didn't change anything. Maybe I need different USB cable because I saw other people complaining about that. Also keep in mind that in the program there it says MODEL, it keeps blank space. Should it be so? In couple of Youtube videos I noticed that other people's smartphones were detected...
Click to expand...
Click to collapse
After hiting the yellow arrow in lg flashtool you have to reconnect the phone.
Also you can try flashtool2014 https://mega.co.nz/#!Hlo22baS!zXV3VKRZzOI5EtO5MEAUzICC5kcx-a7xAGspZzhKMFs
You have to instal lgb2c before that https://mega.co.nz/#!70hBEQZK!IpOGBNLLu4sfRBzygJw2J8vh0B3OLgaVto26S21rsHs
If you facing failed to connect server error then you also have to edit the host file in C:\windows\system32\drivers\etc\hosts
And add this line 127.0.0.1 csmg.lgmobile.com

bitdomo said:
After hiting the yellow arrow in lg flashtool you have to reconnect the phone.
Also you can try flashtool2014 https://mega.co.nz/#!Hlo22baS!zXV3VKRZzOI5EtO5MEAUzICC5kcx-a7xAGspZzhKMFs
You have to instal lgb2c before that https://mega.co.nz/#!70hBEQZK!IpOGBNLLu4sfRBzygJw2J8vh0B3OLgaVto26S21rsHs
If you facing failed to connect server error then you also have to edit the host file in C:\windows\system32\drivers\etc\hosts
And add this line 127.0.0.1 csmg.lgmobile.com
Click to expand...
Click to collapse
Reconnected - didn't change.
Yeah, I will try other flash tools.
P.S. any advice on Time Out error? Why it is happening and how to stop it?
EDIT: somehow doesn't open links.

Coolguy981 said:
Also keep in mind that in the program there it says MODEL, it keeps blank space. Should it be so? In couple of Youtube videos I noticed that other people's smartphones were detected...
Click to expand...
Click to collapse
For example here https://www.youtube.com/watch?v=trhIgKL2FlI it instantly shows P920 after selecting AP file, while mine's not. Maybe I got wrong drivers installed...

Coolguy981 said:
Reconnected - didn't change.
Yeah, I will try other flash tools.
P.S. any advice on Time Out error? Why it is happening and how to stop it?
Click to expand...
Click to collapse
I have no idea why you get timeout error. I got these kind of errors with my Optimus 2x but after several tries I got passed. I falshed baseband and the rom separately.

Coolguy981 said:
For example here https://www.youtube.com/watch?v=trhIgKL2FlI it instantly shows P920 after selecting AP file, while mine's not. Maybe I got wrong drivers installed...
Click to expand...
Click to collapse
that is matter of dll. I dont remember well, but I used the dll from an extracted kdz to make lgflashtool work with my optimus 2x p990

@Coolguy981
Friend, have you tried flashing a KDZ? It is a much more reliable way to flash your phone, especially after you have already run into problems. The LG Mobile Support Tool has changed a lot since I last used it but I'm sure it still has an emergency recovery function where you type-in your IMEI and the Tool recovers your phone to it's original factory state. After that, you can use the AIO tool to install a custom recovery, then root, then whatever you want...
Don't forget that this phone is unbrickable and if you ever run into serious problems, Xbsall's resurrection guide will bring your phone back to life.

dreccon said:
@Coolguy981
Friend, have you tried flashing a KDZ? It is a much more reliable way to flash your phone, especially after you have already run into problems. The LG Mobile Support Tool has changed a lot since I last used it but I'm sure it still has an emergency recovery function where you type-in your IMEI and the Tool recovers your phone to it's original factory state. After that, you can use the AIO tool to install a custom recovery, then root, then whatever you want...
Don't forget that this phone is unbrickable and if you ever run into serious problems, Xbsall's resurrection guide will bring your phone back to life.
Click to expand...
Click to collapse
Tried this http://forum.xda-developers.com/showthread.php?t=2191698 didn't work. I put in S/W mode and ran UpTestEX put kdz file in it and pressed Normal web upgrade test and Upgrade Test. Nothing happens. So instead I chose Start Upgrade. The program shows line: " Extract kdz file" and do nothing for whole minute and my phone shutdown (it does that always if in S/W more than a minute and doing nothing). The program crashes and says Don't send error. Losing my faith in resurrecting this phone :crying:

Coolguy981 said:
Tried this http://forum.xda-developers.com/showthread.php?t=2191698 didn't work. I put in S/W mode and ran UpTestEX put kdz file in it and pressed Normal web upgrade test and Upgrade Test. Nothing happens. So instead I chose Start Upgrade. The program shows line: " Extract kdz file" and do nothing for whole minute and my phone shutdown (it does that always if in S/W more than a minute and doing nothing). The program crashes and says Don't send error. Losing my faith in resurrecting this phone :crying:
Click to expand...
Click to collapse
You must have already installed LG B2C app on your PC. This is the official LG Mobile Update Tool.
- Just run that.
- Connect your phone in S/W Download mode.
- Look for Emergency Phone Recovery (or something like that) in the B2C tool.
- Type-in your IMEI when it asks you.
- Let it do it's job.

dreccon said:
You must have already installed LG B2C app on your PC. This is the official LG Mobile Update Tool.
- Just run that.
- Connect your phone in S/W Download mode.
- Look for Emergency Phone Recovery (or something like that) in the B2C tool.
- Type-in your IMEI when it asks you.
- Let it do it's job.
Click to expand...
Click to collapse
Yes, I have installed LGMobile Support Tool. I have only found Upgrade Recovery. When I select it, insert my IMEI but it says my phone is up to date.

I think I killed my brand new phone

I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.

Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David

DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.

In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck

If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting

viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?

If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.

whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date

Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem

whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.

whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work

whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?

viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.

whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse

So it sounds dumb but try rebooting your computer and switching USB ports then trying again.

whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port

[REQ] Unihertz Titan Stuck in Bootloop

Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif&notif_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!

DorkyDev said:
Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif&notif_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!
Click to expand...
Click to collapse
Are you needing help or you solved the bootloop?

I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.

DorkyDev said:
I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.
Click to expand...
Click to collapse
platform-tools-latest | drivers USB OEM | MTK USB driver
Obviusly you only need flash stock recovery.img as your device has A9.
For Custom Recovery like TWRP maybe I can ask my friend to help you. If - you still TWRP want?!

Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DorkyDev said:
Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.View attachment 5518101
Click to expand...
Click to collapse
Search in the internet How install MTK drivers, specially in the Win7. Better in Win10 and if you as that so the drivers [link] is much better, You can try installing that file but need reboot your computer. After try flash with SPFT.
Don't choose FORMAT+ALL or any option with FORMAT+........
Win7 need more effort to start drivers for Mediatek devices!
You can try pressing constantly the VOL - button when put USB for SPFT work.

The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.

DorkyDev said:
The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.
Click to expand...
Click to collapse
We often don't realize that certain errors are normal on our machine. So the question is to test in others computers.
But there are possibilities of company blocks or even something that has happened on the phone without it really should happen.
Some interesting cases:
1- I noticed with the image you showed about trying to flash all the firmware.
** So even if you have tried the Download only or Firmware Upgrade options, the question remains if you tried to flash only the recovery.img file? Obviously you can have the same error in SPFT?!
2- Cases of hardware vs software that match the use and characteristics found such as restarting the PC and trying to flash in a different USB port. Same problem?!: Drivers are resolved?!
The biggest case of suggesting something or thinking that this or that is a problem wastes precious time. Confirm the main steps!:
1- Driver correctly installed and working;
2- Driver works: Different USB PORT tested;
3- SPFT version must be tested. Mainly previous versions to confirm the error message that persists or may disappear;
4- Phone particularities: pressing the VOL buttons for a while can trigger the preloader that is responsible for the connection between the SPFT and your phone on the computer. Switching to VOL+ or Power or VOL- with VOL+ or VOL+ VOL - and Power may solve or confirm the non-solution.
Best way: Win10 with driver updates. Find the way to disable unsigned driver installations. But you can use this driver and you must restart your computer for it to take effect.
Make sure the USB port has a speed feature for the flashing process. Example: All USB ports are 2.0 only and SPFT asks for a USB 3.0 port to make the connection.
With everything confirmed the rest is something to question in relation to having the correct firmware file or the device itself having blocked the installation process due to a drastic change in the preloader or something that has changed and is blocking it.
Look previous posts about that so all depends on what you have and how you use it.
Unfortunately everyone (including me) who went through bad times like the one you have now, has a headache because it's a simple process and doesn't know what to do. But on the other hand, it's a huge learning experience when we solve it.
But there is still a choice without a headache: take it to a technical assistance and pay for it!

No on drivers when it goes to do the typical windows installation with the installation boxes in the upper left corner, I keep getting red x's.
I'm letting it charge some more and tomorrow trying again on my windows 7 laptop, as I think I'm also getting hung up on disabling driver signatures on windows 10 laptop. IDK if it's cause I'm dual booting JingOS 0.9 and that cancels out F7 or what the hang up is on that part.

In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.

shivadow said:
In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.
Click to expand...
Click to collapse
Would that also be done in SP Flash Tool or another software? I've also got these MTK tools.

Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.

DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.
Click to expand...
Click to collapse
If you have more drivers for others phones like samsumg, motorola, lg, etc so remove that's and reboot computer. Install again MTK Drivers, UAC permissions and reboot computer. Test SPFT.
But here a good video to see and may be can fix - confirm driver issue in Win7:
Drivers: https://drive.google.com/file/d/1V2FducGB4pNpbkJWVmk2sfRJpf4Q5Bth/view
DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
Click to expand...
Click to collapse
Maybe corrupted zip file?

Question Help: Black Screen after trying to flash stock ROM onto OnePlus 9 Global

Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.

MacroWolf said:
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
Click to expand...
Click to collapse
Update drivers on PC

For the Sahara error, open MSM Tool, click use lite firehose, and click Start. Then do the key combo to get the phone in EDL. When you plug it in, the software will already be preparing to connect to the phone and it should work. If it doesn't, try another port, another cable, etc. Sometimes it's temperamental but usually what's happening is that you're not plugging in and starting the process fast enough as it only stays in EDL mode for a few seconds waiting for a connection.

EtherealRemnant said:
For the Sahara error, open MSM Tool, click use lite firehose, and click Start. Then do the key combo to get the phone in EDL. When you plug it in, the software will already be preparing to connect to the phone and it should work. If it doesn't, try another port, another cable, etc. Sometimes it's temperamental but usually what's happening is that you're not plugging in and starting the process fast enough as it only stays in EDL mode for a few seconds waiting for a connection.
Click to expand...
Click to collapse
Thanks for the advice. Checking the "Use Lite Firehose" has progressed it a bit further. I'm still getting an issue where it's failing at "Param Preload" were it states the error is "Device not match image"
I'll keep looking to see if I can find some more information about this. Thanks for the help!

MacroWolf said:
Thanks for the advice. Checking the "Use Lite Firehose" has progressed it a bit further. I'm still getting an issue where it's failing at "Param Preload" were it states the error is "Device not match image"
I'll keep looking to see if I can find some more information about this. Thanks for the help!
Click to expand...
Click to collapse
Unfortunately when that happens things get a lot more complicated which is why I personally think we should not encourage people to try to flash with fastboot, it messes up more often than it works, and now the device isn't recognized by the MSM.
Go download the Indian 9 Pro MSM Tool and flash that. Then download the global 11.2.10.10 full update from the pinned post and flash that from the local upgrade menu to get a working phone. From there you can either unlock the bootloader and go to a custom ROM or you can continue on to flash the global OOS 12 update.

You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.

Qualcomm drivers.7z
drive.google.com

JonasHS said:
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Click to expand...
Click to collapse
The error OP has is because his device was corrupted by the fastboot flash attempt and the MSM Tool doesn't recognize it as a compatible model anymore. He needs to use the Indian 9 Pro MSM because it doesn't perform this check and then he has to local upgrade to the regular global OP9 software to get back to a stock state. I went through the same crap myself. Fastboot scripts cause more problems and people should just use the MSM Tool.

JonasHS said:
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Click to expand...
Click to collapse
This didn't work. I had these drivers installed and when I switched to the ones you provided it simply did the same thing.
EtherealRemnant said:
The error OP has is because his device was corrupted by the fastboot flash attempt and the MSM Tool doesn't recognize it as a compatible model anymore. He needs to use the Indian 9 Pro MSM because it doesn't perform this check and then he has to local upgrade to the regular global OP9 software to get back to a stock state. I went through the same crap myself. Fastboot scripts cause more problems and people should just use the MSM Tool.
Click to expand...
Click to collapse
Ok, I think I understand some of what I need to do.
1. Download the Indian version of the MSM Tools for the OnePlus 9 Pro?
--> https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
2. Run the MSM Tools with the same method you recommended in your initial post
3. Local upgrade to the global stock rom.
I'm not sure what you mean by local upgrade the ROM. Does this mean using the Global version of the MSM Tools to flash, using fastboot to flash, or will the phone recognize the region disconnect and recommend it update the ROM? Sorry about this. I very much appreciate your help.

MacroWolf said:
This didn't work. I had these drivers installed and when I switched to the ones you provided it simply did the same thing.
Ok, I think I understand some of what I need to do.
1. Download the Indian version of the MSM Tools for the OnePlus 9 Pro?
--> https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
2. Run the MSM Tools with the same method you recommended in your initial post
3. Local upgrade to the global stock rom.
I'm not sure what you mean by local upgrade the ROM. Does this mean using the Global version of the MSM Tools to flash, using fastboot to flash, or will the phone recognize the region disconnect and recommend it update the ROM? Sorry about this. I very much appreciate your help.
Click to expand...
Click to collapse
Local upgrade means download the zip and place in the root of the storage. Go to Settings --> System --> System Updates and then bring up the menu and there's a local upgrade option.
Download the full OTA zip from https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
I had problems with the zip file disappearing if I downloaded it on my desktop and copied it over directly so either download it on the phone, make sure it's got a zip extension, and move it to the root of storage or enable developer options as well as USB debugging, connect to PC, and adb push the zip to /sdcard/ which worked every time I tried it (I have had a hell of a time with this device and bricking and I have it down to a science now lol).

EtherealRemnant said:
Local upgrade means download the zip and place in the root of the storage. Go to Settings --> System --> System Updates and then bring up the menu and there's a local upgrade option.
Download the full OTA zip from https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
I had problems with the zip file disappearing if I downloaded it on my desktop and copied it over directly so either download it on the phone, make sure it's got a zip extension, and move it to the root of storage or enable developer options as well as USB debugging, connect to PC, and adb push the zip to /sdcard/ which worked every time I tried it (I have had a hell of a time with this device and bricking and I have it down to a science now lol).
Click to expand...
Click to collapse
Thanks for all the help. I am still running into an error with MSM Tools. I get the message "Unsupported Target O2"
Are there any good post I can use to read up on more of these error? The tool looks great, but trying to search references to each error has been less than fruitful.
Edit: Never mind. Apparently I needed to restart my computer cause it was looking to the incorrect target. It seems like it is currently working.

MacroWolf said:
Thanks for all the help. I am still running into an error with MSM Tools. I get the message "Unsupported Target O2"
Are there any good post I can use to read up on more of these error? The tool looks great, but trying to search references to each error has been less than fruitful.
Edit: Never mind. Apparently I needed to restart my computer cause it was looking to the incorrect target. It seems like it is currently working.
Click to expand...
Click to collapse
Did it work for you? It's strange that you got that error with the Indian 9 Pro MSM.

EtherealRemnant said:
Did it work for you? It's strange that you got that error with the Indian 9 Pro MSM.
Click to expand...
Click to collapse
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!

MacroWolf said:
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
Click to expand...
Click to collapse
Awesome, glad that you got it sorted.

MacroWolf said:
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
Click to expand...
Click to collapse
I'm having a similar issue. Black screen. I can get it to start the process in the MSM tool (after some trial and error) but it now tells me "Device not match image". I've downloaded the Global tool ( and my device is a OnePlus 9 5G LE2115). OnePlus wants me to send in the device. I'd rather not if I don't have to.

MacroWolf said:
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
Click to expand...
Click to collapse
It's from not restarting after installing drivers

EtherealRemnant said:
Awesome, glad that you got it sorted.
Click to expand...
Click to collapse
I've seen you around while searching for my issue with MSM tool. Can you help?
Backstory: My device (OP9) has no os and no recovery. I managed to get fastboot back after an incident and as far as I can tell, I have EDL mode. However, MSM tools I've tried all get stuck on "waiting for device" after plugging in
Here's a pic of what EDL looks like on Windows device manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does that look right?
Also as far as I can tell I have all the proper drivers. Windows seems to agree when trying to update them in device manager.
What is it I'm missing? Any advice would be amazing.

shadowofdeth said:
I've seen you around while searching for my issue with MSM tool. Can you help?
Backstory: My device (OP9) has no os and no recovery. I managed to get fastboot back after an incident and as far as I can tell, I have EDL mode. However, MSM tools I've tried all get stuck on "waiting for device" after plugging in
Here's a pic of what EDL looks like on Windows device manager:
View attachment 5634873
Does that look right?
What is it I'm missing? Any advice would be amazing.
Click to expand...
Click to collapse
Update the driver.
Unbrick OnePlus 9, 9 Pro Using EDL Firmware With MSM Download Tool
OnePlus has finally launched its OnePlus 8 series successor known as OnePlus 9 and 9 Pro with a much-upgraded camera, processor, display, refresh rate,
www.getdroidtips.com

Mate. Where were you the other day!
I'm actually embarrassed it was that easy. All day I've been on this. All. Day.
I swear I installed those drivers the first time as well. Windows confirmed everything was legit too but failed anyway.
Seriously thank you.

Glad that you got it fixed now. I have bricked my phone enough times messing with custom ROMs that I have the whole restoration process to a refined science at this point lol.