Database Users

stock at google page...please help

I tried to root my new nexus s that i got last friday.....
tey must be some thread about this but my english is not in top shape...
i am now stuck at google page when turning on my phone. must be something about my boot....
I live in Canada and my provider is roger here all the information that i found :
in fastboot mode:
product name: herring
hw version : rev 16
bootloader version : i9020xxka3
baseband version : i9020uckb2
carrier info : att
on my box:
model: gt-i9020fsrrwc
Please i realy need help.....
Vbob

Describe steps you have taken to root in detail.

i know this is not the right place to start, but i did't know....
hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
i was stock after "fastboot flash boot rootboot.img" i was ubable to reboot
Vbob

any one can help me?
Vbob

Download this first
http://www.mediafire.com/?0pzz830oc0xa0e7
Rename it to rootboot.img and overwrite the one in C:\nexusroot
Try
Code:
fastboot flash boot rootboot.img
again.

ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob

thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob

im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you

vbobmac said:
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
Click to expand...
Click to collapse
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
redlilcivic said:
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
Click to expand...
Click to collapse
You need to describe the steps you have taken, and describe the problem with more detail.

If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
Click to expand...
Click to collapse
i did a update yesterday, and now i think i dont have the right system recovery.
now when clicking system recovery, i get a "!" whit the android character...

vbobmac said:
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
Click to expand...
Click to collapse
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?

[email protected]_OC said:
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
Click to expand...
Click to collapse
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App

reddv1 said:
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.

[email protected]_OC said:
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
Click to expand...
Click to collapse
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App

reddv1 said:
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, i can mount my phone, but when i try to install the default rom, but it's not working. I have an error.
At least the manipulation is working, i can mount on my computer the nexus.
Do you have a rom 2.3.4 for Nexus i9023 please? Maybe i don't flash with a good rom?
Thanks again for your help.

I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".

[email protected]_OC said:
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
Click to expand...
Click to collapse
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App

reddv1 said:
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
And I think, i don't have the good bootloader.
My phone is a Nexus S i9023, but since i try to root my phone, my bootloader version is the "i9020XXKA3".
You think, i have to change the bootloader first?
For flashing bootloader and clocwork recovery, i have to do it from Windows?
Waiting for your answer.
Thank's a lot

[email protected]_OC said:
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
Click to expand...
Click to collapse
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App

reddv1 said:
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash the recovery, and now i have the v4.0.0.2, but i still can't flash a rom.
I still have the same message:
"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys" ||
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"
E: Error in /sdcard/update 2.3.3.zip
(Statut 7)
Installation aborted.
Don't you think it's because my bootloader is not the good one?
Can flash it too, from Windows?

[Q] how to root Nexus 10 (upgraded to Kit Kat 4.4)

Newbie here.
Pls guide me..
Many tks!
Sent from my SM-N9005 using xda app-developers app

Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord

Issues with rooting (4.4), stuck after flashing recovery
I just got my Nexus 10, and unlocked the boot loader, then flashed the custom recovery. All was fine, and I could boot into recovery, however recovery can not mount any filesystems. So I rebooted, now the Nexus does not boot, but hangs on the intro animation, normally meaning in my experience that the kernel is looped and is no longer finding (or else) booting the OS. I've tried booting 3 times.
So then, the steps I took,
enable USB debugging
were copy over the zip file for supersu
reboot to (fastboot mode), verify device
unlock boot loader "fastboot oem unlock"
flash the recovery "recovery-clockwork-touch-6.0.4.3-manta"
reboot into recovery
Failed to mount filesystems
for instance "E: Can't mount /cache/recovery/command or E:Can't mount /sdcard .... (you get the idea).
rebooting again a leaving it does nothing.
I also tried side loading a new image in my case "ThunderKat_manta-KRT16S-20131201" and after installing the "UniversalAdbDriverSetup", I was able to do so, I also was also able to side load the google apps "GoogleAppsPack-4.4-20131128", in both cases I get a success message after the install, however there after when I attempt to reboot I'm still stuck looking at the boot animation.
Now I'm really confused as if if the OS was destroyed when I unlocked the device, then side load of the zip contains a new kernel and OS image so it should be working, but it is not. In fact, recovery while still working throws the same can not mount exceptions after the flash as it did before (I rebooted) as I was previously getting and a factory reset, fails to mount /data, but does flash /cache and sd-ext without issues, so again I'm lost as to what to do.
Best guess I have is that partitions such as /data are just missing, I have no idea the state of teh device in such a case, but recovery and side loading using adb are working, how do I recover a working ANDROID OS from here?
Thanks,
ERIC

stuck in loading screen
Hi,
i just got my Nexus 10 yesterday. I tried to root it, but it is stuck in the loading screen. What can i do now? Can i like undo it to get it back to work?
I have the same issue egandt described.
Edit: I just got it back with this tutorial to android 4.2.2 and now i am updating it back up
nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/

I unlocked nexus10,
Flashed cwm,
Installed su, but whn i turned it on, su not found, rootchecker shows no root access..
I also encounter bootloop initially,
Need to wide data / factory reset then its normally booted..
Sent from my SM-N9005 using xda app-developers app

Agreed the factory reset was required to fix the issues I encountered, then installing super-su worked.

I still cannot root the Nexus10..
Any one can help?
Thanks in advance!

XxLordxX said:
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Click to expand...
Click to collapse
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!

xing369 said:
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
Click to expand...
Click to collapse
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .

shimp208 said:
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
Click to expand...
Click to collapse
Thanks for your kind offering of hands!
Last night I tried again to re-flashed latest TWRP as well as latest SuperSU.
I ran 2x Root Checker,
1 said rooted,
1 said no root access, no BusyBox available.
I tried some apps like GMD Gesture, no working or no root access.
So,
Should I redo everything: enable USB Debugging then unlock bootloader then flash CWM then install SuperSU?
I initially gone thru above steps w/o enabling USB Debug..
Many thanks!
Sent from my SM-N9005 using xda app-developers app

Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS

xing369 said:
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.

fritzhy said:
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
Click to expand...
Click to collapse
Very much appreciated for reviving my nexus!
However, after flashing latest TWRP, and installed SuperSU 1.80,
It seems my nexus still unrooted.
Any ideas?
Thanks!
Sent from my SM-N9005 using xda app-developers app

Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk

fritzhy said:
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app

xing369 said:
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If it's needed the app will say so when you open it.

fritzhy said:
If it's needed the app will say so when you open it.
Click to expand...
Click to collapse
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app

xing369 said:
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Not that I can think of, nope...

Help can't put rom on phone in TWRP, cant boot

Hello I was going to flash a rom from stock firmware with TWRP recovery installed when I accidentally wiped the system partition as well so there is now no rom on the internal storage and i cannot boot back into the normal firmware cause it just hangs at the LG logo on startup. I tried a USB OTG device in TWRP but it is not being detected and I don't know how to use the phone in mass storage mode inside TWRP. :crying:
Help would be much appreciated!

bump

Have you tried adb sideload? I did the same, wiped everything, system and internal , bacups and all. I managed to sideload a flashable rom, flashed it and managed to boot up. So: ADB Sideload through twrp is your answer.
Sent from my LG-D802 using XDA Premium 4 mobile app

KapteinKing said:
Have you tried adb sideload? I did the same, wiped everything, system and internal , bacups and all. I managed to sideload a flashable rom, flashed it and managed to boot up. So: ADB Sideload through twrp is your answer.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Was about to try sideload but then just used the flashtool and went back to stock. Thanks anyway!

KiLLa007 said:
Was about to try sideload but then just used the flashtool and went back to stock. Thanks anyway!
Click to expand...
Click to collapse
I'm stuck with the same problem didn't make a back up. I have a ROM but it won't flash because of 12B OTA on G2. So i'm stuck on twrp. Can you send me a link to get flashtool? What else do I need beside flashtool to go back to stock? Thank you

its not system thats the problem, you wiped internal..
adb push the rom to internal. many accurate how to do that with search. dont know top of head
Sent from my LG-D802 using xda app-developers app

Well if you do end up fixing it upgrade to TWRP 2.6.3.4 because it has OTG support!
Sent from my LG-VS980 using xda app-developers app

I'm in the same boat here except I've already tried adb sideload with twrp 2.6.3.3 and it returns an error "cannot read rom.zip" I've tried 3 different zips, many combinations of renaming the zip files. My machine is set to always show file extensions. I've also tried both ways of trying to flash back to stock in download mode. One of them just hangs at BIN CRC check the other will get to 49% and error out. Any suggestions?
Sent from my Galaxy Nexus using xda app-developers app

files and carrier
simonsez2die said:
I'm in the same boat here except I've already tried adb sideload with twrp 2.6.3.3 and it returns an error "cannot read rom.zip" I've tried 3 different zips, many combinations of renaming the zip files. My machine is set to always show file extensions. I've also tried both ways of trying to flash back to stock in download mode. One of them just hangs at BIN CRC check the other will get to 49% and error out. Any suggestions?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
what carrier and flies are you using? What com port is your G2 using? Have you tried using the LG mobile support tool?
I have tried but cant brick this phone, so many ways to communicate

geosnipe said:
what carrier and flies are you using? What com port is your G2 using? Have you tried using the LG mobile support tool?
I have tried but cant brick this phone, so many ways to communicate
Click to expand...
Click to collapse
VS980 Verizon. I've tried Lg flashtool with "LGVS980_20130902_LGFLASHv151.dll"
and VS98010B_13.tot. on com port 41. This one hangs at BIN CRC Check for hours. Won't go any further. I've also tried the uptest method found here in the forums with the files that are in the OP. It gets to 49% and stops and tells me to retry. When I retry it will always stop at 49%\
I can get into download mode and TWRP .While in TWRP, adb recognizes my device and shows recovery next to it. When I go to adb sideload and type adb devices again it will show that I'm in sideload mode but no files will transfer. It just returns error cannot read filename.extension. I've to sideload all kinds of files with different extension types and it always returns the same thing.
---------- Post added at 11:41 AM ---------- Previous post was at 11:27 AM ----------
I just remembered that I had a backup made from a week or 2 ago when I was using cwm recovery. Which isnt recognized in twrp. I didn't loose all of my sdcard content with all this. I was just a moron and forgot to make a twrp backup before wiping my system. And the only rom I have on my sdcard aborts about halfway through.
Sent from my Galaxy Nexus using xda app-developers app

Ok...so I was able to adb push a file to my sdcard using "adb push filename.zip /sdcard/filename.zip. It returned the size and time it took to transfer. But adb push ROM.zip /sdcard/ROM.zip gives me nothing and seems as tho it may have froze up the command prompt. GRR!
---------- Post added at 12:19 PM ---------- Previous post was at 11:52 AM ----------
Got it...thanks anyway.

simonsez2die said:
VS980 Verizon. I've tried Lg flashtool with "LGVS980_20130902_LGFLASHv151.dll"
and VS98010B_13.tot. on com port 41. This one hangs at BIN CRC Check for hours. Won't go any further. I've also tried the uptest method found here in the forums with the files that are in the OP. It gets to 49% and stops and tells me to retry. When I retry it will always stop at 49%\
I can get into download mode and TWRP .While in TWRP, adb recognizes my device and shows recovery next to it. When I go to adb sideload and type adb devices again it will show that I'm in sideload mode but no files will transfer. It just returns error cannot read filename.extension. I've to sideload all kinds of files with different extension types and it always returns the same thing.
---------- Post added at 11:41 AM ---------- Previous post was at 11:27 AM ----------
I just remembered that I had a backup made from a week or 2 ago when I was using cwm recovery. Which isnt recognized in twrp. I didn't loose all of my sdcard content with all this. I was just a moron and forgot to make a twrp backup before wiping my system. And the only rom I have on my sdcard aborts about halfway through.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
The LG Flash Tool and Mobile Support Tool are 2 different utilities for the phone.
Glad to hear you are back up and running!

geosnipe said:
The LG Flash Tool and Mobile Support Tool are 2 different utilities for the phone.
Glad to hear you are back up and running!
Click to expand...
Click to collapse
I actually tried both utilities but both resulted in error. I ended up getting it with "adb push ROM.zip /sdcard/ROM.zip" . It took a really long time, I ended up just trying one last time and left it alone for about 10 mins. When I came back to it, it showed the size of file and time it took to push. I figured I'd post all of this on the off chance it may help someone who has a Custom recovery but no backup or Rom zips to flash on the device.

simonsez2die said:
I actually tried both utilities but both resulted in error. I ended up getting it with "adb push ROM.zip /sdcard/ROM.zip" . It took a really long time, I ended up just trying one last time and left it alone for about 10 mins. When I came back to it, it showed the size of file and time it took to push. I figured I'd post all of this on the off chance it may help someone who has a Custom recovery but no backup or Rom zips to flash on the device.
Click to expand...
Click to collapse
Man you are a life saver. Thanks for coming back and posting your solution for this problem. I had the exact same issue and after hours of trying to install different "rom.zip" files with the same "cannot read rom.zip" error, this finally worked.
I cannot stress enough, how helpful it is when someone like you finds an answer to a problem and takes the time to come back and post the solution.
Thanks again!!!

[Q] Phone will enter recovery but not main bootloader screen

So I am trying to install CM11 on my G2 D802. Root done, Loki done, CWM or TWRP recovery done, CM11 image and GApps on sdcard partition. Now there is just one problem. I need to transfer the boot.img file from the CM11 zip file, however, I am unable to enter the main booloader screen, thus the Fastboot option. When I try to do so, the phone just reboots normally and launches the Android. I have the same problem with both CWM and TWRP. Anyone have an idea as to what is wrong?

Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app

**** Ripple said:
Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.

Stop what your doing read up before you try to do anything.
Sent from my LG-LS980 using xda premium

I've been flashing roms for years and nothing you are saying makes any sense. If you are having trouble entering recovery download terminal emulator. Open app and type su then press enter. You will be asked to grant root access assuming you have root. Then type reboot recovery, after that your phone will boot into recovery. Wipe, flash rom and gapps.
Sent from my LG-VS980 using xda app-developers app

shopperen said:
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.
Click to expand...
Click to collapse
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk

th3g1z said:
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk
Click to expand...
Click to collapse
Kernel files very depending on region. The distributor for LG phones in my country have altered the kernel in such a way, that the boot.img is required to be flashed.

X727 not booting

Hi,
First of all, my device info:
LeEco LePro 3 x727 on the 19s firmware.
I was following the guide found here: https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560 to flash recovery and root my phone. Didnt realize it was for the x720 and not the x727 (stupid, I know)
Did everything in there, booted into the TWRP recovery, flashed the root file and rebooted.
Phone turns on, logo appears then shuts down.
I can't boot anymore.
I CAN boot into fastboot mode.
PC doesn't recognize my device
TWRP's sideload feature doesnt work
I'm obviously new at this, so I can't figure out a way to flash the firmware again (I guess that's what I have to do, do not know though).
What can I do?
I now flashed the correct TWRP file for my phone. works fine.
But how do I push files to the phone so I can flash them?
Any help would be greatly appreciated. Thanks!
Edit 1: Found this guide https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Should I follow that and see if it works? Will wait for confirmation first. Not gonna rush into it like the first time.
Thanks!

Yes here link to files you will need.
Qfil Look :
https://mega.nz/#!BJ52CApB!8lFCesul...r&utm_medium=referral&utm_source=DonanimHaber
Sent from my LEX727 using xda premium

mchlbenner said:
Yes here link to files you will need.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
So I should follow the guide and use those files? Any warnings or tips about the process? And also, no other way around that problem?
Thanks!

I have never needed to do this follow the directions to the tee.
It shame that fastboot doest work for you.
Sent from my LEX727 using xda premium

mchlbenner said:
I have never needed to do this follow the directions to the tee.
It shame that fastboot doest work for you.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
It actually works (fastboot I mean), but now I'm at the point where I try to sideload files but at 48% it gives me an error.

I had the same troubles, many wipes and try finally it worked... The stock file is the hardest to send, because the weight is so high.

marik1 said:
I had the same troubles, many wipes and try finally it worked... The stock file is the hardest to send, because the weight is so high.
Click to expand...
Click to collapse
I was able to push the files using adb instead of adb sideload.
Pushed the Lineage OS and now I'm currently running that.
Thanks for the help !

sirmamay said:
I was able to push the files using adb instead of adb sideload.
Pushed the Lineage OS and now I'm currently running that.
Thanks for the help !
Click to expand...
Click to collapse
If you had adb work why did not flash rwrp?
Sent from my LEX727 using xda premium

mchlbenner said:
If you had adb work why did not flash rwrp?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Hmm, I did, maybe you missed it in the OP. I just wasnt able to push the files for some reason, had to flush the port (5037) to get it to work, and tried a lot of different adb versions until I got it to work with the mfastboot version of it.
Anyways, it's good to know there's another option in case I really brick it.
Thanks!

sirmamay said:
Hmm, I did, maybe you missed it in the OP. I just wasnt able to push the files for some reason, had to flush the port (5037) to get it to work, and tried a lot of different adb versions until I got it to work with the mfastboot version of it.
Anyways, it's good to know there's another option in case I really brick it.
Thanks!
Click to expand...
Click to collapse
Okay so in the original post you said that you do have twrp installed, and you can boot into twrp recovery...right.
Go buy an OTG drive
Load your Rom, Gapps, and Magisk onto otg flash drive
In TWRP: Go to "Wipe" and then to "Advanced Wipe" (Check: Dalvik / ART Cache, System, Data, and Cache
Swipe to Wipe > then go to main menu. ( Note, if you get a Encryption message you will have to wipe the storage, as long as Twrp recovery is installed there will be no issues)
Go to Install then select OTG : Select the ROM file then click "Add more Zips" and select the Gapps and Magisk files
Swipe to confirm Flash
Reboot to system