How to fix "Page_Error ºÎºÐÀÔ´Ï´Ù" when flashing .KDZ - LG Optimus Black

I have spent all my day on this until I finally came with a solution for those (many, from what I've seen!) facing the following error while trying to flash KDZ images:
Code:
(...)
23:25:50 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
23:25:50 : Page_Error ºÎºÐÀÔ´Ï´Ù
23:25:50 : ¿©±â´Â Retry ºÎºÐÀÔ´Ï´Ù
First of all, just pretend your phone is bricked. Open up the official "LGMobile update" (named "B2CAppSetup") program -- I'm assuming you already have it installed -- then go to Customer Support > Recovery Phone, provide the info it asks you and let it do its job.
This is the same method used to unbrick an Optimus Black, and can be used as well to replace whatever is missing in a stock phone that makes the updater fail. Simple but hidden. Now, just retry the same method you tried before to flash the KDZ on your phone; it should succeed.
Good luck!

Hello I have a LG Optimus 3D Max and your tip does not worked here, the lg app gives an error saying something about phone not supported and directs me to the lg site.
Please help.
Here I have only the LG boot logo and I can enter in "S/W Upgrade .. Please wait while upgrading..." Screen.
What should I do ?
Thanks in advance.

Related

Motorola Razr I doesn't start anymore

Hi,
My phone boots until the Motorola Logo (M in a red point) but doesn't do anything else. And every 5 minutes, it restarts and stops at the same place. No animation, just stops like that, a rock with a red point ...
My phone is a Motorola Razr I, updated with the last version of android, no unlock, no root, 8months old, just a lambda user, never tried to root or unlock ... I did nothing before it crashed, it was in my pocket, no wifi ... it stopped alone and on restart, the Red Point of Motorola of Death is back ...
I can start the fastboot menu, but only "Shutdown" works. "Normal Powerup", "Recovery", "BP Tool" or "Factory" write the same log :
Booting with [...]
Failed to lock fuse, code = 0xa0b23d
Failed to lock fuse, code = 0xa0b23c
Fuse read failed bank = 4 SEP_RETURN = 0xa0b23c
Fuse read failed bank = 4 SEP_RETURN = 0xa0b23c
Click to expand...
Click to collapse
I searched on Xda or with my friend Google, but nothing works because every indicated solution is used with a working recovery mode ...
Did you already meet this kind of problem ? Is it a hard brick ? Can I use my phone like a doorblocker ?
Thanks for your incoming help
LanceOmelette
PS :sorry for my english ... (swiss-french inside ...)
PPS : need more informations ? It will be a pleasure to give them ... if I know how to find it (android noob inside)
PPPS : I hope, I was clear in my description ...
LanceOmelette said:
Hi,
My phone boots until the Motorola Logo (M in a red point) but doesn't do anything else. And every 5 minutes, it restarts and stops at the same place. No animation, just stops like that, a rock with a red point ...
My phone is a Motorola Razr I, updated with the last version of android, no unlock, no root, 8months old, just a lambda user, never tried to root or unlock ... I did nothing before it crashed, it was in my pocket, no wifi ... it stopped alone and on restart, the Red Point of Motorola of Death is back ...
I can start the fastboot menu, but only "Shutdown" works. "Normal Powerup", "Recovery", "BP Tool" or "Factory" write the same log :
I searched on Xda or with my friend Google, but nothing works because every indicated solution is used with a working recovery mode ...
Did you already meet this kind of problem ? Is it a hard brick ? Can I use my phone like a doorblocker ?
Thanks for your incoming help
LanceOmelette
PS :sorry for my english ... (swiss-french inside ...)
PPS : need more informations ? It will be a pleasure to give them ... if I know how to find it (android noob inside)
PPPS : I hope, I was clear in my description ...
Click to expand...
Click to collapse
I would try reflashing the original firmware using Motorola's RSD Lite Flash Tool
if you are still on warranty send it back to the seller
totex71 said:
I would try reflashing the original firmware using Motorola's RSD Lite Flash Tool
Click to expand...
Click to collapse
Thanks Totex.I tried : the log is :
Getvar max-download-size
Downloading ...
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed
Click to expand...
Click to collapse
and in RSD Lite :
Status : Failed flashing process 1/11 flash gpt "gp_signed" -> phone return FAIL
Click to expand...
Click to collapse
mmmmmh I presume it's bad ... very bad ... :crying:
Thanks ICuaI, I keep a small hope to not use this last advice
LanceOmelette said:
Thanks Totex.I tried : the log is :
and in RSD Lite :
mmmmmh I presume it's bad ... very bad ... :crying:
Thanks ICuaI, I keep a small hope to not use this last advice
Click to expand...
Click to collapse
Is there ICS or JB on it? and did you try to flash ics?. if so, try the latest jelly bean firmware
Which firmware did you try to flash? I think you need this one:
http://sbfdownload.droid-developers.org/smi/CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip
It is retail eu jelly bean
via RazR I & Tapatalk 4
Thanks
but no ...
It didn't work ... now, it failed on step 2
Log on phone :
Getvar max-download-size
Downloading ...
Flashing gpt ...
OEM fb_mode_set
Fastboot command failed
Click to expand...
Click to collapse
which version of RSD-Lite do you use? What did you try?
Come on, tell us a little bit more. With "No it does not work" we cannot help you.
Ok ... sorry ... I will try to do my best :
RSD Lite 6.0 / Windows 8 / I presume Jelly Bean was my last version on my phone because I checked 1 day before for any update.
The informations on fastboot flash mode :
AP Fastboot Flash Mode (secure boot)
20.25 (sha - [...])
IFWI Info: 42.26
eMMC Info: Size 8GB
Barcode: [...]
Battery (Okay): 3.5v (temp 29.0)
Connect USB Data Cable
ROM-Key: Motorola-Key
Modem Status: Secure
Click to expand...
Click to collapse
I tried to flash my phone with the firmwire you gave me
Connect my phone on RSDLite with USB, Select the xml file and start the process. That stopped after few seconds on step 2
All others exemples found on Google to rescue my phone used the recovery mode or an other option given by the fastboot mode : the probem is every option in the fastboot mode (except Power Off) crashes my phone. So I didn't do lot of things finally ...
Can I give you more informations ?
LanceOmelette said:
Ok ... sorry ... I will try to do my best :
RSD Lite 6.0 / Windows 8 / I presume Jelly Bean was my last version on my phone because I checked 1 day before for any update.
The informations on fastboot flash mode :
I tried to flash my phone with the firmwire you gave me
Connect my phone on RSDLite with USB, Select the xml file and start the process. That stopped after few seconds on step 2
All others exemples found on Google to rescue my phone used the recovery mode or an other option given by the fastboot mode : the probem is every option in the fastboot mode (except Power Off) crashes my phone. So I didn't do lot of things finally ...
Can I give you more informations ?
Click to expand...
Click to collapse
Here's your problem. You need RSD 6.14. Other versions are too old to recognize the new Moto phones.
tatazeuz said:
Here's your problem. You need RSD 6.14. Other versions are too old to recognize the new Moto phones.
Click to expand...
Click to collapse
I just tried with RSD 6.1.4 and 6.1.5, same error : OEM fb_mode_set / Fastboot command failed.
I will go to my seller this afternoon and try to use my warrant.
Thanks for your help :-/
LanceOmelette said:
I just tried with RSD 6.1.4 and 6.1.5, same error : OEM fb_mode_set / Fastboot command failed.
I will go to my seller this afternoon and try to use my warrant.
Thanks for your help :-/
Click to expand...
Click to collapse
Go to the xml and delete the command that fails, in this case OEM fb_mode_set
It was an idea I found too but I didn't know the utility of this line and I didn't want to have a brocken version ...
But now my phone is in the hand of my seller ... I can only pray to have it as soon as possible ...
Thank you everybody for your help It was a pleasure to ask you a question The answers were fast and understable for me
I will give you the result of the investigation of my seller (2weeks to 1month) if I don't forget ...
LanceOmelette said:
It was an idea I found too but I didn't know the utility of this line and I didn't want to have a brocken version ...
But now my phone is in the hand of my seller ... I can only pray to have it as soon as possible ...
Thank you everybody for your help It was a pleasure to ask you a question The answers were fast and understable for me
I will give you the result of the investigation of my seller (2weeks to 1month) if I don't forget ...
Click to expand...
Click to collapse
I deleted fb_mode and it all flashes like it should. I think it just sets it up on fastboot or smth like that
Sorry for the delay, I'm on a trip around the world and I just received my phone back from the seller. But like I thought : no discussion, no message to give the reason or the solution. My phone is back, they made a big hardreset.
Thank you, everybody for your help. I learn some new things
Bye
Lance

[Q] Soft Brick without Custom Recovery (Logs Included) - LG G Flex T-Mobile (D959)

I've had this phone for a few days and I bricked it by reverting my build.prop from this thread http://forum.xda-developers.com/showpost.php?p=55838361&postcount=2 . It is an unlocked phone T-Mobile D959 on 4.4.2. I was having lots of trouble and crashing apps so I decided to start fresh and replace with this file from the thread. After replacing, it does not allow me to boot. Factory hard reset does not work (since I believe it does not change build.prop). It shows Android mascot for ~10 seconds and then black screen. If I start phone normally the screen will boot LG logo then go to black with front notification light constantly flashing from cyan to green and looping.
I do not have a custom recovery and I can only access "Download Mode." I have tried the KDZ flashing with LG Flash Tool 2014 with LG_KDZ_FW-Update_OfflineFix. I keep getting an error at 2%/3% of the last step depending on the setting (3% on CS_EMERGENCY, 2% on EMERGENCY, 2% on DIAG). I am putting the phone on COM41 and tried both USA/KITKAT KDZ files.
Does anyone know what settings I need for this method?
I have also tried the LG Flash Tool 1.5 with TOT using a different variant's *.TOT file in hopes it would work long enough to boot/think of a new solution but this fails due to a cross firmware check.
I see that some people on this forum were able to do it then fix their phone after a few more steps. Someone used a .DLL from another firmware and the program let him flash. Does anyone know of any programs (or tricks to bypass cross firmware check) I can use to flash a different/wrong variant's *.TOT file?
This is a strange part of the 1st log file:
"[ 7:20:12] Cross D/L Fail, phone : LG-D959, binary : Unknown
[ 7:20:12] Download exception Error
[ 7:20:12] ¡Ú¡Ú ERROR REASON : LAF_ERROR_INVALID_INPUT_FILE"
FULL LOG FILES:
View attachment 2986866
View attachment 2986867
Make sure you have internet connection. And boot to "download mode." Plug your phone into your PC, open up the LG PC Suite software that comes on the phone. If you don't have it just go to http://www.lg.com/us/support-mobile/lg-D959
About halfway down the page will be a download link for the "pc suite". Download it and run the .exe. Once you have it opened up click "mobile devices" on the top toolbar. And then select "Restore upgrade errors". And let it do it's magic.
I know this method works. I used it 2 days ago in kitkat and have used it about 20 other times. Due to having no custom recovery, once I softbrick this is what I have been using to come back to stock unrooted kitkat. Then I use " Dfuse's downgrade and unroot the easy way"
mattwheat said:
Make sure you have internet connection. And boot to "download mode." Plug your phone into your PC, open up the LG PC Suite software that comes on the phone. If you don't have it just go to http://www.lg.com/us/support-mobile/lg-D959
About halfway down the page will be a download link for the "pc suite". Download it and run the .exe. Once you have it opened up click "mobile devices" on the top toolbar. And then select "Restore upgrade errors". And let it do it's magic.
I know this method works. I used it 2 days ago in kitkat and have used it about 20 other times. Due to having no custom recovery, once I softbrick this is what I have been using to come back to stock unrooted kitkat. Then I use " Dfuse's downgrade and unroot the easy way"
Click to expand...
Click to collapse
Thanks for the reply! The LG PC Suite method didn't work. It went through all the steps then failed.
Dang.

D405N Brick - Any help?

Hi, I have LG D405N with hard brick (bad recovery.img flashed). From this moment phone doesn't give any signals.
Trying to solve this problem, by copy aboot.img to partition on linux system.
Not work. I think i have a bad aboot.img.
Anyone can help me?
Are you able to get to download mode? If so flash the KDZ.
same problem no download mode i need aboot file please
k01vu said:
Hi, I have LG D405N with hard brick (bad recovery.img flashed). From this moment phone doesn't give any signals.
Trying to solve this problem, by copy aboot.img to partition on linux system.
Not work. I think i have a bad aboot.img.
Anyone can help me?
Click to expand...
Click to collapse
see my guide here: http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
Hello
Can anyome help me please? I bricked my Lg L90 P405n after choose bad recovery.img file. Phone is dead, when i connect it to the computer, i see Android USB serial device and one drive with etc 60MB capacity.
I tried some advices from forum, but nothing was succesful.
Now i see phone as QUALCOM USB .... device , but when i set boardiag and click on Start button a see message Failed during loading flash programmer, Test aborted when i choose G2MLTE (MSM8926) and Device was not found in dload trying flash programmer when i choose W7 (MSM8226).
Attempts over LG Flash tool ended after 4% with error communication with the phone.
Have anyone correct method for D405n and correct MBM files with partition.txt?
Thank you
Martin
mcambel said:
Hello
Can anyome help me please? I bricked my Lg L90 P405n after choose bad recovery.img file. Phone is dead, when i connect it to the computer, i see Android USB serial device and one drive with etc 60MB capacity.
I tried some advices from forum, but nothing was succesful.
Now i see phone as QUALCOM USB .... device , but when i set boardiag and click on Start button a see message Failed during loading flash programmer, Test aborted when i choose G2MLTE (MSM8926) and Device was not found in dload trying flash programmer when i choose W7 (MSM8226).
Attempts over LG Flash tool ended after 4% with error communication with the phone.
Have anyone correct method for D405n and correct MBM files with partition.txt?
Thank you
Martin
Click to expand...
Click to collapse
Did you choose the right Com Port in b2b?
Yes i choose correct one. Today i make some other things and now is phone functional, but after restore phone lost IMEI information.
I use advice in this post http://forum.xda-developers.com/showpost.php?p=61636749&postcount=34.
Next question - is some way to restore/fill IMEI ?

Lg Optimus 4X HD Doesnt Boot to android

I rooted my phone with a locked bootloader So now when I try to open my phone I start getting this message [LGE SECURITY] Error Boot Image Signature then after 5 seconds it shuts down I tried everything I cant open my phone please help
Same issue!
I have the same problem here. Did you find a solution?
For Now flash your P880 with v20 kdz file, you can find it in General Threads.
Link for finding v20 kdz file
check post #3 by RuedasLocas
http://forum.xda-developers.com/showthread.php?t=2177616
and for Flashing steps
http://forum.xda-developers.com/showthread.php?t=2069723

Badly Needed HELP! LG G4 T-Mobile H810 Accidently Locked Bootloader With ADB

Hello Everyone!!!
I am urgently needing help on my T-Mobile LG G4 H810 and I'm at my WITS END! I rooted and unlocked the bootloader, but I was trying to remove the text on the top left on the splash screen Unlocked Bootloader. I didn't go into Settings to re-lock the bootloader and I typed in the command using adb! I know it was stupid but I didn't think it would brick my device! So, When I turn on the phone, the top left corner it says:
Secure booting Error!
Error Code : 1003
MODIFIED !!
Trust Me I've Properly installed LG Drivers and all Software to a T and Tried Many if Not All Versions (2014, 2015, 2016, 2.0.1.6 etc)
Also....During Firmware Update a.k.a Download Mode Inside the Box it Shows: 633A B100
Things I've Tried:
- Doing a Factory Reset, pressing Power and VOL Down then release and press Power again. After Reset it still doesBootloop with 1003.
- Following This Guide https://forum.xda-developers.com/tmobile-g4/help/secure-booting-error-1003-t3315915 Which I got to LG UP while in Download Mode but says Model: Unknown COM Ports: [COM10, H872... and WILL NOT let me continue because it's Unknown Device. I Tried Switching COM Ports to COM3, COM41 etc. But Didn't Help.
- I've Watched Youtube Videos to Use LG Flash Tool for ALL VERSIONS on Three Different Laptops! The procedure is as follows:
Type: CDMA PhoneMode: DIAG Rest Mode 33000. So I select the .kdz and Normal Flash or CSE Flash (I've tried both on every .kdz file I have), Read Phone Information just leads to program freezing, So I Press "START" Then "OK" for the Language English. The % bar goes UP and It gives The Connection Failed Error Which is Normal. On the Phone in that Box now Reads:
633A S0.0 AS0.0 B100 UHS
S U LG-H811 06.0 Hrev_10
HS1120v
The % stops and the timer keeps going but in the box it now just shows 633A B100
The KDZ Files I've Tried: H811V20p_00_0913, H811V20r_00_0111, H81110H_00, H81120i_00_0201, T-Mobile H811 10N, PR H810PR10a_02, PR H810PR10a_04.
I Switched Out Multiple Cables But Hasn't Helped!!!
I have been doing this for countless hours each week for several weeks and I can't believe Every Method Hasn't Worked! PLEASE HELP! I'M LOSING MY MIND DOING THIS! :crying:
P.S.
YES, I have opened the Phone and the Mainboard is a H810 but it was Sold to Me as an H811 Which at the Time Firmware showed H811 Last Time I Checked.

Categories

Resources