Seeing as there isn't a section for the LG P870/LG Escape I'm going to try and get as much info condensed into one thread for now.
Not even sure how popular this phone is but, hopefully this will be of some use to someone.
KDZ:
I know this isn't posted anywhere so here is the v10f KDZ from LG. It is the latest firmware as of 11/6/2012:
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP870/AATTBK/P87010f_00/P87010f_00.kdz
If you don't know how to flash a KDZ I will make a guide here soon. V10f is rootable using the method below as is v10c
Download Mode:
To get into download mode turn off your phone, press and hold the vol+ and vol- keys, with those held down insert the USB cable while continuing to hold down the keys. After a few seconds phone will enter download mode automatically.
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Thanks! My wife just got this. I was able to root and update and retain root with OTA rootkeeper. Was looking for a kdz just in case. If there's enough interest i will see if i can port TWRP so we can cook up some custom roms.
I am definitely interested in custom roms, I have this device. Its not bad considering the price and what you get. 1494 on geekbench too! Pretty decent!
---------- Post added at 07:49 PM ---------- Previous post was at 07:44 PM ----------
Thanks for the effort
Aye guys I'm new into rooting and android in general, but I don't really understand how to root this phone. Kinda been looking around for a while and I was wondering if you can write some sort of guide. As of now I'm pretty lost the other threads aren't giving me any general information on exactly how to root the LG P870 or androids in general.
-Thanks
Btw I understand what exactly what rooting does to your device and the purpose of rooting, its just exactly how to root the device.
Well first things first do you have the android SDK installed on your computer
cyclejim said:
Well first things first do you have the android SDK installed on your computer
Click to expand...
Click to collapse
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Urabewe said:
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Click to expand...
Click to collapse
He
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Thanks for the effort
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
KDZ is the LG format for ROMs which is the built in read only memory that hold the instructions for the phone to run the hardware and features.
But I just rooted my phone with a combination of the above files, and it didnt go exactly as I hoped. First I ran the v1.2 batch file linked above, (the 1.6 batch file archive is invalid and doesnt extract properly. It seemed like it ran properly, i did the restore (no data destructive you shouldnt lost any data) but I didnt have root when completed. Then I tried the v17 of the original thread which can be found here http://forum.xda-developers.com/showthread.php?t=1886460
That one also ran but failed at the end saying something about me not having root on the phone.
I than ran the v1.2 batch file not once, but twice in a row. The second time I found my phone operating in "emulator mode" in other words, it was running laggy as hell and very slow. I then ran the V17 batch file from the link above, and boom it worked. So as you can see it wasnt typical, but I think if you dont have success with the 1.2 the first time, run it again, if it still didnt work, try running v17 like i did. I now have root and my phone is working fine.
Basically, I got the Escape then got the Nexus7 and have been involved in that. Really haven't been doing much with the Escape. I will be looking into more for everyone and hopefully get a custom recovery at the very least. Then at that point we can start thinking about rom. Until then we are stuck with what we have. I will get more info for everyone , till then this is what we have. If you think you can help go for it. If not sorry but this is the best info there is for our phone . I will positively without a doubt post any new info here so if that's what you are looking for this is the right place until then, thank you and you are welcome.
Sent from my Nexus 7 using xda premium
Markyzz said:
He
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Click to expand...
Click to collapse
So when I run the .bat file do I just run it in cmd? I'm kinda knew at this lol.
Also does my phone have to be in download mode?
Sorry for the inconvenience but where exactly do I run the .bat file?
-Thanks
One more thing I never downloaded a .zip or .rar file.. Could you please leave me a link?
Rooted
Thanks people I guess I just needed time to figure it out lol. I ran it in cmd twice(1.2v) but not right after each other and the second time it worked thanks guys.
Well. I tried to install beats audio but now it won't even load up just boot loops when it gets to at&t...
Bricked
Great the first bricked lg p870 lol, anyone know how to fix this. Or is it just a brick?
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
GHazard said:
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
Click to expand...
Click to collapse
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Markyzz said:
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Is their a guide on how to flash the device using the kdz flash tool? I mean my phone won't turn on though. It goes into the lg logo then just goes black (the back light is still on).
K I have all the tools but
I downloaded every tool from this thread
But in the PDF guides it says to put the phone in Upgrade mode by removing the SIM, battery and SDC(Micro sd card?) so I did that. Then insert the usb while holding the Volume Up button. All that happens on my phone is the home keys on the bottom just flash. And my phone doesn't connect to my computer either.
My Notes on LG P870
Ok I have fixed my device, well twice now. It seems whenever you try to change any file within the root it restarts, then boot loops. I tried too change a font using Rom Toolbox, it restarted then boot looped. I rooted the device using the 1.2v script once, but this time I'll try 1.7v and see if I can change fonts etc.
Are any of you guys having any problem with this?
If you do, and you are soft bricked just:
Download UPK 3.7.1
Then open up LG /mobile Update
Click Install Drivers(Make sure your phone is not connected) Choose your phone and carrier
Let that finish(Gonna take awhile you have to install all of them)
Then click Install updates...Done
Worked
Posting confirmation for an LG Escape (p870). 10f rooted using the tools linked in first post. Used version 1.2 to start and had to use the version 17 of the other rooting kit to finalize like another user encountered as well. Thanks will be given if they haven't been yet.
Related
Ok I have the LG-P999dwp version, and was in unable to do the update through the lg updater. Was told that i have latest version. I am also running win7 ultimate and the KDZ program would always crash, so i found a work around.
I downloaded the LG kdz program and the V21_00.Kdz file You can get them from here, http://forum.xda-developers.com/showthread.php?t=1179750 here are pics to help you do this on a windows 7 ultimate and should work for any version of win 7.
The pictures show you what to do.
1: open the KDZ program ( follow the instructions in the read me )
then keep the cdma and DIAG alone and choose the browse and click on the V21E_00.KDZ file.
Sorry if this has been posted but i searched and could not find anything on how to do this. I was working out a few ways to do this on win 7 without installing win xp
2:Click on read phone information at the bottom of the program.
3:Click on Upgrade Start
4:Change country to different country and change Language to english
5:click ok and this opens up the LG updater and will push the update of GB to your phone on windows 7 machine and for phone with LG-P999dwp model # (aka refurb)
thank you soo much!
Works!!! Just follow the steps exactly. My wife has a p999dwp and I have a p999dw. Ive been trying to get Gingerbread on hers for two days now (the official way). I can now find one complaint about the update, I love it. I haven't used Bluetooth yet though. Thanks so much.
Thanks... Worked perfectly....
Just in case anyone wants to know .... I put my phone back to stock and unrooted before I did the update process.... Everything went smooth, update process took about 10 minutes.. Thanks again Bullseye....
I can't get into S/W Update mode now to flash ClockworkMod ???
EDIT: Never mind...had to try it a bunch of times (volume down and plugging in) before it worked
see my only problem is everytime i try to install the lg updater tool it stops quarter of the way and doesnt move, i have a windows 7
how did u guys get the update tool to install, i run it as administrator and it starts but then stalls quarter of the way? and it told me i had to install the tool , but then i just tryed launching the update and it started the process, of course i didnt try with the phone plugged in, what do u guys think
It doesn't even want to read my phone info....it gives me Get Chiptype Error. Tried with Debug mode too-still nothing. It keeps freezing on me....I am running Win7 Ultimate 64bit.
Anyone else having the same issues. I have all the drivers installed.
you have to be in stock 2.2 froyo doesnt matter if youre rooted or not, and stock recovery, and run the tool while booted into froyo with usb debugging on .. and i dont know but i had my sd card mounted
and by the way if this worked for you THANK the freaking OP because he figured it out and you couldnt he's awesome, love you man xD
sincest said:
you have to be in stock 2.2 froyo doesnt matter if youre rooted or not, and stock recovery, and run the tool while booted into froyo with usb debugging on .. and i dont know but i had my sd card mounted
and by the way if this worked for you THANK the freaking OP because he figured it out and you couldnt he's awesome, love you man xD
Click to expand...
Click to collapse
I am running stock Froyo and I am not rooted. I have stock recovery as well. I keep getting the same error...it starts reading my phone info and then Bam! Get Chiptype Error!
yes sir , for sure so sincest your talking about the lg update tool ur telling me i have to install it with the phone actually plugged in?
doesnt really matter, i had it unplugged till the window like the screenshot came up, try reinstalling the 3.x.x drivers from LG theres a thread somewhere and then plug your device in a different usb porn and wait for it all to install
It doesn't work for me guys. Tried reading the phone info as advised-it can't complete the operation. I get the stupid error and nothing happens. Don't know how to go around that error. Tried running the R&D tool in compatabilty mode and still got the same error.
Anyone else having the same issue?
wm2485 said:
Works!!! Just follow the steps exactly. My wife has a p999dwp and I have a p999dw. Ive been trying to get Gingerbread on hers for two days now (the official way). I can now find one complaint about the update, I love it. I haven't used Bluetooth yet though. Thanks so much.
Click to expand...
Click to collapse
Do you guys click on read phone info button on the second screen as well? That's where I am getting the Chiptype Error. Have you guys tried that? I am afraid if the tool doesn't read the phone info it won't be able to update it properly and I may brick my device. Any advises?
dude i cannot get B2Cappsetup to run! sucks it just stops quarter of the way
Did you install the msi file in the kdz folder... And I only clicked read phone info at the beginning ..
Sent from my LG-P999 using XDA Premium App
try skipping the read info and just click start upgrade.
sarni84 said:
dude i cannot get B2Cappsetup to run! sucks it just stops quarter of the way
Click to expand...
Click to collapse
Does it give some kind of an error? What kind of windows are you running?
Try rebooting your PC and reinstalling it... Only thing I did was downloaded the LG updater the other day and reinstalled it ... after it installed I connected my phone and it installed some drivers...
Sent from my LG-P999 using XDA Premium App
I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)
need more info
what model number do you have, what can you get into, what cant you get into etc
lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90
i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision
Hi,
I was trying to root and install a custom rom on a friends phone. She has T-Mobile Galaxy S 4G. I was rushing through the whole project cause I had work and accidentally installed T-Mobile Vibrant Stock 2.1 using Heimdall. It was my fault. I did a google search for SGH-T959, but failed to realize that SGH-t959U is Vibrant and SGH-T959V is Samsung Galaxy S 4G...
After flashing the wrong ROM, I could not get it back into Download mode. I removed the SIM, SD card, Battery, and then tried putting it back into download mode (without the SIM or SD card) and that worked. I was able to get it into download mode at that point, but it would still not turn on or boot into recovery.
After realizing it was the wrong Flash, I searched online and found this http://forum.xda-developers.com/showthread.php?t=1358498 , after searching for users who bricked their phone previously and this was listed as a solution... the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Read the second link in my signature and see if it helps you with Heimdal.
lumin30 said:
Read the second link in my signature and see if it helps you with Heimdal.
Click to expand...
Click to collapse
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
JGonzo1299 said:
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
Click to expand...
Click to collapse
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Just replying to the OP... Still follow the instructions in my previous post.
JGonzo1299 said:
the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
Click to expand...
Click to collapse
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
JGonzo1299 said:
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
Click to expand...
Click to collapse
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
JGonzo1299 said:
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Click to expand...
Click to collapse
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
bhundven said:
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Click to expand...
Click to collapse
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
bhundven said:
Just replying to the OP... Still follow the instructions in my previous post.
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
Click to expand...
Click to collapse
Yeah i followed Vibrant instructions on accident. It was a careless mistake. Ill ignore the CSC error then and Ill try using a different USB port. My usb cable is brand new from my SIII. I don't think its a problem. But my mac USB ports are pretty old.
JGonzo1299 said:
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
Click to expand...
Click to collapse
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
bhundven said:
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
Click to expand...
Click to collapse
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
JGonzo1299 said:
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
Click to expand...
Click to collapse
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
When i originally encountered the problem. I downloaded the 'back to Factory stock rom' for vibrant. It was an ODIN file so it was .tar, I downloaded its associated PIT file.
I loaded the PIT file into heimdall under the 'flash' tab
i extracted the .tar file and found 6 files. i took each file and loaded them individually to heimdall 1.3.1 under the 'flash' tab.
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Once I flashed those it wouldnt boot and was just black. could only go into download mode.
Then I realized i messed up and used the wrong ROM.
Came into this thread for SGS4G
Found the right files.
Phones been broken since and ive been following the instructions listed above. hope that makes sense. im at my work desk. sorry. Ill try to find the link of the go back to factory stock file i found on the vibrant forums but it was whatever vibrant came with out of the box. and it was a verified stock ROM. I just followed the instructions to the T until I encountered problems.....
bhundven said:
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
Click to expand...
Click to collapse
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
JGonzo1299 said:
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
Click to expand...
Click to collapse
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
bhundven said:
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Click to expand...
Click to collapse
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
champ1919 said:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
Click to expand...
Click to collapse
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
JGonzo1299 said:
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
JGonzo1299 said:
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Click to expand...
Click to collapse
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
hechoen said:
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
Click to expand...
Click to collapse
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
champ1919 said:
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
Click to expand...
Click to collapse
Thank you. I'm going to try this after I try what i just posted above first. Will post results later tonight around 11 EST. Work computer wont let me download any links.
JGonzo1299 said:
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
Click to expand...
Click to collapse
Yes that is what I mean.
I don't own a vibrant so I have know idea what dbdata is for. Maybe someone will chime in with a better answer. Doing it this way you should be able to get the phone back to where it was. Again this is my best guess at how to try to fix it. Plus it's really hard to brick a brick(bad joke I know but i had too).
Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.3
for your AT&T Samsung Galaxy Express
Read this whole post before doing anything
Enjoy
Odin Flashable - OUDHS CWM-based Recovery 1.0.3.3
Odin 3.04
Drivers
Directions:
1) Download the above files
2) Extract Odin3-3.04.zip and copy the tar that you downloaded into the folder
3) Run Odin as an administrator
4) Power your device off
5) Press and hold volume down and power to enter download mode
6a) Connect your phone to your computer
6b) Wait for drivers to finish installing if they need to be
7) You should see Odin find your device by marking a blue square in the ID COM box
8) Click on PDA and choose the recovery tar you downloaded
9) Click start
-----------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now if you wish to root youll need to follow these instructions
-----------------------------------------------------------------------------------------------------------------
SuperSU+ 1.25
Directions:
1) Download the above file
2) Connect your phone and copy them to your phone
3) Once they are copied power down your device
4) Hold volume up and power to enter Clockworkmod recovery
5) Navigate recovery by using the volume keys and power to select
6) Choose install zip from sdcard, then pick internal or external (where you copied it to)
7) Scroll down to the SuperSU+.zip and select it to install
-----------------------------------------------------------------------------------------------------------------
Congrats you are rooted! this procedure will work on any firmware update you guys get
-----------------------------------------------------------------------------------------------------------------
If you enjoyed getting root/recovery and want to show appreciation you can always buy me a coke
Source
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) For being the best we can for those whom need us
rdawson28 For being an awesome tester
BlindArtisan For providing the stock recovery, thanks man
I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.
Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?
BlindArtisan said:
Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?
Click to expand...
Click to collapse
www.shabbypenguin.com/OUDstuff/Samsung/ATT/Express/Express-OUDHS-CWM.tar
Thank you. An alternate way to install for those who are rooted and don't want to use Odin.
Create a copy of the recovery on your sdcard.
In the android terminal or adb with shell type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
To make the recovery permanent.
Find /system/etc/install-recovery.sh
Rename the file install-recovery.sh.backup
Reboot into recovery and enjoy the glory.
Sent from my rooted SAMSUNG-SGH-I437 using xda app-developers app
JDC2389 said:
I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.
Click to expand...
Click to collapse
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.
Sworder said:
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.
Click to expand...
Click to collapse
You could always uninstall the drivers then install fresh ones from Samsung. Or use the in phone method.
Sent from my rooted SAMSUNG-SGH-I437
I has to uninstall then put the fresh drivers on thats the easiest way
Sent from my SAMSUNG-SGH-I437 using xda app-developers app
Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.
invert_nexus said:
Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.
Click to expand...
Click to collapse
I have the exact same issue with the date.
I don't quite understand what you are saying, but It doesn't try to fix root on boot it tries to fix the recovery.img
Sent from my rooted SAMSUNG-SGH-I437
Thanks blind you came through for me, that way I didn't have to worry about my phone being recognized in download mode. Nice job on the recovery it looks fantastic.
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Someone needs to make a video about this root method to spread the word and upload it to youtube!
Worked flawlessly on a new phone. A 6 month old one, all appears ok, it sees the phone, odin loads the image, phone reboots ok. When I try try to reboot into recovery mode I get the stock recovery, not CWM.
Any ideas?
guys i am so sorry, i had to reinstall linux and thought i lost teh device t ree, anyways i compiled a new version of OUDHS recovery for yall. and finally uploaded source
Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?
invert_nexus said:
Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?
Click to expand...
Click to collapse
source is at the link
and there is a good deal different in the latest version. honestly i suggest everyone upgrades
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
Havent updated yet but sounds like the same problem as before ill test tomorrow been really busy also gonna work on the cooked up rom more when I get a chance im sure the recovery issues will be fixed shortly
Sent from my SAMSUNG-SGH-I437 using xda app-developers app
invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
the time will always be off, recovery doesnt talk to the rest of the phone. crap, did that get fixed? or was it always broken?
shabbypenguin said:
the time will always be off, recovery doesnt talk to the rest of the phone.
Click to expand...
Click to collapse
Odd. Is that just an ussue with this phone?
crap, did that get fixed? or was it always broken?
Click to expand...
Click to collapse
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.
invert_nexus said:
Odd. Is that just an ussue with this phone?
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.
Click to expand...
Click to collapse
the time this is android wide afaik. twrp and official cwm have teh same bug :/
and crap that means some of the new features broke stuff for yall :/ ill put the old on back up in the OP i was really hoping to give you guys touch recovery
KitKat the EASY Way!!!!
Or, go back to 4.2.2 JellyBean
If you are going to return your phone back to warranty, I would suggest this method in this thread as it does a COMPLETE wipe of your device and puts it back to 'Factory'. It removes Root Flags so it does not show having been rooted, and removes ALL data.
Disclaimer: This is not MY method, but a method I used. The information and files have been figured out over time by many individuals and it's been combined in this thread.
This thread is to help Noobs AND Veterans to flash their ATT D800 LG G2 to KitKat. This will be very spelled out, and I’ve even included a video (see below), so NO Mistakes. Yes, that means you!
PLEASE refer to the Video Below before asking questions, as too many questions get a little overwhelming.
Warning! Please Read!
This WILL erase everything on your phone and put it back to FACTORY STATE, so be sure you’ve backed up!
Ok, first thing you need to do is download the version you want. I’ve got KitKat 4.4.2 version D80020c, and I’ve got JellyBean 4.2.2 version D80010o. These are VERY LARGE files, so be patient, although I am able to get as much as 6MB/s download speeds from this server.
BIG THANKS TO bigfau for the KitKat TOT and DLL files!!!
Download Installer - KitKat 4.4.2 D80020c - This Flashes Stock KitKat, WITHOUT Root, and WITHOUT Recovery. - Use TowelRoot and AutoRec to get Root and Custom Recovery. - Single File LARGE archive. KK MIRROR DOWNLOAD
D80020c Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download.
Download Installer - JellyBean 4.2.2 D80010o - Single File LARGE archive. JB MIRROR DOWNLOAD
D80010o Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download..
Download Installer - JellyBean 4.2.2 D80010d - This is for those who want to install Custom Recovery and not update to KK... - Single File LARGE archive.
Now, for the fun stuff (You may want to print this out for reference and check them off as you go)
Pre-requisites:
1. Be sure your phone is currently running a Compatible based ROM. If not, please flash a Custom Compatible Based ROM onto your phone. (ie: If you have a D800, be sure you have a D800 ROM on it. If you have a D802, be sure you have a D802 based ROM on it.)
2. Be sure you have turned on USB Debugging before starting.
Step #1: Program Installation:
1. Save the installer to your desktop
2. Run the Installer by double clicking
3. Wait a while for everything to extract (It might look like nothing is happening. This can take a few minutes, be patient, it’s HUGE)
4. (On Win7 or Win8, Accept User Account Control)
5. Accept my License
6. Don't Change Anything and click ‘Install’
7. Wait some more… and more… Large files are extracting…
8. When it pops up, click ‘Next’ to install the LG drivers. Even if you’ve already installed them, install again! This is to verify you’ve got the right ones installed.
9. Click ‘OK’ to finish the Driver install
10. Click ‘Next to install the LG Flash Tool
11. Don't Change Anything and click ‘Install’
12. Uncheck ‘Run LGFlashTool 1.8.1.1023 and click ‘Finish’ (If you forget to uncheck this, just close the program when it opens)
13. Click ‘Next’ to start the LGFlashTool Patch. (This makes it so you don’t need to change the date back on your PC)
14. Click ‘Next’ again
15. Click the bullet to ‘Agree to my License’ and then click ‘Next’
16. Don't Change Anything and click ‘Next’
17. Click ‘Start’
18. Click ‘Next’
19. Click ‘Exit’ to finish Patch Installer
20. Congratulations, Program Installations are all DONE!
Step #2: Place Phone into Download Mode:
1. With phone NOT plugged into a USB Cable, Hold the Power button to turn off phone
2. Plug your USB cable into your computer
3. Hold the Volume UP Button on your Phone
4. While Still Holding the Volume UP button, plug in the USB cable to your Phone
5. Continue to hold the Volume UP button until your phone enters Download Mode
6. If this does not work, pull the USB cable and start from #1 of this section
Step #3: Change Com Port to 41
1. With your phone STILL in Download Mode and STILL Plugged into Computer
2. Go into Device Manager
---a. Press and hold your Windows Key (Between CTRL and ALT)
---b. Tap the ‘Pause/Break’ Key (Usually Top Right of Keyboard, might be different on yours)
---c. Click on ‘Device Manager’
3. In the Device List, scroll down to ‘Ports (COM & LPT) and double click to expand
4. Find the ‘LGE AndroidNet USB Serial Port (COM4)’ (Your COM Port Number might be different, that’s OK)
5. Double click to open the port
6. On the Tabs at the top of that screen, click on ‘Port Settings’
7. Click on ‘Advanced…’
8. Click on the Com Port number to drop down the list
9. Scroll down to ‘COM41’ and select it
10. Click ‘OK’ Button to save that
11. Click ‘OK’ Button to close the Com Port Properties
12. Close the Device Manager
13. Close the System Window
14. Go back to the Desktop
15. That’s it, You’ve Changed the Com Port to 41
Step #4: Run LGFlashTool:
1. Double Click the ‘LGFlashTool’ icon on the Desktop (Win7 or Win8 accept ‘User Account Control’)
2. In the ‘Model Config’ window, check the box ‘Select Manual Mode’
3. Next to the DLL space, click the Three Dots ‘…’
4. Select the DLL file named ‘LGD800_.....v160.dll’
---a. For 4.4.2 KitKat, select ‘LGD800_20130811_LGFLASHv160.dll’
---b. For 4.2.2 JellyBean, select ‘LGD800_20130904_LGFLASHv160.dll’
5. Click the ‘Open’ Button
6. Next to the S/W space, click the ‘Remove ALL’ Button
7. Next to the S/W space, click the ‘Add’ Button
8. Select the tot file for the version you are flashing
---a. For 4.4.2 KitKat, select ‘LGD800AT-01-V20c-310-410-FEB-02-2014+0.tot’
---b. For 4.2.2 JellyBean, select ‘LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot’
9. Click the ‘Open’ Button
10. Click ‘OK’ Button to save choices
11. In the LG FlashTool program, click the ‘Yellow Arrow’ pointing to the Right.
12. Wait for the program to verify your DLL and TOT selections (This takes a while)
13. If successful, you will see ‘READY!!’ on ‘Port 1 (COM41)’
14. If you DON’T see ‘READY!!’, you may need to start over
15. If you see ‘READY!!’ unplug your phone from the USB cable and Plug it right back in. DO NOT PRESS ANY BUTTONS ON YOUR PHONE. It should STILL be in Download Mode.
16. The LG FlashTool progam will now start flashing your phone!!
17. At around 80%, the program will restart your phone.
18. It takes a while for the phone to restart, but it will boot to Android. Wait for the flash program to finish and it will turn your phone back OFF. And give you a ‘SUCCESS”
19. Close FlashTool
IF for some reason, the LG FlashTool does not finish 100%, and you get a ‘Fail’, as long as your phone has now rebooted into Android, you don’t need to worry about this. Just close the program, and enjoy your Freshly Restored LG G2!
For anyone having issue with the device check not passing due to mismatched device (caused by flashing a Custom ROM with Different device model ID to your D800: ie, D801 to a D800 or vice versa.), try using the attached dll file instead of the device specific one. It has been reported to work for many... You will need to extract the zip file to get the dll.
good stuff bud!
Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies
Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.
epapsiou said:
Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies
Click to expand...
Click to collapse
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
BAM1789 said:
Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.
Click to expand...
Click to collapse
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
You my friend are a very nice person lol. Taking the time to put this together.
Sent from my LG-D800 using Tapatalk
SuperSport said:
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
I haven't had my G2 very long so I haven't been able to test myself, but just looking around the forum seems the 10o firmware causes boot issues with some custom ROMs. I could be wrong though. Maybe the problem doesn't exist anymore and I'm reading old info.
SuperSport said:
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.
epapsiou said:
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.
Click to expand...
Click to collapse
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
SuperSport bro u made my life so much easier. Thank u for your hard work bro.
Sent from my LG-D800 using Tapatalk
SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.
epapsiou said:
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.
Click to expand...
Click to collapse
I'm having the same issue flashing any stock based rom on 800o. It throws me in a bootloop. How would I get the 800d fw?
Sent from my LG-D800 using Tapatalk
SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.
Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.
Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app
Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?
Sorry Everyone, I've been out of town and only on my phone, but mostly busy with family stuff.
freebee269 said:
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.
Click to expand...
Click to collapse
Thank you for the clear info. I will build a 10d version. Hopefully tomorrow.
strose09 said:
Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.
Click to expand...
Click to collapse
I'm sorry, I have been away from home. Just read this. Yes, you are fine if your phone is rooted. This Flash will remove Root. As mentioned in the First post, there is currently no way to root KitKat, (Unless I've missed something since last night). So root, then go to KitKat.
mjgspr95 said:
Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Some people have issues with Internet Explorer on Mega Website. You might install Chrome or Firefox and try it that way, or use a Download Manager of your choice.
humblehyper said:
Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?
Click to expand...
Click to collapse
That is Correct, no Custom Recovery. Not unless something has appeared since last night when I last went through the forums.
Usefull guide thanks
but i think there is not a difference between those Flash DLL i had 20130904 and just freshy flashed KitKat
also if anyone cares about a LG Flash tools "PASS" then while it stops on 80-94% and boot into OS itself, do a Factory Reset of phone and it will check a Factory Flag (it sets to 5) and gives message a PASS
Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk
pcoruganti said:
Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Oh but indeed it is.
Sent from my LG-D800 using Tapatalk