My kaiser bricked? - Tilt, TyTN II, MDA Vario III Android Development

I think my kaiser is bricked somehow. I left it sitting on my charger and came back and it was frozen and now when I turn it on nothing happens except the green light comes on. I can sometimes by messing around with the power plug and battery get it back into android but I cannot even bring up my bootloader anymore. I have no idea if its bricked or whats wrong with it.

Please define messing arround with power plug and battery . Did you try another battery? Battery contacts, miniusb contacts...worst case, something is burned inside. Camera+power+reset doesn't work?
Also, check what was your wife doing before you came back

lol she would never do anything to my phone. By playing with the power plug I mean just plugging it in and taking it out and what not. It's really hard to define it, I would just say ****ing with it lol.

I've come to the conclusion that the radio in my tilt died. Why must my phones always die from a dead radio =( android still works but I can't get into the bootloader anymore and I can't flash a new kernel or even reinstall. Will be nice to see how long this lasts lmao

Can you dump your kaiser to see what is left in our rom?
Follow this procedure to dump your kaiser:
First you have to install QPST (http://www.megaupload.com/?d=OW3ERRNB)
1. Turn on kaiser , now you enter the OEMSBL. You will see nothing on your phone!
2. Your computer will ask drivers for a device if you didn't installed the MotoQ drivers before. Point it to the extracted drivers!
3. If QPST is installed on your computer, disable the com port in the QPST Configurator.
4. Launch mtty and select your com port that is listed as Qualcomm Dignostic Interface 6000 (Comx) in the device manager.
5. Type "h" <Return>
6. if you got any output continue to 7 else pull out the battery, reinsert it and restart at 1
7. type "radata 90000000 1" : Your kaiser is now in loading mode.
8. Close mtty
9. launch the QPST configurator and add the comport and ENABLE it.
10. remove the usb cable of the phone, and reinsert it.
11. your phone must now be listed as Q/QCP-xxx (download)
12. Launch the "QPST Memory Debug" tool to dump smi.bin and ebi.bin
13. Click on browse to select the right com port
14. Click on "Get Regions"
15. Click on "saveto..." to save the files to a directory
16. Zip the files and send it to me.

massivekid said:
Can you dump your kaiser to see what is left in our rom?
Follow this procedure to dump your kaiser:
First you have to install QPST (http://www.megaupload.com/?d=OW3ERRNB)
1. Turn on kaiser , now you enter the OEMSBL. You will see nothing on your phone!
2. Your computer will ask drivers for a device if you didn't installed the MotoQ drivers before. Point it to the extracted drivers!
3. If QPST is installed on your computer, disable the com port in the QPST Configurator.
4. Launch mtty and select your com port that is listed as Qualcomm Dignostic Interface 6000 (Comx) in the device manager.
5. Type "h" <Return>
6. if you got any output continue to 7 else pull out the battery, reinsert it and restart at 1
7. type "radata 90000000 1" : Your kaiser is now in loading mode.
8. Close mtty
9. launch the QPST configurator and add the comport and ENABLE it.
10. remove the usb cable of the phone, and reinsert it.
11. your phone must now be listed as Q/QCP-xxx (download)
12. Launch the "QPST Memory Debug" tool to dump smi.bin and ebi.bin
13. Click on browse to select the right com port
14. Click on "Get Regions"
15. Click on "saveto..." to save the files to a directory
16. Zip the files and send it to me.
Click to expand...
Click to collapse
Would be nice if my kaiser was detecting still... It's weird. It's almost like it has no boot loader but yet it will still sorta boot android.

If the Green led comes on, you are in the OEMSBL. Does your computer asks for drivers when you connect your kaiser to your computer? Ifso, you need the MotoQ drivers (found in this forum) to connect your kaiser OEMSBL to your computer. Then you can use MTTY to talk with it. (if you type something you will not see any output. Only after presing enter/return.
If you need help, let me know.

I've used mtty before. The green led DOES come on but it does not detet at all on my computer. It is not asking for any drivers. When I plug it in nothing happens

then it goes further then the oemsbl.
If it boots Android, it must pass the SPL, so did you try to hold the camera button and then turn on your device? If the SPL tricolor shows, then you can flash. (in theory)

massivekid said:
then it goes further then the oemsbl.
If it boots Android, it must pass the SPL, so did you try to hold the camera button and then turn on your device? If the SPL tricolor shows, then you can flash. (in theory)
Click to expand...
Click to collapse
I've tried to get into the tricolor screen but it is not working with camera + Power and battery insert or on Camera+power+soft reset. I used to have an HTC screen I added display before the kernel loaded. Now the first thing I see is my loading screen for android around a minute or so later only when it's plugged into power.

That's strange. And what is happening when you press the green phone key and powerup? (OEMSBL boot) keep pressing the green button for 5 secs If the green led comes on. Then connect your phone to your computer. Does it appear in the windows device manager?

Does not detect in device manager at all, not even as an unknown device. It's as if nothing was plugged in

If it is not listed as a serial port device. (ports Com & LPT)
then it is not in the OEMSBL. Is your device Security unlocked? If not this can explain why it doesn't enter the OEMSBL with the green button.
Did you also try to put an upgrade file (KAISIMG.NBH) on your root of the SD card?
Maybe this will get launched when your device is turned on?

massivekid said:
If it is not listed as a serial port device. (ports Com & LPT)
then it is not in the OEMSBL. Is your device Security unlocked? If not this can explain why it doesn't enter the OEMSBL with the green button.
Did you also try to put an upgrade file (KAISIMG.NBH) on your root of the SD card?
Maybe this will get launched when your device is turned on?
Click to expand...
Click to collapse
I'll try that out as i've always flashed via usb. Also it is Security unlocked and it is SIM unlocked too.

Nope that did not do a thing. I took a WM rom nbh renamed it to KAISIMG and set it on the root of the SD and it did nothing.

Oh yes, you are right.
in order to load the KAISIMG.NBH, you have to enter the SPL.
hold Camera button and power on. wait 2 secs and unpress the camera button. Then wait for 1 minute, and press the power button again (Power button = start flashing, action key = cancel).

just tried that and still nothing out of my phone

massivekid, i have very similar problem, but my phone turned on.
I dont can turn on bootloader , i try very much metods and any working.
my phone always turn on Smart Mobility i can't change android kernel/back to the windows
few times i tun my pda on blinking yellow led, but computer no see the device

but it still boots into android?
then a jumpspl for android would cure it ;-)

Can you try this one?:
- Remove USB cable/cradle
- Remove battery and re-insert it
- Hold Camera and insert the USB cable.
What do you see now?
The reason why i ask this, is that you have told me that it boots android when you insert the power/usb cable and you see output after 1 min or so when booting android. This behaviour was added to android to let the battery charge...
So the poweron procedure difference from when you press the power button, or when you let the kaiser charge...

Related

Diamond not conecting

I want to upgrade rom on may diamond but when conect the phone to my conputer the phone it just starts to charge. The computer does not detect him and I have activated usb conection on the phone.
I am using a standard miniusb cable used also for canon fotcamera, Nokia N95, motorola V3 (v360 L6, L7 etc.)
I did instaled Activesync on my computer but still no result.
You did no say which Win OS you are using - If Vista then you do not need activesync (AS) but windows mobile device centre or any other Win OS Before Vista then AS is what you need. AS needs to be installed before you connect your phone to the PC.
Have you restarted your PC first before install - this also helps sometimes
Try this....
Start>Settings>Connections>USB to PC and here ....uncheck the box Enable advanced network functionality
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
R3PUBL1K said:
You did no say which Win OS you are using - If Vista then you do not need activesync (AS) but windows mobile device centre or any other Win OS Before Vista then AS is what you need. AS needs to be installed before you connect your phone to the PC.
Have you restarted your PC first before install - this also helps sometimes
Click to expand...
Click to collapse
I am using Win XP SP2 and I have tried every thing that you said but nothing.
band27 said:
Try this....
Start>Settings>Connections>USB to PC and here ....uncheck the box Enable advanced network functionality
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
Click to expand...
Click to collapse
I did uncheck that box but without any results so now I will try internal method. But I'll have to send the file to the phone via bluetooth and see if it works.
band27 said:
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
Click to expand...
Click to collapse
How much is it supose to take "Internal method"?
After pressing Vol_Down + Back button it showed the three color screen then it changed to a white screen with loading on it and it stays like that (after pressing Vol_Down + Back button I didn't press nothing else).
The Internal Method shouldn't take you any longer then 2 min. or so.
Once you have started the flashing to begin in the Grey menu....it will eventually say OK...OK
and yes
at this stage you soft reset and press vol down and centre round button.
Grey menu then gives you a choice to reset back to manufactures settings which is what you want (vol UP)......this should take an additions 2 min. if that.
band27 said:
The Internal Method shouldn't take you any longer then 2 min. or so.
Once you have started the flashing to begin in the Grey menu....it will eventually say OK...OK
and yes
at this stage you soft reset and press vol down and centre round button.
Grey menu then gives you a choice to reset back to manufactures settings which is what you want (vol UP)......this should take an additions 2 min. if that.
Click to expand...
Click to collapse
I have tried everything that you said and nothing.
The only diference is that now when I conect the cable to the phone it asks me witch mode to conect it (Activesync or storage), but the computer still doesn't see's it.
Tried another USB-cable?
chribruu said:
Tried another USB-cable?
Click to expand...
Click to collapse
I tried with 3 diferent cables.
Have you tried putting your device into bootload mode (soft reset & vol. down) and the connecting to your pc. The bottom of your coloured screen should switch from serial to usb....If this switches to USB then you are good to go with downloading what ever Rom using the RUU_
Keep me posted...
band27 said:
Have you tried putting your device into bootload mode (soft reset & vol. down) and the connecting to your pc. The bottom of your coloured screen should switch from serial to usb....If this switches to USB then you are good to go with downloading what ever Rom using the RUU_
Keep me posted...
Click to expand...
Click to collapse
It doesn't switch's to usb it only shows "serial". If I put it into bootmode while it is conected to USB it shows nothing, not "USB" or "Serial" it's blank.
I am begining to belive that there is a hardware problem in my phone.
Do you have .NET framework installed on your PC! if not, get it from http://www.microsoft.com/downloads/d...DisplayLang=en

How to flash if activesync won't work

I can't get my Diamond to talk to activesync on two machines (one of which it used to be fine with). Given that, is it possible to flash it? What's the procedure?
Kallisti said:
I can't get my Diamond to talk to activesync on two machines (one of which it used to be fine with). Given that, is it possible to flash it? What's the procedure?
Click to expand...
Click to collapse
look in my sig
...
enter bootloader and plugin to pc. and pray it got detected as mobile device in device manager. if it does, run ruu.
if not, here's a work around.... turn on phone. go to setting > connection > usb to pc > and change to connect as storage device.
plugin to pc and copy .nbh file of your choice to internal storage (rename .nbh file to diamimg.nbh) (which will be most likely detected as a usb drive)
use stylus and reset phone. hold vol down and back button.... you'll be in bootloader and soon a screen will pop up "triggering movinand bla bla bla..."
press power button to start flashing. when done, use stylus to reset again, now press vol down and circle.
hard reset device > press vol up to continue.
wait for device to self customize.
by the way, this might not work.
Brilliant - updating it now. Thanks guys

Firmware Update freezes

Morning, im following this guide - http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 and am on the section --
=====
6.) Well that was easy , let's continue (Now that we have the files on our device we want to put our device is download mode)
(Note this method may vary from device to device)
Power off your device
When the device is powered off, hold volume up and insert a USB cable connected to the PC
Wait for the drivers to install
=====
But it just sits there on 0% telling me to not remove the the usb, it never moves. If i remove the cable i have to remove the battery to restart it and then it boots like normal. Tried 3 times now and have the same issue.
Do i just keep trying? Am i missing something?
Thanks in advance for your help.

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.

Question Oneplus 9 pro bricked, impossible to get to EDL

Hey all,
So i've unlocked by bootloader, flashed a custom recovery to then proceed with LineageOS flashing. However it went completely wrong as on reboot i'm stuck with the bootloader unlocked warning and then a blackscreen.
I still have access to fastboot mode however it's impossible to flash a customer recovery ("No Such Partition") and also impossible to directly "fastboot boot recovery.img" as the phone simply reboots on the warning and then blackscreen.
The only solution seems to get the device to qualcomm EDL mode and reflash all with the MSM tool (which I have as well as all the drivers) however I cannot get my Oneplus 9 pro to EDL mode...
I've tried all the fastboot commands (fastboot oem EDL, fastboot reboot EDL, none of them work) as well as the combination volume UP + volume DOWN + plugging the cable (it just boots the fastboot mode.
Honestly would greatly appreciate any help as it is the first time in a decade I hard bricked a phone like this as it seems all the partitions are broken.
Make sure you have it unplugged when you do the button combos, as it will just start to boot while it's plugged in. Also, if you can reach fastboot, you can almost definitely reach EDL. Try unplugging and holding power+vol up for a bit which forces it to completely power off. Then try getting into EDL through the normal button combo/plugging. This is what I had to do since once it got into the booting/no-booting cycle I couldn't get to EDL.
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Good advice above.
Last time I couldn't reach EDL with my previous phone, it turned out to be an issue with the drivers I had installed. I uninstalled all Android-related drivers including some generic thing that showed up in device manager when plugging in the phone, then reinstalled the latest Qualcomm drivers.
Also possibly try a different USB cable if you have one. My OP9P didn't show up when the cable it came with was plugged into my USB-C port for some reason, but it worked fine with a generic Type-A to C cable I had sitting around.
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Tornadeur said:
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Click to expand...
Click to collapse
I can fix it bro pm me telegram .. @Hunar71
Hunar999 said:
I can fix it bro pm me telegram .. @Hunar71
Click to expand...
Click to collapse
Can you help me too, I have exactly the same problem…
If you use Windows, you need to see "QDLOADER 9008" in Device Manager > Portable Devices.
When you got this it will work, 100% .
It worked for me a few days ago. My laptop runs on Windows 11 x64. And only have usb 3.0. NO usb 2.0.
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Alberhasky said:
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Click to expand...
Click to collapse
Yeah make sure it's exactly the same name of that driver - worked for me on oneplus 9
If you have access to fastboot still. Try switching slots. Then going into EDL
For anyone looking for help, please DM me.
djsubterrain said:
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Click to expand...
Click to collapse
Thanks a lot man. Saved my Day. First 9Pro successfully restored ;-) Thank you and merry Christmas to all.
Guys I do not need to use the MSM Tool Anywhere until I reach the step where my device is being successfully detected as "QDLOADER 9008" in my windows device manager correct?
Or does the MSM Application need to be running when I reboot to EDL mode?
I am following this guide.
Please help
I always have phone powered off, and while holding both volume keys I plug it into USB cord(that is already plugged to pc) and then click on enum(button in msm screen) until it says connected then hurry and click start. Once it starts I can let go of volume keys.. Also more than likely u will need to click the box to "use lite firehose" or "Sahara communicaion" will keep failing.
make sure you have oneplus 9 pro drivers and " qaulcomm incorporated - Ports" Driver) and ("qaulcomm communications inc-Net" Driver) so your phone in edl which will be already most likely be running before you plug it in. just hold down both volume buttons and plug in to the usb port to your pc and release once plugged in and start the msm tool and hit enum it should say connect provided that you have all the necessary drivers above so the pc usb port will be able to communicate/recognize you device. its never usually A 1 and done type of thing. everytime i brick my phone its always the 100th try before i get a com port connected and the software communicating successfully, so just be patient and take your time. you will get it back up and running,
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
can't get into edl mode
how can I get oneplus 9 pro into edl mode while it's refusing to turn off? keep in mind that I can't use adb. but was able get fastboot devices command to work and I did not use any third party roms, didn't unlock the bootloader, and do not have...
forum.xda-developers.com
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
Well you have a corrupted boot.img or you would not be trying to edl. Also you probably are holding down multiple buttons to power off to your phone and your either not remembering or forgot that these combination of buttons are booting you into other modes fastboot, recovery or system.

Categories

Resources