Develop Bugs

[ACS] [How to] Root, Unroot, Hotspot, Roms, Tips and more! (12 videos) 5/18/12

This would be updated videos to show the latest methods to root unroot and more!
Development:
How to install the android sdk:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
How to install Drivers on PC:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
How to unlock bootloader:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
How to root the Sprint Galaxy Nexus:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
How to get free wifi hotspot:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
How to unroot:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
How to install a radio:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
How to install the Black ICE Rom:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
Review of the Black ICE Rom:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
Tips and more:
Unboxing the Sprint Galaxy Nexus:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
1080p Video camera test:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12
Radio speed test: FC12 vs. FD01:
http://forums.acsyndicate.net/showt...tspot-Roms-Tips-and-more!-(12-videos)-5-18-12

Mine as well.. Just in case

qbking77 said:
Mine as well.. Just in case
Click to expand...
Click to collapse
THANK YOU! Every other post was about how to unlock, how to this, how to that. Glad to see you in the Sprint nexus section!

I request a sticky please!!!
Kenny!!!!
Please Sticky

davidrules7778 said:
I request a sticky please!!!
Kenny!!!!
Please Sticky
Click to expand...
Click to collapse
+1 Mr. Glass!

Thanks QBK nice work!!!

hey I rooted with the galaxy nexus toolkit 6.0 way and was wondering if i can unroot and go back to stock with the unroot method here??
thanks

jsonger121 said:
hey I rooted with the galaxy nexus toolkit 6.0 way and was wondering if i can unroot and go back to stock with the unroot method here??
thanks
Click to expand...
Click to collapse
99.9 percent sure
However that extra .1 percent i am not

Good to see you here QBking... did you jump on the nexus bandwagon too?

Of course you get a sticky and my nandroid thread doesn't have one

Wordlywisewiz said:
Of course you get a sticky and my nandroid thread doesn't have one
Click to expand...
Click to collapse
Take another look
FNM

can someone help me with why when i plug my phone "in fasstboot mode" in to my pc and then open a command prompt and type fastboot devices it will not recognize it. theres a part in the unroot video where he is in "downloads" and then opens cmd it works, then when i try it....nothing.....
thanks for any help.

I just needed the files
(These will be used, to update my Root Helper, and make it usable, for everyone )

computer wont recognize phone while in bootloader mode i type fastboot oem unlock and it just waiting for device. any help??
edit: nevermind!!!!
Edit again: I got root!!! Yeah!!!

justen7723 said:
computer wont recognize phone while in bootloader mode i type fastboot oem unlock and it just waiting for device. any help??
edit: nevermind!!!!
Edit again: I got root!!! Yeah!!!
Click to expand...
Click to collapse
What did you do different cause mine just sits in bootloader mode and the command prompt just says waiting for device.... it's been about 5min now ><
and when my computer recognizes the phone in recovery it makes a weird connextion noise not like the usual one

Nitefall said:
What did you do different cause mine just sits in bootloader mode and the command prompt just says waiting for device.... it's been about 5min now ><
and when my computer recognizes the phone in recovery it makes a weird connextion noise not like the usual one
Click to expand...
Click to collapse
It's picky about recognizing the USB. My problem was actually fixed by using a different USB port. Try reinstalling the drivers, or using a different USB port, or downloading pdanet and maybe some light threats.

jesusice said:
It's picky about recognizing the USB. My problem was actually fixed by using a different USB port. Try reinstalling the drivers, or using a different USB port, or downloading pdanet and maybe some light threats.
Click to expand...
Click to collapse
Yea I finally got it after I posted that just hadn't been back to fix it lol
Thanks anyway I did switch usb ports and cables

How To Videos
I'm not as big as qbking77, and I'm not sure if the mods would be happy with me starting a new thread with my how to videos, and I'm not trying to step on anyones toes. My video shows a completely different root method than qbking does, and it shows you how to unlock the bootloader in the same video.
http://www.youtube.com/watch?v=bf7H3QT_Vqc&hd=1&list=PL2A3C66EF2F16BA1E
A playlist of mine can be found here,
http://www.youtube.com/playlist?list=PL2A3C66EF2F16BA1E
If it would be better to start my own thread, (mods) please let me know!

I would like to use CWM instead of TWRP that is used in the instruction videos.. Any suggestions?

jcarlm said:
I would like to use CWM instead of TWRP that is used in the instruction videos.. Any suggestions?
Click to expand...
Click to collapse
Yeah, you could download the recovery.img from Koush's website, or you could use the method I did in my video.
http://www.youtube.com/watch?v=bf7H3QT_Vqc&hd=1&list=PL2A3C66EF2F16BA1E
EDIT: Here are the .img's for ALL phones. Pick the one for your phone.
http://www.clockworkmod.com/rommanager

Help with unlocking and rooting

I can't seem to get this to work. I'm trying to unlock my phone using the nexus toolkit but when I put my phone into fastboot mode and click the unlock option on the toolkit I just get '< waiting for device >'. Every video I watch just shows them plugging the phone in and then having the program unlock it for them. It's not doing the same for me. Any suggestions?

Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.

063_XOBX said:
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
Click to expand...
Click to collapse
Every guide and video I find uses that method. Do you have a link to the other method?

http://forum.xda-developers.com/showthread.php?t=1529058

063_XOBX said:
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
I still get the 'waiting for device' when I do it this way too. I have the most current samsung drivers. I also did everything to set up ADB.

uninstall the drivers and reinstall using the naked drivers.

[Noob-friendly] Poor man's FlashTool

Version 3 released! Check for even more simplicity and a new UI! NO more copying!
Click to expand...
Click to collapse
If you're experiencing errors, please report them either in the thread or PM me.
Please report ANY errors or typos you come across, I made this in 4 hours without a single break, so there's bound to be an error somewhere
What's new:
-Completely rewritten (ACTUALLY written, not VB)
-Even simpler! NO MORE COPYING!
-Even smaller in disk size!
-No tutorial needed! Yes, it's that easy -- just read carefully and don't panic
There's still no way to:
-relock the bootloader
-flash FTF files
_____________________________________________________________________________________________
Note: Inside the Fastboot.rar, there are fastboot drivers for 2012 Xperias. Install them if you dont have them yet. Those are the only useful files you need from that folder, everything else (both adb and fastboot) are already contained in the new BU.zip!
TESTING:
Reported working Windows versions:
Windows 7 x86
Windows 7 x64
Windows Vista x86
WANT TO HELP?
Then test it and report your phone model and windows version (x64/x86, service pack etc.) -- send me a PM
Please do... You can always flash a kernel or recovery.
Thanks for helping me and all those noobs out
About the attachments:
-Fastboot; contains adb and fastboot, plus Xperia 2012 Windows drivers
-BootloaderUnlock; contains the old PMFT - version 2 (kind of useless unless you understand everything it says in there)
-nexus; the NEW PMFT - version 3 -- if you already have the drivers, this is all you need

someone755 said:
I've been getting some questions on PM lately, about 'how to unlock my bootloader'...
So, fed up with those infinite PMs, I quickly put this together (30 minutes, not much).
It's not much, and I've only tested it for one minute, but it should help the average noob user get their bootloader unlocked.
(I've only tested this on a x86 Win7 PC, so please help me find out where this works on.)
So, the basic idea is, that the noob user extracts the attached adb and fastboot .zip file and extracts it to disk C: (I'll make options for other drives later on, I just need to know whether or not this works). The user then opens up the program inside BootloaderUnlock (and installs it), and, after many warnings, gets to a screen where he is told to input his Bootloader unlock code (obtained from Sony's website).
The program then warns the user a little more, just to make sure he understands, and then, two lines of text show up.
The user enters those lines of text into the console window (the fastboot.exe he extracted at the beginning) and Viola!
If all steps have been done correctly, he now has an unlocked bootloader
It's a simple, yet fool-proof concept, tested on a complete phone moron (after reading some instructions on Sony's unlock site).
Please help me test this, as this may be really helpful to those that don't understand FlashTool and don't have an idea how to do it via the official method.
Also, if you don't understand, there are some instructions within the program (written in VB, so you may need NET framework... MAY need it...)
Thanks for helping me and all those noobs out
Note: extract the fastboot.rar to C:, so you will have the fastboot.exe in C:\Fastboot\fastboot.exe
Note: Inside the Fastboot.rar, there are fastboot drivers for Xperias. Install then if you dont have them yet.
Note: The BootloaderUnlock.rar is a visual basic program. Please help me test it on different Windows systems (XP, Vista, 7, 8, 2000; all both x86 and x64)
Click to expand...
Click to collapse
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app

derrickdroid said:
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app
Click to expand...
Click to collapse
No it wouldn't. It'll either work or not
Sent from my Jellybean Xperia S

Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...

someone755 said:
Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...
Click to expand...
Click to collapse
i think he was referring to:
IF you are so beginner that you aren't able to even unlock your bootloader
THEN you could be so newbie to brick it

That's possible, if you're pointing to the fact they could brick their phone after unlocking the bootloader.
But before the unlock, no, it wouldn't be possible...
But hey, some people might have trouble with windows and are new to it. (I know many linux users that are forced to use windows for their phones that could use tools like this for their phones (not Sony, but others...)...)

So can this way unlock any bootloader even if it says bootloader locked? Thanks
Sent from my LT28i using xda app-developers app

Nope.
Did you not read the first post?
It's the same as the official method, but simplified...
Nothing's changed, basically, so it can't do more and it can't do less!

Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app

Its not the phone, it's the carrier...

mcmanone said:
Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
It's because companies like AT&T give locked down phones away for free with a service contract. That way they can lock some services to make you pay more. For example AT&T makes you pay an additional monthly fee for the use of tethering (only when you use the att stock Rom, it's free on generic version )
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread

So I guess it's great in my country;
you don't get a 'free' phone, you pay at least 1€ (depending on the plan you chose; I chose the one where I get to pay 370€ for a nozomi)
You can always trade your phone on Swappa (you have loads of ads on CM's sites and forums) and get an unlockable one...

what is the difference between this tool and this one?
http://forum.xda-developers.com/showthread.php?t=1794800

This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...

someone755 said:
This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...
Click to expand...
Click to collapse
okay thanks....
DOWNLOADING

Let the Noob try it !!
Hey Guys,
I am a Noob and have been trying to unlock my bootloader for about a week now, I have tried a few methods without any joy.
I will give this a go and will report back if it works or not. :laugh:

Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...

someone755 said:
Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...
Click to expand...
Click to collapse
Hi,
Thanks for the reply, the problem i have is with the drivers. I have tried different solutions as posted here and on the web.
But still could not get the drivers to work??
I will try this method as it states the drivers are included. If it all works awesome, if not then I fail and will forever be stuck with stock rom's.

Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?

someone755 said:
Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?
Click to expand...
Click to collapse
I'm running windows 7 on a 64 bit laptop.
Tried the flashtool drivers also but still no joy, I check in device management for S1 and each time there is a problem installing the drivers.
I still have a PC running vista so might give that a try if all else fails.
Thanks for your help so far, will keep you updated with how I get on

[Q] Received Ebay Phone, am I screwed?

Ok, I bought a galaxy nexus SCH i515 off ebay. The phone was listed as verizon, all the information behind the battery came up as sch i515. However when I powered it on. The phone said activate samsung account. The phone matches verizon info on the back. I contacted verizon and they said most likely the phone was rooted and that the phone could not be switched back even after a hard reset (which i did). I have wifi so used that to get on play store and downloaded rootchecker.... it says phone is not rooted.. (did original owner just unroot phone) am I screwed or is there anything I can do to get verizon able to activate it?

1) wrong section
2) follow this: http://forum.xda-developers.com/showthread.php?t=1626895
after step 2, check in the phone status menu for the model number.

So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)

loopers said:
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
Click to expand...
Click to collapse
I appreciate your quick informative answer but if i've already called verizon and they have informed me that the imei is not in their data base.... if i do all these steps and flash back to complete stock the imei still will not be in there data base correct? I mean I'm still stuck on this.... if I need to start asking somewhere else please let me know. Thanks

Just flash the factory images from Google. And make sure the ESN is good you can check it just Google search
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2

where is the factory images from google? Sorry i've been back and forth with seller and verizon and DO NOT want to screw this up

I see nothing specific from google search that says from a google site to flash these files to phone with steps

loopers said:
I see nothing specific from google search that says from a google site to flash these files to phone with steps
Click to expand...
Click to collapse
sorry found files

well found everythhing i need and loaded into the bootloader.. can't get it unlocked because it won't recognize fastboot devices..... it recognizes nothing. tried multiple ports.usb ports that is.... comes up with error code 214dfddsf i can't remember.... googled error.. no one really knows a fix.. if anyone knows of a toolkit for 4.1.1 or similar for samsung galaxy nexus let me know.... i've been trying to get my wifes phone activated for 6 1/2 hours and i'm done with it less you guys have a clear cut alternative.. i don't expect anyone to jump up and say here ya go but if ya do i'd greatly appreciate it.... i've googled the error to death.. no clear cut fix.... and i'm not trying to load up a rom.. i neeed to get the phone completely factory reset so i can get it activated from verizon..

oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....

loopers said:
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
Click to expand...
Click to collapse
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever

Pirateghost said:
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Click to expand...
Click to collapse
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb

loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Try wugs nexus root toolkit. More friendly for new users. Just Google the name and it'll come up.
Sent from my Galaxy Nexus using xda premium

loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL

as is strewn throughout these forums....ADB and FASTBOOT use different drivers. just because you have adb working doesnt mean that fastboot is setup properly

Sandman-007 said:
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
Click to expand...
Click to collapse
those are the drivers i have installed i think someone completely fudged this phone

those are all google nexus don't say anything about samsung version :\

fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope

loopers said:
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
Click to expand...
Click to collapse
No need to root, just install drivers, unlock bootloader and flash stock image, then lock the bootloader up..

Got it fixed. Tool kit worked. Txx
Sent from my SCH-I535 using Tapatalk HD

lg g4 root issue

hello guys
need yout help, tried searching google for sulotion but came up empty.
ive rooted the lg g4 h815(android 6.0-V20c-SEA) before via iroot pc but after factory reset its returned to be unrooted.
when i try to root again its keep failing because of debugging issue (the software keep telling me its not in debugging altough it is)
i think the problem is when i do usb debugging - connecting to pc the option is checked in the check box but it turns gray.whats the problem is? how can i fix it ?
thank you in advance

If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, if the the G4 Factory Reset protocol deletes the system partition, and then reinstalls it, then this would explain why/if you lost root, I do not know if that's the protocol though. If iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
I recommend wiping Data, Cache and Dalvik from TWRP next time, if that's not what you did this time. :good:

Williquah said:
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, although I've never heard of that, if iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
Click to expand...
Click to collapse
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much

mikmikush said:
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
Click to expand...
Click to collapse
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!

Williquah said:
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Click to expand...
Click to collapse
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response

About phone ????

mikmikush said:
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
Click to expand...
Click to collapse
Sorry for forgetting the whole reason you're in this problem is because of a factory reset lol, of course you have your data backed up. And trust me, I understand about the brick, I really messed up my G3 2 years back. Thanks also for the device pictures, could you post a shot of "About Phone=>>Software Info". That would be great!
Funny thing I just did that same phone rotation thing very recently XD

Lol love rotation, here

mikmikush said:
Click to expand...
Click to collapse
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.

Williquah said:
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Click to expand...
Click to collapse
Thank you thank you! You are awesome.
I will follow the links later and reply ...
I will ???? thank you

@mikmikush You're welcome, my pleasure!

Williquah said:
@mikmikush You're welcome, my pleasure!
Click to expand...
Click to collapse
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?

mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial

CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
its like my problem?
what did u do?

mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
H815 SEA?/Same software version and error?

Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003

htr5 said:
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?

Williquah said:
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
H815 SEA?/Same software version and error?
Click to expand...
Click to collapse
Williquah said:
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Click to expand...
Click to collapse
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated

mikmikush said:
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
Click to expand...
Click to collapse
Trust me, I understand your frustration, I'm going to make a guide for you in the next 6 hours or so.
Try a different computer if you can, I haven't had adb fail but many other tools sometimes work
on different computers for me. I've also heard "Dell PC Suite" should be uninstalled as it could cause adb hang ups,
if you have it. @htr5's guide might work for you if you have a software update available, I'm not sure though since it's not specifically for your device.
Regardless, I'm sure you will need to use adb soon, so we have to fix that.
I will try to make that guide asap, I obviously can only do so much, again, since I don't have your device, hopefully it will help though. I highly suggest trying on a fresh/different computer though.
Edit: Try USB 2.0 if you were using a 3.0 port (3.0 ports have the SS along with the usb "logo")
USB 2.0 is on the right:

"H815 SEA Root/General Guide"
@mikmikush
It does seem that you can treat your SEA device very similarly to the EU common version, in ways such as flashing KDZ's and rooting.
I cannot confirm this, but mentions in this thread: http://forum.xda-developers.com/g4/help/safe-root-h815-v10b-sea-variant-t3184152 make it seem like it should be okay.
Aoi_sora9x said:
I'm a SEA variant holder here.
It's fine, you can use the Low Effort Root method. You can also flash the EU open KDZ without any problem.
You lose VoLTE, but to me it doesn't matter so I don't really care.
I'm running the latest 10E ATM, and it's much much better than 10B, so flash away.
Click to expand...
Click to collapse
Yes, that post is for v10b, but it should also work for v20d/v20c. (Not the Low Effort Root method) - You will be working with EU software v20d.. while you are with SEA v20c,
so it's up to you if you want to try this, but it's the closest I can come right now. Thank @htr5 because I believe he has all of this in his guide, and I'll probably send you to his guide halfway through.
You may lose some features or brick your device by flashing firmware/software made for other devices. Trust your instinct!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install adb setup from here this includes necessary adb drivers, adb itself, and fastboot.
2. Install LG Mobile Driver
3. Download LGUP tool from here (This is for restoring your device to stock if you softbrick via KDZ)
Follow this thread if/when you need to.
4. Here contains a KDZ for EU v20C, which I'm 99.9% sure will match your current software, even though it says for EU.
5. Here contains every partition including the KDZ for 20d by @autoprime, which will be necessary if you decide to root from @htr5's guide (v20d Root Method)
6. Once again, try to unlock the bootloader officially through LG, if you are successful, you can follow @htr5's 20d Root Guide here
7. Be careful and let me know how it goes
@autoprime Mentions that there is "NO anti-rollback qfuse used in this update" (20d) so if you flash the 20d KDZ and it works, I believe you should then be able to downgrade successfully to an earlier firmware version - without worrying about qfuse - and root using a Lollipop (5.0/5.1) method if you can't get anywhere on Marshmallow (6.0). - This I'm not 100% positive about, again, but it is my thinking.
Please thank anyone I mentioned and anyone who's link I provided, they all deserve it!