So I relocked my bootoader, and now I want to unlock it again, it fail. I even tried to just use fastboot commands to boot into recovery and it comes back as
failed phone must be rooted." I did use flashtool to reflash back to stock r800x firmware 2.3.2 I dont know what it s going on. I have flashed my phone before and unlocked the bootloader but now it wont.
I relocked my bootlaoder to ota to 2.3.3. but decided to go back to 2.3.2. for the time being.
Any ideas why this is happening?
tried to unlock the bootloader and it fails everytime. Using fastboot commands for recoveryPLAY comes back with a "phone must be rooted" line.
Your key could be wrong
Sent from my R800i using XDA App
Its the same key I used before to unlock the bootloader. I have retried if 4 times now and made sure I am not mistyping anything.
I did back up my TA using Omnius before relocking my bootloader, but to be honest I have no idea why I would need to backup the TA, I am guessing its part of the bootoader and if so is it possible to reflash that?
Ok so I tried to reflash the TA files I saved and it says failed everytime... I redid it 3 times, all failed. Here is the info it spits out.
Code:
Action journal
13:35:20 Restore TA
13:35:20 Allows to restore the TA (Trim Area) content.
13:35:20 Operating system: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit
13:35:20 Application version: 0.23.3995
13:35:20 . The action name is 'Restore TA'
13:35:20 Selected phone type: Xperia™ PLAY
13:35:20 Selected connection method: USB EROM
13:35:20 i Instructions
13:35:20 i 1. Make sure the phone battery is charged to at least 50%.
13:35:20 i 2. Switch off the phone!
13:35:20 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
13:35:20 i 4. Press and hold the return back button, then connect the cable to the phone!
13:35:20 . The action started waiting for the user
13:35:39 . The action finished waiting for the user
13:35:39 Connecting via SEMC USB Flash Device (USB1)...
13:35:39 Device driver version: 2.2.0.5
13:35:39 Detected chipset: MSM7X30
13:35:39 Boot mode: EROM
13:35:39 EROM version: 1241-3656 R9A021
13:35:39 IMEI: (I deleted this cuz i can)
13:35:39 Device ID: 4058AD36DB8B3F13C8F63D2314843C6B4BAB1163
13:35:39 Minimum loader AID: 0001
13:35:39 Color: Red SEMC
13:35:40 e Server settings are incorrect.
13:35:40 i The username or the password field is empty.
13:35:40 e Failed!
13:35:40 . The action entered shutdown phase
13:35:40 . The action reported failure
Error code
# 7F1491C64A78F909
Error details
---
70 77 AA 9D BC FA 38 17 72 2B 53 C6 B6 8D C0 44
46 B6 24 4D 71 10 16 4E FE F7 D4 29 41 78 30 F8
4A 68 9A C2 F2 BB 58 47 92 34 C4 08 D6 FB BA 43
74 A0 BC AD 9E 1F C1 35 0B D7 E2 44 9A 03 F0 A1
6A 02 54 7E D2 33 23 42 E0 98 5C CB F6 39 B8 75
34 6C 32 12 BE B5 78 53 EF 31 F0 44 28 CF 10 B1
76 41 74 43 4E 81 E5 AF F9 19
---
Bump....... anyone have any ideas how to get back to root.... None of the commands to boot into recovery are working......
I am guessing the TA restore failed as the bootloader is still locked and I am unable to unlock it using the key code I used originaly to unlock it
I am going to try SEUS to see if repairing it (even though the phone works fine, just not accepting fastboot commands) and see if maybe that will someone allow me to do fastboot commands.
Same results... still fails
I'm wondering, even though I ota'd to 2.3.3, but then used flashtool to go back to stock 2.3.2 and I am still unable to use fastboot to unlock or use recoveryPLAY. I wonder if somehow the boot from the ota is still embedded and not accepting the commands from fastboot? Despite fully flashing back to 2.3.2. Just my thoughts. I will probably have to wait until there is root for 2.3.3 for Verizon (R800X), however if there is anyone that has an idea I would really appreciate it.
bump...............
As far as the TA backup afaik it cost's money to restore it again and it's only free to do the backup. That might be the reason for the error you get when trying to restore.
You could always turn to this (I'm not sure, but i don't think you can reverse it, no relocking after it's done. You'll have to ask about that):
http://forum.xda-developers.com/showthread.php?t=1232050
Regards Dousan...
Related
I have a GT540 stuck at the LG animation. I had Cyanogen 6.1.1 which I didn't really like (was having some big issues with it), so I flashed a 2.1 ROM and now I'm stuck.
I have tried:
* disabling LGE Modem in device manager, rebooted laptop and phone, reconnect then flash
* booting boot into fastboot mode - screen does not go black, stays stuck at lg logo. Fastboot commands leave <waiting for device>
* using ADB while phone stuck, error "device not found" - same in download mode
* booting into safe mode with home+power button, phone stops at animation still
* flashing using KDZ in all 3 modes both when the phone is stuck and also in download mode
* flashing using the KP500 updater as described at hxxp://android.modaco.com/index.php?showto...t&p=1394990
* flashing using LG mobile support tool recovery option
* reinstalling LG drivers
* flashing with phone in download mode through LG Mobile Support tool in recovery mode, error "No software update available for this device"
* connecting to the phone through hyperterminal to do a factory reset then flashing
* some people are reporting this problem with a corrupt SD card. Removed SD card, still having this problem
* removing battery, connecting USB cable (displaying phone with arrow screen) and flashing in all 3 KDZ modes
* booting download mode by removing battery and holding VOL- while plugging cable in
I can't find ANY more ideas no matter how hard I search. I've been trying to fix this for 2 days solid now and I seem to have tried everything.
Halp!
@above
Did u tried to flash Quarx black ROM ?
I've flashed Vodafone 2.1 official, Baltic 2.1 official, French 2.1 official, a 2.1 with fastboot, and Clockwork Recovery 2.1... also out.kdz as mentioned in this thread hxxp://forum.xda-developers.com/showthread.php?t=825173&page=3
I'll try the Quarx ROM now but I don't like my chances
EDIT: out.kdz in the thread above is the same ROM as in the quarx black rom thread here hxxp://modmymobile.com/forums/527-lg-androids/557934-gt540-rom-black-system-rom-quarx.html so yes, I've already tried that ROM.
I've logged a service request with LG but I REALLY want to get it working without waiting a week or two for them to get to it...
thanks
EDIT #2: I CAN access the phone using Hyperterminal on COM12 (tried a hard reset that way) but I have no idea what commands exist or anything through that terminal...
When you tired to flash a ROM with fastboot what happened? still stucked @ LG logo
I can't do anything with fastboot - if I hold camera+power it won't give me a black screen, it just gets stuck at the same spot (last frame of the LG animation, white LG logo)
I tried running fastboot commands in this state but I just get <waiting for device>
EDIT: I've just re-flashed the quarx ROM but getting the same problem, camera+power hangs at the LG logo and fastboot reboot just sits there with <waiting for device>
I was wondering, is there any way at all to install software through a hyperterminal? This seems to be the only connection method that works (adb doesn't work either). I followed these instructions to do a factory reset and it worked:
In Hyper Terminal type
AT
OK --> if youre getting OK, then connection with your device is OK, if there is no OK, check again your PORTS
if you get OK, the type
AT%FRST
FACTORY RESET OK --> this will perform factory reset to your device, it might fix your problem but it might not
Click to expand...
Click to collapse
It didn't fix the problem, but I was able to connect and successfully perform the reset so at least that connection works... Maybe I could erase the system and then try flashing in cs_emergency mode or something?
1. Remove battery,sim,mmc coonect ur phone to pc using USB cable
2. Press Volume down + power when it boots
3. It should go to download mode now
tell me whether it is going to download mode or not
It goes into download mode when I do that, I've tried flashing in DIAG, EMERGENCY and CS_EMERGENCY modes this way with no success.
20B FAST
Try this: flash it in normal mode with KDZ updater.
Then when flash is finished enter in fastboot mode ( in this ROM flashboot is not black screen, it is blue screen with white letters) so you can easy see when you are enetered in fastboot.
then
fastboot -w
We have liftoff!
Booting the phone normally I get the LG picture, LG animation then loop at the android animation (one step further than I was getting before...)
Phone booted into blue screen fastboot mode and fastboot commands work (fastboot -w, fastboot reboot etc).
fastboot -w gives the following readout
fastboot: processing commands
fastboot: erase:userdata
skipping @ 3215 (bad block)
cannot erase @ 3215 (bad block?)
fastboot: erase:cache
Click to expand...
Click to collapse
Best of all, the phone boots and runs normally after I ran fastboot -w. ADB commands work when the phone is booted normally. But is the 'bad block' message something I should be concerned about?
So 2 things - first, should I now be able to flash it with an official 2.1 ROM? I don't really want to reinstall Cyanogen as I had a lot of minor but REALLY annoying problems with it (bad touch and haptic feedback was the worst). I would just like to flash an official 2.1 for the time being while I find a better 2.2 port. And second, can you explain what's so special about this ROM that it worked when all the others I tried (at least 10 of them), including fastboot-enabled ones, didn't?
Thanks!
Best of all, the phone boots and runs normally after I ran fastboot -w. ADB commands work when the phone is booted normally. But is the 'bad block' message something I should be concerned about?
I have also two bad block but it seems that flash found them ,and skip writing to them so I think that is ok.
- first, should I now be able to flash it with an official 2.1 ROM?
You should in theory: I found that I cannot flash my LG540 with any official ROM since I flash it with fastboot rom. ( and I wrote on several forums, no one give me answer) In fact, only few users tell they can flash it without any problem, but much more have same problem like me. So if you successfully flash with original ROM, tell me about that.
And second, can you explain what's so special about this ROM that it worked when all the others I tried (at least 10 of them), including fastboot-enabled ones, didn't?
I made it at home, in peace of my room
I dont know what is so special, but I rearrange few official ROM into fastboot for reason I tell before in this message.
Well thanks again I am in the middle of flashing official vodafone 2.1 so I'll let you know how that pans out.
Which ROM did you modify to come up with this one? It looks like baltic I guess
EDIT: Flash with official Vodafone Australia 2.1 ROM unsuccessful. The phone loops at the Android animation (although this is still further than I was getting before), I left it for a while (15 minutes or so) in case it was a slow first boot but it's still looping.
I guess I'll flash with your ROM and use that for a while, maybe I'll stick quarx on it.
thanks for your help mate I've been trying to unbrick this phone for nearly a week
So I tried to install black quarx using the guide in this thread: http://modmymobile.com/forums/527-lg-androids/557934-gt540-rom-black-system-rom-quarx.html
However the ROM that it says to install first leaves my phone hanging at the LG logo again. Something you did when you made your ROM avoids this problem that all other ROMs seem to cause..
I'm going to reflash with your ROM then skip the rom step in that guide and just install the black quarx system.img over the top of your ROM... we'll see if that works!
looking at the screencaps for that black quarx, something tells me I need the ROM as well as the system.img for it to work.... oh well we'll see what happens
CowboyDan said:
So I tried to install black quarx using the guide in this thread: http://modmymobile.com/forums/527-lg-androids/557934-gt540-rom-black-system-rom-quarx.html
However the ROM that it says to install first leaves my phone hanging at the LG logo again. Something you did when you made your ROM avoids this problem that all other ROMs seem to cause..
I'm going to reflash with your ROM then skip the rom step in that guide and just install the black quarx system.img over the top of your ROM... we'll see if that works!
Click to expand...
Click to collapse
That was case with me also. When I try quarx ROM I didnot have get it to work.
So I flash "my rom" then erase ALL
- fastboot -w
- fastboot erase system
- fastboot erase boot
and then reboot phone
fastboot reboot
Enter in fastboot mode, and flash it with quarkx ROM and should work without problem. But since black theme Quarx use i so dark for me I found it unusable, And ROM is not heavly modified so difference between them and stock ROM is not big. So for that reason I go back to "my" rom and stick to it...
CowboyDan said:
Which ROM did you modify to come up with this one? It looks like baltic I guess
EDIT: Flash with official Vodafone Australia 2.1 ROM unsuccessful. The phone loops at the Android animation
Click to expand...
Click to collapse
I was modify UK ROM , BALTIC ROM, and OPEN EUROPE ROM ( you have it)
Baltic rom was smallest but have strange symbols when listing applications for remove ( white squares) . Also many other have that so I remove it from my phone. Beside that all was ok.
UK ROM was also ok, but have random FC on one application, so I finally flash it with OPEN EUROPE ROM, change application that have FC and now is all ok.
Battery have about 4 days of "life", phone doesn't slow down and I am happy with that ROM.
Yes, that is error I get ( but you go further then me, I stuck on LG logo)
Hey mate just noticed something tonight when I left the house (and got off wifi), mobile data doesn't work? I did a factory reset and it still doesn't work, double checked the settings and it should be fine...
Does it work on your phone?
Never have any problems with mobile data. Since you noticed wifi and mobile data doesnot work together.
Look at PAN for Internet, does at end stay: default- last option.
It must not be empty
Option name is APN model:
i have flashed lg gt540 with official android 2.1
i have flashed lg gt540 with official android 2.1 and i can say honestly i have do that 5 or 6 times on my phone depend of wich custom rom i have used before
NOW I CAN'T
I DON'T KNOW WHAY
I HAVE THE SAME PROBLEM WITH STUCK LG LOGO
I HAVE TRAY 10 TIMES STILL I CAN'T FLASH OFFICIAL ANDROID 2.1
pepi74 said:
Best of all, the phone boots and runs normally after I ran fastboot -w. ADB commands work when the phone is booted normally. But is the 'bad block' message something I should be concerned about?
I have also two bad block but it seems that flash found them ,and skip writing to them so I think that is ok.
- first, should I now be able to flash it with an official 2.1 ROM?
You should in theory: I found that I cannot flash my LG540 with any official ROM since I flash it with fastboot rom. ( and I wrote on several forums, no one give me answer) In fact, only few users tell they can flash it without any problem, but much more have same problem like me. So if you successfully flash with original ROM, tell me about that.
And second, can you explain what's so special about this ROM that it worked when all the others I tried (at least 10 of them), including fastboot-enabled ones, didn't?
I made it at home, in peace of my room
I dont know what is so special, but I rearrange few official ROM into fastboot for reason I tell before in this message.
Click to expand...
Click to collapse
pepi74 said:
Try this: flash it in normal mode with KDZ updater.
Then when flash is finished enter in fastboot mode ( in this ROM flashboot is not black screen, it is blue screen with white letters) so you can easy see when you are enetered in fastboot.
then
fastboot -w
Click to expand...
Click to collapse
Hi, I'm stuck at the LG screen, can't enter recovery mode and have no idea what fastboot is. so I've downloaded V20B_00 from elsewhere and I'm unable to finish the process. Is there any different between that and the you FAST version? If so can you please let me know how I can get it?
I'm flashing in emergency mode and I got Upgrade Error -
WParam: 100
LPram: 502
LOG:
12:42:07 : Launching SW update
12:42:07 : Unpacking KDZ
12:42:07 : KDZ file extraced
12:42:08 : Files were extracted.
12:42:08 : LGMobileDL Load.
12:42:08 : Port = -1
12:42:08 : Connecting to phone
12:42:18 : Check Phone mode = 2
12:42:25 : Phone type check.......
12:42:27 : LGMobileDL.DLL Loading....
12:42:27 : _SetAuthMark Fail
12:42:27 : AuthMark°¡ Á¤È®È÷ Phone¿¡ Write µÇÁö ¾Ê¾Ò½À´Ï´Ù!
12:42:27 : _SetAuthMark Fail
12:42:27 : LoadCDMAPhoneData() Error
12:42:27 : _DetachDLL Call
12:42:27 : _DetachDLL Call End
12:42:27 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\DZ_GT540AT-00-V20b-BAL-XXX-SEP-13-2010.dz
12:42:27 : Param : moduleDir =
12:42:27 : Param : waitTime = 33000
12:42:27 : Param : UsbHighSpeed = 1
12:42:27 : Param : PhoneMode = 2
12:42:27 : Param : BinVersion = V20B_00
12:42:27 : Param : AuthMark = 21332
12:42:27 : Call fn_StartUpgrade
12:42:51 : CDMA: wParam = 100, lParam = 502
12:42:51 : Step : Upgrade Error2 - Error Code : 502
12:42:51 : ResetStartInfo() Call
12:42:51 : _DetachDLL Call
12:42:51 : _DetachDLL Call End
12:42:51 : FreeLibrary Call
12:42:51 : FreeLibrary Call End
12:42:51 : ResetStartInfo() Call End
12:42:53 : ===FINISHED===
12:43:44 : OnModelDllMsg(OnMsgFromModelDll-CDMA) delete m_pLGCyonUpdate
Thanks
LG gt540
mejack03 said:
1. Remove battery,sim,mmc coonect ur phone to pc using USB cable
2. Press Volume down + power when it boots
3. It should go to download mode now
tell me whether it is going to download mode or not
Click to expand...
Click to collapse
Hi, I have the same problem, my phone was working fine until when I tried to upgrade to a higher version android and it fot stuck and took a long time so had to unplug it from the USB. Then when I tried to on it it was getting stuck at the white LG logo. Only once I was able to get it to the download mode, unfortunately I did not know what to do after that tried to plug it into my system but nothing happened, so just removed the battery after that and still standing at the same place. I teied as instrucked but nothing happenes. Please help me with this.
Just got my streak yesterday, only had it a few hours and i've somehow managed to brick it already !
Started on the official 1.6, upgraded to official 2.2, rooted it, installed clockwork recovery. All was fine up until this point, i then went to install the performance fix http://forum.xda-developers.com/showthread.php?t=848487 but after doing so my streak stopped booting, since then its just hanging at the dell logo.
First thing i tried was restoring to the default recovery rom by holding power + volume buttons and option 2. This didnt work so i then tried this http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/ and still no luck.
I've been at it for hours and its late so im giving up for now, i just hope the xda community can help me out.
Edit: I should add that the recovery image (option 2) is going through fine without errors, its only that when it boots it hangs at the dell logo. Also, fastboot is working so hopefully its not completely bricked. Is there anything i can do ?
get qdl tool and see if u can get to 305 stock
GET QDL TOOL HERE
Turn phone completely off, hold volume up and plug phone to computer
Open QDL Tool
if you have the correct driver, it will recognize ur phone
if not, the driver is included but u have to search how to install it
Hit Run and wait about 3-5 minutes
When its done it will reboot and be on stock 305 and then u can try again with ur update
Thanks just had a go at QDL but cant seem to get it to work. I got it to detect my phone as the Qualcomm HS-USB Diagnostics 9002 but after clicking run it just errors.
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Thu Apr 28 02:21:41 2011
Check image DBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
ERROR[D14]: Streaming hello Failed!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2011/04/28 02:22:01
Elapsed Time: 19.70 sec
After countless hours of going insane i have managed to get my streak working again using the o2 package (build 8105) found here http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/
I couldnt get QDL to work for some reason so in the end i just downloaded the above package, copied to sd, renamed to update.pkg, powered on with volume buttons and chose option 2.
Its working now so thats the main thing, i was worried i might have bricked it for good ! Now i just need to get back to the official dell rom
If I wre doing this, I would get the multi_recovery tool. I would put the 351 package on your SD card
Flash the 351 recovery with the tool. Do not boot up go right into the recovery and point it to the 351 package. Make sure the 351 package has been renamed to the proper name. Either update.pkg or update.zip.
Worked like a champ for me.
Sent from my Dell Streak using XDA App
alperin1 said:
If I wre doing this, I would get the multi_recovery tool. I would put the 351 package on your SD card
Flash the 351 recovery with the tool. Do not boot up go right into the recovery and point it to the 351 package. Make sure the 351 package has been renamed to the proper name. Either update.pkg or update.zip.
Worked like a champ for me.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
That's the method that just broke my phone.
ducehlmg said:
get qdl tool and see if u can get to 305 stock
GET QDL TOOL HERE
Turn phone completely off, hold volume up and plug phone to computer
Open QDL Tool
if you have the correct driver, it will recognize ur phone
if not, the driver is included but u have to search how to install it
Hit Run and wait about 3-5 minutes
When its done it will reboot and be on stock 305 and then u can try again with ur update
Click to expand...
Click to collapse
Sorry but bug in but I'm having the same issue. I finally got QDL to work but after it finishes, the phone shows a screen with "Andriod system recovery utility
Press the shutter button to start emergency software recovery
Warning all data will be erased
Press the Volume up button to power off without recovering".
After I press shutter the it loads the update.pkg and then sits on the dell logo, and sits, and sits.
I'm now back on the official dell 2.2, in the end i had to flash the 351 recovery image to get the rom pkg to work.
I flashed the above recovery in fastboot mode since i cant get QDL to work, checked my drivers countless times, tried windows 7 64 bit and 32 bit, aswell as windows xp 32 bit. 64 bit always gives me the d14 error and 32 bit is the d2 error so i just cant understand why it wont work, surely it cant be a driver issue since fastboot works flawlessly and i've spent hours checking the driver now. Also i've followed the guide on streakdroid to the book so im pretty certain my setup is perfect.
Anyway, im happy with the official 2.2 for a while now but at some point i would like to try a custom rom through qdl, etc.
drkdeath5000 said:
After countless hours of going insane i have managed to get my streak working again using the o2 package (build 8105) found here http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/
I couldnt get QDL to work for some reason so in the end i just downloaded the above package, copied to sd, renamed to update.pkg, powered on with volume buttons and chose option 2.
Its working now so thats the main thing, i was worried i might have bricked it for good ! Now i just need to get back to the official dell rom
Click to expand...
Click to collapse
That's it? WHen I installed the recovery from your link, after it said recovery install done(something along those lines) the phone didn't restart like it has with my previous recovery installs. I waited a few minutes, pulled the battery, and restarted into recovery, hit update and it has been a blank screen since.
I think I'm out of luck. I had the phone plugged into the charger all night and I'm trying to flash it now and the battery is at 0%. Can't charge it or anything. Time to call dell.
Hi!
I have developed a problem with my LG Swift L5 (e610) phone. The problem is, that I tried to downgrade from Android 4.1.2 to 4.0.1, but I must have chosen the wrong KDZ file, because the phone is bricked, all I see after turning on my phone is a white screen (But I think that it is working, because I can hear the boot sound, and the screen dims). I have included a photo of my phone below.
Now here comes the real problem. I have got all the drivers installed, but my phone isn`t detected by my computer. And I don`t think my phone detects my computer either, because when I connect my phone to a USB port, the screen doesn`t light up. When I connect my phone, and try to flash a new system using the KDZ Updater, my phone isn`t detected either.
I hope somebody out there will be able to find a solution to my problem! Thanks.
can you get your phone to download mode?
Hi, thanks for your reply!
Well, I don`t actually know if my phone is in download mode (after using vol-up + vol-down + power), because the screen is white! Let`s put that as a no, I can`t boot into download mode. Does anybody have any other ideas?
PeterNicholson said:
Hi, thanks for your reply!
Well, I don`t actually know if my phone is in download mode (after using vol-up + vol-down + power), because the screen is white! Let`s put that as a no, I can`t boot into download mode. Does anybody have any other ideas?
Click to expand...
Click to collapse
1. Switch off the phone
2. Remove battery
3. Hold power and volume up button
4.Plug in USB cable
....and phone will enter into emergency mode.
Drivers for USB my install, let them finish and then flash the KDZ you want using KDZ updater.
Hi, thanks for your reply!
I did exactly what you told me to do, I even reinstalled the LG United Mobile Driver, it seems to detect my phone now, but I have came across a new problem. Here is the log:
Code:
[R&D Test Tools Log File]
08:09:32 : Start fn_StartUpgrade
08:09:32 : Extract kdz file
08:09:40 : kdz decrypt Success
08:09:45 : Extract file Success.
08:09:45 : LGMobileDL Load.
08:09:45 : Port = -1
08:09:45 : Connection check start.
08:09:54 : Check Phone mode = 2
08:10:11 : Phone type check.......
08:10:12 : _DetachDLL Call
08:10:12 : _DetachDLL Call End
08:10:12 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\LGE610AT-00-V20a-EUR-XX-APR-04-2013+0.dz
08:10:12 : Param : moduleDir =
08:10:12 : Param : waitTime = -2129117282
08:10:12 : Param : UsbHighSpeed = 1
08:10:12 : Param : PhoneMode = 2
08:10:12 : Param : BinVersion = v20a_root_UP_BY_GALAS2_COPY
08:10:12 : Param : AuthMark = 50008
08:10:12 : Call fn_StartUpgrade
08:10:12 : CDMA: wParam = 206, lParam = 0
08:10:12 : Model Dll Msg Not Found(206, 0)
Okay guys, it doesn`t matter, I posted to quickly, I have managed to fix it! Thanks for your great help guys!
ic90 said:
1. Switch off the phone
2. Remove battery
3. Hold power and volume up button
4.Plug in USB cable
....and phone will enter into emergency mode.
Drivers for USB my install, let them finish and then flash the KDZ you want using KDZ updater.
Click to expand...
Click to collapse
not working, I have a L5
mamece2 said:
not working, I have a L5
Click to expand...
Click to collapse
What is not working? Emergency Mode or detecting USB cable?
ic90 said:
What is not working? Emergency Mode or detecting USB cable?
Click to expand...
Click to collapse
Emergency mode is not working, how could I force emergency mode from ADB (linux)?
reboot download doesnt work.
My HD2 after being on the shelf for 6 months won't boot getting stuck on the HTC logo, sometimes while trying to boot it will vibrate 5 times. I took out the cards (sim and sd), didn't work. What's interesting is that the first time I booted it after the 6 months it booted, but got stuck on the homescreen, though I could see my ROM fully booted, after taking out the battery to reboot, it wouldn't boot anymore. Tried keeping it with the battery out for 3 days and booting it: first time it got passed the HTC logo and got stuck on Android logo, after booting again it's getting stuck on HTC logo again.
Read on the forums it might be because of bad sectors on the NAND. Problem is I can't connect to the phone through usb: `adb devices` doesn't list anything: I tried while stuck on HTC logo and while in HSPL (after holding volume-down and power). I have the google usb driver installed.
I can boot into recovery (ClockworkMod Recovery v3.1.0.0) and connect using adb. Not sure what to do now though.
Any help or insight would be much appreciated.
Update: did `adb shell dmesg` and found a few "BAD BLOCK" messages. The whole dmesg: pastebin.com/raw.php?i=TWveK0WA ; and below an excerpt:
Code:
<5>[ 2.275085] Creating 6 MTD partitions on "msm_nand":
<5>[ 2.275146] 0x000004320000-0x000004420000 : "misc"
<5>[ 2.276763] 0x000004420000-0x000004920000 : "recovery"
<5>[ 2.282531] 0x000004920000-0x000004e20000 : "boot"
<5>[ 2.288269] 0x000004e20000-0x00000e420000 : "system"
<4>[ 2.403808] ###BAD BLOCK 1501 0BBA0000###
<5>[ 2.446746] 0x00000e420000-0x00000e920000 : "cache"
<5>[ 2.452514] 0x00000e920000-0x00001e820000 : "userdata"
<4>[ 2.465698] ###BAD BLOCK 1964 0F580000###
<4>[ 2.537445] ###BAD BLOCK 2511 139E0000###
<4>[ 2.547851] ###BAD BLOCK 2590 143C0000###
<4>[ 2.548004] ###BAD BLOCK 2591 143E0000###
BAD Blocks everywhere ... my HD2 is worse ...
dmos62 said:
My HD2 after being on the shelf for 6 months won't boot getting stuck on the HTC logo, sometimes while trying to boot it will vibrate 5 times. I took out the cards (sim and sd), didn't work. What's interesting is that the first time I booted it after the 6 months it booted, but got stuck on the homescreen, though I could see my ROM fully booted, after taking out the battery to reboot, it wouldn't boot anymore. Tried keeping it with the battery out for 3 days and booting it: first time it got passed the HTC logo and got stuck on Android logo, after booting again it's getting stuck on HTC logo again.
Read on the forums it might be because of bad sectors on the NAND. Problem is I can't connect to the phone through usb: `adb devices` doesn't list anything: I tried while stuck on HTC logo and while in HSPL (after holding volume-down and power). I have the google usb driver installed.
I can boot into recovery (ClockworkMod Recovery v3.1.0.0) and connect using adb. Not sure what to do now though.
Any help or insight would be much appreciated.
Update: did `adb shell dmesg` and found a few "BAD BLOCK" messages. The whole dmesg: pastebin.com/raw.php?i=TWveK0WA ; and below an excerpt:
Code:
<5>[ 2.275085] Creating 6 MTD partitions on "msm_nand":
<5>[ 2.275146] 0x000004320000-0x000004420000 : "misc"
<5>[ 2.276763] 0x000004420000-0x000004920000 : "recovery"
<5>[ 2.282531] 0x000004920000-0x000004e20000 : "boot"
<5>[ 2.288269] 0x000004e20000-0x00000e420000 : "system"
<4>[ 2.403808] ###BAD BLOCK 1501 0BBA0000###
<5>[ 2.446746] 0x00000e420000-0x00000e920000 : "cache"
<5>[ 2.452514] 0x00000e920000-0x00001e820000 : "userdata"
<4>[ 2.465698] ###BAD BLOCK 1964 0F580000###
<4>[ 2.537445] ###BAD BLOCK 2511 139E0000###
<4>[ 2.547851] ###BAD BLOCK 2590 143C0000###
<4>[ 2.548004] ###BAD BLOCK 2591 143E0000###
Click to expand...
Click to collapse
Dear friend ... the DMESG says that there are too much bad blocks in the NAND ... The problem is that the phone haven't been used for a long time because those chips are too old ... nowdays they use another kind of silicon for their chips that don't get bad blocks after long times ... The thing I recommend is to make a full backup with the Recovery then try doing a Clean ROM Flash ( do a fullwipe + flash ROM ) if the ROM didn't boot again , do a Task29 then try reflashing the Bootloader and reflash the CWM again and reflash the whole ROM ... If booted , restore the data partition and enjoy but if not , try another Bootloader it also can be a good try ... Good luck
With Best Wishes
Hitman1376
Hi ,
I have a Huawei P8 GRA-UL00 phone and a few minutes ago , I had aError Func NO : 11 (reovery image) Error NO : 2 (load failed!) problem in fastboot.the name of FASTBOOT&RESCUE Mode has changed to RESCUE Mode.. I want to teach you how to solve this problem. What are the possible causes of this problem?
reasons :
The phone needs a reboot . And some other reasons for this problem are : Improper installation or tampering ROM and/or Recovery, tampering Bootloader and root the phone
How to Solve :
I connected the phone to the computer in the same mode (using a USB cable). After about 20 minutes, in the same mode, when the phone was in RESCUE MODE and connected to the computer. I pressed the power button and the mute button simultaneously for a few seconds until the phone rebooted and re-entered the fast boot. But this time there was no such problem.
if any problems or question's , commend here .
Regards ,