I tried rooting my LGP-769 (originally 20f) using a bin and KDZ for 20d. Halfway through, the software (on the PC) crashed, and now my phone is stuck at "S/W Upgrade" screen. It no longer appears in device manager, and the LG software used for flashing does not see it as connected, so I can't flash anything back that way. Things that I've tried:
Hard boot: no change, still stuck at S/W upgrade
Leave battery out for 15 min: no change
Can't flash because device no longer exists in Dev Manager
Do I have any options here? What went wrong?
Thanks in advance. I've only been a smartphone owner for a week and I'm worried that I've already ruined my device.
I can fastboot (just gets to mirrored LG logo), but this does not allow access to any software, nor does this change anything in device manager or the LG recovery tool.
http://forum.xda-developers.com/showthread.php?p=44756934
CM 10.1 P769
kuma82 said:
http://forum.xda-developers.com/showthread.php?p=44756934
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the tip! Unfortunately this did not work for me; I posted details of how it failed in that thread, but the short story is that LG's KDZ-uploading tool does not see the phone as connected, even though the OMAP fastboot device does appear in windows' device manager. Do you have any other thoughts on how this might be fixed?
Are you sure you flashed the ice cream x & u? Try doing in manually to make sure?
CM 10.1 P769
kuma82 said:
Are you sure you flashed the ice cream x & u? Try doing in manually to make sure?
CM 10.1 P769
Click to expand...
Click to collapse
I tried ICS and JB in the fastboot utility for all models on the file (p760, 768, 759 I think); none worked. Which is to say that the phone looked like it fastboot'd (according to display and dev manager), but the LG utilities (used for KDZ flashing) would always say the phone is disconnected.
What do you mean by doing it manually? I haven't seen an option like that before - interested.
When you fastboot and choose 769 ics x and you you should see it say its copying x and u. Doesn't sound like it went through proper. I have wiped completely the boot partition and flashing those 2 make it recognize the phone again.
Sent from my LG-P769 using xda app-developers app
quickfastgoninja said:
I tried ICS and JB in the fastboot utility for all models on the file (p760, 768, 759 I think); none worked. Which is to say that the phone looked like it fastboot'd (according to display and dev manager), but the LG utilities (used for KDZ flashing) would always say the phone is disconnected.
What do you mean by doing it manually? I haven't seen an option like that before - interested.
Click to expand...
Click to collapse
Instructions for doing it manually.
http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
Note: if you get type
fastboot devices and nothing comes up, you might not have installed the drivers twice. If you do see fastboot installed in two locations, let me know you might have another issue.
CM 10.1 P769
kuma82 said:
Instructions for doing it manually.
http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
Note: if you get type
fastboot devices and nothing comes up, you might not have installed the drivers twice. If you do see fastboot installed in two locations, let me know you might have another issue.
CM 10.1 P769
Click to expand...
Click to collapse
Thanks, I'll give that a shot tonight. What does the poster mean by "images" to move into the folder - KDZs?
quickfastgoninja said:
Thanks, I'll give that a shot tonight. What does the poster mean by "images" to move into the folder - KDZs?
Click to expand...
Click to collapse
Lol I am the poster, I extracted the images .img files. You have to download the files (.img s)and put them in the "yours" folder. Open the fastboot (lelus) folder and inside you will find another folder named yours.
CM 10.1 P769
kuma82 said:
Lol I am the poster, I extracted the images .img files. You have to download the files (.img s)and put them in the "yours" folder. Open the fastboot (lelus) folder and inside you will find another folder named yours.
CM 10.1 P769
Click to expand...
Click to collapse
Whoops! Sorry about that...
Ok, flashed following those procedures with those IMGs. Tried using LG Mobile Support Tool --> Upgrade Recovery, but that still hangs as usual. I'll try the Lelus method for flashing V20D kdz next. I'm guessing I should let it return to S/W Upgrade mode, and not try to keep it fastboot'd for this?
Thanks again.
More info on fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
CM 10.1 P769
Ok, I tried both LG update tool's recovery as well as the offline flash method - each of these in both fastboot mode as well as S/W upgrade (after fastboot + reset) - no luck, unfortunately. Update tool hangs, and offline flash says cell phone is not connected.
I've never seen fastboot drivers in more than one location in dev manager though - never saw it listed under "TI boards"? I had thought that fastboot was successful because [fastboot devices] command lists the device as connected (following manual IMG flashing).
quickfastgoninja said:
Ok, I tried both LG update tool's recovery as well as the offline flash method - each of these in both fastboot mode as well as S/W upgrade (after fastboot + reset) - no luck, unfortunately. Update tool hangs, and offline flash says cell phone is not connected.
I've never seen fastboot drivers in more than one location in dev manager though - never saw it listed under "TI boards"? I had thought that fastboot was successful because [fastboot devices] command lists the device as connected (following manual IMG flashing).
Click to expand...
Click to collapse
I never used the lg recovery tool, but I heard it takes a couple of hours to download and run. Maybe you though it was hanging, but it wasn't.
CM 10.1 P769
seriously guys help....!!!
hey guys i wanted to unlock my bootloader
was following multiple guides as when i typed "adb reboot oem-unlock" it used to reboot phn normally
i used OMAPFlash_1229_2ndlastt and did something with "uboot" after that nothing is working
no s/w mode nothing... but my pc device manager detects it...
seriously guys help....!!!
Related
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.
ok, I used pimp my rom and well one little setting in the GPU area caused it to blackscreen.. so I decided to just clear the phone hard reset.. but no luck.
so now im stuck, LG comes up and SW does.. but I can not get the PC to clear the phone it keeps saying usb disconnected please connect.., I was using the Metro PCS rom.. 10D I believe, but anyways anyone that can step me in the right direction would have my gratitude.. ive tried the lelus method.. and just not working right.. maybe its the drivers.. but I made sure all of them are installed..
Cobra11Murderer said:
ok, I used pimp my rom and well one little setting in the GPU area caused it to blackscreen.. so I decided to just clear the phone hard reset.. but no luck.
so now im stuck, LG comes up and SW does.. but I can not get the PC to clear the phone it keeps saying usb disconnected please connect.., I was using the Metro PCS rom.. 10D I believe, but anyways anyone that can step me in the right direction would have my gratitude.. ive tried the lelus method.. and just not working right.. maybe its the drivers.. but I made sure all of them are installed..
Click to expand...
Click to collapse
Leave your phone on while performing the offline flash, don't put it in s/w mode first. Your phone will go into s/w upgrade mode on it's own. Oh and use my modified/hex edited 11th bin
kuma82 said:
Leave your phone on while performing the offline flash, don't put it in s/w mode first. Your phone will go into s/w upgrade mode on it's own. Oh and use my modified/hex edited 11th bin
Click to expand...
Click to collapse
no go, i got a video ill put up in a bit, if i unplug it in SW mode and plug it back in i get close, but then when it starts flashing the program crashes...
I can not get it to flash while its on regular.. it keeps saying check usb, the phone its self starts up then goes to LG then a blank screen no metro or tmobile.., there is no feed back when you press the screen either, if you try to hard reset it only restarts the phone..
Cobra11Murderer said:
no go, i got a video ill put up in a bit, if i unplug it in SW mode and plug it back in i get close, but then when it starts flashing the program crashes...
I can not get it to flash while its on regular.. it keeps saying check usb, the phone its self starts up then goes to LG then a blank screen no metro or tmobile.., there is no feed back when you press the screen either, if you try to hard reset it only restarts the phone..
Click to expand...
Click to collapse
have you check if the kdz is named properly (all caps) eg. V10G_00.kdz
if it's like this v10G_00.kz it will not work.
kuma82 said:
have you check if the kdz is named properly (all caps) eg. V10G_00.kdz
if it's like this v10G_00.kz it will not work.
Click to expand...
Click to collapse
yup all caps, hmm, this is tricky
It might be corrupted try downloading it again. which version is it? I might have it and if I do i'll give you the checksum fof it.
kuma82 said:
It might be corrupted try downloading it again. which version is it? I might have it and if I do i'll give you the checksum fof it.
Click to expand...
Click to collapse
I have the same problem, I have installed a wrong kdz and I try to install another one now but it returns me an error: usb and cellphone are not connected, or something like that, at 15% of instalation.
And my phone is in s/w mode with all drivers installed.
Soulwisher said:
I have the same problem, I have installed a wrong kdz and I try to install another one now but it returns me an error: usb and cellphone are not connected, or something like that, at 15% of instalation.
And my phone is in s/w mode with all drivers installed.
Click to expand...
Click to collapse
Plesae left your phone turn on and put it in LG software mode. Then in R&D Flash tool select DIAG mode instead of EMERGENCY. You phone should boot to S/W update mode automatically.
artit said:
Plesae left your phone turn on and put it in LG software mode. Then in R&D Flash tool select DIAG mode instead of EMERGENCY. You phone should boot to S/W update mode automatically.
Click to expand...
Click to collapse
I cannot start my phone! Because I have installed a wrong kdz.
My phone does not boot, I can only enter the S/W Mode.
Soulwisher said:
I cannot start my phone! Because I have installed a wrong kdz.
My phone does not boot, I can only enter the S/W Mode.
Click to expand...
Click to collapse
OK. Two options to solve this problem.
1. You can use LG Mobile support tool to recover your phone. Load it from LG website select recover phone from menu.
or
2. Flash ICS u boot & x-loader via fastboot. Please refer to to fastboot tool at http://forum.xda-developers.com/showthread.php?t=2292828 after that your computer should reconize your phone in S/W update mode and you can flash kdz.
artit said:
OK. Two options to solve this problem.
1. You can use LG Mobile support tool to recover your phone. Load it from LG website select recover phone from menu.
or
2. Flash ICS u boot & x-loader via fastboot. Please refer to to fastboot tool at http://forum.xda-developers.com/showthread.php?t=2292828 after that your computer should reconize your phone in S/W update mode and you can flash kdz.
Click to expand...
Click to collapse
Thank you!
sadly still doing the same thing... i must be missing something.., I was able to get it show fast boot.. but what do you do after? try flashing kdz using the tool? im still getting the not connected
Cobra11Murderer said:
sadly still doing the same thing... i must be missing something.., I was able to get it show fast boot.. but what do you do after? try flashing kdz using the tool? im still getting the not connected
Click to expand...
Click to collapse
Did you flash ICS u-boot & x-loader?
artit said:
Did you flash ICS u-boot & x-loader?
Click to expand...
Click to collapse
I flashed the jb one, do i need to flash ICS one and then flash a ics kdz?
Cobra11Murderer said:
I flashed the jb one, do i need to flash ICS one and then flash a ics kdz?
Click to expand...
Click to collapse
I mean in fastboot script by Lelus, there're option to flash ICS u-boot & x-loader. Did you flash it on your phone? Because on JB KDZ flash tool cannot detect our phone. It work fine if our phone have ICS u-boot / x-loader.
artit said:
I mean in fastboot script by Lelus, there're option to flash ICS u-boot & x-loader. Did you flash it on your phone? Because on JB KDZ flash tool cannot detect our phone. It work fine if our phone have ICS u-boot / x-loader.
Click to expand...
Click to collapse
gotcha, ok I flashed the JB u-boot & x-loader lol, no wonder.., ill try in a bit and flash the ICS u-boot & x-loader and see how that goes.. that's prob where I messed up lol
artit said:
I mean in fastboot script by Lelus, there're option to flash ICS u-boot & x-loader. Did you flash it on your phone? Because on JB KDZ flash tool cannot detect our phone. It work fine if our phone have ICS u-boot / x-loader.
Click to expand...
Click to collapse
thats what i did wrong lol, thankyou so much!, it works again!!
So I recently wanted to load a custom rom on my p769.
Unfortunately, I tried to flash a rom without actually having the bootloader unlocked (thought i did?)
Now i'm forever stuck at the "LG Security Error" screen.
I can't seem to do anything else! :'(
The only other mode I can boot into is S/W update screen (holding volume up and plugging in usb cable).
I tried to get to another mode I read about (vol up + vol down then plug usb cable for "download" mode, to no avail)
Anyway, once I do get it into sw update mode, I can't seem to do anything either way, when i try to list adb devices, none are listed, when i try to use lg mobile tool, it never connects, when i try to use kdz offline update tool, it doesn't see the phone, it just keeps trying to connect, the log freaks out at "_IsConnectedPhone Call", and just keeps trying to "connect" to phone but can't
Am I totally screwed here?
What can I do? Any help appreciated!
rotatorkuf said:
So I recently wanted to load a custom rom on my p769.
Unfortunately, I tried to flash a rom without actually having the bootloader unlocked (thought i did?)
Now i'm forever stuck at the "LG Security Error" screen.
I can't seem to do anything else! :'(
The only other mode I can boot into is S/W update screen (holding volume up and plugging in usb cable).
I tried to get to another mode I read about (vol up + vol down then plug usb cable for "download" mode, to no avail)
Anyway, once I do get it into sw update mode, I can't seem to do anything either way, when i try to list adb devices, none are listed, when i try to use lg mobile tool, it never connects, when i try to use kdz offline update tool, it doesn't see the phone, it just keeps trying to connect, the log freaks out at "_IsConnectedPhone Call", and just keeps trying to "connect" to phone but can't
Am I totally screwed here?
What can I do? Any help appreciated!
Click to expand...
Click to collapse
You're on JB, right? KDZ offline flash tool cannot detect phone in JB. you have to flash ICS x-loader/u-boot then that tool can detect your phone. please visit http://forum.xda-developers.com/showthread.php?t=2292828
For LG mobile support tool problem, it need to download rom from LG server. Have you remove/comment 1-2 line that you add to hosts file? You said it never connect that mean it don't see your phone?
artit said:
You're on JB, right? KDZ offline flash tool cannot detect phone in JB. you have to flash ICS x-loader/u-boot then that tool can detect your phone. please visit http://forum.xda-developers.com/showthread.php?t=2292828
For LG mobile support tool problem, it need to download rom from LG server. Have you remove/comment 1-2 line that you add to hosts file? You said it never connect that mean it don't see your phone?
Click to expand...
Click to collapse
I've tried this as well, but I don't know if i'm doing it correctly
I installed the 'drivers' it needs (following the readme file) when it shows the "unknown/other" device (the part where you have to catch it in device manager).
After this, I run the start.bat, enter 5 and hit enter, i unplug my phone and hit any key, then i plug it in as it says and it does it's thing, then i wait for 4 seconds when it begins to say "waiting for device", i put my battery in and it just stays there, waiting for device
Can you help me figure this out? Am I doing something wrong?
rotatorkuf said:
I've tried this as well, but I don't know if i'm doing it correctly
I installed the 'drivers' it needs (following the readme file) when it shows the "unknown/other" device (the part where you have to catch it in device manager).
After this, I run the start.bat, enter 5 and hit enter, i unplug my phone and hit any key, then i plug it in as it says and it does it's thing, then i wait for 4 seconds when it begins to say "waiting for device", i put my battery in and it just stays there, waiting for device
Can you help me figure this out? Am I doing something wrong?
Click to expand...
Click to collapse
Please read these three link
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
kuma82 said:
Please read these three link
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
Click to expand...
Click to collapse
i think i'm making some progress, thanks for helping so far!
anyway, i'm able to get fastboot on my phone (i think?), the screen on the phone shows the flipped LG logo and at the top right it says 2.0 fastboot (flipped of course)
but, what am i supposed to do here?
i see the 2 omap devices listed on my device manager
whenever i try to run the kdz offline flash tool (if i'm using the right one), it still doesn't detect the phone as connected, doesn't even try, just errors and tells me to connect to usb port and restart or exit
what am i supposed to do once i'm in fastboot recovery for my phone?
should i comment out the 2 listings i added to the hosts file? should i NOT be running shttps app? which kdz offline flash tool should i be using? (currently trying: UpTestEX_mod2_marwin.exe)
rotatorkuf said:
i think i'm making some progress, thanks for helping so far!
anyway, i'm able to get fastboot on my phone (i think?), the screen on the phone shows the flipped LG logo and at the top right it says 2.0 fastboot (flipped of course)
but, what am i supposed to do here?
i see the 2 omap devices listed on my device manager
whenever i try to run the kdz offline flash tool (if i'm using the right one), it still doesn't detect the phone as connected, doesn't even try, just errors and tells me to connect to usb port and restart or exit
what am i supposed to do once i'm in fastboot recovery for my phone?
should i comment out the 2 listings i added to the hosts file? should i NOT be running shttps app? which kdz offline flash tool should i be using? (currently trying: UpTestEX_mod2_marwin.exe)
Click to expand...
Click to collapse
You should run start.bat and select flash ICS u-boot/x-loader for P769
When it finish, reboot you phone to S/W update mode and try to use UpTestEX_mod2_marwin.exe to flash your P769 kdz again to restore your phone.
Maybe I miss something about P769 model, please search in FAQ forum many people have this issue, and most of them have fixed it.
artit said:
You should run start.bat and select flash ICS u-boot/x-loader for P769
When it finish, reboot you phone to S/W update mode and try to use UpTestEX_mod2_marwin.exe to flash your P769 kdz again to restore your phone.
Maybe I miss something about P769 model, please search in FAQ forum many people have this issue, and most of them have fixed it.
Click to expand...
Click to collapse
you guys are awesome!
finally got my phone back on rooted firmware
now to unlock the bootloader
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.
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.