Related
Hello so I am new to these forums but have used them in the past for assistance. I have been trying to root a att fusion 2 aka u8665 ive seen a couple posts on here about how to and someone said they were successful but vauge steps cause frustration.
http://forum.xda-developers.com/showthread.php?t=1920528
http://forum.xda-developers.com/showthread.php?t=1976657
As i said i have been trying for a while and basically tried everything listed in those two posts, also the post where they said they managed to attain root through fastboot confused me. From what i understood fastboot needs root to be able to operate, otherwise the steps in the post about using adb i just keep running into permission issues where i cant mount anything to root it.
I had trouble myself, but figured it out. I recompiled all the files posted by RFE.
https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Sent from my NookColor using xda app-developers app
still stuck
thank you for the quick response, but see the issue i was having is that fastboot is installed through the adb, yet i cant get it to recognize my device. but again thanks for the quick reply but one last thing this recovery.img is it a pre rooted image?
gm4n1989 said:
thank you for the quick response, but see the issue i was having is that fastboot is installed through the adb, yet i cant get it to recognize my device. but again thanks for the quick reply but one last thing this recovery.img is it a pre rooted image?
Click to expand...
Click to collapse
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
fastboot not seeing device
RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
not yet i am going to try again in a bit here though, still running into issues where fastboot will not recognize the device. im guessing a driver issue, except not sure why they wont work.
RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
ok so i got to where i need to use the actual flash command but it returns a error " cannot determine image filename for 'recover.img' "
RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
thank you all rooted now
RoboticBuddy said:
I had trouble myself, but figured it out. I recompiled all the files posted by RFE.
https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
If anyone else would like to contribute please do. I've had 5 attempts at registering this type of device without triggering a call-home. I've swapped out 90% of all the components that brand the phone AT&T (including huawei-hardware-extensions & mobile phone "care"??). When using Titanium Backup you will notice that some of the specially protected APK files cannot be removed or "found" - you will get the message "APK file not found." The only way to get around this is to use fastboot and pull the file from the device before removing it. If you remove the wrong system APK your phone won't be bricked, but it will give you infinite android.acore force close loops and other nasty crippling bugs (such as no touch-keys backlight). If you want to be sure that you are not doing any damage, do a full reboot and cache clear after uninstalling any of the AT&T prepaid system components. Many of the system components can not be removed or replaced with other versions until their dependencies are replaced or removed as well. Titanium Backup once again comes in handy and lets you select an android ID or "profile" which is a UID that is tied to your Google Play / Android Market account. You will have to create a new random Android ID after you have have replaced all the apps. Make sure you remove any files like Twitter that have been specially made for this phone & include a long unique ID like Twitter-3-6-0-(123456)--00000_V300_001.APK - the phone is incredibly fast without any google or ATT stuff on it.
Hi everyone. I had a long journey trying to root my phone, I originally had ICS and tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2044645 It was able to get my phone rooted by step 7, but then I couldn't get into recovery mode, it kept giving me:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
So I thought perhaps this doesn't matter at this stage and so I continued on with the tutorial. Eventually (long story short) something happened and now I have downgraded to Android 2.3.6 but my phone is no longer rooted (I don't have 'super user' app and root checker says I'm not rooted). I tried upgrading back to at least ICS through software update but it gives me a "you are not registered" (or something like that) and won't update.
I have no idea what to do now. I honestly just want to get ICS back and give up on this whole rooting attempt. Any ideas/help appreciated.
You should have followed this guide :
http://forum.xda-developers.com/showthread.php?t=2044645
It's newer and much easier. Now for the problem at hand, run the v18f exe file from the above guide. That should fix the issue you have then be able to get to any rom from there. Make sure you follow the guide precisely.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
You should have followed this guide :
http://forum.xda-developers.com/showthread.php?t=2044645
It's newer and much easier. Now for the problem at hand, run the v18f exe file from the above guide. That should fix the issue you have then be able to get to any rom from there. Make sure you follow the guide precisely.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply. I actually was able to just use the LG update on it's own to get ICS back, though the phone isn't rooted anymore.
At some point I did try the tutorial you sent but it wouldn't let me get into recovery mode, it gave me the error I mentioned. I'm just wondering though, if I use that tutorial again, will it work with ICS and v20f? Also, by the end of it what will i get? a rooted phone with Gingerbread? (sorry if they're stupid questions, I'm still learning).
hellored said:
Thanks for the reply. I actually was able to just use the LG update on it's own to get ICS back, though the phone isn't rooted anymore.
At some point I did try the tutorial you sent but it wouldn't let me get into recovery mode, it gave me the error I mentioned. I'm just wondering though, if I use that tutorial again, will it work with ICS and v20f? Also, by the end of it what will i get? a rooted phone with Gingerbread? (sorry if they're stupid questions, I'm still learning).
Click to expand...
Click to collapse
You got that error because you tried to install CWM with the ICS boot loader still installed. The link I provided has you install v18f so it can be rooted and them use the program to keep root so you can downgrade to Gingerbread so CWM can be installed.
One more thing: if all you want is root but don't care about installing another ROM use this to root v20c and stay 100% stock other than root: http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my LG-P930 using xda app-developers app
Swetnes said:
You got that error because you tried to install CWM with the ICS boot loader still installed. The link I provided has you install v18f so it can be rooted and them use the program to keep root so you can downgrade to Gingerbread so CWM can be installed.
One more thing: if all you want is root but don't care about installing another ROM use this to root v20c and stay 100% stock other than root: http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Okay, I get it. I think I might've missed a step somewhere along the line or something. However, as you said, I really just want to root to give myself the super user ability/app since I find it helpful. I did try the link you provided before and now again but it won't work. First of all I have v20f not v20c (is that why?). Second, I choose normal mode, and then it tells me to look at my phone and click restore. My phone shows a window saying "Restore my data" and "Do not restore" but also asks for a password. Since I don't think I have a password I click on Restore my data (and leave those field blank). My phone says "Restore Starting"...then it says "Restore ended" (within a few seconds) but the Bin4ry bat file won't move on to the next step. It just stays at "Running..." Any ideas?
hellored said:
Okay, I get it. I think I might've missed a step somewhere along the line or something. However, as you said, I really just want to root to give myself the super user ability/app since I find it helpful. I did try the link you provided before and now again but it won't work. First of all I have v20f not v20c (is that why?). Second, I choose normal mode, and then it tells me to look at my phone and click restore. My phone shows a window saying "Restore my data" and "Do not restore" but also asks for a password. Since I don't think I have a password I click on Restore my data (and leave those field blank). My phone says "Restore Starting"...then it says "Restore ended" (within a few seconds) but the Bin4ry bat file won't move on to the next step. It just stays at "Running..." Any ideas?
Click to expand...
Click to collapse
Ok now we are getting somewhere. First of all v20(x) doesn't matter. If it hangs on you saying "running" just close the "command" window, and try again. The couple of times I have tried it it has always done that the first time but then worked the second or third time. It is at that point the phone is supposed to reboot. Good luck.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok now we are getting somewhere. First of all v20(x) doesn't matter. If it hangs on you saying "running" just close the "command" window, and try again. The couple of times I have tried it it has always done that the first time but then worked the second or third time. It is at that point the phone is supposed to reboot. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
First off, thanks for keeping up with me. Well, after like the fifth try, using a way of opening the bat file through cmd manually (not sure how it's any different) I actually got it to say "Successful" and it actually rebooted my device!!...However, it then said something like "Permission denied (are you root?)" or mount failed. So although the file said at the end that my root was successful, I realize it really wasn't and I even made sure; I don't have super user or anything and even root check doesn't say I'm rooted.
I tried it one more time after, but again, it wouldn't reboot. So I tried it again and this time after clicking Restore, I unplugged and plugged my USB. It did say "success" and rebooted my device, though again, the same "mount" error came up and my device isn't rooted.
Any ideas??
Two questions: first what version of windows? Second how are you launching the bat file?
Sent from my LG-P930 using xda app-developers app
I have Windows 7 64 bit and initially I just launched the bat file but double clicking it/opening it normally. However, as I mentioned, the one time it did work I opened the file using this method: youtube . com/ watch?v=7EpkrCq1gfM (all you do is launch the bat file 'manually' more or less by opening cmd prompt then directing it to the folder with the bat file, then running the bat file)
Okay I will thing you might try.... Copy the bat file along with the stuff folder to c:\. This is a wild stab in the dark but under Windows 7 the root folder has different permissions than sub folders and then just double click on the bat file from there.
If you are still having issues use this process: http://forum.xda-developers.com/showthread.php?t=2044645
Basically you get the ICS leak v18f use the tpsparky method to root then using the keep root method to keep root while you upgrade to v20f.
Sent from my LG-P930 using xda app-developers app
Tried moving it to c:\ but same error "cannot mount" or whatever.
Swetnes said:
...
Basically you get the ICS leak v18f use the tpsparky method to root then using the keep root method to keep root while you upgrade to v20f.
...
Click to expand...
Click to collapse
Does this mean you're suggesting I just do the whole guide all over again or do you mean I can just stop at some step?
hellored said:
Tried moving it to c:\ but same error "cannot mount" or whatever.
Does this mean you're suggesting I just do the whole guide all over again or do you mean I can just stop at some step?
Click to expand...
Click to collapse
You can follow the whole guide if you want to install CWM. However if you use v20f as your kdz file or any other ics kdz this will accomplish what you want.... Rooted ics. Do you have the kdz file for v20f? Or another way to look at it is the whole purpose of the before and after bat files is to maintain root when going from one rom to another. You don't have to go to Gingerbread only if you want to install CWM.
I just wish I knew why you were having to many issues.... Try this open a windows command prompt and go to the stuff folder and type the following command:
adb device
What do you get back in response?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
You can follow the whole guide if you want to install CWM. However if you use v20f as your kdz file or any other ics kdz this will accomplish what you want.... Rooted ics. Do you have the kdz file for v20f? Or another way to look at it is the whole purpose of the before and after bat files is to maintain root when going from one rom to another. You don't have to go to Gingerbread only if you want to install CWM.
...
Click to expand...
Click to collapse
O, okay, I see. Well ya, at this point I just want rooted ICS...which I did have before, I just couldn't get into recovery mode as mentioned. But it seems I need to get gingerbread for that...is that right? That's why I got this error before:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
It meant that even though I had it rooted, because I had ICS it couldn't go into recovery?
As for V20f kdz, I found this thread which seems to give it to you: forum.xda-developers . com/showthread.php?t=2073620 (right?)
Swetnes said:
....
I just wish I knew why you were having to many issues.... Try this open a windows command prompt and go to the stuff folder and type the following command:
adb device
What do you get back in response?
...
Click to expand...
Click to collapse
It gives me the "List of devices attached:" and then under it my device code.
hellored said:
O, okay, I see. Well ya, at this point I just want rooted ICS...which I did have before, I just couldn't get into recovery mode as mentioned. But it seems I need to get gingerbread for that...is that right? That's why I got this error before:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
It meant that even though I had it rooted, because I had ICS it couldn't go into recovery?
As for V20f kdz, I found this thread which seems to give it to you: forum.xda-developers . com/showthread.php?t=2073620 (right?)
It gives me the "List of devices attached:" and then under it my device code.
Click to expand...
Click to collapse
I literraly had this exact error on my p930 2 days ago when a tried installing CWM for the first time. the only way i was able to unbrick the phone was following this guide.
http://forum.xda-developers.com/showthread.php?t=1784709&page=4
if you have any questions you can ask me, i just did it on my phone so i should be able to answer unless you run into a problem i didn't
At what stage do you get the secure boot error? Is it after v18f is rooted and you are doing the before and after bat files with. KDZ file?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
At what stage do you get the secure boot error? Is it after v18f is rooted and you are doing the before and after bat files with. KDZ file?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
if his problem happened the same as mine after trying to boot into cwm for the first time you get the error, becuase lg has a secure bootloader. after this i had to follow the unbrick guide, eventually you end up with at&t stock rom, then you are able to boot into cwm and install a custom rom like CM
One thing just occurred to me you need to stop at step 18 on the unbricking guide. If the KDZ that you are using is one of the v20(x)_00.kdz variants do not use adb to push the recovery.img file this WILL brick your phone and cause the secure boot error this is used to push recovery onto v10(x)_00.kdz only.
Sent from my LG-P930 using xda app-developers app
KronicSkillz said:
I literraly had this exact error on my p930 2 days ago when a tried installing CWM for the first time. the only way i was able to unbrick the phone was following this guide.
http://forum.xda-developers.com/showthread.php?t=1784709&page=4
if you have any questions you can ask me, i just did it on my phone so i should be able to answer unless you run into a problem i didn't
Click to expand...
Click to collapse
Okay thanks, I will try this guide once I get the chance and report back to you. Just a question though, I'm assuming this guide will still give me Gingerbread at the end of it, correct?
Swetnes said:
One thing just occurred to me you need to stop at step 18 on the unbricking guide. If the KDZ that you are using is one of the v20(x)_00.kdz variants do not use adb to push the recovery.img file this WILL brick your phone and cause the secure boot error this is used to push recovery onto v10(x)_00.kdz only.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Um, you mean stop at step 18 of the original guide you linked me or the one that KronicSkillz is suggesting? I honestly just use whatever the guide says/provides, I don't bring in any outside files. Previously I mentioned I might use another one because you suggested it would work well for me by keeping ICS. But originally I just follow the guides step by step.
hellored said:
Okay thanks, I will try this guide once I get the chance and report back to you. Just a question though, I'm assuming this guide will still give me Gingerbread at the end of it, correct?
Um, you mean stop at step 18 of the original guide you linked me or the one that KronicSkillz is suggesting? I honestly just use whatever the guide says/provides, I don't bring in any outside files. Previously I mentioned I might use another one because you suggested it would work well for me by keeping ICS. But originally I just follow the guides step by step.
Click to expand...
Click to collapse
At the end you'll end up with AT&T stock gingerbread. in the middle you'll be running a stock korean rom, but that is temporary.
as per your 2nd comment if you resintall stock ICS that will rebrick your recovery and CWM will cause another error if you ever try to run it.
this is the reason your phone had the errors you posted
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
If the whole purpose behind this is you just want ICS why didn't you just run the LG update tool, STOCK ICS can be updated with their stock PC usb tool.
anyways its too late for that.
to save your phone you have to follow that guide to restore it to original AT&T Gingerbread. then you perform a backup with CWM and THEN you can flash whatever ROM you want on your phone be it custom or Stock ICS. I have a feeling flashing the stock ics might rebrick your recovery though. not 100% sure on if it will or not.
---------- Post added at 01:24 PM ---------- Previous post was at 01:22 PM ----------
as per your question about which guide, i think we both linked you the same guide, except the one i linked was the Sticky version that was a little more detailed (i think) but in either case you should pick one guide and stick to it don't read both of them and go back and fourth you could get easily confused even though like i said i think they are the same guide/method of unbricking. There is a reason though that the guide i linked is the TOP STICKY on the forums for this phone. Because it is the solution to unbrick all p930s who have gotten bricked, which is almost anyone who updated their phone since they bought it, a few ppl got lucky and had Roms old enough that LG hadn't locked their recovery yet and they didn't get the error you were seeing.
The only reason I suggested stopping at step 18 was because it seemed like the v20f kdz file was being installed instead of the v10f because of the secure boot error. V20f is ICS, there is no logical reason why v10f is generating the error. Which kdz file are you flashing during that step in the guide?
Sent from my LG-P930 using xda app-developers app
Hi i rooted my phone (HTC One V) long time ago and have a custom ROM. I still have superuser in my settings. Yesterday, i don't know why, i installed superSU from play store but soon uninstalled it. Today i installed an app and it says device not rooted. I intakes superSU again and it said no SU binaries. In my settings there is superuser but i installed a root checker and it said no proper root found. Dies that mean i will have to root it again. I have sphongle ROM and Clockwork recovery (something like that). I am not an expert. Please help!!!
Sent from my One V using xda app-developers app
Reflash supersu ?
Sent from my HTC One V using xda app-developers
It wouldn't have been a problem. But I bricked my tablet a week ago and am trying to avoid it. I seem to have got scared since then. Any easy way. And i checked my apps lost superuser access too.
Sent from my One V using xda app-developers app
FocusBlast said:
It wouldn't have been a problem. But I bricked my tablet a week ago and am trying to avoid it. I seem to have got scared since then. Any easy way. And i checked my apps lost superuser access too.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I bet that while uninstalling the new SU app, it also uninstalled some SU binaries as a part of it. Just reflash the old SU trough recovery and no harm will be done. If you are scared you can always make a full backup.
I rooted my phone a long time ago by following tutorials. I failed a lot of times in the process. It took me 10 hrs to install my first custom ROM (legit good 10hrs since i started rooting and was stuck in HTC logo) Because i always did some mistakes. I am not scared of loosing data. I am scared of bricking my phone. Besides i don't remember what exactly i did when i rooted it. Right now I have a custom ROM (sphongle) and have clockwork recovery. Can some give me the link to files and tell me what exactly i need to do. I don't have much knowledge about rooting and stuff. Since i bricked my tablet. I really have got scared. I just lost confidence. It is funny but i have custom ROM and recovery but no root (that's what i think).
Sent from my One V using xda app-developers app
FocusBlast said:
I rooted my phone a long time ago by following tutorials. I failed a lot of times in the process. It took me 10 hrs to install my first custom ROM (legit good 10hrs since i started rooting and was stuck in HTC logo) Because i always did some mistakes. I am not scared of loosing data. I am scared of bricking my phone. Besides i don't remember what exactly i did when i rooted it. Right now I have a custom ROM (sphongle) and have clockwork recovery. Can some give me the link to files and tell me what exactly i need to do. I don't have much knowledge about rooting and stuff. Since i bricked my tablet. I really have got scared. I just lost confidence. It is funny but i have custom ROM and recovery but no root (that's what i think).
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Best way is then just to follow the guides once again. Just look for Rooting your HOV and flashing ROM guide here on forums. Follow and enjoy.
But i already have recovery boot loader unlocked and a custom ROM. Are u trying to say i have to do all of that again. Isn't there any way to just install something like a zip from recovery ?
Sent from my One V using xda app-developers app
Just follow the guide
http://forum.xda-developers.com/showthread.php?t=1598964
Ship to the step about rooting and follow all instructions. You'll do fine
Sent from a phone that's running a ROM
Thanks
mrcorey said:
Just follow the guide
http://forum.xda-developers.com/showthread.php?t=1598964
Ship to the step about rooting and follow all instructions. You'll do fine
Sent from a phone that's running a ROM
Click to expand...
Click to collapse
Thanks a lot. It is updating binaries. Didn't try any superuser app yet but trust you guys. Thanks a lot once again.
Thank you so much guys. I finally have root again. Superuser in settings is useless now but it doesn't matter. And in superSU settings there was an option to make it system app. Should I do it ?
Sent from my One V using xda app-developers app
After this it actually solved a notification bar glitch i always had. Don't know what fixed it. But yes now it works perfect too.
Sent from my One V using xda app-developers app
Glad you got it fixed
Sent from a phone that's running a ROM
I DOWNLOADED ALL THE FILES(LG DRIVERS,CM11, GOOGLE APPS) FOR THE ROOT PROCESS, I AM ON LG SPRINT OPTIMUS G 4.1.2 AND CLOCKWORK MOD RECOVERY ALWAYS SAYS "ERROR OCCURED WHILE FLASHING YOUR DEVICE" so i can not root it at all. ive looked everywhere but nothing works.so I CAN NOT BE GRANTED SUPERUSER ACCESS UNTIL THAT ERROR GOES AWAY I SUPPOSE..NEED HELP.
When I FIRST OPEN UP ROM MANAGER WITHOUT ANY ACTIONS IT SAYS "SUPERUSER WAS NOT FOUND GOOGLE IT"
espada4 said:
I DOWNLOADED ALL THE FILES(LG DRIVERS,CM11, GOOGLE APPS) FOR THE ROOT PROCESS, I AM ON LG SPRINT OPTIMUS G 4.1.2 AND CLOCKWORK MOD RECOVERY ALWAYS SAYS "ERROR OCCURED WHILE FLASHING YOUR DEVICE" so i can not root it at all. ive looked everywhere but nothing works.so I CAN NOT BE GRANTED SUPERUSER ACCESS UNTIL THAT ERROR GOES AWAY I SUPPOSE..NEED HELP.
When I FIRST OPEN UP ROM MANAGER WITHOUT ANY ACTIONS IT SAYS "SUPERUSER WAS NOT FOUND GOOGLE IT"
Click to expand...
Click to collapse
So you're on stock right now? And it is ZVC right? And you updated via updates or LGNPST, right?
If all of the above is correct, ... are you using the KK recoveries?
If you are, then when you flash the ROM you may need to install the flashable SuperUser.
If you're just trying to root and unlock your phone, look in the Development section for the root guide. You must be on stock to root/unlock your phone. If you used Freegee to unlock them you'll have the required recovery to flash KK ROMs.
Sent from my LG-LS970 using XDA Premium 4 mobile app
espada4 said:
I DOWNLOADED ALL THE FILES(LG DRIVERS,CM11, GOOGLE APPS) FOR THE ROOT PROCESS, I AM ON LG SPRINT OPTIMUS G 4.1.2 AND CLOCKWORK MOD RECOVERY ALWAYS SAYS "ERROR OCCURED WHILE FLASHING YOUR DEVICE" so i can not root it at all. ive looked everywhere but nothing works.so I CAN NOT BE GRANTED SUPERUSER ACCESS UNTIL THAT ERROR GOES AWAY I SUPPOSE..NEED HELP.
Click to expand...
Click to collapse
Ok first off, sheesh on the all caps bro - don't need to yell! lol. I am a little confused though. You downloaded all the files but how did you actually try to root? I'm confused because you say clockworkmod recovery says "error while flashing your device" but it's my understanding that you can't even install CWM without having root access. Can you still get back into your stock? If you can, look at your apps, if you see Superuser or SuperSu then you are rooted. If not, you have two options - use the Framaroot app that you can find in the play store. Install that and use the Gandalf exploit. Option two is to use Fiddy619's Universal root method, just search the general section here and you should find it. I have tried both and both have worked successfully. After that, you need to unlock your bootloader in order to install CWM or TWRP correctly. The easiest method is to install another app from the play store called "FreeGee" and use the sbl unlock method. It will unlock the bootloader and install either CWM or TWRP for you, your choice. If you have any questions or run into more problems just let me know and I'll help dude.
EDIT: @engine95 is much faster than I.
EDIT#2: I type too much, Lol! Also, I haven't used FreeGee in awhile and keep forgetting it's been overhauled - not sure if you even have to pick sbl unlock or it's just become the default.
Just barely. Besides... 2 heads are better than one.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Just barely. Besides... 2 heads are better than one.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ha ha, very true, and like always I'm over my thank limit for the day so thank you.
issues
engine95 said:
So you're on stock right now? And it is ZVC right? And you updated via updates or LGNPST, right?
If all of the above is correct, ... are you using the KK recoveries?
If you are, then when you flash the ROM you may need to install the flashable SuperUser.
If you're just trying to root and unlock your phone, look in the Development section for the root guide. You must be on stock to root/unlock your phone. If you used Freegee to unlock them you'll have the required recovery to flash KK ROMs.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i sent u a msg,keyboard caps got stuck lol
When I was Brand new learning how to do everything Fiddys root method was a breeze for me, all uphill from there
Sent from my Optimus G using XDA Premium 4 mobile app
k5t4j5 said:
When I was Brand new learning how to do everything Fiddys root method was a breeze for me, all uphill from there
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's how I rooted the first time before the lgog's glass back broke. But the second phone I got, I used framaroot, then freegee - had twrp installed before I left Best Buy. Hahaha.
Haha, yeah the more you learn the easier it gets it seems
Sent from my Optimus G using XDA Premium 4 mobile app
I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Get this one: MDB08I - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mdb08i-factory-64536fcf.tgz , unpack it fully down to the folder that has the image files in it and that can be anywhere (let's say \temp for now).
Notice that there is a batch file that can do a full flash of the OS that you'll have unpacked from the .tgz file. You'll use that once in Fastboot to flash it. Don't worry about having TWRP or a special bootloader before you do any of this. Just get into fastboot (like "adb reboot bootloader" or hold down up&down&power buttons for awhile until in fastboot). Once in flashboot:
Flash MDB08I, boot things up, set things up, make sure it seems "normal" and check the "about phone" settings, and then you should be set to do what you want with the modified image & TWRP, etc.
I don't know what I'm doing wrong but when I try to flash I get an error "fastboot is not recognized...blah."
Sent from my Nexus 5X using XDA Free mobile app
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
You need to put the extracted files from the download "flash-all.sh, flash-all.bat, flash-base.sh bootloader-bullhead-bhz10i.img, image-bullhead-mdb08i.zip, radio-bullhead-m8994f-2.6.28.0.065.img" in the same folder as platfrom-tools. From there you run the flash-all.bat in the command prompt. just did it today.
dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
If you are getting confused you can always use the Unified Android Toolkit to download/flash the MDB08I image automatically. It will guide you through decrypting and rooting it too.
If you want to learn and do it all manually then good luck
Mark.
dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
You say that you "confirmed fastboot and adb are working correctly", but that doesn't sound right since your prior post said that "fastboot not recognized". Everyone else that's posted is on the right track and you need to be certain that fastboot (and adb for that matter) are in the correct path or they won't run or be recognized. It's not automatic. You need to either modify %PATH% var in windows, but that's semi-complex, or take the easy road, and move a copy of fastboot & adb to the same folder your image files (.img) are in. Also be certain to move the 'flash-all.bat' file(s) to the same place.
Change your directory to be where all those files are. Be certain the device is in fastboot mode and then make sure it's all working by doing this (or these) commands:
Code:
c:\{place-where-it's-all-at}: fastboot devices
That command should list some number which is the device number which verifies that fastboot is recognized and that the device is recognized.
you can do the same thing with adb (adb devices, look at the number).
---------------------- If that works.... -----------------
Stay in that folder and do the flash-all.bat (OK, I don't recall the exact name of their everything flash file, but I think it's that). It takes some time, but I've used these instructions to help a couple people through this.
Of course, mskip's way is also fine. Whatever works is good. -- Good luck. You're no where near being bricked and in good shape to get this done.
I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
The way I've talked about flashing the image, you don't need TWRP, or anything before you do it, other than what I said. If someone has now put up a zip version of the image, then yeah, you'd need custom recovery, but you don't need to use a zip image. It's less confusing just to use the native stuff and fastboot.
Is fastboot working or not. Are you sure you are getting the phone into fastboot? Can you get output from a "fastboot devices" command? Also, please give us the exact error messages. Write them down when you see them. It'll help whichever of us is trying to help.
I helped someone with this type of problem over here http://forum.xda-developers.com/showpost.php?p=63439400&postcount=17 , so maybe reading that will help.
I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Good. There's no point in installing TWRP at all unless you allow modifications. Allow them and tell that screen to go away forever. Good luck.
Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Once you get to this point (installing TWRP), it's best to find & follow the best guide (by that I mean that people had the least problems with) verbatim. Then ask questions in that thread:
I took a quick look and this one looks fine: http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Another way to to use mskips ways, but ask questions afterward in his thread.
I don't have a 5x (or anything like it) and I only really want to comment on things I've done a number of times before. My only comment about boot "quickly" vs. "booting normally", is that the first time you've done something "traumatic" like unencrypting, or wiping something, then of course it takes longer to do a regular boot. Booting into recovery should always be nearly instant.