Database Users

[q] problems with lg gt540

hi guys.. could you help me with my problem.!
I have an LG GT540 android 1.6 firmware version(stock)
So here are my problems:
1. I tried to upgrade it from 1.6 to 2.1 using this tutorial http://forum.xda-developers.com/show...27&postcount=3 thanks to lavero.burgos for posting it, I was successful at first part, but I cant follow the next because my device wont go to fast boot,, I tried putting it off, then camera+poweron but it doesnt do anything. It doesn't light, no lg logo appears, just nothing although the computer can read the drive when I connect it through usb. So I cannot flash it to 2.3,2.3 because it just wont go to fastboot.
2. When I turn it on normally, It takes long before it response like after 30sec to light, but just light, no lg logo appears although it wasnt bricked because I can use it normally after just waiting to on.(annoying)
3. Since I upgraded it to 2.1, I lost all 3rd party application and the internal apps were the only left, so I copied all my saved apps (.apk) to my sd card but the problem is there is no saved app on my phone to read and install those apps from my sd card.(irritating)
4. My device wont read my sim card, when I start it it says "sim card unprovisioned" so basically I cant connect to mobile networks here in the philippines(im using globe telecom). I feel that Im stucked in the middle of nowhere since I cannot contact and txt all my family and friends.
5. I cant connect to wifi,, when my device detects wi-fi, I try to connect to it but from the log it only try to connect but doesn't obtain the ip address. Even when the wi-fi signal is strong, it does the same thing.
So please help me guys,,I want to hear from my fellow xda-developers badly,,,
PS. also those who have problems with their LG GT540 pls feel free to post and share it with us here... thank you all guys in advance....

hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Step one!
1.turn off phone.
2.hold the POWER button till you feel the beep.
3.let go of the POWER button when you feel the beep and hold onto the CAMERA button only.
4.hopefully it turns on to a blackscreen and nothing else(fastboot)
5.unzip this CLICK ME!! to desktop and open the flash all no wipe file
or......
1.turn on your phone.
2.go to settings>applications>development>tick the usb debugging
3.connect phone to computer (make sure phone is on)
4.unzip this CLICK ME!! to desktop and open the flash all no wipe file
5. phone should boot into blackscreen like the one above......
Click to expand...
Click to collapse
Step 2!
both should flash a recovery image. Next
1.make sure the phone is off
2.press POWER button
3.when you feel the beep let go of POWER button and press the HOME button only.
4.phone should boot into recovery mode.
5.take out battery again
6. download a rom into the sdcard using computer
7.go to recovery again using the steps above (steps 1 to 4)
8.select wipe all data factory reset or something like that....
9.install zip from sdcard
10.select from sdcard
11.choose the file you downloaded
12.finish flash and reboot phone.
Click to expand...
Click to collapse

excellent guide! big thanx

bs828 said:
hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Click to expand...
Click to collapse
Thanks,, Ive tried the 2nd option on step one and i think my phone successfully got to fastboot(just clean blank screen) so the cmd automatically run and states
C:\Desktop\adb rebootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: protocol fault <no status>
C:\Desktop\fastboot flash recovery recovery.img
< waiting for device >
Did I miss something???

ok try again this time with the phone turned on. and then run the script and did you install the drivers?

bs828 said:
ok try again this time with the phone turned on. and then run the script and did you install the drivers?
Click to expand...
Click to collapse
yeah I installed the drivers...

hmmm maybe there are no fastboot drivers(main suspect....) there are a few ways to get it but for mine i just plug my phone in to my pc (windows 7 64bit) it just recognize it and tries to get the "google fastboot interface" drivers from windows update...

Try Volume Up+Search Key+Power to go into Fast boot Mode, There's different keys to activate Fastboot Mode (There is different versions of Fastboot)
Sent from my LG GT540 CM9 PreRC Polish Blood using xda premium

Your phone is/was bricked
Hey, I'm sorry to bing back such an old thread, but I just wanted to say this for posterity: your phone has/had a soft-brick. This means: you can't see Android nor LG boot logos, can't enter Recovery and (maybe) can't access Fastboot, but I'm not too sure on that last one. Besides that, the phone works "okay", but you should try to fix it.
Basically this soft-brick is almost always caught when upgrading from 1.6 to 2.1, so everyone should have it, including me. It took me a whole year to realize how to friggin' fix it lol, but here goes what I did:
Thanks for your help everyone, I came to a solution after a full year lol. Here's my enlightenment, from another Thread:
------------------------------------------------------------------------------------------
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
--------------------------------------------------------------------------------------
Also, if you look in here you'll find how to flash an awesome ROM, Cyanogen Mod 10 (should say "Final Version#2).

Bootloader showing just a black screen

I have three Shield TV boxes (all stock-rom 2.1) and tried to flash the new Vulkan Update 3.0. I was successful on two of them by doing the follwwing steps:
1. Connected via USB to PC
2. Activated Developer-Mode and then ADB (actually I had that done long time before)
3. Booted into Bootloader using ADB-command
4. Unlocked Bootloader using Fastboot-command (all apps and date wiped out)
5. Reboot (after that had to setup Shield TV and repeat steps 1 and 2)
5. Booted again into Bootloader
6. Flashed TWRP-image using Fastboot-command
7. Reboot
8. Booted again into Bootloader
9. Selected "Boot recovery kernel" (= TWRP)
10. Installed Vulkan 3.0 Update Image via TWRP (Zip-File)
11. Reboot
Done.
It worked perfectly fine on two of my shield TV boxes. But I have problems with the third one: Everytime I enter bootloader I do not have any video. The screen is totally blank (black screen). I can use Fastboot-commands from my PC though (e.g. unlocking Bootloader and flashing TWRP seems to work since the output on the PC tells me so). But since I absolutely do not see anything I cannot enter TWRP and use it for flashing the Vulkan Update 3.0 then. Even more: Not being able to enter (or at least "see" anything in) bootloader and TWRP will make it hard to administrate the box in the future.
I meanwhile tried three different displays - no difference. I also tried factory restore and flashing the older dev-images of 2.1, 2.0 - and even 1.3 and 1.4. I was hoping these images would somehow repair the bootloader (since I suspect it is broken, showing no screen). But they obviouly did not. Bootloader stayed black every time I entered it anyway what firmware I was using. Funny thing is that booting into Android TV itself just works fine all the time. I have the NVidia logo, the start animation and - of course - the Launcher screen with all apps. So I can use the shield box. Just the bootloader seems to show nothing (it is responding to fastboot-commands, but only shows blank screen). Therefore I cannot upgrade to Vulkan 3.0 or do any administrative things that require to "see" the bootloader or TWRP .
Any ideas how to repair it?
Thanks in advance for any help!

Ok, after some trying I was able to boot into stock recovery mode: I connected the Shield TV box via USB with my PC and at the DOS prompt I entered "adb reboot recovery". When I saw the Android-Symbol I pressed the power button on the Shield TV box for 2 seconds and then entered the recovery menu. I then selected ADB sideloading and on my PC I typed "adb sideload name.zip" (whereas "name.zip" was the name of the Vulkan-3.0-Image-ZIP-File). Then flashing went well. Now I am on 3.0 and I can begin setting up all apps again.
However, I once again tried entering the bootloader menu but it still just shows a blank screen. So that is still broken. Does anybody know how I could get the bootloader to display anything again?
Regards,
FantasticN

Something new, strange...
Izsūtīts no manas Nokia 3310 используя бесплатную xda app

You could try flashing the weird box with the factory images ( https://developer.nvidia.com/shield-open-source ), maybe it's somehow on an older bootloader that has a bug, or it's partially corrupted. You don't need to see anything in fastboot to flash the factory images. Heads up, they will wipe your device (unless you remove the -w switch from the batch file that initiates the flashing process).

Solution: 50% when unlocking bootloader

EDIT: SOLUTION (Not a fix)
For those who are stuck at "50% saying current account is different from the a/c info of device"
It is due to the database miss-match in their server ,the possible sollution are :
Remember: for MediaTek devices you will have to first flash a China Dev ROM onlu then you can get the unlock successful.
But this is not a recommendation for Qualcomm Devices.
1. Go to i.mi.com and look weather your device shows up in the find device (this is required only to be sure as to your device is connected to their server and they have updated the info on your Device too).
2. Reset your Phone sign in and turn on find device. turn on usb debug and oem unlock connect to pc allow whatever is asked on your phone also check always trust, then open adb folder and open cmd there and type adb devices your phone will ask for authorisation allow it and check always trust.
3. Mail your concern with user ID and also the snapshot of the error as they will ask for it,to your regional service (I am an indian so i had to mail it at [email protected])(just google contact xiaomi) wait for their reply.
You can PM these persons on MIUI forum regarding the 50% stuck issue.
{ EDIT 2:
You may contact these person in MIUI forum:
1) vincent_khoo
2) PatrickXi
( @bravonova gave me these names you may try I haven't cross checked as mailing will most probably solve) }
The last method should Work for everyone as it's a db miss-match which should be fixed after this.
PS: This a solution and not a fix so it will take time.
PPS: Don't blame me for all the trouble Blame Xiaomi.

ilvmyname said:
Ok, so I have been trying to move to miui 8 global beta version now for a long time and haven't succeeded, the updater app says could not verify update package.
I have a pretty good net connection so that's not an issue.
Also If I try download latest rom it says "Can't download update, wait a minute or two" and this it has been saying for about a week now (ironic).
So, I requested for unlocking the bootloader got the confirmation messages after 3 days tried to unlock now stuck at 50% saying "account is different from the account in the phone info"
I don't want to use the fast boot edl method of flashing rom as my lappy keeps getting sudden shutdown, so I don't want it to shutdown in between and get hard bricked.
I have tried MiPc suit but since it cannot do a backup(again app bug) so cannot flash through it.
I have looked in to the mi cloud and my phone does gets located.(possible solution given for unlock bootloader but even that didn't work).
Can anyone please help me on this or will I have to be on this ****ty unrooted Rom forever.
Currently on miui 7.5.3.0 global stable rom.
Any suggestions will be appreciated ty
Click to expand...
Click to collapse
I unlocked it just today!make sure all drivers are installed..boot into fastboot mode :- power off then hold vol down + power button.w8 for the drivers to get installed
Now boot into recovery mode :- turn off device and hold volume up + power button.w8 for the drivers to get installed.
I was stuck at the same 50% error..one of d xda member told me to boot into recovery mode and let the drivers get installed and taddaa...bootloader unlocked
Make sure u r logged in to the same account in ur phone u r using to unlock the bootloader

I fixed this by updating to latest version in miui app in fastboot mode.

Same problem for me. I tried using the MIUI PC Suite, it tells me my phone isnt up to date even though it is. Recovery mode drivers fail. Requested unlock over 2 weeks ago and got the SMS 9 day ago... still stuck at 50% error. Its driving me nuts.

Warrimonk said:
Same problem for me. I tried using the MIUI PC Suite, it tells me my phone isnt up to date even though it is. Recovery mode drivers fail. Requested unlock over 2 weeks ago and got the SMS 9 day ago... still stuck at 50% error. Its driving me nuts.
Click to expand...
Click to collapse
i today unlocked my bootloader...try doing this go into recovery mode by pressing power+volumeup button. You will see a picture telling you to connect ur phone to pc using usb cable..connect your phone to your pc now w8 and let the drivers get installed and try again..i did dis and unlocked it today before that i was getting the same error even today got the same error before doing this.

hitesh1792 said:
i today unlocked my bootloader...try doing this go into recovery mode by pressing power+volumeup button. You will see a picture telling you to connect ur phone to pc using usb cable..connect your phone to your pc now w8 and let the drivers get installed and try again..i did dis and unlocked it today before that i was getting the same error even today got the same error before doing this.
Click to expand...
Click to collapse
First of all thanks for the reply sir but
I tried entering to recovery mode and then connect to pc but nothing happens, I mean it does not show connected even after say 5 minutes.
Although when trying to enter into the fastboot mode and then connecting to pc the drivers do get install and it shows connected and stucks at 50%
I do have adb drivers RN3 USB drivers installed on my pc
But all things in vain.

Garyj881 said:
I fixed this by updating to latest version in miui app in fastboot mode.
Click to expand...
Click to collapse
I am sorry sir but I didn't get you, you updated to latest version of miui through the updater app right? And then entered to fastboot mode to unlock right?
My updater app also doesn't work It says cannot verify update package and so I am stuck like from all corners.

ilvmyname said:
First of all thanks for the reply sir but
I tried entering to recovery mode and then connect to pc but nothing happens, I mean it does not show connected even after say 5 minutes.
Although when trying to enter into the fastboot mode and then connecting to pc the drivers do get install and it shows connected and stucks at 50%
I do have adb drivers RN3 USB drivers installed on my pc
But all things in vain.
Click to expand...
Click to collapse
Are you able to see this pic on your device when you enter recovery mode??

hitesh1792 said:
Are you able to see this pic on your device when you enter recovery mode??
Click to expand...
Click to collapse
Yes

ilvmyname said:
Yes
Click to expand...
Click to collapse
connect your device to your pc and let the drivers get installed...and if u are using a desktop pc do not use the usb port which is at the front of the cpu..use the one which are at the back of the cpu...the image i am attaching shows which drivers get installed.
after drivers get installed remove usb cable and again boot into fastboot mode (power + volume down ) and try again to unlock bootloader

hitesh1792 said:
connect your device to your pc and let the drivers get installed...and if u are using a desktop pc do not use the usb port which is at the front of the cpu..use the one which are at the back of the cpu...the image i am attaching shows which drivers get installed.
after drivers get installed remove usb cable and again boot into fastboot mode (power + volume down ) and try again to unlock bootloader
Click to expand...
Click to collapse
Okay, so i am missing drivers i guess.
Have you pre installed any drivers if so can you provide me a link?
as when i connect into recovery mode only the bootloader interface driver get install and nothing else and hence it still doesn't show connected in the recovery mode.

ilvmyname said:
Okay, so i am missing drivers i guess.
Have you pre installed any drivers if so can you provide me a link?
as when i connect into recovery mode only the bootloader interface driver get install and nothing else and hence it still doesn't show connected in the recovery mode.
Click to expand...
Click to collapse
strange!bootloader interface driver gets installed when connected in fastboot mode..uninstall that driver connect your phone in recovery mode and see if dese drivers get installled..nope i do not have any link because as soon as i connected my phone into recovery mode the drivers automatically got installed!
ps :- i was able to unlock bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000.23_5.1_global_f5889c1549

i too have the same problem !! if you got the solution please tell me !!

T/[email protected]$ said:
i too have the same problem !! if you got the solution please tell me !!
Click to expand...
Click to collapse
i was able to unlock the bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549...
i was not able to unlock it before i connected my phone into recovery mode and installed the drivers on my pc..as soon i did it the bootloader got unlocked .before that i was getting the same error even after flashing the V7.3.7.0.LHOMIDD firmware

hitesh1792 said:
i was able to unlock the bootloader after flashing kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549...
i was not able to unlock it before i connected my phone into recovery mode and installed the drivers on my pc..as soon i did it the bootloader got unlocked .before that i was getting the same error even after flashing the V7.3.7.0.LHOMIDD firmware
Click to expand...
Click to collapse
how to flash kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549.?
when i connect my device in recovery mode nothing happens

For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.

T/[email protected]$ said:
how to flash kenzo_global_images_V7.3.7.0.LHOMIDD_20160523.0000 .23_5.1_global_f5889c1549.?
when i connect my device in recovery mode nothing happens
Click to expand...
Click to collapse
it must install the drivers...please do check out the steps mentioned above by the xda member "otyj" he helped me to unlock my bootloader

I had the same problem and believe me I did everything possible as you are also advised in this forum.
But it had nothing to do with this.
Just wait and watch.. try everyday once and I think you will get in 7-10 more days.
I was also frustated at that time but now I can unlock everysingle time I want when it gets locked.

otyg said:
For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.
Click to expand...
Click to collapse
where can i find fastboot images ?
and when i plugin in recovery mode nothing happens !!
and your were telling that app will be installed in phone when we connect wiith mi pc suit, can you clearly explain it ?

otyg said:
For Kenzo / SD / Snapdragon only.
1. Install Mi PC Suite, plug your phone in and install the app on the phone when it prompts (then close mi pc suite) - this provides all the drivers needed for the next step
http://en.miui.com/thread-92720-1-1.html < Mi PC Suite
2. reboot the phone to recovery mode ( Vol UP + Power ), let drivers install on pc - wait, then reboot again to fastboot mode (VOL Down + Power) let drivers install on pc - wait - it might take a few minutes to install the drivers don't unplug the phone during this time.
3. download and install the unlock tool - log into your account, after it checks you have permission press unlock
http://en.miui.com/unlock/ < unlock tool
----------------------------
(if it still fails proceed to next step)
4. use xiao mi flash beta and install the latest kenzo global fast boot image (I have heard some people needed to use the Chinese dev firmware- the global stable worked for me though), use the clean all option selected at the bottom of mi flash. (this will erase ALL data on the phone)- backup before doing this.
http://en.miui.com/thread-281979-1-1.html <- xiao mi flash beta
5. let phone boot up first time, log into the mi account on the phone with your email / password, if your phone number doesn't work then select option to log in with email / password.
6. reboot to fastboot again and press unlock it should proceed now
Do at own risk I am not responsible for bricked devices.
Click to expand...
Click to collapse
Okay I will try flashing a rom through MiFlash toll b'coz the above methods didn't work and will quote if that's how it gets fixed

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.

Did you managed to fix this?

Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!

ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).

Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

S6 lite malfunctioned and now does nothing.

History:
I have a samsung tab S6 lite LTE version. The tablet freezed out of nowhere when I was working and restarted but stuck in bootloader. After a while, and after removing the sd card, the tablet functioned properly. The tablet had more 80% of battery charge.
I thought the new update might fix the issue. I installed the update. it restarted and stuck in bootloader again. Power and Volume Down buttons will restart the tab, but it never went past the bootloop.
Left it for 12 hours without charging, and then the tablet went into recovery mode. I wiped the cache and when figuring out the other options in recovery it switched off and did nothing. When connected to a charger, a circle with lighting icon showed up. No combination of buttons worked.
Took it to the service center, and was told the motherboard needs to be replaced. I knew it was a software problem so I came home without replacing the motherboard.
I put the tablet on charge for a while and pressed volume up and down button and connected it to the computer. The tablet went into download mode. I immediately downloaded Odin and stock firmware and tried to flash only the BL file to the tablet. It failed few times, maybe because of faulty cable. I used another working cable and tried to flash the full firmware and the tablet disconnected again from the pc.
But now the tablet showed "an error occured while updating and use smart switch for emergency recovery". Smart switch on pc did not detect the tablet, but Odin did. The device manager detected the device as samsung mobile usb composite device. I used a new usb cable and flashed the stock firmware using Odin. The process was success but the tablet died.
It does nothing when connected to a charger or pc. No display and no buttons worked.
I opened the tablet by removing the display, and disconnected the battery physically. But nothing happened.
I tried several times to connect to pc, and for once it was detected by the pc.
This time I flashed the stock firmware using odin with nand erase and repartition. extracted the pit from csc file and added it to Odin.
The flash was a success but the tablet remains unresponsive. I checked the display to see if I had cracked or damaged it while opening, but it is good.
Now Sometimes, the tablet gets detected by pc as samsung mobile usb composite device and I could even flash the firmware with success. But the tablet displays nothing and is unresponsive.
Can Anybody advice What I can do now?
PS. I used the correct firmware meant for s6 lite LTE version every time I flashed.

Disconnect devices from PC USB port & uninstall official Samsung USB drivers. Reboot & re-install drivers. Connect to another USB port preferably at the rear PC.
Flashed latest Android 10 instead of the latest Android 11 stock firmware (AP *super.img.tar file ONLY) using Odin (I used official Odin3_v3.14.4) with Auto-Reboot, Nand Erase and Re-Partition. Input *.pit file. Flashing process might take 'years' but be patient until it ended & auto boot up successfully. Try another USB port if it failed. Therafter, flash the rest of stock WITHOUT Nand Erase & ONLY Re-Partition, Auto Reboot & F. Reset Time.
Once it successfully got flashed & auto reboot, wait patiently as it might also take a longer time than normal to boot up. Charge the device to optimal. Done!
Optional (Remove Knox Guard)
Connect to the internet. Login to your Google & Samsung account to update everything & reboot upon further updates. Thereafter, boot to Download Mode & flashed AP (Magisk Patched *boot.img, blank *vbmeta.img & patched *vbmeta_samsung.img) + BL (Blank *vbmeta.img) WITHOUT Nand Erase & Re-Partition. After successful boot up, reboot back to Download Mode & ensure there's no 'KG State' on the list before deleting('root delete' not ADB) Knox Guard or app named Payment Service as in Android 10.

Thanks. I will try.

7GHz said:
Disconnect devices from PC USB port & uninstall official Samsung USB drivers. Reboot & re-install drivers. Connect to another USB port preferably at the rear PC.
Flashed latest Android 10 instead of the latest Android 11 stock firmware (AP *super.img.tar file ONLY) using Odin (I used official Odin3_v3.14.4) with Auto-Reboot, Nand Erase and Re-Partition. Input *.pit file. Flashing process might take 'years' but be patient until it ended & auto boot up successfully. Try another USB port if it failed. Therafter, flash the rest of stock WITHOUT Nand Erase & ONLY Re-Partition, Auto Reboot & F. Reset Time.
Once it successfully got flashed & auto reboot, wait patiently as it might also take a longer time than normal to boot up. Charge the device to optimal. Done!
Optional (Remove Knox Guard)
Connect to the internet. Login to your Google & Samsung account to update everything & reboot upon further updates. Thereafter, boot to Download Mode & flashed AP (Magisk Patched *boot.img, blank *vbmeta.img & patched *vbmeta_samsung.img) + BL (Blank *vbmeta.img) WITHOUT Nand Erase & Re-Partition. After successful boot up, reboot back to Download Mode & ensure there's no 'KG State' on the list before deleting('root delete' not ADB) Knox Guard or app named Payment Service as in Android 10.
Click to expand...
Click to collapse
By chance is it going to work for KG:Locked status device? I'm on F62, i bought this (second hand) few days ago from another city. Tapping on build number doesn't give any response, When i try to flash any firmware I'm getting response "All binaries are not allowed to be flashed" I'm pretty much confused what's happening here

Rolith Rtw said:
By chance is it going to work for KG:Locked status device? I'm on F62, i bought this (second hand) few days ago from another city. Tapping on build number doesn't give any response, When i try to flash any firmware I'm getting response "All binaries are not allowed to be flashed" I'm pretty much confused what's happening here
Click to expand...
Click to collapse
Did you solved it?