Ok so i just found out today about the WM6 upgrade for the xv6700 so i decided to try it.
I have a Verizon XV6700 with bootloader v1.04
i used the rom from http://forum.ppcgeeks.com/showthread.php?t=7671
i downloaded the one that says Verizon not the Verizon with bootloader 1.02
I run a pc with windows vista
here is what i did step by step
I put the ppc into bootloader mode and then connected it to the pc via usb
then i opened the exe file from my desktop and followed the directions and then clicked install
it then popped up a little window saying checking the information on your device....please wait.... and below it it said dont disconnect your device until the update is complete...
i read that the update takes about 7 mins i allowed it to sit at this for 20 mins and it still did nothing...so i disconnected the usb and then tried to restart the phone and everytime i turn it on it goes straight back to the bootloader screen i cant get out of it...is there anyway for me to get my phone to work? did i brick it? If anyone can help me it would be greatly appreciated
geez, looks like i am not the only one messing up here. I regret this fancy roms by now... but search on PPCgeeks.com some article called "stuck on BL screen" or stuck on bootloader, there''s a little exe you run to get out of it. good luck
i got mine stuck too, but no on the BL.
Related
I wuz flashing it went to 99% and gave me an error so I reset and it wuz still stuck so I took out the battery and now it won't do anything when I plug it into the pc it says unrecognized usb device is there anyway to get the pc to recognize it so I can fix it any help is appreciated
bootloader
Put it into the bootloader, the PC wont recognize the device until you flash it again, but you should be able to fix it. Get into the bootloader by pressing the power key and the voice commander button (looks like an old tape) at the same time and while holding, press the soft reset button on the bottom. This should put you into the bootloader mode, (the backlight does not light up, it just says bootloader and USB or SERIAL in faint writing depending if you have it attached to your PC)
invoking boot loader
Yes...I had a similar issue yesterday and thought to use the button sequence to force the bootloader. The other thing I had to do was get a flashlight and note the bootloader version of 2.05. I then ran the latest update tool from one of the kitchens and that allowed me to load the image of choice that I placed in the same folder.
how did you do it?
I used UNI_bootloader EXIT.exe to get mine back. same situation, v2.05 bootloader, unplugged at 99%. stuck at v2.05. run the exe, and its fine.
Sadly enough i need to post this.. i have both the 6800 and the 6700, i did the same thing twice ... starting with the 6800, had no problem fixing that one, but the 6700 for some reason after a stock rom flash that didnt take completely its stuck saying Serial (top), 1.00 (bottom) , tried uni_bootloader, tried reflashing, for some reason it cannot catch the device, however, the drivers are loaded just fine, that much i know it worked before. any ideas on how to kick start this thing ( i have no memory card at all in it , havent been able to find a miniSD around here anywhere ). Any ideas would greatly help. Thanks in advance.
Welp, Just wanted to start out with a clean slate. Went to RUU my phone and durring the RUU about 70 seconds into "Waiting for Boot Loader" windows pops up and says "The device attached has malfunctioned - blah blah blah".
Ends up coming up with Error 171 USB Connection Failed in the RUU.
Any ideas? HTC bootloader is a Device in the list.
ADB works when the phone is booted.
HTC Sync drivers are there...
Windows 7 x64.
Booted into Fastboot USB and ADB can't seem to find the device which is weird.
I have never had an issue with my phone doing stuff like this till now. I think I bought the golden hero that has no issues at all LOL.
Any ideas fellas...and the few ladies that pass through?
Kcarpenter said:
Welp, Just wanted to start out with a clean slate. Went to RUU my phone and durring the RUU about 70 seconds into "Waiting for Boot Loader" windows pops up and says "The device attached has malfunctioned - blah blah blah".
Ends up coming up with Error 171 USB Connection Failed in the RUU.
Any ideas? HTC bootloader is a Device in the list.
ADB works when the phone is booted.
HTC Sync drivers are there...
Windows 7 x64.
Booted into Fastboot USB and ADB can't seem to find the device which is weird.
I have never had an issue with my phone doing stuff like this till now. I think I bought the golden hero that has no issues at all LOL.
Any ideas fellas...and the few ladies that pass through?
Click to expand...
Click to collapse
I have had problems with my usb port not having a good connection. You can try holding the usb cable in and up towards the screen and see if that helps. That is what I had to do before replacing my Hero.
animal7296 said:
I have had problems with my usb port not having a good connection. You can try holding the usb cable in and up towards the screen and see if that helps. That is what I had to do before replacing my Hero.
Click to expand...
Click to collapse
No Dice.
Phone still works fine, but I figure I'll format it as often as I do my laptop LOL.
Just thought I would also mention that when RUU reboots the phone, it sticks at the HTC screen. And I have to pull the battery to reboot.
-------------------------------------------
I feel like just a noob, I never have problems
-------------------------------------------
Ok so if this happens to anyone else here is what I did to get it fixed.
Run the RUU, and let it fail with Error 171.
The RUU will say the Current Image version (In my case) is FRESH.
Being replaced with 2.56.....
After it fails and it is stuck at the HTC screen, Run the RUU again.
This time it says Image version 1.56....
being replaced with 2.56....
It successfully went through the second time after it was stuck at HTC.
Kcarpenter said:
Ok so if this happens to anyone else here is what I did to get it fixed.
Run the RUU, and let it fail with Error 171.
The RUU will say the Current Image version (In my case) is FRESH.
Being replaced with 2.56.....
After it fails and it is stuck at the HTC screen, Run the RUU again.
This time it says Image version 1.56....
being replaced with 2.56....
It successfully went through the second time after it was stuck at HTC.
Click to expand...
Click to collapse
Glad to see ya got it working.
Kcarpenter said:
Ok so if this happens to anyone else here is what I did to get it fixed.
Run the RUU, and let it fail with Error 171.
The RUU will say the Current Image version (In my case) is FRESH.
Being replaced with 2.56.....
After it fails and it is stuck at the HTC screen, Run the RUU again.
This time it says Image version 1.56....
being replaced with 2.56....
It successfully went through the second time after it was stuck at HTC.
Click to expand...
Click to collapse
Thanks for this! I had tried 4 or 5 times and was starting to get worried!
New to the forums, great stuff here guys!
This is great! I've search for 2 weeks trying to figure this out. Just to clarify, because some things above are implied, not explicit:
1. Run the RUU
2. Get error 171, hit the exit button.
3. Don't do anything to the phone (like remove the battery to unfreeze it or unplug it)
4. Run the RUU again
5. You win!
I'm glad this was covered, I've been getting this BS connection error 171 and have tried at least 10 times without success, I'll have to try it like this.
Heya!
I bought a demo LG Quantum for a song today and I've been trying to remove the Demo software by following these instructions:
Through work aquired a Mozart with Telstra Demo(Store) Rom. Very furstrating as it wouldnt hold settings and kept playing that damn video.....
Downloaded this rom (following the links from here and trying a few download mirrors until I found one that worked)
Turned off Phone
Held Volume Down Key while Pressing Power Button (This turns the phone on and launched Bootloader)
Connected to PC Waited about 5 minutes while Windows auto detected the drivers and installed what it needed
Right Mouse clicked on the downloaded Rom and selected "Run as Administrator"
Followed the prompts.
****NOTE**** When it got to 10% the phone rebooted - LET IT!!!!! DO NOT TOUCH IT DO NOT DISCONNECT IT - Just wait -The computer will redetect and about 10 Min later VIOLA - All sorted nice and clean WP7 HTC Mozart (with a with Telstra One Hub - which aint that bad) - Whacked the 3 Sim card in - Downloaded Connection Setup Wizard from market place and a few minutes later was sending and receiving MMS etc
Click to expand...
Click to collapse
However, I don't know if this applies to the LG Quantum since I can't seem to access the Bootloader screen and the ROM I can't find an executable ROM file like the one he refers to.
Has anyone resolved this problem on their Quantum?
Could you help me through it?
Thanks in advance,
-Aylmer
Nevermind! I was trying to flash it, but, in the LGDP2 Flashing app, I was plugging in the phone before pressing start!
Oups!
If you're still having problems, the other trick is to use the drivers from the LG Mobile Support Tool.
I got mine from eBay for $100...it is a Demo unit. This thread is very helpful and hope to remove the "Device Alive" software and enjoy my nifty windows phone!
As an avid Android and iOS user I look forward to having fun with WP7
voltagex said:
If you're still having problems, the other trick is to use the drivers from the LG Mobile Support Tool.
Click to expand...
Click to collapse
How would that trick work?
Does anyone have the link for the stock rom? I can't seem to be able to download from http://depositfiles.com/en/files/tmh1fz1ed. It always says invalid param. Could anyone post it here or upload it to mediafire or something? Thnx
ok managed to download the LG c900 ROM but installing the LGDP2 gives me the Installshield error , Catastrophic Error. And my LG USB Modem doesn't wanna install
Could you give more detail about the problem?
Also, which version of Windows are you using?
I was trying to root my phone using the information/program on http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 . The program started to run and seemed to be working but it never finished or I was an idiot who didn't give it enough time. Either way, I now have a phone that I can only get to the bootloader screen but it isn't unlocked so I can't put a new ROM on it and the factory reset doesn't get me back in. Is there any way to unlock from here or do I need to seek out and download the stock Verizon ROM and install it again via the SD card?
mwolf00 said:
I was trying to root my phone using the information/program on http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 . The program started to run and seemed to be working but it never finished or I was an idiot who didn't give it enough time. Either way, I now have a phone that I can only get to the bootloader screen but it isn't unlocked so I can't put a new ROM on it and the factory reset doesn't get me back in. Is there any way to unlock from here or do I need to seek out and download the stock Verizon ROM and install it again via the SD card?
Click to expand...
Click to collapse
After you get your phone back to 5.0 stock, run the one click root again on win 10 using the stock cable if you have it, then install SuperSU. Go to thread Official bootloader unlock for Verizon note 3 by ryanbg. This will completely unlock bootloader and you can install TWRP. But read the warning thread about using the new version.
I'm new at this but it worked for me
Good luck, some of those threads have info on getting you back to normal
Thank you for your reply. Unfortunately, right now I'm not sure if I'll even be able to get back to 5.0. The original USB cable is a thought as I'm not able to get the PC to see the phone. My only access is SD card so far.
mwolf00 said:
Thank you for your reply. Unfortunately, right now I'm not sure if I'll even be able to get back to 5.0. The original USB cable is a thought as I'm not able to get the PC to see the phone. My only access is SD card so far.
Click to expand...
Click to collapse
If you:
- pull battery, wait 10 sec, insert battery. (USB *not* plugged in)
- startup w/ Vol-Down+Home+Power
- select "Cancel" when warning splash screen displays
what happens? Does it hang for a while before it goes back to the Odin Download screen?
I'm not aware of any method to install from the SD card.
(Maybe w/Mobile Odin but that doesn't apply here).
99% of the time if there is a connectivity issue between the phone & the PC, the issue is on the Windows side if things.
bftb0 said:
If you:
- pull battery, wait 10 sec, insert battery. (USB *not* plugged in)
- startup w/ Vol-Down+Home+Power
- select "Cancel" when warning splash screen displays
what happens? Does it hang for a while before it goes back to the Odin Download screen?
I'm not aware of any method to install from the SD card.
(Maybe w/Mobile Odin but that doesn't apply here).
99% of the time if there is a connectivity issue between the phone & the PC, the issue is on the Windows side if things.
Click to expand...
Click to collapse
When I go through the steps you suggest, after I select the cancel action, the phone restarts and enters the boot loader with very little delay. The whole process takes about 10 seconds.
I've downloaded the stock ROM. Is there a way to install it from SD card? Can I use Odin on it to create a file the phone can boot from? It seems there should be something I can do...
Also - As for the connectivity issue being on the windows side, before this whole process, I had no issues connecting to the phone from Windows so I do not believe it is on that side...
mwolf00 said:
When I go through the steps you suggest, after I select the cancel action, the phone restarts and enters the boot loader with very little delay. The whole process takes about 10 seconds.
I've downloaded the stock ROM. Is there a way to install it from SD card? Can I use Odin on it to create a file the phone can boot from? It seems there should be something I can do...
Also - As for the connectivity issue being on the windows side, before this whole process, I had no issues connecting to the phone from Windows so I do not believe it is on that side...
Click to expand...
Click to collapse
'
Whew - I was able to get the stock ROM back on the phone. There was a pending update on my PC which might or might not have been part of the issue. After the restart, I was able to us Odin to push it back on. Now to root the thing again...
Need Help! GF gave me her 1+6T, carrier locked to T-mobile. I have AT&T, so I attempted to unlock the device using this link :
https://www.google.com/amp/s/www.xd...nternational-without-unlocked-bootloader/amp/
I read, followed, re-read the instructions. I kept getting the error 'Sahara communication failed'. I tried all 3 USB ports and made sure i had the correct drivers installed. The phone shows up and connects in the tool, then it gives me the error after starting the patch. Next i unplugged the phone and found it to be bricked. it wont turn on. I tried holding down the power button for 20 seconds, used button combinations, nothing. Yet it still shows up on my computer when plugged in using volume +/-
I tried using this method to unbrick:
https://www.xda-developers.com/unbrick-oneplus-6t-t-mobile-international/
Still bricked, and still gives me the same error.
What can i do? Please assist, my girlfriend is going to be pissed if i can't get this working lol. I need to get the phone working again + unlock to get my at&t sim card working on it. Thanks in advance!
EDIT: I got the phone on!!! Now I just need getting the phone unlocked. Still getting the 'Sahara communication failed' error
**EDIT 2 : EVERYTHING IS SOLVED AND WORKING NOW YOU CAN DELETE THIS
Mine gives the usb device malfunctioned error. I have installed the qualcomm usb drivers. The MSM tool wont recognize it, and my phone wont boot in any other mode except EDL. It will not boot to bootloader or anything. Funny thing is, all I was trying to do was convert the T-Mobile version to international which I've done before. During that process, it hung at "recording downloading time". I let it go for 20 minutes, according to the guide it is supposed to take 5. I canceled the process, (I had done this one other time before, and it booted just fine) and now nothing works. Please help.