Develop Bugs

Invalid Tool Error

So..my phone is rather useless at the moment. Won't load the rom after freezing up while i slept last night. I go into bootloader and try to reflash but get the error "Invalid update tool" and it says something about a newer version. Has anyone had this error or know how to fix it? I am in desperate need of assistance here. Thank you for all replies in advance.
Edit: The exact error is as follows
Code:
ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA Phone. Please get newer Update Utility.
I was running Kavana cooked rom 6.1.
I have tried to reflash with atleast 5 different roms and they all present this error.

Just checking, but did you try the default ROM for your device? If it is a T-mobile Dash, you will want to use one the the Tmobile stock ROM's first.

cswroe said:
Just checking, but did you try the default ROM for your device? If it is a T-mobile Dash, you will want to use one the the Tmobile stock ROM's first.
Click to expand...
Click to collapse
Yeah, I tried them and got the same error. Thanks, though.

OxR said:
So..my phone is rather useless at the moment. Won't load the rom after freezing up while i slept last night. I go into bootloader and try to reflash but get the error "Invalid update tool" and it says something about a newer version. Has anyone had this error or know how to fix it? I am in desperate need of assistance here. Thank you for all replies in advance.
Edit: The exact error is as follows
Code:
ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA Phone. Please get newer Update Utility.
I was running Kavana cooked rom 6.1.
I have tried to reflash with atleast 5 different roms and they all present this error.
Click to expand...
Click to collapse
I know this might be a stupid question of me but, did you do a hard reset?
Why would you make another thread regarding issues with your phone, when you already have a thread going about problems with your phone?
Please post accordingly You should've posted this other issue on your previous thread, rather than making a new one! Can you imagine if everyone would make a thread for every little issue with their phone?

roloracer said:
I know this might be a stupid question of me but, did you do a hard reset?
Why would you make another thread regarding issues with your phone, when you already have a thread going about problems with your phone?
Please post accordingly You should've posted this other issue on your previous thread, rather than making a new one! Can you imagine if everyone would make a thread for every little issue with their phone?
Click to expand...
Click to collapse
It won't hard reset. I made a new topic because this is a completely different problem. I apologize if it was not necessary.

Bump.
Any ideas at all?

Ah yes.
My bomb didn't detonate until some time Wed/Thu night. 6am Thu morning I had to be at my local Polling Station where I was to be the 'Presiding Officer'.
Bad, bad timing.
Still, I managed a hard reset without the SD card in, (this took a few attempts), and having basic phone function, off I went to do my bit for European Democracy - honestly, the whole thing would be chaos without me ...
Anyway, I digress. I do that quite a lot. There was this one time ...
... I didn't get 'round to trying to sort it all out until Sat afternoon, (the phone, not the European Parliament), and as I have flashed this phone to buggery and beyond I expected it to take little time.
Ha. Ha. Ha.
I downloaded the latest version of the Energy ROM, (love it, love it, love it), ran the .bat file and; error 270.
I sparked up the bootloader and, of course, no connected device meant no update. I tried various 'stock' ROMs and got the same error you describe.
In UK, my provider is BT and there is no image link in the stickies, (I have finally found one, I will send a Mod a link), and tracking a full basic .exe image proved really difficult.
However, once found, all my problems evaporated.
So, find an executable basic ROM image from the phones' original provider, fire up the bootloader, run the .exe and a few minutes later you will be able to reflash.
Honest.
I believe you can also load the image as a .cab file onto the SD card and install from there but I didn't have to investigate this so can't promise anything. Sorry.
The ROM image is the key.
Once the bomb detonates, hard reset etc seems to become a bit flakey - keep trying.
I'm rambling again, aren't I?
Another beer I think ...
** Edit **
Yes, of course the BT ROM is now working.
Now I don't need it.
Ah well.

[Q] Constant crashes/reboots

I have suddenly developed a problem with my DHD. As soon as it connects the network via WCDMA/(3G) it crashes. I can use GSM without any problems. If Mobile data is enable, then that works with 'G' over icon. I have already done a restore to last April and a system reset, but neither made any difference. I have also tried different SIM and SD cards. It started by occasionally crashing with Maps running, and it got quite hot. It would be OK after 4-6 restarts, but now as soon as it tries to connect it crashes.
I am in the UK in SW and mobile coverage is very patchy. There is no 3G at home and only GSM in some rooms.
The phone is unlocked, but with S-on. I have ClockworkMod recovery running, and the system is:
Standard 2.3.5
Kernel 2.6.35.10-g931a37e (Nov 2011)
Sense 3.0
Software 3.12.405.1 with CL199157 release key
Radio 12.65.60.29U_26.14.04.28_M
Any help would be appreciated. I am beggining to think it's a hardware/motherboard problem
Thanks

I think it's a rom problem

Gussta said:
I think it's a rom problem
Click to expand...
Click to collapse
But it is the original ROM, and I get the same after a restore to 12 months ago, and a Factory Restore.
Thanks for the comment.

Factory reset sometimes is not enough.
Try flash it again.

Gussta said:
Factory reset sometimes is not enough.
Try flash it again.
Click to expand...
Click to collapse
A bit more ifo from the Log:
The "Sent to HTC" log file shows this error e.g.
[SMD]ARM9 has CRASHED
[SMD]smem: DIAG '[WCDMA]
07:17:25 FATAL: rrc (rrccsp.c:08982) Failure adding acq. entry in CSP substrate %d (irq0)
Restarting Linux...
I shall try a reflash next.
Thanks

Ratsea said:
A bit more ifo from the Log:
The "Sent to HTC" log file shows this error e.g.
[SMD]ARM9 has CRASHED
[SMD]smem: DIAG '[WCDMA]
07:17:25 FATAL: rrc (rrccsp.c:08982) Failure adding acq. entry in CSP substrate %d (irq0)
Restarting Linux...
I shall try a reflash next.
Thanks
Click to expand...
Click to collapse
I found this thread: http://forum.cyanogenmod.com/topic/50801-random-reboots-2/
It's supposed to be a problem with some version of GB (UK) rom.
If flashing rom, get you the same error you can try use aahk to get S-off on your device, and after that you can flash WWE ROM (it's a standard world wide rom witch allways work the best).
Here's the link of shiped roms: http://www.androidruu.com/?developer=Ace
And if u get s-off you can use this rom: http://forum.xda-developers.com/showthread.php?t=1382235
In first thread that I send you some one said that it can be problem with battery. Try if u have the same problem when you charging it.
P.S.: I have remember now that my friend has the sam problem when he try to use the camera with flash on (even if battery was charged more than half), and when he raplace the battery, everything work fine.

I am a bit confused as I didn't think I needed S-Off to update ROM, provided I manually flashed the boot.img file. I have moved away from AAHK as it is no long supported if you get into trouble.
This problem is curious as it only started a week ago after a trip to Morroco, and curiously there is an identical problem report on the Vodafone forum after a trip to Morroco (see forum-dot-vodafone.co.uk/t5/HTC/WDCMA-Fatal-error-boot-loop/td-p/1605342). No solution though.
I shall have a go at a new ROM, and report the outcome.
Thanks for the help.

Ratsea said:
I am a bit confused as I didn't think I needed S-Off to update ROM, provided I manually flashed the boot.img file. I have moved away from AAHK as it is no long supported if you get into trouble.
This problem is curious as it only started a week ago after a trip to Morroco, and curiously there is an identical problem report on the Vodafone forum after a trip to Morroco (see forum-dot-vodafone.co.uk/t5/HTC/WDCMA-Fatal-error-boot-loop/td-p/1605342). No solution though.
I shall have a go at a new ROM, and report the outcome.
Thanks for the help.
Click to expand...
Click to collapse
If you have stock ROM you can flash it only with stock rom provided with your carrier
With unlocked hboot, with S-off or with goldcard you can flash with other carrier.
In my opinion the best way is always S-off and stock rooted wwe rom.
With this solution when ever you get some problem or birck you can fix it because you have all premissions.
Unlocking hboot with HTC dev is the worst way. People report to many bugs.
About aahk, you can get when ever you want suport for it, here on this forum.
Or you can use AAHK2 by Phiber2000: http://forum.xda-developers.com/showthread.php?t=2367322
Did you try with full battery and mobile phone connected to ac adapter to see if you have the same problem?

This is quick hard work - I have Window 8.1 and I can't get the PC to see the DHD in CMD/Fastboot, so I am a bit stuck. It can't enumerate the device..
HTC Sync works and I have the latest drivers etc. AAHK2 says it can see the DHD whilst it is switched on, but in the bootload, it fails.
I shall have to find a Win7 pc, as it did work when I rooted and unlocked the DHD.

Ratsea said:
This is quick hard work - I have Window 8.1 and I can't get the PC to see the DHD in CMD/Fastboot, so I am a bit stuck. It can't enumerate the device..
HTC Sync works and I have the latest drivers etc. AAHK2 says it can see the DHD whilst it is switched on, but in the bootload, it fails.
I shall have to find a Win7 pc, as it did work when I rooted and unlocked the DHD.
Click to expand...
Click to collapse
Did you try something like?:
http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-81/
or
http://forum.xda-developers.com/showthread.php?t=2596698

Gussta said:
Did you try something like?:
I did look, but there are x64, and I am x86, so 32 bit. I think it should be working OK
Click to expand...
Click to collapse

Ratsea said:
Gussta said:
Did you try something like?:
I did look, but there are x64, and I am x86, so 32 bit. I think it should be working OK
Click to expand...
Click to collapse
Did you try first to go in fastboot with HTC sync opened that he first try to install driver propperly for that mode.
I think I have had the same problem even in WIN 7 x86
Click to expand...
Click to collapse

Gussta said:
Ratsea said:
Did you try first to go in fastboot with HTC sync opened that he first try to install driver propperly for that mode.
I think I have had the same problem even in WIN 7 x86
Click to expand...
Click to collapse
I didn't think this would get so complicated!! I have fired up an old Vista PC, and updated the drivers from the AAHK2 post. They would not install - error reading transform location - so I downloaded the lastest HTC version 4.1.0.1. and used them instead.
I can run 'fastboot getvar all' on a CMD window, no problem, but...... if I try with AAHK2.cmd, it starts, and clears some old stuff, then says, NO phone connected. The phone is in bootloader/fastboot usb mode (in red). I guess its still a driver problem.
This is a dumb question, but I assume the phone should be in Bootloader mode, as I did try the script aahk2.cmd with the phone just running normally, and it did see it and proceeded to the next menu - it suggested option 'h' for HTCDev unlocked phone.
Click to expand...
Click to collapse

Your hboot is: locked, unlocked, relocked?
What it's say in hboot?

Gussta said:
Your hboot is: locked, unlocked, relocked?
What it's say in hboot?
Click to expand...
Click to collapse
unlocked,
If I start it AAHK2 with phone normally on, it starts Ok, It want to download an RUU - I have already done this but maybe have put it in the right place. Should it be on the SD card somewhere (PD98IMG-Xgb.zip)?

Ratsea said:
unlocked,
If I start it AAHK2 with phone normally on, it starts Ok, It want to download an RUU - I have already done this but maybe have put it in the right place. Should it be on the SD card somewhere (PD98IMG-Xgb.zip)?
Click to expand...
Click to collapse
I never use AAHK2.
I only use the AAHK but i think it isn't much difrent.
You can:
when you go in fastboot type: fastboot oem lock
boot in rom
In aahk when you first time download PD98img-GB2.zip it allways stay somwhere in first folder of unziped aahk
after you boot in rom, run aahk2 and if you relocked hboot just press "1" instead of "h".
When I get home I will download AAHK2 and open the script to see what's the difrent's between.

Same Problem!
Hi
I think i have the same problem... I got back from a trip to Morocco last week... my DHD worked fine while over there, but started rebooting as soon as i turned Airplane mode off when landing back in the UK.
It can turn on for periods, and seems very stable when i disable the radio (turning on airplane mode, or removing the SIM). I think it's crashing whenever it searches for a network (regular reboots while driving, but not when sitting at my desk). I can force a reboot by searching for a new network in the settings. Are these symptoms the same as yours?
It's a 3 year old Orange DHD, using the stock build (not rooted yet).
I'd love to know if you get any more clues to your problem.
Ratsea said:
I am a bit confused as I didn't think I needed S-Off to update ROM, provided I manually flashed the boot.img file. I have moved away from AAHK as it is no long supported if you get into trouble.
This problem is curious as it only started a week ago after a trip to Morroco, and curiously there is an identical problem report on the Vodafone forum after a trip to Morroco (see forum-dot-vodafone.co.uk/t5/HTC/WDCMA-Fatal-error-boot-loop/td-p/1605342). No solution though.
I shall have a go at a new ROM, and report the outcome.
Thanks for the help.
Click to expand...
Click to collapse

FlaminDave said:
Hi
I think i have the same problem... I got back from a trip to Morocco last week... my DHD worked fine while over there, but started rebooting as soon as i turned Airplane mode off when landing back in the UK.
It can turn on for periods, and seems very stable when i disable the radio (turning on airplane mode, or removing the SIM). I think it's crashing whenever it searches for a network (regular reboots while driving, but not when sitting at my desk). I can force a reboot by searching for a new network in the settings. Are these symptoms the same as yours?
I'd love to know if you get any more clues to your problem.
Click to expand...
Click to collapse
Hi, and yes pretty much. I have found that if you set the phone to GSM only, it fixes the reboots (as does airplane mode too), and data is still received over 3G if available.
It is very curious about Morocco though. We were in Marrakech for about 5 days, and used the Maps on the phone (offline mode) a lot. I also saw another vodafone report too dated July 2013, so something is happening.
I have now managed to run AAHK2 and rooted and S-Offed the phone, so I shall be trying some other ROMs. I have tried KitKat, but in kept freezing.
Good luck.

Gussta said:
I never use AAHK2.
When I get home I will download AAHK2 and open the script to see what's the difrent's between.
Click to expand...
Click to collapse
Thanks for you patience, I have finally run the AAHK2 script, and after another couple of driver problems, and a failed flash, got it running.
The drivers are different for 2.3.5 vs 2.3.3, so that confused Vista.

Ratsea said:
Hi, and yes pretty much. I have found that if you set the phone to GSM only, it fixes the reboots (as does airplane mode too), and data is still received over 3G if available.
It is very curious about Morocco though. We were in Marrakech for about 5 days, and used the Maps on the phone (offline mode) a lot. I also saw another vodafone report too dated July 2013, so something is happening.
I have now managed to run AAHK2 and rooted and S-Offed the phone, so I shall be trying some other ROMs. I have tried KitKat, but in kept freezing.
Good luck.
Click to expand...
Click to collapse
Ratsea said:
Thanks for you patience, I have finally run the AAHK2 script, and after another couple of driver problems, and a failed flash, got it running.
The drivers are different for 2.3.5 vs 2.3.3, so that confused Vista.
Click to expand...
Click to collapse
Yesterday I stayed long at work so I didn't try anything. Congratulations for success with AAHK2.
If you install kitkat or any other custom rom, before installing you have to do a factory reset from recovery mode, flash new rom, flash boot.img via fastboot: fastboot flash boot boot.img, after that go to recovery mode: factory reset, wipe all cach, wipe dalvik, and everything you can wipe, and reboot.
After that it should work fine. But take in consideration that in all that custom rom always something don't work.
For first testing I suggest that you install stock rooted rom from this thread:
http://forum.xda-developers.com/showthread.php?t=1382235
And in the first post you have as well radio partition. Flash it necessarily.
P.S.: With stock rooted rom, you will not lose S-off, CWM, etc...

Blu Advance 4.0 L A010U ROMs

Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance

I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!

Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.

Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.

Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.

I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?

Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!

Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.

I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method

well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.

What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.

Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.

Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..

Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.

links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy

SOLVED [HELP] LG G4 (H815P) Bricked "Authentication Fail #9"

Hello everyone
So, this is my problem here, I got my G4 last week, rooted it to debloat, followed the instructions I found here on XDA, and it was working as a charm.
The problem came when I wanted to change the (micro) SD card to another phone, I took the back cover off, took out the SD card, and a warning message about the SD card might be damaged came on screen.
So I turned off the G4, after I was ready to put back the SD, tried to power on the phone again and the error message appeared.
"Security Error, Auth Fail #9" and then it just won't boot.
Hope anyone can help me.
I was on stock Telcel Firmware, had rebooted the phone several times before with no issues so far.

Never mind, I just reflashed stock firmware found
here: http://devtester.ro/projects/lg-firmwares/
then followed this steps
Tutorial: http://devtester.ro/projects/lg-firmwares/install.php
So, after a clean flash, it booted again, as Iv'e had it for just one week, nothing was lost.
Hope this helps anyone else facing this strange problem.
By the way, if anyone know something about the possible cause for this malfunction, I woud really appreciate you sharing info.
Cheers!

i Have had the same problem i was woundering if you could please walk me through the steps on how you fixed yours.
I recently just bought a new LG G Stylo with MetroPCS. this is my first time being with android so i took it upon my self to root the phone and see what all i could do with it. Everything worked fine for a couple of days then i tried to reset my phone and when it tried to come back on the lg logo cane up and it said Authentication fail #9. I try to factory reset the phone but it goes back to the same screen. I can not put the phone in download mode and my computer does not detect that there is a phone there. If there is anyone who can help me please it will be greatly appreciated.

joyousfrank said:
Never mind, I just reflashed stock firmware found
here: http://devtester.ro/projects/lg-firmwares/
then followed this steps
Tutorial: http://devtester.ro/projects/lg-firmwares/install.php
So, after a clean flash, it booted again, as Iv'e had it for just one week, nothing was lost.
Hope this helps anyone else facing this strange problem.
By the way, if anyone know something about the possible cause for this malfunction, I woud really appreciate you sharing info.
Cheers!
Click to expand...
Click to collapse
How can be LG G4 H815P be rooted, have read many tutorials, but no one is for the variant "P" (Telcel).
Thanks!!!

Hello!
Well, I found out the source of the problem on "error 9".
As it happened again a couple days after posting the thread.
In my case, when I uninstalled LG apps, such as music and video apks, "error 9" would come up on next boot.
Follow the tutorials, the most important thing is to have the right version of SW to your phone.
Also, I had to download LG bridge, then a pop-up came telling that drivers for the phone should be updated, I just accepted the update and then my phone was detected on my PC .
If you encounter a problem, please provide me a little more info (with caps if possible).
Hope to help you.
Enviado desde mi LG-H815P

@joyousfrank. I've just been de-bloating my phone and managed to get a Security Error problem and was hoping to use this method to get the thing live again. Trouble is that Google is blocking the LGFlashtool download link. Any chance you have another link or could maybe upload a copy of the tool somewhere? Cheers

joyousfrank said:
Hello!
Well, I found out the source of the problem on "error 9".
As it happened again a couple days after posting the thread.
In my case, when I uninstalled LG apps, such as music and video apks, "error 9" would come up on next boot.
Follow the tutorials, the most important thing is to have the right version of SW to your phone.
Enviado desde mi LG-H815P
Click to expand...
Click to collapse
Hi, my version of the G4 is H815P too (CLARO BR), and I want to know wich tutorials you're referring to and if you encounter a method to surpass this issue when trying to remove/debloat the phone...

wadken1 said:
@joyousfrank. I've just been de-bloating my phone and managed to get a Security Error problem and was hoping to use this method to get the thing live again. Trouble is that Google is blocking the LGFlashtool download link. Any chance you have another link or could maybe upload a copy of the tool somewhere? Cheers
Click to expand...
Click to collapse
Sorry I couldn't help you, but it's great to know that you have solved your problem.

depechemodem said:
How can be LG G4 H815P be rooted, have read many tutorials, but no one is for the variant "P" (Telcel).
Thanks!!!
Click to expand...
Click to collapse
I used this thread as a guide
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
(Follow the steps for International H815 10c Version)
This is the rooted image I used http://forum.xda-developers.com/g4/...on-root-lg-t3164765/post62251256#post62251256
After you download it just unzip it, and rename the .img file to "system.rooted.H81510c-EU"
The file must be system.rooted.H81510c-EU.img
Hope to help.
Cheers!

hralm said:
Hi, my version of the G4 is H815P too (CLARO BR), and I want to know wich tutorials you're referring to and if you encounter a method to surpass this issue when trying to remove/debloat the phone...
Click to expand...
Click to collapse
Hello!
The first thing to do, is to find the right SW foy your phone model (and carrier) as I read some problems when flashing other different than stock.
Look up here http://devtester.ro/projects/lg-firmwares/download.php there's where I found the SW for Telcel. Just input your IMEI on that page and it will give you a download link.
Then, follow this steps http://devtester.ro/projects/lg-firmwares/install.php
It's important to tell you that my phone wasn't detected by my PC until I downloaded LG Bridge as it comes with the latest drivers, so I recommend you to do this if you face the "not-detecting phone PC".
And for last, I suppose that there should be thread with a list of safe to uninstall apps (this is my first LG so not totally sure).
As there's enough room for apps on the phone, I just ended freezing annoying apps with Link2SD to avoid having the "Authentcation Error #9" problem.
Hope to help you, cheers!

FLASHGOTHOPS said:
i Have had the same problem i was woundering if you could please walk me through the steps on how you fixed yours.
I recently just bought a new LG G Stylo with MetroPCS. this is my first time being with android so i took it upon my self to root the phone and see what all i could do with it. Everything worked fine for a couple of days then i tried to reset my phone and when it tried to come back on the lg logo cane up and it said Authentication fail #9. I try to factory reset the phone but it goes back to the same screen. I can not put the phone in download mode and my computer does not detect that there is a phone there. If there is anyone who can help me please it will be greatly appreciated.
Click to expand...
Click to collapse
Hope it's not too late.
The first thing to do, is to find the right SW foy your phone model (and carrier) as I read some problems when flashing other different than stock. (This is important as I've only done this with G4, so you're going to do the search for the right SW)
You can look up here http://devtester.ro/projects/lg-firmwares/download.php there's where I found the SW for H815P (Telcel). Just input your IMEI on that page and hopely it will give you a download link.
Then, follow this steps http://devtester.ro/projects/lg-firmwares/install.php
It's important to tell you that my phone wasn't detected by my PC until I downloaded LG Bridge as it comes with the latest drivers, so I recommend you to do this if you face the "not-detecting phone PC".
Cheers!

Phone stuck in "Download mode" after official Pie OTA update!

Hey good people.
Yesterday i was excited to see the notification for Pie update come up, so i quickly installed it on the phone. It finished, then asked me to reboot, so i did. But for some reason, the phone couldn't reboot properly, and ended up getting stuck in download mode.
Tried to get out of it using every combination, nothing worked. Then i decided, well, lets reinstall the firmware on it. If i could find any! Majority of links are misleading, don't work, yandex disk links didnt let me download anything. Tried like 3 different versions of OST, none of them worked, not even the patched one, not to mention the lack of firmware in the first place.
The only step forward i could make is getting the phone to show up in device manager, because it hasnt even showed up before.
i've never even fiddled with the device's software or anything, everything was 100% stock and untouched.
i'm seriously disappointed in nokia, already contacted the reseller who yet has to reply (i don't have much hope for that either).
Any kinda help would be highly appreciated.

gabika1941 said:
Hey good people.
Yesterday i was excited to see the notification for Pie update come up, so i quickly installed it on the phone. It finished, then asked me to reboot, so i did. But for some reason, the phone couldn't reboot properly, and ended up getting stuck in download mode.
Tried to get out of it using every combination, nothing worked. Then i decided, well, lets reinstall the firmware on it. If i could find any! Majority of links are misleading, don't work, yandex disk links didnt let me download anything. Tried like 3 different versions of OST, none of them worked, not even the patched one, not to mention the lack of firmware in the first place.
The only step forward i could make is getting the phone to show up in device manager, because it hasnt even showed up before.
i've never even fiddled with the device's software or anything, everything was 100% stock and untouched.
i'm seriously disappointed in nokia, already contacted the reseller who yet has to reply (i don't have much hope for that either).
Any kinda help would be highly appreciated.
Click to expand...
Click to collapse
Which type and do You have a screenshot from the startscreen.

Maybe this helps

Part 2

EricH7001 said:
Which type and do You have a screenshot from the startscreen.
Click to expand...
Click to collapse
i honestly have no idea about the type, but i have screenshot

actually, no matter what i pressed in what order or battery percentage, it just said "download mode", and i also couldnt even turn the phone off either.
tbh i've contacted the reseller since then, and we'll probably just send it back in the next few days

gabika1941 said:
i honestly have no idea about the type, but i have screenshot
Click to expand...
Click to collapse
Don't you have the retail box? The type should be written on it. Also, do you have the ZEISS logo on the camera? If not, then you most likely have the TA-1054 variant, which is for the Chinese market.

intervall said:
Don't you have the retail box? The type should be written on it. Also, do you have the ZEISS logo on the camera? If not, then you most likely have the TA-1054 variant, which is for the Chinese market.
Click to expand...
Click to collapse
it must be the Chinese then, because it doesn't have Zeiss or android one logo on it.
But actually, is that very significant?

gabika1941 said:
it must be the Chinese then, because it doesn't have Zeiss or android one logo on it.
But actually, is that very significant?
Click to expand...
Click to collapse
Well, I cannot be 100% sure. But I would assume that if your phone was running a ported version of the global ROM and not the official Chinese firmware and it somehow got an OTA update then because of the differences in how the phone's memory is partitioned it would make sense that the device ends up being bricked after trying to flash something not ment to be flashed on it. :/ I hope this makes some sense to you. Also, if I am correct then it makes no sense to blame HMD for this because they have not done anything wrong. It is most likely the reseller who reflashed your TA-1054 with a ported version of the global ROM.

intervall said:
Well, I cannot be 100% sure. But I would assume that if your phone was running a ported version of the global ROM and not the official Chinese firmware and it somehow got an OTA update then because of the differences in how the phone's memory is partitioned it would make sense that the device ends up being bricked after trying to flash something not ment to be flashed on it. :/ I hope this makes some sense to you. Also, if I am correct then it makes no sense to blame HMD for this because they have not done anything wrong. It is most likely the reseller who reflashed your TA-1054 with a ported version of the global ROM.
Click to expand...
Click to collapse
i've legit thought about that! the box itself has lots of chinese on it, so it might be the case. Either way, reseller responded and i'll probably just sent it back to them this week because apparently it's their fault.
strangely, my mi a1 didnt even let the OTA install when i had the bootloader unlocked, so it's weird to see a phone getting bricked like this. I actually felt guilty for letting the OTA install, even though i didn't do anything wrong here (exceptionally:laugh
Thanks for the suggestions m8!

I think You bought a crappy Chinese dummy Nokia 6.1 HMD is not in Finland hands anymore.
The hardware is different. And the software is Android one.
I am curious how your reseller solves the problem.

can anyone tell how can help to exit from download mode. i have tried by connecting charger and holding pwr button and vol up and after andriod logo came i released by pwr button and holding the vol up button. its not worked
later i connected to my pc and install adb driver and fastboot and then through cmd prompt i run adb bootloader but its not working then i check adb devices but there is nothing shows in attched devices and also i tried with fastboot reload then mobie restarts and came back to dowload mode. so out of these step can anyone have any suggestions to get back my mobile..thank you

ok so, i kinda neglected the thread but heres what happened:
i tried EDL mode with deep flash cable, didnt work. i tried installing all sorts of drivers on my PC from all sorts of sketchy sites, after a point i decided not to mess my PC or the phone up even more.
i contacted my reseller who "fixed" the phone by installing the pie update on it somehow, and it's functional now. i even told them the phone wasn't the european version but they didn't seem to care, and i didn't feel like playing with them anymore. but it's FAR from stable, buggy as hell, and LTE B20 doesn't work either (that might have a thing or 2 to do with the phone being chinese...)
thanks for all of u for helping, this particular phone was way more than enough reason for me not to buy a nokia again ))))