Database Users

[Q] Nexus 7 (4.1.2) can't root

Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message

IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...

yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.

NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.

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

comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.

bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.

comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.

NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...

I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.

comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...

I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2

I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock

Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?

Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app

MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.

To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] [HELP] Missing recovery 4.3

I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
EDIT: when I get the no command "fallen android" when i select recovery from the bootloader on pressing power+vol up does give me acces to the stock recovery. But even on using wug's 1.6.6 root kit I'm unable to root the device and install a custom recovery

Vikas Rao said:
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
Click to expand...
Click to collapse
Have you tried redownloading twrp seems like a bad download?

yamani.m said:
Have you tried redownloading twrp seems like a bad download?
Click to expand...
Click to collapse
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot

Vikas Rao said:
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Click to expand...
Click to collapse
I would try to flash the full stock google image with fastboot and see what happens ?

Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!

EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
I also did it this morning, works fine

EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
Nope did the same thing! gives me the cannot load error, I just copy pasted the filename so can't go wrong there. And a stock rom flash is an option but the thing is i don't have a custom recovery nor root access for titanium backup don't wanna spend time again personalizing. I'm sure there is a simpler way.

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

[Q] Regretting upgrading to 4.4 on Nexus4

Need help...
I installed the new PA AOSP 4.4 on Mako. I had not installed GAPPS. Started the phone up into 4.4, thought "don't like this", turned off went into CWM, went into recovery and was hit with a knocked over android with the red warning sign. I have tried multiple times without success to get into recovery.
I downloaded Flashify and it says I do not have SU permission on your device. Downloaded superSU and was greeted with the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
How do I get back to 4.3? is it possible? or do I have to wait for a root now? Is there any way just to get GAPPS or the Playstore?

Find efrant's guide on flashing back to stock using fastboot. It'll get you 100% back to stock, and teach you the right way to do it.

username8611 said:
Find efrant's guide on flashing back to stock using fastboot. It'll get you 100% back to stock, and teach you the right way to do it.
Click to expand...
Click to collapse
Can you do me a huge favor and find it, I have no idea which one I am looking at.

PhysicsNerd said:
Need help...
I installed the new PA AOSP 4.4 on Mako. I had not installed GAPPS. Started the phone up into 4.4, thought "don't like this", turned off went into CWM, went into recovery and was hit with a knocked over android with the red warning sign. I have tried multiple times without success to get into recovery.
I downloaded Flashify and it says I do not have SU permission on your device. Downloaded superSU and was greeted with the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
How do I get back to 4.3? is it possible? or do I have to wait for a root now? Is there any way just to get GAPPS or the Playstore?
Click to expand...
Click to collapse
so what happened is you did everything wrong. first off, you should have flashed the rom, gapps, and supersu 1.65(for root). and that android laying there is the stock recovery. you lost it because the rom replaced your recovery with the stock recovery. all you have to do is flash a custom recovery via fastboot, then flash supersu 1.65 in the custom recovery that you just installed. next time, figure out what you have to do before doing it.

simms22 said:
so what happened is you did everything wrong. first off, you should have flashed the rom, gapps, and supersu 1.65(for root). and that android laying there is the stock recovery. you lost it because the rom replaced your recovery with the stock recovery. all you have to do is flash a custom recovery via fastboot, then flash supersu 1.65 in the custom recovery that you just installed. next time, figure out what you have to do before doing it.
Click to expand...
Click to collapse
Thank you so very much, I thought I was downloading PA 3.99 just under a different name which is why it kind of shocked me when GAPPS 4.3 said it couldn't install.
I really appreciate your time, I was panicking here for a second.

PhysicsNerd said:
Thank you so very much, I thought I was downloading PA 3.99 just under a different name which is why it kind of shocked me when GAPPS 4.3 said it couldn't install.
I really appreciate your time, I was panicking here for a second.
Click to expand...
Click to collapse
na, this is a simple faux pas made by hundreds of thousands(it seems) over my android years. and its not even a big error, its easily fixed, but it does freak out way too many

simms22 said:
na, this is a simple faux pas made by hundreds of thousands(it seems) over my android years. and its not even a big error, its easily fixed, but it does freak out way too many
Click to expand...
Click to collapse
Happy that there is a solution. I'm having the same exact issue and i don't know flashing the recovery image in fastboot mode. If you could put up a link or a video on how to go about it , that would be great

Trying to push recovery.img using fastboot , but gettin "waiting for device"error. should have just let the 4.3 stay. damn. no gapps. no recovery .

747nemesis said:
Trying to push recovery.img using fastboot , but gettin "waiting for device"error. should have just let the 4.3 stay. damn. no gapps. no recovery .
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=2015469 or other toolkit

PhysicsNerd said:
Need help...
Started the phone up into 4.4, thought "don't like this"
Click to expand...
Click to collapse
Just out of curiousity, why didn't you like it? You can always get a different launcher

Simplest way to fix it is DL one of the nexus tool kits. Me I use http://forum.xda-developers.com/showthread.php?t=2171332 and its that easy why make it harder than it is or read the full op

acultr said:
try this http://forum.xda-developers.com/showthread.php?t=2015469 or other toolkit
Click to expand...
Click to collapse
tried that . it is saying fastboot device not found. what to do now?

747nemesis said:
tried that . it is saying fastboot device not found. what to do now?
Click to expand...
Click to collapse
properly installed the driver?

Problem Flashing
Hi, i have a problem flashing rastakat. To Install in bootloader, appear: Error flashing zip. I download again the zip, but appear the errror again, What i can doing bad? tks

acultr said:
properly installed the driver?
Click to expand...
Click to collapse
FInally got it to work . Had issues with drivers i guess , so i connected my nexus 4 to a macbookpro(hate apple though ) and it was done in less than a minute