[Q] Oh my. SBF failed. Am I out of luck? !Resolved! - Droid 2 Global General

I have (er, HAD) a rooted stock droid 2 global. I read copious amounts of info to guarantee that my move from a blur-laden rom to a considerably-blur-LESS rom (Hexen) would go as pain free as possible. I printed out all the rsdlite info I could find, located all the appropriate files and drivers, found a good, md5 verified stock sbf, and prepared to make my phone better.
Step-by-step I re-read the instructions until I thought I had it right. I started, and waited for the final step "phone[0000]: phone is being rebooted."
It never came. I did everything right and it ended with rsdlite's status on the phone reading :"failed flashing process. phone [0000]: error switching phone to bp pass through mode (0x70bE); phone disconnected," and my pc giving me a "found new hardware: flash mdm6600" message. I am not able to find a driver for the mysterious new device that crops up as my phone is trying to reboot.
My phone sits unperturbed, still reading "SW Update in progress..." If I try to shut it off, it doesn't respond. And when I battery-pull and put the battery back in, it starts up immediately with a "Bootloader D0.11 Code corrupt..." message.
I cannot make it go into bootloader mode. All it does it what I've told you.
So, you tell me, please, am I screwed? Am I the proud owner of a 3-month old brick?
Dan

resolution
My phone is back.
Half the reason (okay 9/10ths) I posted was because I thought my phone was finished. I had searched thru here and the web many times during each SBF re-attempt, and I seriously think there were at least a dozens tries minimum.
No documentation was found for my issue: Bootloader D0.11
On my last search I found a set of Motorola USB drivers that were a newer version than what I had found every other time. They made the difference. The drivers that *worked* were V4.7.2.0. The previous drivers were 4.6.5.
I hope this helps...
Dan

What did you do to get out of the bootloader D0.11 screen?

Well, like I've said, all I did was use a different set of Motorola USB drivers. The drivers made the phone be recognized by the PC during the RSDlite process.
These are the drivers I used: Motorola_Driver_Installer_v4.7.2.0.msi.zip
All I did was RSD *again* exactly as I had been doing.
The only differences are that the whole process begins with the bootloader error message being displayed on the phone. RSDlite will recognize the phone when it gets to that part of the process. And when you get to the "switching the phone into BP mode" message and the simultaneous PC message "found new hardware: flash mdm6600" the pc message appears *very briefly* (presumably because *now* it has MDM6600 drivers) and the RSD process continues, exactly as it was supposed to.
I hope I've answered your question clearly. And I hope this helps you with your D0.11 error.
Just so that you know, I am *no* expert by any means when it comes to this stuff. I'm just like you: looking for answers.
Good luck,
Dan

Thanks for the help. After two hours last of searching and downloading last night, I finally got my wife's droid restored.

Related

error 112 -- please help

can somebody help me update my t-Mobile XDA? i messed up my phone once already and know i keep getting error 112 during first step in update. CE Erase fails according to the log. Something is clearly locked, but I don't know what i am doing wrong or forgetting. I don't think t-mobile will restore my phone a second time. please help. I have tried diamondv1.2, wm2005, wm2003se, nothing seems to work.
UPDATE: sorry wrong categorie
not sure if that last big is a signature or a real confusement if so then
you cant use rom from one device on another so i would make pretty damm sure which device i had before trying to flash in worst case you can ruin the device 100%
i checked the requirements, so that should be ok. i just keep getting that same error 112, like something is locked. i haven't been able to find out what the error means. any tips?
and the update software i used checks if the device is right...
perhaps some more details:
if i connect it to my charger it will say serial, unless i pull the plug out a bit, then it will say usb.
if i connect to my pc via usb it will say usb v1.00, but after a while this will disappear and the RED light will go on
I have tried flashing it, but since activesync does not see it as a pocketpc anymore, i can't flash.
i have read a 100 posts by now, but i have not found any solutions.

USB not working after flashing Damage Control

So let me start by saying I have been researching these forums for the last 8 hours trying to following instructions on getting my phone to connect to my computer and with no luck, hoping someone out there can please help me step by step in correcting my problem.
1)I flashed DC's Rom, then flashed the most current radio, then flashed the most current Wimax.
2)I noticed that when I connect my phone to the computer, it says device is not recognizable. The phone charges but does cannot be seen by the computer as a disk drive (I'm trying to RUU to stock but the comp. will not see my phone and I've already tried running RUU but it also is having probs seeing the phone).
3)I've read Calculin's instructions in fixing the SD Card and USB as close as possible but also no luck. I've downloaded Android-SDK Tools and ran CMD with the Instructions saying type in "fastboot oem boot", from there, thats where I get stuck, it just says "waiting on device". Not sure where I go from there, I'm in Reboot mode where it has Fastboot on my evo screen.
Any help would be much appreciated, I'm just so frustrated and I'm trying to get back to square one.
Unplug your phone and restart it, then plug it back in. I had to do this 3 times before it started working again. Other than that, you might just need to download the new drivers.
And you posted in the wrong section.
Sorry about posting in the wrong section, what drivers should I install, are you talking about the new HTC Sync Files or something else? Can you point in the direction to get these files?
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
faquedado said:
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
Click to expand...
Click to collapse
You should be able to get the proper drivers from either Sprint or HTC's web site. There are links on both sites. Also, when you install / reinstall the sync drivers make sure anti-virus is disabled. If the situation continues and you've tried everything else other folks suggested look at program permissions in your anti-virus program. I was having something similar and CA anti-virus was not letting the program start-up. I had to toggle it to "allow".
Good Luck.

“Firmware upgrade encountered an issue” when using Heimdall

Howdy folks!
I am working my way through a minor (?) technical difficulty.
Would appeciate any suggestions you folks can off this newbie along the way.
Earlier today, I made an absent-minded mistake. Tried to go to my stock Froyo kernel without undoing my voodoo/lagfix/ext/watchamacallit setup. Whoops. Bootloop. No recovery mode available.
So, I attempted to use the procedure described in [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3 here:
http://forum.xda-developers.com/showthread.php?t=1524081
I’m in Windows 7.
I right-clicked on the Heimdall one-click program (Stock_SGH_I997_UCLB3_Repartition-One-Click), but there was no option to run as administrator. So I just double clicked it and it opened it (deviated from instructions on the first step...oh oh).
With the Heimdall one-click program now open, I put my phone in download mode and it indicated connected (perhaps in retrospect I connected too early)
I followed instruction on the PC program to install drivers, which it did (I already had Samsung drivers installed that I used successfully for SOC root program and for EFS Pro, I’m not sure what it was installing).
The pc program told me it needed to reboot. The phone screen said something about “dont’t shut off...”. I wasn’t sure what to do at that point, so I granted the pc permission to reboot.
PC rebooted, phone remains attached the whole time
Upon reboot, the Heimdall one-click program did not start up again.
So I double-clicked it and started it again.
The phone remained attached, but was not recognized as connected by the pc one-click program.
So I pushed 3 buttons on the phone to get it to turn off, then removed the batteries.
.
Then started pc Heimdal one-click program again. Then put my phone in download mode which it did successfully.
Then ran the flash and go the message “The FACTORYFS upload failed!”
(This occurred run without the checkbox about bootloaders)
At that point I checked the checkbox about bootloaders, and it came up with some scarey warning so I didn’t flash (probably should have).
I once again deenergized the phone (three-buttons, remove battery during the brief period it’s deenergized). Shut down pc heimdall one-click program.
Then started pc heimdall program.
Tried to put phone into download mode and received the following inauspicous message:
“Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again”
Deenergized phone again. Shutdown pc program. Powered PC off. Restarted pc. Restarted Heimdall one click.
Tried to put the phone in download mode again and got the same error message.
I don’t know anything about selcting recover mode, not sure how to follow that instruction (any ideas?).
What I did next was search for the error message. It apparently has not been reported in the Infuse section, but I found two threads with this message discussed in the Galaxy S2 section.
“help” is the title of the first
http://forum.xda-developers.com/showthread.php?t=1189473
“Firmare upgrade encountered an issue - Am i done for?” is the title of the 2nd:
http://forum.xda-developers.com/showthread.php?t=1386232
There may be some more out there...
What I gathered was that I needed to remove my drivers.
I did remove the Sansung USG drivers in my control panel. I think these are the one’s I already had installed prior to me SOC root.
Rebooted.
Reinstalled drivers (filename SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Restarted Heimdall one-click.
Put phone in download mode.
The same error message indicating that my phone has “issues”
Uninstalled my Samsung USB driver again.
Went back and looked at my control panel, there is another program. Keis. Uninstalled that. Rebooted.
Reinstalled SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver
Reinstalled Kies_Mini_For_Captivate_11011_4.exe
Rebooted
Started the Heimdall one-click program.
Put phone in download.
Get the same error message on the phone (firmware upgraded encountered an issue...).
PC at this time thinks the phone is “connected”. So I clicked flash.
It proceeds to the next screen for driver installation.
I selected options / all / Samsung usb / Replace
PC Error message: Driver installation failed.
From those other threads, I’m pretty sure if I get my drivers straightened out I’ll be all right.
I don't know what I did wrong with the drivers... if anyone has a link with concise instructions for uninstalling/reinstalling the required drivers, maybe that would help me see if I've done something wrong.
Any other suggestions?
My java version is Version 6 Update 25
I have made a couple of change to this, a post I did for someone else today. You have done an excellent job of trying to resolve this- I hope this will be helpful.
There are a couple of things to point out:
Get Kies off your computer - it is a source of problems. Also means delete from recycle bin if there.
Download the Infuse drivers from bigjoe's ISET here: http://d-h.st/sKF
Thanks to bigjoe for an amazing page of resources !!
Be sure you have the latest version of Java here: http://www.java.com/en/download/index.jsp
Follow qkster's instructions he provides here:http://forum.xda-developers.com/showthread.php?t=1524081
Post 1 gets you back to stock- Post 2 gets root back.
Big thanks to qkster for doing this - saved many phones for countless number of users !! Me alone over a million times and counting
A video- no academy award nomination, but can be helpful : http://www.youtube.com/watch?v=sHyY7WHx4zc
Video is returning to Gingerbread.
You are willing to learn - therefore there will be many who are willing to help.
Take your time- do it right once and it will be easy next time !!
Heimdall uses it's own driver.
Once you install heimdall on one USB port of your pc, reserve that 1 port for going back. Also good to use that same USB cord.
The first part where it failed was because of bad connection. You just needed to change USB cord or change the port.
Read the heimdall thread and the how to thread a few times...
You could also use the froyo heimdall i put together for ucke3..see my sig link
Thanks very much for the replies.
Updated java.
Uninstalled Kies and Samsung driver (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Rebooted.
Reinstalled Samsung driver from bigjoe's link (same file).
I think it asked me to reboot.
Started the PC Heimdall program.
Attempted to put phone in download mode, it says "Firmware upgrade encountered an issue....".
So phone is not recognizing PC.
But PC recognizes the phone as connected.
Press flash. It goes to next page... I list all drivers, there is nothing Samsung in there.
Disconnected phone. Shut down program. Removed drivers/rebooted / reinstalled Samsung driver
Started Heimdall.
Attempted download mode, same error message "Firmware upgrade encountered an issue..."
Tried flash anyway, the next screen list of devices still has no Samsung.
Oddly when I go back to the first pc screen and try plug/unplug the phone, the PC recognizes phone as connected/disconnected. But it doesn't recognize it on the 2nd page where it tries to install the driver. And the phone has never successfully entered download mode since the first one or two tries...I get this "Firmware upgrade encountered an issue with yellow triangle screen every time since.
All above was on a single USB. I then tried on two other USB's same result. I may try another PC tomorrow night after work.
And will review the qkster's thread again as well as the video link posted by Pony Express.
Will report those results...
For now my head hurts . Time to call it a day.
Thanks for all your help.
I definitely appreciate it.
post deleted by op
meaning of this error message?
deleted
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
For the moment don't check the bootloaders. You will only need them for ICS and JB to get rid of rainbows in the recovery. A bootloader flash is practically the only thing that can brick our phone.
Is that "firmware upgrade.." screen the one with the pc!phone? It has been a long time since I soft bricked so I don't recall if it said that somewhere.
If heimdall is giving you issues, try Odin and see how it goes there.
Sent from my sweet & buttery Infuse
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
Yes...that's represents download mode...just another form...heimdall should still work
Sent from my SGH-I997 using Tapatalk 2
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
qkster wrote:
Heimdall uses it's own driver.
Click to expand...
Click to collapse
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
qkster's how to:
2. If you have not used Heimdall, you will need to set up the driver for device recognition
Click to expand...
Click to collapse
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
qkster's how to:
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked.
Click to expand...
Click to collapse
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
qkster's how to
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
Click to expand...
Click to collapse
I'm a little nervous about turning off my security program (a/v, firewall etc) since I haven't done that in years.
Have there been problems attributed to doing this with security enabled, or is it just a general suggestion to avoid interruptions from unexpected scans or pop-ups etc? (my security runs peacefully in background and never interrupts me unless I ask it)
If it's really necessary to disable security program, I'd feel better about keeping my internet disconnected for the duration that the anti-virus is off. Is there any problem created if the internet connection remains disconnected for the duration of this process?
electricpete1 said:
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
Click to expand...
Click to collapse
Drivers: when you launch heimdall it will install its own custom drivers for whatever usb port its pluged into...so if you plug it into one of your ports in the front and run heimdal only the port the phone is currently plugged into will be effected by the new driver. the driver is only used when in download mode...so dont uninstall your current drivers
selecting device: i think you got it (if my memory is correct...) just launch and run heimdall with device connected in dl mode...when you get to installing drivers just go to options and choose list all...i cant remember the exact name the infuse shows up as though
Bootloaders: just flash the first time without it checked...if it doesnt go through then check it and flash again
Antivirus: i have never turned off my anti virus when using heimdall on any of my computers (one computer uses norton 360 premier, the other one uses avast free) i never had it conflict with the process...so just leave it on for now...and only turn it off if you are having problems...if your worried about viruses then disconnect from the internet when you turn off your anti virus -i dont think the heimdall relies on internet at all...well maybe for the drivers...so just dont turn anything off until after you get the drivers
EDIT: i have a frseh install of windows 7 on my dev computer that i havent used heimdal on yet...so ill run it and clarify the driver section...i dual boot both linux and windows...currently im near the end of a repo sync so as soon as that finishes ill boot into windows and run heimdal...in less then a half hour hopefully...
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases but one, the anti-virus/firewall was on and pc connected to internet
In one case I tried with anti-virus off and pc diconnected from internet.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall, it takes me to the first Heimdall screen, which shows "device status" red/disconnected as expected.
I try to put phone in download. Get the error message screen on the phone (see subject line). The "device status" shown on the pc changes from red/disconnected to green/connected (as expected).
I Click flash.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
Device status still shows green/connected on the first Heimdall screen.
If I press flash again, the experience at the second screen repeats without showing Samsung driver.
Before I go to the next configuration (next usb port or cord or whatever), I remove the phone and close out the Heimdall program.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). Does this change fact change your suggestion about checking the flash bootloaders box?
electricpete1 said:
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall.
Try to put phone in download. Get the error message screen.
Click flash in the first Heimdall screen.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it.
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). In this circumstance, do you still think it’s ok to check bootloaders?
Click to expand...
Click to collapse
you should probably wait until you get the heimdal drivers installed...im still wating for my reposync to finish...for some reason the download slowed down to 200kb/s,,,so it could take a while...
but for the drivers do this
1) On the menu bar (Device,Options,Help) Click Options --> List All Devices
2) Under USB Device select “Samsung USB Composite Device”
if its not locating it then try differnt ports/cables...if still no then run as admin...rightclick or shift+rightclick...if still not showing up...maybe bad usb port on the phone?
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that... tomorrow. Right now, my pillow awaits.
electricpete1 said:
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that when I get a chance.
Click to expand...
Click to collapse
Did you try holding shift while right clicking?
Sent from my SGH-I997 using Tapatalk 2
electricpete1 said:
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
Click to expand...
Click to collapse
Thanks for pointing out the imprecise grammar, Pete.
I corrected the op.
Recheck step 6 and 7.
To get heimdall to install its drivers, Zadig, you need the initial Samsung Android drivers. so when you pull down the zadig menu, Samsung Adroid device should show up.
Then reboot the PC.
Then try connect in dl mode again.
You had it at some point...
Thanks all.
That is now very clear qkster. (Actually it was reasonably clear before and I was pretty sure I knew what you meant, but just wanted to double check in case I was misunderstanding something)
I've had some trouble running as administrator, apparenlty others don't
Here's my difficulties and how I resolved it (I think):
DIFFICULTIES IN RUN-AS-ADMINISTRATOR.
If I right-click on an executable file (anything.exe), I get option to run as administrator. Great.
If I right click on a jar file (like the one I'm trying to run), no such option. Sad.
Same thing with short-cuts.
If I right-click on shortcut to exe, I can choose compatibility tab and select run as administrator. Great.
If I right-click on shortcut to jar, there is no compatibility tab. Sad.
HOW I RESOLVED RUN-AS-ADMINISTRATOR (I think)
I found some instructions for specifically for running jar as administrator here:
http://stackoverflow.com/questions/...r-with-administrators-privileges-on-windows-7
Specifically, click start, type cmd in the window just above start, right-click on the cmd result, and click "run as administrator.
That takes you to an elevated command prompt with the word administrator in the window heading.
Navigate to the directory and type
java -jar myfile.jar
where myfile is your file name (I renamed it to shorter name to make it easier).
RESULT:
I was able to launch Heimdal from the elevated command prompt.
Unfortunately, results have been the same thus far when using Heimdall launched from elevated command prompt as the previously reported results.
QUESTION: is there any way to check the program truly has admin priveleges?... it didn't ask any permission when launching Heimdall from the elevated command prompt.. the only permission asked was when launched cmd from the windows start menu screen.
I will repeat a few of yesterdays trials.
If those are unsuccessful, I think next step is trying GTG's package with ODIN.
QUESTION: Is there any way to clear any settings loaded into the USB ports by the Heimdall so they don't interfere with ODIN?
For Odin, just install the drivers you see at the iset page or kies drivers.
If you had a pc, one user when you log on, it is auto assume admin.
You can also go to control panel, users, look at privileges

Question OP9 Hard Bricked, cannot enter EDL mode because Windows won't properly recognize device, please help

I followed this tutorial. Qualcomm drivers worked briefly for detecting my device initially. I unplugged, opened up the MSM tool and went to plug the phone back in to begin the process, no luck. Now when I check device drivers it shows this error (Device Descriptor Request Failed). Does anyone have any experience with how to fix, its driving me nuts.
lukebukowiec said:
I followed this tutorial. Qualcomm drivers worked briefly for detecting my device initially. I unplugged, opened up the MSM tool and went to plug the phone back in to begin the process, no luck. Now when I check device drivers it shows this error (Device Descriptor Request Failed). Does anyone have any experience with how to fix, its driving me nuts.
Click to expand...
Click to collapse
Keep at it.
I spent two days unbricking a 7T when it happened. Take 2/3 tutorials and see that every condition is met. Don't forget to look for the proper Qualcomm pilots, you might need to update them manually. (If I didn't know any better I'd say that your problem here)
The drivers you're looking for are named QDLoader something.
I know it should work because I did it on the One plus 9 if my memory serves me right, you just need to follow through and make sure that you also have the right MSM tool.
Pay attention to small details like the phone might be crashing on the start you should restart accordingly, or maybe you're not pressing the right volume button (was it up + power? I don't remember) and see what your computer sees plugged in.
Use more than one USB cable just in case but seems unlikely.
I followed this procedure since the one you referenced the google docs link would never download for me: https://www.droidwin.com/unbrick-oneplus-9-pro-msm-download-tool/
I had to use the alternate method to get to EDL mode in that tutorial since the normal one did not work. I also had to uncheck the box that said something about SHA256 before it would say Waiting.

Stuck in EDL mode. Tried everything. Any insight would be appreciated :)

Hi,
I f'd up when trying to install the pixel experience and chose the wrong rom. When I flashed it the phone went into EDL mode. The PC now recognizes it as Qualcomm.
I have found the correct ROM and tried to install it using several versions of MiFlash and QFIL to no avail.
I removed the phones battery and did the two point short and still, no change.
I bought a Xiaomi usb cable from amazon for Mi Note 10 and above and still same errors occur (yes, I tried all USB ports).
I have installed the unsigned drivers correctly, still, same error.
I hold all the buttons on the device for 30 seconds and then plug it in and hit flash ASAP. The result is always cannot read from COM07. Then, if I try and flash again, it says it cannot read hello packet.
With QFIL I get the sahara error.
I may be missing something here, I'm a noob who should have read the instructions and double checked everything. I have paid someone on telegram to help me, but they seem to be out of ideas too and can only suggest that it might be a hardware issue. Can installing the incorrect firmware damage hardware beyond repair?
At this point I am close to just giving up as it's taken so much of my time and the stress is unbearable lol.
Thanks to anyone who reads this post, hopefully there is something that I haven't tried yet.
Thank you
You need Xiaomi AUTH or proffessional repairing tools. Or wait untill someone patch the loader.

Categories

Resources