Dear all,
and thanks in advance to anyone willing to spend some time to help me.
It all started few days ago when I turned off my LG L9 (updated to the last version available for my brand (Italy - TIM), I believe it was Jelly Bean V20C).
When I turned on the phone again, it was stuck on the lg logo.
Then I started to read this forum, and the first thing I tried was the HARD RESET. After that, a sadly image of the android robot with a red triangle lying upon its body appeared.
This image now shows up every time I boot my phone, just after the LG logo.
Then I tried:
- recovery from LG Mobile Support Tool
- followed this guide: [GUIDE] [UNBRICK][ROOT] FLASH Any LG Factory ROM (kdz) WITH OFFLINE FIX
- tried KDZ update tool alone (3GQCT in combination with all modes: DIAG, EMERGENCY, CS_EMERGENCY).
In order to use the Offline fix guide, I run fastboot with option number 2, to upload ICS x-loader and u-boot, otherwise the phone was not recognized by the tool (_IsConnectedPhone(0)).
But in all cases of kdz update, the phone reboots at exactly 90% of the process and after the initial LG logo the red triangle is back again .
Harder reset won't work either after the update.
I tried Italian firmware V10A_00, V10B_00, V10C_00, V20C_00, but none of them works.
I noticed that after the update to an ICS firmware, when I try the hard reset procedure, I can see the android recovery image just one frame before the red triangle appears.
I also tried to install a CWM recovery, but without the bootloader unlocked I got a "security error", that went away with a kdz update.
I searched this forum and I think I can't unlock the bootloader with a bricked phone, am I right?
I plan to make a last recovery with the LG Mobile Support Tool and send it to warranty, so that no trace of fastboot manipulations should be visible (right?).
I have read a lot of threads on this forum (and others) before posting here.
If you know of anything I can try, please let me know.
Thank you!
Absolutely the same...
I have this problem, too. Did you find how to fix it?
What happens during the recovery with the LG tool? I am sure I read about stopping at 90% and a solution somewhere here... search for it, I dont have the time, sorry...
Sent from my LG-P760 using xda app-developers app
i have the same issue .
at 90% phone reboots and red triangle dead android appears .
i think its a problem with the drivers . tried this on win 8.1 , 7 and xp on 2 different computers . same results .
i got the same with lg recovery and offline kdz method .
would be very nice to find a fix
I brought the phone to the warranty office. They substituted the "pcb main" so I believe it was an hardware problem.
Hello,
I got the same problem. Using the same methods and got no positive results.
Does someone solve this?
hello my friends. have any of you solved this problem?
i did exactly what op did, and no results.
I never had a red triangle issue. This probably neans that the bootloader is kocked AND encrypted. In the beginning this was the case with the US T-Mobile variant, and seemingly for all L9s from the final oroduction run. For other phones you needed to flash a certain stock rom, v10a or the first couple of v20s, then unlock the bootloader.
You should try using the CSE Flash mode from LG Flash Tool 2014.
I have the same problem, the difference is when i try to flash kdz it gives me error at 50%. I tried all the methods that op does but no succes. I also tried flashing img's manually from fastboot, i tried cwm and twrp as recovery.img and even extracted original kdz to img's and flash every partition manually. The system.img is the main problem cause you can't flash such huge file (1gb) through fastboot. Maybe someone have some idea is there any way to unbrick my phone? Bootloader is locked, and device had no root before brick.
Hey Guys,
I tried to root my Samsung S4 GT-I9502 (OS Android 4.3), for that I found this website:
http://marrkdaviid.com/2013/08/fix-caller-id-install-google-play-on-the-galaxy-s4-i9502/
But it failed (more information below) and I had the following error message and no wifi.
I am able to put the device into download mode, though I keep getting this error message when I try flashing the device in Odin.
(here someone with a similar problem: http://androidforums.com/international-galaxy-s4-all-things-root/768632-sos-cannot-open-gt-i9502-after-failed-boot.html)
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I live in China and I just bought the phone, I needed 5 days to download the necessary files, because most download pages are blocked in China. So I am loosing my last nerve right now.
I am pretty confident that I have the correct Samsung drivers installed. I don’t have Samsung Kies installed. I have even tried using a different computer (Laptops), and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUCMG2_I9502CHUCMG2_I9502ZNUCMG2_HOME.tar.md5
I9502ZNUEMK3_I9502CHUEMK3_I9502ZNUEMK3_SVA.tar.md5
Someone with a the same problem tried the 'Firmware upgrade and initialization' option in Samsung Kies, but it didn’t work, so I didn’t try. (Here the link: http://forum.xda-developers.com/showthread.php?t=2382979)
Instead I tried a recovery. I used Odin 3.07 and the following file:
i9502-cwm-recovery.tar.md5
I got my phone back to work for a while, I reset the phone, just in case. But know I can’t switch the Wifi on and the phone wants to Reboot.
So I allowed the phone to Reboot, I clicked on “reboot system now” and then on “Yes – (I forgot what was written behind the Yes, but I didn’t just click on the normal Yes, I clicked on the Yes - …)
The problem here: The Phone changed to a China Unicom Screen and stayed like that. After 5 h I took the battery out, but I couldn’t restart the phone.
So I did an cwm recovery and know I am afraid to reboot. The Wifi is not working and I can’t find any information about how to fix it.
So please help me. Do I reboot? Can I already install SVA ROM, although I couldn’t flash the Stock Firmware? Do I send the phone back and give up?
Please let me know if you need any other information to be able to help me.
PS: This is the first time that I flash a smart phone. And although I already spent several days now, searching the internet for how-to-dos, tips & tricks, guidelines, Q&As and god knows what, I still do not fully understand what exactly I am doing here. Hence, I would be very happy to receive somewhat easy understandable answers.
Thank you so much for your help!
Anna
Hello!
I'm a newbie and I really need help with my bricked(?) phone. First a short intro to how the problem came to be:
I own an old (but I still love it) and extremely rare phone, the original Samsung Galaxy Beam (I8520).
There is no official update for it, so it is stuck on Android 2.1.
The thing I miss is Netflix, and Netflix officially only supports 2.2+, so I thought I could try to fool Netflix into running anyway by editing puild.prop.
But to be safe, I used an app called Device Spoofer. In this I could try different model infos by selecting different phones in a list.
I tried a couple and found one it would except. Then it required a reboot, I believe, and now my phone won't start up.
I get to the Samsung logo and then a Starhub carrier logo, as usual, and then the phone just turns black.
There is supposed to be a way to get into download mode by holding some buttons, but that doesn't work on my phone. I have read something about it being a bug on some Samsung models. But anyway, I have bought one of those usb sticks that puts the phone into download mode, and it works.
I have tried to use ADB, but it doesn't seem to find my phone. I also tried to flash a firmware to the phone, but that doesn't work either, Odin gets stuck at "SetupConnection..". The only firmware I have found online is one called I8520STHJI1.tar, which is the last firmware version made for the phone and the version that is factory installed on my phone.
The I8520STHJI1.tar contains the following files:
cache.rfs
modem.bin
ramdisk.img
SS_DL.dll
system.rfs
userdata.rfs
zImage.img
Is there anything that can be done?
Thank you!
After googling, it seems that I need a certain version Odin to be able to flash the i8520.
What I need is Multi Downloader v.1.7.3L
Does anybody have that?
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
edit: correction, not clickbait, but need to signup
vincom said:
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
Click to expand...
Click to collapse
Yeah i saw your post a couple of days ago and it is legit , about the file hosting it's not clickbait it's just 4shared and this little guy is older than the xda :laugh::laugh: , i agree that the androidfilehost is faster and more convenient but i'm not the uploader , i just copied it from another source, it would be great if you re-upload it for others and i will update the link.
Now we come to testing: i tested this myself and it is 6.0.1 for sure but i don't remember which release it was cause i updated to 7.1.1 20.32.67.25 release for various reasons, mainly for battery life (spoiler: not much difference and it's still poor) and i will keep flashing / debloating apparently in (in search of incredible) but i'm quite sure this phone is hopeless without a custom ROM from scratch as the amount of services and wakelocks are enormous.
Why don't you participate and use your knowledge in the "allegedly upcoming" Lineage 15.1 hopefully we get a working build before the end of the year :cyclops: i'm sure you are aware of the situation.
And if you're into kernels then kernelwise this phone's kernel was made by noobs ,ASUS put an AMOLED display and they are not using it's features as the blacks are lit and power consumption by the screen is well above an LCD one of the same size.
Long story short buying this phone was/is a mistake.
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
vincom said:
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
Click to expand...
Click to collapse
All you need is one fw to start with and after that you can update to whichever release you want without any problem , strait forward from asus site and update via sd card even if it's rooted or bootloader unlocked, you can do anything and even get updates as FOTA app works as soon as you boot cause asus update procedure is very primitive HOWEVER it should be on stock recovery and honestly twrp is pretty much useless here and i didn't seem to need it in anything with this device!! (i use magisk to root), it's not like there's half a dozen of custom ROMs to flashed , the only possible modification is within the stock fw and that's our limit.
If you find a screen replacement under 50$ it is worth it , i knew that 2.5D glass is poor engineering and very fragile, so screen protector and case was crucial since day 1.
Notes:
Don't trust asus download center's description cause i downloaded the latest nougat release before the Oreo (as described in their section) and it turned out to be the first release of their lousy O fw.
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
the only one i can't get adb enabled so i can mirror the screen is the mm 11.40.86.71, the same one you have linked here
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
vincom said:
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
Click to expand...
Click to collapse
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
sam.fisher190 said:
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
Click to expand...
Click to collapse
not impossible, very doable to use a phone even with a dead screen.
after alot of trials and error ...from a new flashed stock thats was completely wiped, i can get to a remotely controlled/viewed phone in about 10mins .
i will write up a tut on that.
i can get that done with all the availabe working raw fw except with the mm 2017/04 release
yes, i have a completely dead screen, no display, no touch. all other phone functions work.
the reason for stock recovery procedure was to update to oreo, but i really dont care if i get it. just seeing if its doable.
playing with it for giggles, going to be a security camera as the cam is vg, useless as a phone that has no working screen.
i can be the sacrificial tester if need be, pretty hard to hardbrick this phone as i also have the back cover off so to disconnect the battery connector for those hard soft brick occasions and/or to make sure phone was completely off b4 doing something
I think I killed my phone please help Asus ze553kl
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Nikido2930 said:
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Click to expand...
Click to collapse
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
vincom said:
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
Click to expand...
Click to collapse
sam.fisher190 said:
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
Click to expand...
Click to collapse
THREAD CLOSED and download link removed. 4shared.com requires to have an account for downloading i.e. not accepted as file host on XDA.
Please advise the moderators' team when ready to provide a download link from an accepted file host.