Database Users

Anyone flash upgrade software/flash ROMs for customers?

I just bought a second hand Touch HD apparently running win6.5 + with additional software on. At present the phone appears to have a number of software "issues". Texts don't always send or get received, I cannot access the deleted messages folder, it appears to run quite slowly, and has frozen a couple of times (there are more but cant remember them all).
Unfortunately I am not in the slightest bit knowledgable about how to flash ROMs etc. I have read many of the threads but simply do not understand the instructions or often even the jargon.
All I want from my phone is for it to run as quickly and reliably as possible without any glitches. The only additional software I need is the TomTom which is installed and if possible it would be good to be able to download some of the available apps if I wanted (though not vital). I also use it to send/receive emails, as a modem for the laptop occassionally, and for simple web browsing.
Is there anyone out there who can sort a phone for customers - anywhere I can send my phone and pay someone to wipe the phone clean, install a decent ROM, and reinstall the TomTom?
Any help or advice would be much appreciated

While I would love to say, "I'll do it for you" I think the expense of posting stuff wouldn't be worth it in the end. It's really not hard to flash as long as you do a bit of reading. And it's a rewarding experience. May sound odd but it feels good to make a device your own, even if it's for someone else.
Theres are only one step I recommend to everyone to ge them started and that's to HardSPL a device. This basically makes your device so that if you make a mistake on it, 99.999% of the time it's fine and can be re-done and sorted out.
If you havn't tried another sim card in it to see if its unlocked or not, then best to do that, or ask in a phone shop.
From what you describe about the phone, it sounds like someone has already flashed it before so you will need to check if it is HardSPL'd already or not. To do that hold down the bottom volume button on the side of the phone then press the power button on the top. It says SPL-something. If it's 1.56.OliNex you're good to go. If not, go here. Then I would recommend flashing a rom from the "roms" section, there are many to choose from there, but I recommend Topix 3.5.5. Then just install Tomtom and you're set.
While it looks like a lot of reading, there are some great guides there, and it's definitely worthwhile and very easy. Just run through them in the order I listed and you'll be laughing after you've done it, wondering why you were so hesitant before.
Good luck.

Cheers stuntdouble,
At the risk of sounding totally incompetant, I tried what you said but holding the volume down button and pressing the power button appears to do nothing except turn the phone in and out of standby. I also tried it with the phone off and it simply turned on again.....
The previous owner has installed win6.5 and the interface from the HD2 (apparently) but it doesn't appear to work properly. Hence my wanting to sort the phone. I will hold out hope I can find someone who will do it for me.

lorin616 said:
Cheers stuntdouble,
At the risk of sounding totally incompetant, I tried what you said but holding the volume down button and pressing the power button appears to do nothing except turn the phone in and out of standby. I also tried it with the phone off and it simply turned on again.....
Click to expand...
Click to collapse
In order to check your current SPL version, you need put the phone into Bootloader mode. To do this, you need to press down on both the bottom volume button and the power button simultaneously for a few seconds, you will see a tri-coloured screen - the red section at the top tells you what SPL version you have. To exit this screen, just remove the battery cover from the back, remove the battery for 3 seconds, and then re-insert and power on the phone again to return to normal.
The previous owner has installed win6.5 and the interface from the HD2 (apparently) but it doesn't appear to work properly. Hence my wanting to sort the phone. I will hold out hope I can find someone who will do it for me.
Click to expand...
Click to collapse
I suggest you follow this guide, it tells you exactly what you need to do step-by-step when flashing your phone.

LG G2 D802 - Power Button Problem

Hey everyone,
First of all thank you for taking a look in my thread, this is my second post here in this forum but, I just have to tell you guys, I've been around since 2012 and you guys rock!
Anyway enough of chit chat, so I had my phone pretty much hard bricked, thanks to some tutorials I've finally found a way to get it back to life BUT ( there's always a but ), it isn't like before, everything was working very nicely after the fix, the Power button stopped working, the volume rockers are still fully functional but the power button isn't. So I thought "f*ck this, I gotta buy a new flex assembly", that's what I did, it arrived today, so I got to work and put it all together with the new button, but for my surprise it is EXACTLY de same as before, so it seems like it has nothing to do with the flex assembly/buttons itself but something more like motherboard or something..
Have any one of you guys had this issue? By the way another very interesting thing is that the buttton "still gives signal" since if I press on it, it doesn't do anything even with the phone off BUT, if I have the phone turned on, and I press it for 5+ seconds , it shutdowns the phone as it should! So why isn't it working when I do a press, but if I hold it works?
By the way my phone when died even the partition table got corrupted, so I even had to redo that could it have anything to do with it?
Oh and the basic tips of putting the phone in Download Mode and fully revert to stock didn't work, already did it many times since I brought it back to like..
Regards, and thank you for reading this LONG post and spending your time with me :silly:

Anyone got any clue please?..

SlashPT09 said:
Anyone got any clue please?..
Click to expand...
Click to collapse
Hi, i has been a long time until you wrote this topic, but now, in 2018, i got the same problem that you.
I bricked the phone, unbricked with some xda's tutorials, install a kdz image and system got ok, but the damn power button not work.
It work on a very specific moment that is when the phone is on and i press the button, after 5 seconds the phone turn off, but none menu appears, it just turn off. Besides, it won't work to turn on the device. In this case, i aways need to put the cable and when the LG log appears I must remove (if not, the battery symbol is shown, and the device not turn on).
I wonder if you were able to fix your phone or someone of xda had this problem.
Thanks

Nope never got it fixed just moved on and bought another device, besides that is now a outdated device..

Urgent help needed... tried everything!

Hi everyone,
You can probably guess where this is going. I bricked my Axon 7 Mini B2017G.
Yesterday I had the genius idea that I was going to do something awesome with my phone, so I went into recovery and flashed a file called "emmc_appsboot.mbn" but unfortunately it was until only afterwards that I discovered that it was for the A2017G, which I think is the not-mini version of the phone, and I probably have the B2017G. And let's assume that as of yesterday, I knew absolutely NOTHING about smart phones. I can press the power button and get nothing. No boot. No recovery. No backups.
What I've tried:
I cannot get into the same mode I did yesterday that lets me flash files from an sd card, which I think is called Recovery Mode.
I can get into a mode that says FASTBOOT MODE by holding the up and down arrows, which I think is called EDL Mode.
In EDL Mode, it says "DEVICE STATE - locked" in scary red letters.
In EDL Mode, ADB doesn't work, because I think ADB is much higher level, like some application on the OS that you talk to via networking protocols?
The fastboot command doesn't work, because it gives me an error that OEM unlock isn't allowed.
The Axon7Tool doesn't work because it can't detect the phone, maybe because it's looking for the non-mini version?
The MiFlash tool is the ONLY thing that can detect my phone! This must be important but:
I've tried shoving dozens of zip files into MiFlash from the interwebs, but they all give me an error that it couldn't find a bat file named "flash_all_except_data_storage".
There are so many versions of MiFlash available - some are versioned by date, some look kinda like major.minor.revision, and they're all anywhere between 20%-100% in Chinese (which I thought I couldn't read, but somehow I think the buttons "Next", "Prev", and "Do the things" are the same in every human language now).
When I look up information about MiFlash, it sounds like it's for another company that's not ZTE!
But when I look up information about unbricking the non-mini, XDA forum guides say to use MiFlash!
That one website Host with all the Files and the Androids, doesn't have any files for the Axon 7 Mini.
I am NOT opening up my phone case. At worst, I'm going to RMA my phone in and pretend that I was taking a vacation to... Upper Michigan(?)... and that it was on hold at the post office and found out it was a lemon when I opened it. Because science.
I barely have any Internet - only for a few hours a day, with varying degrees of dialup slowness, and various degrees of all the good websites are blocked (yes - sometimes all of the proxies).
Also... please don't assume I have certain things installed such as adb, fastboot, miflash, etc. Please let me know exactly what I need, where, and what versions. This is because I have less than ideal computer access.
MiFlash must be the key! It sounds to me like the parts ZTE used to make the phone has a secret hidden backdoor built into the USB jack where if you send certain commands, it opens up a tunnel somehow (potentially a serial connection?) that goes straight into the phone's insides, with no limitations, that they probably use to do... put software on the phone in the factory???
But what is this .bat file that it needs? What do windows files have to do with my weird-linux-java phone? Where can i get the correct boot files to put on my phone and how can I shove them into MiFlash so that it works? Can I steal these files from somewhere, or fashion them somehow, or get them from one of you guys? Am I doing something completely wrong? What other information can I give you to help me better? How can I unbrick my phone? I know it must be possible! (without cracking open the case and poking 5V wires into various places)
Please help me urgently! Thank you, you all have my eternal gratitude <3
EDIT 2018.05.17 21:00+0000:
So I found a script file on the interwebs with the same name that MiFlash is looking for - "flash_all_except_data_storage" - and all it contains is a bunch of fastboot commands that appear to flash individual files to separate ...sections? ...paritions?? One of them is even the file that I borked - the "emmc_appsboot.mbn" file. What does MiFlash have to do with fastboot? When I had tried to do fastboot before, I wasn't allowed to modify the device. Where can I get the correct emmc_appsboot file for my specific device? And am I on the right track? How do these things fit together and how do I use these things?
EDIT 2018.05.18 01:30+0000
There's so many conflicting guides on the Internet... is the mode that I'm booting into by holding down both volume buttons with the words "FASTBOOT MODE" actually called bootloader mode? If so, how do I get into EDL!?!?!?! Help pls.
EDIT 2018.05.18 03:00+0000:
I tried bs-ing the script file that MiFlash is looking for and it appears that the only thing MiFlash does is run fastboot for me! That's not helpful at all because fastboot can't flash!! I'm beginning to believe that I'm not actually in EDL mode. How do I get into EDL??

If you have the US model, entering EDL mode is done (while the phone is off) by holding down the Volume Up and Down keys at the same time while plugging the phone into your computer, and afterwards, continuing to hold down the keys for at least 3 more seconds, then letting go.
Note that there will be no indication that EDL mode is on; no lights, screen is completely off, and no sounds/vibrations whatsoever. The only way to identify whether your device is in EDL mode is via tuliptool (which you can find in the ROM/Development section for this phone) or through your computer's device manager.
Good luck, I hope this helped.

Oh. My. Goodness. Thank you so much for replying!!!!
So I was initially correct in thinking that EDL is the volume up and volume down and then plugging in. That's EXACTLY what I've been doing, but when I do it, I get to a screen with a lot / some text on it as I've briefly described before.
The screen has, notably, words in red text that say "FASTBOOT MODE". It also presents me with an invisible menu that I can scroll with the volume keys - "Start" in green, "Restart bootloader" in red, "Recovery mode" in red, and "Power off" in white. I'm assuming that I can select an option with the power button - selecting "Power off" correctly, well, powers off my phone. Selecting "Restart bootloader" seems to restart my phone into the same mode. Select the other options gets my phone into a... bootloop? It's when my phone has an underscore in the very lower right, just a few pixels wide, that appears for a bit and disappears again, followed by a very short vibration before it repeats.
In this mode, it presents itself to my computer as a USB device vendor 0x18d1 (which my computer calls Google) product 0xd00d (which my computer calls "Android Bootloader Interface"). I dunno how you guys write out these USB codes sorry.
Does this mean that I have the EU version? I really hope not! Is there any way I can check? What do I do if it is the EU version?
JoeGatto said:
If you have the US model, entering EDL mode is done (while the phone is off) by holding down the Volume Up and Down keys at the same time while plugging the phone into your computer, and afterwards, continuing to hold down the keys for at least 3 more seconds, then letting go.
Note that there will be no indication that EDL mode is on; no lights, screen is completely off, and no sounds/vibrations whatsoever. The only way to identify whether your device is in EDL mode is via tuliptool (which you can find in the ROM/Development section for this phone) or through your computer's device manager.
Good luck, I hope this helped.
Click to expand...
Click to collapse

So....
I got my phone working again. (and bonus points for it now being unlocked... yay!) But of course not rooted, darn.
I'm not ungrateful for the help from everybody in the XDA community, quite the opposite - everything here has been super helpful and it goes without saying that I wouldn't have been able to fix my phone without all of your help. But in my humble/honest opinion... forums are the wrong place for all of this. Unless I completely missed a whole website you guys are hiding somewhere? I think you're all doing this wrong.
Whenever a forum post/guide, sticky or not, says, "download this software and press this button", that's completely wrong - it's nonsense. Devices simply don't work like that. Same for, "hold these buttons for x seconds", "go to this menu and enable this", "install this thing then replace this with that", etc. That's not how it's actually done. I can kinda guess why the XDA community doesn't care about any of that. You have your developers that make roms, then you have you the other folk that install the roms. Sometimes. And other times brick their phones.
From my understanding, humans have spent the last few decades (at LEAST) actually taking a look at technology - dividing it up into little pieces and giving each one a name. Now that you can name them, you have (more) power over them. These little pieces all connect with each other in some way. There are also collections of pieces that operate together to perform some sort of function. Understanding how specific pieces fit together and function together gives one the ability to modify them.
In my mind, there needs to be a collection of these... names... in a simple format that lists precisely what each piece does, and what other name-pieces interact with....
...
Well then! As I was about to wrap up my post, I came across this little gem - https://forum.xda-developers.com/wiki/Main_Page - so you people were hiding such a website this whole time! You won't believe how silly I had felt when I discovered that website. Wow, I must be pretty stupid. I was bumbling around on the forums this whole time like an idiot.
The XDA Wiki has the potential to be an amazing source of good, an even better version of the amazing pool of knowledge that you all have here on the forums. I just wish that there was more content to it! The wiki has absolutely no mention of the words B2017G, Axon 7 Mini, or even the Axon 7. It would have been such a treasure if the wiki had actual information on it. Whoever is actively working on the wiki - keep up the great work that you're doing.
Please add more information to the wiki! It could help so many people.
Well, that is all. Peace everybody.

Hi buddy,
I can easely understand the frustration you got. I have this axon mini just to play/have fun testing new roms, etc...
Recently I got the same issue you had before: I mean black screen, no led, no battery charge, nothing except this Quadcomm drviers.
Good point are :
- Miflash is running & is recognizing the phone
- Windows is also recognizing the phone
Bad points are:
- ADB do not recognize the axon
- No flashtool also
May I kindly ask you the methodology you used in order to wake up this phone ?
I've the B2016G
thx

Nathan4 said:
XDA Wiki: https://forum.xda-developers.com/wiki/Main_Page
The XDA Wiki has the potential to be an amazing source of good, an even better version of the amazing pool of knowledge that you all have here on the forums. I just wish that there was more content to it! [...] It would have been such a treasure if the wiki had actual information on it. Whoever is actively working on the wiki - keep up the great work that you're doing.
Click to expand...
Click to collapse
@Nathan4 - "To be able to create or edit pages, you must be registered as a user at xda developers." - So you can add your knowledge to the Wiki for a start!

oneplus 2 not working after screen replacement

My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe

Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.

there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..

Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx

Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs

@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.

dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs

Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.

Screen won't turn off and cannot have LG UP recognize my device from the frozen scree

a) phone stuck on the screen as seen here
b) pressing volume down and power button for eight seconds or so simply restarts and brings me back to this same screen
c) I'm not getting the pink circle LG logo thing in the interim (between screen going blank and coming back up). The phone just boots up to this particular screen without anything in between, except for black screen for brief second
d) The phone does not have an unlock bootloader because this model HD870DS is not unlockable
Does anybody know how to force shut this phone down? Do I have any other alternatives to make this phone running again?
My only hope is that if I can somehow, with the help from the good folks here, shutdown the handset so that I can use the LGUP to flash the original KDZ file.
Any help would be appreciated.

Try vol down + power for about 5-6 seconds. Longer will soft reboot. Else wait for battery to run out.

Fixed! I had to force into download mode and then automatically have the LG Bridge detect an 'update' and download it. LGUP does not and did not work and neither did/does Uppercut in trouble shooting, if anyone is interested in February of 2020. I know what I am talking about. With so much development here at XDA and this phone not aging so well (sporadic Pie updates around the world, etc), all the DLL files, LGUP versions, and Uppercut versions vary from 1.0 to 1.14 to 1.16 on the web (combined). With no dedicated developer/maintainer of pooling these resources AND updating them periodically, it is pretty much up to one's own, on which combo of LGUP-DLL--UPPERCUT to use and which kdz to download, etc. Lot of misinformation exists out there as to which file you should or should not use. That is my two cents on the situation involving LG G6, here at XDA and elsewhere. Those that got updated to Pie (India was latest) are in luck. Others, you can go to hell, as far as LG is concerned.
Anyways, for those who might/can/could end up EXACTLY in my position, here is how to troubleshoot
a) if you are on bootloop like I did, when on that screen, press Vol down and power simultaneously for eight to ten seconds until the screen turns black. Then...
b) AS SOON AS IT TURNS BLACK, let go of both buttons and simply keep the Vol Up button pressed
c) you will see the blue dotted 'download mode' start
d) connect your cable to the lappy or desktop
e) here is the most imp part--you DO NOT need anything other than LG Bridge to restore your phone the correct manner i.e. if you are a noob and don't want to spend more than 72 hrs seeking the right amount of info and right type of issue pertaining to you
f) how to do it: https://www.youtube.com/watch?v=JNAvoq3Dr6U. Follow this guy's instructions. He explains well and to the tee. LG bridge will automatically download the requisite kdz file for you. You do not have to download anything.
Finally, worth mentioning, a certain junior member here at XDA (with three posts since 2018; my bad that I did not read up on his reputation before following his/her instructions on how to recover my bootloop) on this very forum, managed to slip in an .msi file extension that was actually a malicious malware that crashed my computer. Fortunately, I have a backup system to work with, so I got away with that. Keep your eyes peeled for your best solution. Keep reading and researching and never give up. It takes time but there is rarely a thing as hard brick these days...