Related
Is lg or Google providing flasher for N4.if yes then how to get it.
If no then which is safest way to flash N4.
I an not having any idea about android . N4 is my first android device so please help me.
http://developer.android.com/sdk/index.html
Then read the many tutorials around here.. Stay away from Toolkits..
Toolkits are for begginers. He's not gonna know how to fastboot flash that fast either. But I recommend that being your last option.
Sent from my Nexus 4 using xda premium
styckx said:
http://developer.android.com/sdk/index.html
Then read the many tutorials around here.. Stay away from Toolkits..
Click to expand...
Click to collapse
I am reading couple of tread but I can't stuck to one of the method.now I am reading efrant method shall i try this. basically i am not understand collecting drivers and flashing .is their any method just installing pc suit & all legal work which we use for older devices. one more how to launch command prompt do i type it in "RUN".
I dont understand why he should stay away from toolkits, I mean that f he doesn't want to learn how to develops roms than toolkits are the best for him
Sent from my Nexus 4 using xda app-developers app
Odp: how to flash(format) N4.
OH cmon guys. Toolkits are good for noobs. I tried to use those all tutorials and i didn't even install proper drivers correctly. IF he screw up smth he will be dissapointed. My opinion first toolkit than learn and do it manualy if you want.
Sent from my Nexus 4 using xda app-developers app
GS150R said:
I am reading couple of tread but I can't stuck to one of the method.now I am reading efrant method shall i try this. basically i am not understand collecting drivers and flashing .is their any method just installing pc suit & all legal work which we use for older devices. one more how to launch command prompt do i type it in "RUN".
Click to expand...
Click to collapse
- Install the Naked usb drivers 0.72 from here http://forum.xda-developers.com/showthread.php?t=1996051
- Install the Platform-tools from here http://developer.android.com/tools/sdk/tools-notes.html.
- Connect the phone with the pc and install the drivers you downloaded.
Set up adb, here is a how to http://forum.xda-developers.com/showthread.php?t=1590800
Open cmd and type : adb devices, you should see a serial number now.
Type the command and hit enter.
Some Adb commands:
See if the adb drivers are installed correctly: adb devices
Reboot: adb reboot oem
Bootloader: adb reboot bootloader
See if the fastboot drivers are installed correctly: fastboot devices
Unlock bootloader: fastboot oem unlock
Flash recovery: fastboot flash recovery recovery-name.img
Flash kernel: fastboot flash boot name boot.img.
I hope this is a kind of a start to get familiar with this stuff, the problem with toolkits is that you will stay a noob forever and when a problem occurs people have no idea how to fix it because they often have no clue whats happening.
Using a toolkits is like watching tv all the time, it prevents you to think and it softens the brain
Odp: how to flash(format) N4.
Open command and write: adb devices. Nothing happen. I got installed drivers correctly because i root my phone already. Wrong command or filename.
Sent from my Nexus 4 using xda app-developers app
Adikbzik said:
Open command and write: adb devices. Nothing happen. I got installed drivers correctly because i root my phone already. Wrong command or filename.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
first type: cd c:\android-sdk\platform-tools or wherever you installed the sdk. The sdk folder must be installed directly on the C (or other) drive and NOT in a map/folder.
Here is a tutorial to set up adb: http://www.youtube.com/watch?v=oaNM-lt_aHw
Adikbzik said:
OH cmon guys. Toolkits are good for noobs. I tried to use those all tutorials and i didn't even install proper drivers correctly. IF he screw up smth he will be dissapointed. My opinion first toolkit than learn and do it manualy if you want.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
toolkits are great, but every single time ive used them for nex4 i had a broken phone afterwards. even for such simple things like flashing a recovery. fastboot is such a simple tool, i would also recommend using that instead.
molesarecoming said:
toolkits are great, but every single time ive used them for nex4 i had a broken phone afterwards. fastboot is such a simple tool, i would also recommend using that instead.
Click to expand...
Click to collapse
Everything you know or are able to do is easy
The first time you do this however is always a search and trial and error thing.
I agree, efrants guide is kinda confusing if your completely new to android. But its very complete, here's another way you can go about using it...
1st, follow steps 1-8 (stop after unlocking boot loader) in this root tutorial. http://www.androidrootz.com/2012/11/how-to-root-nexus-4-on-windows.html?m=1 . this is an easy way to get your fastboot folder set up. Power off phone when done.
Next, download the nexus 4 Occam image here: https://developers.google.com/android/nexus/images#occamjdq39 . use 7-zip to extract it anything that is a zip file. Youll probably have to extract 2-3 times to get all 6 .img files you need. Once you get all 6 img files, move them to the Rootnexus4 folder.
Last, power your phone back into the boot loader by holding the vol buttons + power. Go back to efrants tutorial, go back to your command prompt, and start with part D) 6 (the part about flashing boot loader). Keep on following the instructions from there and u should be good to go http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using xda app-developers app
I got SDK working now. Thanks for video, nowhere says to add path in Computer properties that's why my command didn't read adb. Now i can use brain to flash :victory:
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
yes
Sent from my Nexus 4 using xda app-developers app
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
g2uzer said:
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
I used Mr Skip's and it worked really well, most important thing to get right is installing the drivers on your PC, I donated to him cause it has so many options and worked so well
Never have and never will. Once you learn fastboot it's too much fun playing in the command prompt lol.
spaceman860 said:
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
g2uzer said:
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
i disagree with you..
instead of using "done", id use "profit" :silly:
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
soham_sss said:
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
simms22 said:
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
Click to expand...
Click to collapse
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd like a video of this too.
Can you brick your phone while unlocking? Or just while flashing?
g2uzer said:
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
use the nexus 4 toolkit by msskip..
its the best one so far and very easy to use...and dont worry abt bricking..
post if any issues,,.
No toolkit. It's important to know how to use fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta
Unlocking the bootloader and rooting for new users
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, like I said, the toolkit makes it a lot easier to flash a factory image and frankly, I think it's safer. Less room for mistakes. The less you toy around with flashing the bootloader and the radio, the better chance you have of not bricking your device. Fortunately, when your bootloader is unlocked, as long as you aren't doing anything crazy, you will have a hard time bricking your device. If you have any further questions while you're working on it shoot me a PM and I will try to help. Good Luck!
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Superb, all this I know already as I did this with one v
But, I read in some tutorial that if you don't reboot to stock recovery and data reset your phone AFTER you've unlocked the boot loader, you will end up with a soft brick? Is it true?
Sent from my Nexus 4 using xda app-developers app
I've been playing g with androids for a long time and dozens of devices. Personally have never used a toolkit and its hard for me to recommend or knock them.
My view is a toolkit teaches you nothing
If a toolkit was made so was another method
Everyone will have an issue with something at some point, so the more you learn now the less freaking out latter
Learning to do thongs yourself will always be safer, I mean yes manually typing a dd command can be dangerous but if you know what you are doing you know when to be cautious, there will always be an example for either argument on this, but I truly can't see a reason to believe a tool kit is safer
But I'm a to each their own sorta guy, but also one who feels the need to learn as much as possible so will promote as much manually methods for anything in life and will do my best to stay away from auto-just-about-anything.... Just a my $.02
Sent from my Nexus 7 using xda premium
Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.
Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)
For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.
Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.
demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks
Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
fir1996 said:
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
Click to expand...
Click to collapse
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
JudgeDread11 said:
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
Click to expand...
Click to collapse
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Dylan2232 said:
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
JudgeDread11 said:
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
Click to expand...
Click to collapse
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Dylan2232 said:
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Click to expand...
Click to collapse
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying anything is learning how to backup and restore.
JudgeDread11 said:
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying any freething is learning how to backup and restore.
Click to expand...
Click to collapse
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Dylan2232 said:
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Click to expand...
Click to collapse
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
hi , good news for Huawei y5 2017(MYA-L22) users.
Download latest lineage14.
visit to my blog.
cheers
https://p55novo.blogspot.com/2018/07...e-141-for.html
JudgeDread11 said:
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
Click to expand...
Click to collapse
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Dylan2232 said:
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Click to expand...
Click to collapse
For rooting you need unlocked bootloader ( if you don't do ir then below won't work).
1)download the 4pda app from google play store and register an account .
2) download the TWRP.img file from 4pda website here is the link
https://4pda.ru/forum/index.php?showtopic=823938&view=findpost&p=74424572
3) enable developer mode in your phone by going to setting about phone , tap 6 times on the build number.
4)go to developer mode and enable usb debugging and oem factory unlock .
5) go to your pc install adb here link https://forum.xda-developers.com/showthread.php?t=2588979
6) now conect the phone to the pc and run cmd , type adb reboot bootloader . (Your device ahould restart and enter bootloader mode (white screen)).
7) now take the TWRP.img (must be copyied to desktop ) and type in cmd cd desktop.
8) type fastboot flash recovery TWRP.img (change the file name to TWRP ).
9) type fastboot reboot.
Now you have successfully install TWRP on your device.
Continue... If replied
Since I bought the OnePlus 5 when it launched, I have not rooted a phone since. I have since gotten rid of my windows computer and now have a Chromebook. Can anyone point me to a how to with a Chromebook if possible? All I find are articles on rooting/unlocking a Chromebook. Thanks for the help.
Sent from my ONEPLUS A5000 using Tapatalk
jbela1911 said:
Since I bought the OnePlus 5 when it launched, I have not rooted a phone since. I have since gotten rid of my windows computer and now have a Chromebook. Can anyone point me to a how to with a Chromebook if possible? All I find are articles on rooting/unlocking a Chromebook. Thanks for the help.
Click to expand...
Click to collapse
I plan on doing this too, you have to put your Chromebook in developer mode and then you can use ADB and Fastboot, they are built in. The only possible snag I was reading about is that you might have to use a script to update ADB and Fastboot for them to work properly. Then you can use Fastboot to unlock the bootloader and boot or flash TWRP. I'm hoping it will work, I have done it before. Once your Chromebook is in developer mode(not the developer channel), you can open up the terminal and type 'shell', and you will have ADB and Fastboot there.
It is indeed possible. I have a Chromebook Pro and had to do this for my Mate 10 which was a *****. Let me find the thread, it essentially has a script that allows certain apps to run in system mode, that way you don't have to keep using +r etc etc. i'll find it.
And yes, it has to be in Developer mode and it's different depending on which Chromebook you have
EditL https://www.xda-developers.com/adb-fastboot-chromebook-chrome-os/
YrrchSebor said:
I plan on doing this too, you have to put your Chromebook in developer mode and then you can use ADB and Fastboot, they are built in. The only possible snag I was reading about is that you might have to use a script to update ADB and Fastboot for them to work properly. Then you can use Fastboot to unlock the bootloader and boot or flash TWRP. I'm hoping it will work, I have done it before. Once your Chromebook is in developer mode(not the developer channel), you can open up the terminal and type 'shell', and you will have ADB and Fastboot there.
Click to expand...
Click to collapse
sledgie said:
It is indeed possible. I have a Chromebook Pro and had to do this for my Mate 10 which was a *****. Let me find the thread, it essentially has a script that allows certain apps to run in system mode, that way you don't have to keep using +r etc etc. i'll find it.
And yes, it has to be in Developer mode and it's different depending on which Chromebook you have
EditL https://www.xda-developers.com/adb-fastboot-chromebook-chrome-os/
Click to expand...
Click to collapse
Ah thanks, I came across that thread when I was researching it too. I've never rooted a Huawei phone before, but I believe the OnePlus should be pretty easy, it just needs a couple of basic fastboot commands so I'm hoping it's just a matter of getting fastboot to recognize the device and run the commands.
jbela1911 said:
Since I bought the OnePlus 5 when it launched, I have not rooted a phone since. I have since gotten rid of my windows computer and now have a Chromebook. Can anyone point me to a how to with a Chromebook if possible? All I find are articles on rooting/unlocking a Chromebook. Thanks for the help.
Click to expand...
Click to collapse
So I was able to unlock the bootloader with my Chromebook. I had to put it into developer mode, and then I ran a quick script that I found on a guide here: https://www.howtogeek.com/358285/how-to-use-adb-and-fastboot-on-a-chromebook/amp/
Then once I booted my Oneplus 6T into fastboot mode, fastboot recognized the device and unlocked the bootloader.
Another update: everything works fine, ADB and fastboot. The 6T does not have an official TWRP Recovery yet, but the unofficial one works okay, and you can just boot it rather than installing it, and then sideload Magisk to root that way. All up and routed here with Chromebook only.
YrrchSebor said:
So I was able to unlock the bootloader with my Chromebook. I had to put it into developer mode, and then I ran a quick script that I found on a guide here: https://www.howtogeek.com/358285/how-to-use-adb-and-fastboot-on-a-chromebook/amp/
Then once I booted my Oneplus 6T into fastboot mode, fastboot recognized the device and unlocked the bootloader.
Click to expand...
Click to collapse
I cannot for the life of me get this to work on my Chromebook plus. The scripts down work. I unrooted my phone to test some things, then my computer died. I desperately want to root again without waiting for my laptop to get fixed.
Ryano89 said:
I cannot for the life of me get this to work on my Chromebook plus. The scripts down work. I unrooted my phone to test some things, then my computer died. I desperately want to root again without waiting for my laptop to get fixed.
Click to expand...
Click to collapse
Which Chromebook plus do you have? I just remembered that, according to the guide, the scripts to fix ADB and fastboot work on intel-based Chromebooks.
YrrchSebor said:
Which Chromebook plus do you have? I just remembered that, according to the guide, the scripts to fix ADB and fastboot work on intel-based Chromebooks.
Click to expand...
Click to collapse
I believe that mine is the lesser hexacore version.
Ryano89 said:
I believe that mine is the lesser hexacore version.
Click to expand...
Click to collapse
that must be the exynos processor so I'm not sure what the fix is if there is one. Just brainstorming here but could you install ADB and fastboot on the Linux terminal if your Chromebook has Linux app functionality already?