Develop Bugs

Newbie but I hope not !!! help btw !!!

I own a new blue angel...called by O2 II's
So, after i read ,again,and again...I have successed enter boot loader.
With white screen it's shown the version 2.07 and the line at the top "Serial"
(uhm, i use WM2003SE as the original pda when i purchase)
Ok, the problem now is, i can't flash anyrom (in Wiki and any rom i found)
After the line appear "Don't plug cable or craddle of ...." it's seem to verifie it's self... and then the line appear again "this tool is not support for this device".....and some error like that.
I was totally confused, how i made the thing go wrong? or just i missed something???
i make a soft reset, then hard reset and then 3 button together to get the white screen with no light, still see words such as: serial, version 2.0.7...
When i plug the usb cable , then the serial change into USB as usual.
As my experience,( Dopod810 and Qtek S200) everything is normal...
One problem too, i can't connect to PC with activsync (i tried any versions as possible)but itself avaiable on Boot loader...
All you understand what happen with me???
Please help me out of this. I want my Blue Angel is not the worst i got ...(i think it's possible go up to wm6???)
Finally, thanks you all for listening( reading this topic)

Yep, Happened to me too. Heres the fix.
The regular WM6 exe will give you an error everytime with the O2 IIs. Finally I printed out the WM6 directions, and also the Blue Angel for beginners and some other threads and found the answer.
You are in the right place (stuck in bootloader that is). Now you should be ready to load the OS. In the Upgrade folder you will find:
"MaUpgradeUt_noID.exe"
Run it and you will see the progress bars on the Windows screen and the dark XDA screen. Don't bother it - allow it to complete.
After it completed, I was unable to restart, soft reset, hard reboot. I think I actually had to take the battery off. When I powered it again I saw the Color Bars and knew it was good.
Good luck, Be careful. Try to be calm. I know when I was stuck in between Roms I was close to being a nervous wreck.

erh, one more message when i fkash rom...
This MaUpgradeUT novid erh something like this but this
" This tool is not support for my device" or somehow ...
I think i really stuck...
when itself verifie version of rom , i can't see both version appear on windows.
ie : version rom which is in PDA and version of rom which is in the OS i next to flash(want to flash).
So Confused . Anyway, thank for helping !!!

You are close!
Yea,
I Kept getting that too. Couldn't see both versions. Got a couple of different error messages. you are right where I was. you've got to find the upgrade exe. in one of the folders. My IIs was stuck in bootloader and I started that upgrade and it skips checking the IIs first and just begins to xfer the data.

Bricked Magellan Roadmate 1212

So I was given this GPS and it's throwing me for a loop... You can power it up and see the Magellan splash screen. The progress bar will go all the way across (or sometimes stop one notch before the end...) then it'll freeze. This is as far as I've been able to get it.
When connected to a computer, it'll register as two devices. First as an unknown device, then halfway through disconnects and shows up as a Windows mobile device. A few seconds once the progress bar goes all the way across it disconnects. It never shows up as a mass storage device. Activesync will catch it momentarily.
I've tried numerous techniques to boot off an SD card or the power-reset combo to access the bootloader but nothing seems to work. Does anyone know of any other mythical techniques that may allow access to this device? I've got the latest firmware upgrade handy. How close it gets to booting makes me feel it's still fixable, I hate calling it a lost cause!

Bricked Roadmate 1212
Just got a new Roadmate 1212 and upgraded it from 3.00 to 3.12. After downloading the update to the unit it rebooted a couple of times in the process of installing the update so your problem may just be a failed update.
The update procedure also stressed not to plug in the unit into the USB before the update install program tells you to do so. If you did this you may need to delete the Windows drivers installed for the unit before attempting the update again. In my case on Vista, when I plugged the unit as prompted by the update, I got one brief message as Vista installed the driver and then the update loaded in about 5 minutes. After then update, Vista reported two drive letters for the unit. The one labeled TFAT was accessible and I was able to browse around and look at files. If you get this far, it may be possible to copy the \SYS files from a good unit and get yours up and running (just a guess).

[Q] Boot loader after every phone start, can´t run phone

Hi, I have a problem with my defy and I really short to deal with that. First my defy stopped on red M logo and done proceed to system start. So I go to service menu, set clear cache- cache were cleared for 30mins so I take out batery, then I set - format/factory reset. same problem, it goes without end so after batery goes off, I make McGiver style for bring pnone to life and go to boot loader, run firmware flash over RSD lite and wait......after that RSD give me this message - Phone [0000] Error verifiing code group 33 Checksums. File:0x8BAC,Phone:0x4805 . RSD do nothing, on phone were instaling. after our when I suppose this is and I take out batery from phone and try run it. Every time start boot loader with message :
Code Corrupt
Battery OK
OK to Program
Conect USB
Data Cable
I cant launch android recovery, and If i flashed firmware again a have the same and. Can you please somebody help me with that??
Thanks,
ps. sorry for my english I think is not perfect

new thing, new error mesage from RSD. he pass Checksums errors, than give me message - restarting device ( that is not happend, device were still on), afted while there is new message : Failed flashing proces. Failed plashing proces. phone [0000] Error geting subscriber unit checksum. Device API error: 0xe003003F Command : (RQRCS 0xe403203f); phone conected
result FAIL
I am really desperate.. anyone have experience with this??
Thanks for any advice.
NoDi

As I see probably nobody had this issue like I had. Tomorrow I try bring phone to seller (Vodafone), and than I have to pray for reflashing it from them. Anywhere I will post result from them after I get some, If somebody have the same problem in future like I had.
NoDi

Difrent SFB
try usuing difrent sfb f.
have similar problem at some time...
just try using another sfb and do factory reset each time

yea.. some sbf have higher or lower on img version which might prevent your phone from fully flashed.

I tried various different FW from here. Everytime the same results. Today I was bring phone to Vodafone, I wonder on verdict

you said you tried all firmware versions, can you try diffrent RSD Lite version, may be RSD lite having problem. I am using " RSD Lite 4.9.msi ".

so phone is back. In report from service were Changed bad SWAP module. In used parts were 1pcs of RF board. Anyway I brought phone back to Vodafone because he cant sign in other than 3G network, and many places in our country are sill only 2G.

Bricked my Vibe P1a42 with QFIL

Hi, I decided to write here, I hope you can help me out.
So today I tried to root my phone with the instructions found at https://forum.xda-developers.com/showpost.php?p=68696079&postcount=114
I checked that my build no. is S288, so with rooting there would be no data loss for me (I still backed up everything important of course)
First problem I came across was that I had to found how to download QFIL, I downloaded and installed version 1.0.0.2 I think.
Second was that I couldn't get the Qualcomm Com port to show in QFIL neither in Device Manager. I figured out that as well, by doing loads of research (googling)
I also installed ADB to help me get into the state where I see the Qualcomm port, because normally if I just power it off, and connect it to my PC, it powers on in the "charging interface"
So everything was working, I downloaded the P1a42_S288_160721_ROW_RAW_QFIL file, extracted it, filled in everything in the QFIL program and hit Download while holding the + & - buttons to enter TWRP mode or whatever it is called. It returned with this:
Code:
PROGRAM: Send raw data fail
Failed to write I:\Telefon Ment�sek\Lenovo Vibe P1\Root (2017,03,11)\P1a42_S288_160721_ROW_RAW_QFIL\recovery_twrp.img to the device
Download Fail:System.Exception: Failed to upload the emmc images to the phone using Firehose
...
Download Fail: FireHose Fail FireHose Fail
Finish Download
Sorry, I can't write down everything bc I already closed the program, so I'm writing these off of screenshots
I already tried other USB cables, other USB ports, other drivers, even other ROMS, but everytime I try, I get this message:
Code:
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
So currently I can't power on the device in any way, tried holding + and -, + and power, - and power, home and power, home power and +, home power and -, home power + -
Please help me, I would be really glad Cheers!
Also, sorry if my English is a bit poor, I'm a 15 year old boy who's native speaking lang is not English
P.S. I also don't know if I broke my warranty with this or not, because I technically have not rooted the phone, just did something else. And also, what if someone would've stolen it and I would've got it back and I wouldn't be able to turn it on because the thieves have broken it? (That is not the case right now, just asking).
PS 2: I have an alarm at 0:00 today, but I doubt that the phone is just gonna magically turn itself on for the alarm, we'll see. I may also try to leave the phone to completely discharge (I remember now why I didn't want to buy a phone with a built-in battery)
EDIT: I didn't mention, that the first time I tried to flash, I was using files from a Directory that's path contains both spaces and unknown (?) characters (é) (only unknown by the software) as seen above in the first box.

gabor6505 said:
Hi, I decided to write here, I hope you can help me out.
So today I tried to root my phone with the instructions found at https://forum.xda-developers.com/showpost.php?p=68696079&postcount=114
I checked that my build no. is S288, so with rooting there would be no data loss for me (I still backed up everything important of course)
First problem I came across was that I had to found how to download QFIL, I downloaded and installed version 1.0.0.2 I think.
Second was that I couldn't get the Qualcomm Com port to show in QFIL neither in Device Manager. I figured out that as well, by doing loads of research (googling)
I also installed ADB to help me get into the state where I see the Qualcomm port, because normally if I just power it off, and connect it to my PC, it powers on in the "charging interface"
So everything was working, I downloaded the P1a42_S288_160721_ROW_RAW_QFIL file, extracted it, filled in everything in the QFIL program and hit Download while holding the + & - buttons to enter TWRP mode or whatever it is called. It returned with this:
Code:
PROGRAM: Send raw data fail
Failed to write I:\Telefon Ment�sek\Lenovo Vibe P1\Root (2017,03,11)\P1a42_S288_160721_ROW_RAW_QFIL\recovery_twrp.img to the device
Download Fail:System.Exception: Failed to upload the emmc images to the phone using Firehose
...
Download Fail: FireHose Fail FireHose Fail
Finish Download
Sorry, I can't write down everything bc I already closed the program, so I'm writing these off of screenshots
I already tried other USB cables, other USB ports, other drivers, even other ROMS, but everytime I try, I get this message:
Code:
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
So currently I can't power on the device in any way, tried holding + and -, + and power, - and power, home and power, home power and +, home power and -, home power + -
Please help me, I would be really glad Cheers!
Also, sorry if my English is a bit poor, I'm a 15 year old boy who's native speaking lang is not English
P.S. I also don't know if I broke my warranty with this or not, because I technically have not rooted the phone, just did something else. And also, what if someone would've stolen it and I would've got it back and I wouldn't be able to turn it on because the thieves have broken it? (That is not the case right now, just asking).
PS 2: I have an alarm at 0:00 today, but I doubt that the phone is just gonna magically turn itself on for the alarm, we'll see. I may also try to leave the phone to completely discharge (I remember now why I didn't want to buy a phone with a built-in battery)
EDIT: I didn't mention, that the first time I tried to flash, I was using files from a Directory that's path contains both spaces and unknown (?) characters (é) (only unknown by the software) as seen above in the first box.
Click to expand...
Click to collapse
Dear Pls follow this link
https://forum.xda-developers.com/vibe-p1/how-to/lenovo-vibe-p1-a42-c72-root-ready-t3533693
You can see the qualcomm driver only when you switch off phone and hold Volume+/- plus power button.

I can't bc my phone won't turn on currently,
So I probably shouldn't have used ADB to get into fastboot or whatever, my phone may be broken because I tried to do the flash while in that state.
Did you read my whole post though?
The next thing I'll try then is uninstalling all the drivers and programs related to my phone, and then following the guide you suggested, because I still see the Qualcomm port, I just can't do anything with my phone.

OMG, I have waited a few hours, and just randomly thought why not try again flashing the rom (I don't think this is the right word for the QFIL Download procedure), and it worked! So I'm actually really happy I don't need to send it in to repair or try other things. I got the system I started the procedure with, so I didn't actually lost any of my files neither did I root my phone. Now to decide if I want to try again rooting it with the detailed instructions you sent or just leave it like this so I avoid getting into all this again. I think I will try again to root it lol why not
Will report back here if it was successful

I have successfully rooted my phone, and installed the Xposed Framework on my phone, so I'm really happy.
I can't really seem to find where to lock this thread so please someone lock this thread (I am not familiar with this forum, so I don't know if it is needed or not)

[Partialy Bricked] H815 - how to get to stock

Hello Guys
My friend ask me for get a Lineage OS to his H815 with Nougat. I agreed as I made few successful changes from stock to Lineage OS with Samsungs and older LGs (like L3 E400). But G4 is really more complicated, more than I expected . Firstly I wanted to unlock this phone with FWUL, so I download a VirtualBox emulated image with FWUL and after it boots I opened SALT program and it detects the phone. I made a basic backup and then I choosed Unlock G4 (UsU). After that some windows pop up. Last window was a pre-checking, when the bar gets to the end window closed and nothing more was happening. So after almost hour of waiting I just turned off the phone - I thought its all. After that while phone is booting I have those messages in the left top corner:
[820]-----------------------
[870]
[920] Secure boot error!
[970] Error code : 1009
[1020[ OFFICIAL !!
[1070]
[1120]-----------------------
Its booting, but only sometimes its normal boot, most starts are with bootloop, sometimes its start after 10 restarts, sometimes after 2nd restart, sometimes after plug in/plug out USB cable it starts boot normally (connecting cable only to phone, not to PC), sometimes only thing that helps is to take out the battery. I made full wipe to be sure that its not a software problem, but only thing I achived with that is fact that phone has a Nougat and now it have a Marshmallow. It is (was?) H815, but now model name is LGLS991 (?), it gets very long until it shows software version (V20g), IMEI is unknow, even when I type *#06# I get the null response.
I can get into recovery, can put phone into download mode. But i'm not able to do anything to get LOS or a least Nougat.
I've read many, many tutorials how to get G4 working properly after unsuccessful unlock, but nothing helps. What I've tried:
1. Flashing stock Nougat for H815 with LGUP, installed USB drivers, proper DLL, set com to 41, but when I trying to flash, after a 4% i get error: KDZ file is invalid. Downloaded few KDZ firmwares, dont belive that every single one is invalid, there is something wrong with LGUP or with settings, but I cant find what
2. Flashing with LG Flash Tool 2014: tried both normal flash and cse flash and always stoping in the same moment, with "Connection to server failed. Try again in a moment". Read many tutorials about this error, none was helpful in my case.
3. Flashing with LG Flash Tool v1.8.1.1023 and a TOT file, but after select of dll and tot file and press the yellow arrow I get an error: "Failed PreviousLoad()"
Tried all this methods on second computer but without a luck.
What else can I try to get this G4 working properly? Maybe try to install some rom from stock recovery? But which rom will be ok and dont get things worst?
If you need more info dont hesitate to ask. Would be very greatful for any advices .

you definitely didn't read enough... go to read again the UsU thread and as you've read the whole tutorial, you can also read the whole FAQ and the OP, because 90% of what you pointed out in your publication (which incidentally is in the wrong section) is explained there.
A quick advice: Don't try to flash any KDZ/TOT again.