[q] rooting nexus 4 kitkat 4.4.2? Help!! - Nexus 4 Q&A, Help & Troubleshooting

hey guys im new to the whole rooting and the whole android world .. anyways im on the latest version of kitkat (4.4.2) on my nexus 4 and i dont know how to root it. can anyone help me please?
also i dont know if its normal but my nexus 4 still looks like 4.3 JB .. any suggestions as to what can be the issue?
all help is greatly appreciated. thanks

The ui looks basically the same except for more white than blue.
Follow the guides on how to root.
Won't lay it all out for you since there a million guides and so on.
But you will need to unlock the bootloader. That will wipe all your data off your device. Everything will be gone.
After that you just need to boot up and put the su. Zip on the device. Reboot into the bootloader again flash a custom recovery. Or just boot it. Then flash the zip you put on the phone with the custom recovery.
That's it. Done. Now stock rooted.
If this don't make sense to you. It probably won't. Read the quides in general.

albundy2010 said:
The ui looks basically the same except for more white than blue.
Follow the guides on how to root.
Won't lay it all out for you since there a million guides and so on.
But you will need to unlock the bootloader. That will wipe all your data off your device. Everything will be gone.
After that you just need to boot up and put the su. Zip on the device. Reboot into the bootloader again flash a custom recovery. Or just boot it. Then flash the zip you put on the phone with the custom recovery.
That's it. Done. Now stock rooted.
If this don't make sense to you. It probably won't. Read the quides in general.
Click to expand...
Click to collapse
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..

zareefpeeroo said:
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..
Click to expand...
Click to collapse
Did you install Android SDK in your PC? It needs to be installed and set up first, and making sure ADB debugging box is checked in Developer Options in your phone. In addition, when you plug your phone into your PC the first time, look in your phone and select Yes when a dialog pop up asking for authorization to remember your phone.

zareefpeeroo said:
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..
Click to expand...
Click to collapse
Adb offline is a different issue. But it's irrelevant. Adb is not needed.
We need to use fastboot. Not adb. You're doing nothing but wasting your time with adb.
You would get adb up and running for what exactly? To issue the command adb reboot bootloader or adb reboot recovery..... Forget adb...

Why are you trying to root? You shouldn't undertake such tasks if you're not 100% educated on the subject.
Sent from my Nexus 4 using xda app-developers app

Related

[Q] How do you brick your phone?

Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Nexus devices are hard to brick. Just to be on the safe side, just follow the videos, follow instructions and you'll be fine.
"Riddle me this, Riddle me that."
It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results
Federico_96 said:
It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results
Click to expand...
Click to collapse
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
I used wugfresh's toolkit for the n7 and the n4 with absolutely no trouble. Other than not letting the drivers install automatically drivers. Once I let them go on auto it worked like a charm windows xp.
Sent from my Nexus 4 using Tapatalk 4 Beta
Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?
dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
download the 4.2.2 factory images and keep them handy for emergencies, setup and learn fastboot, and never flash anything for another device/not meant for the N4. if you do this, you will never brick it.
Federico_96 said:
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?
Click to expand...
Click to collapse
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Th3RiddL3r said:
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
OK so now typing adb devices i get a serial number and "device", i suppose that now adb is working,and now i installed mtp drivers using this guide
Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
what's the difference between auto root and manual? which is better?
Questions: 1.Difference between manually rooting and auto-rooting
2. This thing say we can root without unlocking bootloader, is that really legit and if so will our stuff be wiped or no?
3.How to back up my phone? Which program to use?
4.Long does it take to root?
dreseansr said:
what's the difference between auto root and manual? which is better?
Click to expand...
Click to collapse
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.
BobWalker said:
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.
Click to expand...
Click to collapse
Wait I'm confused, Clockwordmod is to backup my stuff?
dreseansr said:
Wait I'm confused, Clockwordmod is to backup my stuff?
Click to expand...
Click to collapse
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.
BobWalker said:
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.
Click to expand...
Click to collapse
hm ok so is there any video showing the steps of how to back up my phone or using this programs?
You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta
dreseansr said:
hm ok so is there any video showing the steps of how to back up my phone or using this programs?
Click to expand...
Click to collapse
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.
dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Well I think there is an forum rule that says we're not supposed to discuss about things such as how to brick your phone. And the most, if not all, of the bricks on the Nexus 4 are recoverable anyways.
That being said, before you flash anything, especially kernel or bootloader, be absolutely sure the file is made for your device
Sent from my Nexus 4 using xda app-developers app
nelsonator1982 said:
You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If you have read the thread you will see that i've done that already but since he/she is informing me on a program that they used, i am simply asking for a video that showed them how to do it so i know everything is legit.
BobWalker said:
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.
Click to expand...
Click to collapse
Thank you

can someone please help?

I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
You can use fastboot to erase your current partitions then manually flash the 4.3 stock images.
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
chrisbo4 said:
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
Click to expand...
Click to collapse
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Rirere said:
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Click to expand...
Click to collapse
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
chrisbo4 said:
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
Click to expand...
Click to collapse
Install this through device manager.
http://d-h.st/kDu
Username invalid said:
Install this through device manager.
http://d-h.st/kDu
Click to expand...
Click to collapse
Okay, it's installed. I'm not sure what I should unzip though?
chrisbo4 said:
Okay, it's installed. I'm not sure what I should unzip though?
Click to expand...
Click to collapse
You can either flash stock images with fastboot or install TWRP then flash stock zip file.
chrisbo4 said:
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
Click to expand...
Click to collapse
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
gunner1937 said:
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
Click to expand...
Click to collapse
Thank you for the information, and I'm not offended at all. I spent most of last night reading, and attempting to get adb running on my computer. I experienced issues getting drivers installed, and the computer recognizing the device. Also, trying to find the directories... I'll keep searching to see if I can get this figured out. Thank you again!
Thanks to everyone for helping me through this problem. After a lot of searching, research, reading, and video tutorials, I flashed stock images to the N7 via fastboot. I always thought that adb and fastboot was way too advanced for me (and it probably still is), but at least I got the basics down. Thank you all again.

root issue

I updated my android to 4.3. since then I lost the root permissions. The phone shows as being unlocked when I start it up. when I have tried different programs or apps, I can't get the permissions back. One program I have tried, sorry, don't remember the name, said it was going to reboot the phone, but that never happened. I used it with my older version of android and it worked fine.
When I got into recovery mode, I the the android robot with the red !, saying no command.
I wanted to see if anyone knew what might be going on and what I could do to get back my permissions.
Thanks
jrwn said:
I updated my android to 4.3. since then I lost the root permissions. The phone shows as being unlocked when I start it up. when I have tried different programs or apps, I can't get the permissions back. One program I have tried, sorry, don't remember the name, said it was going to reboot the phone, but that never happened. I used it with my older version of android and it worked fine.
When I got into recovery mode, I the the android robot with the red !, saying no command.
I wanted to see if anyone knew what might be going on and what I could do to get back my permissions.
Thanks
Click to expand...
Click to collapse
Android 4.3 contains security fixes that require root to be updated. Download the SuperSu v1.55 zip from http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip and copy the file to the Nexus' internal storage. Reboot the phone to recovery and install UPDATE-SuperSU-v1.55.zip from Clockworkmod or TWRP, then reboot the phone. You should now be able to grant privileges to the apps that require root access.
BobWalker said:
Reboot the phone to recovery and install UPDATE-SuperSU-v1.55.zip from Clockworkmod or TWRP, then reboot the phone. You should now be able to grant privileges to the apps that require root access.
Click to expand...
Click to collapse
The big issue I am running into is when I try to go to recovery, I get the dead android and "no command" error.
jrwn said:
The big issue I am running into is when I try to go to recovery, I get the dead android and "no command" error.
Click to expand...
Click to collapse
you updated stock, so you now have the stock recovery, thats the "dead" android. flash a custom recovery via fastboot, then flash the supersu su binaries via your new custom recovery. youll be fine, make sure to stay away from root toolkits or you will nwver learn anything, like this. this is such a basic thing to know to do, yet people that use root toolkits dont know.
OK, I'll have to try that tonight or over the next couple of days when I have a chance. Thank you.
jrwn said:
OK, I'll have to try that tonight or over the next couple of days when I have a chance. Thank you.
Click to expand...
Click to collapse
if you dont know how, read a little. its really easy. its a matter of typing one line into a command window
OK, I've tried it, but it doesn't seem as if the computer is communicating with the phone. I have also tried one of the auto programs to do it, but it gets stuck at "waiting for device." If I reboot the device and try to get into recovery mode, I just get a dead android saying "no command" I can't get any other options to try to reset the devices back to factory settings.
I have tried the reset option in the settings menu, but It still saves information and doesn't take the phone back to 4.2, which is what I first had.
I'm hoping someone has some ideas on what I can do. On the other hand, I am planning on upgrading my wife's phone. I might just get a new one, and give her this one, although I'm not sure if I want to get a nexus, maybe a different one this time.
jrwn said:
OK, I've tried it, but it doesn't seem as if the computer is communicating with the phone. I have also tried one of the auto programs to do it, but it gets stuck at "waiting for device." If I reboot the device and try to get into recovery mode, I just get a dead android saying "no command" I can't get any other options to try to reset the devices back to factory settings.
I have tried the reset option in the settings menu, but It still saves information and doesn't take the phone back to 4.2, which is what I first had.
I'm hoping someone has some ideas on what I can do. On the other hand, I am planning on upgrading my wife's phone. I might just get a new one, and give her this one, although I'm not sure if I want to get a nexus, maybe a different one this time.
Click to expand...
Click to collapse
install the right drivers. and dont use one of those "auto" programs, thats why you dont know what you are doing now.
simms22 said:
install the right drivers. and dont use one of those "auto" programs, thats why you dont know what you are doing now.
Click to expand...
Click to collapse
I did try to do it manually, the phone didn't respond. This is why I also tried a program. You are correct, I don't know what to do from this point.
jrwn said:
I did try to do it manually, the phone didn't respond. This is why I also tried a program. You are correct, I don't know what to do from this point.
Click to expand...
Click to collapse
you need to get the driver installed to your computer, fastboot as well. when its all ready, open fastboot and a command window then and type.. fadtboot devices. then itll see your device(or not if the driver isnt installed). when it sees your device, you need fastboot flash your recovery.. fastboot flash recovery recoveryname.img. then you need to flash the latest su binaries via your recovery(latest supersu will work).

LG G2 Fastboot

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.

Please help stuck on teamwin screen, can't enter into Recovery

I just got my brand new Aluminum Nexus 6P last night, I wanted to test out the new Developer Preview #4 right away, so enrolled in the program and got the OTA update which I took, and rebooted running Android N, looks pretty neat, and nice tweaks, and some new features. But I always like to run Rooted and install custom ROM's, but Root is #1 for me.
Ok so I need a little help, I am following the excellent video by Rootjunky ( thank you ), and got through the unlocked bootloader part easily, and now installed TWRP Recovery easily too, but upon first time booting into TWRP, it's just sitting at the Blue and Gray teamwin screen, and not doing anything else, it's not actually entering into the Recovery, to see the list of options, etc...
I powered the device down, and started up again in Fastboot mode, then chose Recovery, and does the same again, just sits at the blue gray colored teamwin screen, and does nothing.
What happened ?
UPDATE:
I powered the device down / off. Then started up again, it went and booted up, to the fresh clean Android N DP 4. But I am not rooted at all yet, due not being able to fully enter Recovery and flash the SuperSU zip yet.
The issue is because of encryption... you would need to run fastboot format userdata... and then flash twrp... you would then be able to use it... p.s use the latest twrp version
SENT... isn't that enough
rohit25 said:
The issue is because of encryption... you would need to run fastboot format userdata... and then flash twrp... you would then be able to use it... p.s use the latest twrp version
SENT... isn't that enough
Click to expand...
Click to collapse
Can you spell that out a little bit for me please ?
So right now I am on the Android N beta 4, I have an unlocked bootloader, and TWRP not booting up for me, so do I need to restart the whole rooting and Recovery method all over again ? I do have a modified boot.img from another thread here dated 06-15, but at what point am I supposed to run the command for format data ? And what is the exact correct sentence and spelling of that command I should enter ?
Download Wugfresh Toolkit. It'll carry you through the process with no problem.
Best part, a Nexus is hard to brick. ?
Curiousn00b said:
Download Wugfresh Toolkit. It'll carry you through the process with no problem.
Best part, a Nexus is hard to brick. ��
Click to expand...
Click to collapse
Wow thanks, but never heard of this thing before. Is it like a all-in-one root kit, that does it all for you ? I have normally followed the YouTube videos on how to do it the long way with command prompt and pushing files to the phone, etc...
Silly question, but with this toolkit, is this something I download and install on the phone itself, or run through my PC ?
Zorachus said:
Wow thanks, but never heard of this thing before. Is it like a all-in-one root kit, that does it all for you ? I have normally followed the YouTube videos on how to do it the long way with command prompt and pushing files to the phone, etc...
Silly question, but with this toolkit, is this something I download and install on the phone itself, or run through my PC ?
Click to expand...
Click to collapse
Could you stop posting the same question in multiple threads? It's inconsiderate of people's time.
Sent from my Nexus 5X using Tapatalk
Holy crap, that Nexus Root Toolkit, is like something from Star Trek future. Did Commander Data write this amazing program ? UNBELIEVABLY FANTASTIC PROGRAM.
I was just on the stock phone, not rooted or TWRP or anything, I then install this nexus Toolkit, run the program, and it totally rooted and installed custom TWRP Recovery on my phone, while still being on the Android N 4 preview. I am blown away at how it did all of this, in like 5 minutes.
Couple questions please;
- Android N doesn't have Xposed, so that kind of sucks, but totally expected with this being a beta preview obviously.
- Seems like some root programs not even working, like my classic AdAway, is that due to this being N ?
- How hard is it to revert back to a MM ROM ? Let's say I want to install Pure Nexus ROM, which is already on my SD Card, can I just boot into TWRP Recovery, wipe system, and flash Pure Nexus + GAPPS and reboot ? Or do I need to do something special first to downgrade to MM coming from N now ?
Zorachus said:
Holy crap, that Nexus Root Toolkit, is like something from Star Trek future. Did Commander Data write this amazing program ? UNBELIEVABLY FANTASTIC PROGRAM.
I was just on the stock phone, not rooted or TWRP or anything, I then install this nexus Toolkit, run the program, and it totally rooted and installed custom TWRP Recovery on my phone, while still being on the Android N 4 preview. I am blown away at how it did all of this, in like 5 minutes.
Couple questions please;
- Android N doesn't have Xposed, so that kind of sucks, but totally expected with this being a beta preview obviously.
- Seems like some root programs not even working, like my classic AdAway, is that due to this being N ?
- How hard is it to revert back to a MM ROM ? Let's say I want to install Pure Nexus ROM, which is already on my SD Card, can I just boot into TWRP Recovery, wipe system, and flash Pure Nexus + GAPPS and reboot ? Or do I need to do something special first to downgrade to MM coming from N now ?
Click to expand...
Click to collapse
Adaway does work you need systemless one? no just wipe everything other then internal flash rom gapps and vendor

Categories

Resources