Hello, Guys. So I did a stupid thing today - I was poking around in the build.prop in my v20d P769. I changed the value of a line concerning the battery, something like "battery_genuine" - My thought was that it was going to enable some sort of alternate battery notification or icon or whatever, I'm not sure what I was thinking.
Anyway, long story short, I rebooted after editing build.prop and now when the phone turns on it just says "use genuine battery - powering off" and shuts off. I had previously uninstalled CWM (getting ready to manually apply v20f) so I can't get to recovery to mount /system. I have been trying all day to get the offline flash method to work and the damn thing won't work half the time. I went through the thread instructions to install small server and edit hosts file - then reboot - when the loopback ip's are in the hosts file the test link on the thread (127.0.0.1:9002) doesn't work and neither LG application will work. If I comment out the loopback lines and restart both of them will open but neither of them will do anything useful. LG Updater tool just says I have the latest software and the UptestEX_mod2_marwin application won't flash anything.
Hoping someone can help me out here so I can recover this phone.
boot the phone in fastboot mode, don't know how to do that with your model though
use fastboot to boot into any custom recovery by typing 'path_to_adb_toolkit_files\fastboot.exe boot your_recovery_image.img'
if fastboot hangs on <waiting for device> install usb drivers
then pull off build.prop, change that field to original value and push it back into the phone
sorry mate, can't explain more detailed
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply man - yeah I can't get to adb, that was my first though so i'm going to try fastboot, only problem is, I don't know how to boot fastboot. Is s/w upgrade mode the fastboot screen (volume up + plug in cable)?
Also, would anyone mind explaining why the small server only outputs "file not found" when attempting to start up the flash tool? The only way I can get the flash tool to even launch is to comment out the loopback lines in hosts. lol man it's times like this when I miss motorola!
*Edit - In case anyone wants to help on this front, here is the output I receive from small server when trying to open B2CappClient or UpTest or even hit the test link in the offline flash thread:
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 4) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 5) >HTTP in:279 out:1993 Time:31
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 6)
GET /favicon.ico HTTP/1.1
Host: 127.0.0.1:9002
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 7) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 8) >HTTP in:279 out:1995 Time:94
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 9)
GET /client/app/live_update.jsp HTTP/1.1
Host: csmg.lgmobile.com:9002
Cache-Control: no-cache
^!!
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 10) >\client\app\live_update.jsp(Undefined/default)
Error. File not found.
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 11) >HTTP in:99 out:2012 Time:62
I recommended removing all lg drivers and etc. Redownload all files, disable firewall and antivirus. But first you need to install fastboot and flash the u-boot for ice cream.
Inside the fastboot zip by lelus is more instructions on how to set it up. And checkout the original thread about fastbooting the l9
And you might want to try on another PC,
You need a good and clean windows environment for all to work well. This is the problem with many people. Plus a lot of antivirus programs don't like the small server.
Sent from my LG-P769 using xda app-developers app
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
SuicideFlasher said:
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
Click to expand...
Click to collapse
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
peoplegetpeople said:
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
Click to expand...
Click to collapse
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Finally got it! :laugh: Turns out, the default path for small server is c:\shttps\www - the problem I gave myself is that when I didn't extract to the c root, I copied from my L9 directory - when I copied none of the contents of \www copied with it, once I moved those files to the correct position it all went through as it should!
Thanks for your help guys!!
kuma82 said:
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Click to expand...
Click to collapse
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
peoplegetpeople said:
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
Click to expand...
Click to collapse
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
kuma82 said:
I didn't have a hard time, but then again I've studied my a** off, and I knew how to fix all problems that popped up. My advice to you is read all the threads about unlocking the bootloader. The video is good but it doesn't break it down enough.
Let me tell you about everything that can go wrong and how to fix it
Problems
1. After flashing the euro kdz your phone won't boot past the logo.
Okay, this problem will make things harder(but do able), because you have to hard reset the device by pressing/holding the vol (-) + home + power (let go of power button when the lg logo comes up)
Plus after a hard reset all data will be wiped and you will have to enable USB debugging on the wonky touch screen.
The chance of this happening is rare because you are not coming from a custom ROM.
2. After flashing you get a security error (or an error during the flashing process).
Now this one sucks because you will need to fastboot and flash the ice cream u-boot. Then put the phone in the s/w upgrade mode and perform the offline flash again.
I had this happen to me once, while flashing the wind kdz. Messing with fastboot is not hard but it takes time to understand it. Get familiar with it first before trying to unlock. I'll send you a link with some more info.
3.After flashing the euro kdz you find out you don't have root.
Sometimes rooting fails (dam computers)
Now I had this happen to me after flashing euro kdz (so no cwm) but I wasn't really worried about that because I had a signal and I could make/receive calls. I had a signal because when I was flashing I swapped out the euro radio (p760.fls) with the metropcs one (lgms769.fls)
Note: you have to extract the radio from the metro kdz and rename it to p760.fls
When flashing replace the 11th bin (with hex edited 11th bin for 20b) & the radio (from metro renamed).
Another thing don't rush the unlock. I waited about 3 to 4 hours before trying, plus I took a couple of calls on the 20b kdz. And I was on wifi.
I flashed the euro kdz at work and when I got home I turned on WiFi and waited another hour.
I'm not to sure about what the video says about turning off and flashing the radio.
When the unlock first came out, the instructions were to not turn off the device before unlocking.
When I flashed the euro kdz I was on the metropcs ROM.
This is what I recommend and did.
Enable USB debugging, show all touches, & allow install from unknown sources.
Leave your phone on normally(don't put it in s/w mode) and flash the euro kdz and hopefully no problems.
After waiting a couple of hours try the unlock command with Adb on your PC.
If all goes good the phone will take you to an inverted unlock screen, just press the volume up (make sure you press the Up button!)
This will take you to the official fastboot (but it's inverted), now in fastboot flash the cwm recovery image.
In cwm flash the touch screen fix and restore a backup.
Another thing make your own backup with the locked bl cwm (just in case you have to erase all data) make backup on external SD. Another thing, Lol ,make sure the backup is good, try to restore it. I have had several corrupted backups with cwm.
I know it's a lot to learn, but then again you want to be prepared.
Think of it like a final exam, Lol and you won't go wrong.
If you get lost just holla at me.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
CM 10.1 P769
kuma82 said:
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
CM 10.1 P769
Click to expand...
Click to collapse
Wow man! Awesome response, really appreciate your input and explanations. It really takes some of the unknown out of it. Thanks!
Sent from my LG-P769 using xda app-developers app
httGeneric Procedure - Turn on " Fake Battery Mode " ( Bypass Genuine Battery Test ).
Boot Error ( " Use Genuine Battery " -power off- )
Entered here since procedure seems to be generic " Turn on Fake Battery Mode " (Bypass Genuine Battery Test).
>> Also called Service Menu: Type in: ##LGSERVICEMENU send (##5473784296368) on the dialpad.
>>enter the security code: 000000, locate: SW/HW Tests or HW test or SW/HW Versions
>> find "bypass booting" in menu locate "fake battery mode" select it and choose on.
--- My phone LG Optimus G Pro E980 (note: the 980 in code refers to model)
when approx 90-95%, with new gold 4200mAh battery Boot up Error ( " Use Genuine Battery " -power off- )
so, i went into hidden menu 3845#*980# ->Settings->Battery->Battery Fake Mode (Turned it ON), seems to be fixed.
By the way, the gold battery tested WORSE THAN 3140mAh OEM, Save yourself time, buy the Quality LG OEM.
Related
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
thchipmunk said:
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
Click to expand...
Click to collapse
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
kuma82 said:
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I just tried it and I get an error"
Updating is not possible any longer due to a fatal error while the LG Mobile Phone Software Update.
Click to expand...
Click to collapse
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
When I do the recovery it returns my phone as a P769BKGO if that helps with anything.
thchipmunk said:
Thanks for the suggestion. I just tried it and I get an error"
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
Click to expand...
Click to collapse
What os are you running also what kdz are you trying to flash ?
Lelus said:
What os are you running also what kdz are you trying to flash ?
Click to expand...
Click to collapse
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
thchipmunk said:
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
Click to expand...
Click to collapse
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Lelus said:
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Click to expand...
Click to collapse
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
thchipmunk said:
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
Click to expand...
Click to collapse
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Lelus said:
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Click to expand...
Click to collapse
I'll reboot and then try that again. I'll check back afterwards.
Should I do anything extra like start the offline flash from scratch as far as drivers? I'm not even sure where to begin in regards to what drivers/files to remove.
Thank you! Thank you! Thank you!
Now I just need to figure out the screen calibration.
Also, what can I do with this now? Do I need to unlock the bootloader to load custom ROMs without getting a security error?
Sorry for my lack of knowledge. My last phone was a Bionic and that was the easiest phone to root and add a ROM to.
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Odds are, you are doing nothing wrong. Check your android version, if you are on 4.2+ (JellyBean) you can't unlock your bootloader quite yet. Here is the thread you should keep track of at the moment http://forum.xda-developers.com/showthread.php?t=2277639&page=152
Insert battery more quickly
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
mven45 said:
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
Click to expand...
Click to collapse
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
maso321 said:
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
Click to expand...
Click to collapse
If you're running a Windows 8 OS, that's the reason it's not working.
Sent from my LGMS769 using XDA Premium 4 mobile app
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Nathan.7118391 said:
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Click to expand...
Click to collapse
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
I'm trying to restore my P769 to stock (Stuck LG logo), and getting nowhere.
How did you get the flash to work? What error did you get when the phone would turn off? How did you get the inverted S/W mode?
My phone only got to 17-20% before getting an connection error using the offline booth method, this was with both JB and ICS u-boot/boot/recovery .imgs from the P769 ROMs--should I try the steps in unlocking the bootloader to at least get to a bootable state?
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
How did you solve this? I am at the same steps, I get into mirrored software mode and then I attempt the offline fix. I have even started the offline fix early to save time. And yet it will only stay on for 2 and a half minutes or so and then shuts off. The farthest i have been able to get it to go is 41%. I have tried fastboot mode to try and send boot.img and it just says that it cannot find the boot partition. So it looks like my only option is the offline fix but it doesn't have enough time to complete. I have tried about 20 or so times how many tries did it take for you? Did you do anything special to get it to finish? any advice on how to get it to finish? Spent about 6 hrs last night trying to get this phone back up and running and this is where i am stuck. Its lame cuz i woke up to the phone like this it was fine when i went to bed. And was for months.
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
Okay guys, I think my phone has a soft brick (no boot logos), so I'm trying to do some restoration... but I'm not having much success.
So, I found a solution in XDA (/showthread.php?t=825173&page=3) saying that I should plug my phone in without battery, SD nor chip and disable the "LG Modem" on my Device Manager. Afterwards, start KDZ Updater and configure it to CS_EMERGENCY. Then I should install a 2.1 French firmware and as soon as KDZ finishes I'd plug off my phone, plug it back in and start it in DL mode again, this time flashing a file named "OUT.kdz", which gives back the boot logos.
Problem: KDZ Updater hangs as soon as I press "Start". It simply freezes when it's in CS_EMERGENCY. I have no solution to this whatsoever, and I also have another thread with previous problems I ran into (Soft-Bricked LG GT540 Optimus).
These are the best forums I've found for any kind of phone, so I'm positive I'll get the help I need, even if I might need to wait some time. Kudos to the admins and every member for taking part of such a great community!
Ebony Dubois said:
Okay guys, I think my phone has a soft brick (no boot logos), so I'm trying to do some restoration... but I'm not having much success.
So, I found a solution in XDA (/showthread.php?t=825173&page=3) saying that I should plug my phone in without battery, SD nor chip and disable the "LG Modem" on my Device Manager. Afterwards, start KDZ Updater and configure it to CS_EMERGENCY. Then I should install a 2.1 French firmware and as soon as KDZ finishes I'd plug off my phone, plug it back in and start it in DL mode again, this time flashing a file named "OUT.kdz", which gives back the boot logos.
Problem: KDZ Updater hangs as soon as I press "Start". It simply freezes when it's in CS_EMERGENCY. I have no solution to this whatsoever, and I also have another thread with previous problems I ran into (Soft-Bricked LG GT540 Optimus).
These are the best forums I've found for any kind of phone, so I'm positive I'll get the help I need, even if I might need to wait some time. Kudos to the admins and every member for taking part of such a great community!
Click to expand...
Click to collapse
I've fixed all my issues! I'll paste what I said in another thread. Yay for one-full-year struggles!
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack