Related
I upgraded to 4.2.2 and it seems I have lost my Root Access. I has SuperSU Pro with OTA Survival mode on installed as a system app before the upgrade but it seems it did not keep Root access. I used Root Checker and it's telling me I am not rooted. I am still seeing the unlock Icon at boot so I assume my boot loader is still unlocked.
Is there an easy way to get my Root access back?
Thanks.
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Thanks for your reply. I will try to follow the steps you outlined however, most of what you said is new to me. I initially rooted my device with the Nexus 7 Toolkit so it was a fairly simple procedure. I have never used the SDK or twrp are there any tutorials on how these work on 4.2.2? Also they will probably update Nexus 7 toolkit to support 4.2.2 eventually, so if I can't figure out the steps indicated I may have to wait.
Another noob question: After the update I can still open busybox and SupeSU, how come these apps still run if I am no longer rooted?
gastonwalpole said:
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
hey man yeh i didnt get how i still had supersu but i definitely wasnt rooted. its all a bit complicated aye, basically you need to download the andriod sdk bundle [now called adt bundle] for whatever you have eg. windows 7 32/64, and the jdk java development kit, look for guides on these, there two youtubers who have helpful channels: driodmodderx and wwjoshdew. also search threads here. you want your device to be recognized by the comp, sdk and jdk do this. twrp is a custom recovery that you can use to flash roms zips etc, you use your comp to send this custom recovery to your device. i would have stayed on 4.2.1 because i dont think you can use custom roms on 4.2.2 bootloader, still 4.2.2 is very smooth, i like it.
Sent from my Nexus 7 using XDA Premium HD app
gastonwalpole said:
Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb.
Click to expand...
Click to collapse
Boy did your post make me happy! I had the exact same problem. Managed to install 4.2.2 with modified OTA update (original was failing due to some discrepency in GoogleCalendar.apk) but even though I had SuperSU in survival mode, I lost my root. I've been trying all afternoon to connect via adb to my Nexus and just couldn't - it was always offline.. I tried 3 different computers and my SGNII phone (which worked) but N7 just wouldn't stop being offline...
I hope this is the solution! Thanx a BUNCH!
One question - my bootloader is unlocked telling by the icon on boot "google" screen - will I lose my apps and data after "re-rooting" that is, after flashing custom recovery and SuperSU?
THANX!!!!!!!!!!!!!
you won't lose anything by flashing recovery or su
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
burnitdown said:
you won't lose anything by flashing recovery or su
Click to expand...
Click to collapse
Great, managed to do it, everything fine. Thanx again!
SimonP2 said:
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
Click to expand...
Click to collapse
And if you can't wait, the workaround is there on http://www.wugfresh.com/nrt/ under IMPORTANT NOTICE.
i downloaded a custom rom and gapps to flash to my nexus, went to recovery to flash, wiped everything including system, when i go to flash the custom rom, BAM !!!!! it didnt download only the gapps did. now i have NO OS , no nandroid backup and no Custom Rom to flash
Pretty stupid of me not to have a nandroid backup but with the storage limitations of 8GB, i didnt do one to save space for other stuff, So basically i have an unlocked bootloader and custom recovery installed, can someone point me in the right direction on how to install an OS to my phone again
You could download ROM to your computer and use adb push to copy it to the phone where you can flash it,
Sent from my GT-P3110 using Tapatalk 2
CptanPanic said:
You could download ROM to your computer and use adb push to copy it to the phone where you can flash it,
Sent from my GT-P3110 using Tapatalk 2
Click to expand...
Click to collapse
I see an option on TeamWin recovery called ADB Sdeload, but i have no idea how to use it.
edit.. see below for command
just download a complete rom and name it rom.zip and put it where you have your adb.exe and fastboot.exe files, make sure to run the command from where you have the files, then just go into recovery and flash it
AW: [q] wiped android system, no nan backup
Go in with "ADB push c:\rom.zip /SDCARD/" this will copy your ROM from your PC to your Nexus. Then you can flash it via your recovery.
In general you can look if a ADB connection is working properly with typing "adb devices". After this you can push your file to your phone.
Gesendet von meinem Nexus 4 mit Tapatalk 2
Could you possibly push it with the nexus4 tool kit it has a flash stock option? Just my two cents just got the phone so I could be wrong
Sent from my Nexus 4 using xda premium
http://forum.xda-developers.com/showthread.php?t=1995688
Install the Nexus 4 Toolkit from the link above... It will install on your C: drive... C:/Google Nexus 4 Toolkit...
Follow the instructions and download the adb files for 4.2.2 found on this page...
Extract them to the folder above, writing over the ones that already exist.
Next, go to https://developers.google.com/android/nexus/images#occam and download the factory rom for 4.2.2
Paste the rom in C:/Google Nexus 4 Toolkit/put_google_factory_image_here
Next, open the .exe called Toolkit in this folder.
Check for update? Say no.
What build do you have? 1
You are now at the main menu...
Select the number 9
Now put your phone in Fastboot mode..
Once its in fastboot mode, type yes and press enter... it will now flash to stock.
This version of the toolkit will not root, b/c adb is different or something... But it will still flash touch recovery, using option 6.
From there you can do what you want, flash a new rom or root stock.... Have a nice day! And click the Thanks button please,
I'm not on often enough to get Thanks....
P.S. I did the same thing yesterday... I'm so used to just wiping everything on my stupid skyrocket.... lol.
But I wanted to do a fresh install b/c I was having some issues with my titanium backup files from the lates rom i was
using on my skyrocket... so now i'm going old school, reinstalling everything one by one from the market... Then i'll do another
titanium backup and a full backup to have a restore point... Makes for a fun weekend...
jpierce1987 said:
http://forum.xda-developers.com/showthread.php?t=1995688
Install the Nexus 4 Toolkit from the link above... It will install on your C: drive... C:/Google Nexus 4 Toolkit...
Follow the instructions and download the adb files for 4.2.2 found on this page...
Extract them to the folder above, writing over the ones that already exist.
Next, go to https://developers.google.com/android/nexus/images#occam and download the factory rom for 4.2.2
Paste the rom in C:/Google Nexus 4 Toolkit/put_google_factory_image_here
Next, open the .exe called Toolkit in this folder.
Check for update? Say no.
What build do you have? 1
You are now at the main menu...
Select the number 9
Now put your phone in Fastboot mode..
Once its in fastboot mode, type yes and press enter... it will now flash to stock.
This version of the toolkit will not root, b/c adb is different or something... But it will still flash touch recovery, using option 6.
From there you can do what you want, flash a new rom or root stock.... Have a nice day! And click the Thanks button please,
I'm not on often enough to get Thanks....
P.S. I did the same thing yesterday... I'm so used to just wiping everything on my stupid skyrocket.... lol.
But I wanted to do a fresh install b/c I was having some issues with my titanium backup files from the lates rom i was
using on my skyrocket... so now i'm going old school, reinstalling everything one by one from the market... Then i'll do another
titanium backup and a full backup to have a restore point... Makes for a fun weekend...
Click to expand...
Click to collapse
Bro you're a lifesaver, i wish i could hit the thanks button 20 times lol. Thanks a lot
hello guys this guide helps you to root your nexus 4 (4.3) and install custom recovery
things needed
1)superuser http://d-h.st/Hhw
2)twrp http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
3)andriod sdk (google it)
* [dont have sdk? then download this http://d-h.st/jCU a replacement for sdk/platformtools (this tools include stuff for windows,linux and mac too.)]
4)adb drivers installed (follow the below mentioned guide)
note:- this is almost same process as this guide http://forum.xda-developers.com/showthread.php?t=2018179 but just updated for 4.3 version
ROOTING process
1)I hope your boot loader is unlocked, if not first unlock it and then start the rooting process and turn on usb debugging (follow above mentioned guide for unlocking bootloader and to turn on usb debugging) after unlocking bootloader reboot device and then copy root.zip(links above) into your phones storage and then reboot to fastboot
2)now download the twrp recovery image and rename it to twrp and move it to sdk/platform tools. in the same directory(i.e platformtools directory) open cmd prompt(to open cmd prompt press shift+rightclick at the same time and select open cmd prmpt window option) and type (without quotes) "fastboot flash recovery twrp.img" and thats it you have flashed twrp
3)now go to twrp (recovery mode) and flash the root.zip (that u copied to the phones storage earlier) and that's it u have obtained the root access.
im not responsible if u bricked your device do it at your own risk
follow this wonderful video if u have any problem or trouble http://www.youtube.com/watch?v=jn5ih0omlxI
hit thanks button if this thread helped ya
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
Thank you I will update that!
thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
BTW you can update that manually via WiFi from playstore as chainfire mentioned in the thread that "if u already have root root access then update it from playstore"
Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??
M.Zaki said:
when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??
Click to expand...
Click to collapse
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck
When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app
amnon.m said:
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck
Click to expand...
Click to collapse
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
I am very happy
M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
so it might not have recognized your adb drivers at the first time.or you could have just downloaded the nexus4toolkit by mrskip and installed adb from it. anyways did u root it?
Thibaultvw said:
When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
now try the link i fixed it
punitthereddevil said:
Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
Click to expand...
Click to collapse
as i mentioned in the thread "this is the similar guide as that is mentioned above just updated for 4.3 version"
Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta
Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...
bartiki said:
Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...
Click to expand...
Click to collapse
i have the same problem with "fastboot boot xxxx.img"!! both CWM and TWRP , return blank!
I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
the new version of bootloader shipped with Android 4.3 factory image changed some of the "fastboot boot" command so you need to specify a kernel commandline to use "fastboot boot" command.
Click to expand...
Click to collapse
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now
bartiki said:
I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now
Click to expand...
Click to collapse
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??
bbsnick said:
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??
Click to expand...
Click to collapse
Somebody mentioned this on first page newest su not compatible only v1.43
Sent from my Nexus 4 using Tapatalk 4 Beta
boysetsfire said:
Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yep it still works after reboot . no problem with that
Newbie here.
Pls guide me..
Many tks!
Sent from my SM-N9005 using xda app-developers app
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Issues with rooting (4.4), stuck after flashing recovery
I just got my Nexus 10, and unlocked the boot loader, then flashed the custom recovery. All was fine, and I could boot into recovery, however recovery can not mount any filesystems. So I rebooted, now the Nexus does not boot, but hangs on the intro animation, normally meaning in my experience that the kernel is looped and is no longer finding (or else) booting the OS. I've tried booting 3 times.
So then, the steps I took,
enable USB debugging
were copy over the zip file for supersu
reboot to (fastboot mode), verify device
unlock boot loader "fastboot oem unlock"
flash the recovery "recovery-clockwork-touch-6.0.4.3-manta"
reboot into recovery
Failed to mount filesystems
for instance "E: Can't mount /cache/recovery/command or E:Can't mount /sdcard .... (you get the idea).
rebooting again a leaving it does nothing.
I also tried side loading a new image in my case "ThunderKat_manta-KRT16S-20131201" and after installing the "UniversalAdbDriverSetup", I was able to do so, I also was also able to side load the google apps "GoogleAppsPack-4.4-20131128", in both cases I get a success message after the install, however there after when I attempt to reboot I'm still stuck looking at the boot animation.
Now I'm really confused as if if the OS was destroyed when I unlocked the device, then side load of the zip contains a new kernel and OS image so it should be working, but it is not. In fact, recovery while still working throws the same can not mount exceptions after the flash as it did before (I rebooted) as I was previously getting and a factory reset, fails to mount /data, but does flash /cache and sd-ext without issues, so again I'm lost as to what to do.
Best guess I have is that partitions such as /data are just missing, I have no idea the state of teh device in such a case, but recovery and side loading using adb are working, how do I recover a working ANDROID OS from here?
Thanks,
ERIC
stuck in loading screen
Hi,
i just got my Nexus 10 yesterday. I tried to root it, but it is stuck in the loading screen. What can i do now? Can i like undo it to get it back to work?
I have the same issue egandt described.
Edit: I just got it back with this tutorial to android 4.2.2 and now i am updating it back up
nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
I unlocked nexus10,
Flashed cwm,
Installed su, but whn i turned it on, su not found, rootchecker shows no root access..
I also encounter bootloop initially,
Need to wide data / factory reset then its normally booted..
Sent from my SM-N9005 using xda app-developers app
Agreed the factory reset was required to fix the issues I encountered, then installing super-su worked.
I still cannot root the Nexus10..
Any one can help?
Thanks in advance!
XxLordxX said:
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Click to expand...
Click to collapse
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
xing369 said:
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
Click to expand...
Click to collapse
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
shimp208 said:
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
Click to expand...
Click to collapse
Thanks for your kind offering of hands!
Last night I tried again to re-flashed latest TWRP as well as latest SuperSU.
I ran 2x Root Checker,
1 said rooted,
1 said no root access, no BusyBox available.
I tried some apps like GMD Gesture, no working or no root access.
So,
Should I redo everything: enable USB Debugging then unlock bootloader then flash CWM then install SuperSU?
I initially gone thru above steps w/o enabling USB Debug..
Many thanks!
Sent from my SM-N9005 using xda app-developers app
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
xing369 said:
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
fritzhy said:
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
Click to expand...
Click to collapse
Very much appreciated for reviving my nexus!
However, after flashing latest TWRP, and installed SuperSU 1.80,
It seems my nexus still unrooted.
Any ideas?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
fritzhy said:
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If it's needed the app will say so when you open it.
fritzhy said:
If it's needed the app will say so when you open it.
Click to expand...
Click to collapse
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Not that I can think of, nope...
Hi all,
current state:
Nexus 4
Lock state: UNLOCKED
Root: Secure Root
OS: no
TWRP versions: 3.O.O / 3.1.1
adb devices log shows:
List of devices attached
************* recovery
I have twrp installed on my nexus 4 of which I accidentally did a factory reset. Now I don't have a operating system to boot into. I could connect it to my ubuntu PC and copy the lineage os 15 zip for mako aka nexus 4. When I used adb tools to reboot into recovery mode and go into Install section of TWRP, "Swipe to unlock/Swipe to allow modifications/Swipe to flash" options get stuck
Problems:
1. Due to swipe stuck problem mentioned earlier, I thought of using adb sideload, which fails with Error: Closed when sideload is to be done for the zip.
2. Thinking TWRP version might be an issue, installed another recent version of twrp, but the same problem persists. (stuck at swiping)
Pls let me know if any other non-touch solution to twrp is available or how to solve the current problem. Any help is much appreciated.
So you explained your situation but never asked a question as what you want.
Want stock or custom ROM or just help with custom recovery or go back to stock?
If you simply want to try everything all over again then go back to stock and redo everything i.e. flash stock > unlock bootloader > flash custom recovery > flash ROM of your choice
The factory image here - https://developers.google.com/android/images#occam
If you want some tools to help you out try some toolkits https://forum.xda-developers.com/nexus-4/orig-development/toolkit-rollup-nexus-4-t2566452
I have unlocked the bootloader but flashing ROM of my choice is causing trouble, as in the twrp install screen, Swipe to install/Swipe to unlock/Swipe to allow modifications, screen is stuck. As much as I swipe to do these operations, swipe doesn't work and control is stuck. This is the main problem to be specific and would expect the swipe to work clean.
/root said:
So you explained your situation but never asked a question as what you want.
Want stock or custom ROM or just help with custom recovery or go back to stock?
If you simply want to try everything all over again then go back to stock and redo everything i.e. flash stock > unlock bootloader > flash custom recovery > flash ROM of your choice
The factory image here - https://developers.google.com/android/images#occam
If you want some tools to help you out try some toolkits https://forum.xda-developers.com/nexus-4/orig-development/toolkit-rollup-nexus-4-t2566452
Click to expand...
Click to collapse
pap18 said:
I have unlocked the bootloader but flashing ROM of my choice is causing trouble, as in the twrp install screen, Swipe to install/Swipe to unlock/Swipe to allow modifications, screen is stuck. As much as I swipe to do these operations, swipe doesn't work and control is stuck. This is the main problem to be specific and would expect the swipe to work clean.
Click to expand...
Click to collapse
Best way to fix this is to flash the factory image.
Later you can root and install custom roms.
Follow the below given procedure
--------------------------------------------------------------------------------------------------------------------------------------------------------
Downloads
Nexus Root Toolkit v2.1.9
androidfilehost.com/?fid=24728673521238129
UniversalAdbDriverSetup
androidhost.org/r1xtW
Android Factory Image -5.1.1 (LMY48T)
dl.google.com/dl/android/aosp/occam-lmy48t-factory-c43c7cfd.zip
------------------------------------------------------------------------------------------------------------------------------------------------------
Procedure
Install Nexus root kit , click "Full Driver Installation Guide - Automatic +Manual".
Follow "Step 1 " and uninstall the existing ADB drivers.
Run" UniversalAdbDriverSetup.msi", which we downloaded .
Click "Flash stock + Unroot" button in Nexus rootkit and follow the instructions .
Select the image we downloaded(occam-lmy48t-factory-c43c7cfd.zip) for flashing and continue .
You will have the nexus 4 restored .
Hi on_se,
I downloaded and installed all the executables you mentioned. Now when I open NRT, it asks me model type. The device I have is nexus 4, and I don't have any android build running in it. Even if I choose any build from the list or Do "Auto detect device + build", it doesn't work; since my nexus 4 isn't booting and isn't present in the list of devices connected to my windows machine. How can I get it to wake since combination of volume up + volume down + power buttons; don't seem to get it into boot mode?
Can you guide me on the step 4 and 5 from your answer?
Thanks
on_se said:
Best way to fix this is to flash the factory image.
Later you can root and install custom roms.
Follow the below given procedure
--------------------------------------------------------------------------------------------------------------------------------------------------------
Downloads
Nexus Root Toolkit v2.1.9
androidfilehost.com/?fid=24728673521238129
UniversalAdbDriverSetup
androidhost.org/r1xtW
Android Factory Image -5.1.1 (LMY48T)
dl.google.com/dl/android/aosp/occam-lmy48t-factory-c43c7cfd.zip
------------------------------------------------------------------------------------------------------------------------------------------------------
Procedure
Install Nexus root kit , click "Full Driver Installation Guide - Automatic +Manual".
Follow "Step 1 " and uninstall the existing ADB drivers.
Run" UniversalAdbDriverSetup.msi", which we downloaded .
Click "Flash stock + Unroot" button in Nexus rootkit and follow the instructions .
Select the image we downloaded(occam-lmy48t-factory-c43c7cfd.zip) for flashing and continue .
You will have the nexus 4 restored .
Click to expand...
Click to collapse
pap18 said:
Hi on_se,
I downloaded and installed all the executables you mentioned. Now when I open NRT, it asks me model type. The device I have is nexus 4, and I don't have any android build running in it. Even if I choose any build from the list or Do "Auto detect device + build", it doesn't work; since my nexus 4 isn't booting and isn't present in the list of devices connected to my windows machine. How can I get it to wake since combination of volume up + volume down + power buttons; don't seem to get it into boot mode?
Can you guide me on the step 4 and 5 from your answer?
Thanks
Click to expand...
Click to collapse
Did you get any solution on this? I m at the same stage.
My PC is not detecting N4, I have no OS installed.
TWRP fastboot/adb dosent work either.
sandy7874 said:
Did you get any solution on this? I m at the same stage.
My PC is not detecting N4, I have no OS installed.
TWRP fastboot/adb dosent work either.
Click to expand...
Click to collapse
Does your phone show in Device Manager (even as unknown device)?
moriel5 said:
Does your phone show in Device Manager (even as unknown device)?
Click to expand...
Click to collapse
no, it dosent. I tried different machines too.
sandy7874 said:
no, it dosent. I tried different machines too.
Click to expand...
Click to collapse
Did you try using a different cable?
moriel5 said:
Did you try using a different cable?
Click to expand...
Click to collapse
No it doesn't
sandy7874 said:
No it doesn't
Click to expand...
Click to collapse
I'm sorry, however I did not understand you.
Did you mean that you didn't, or that you did however it did not change your situation?
moriel5 said:
I'm sorry, however I did not understand you.
Did you mean that you didn't, or that you did however it did not change your situation?
Click to expand...
Click to collapse
I tried different cables but it didn't help me.
sandy7874 said:
I tried different cables but it didn't help me.
Click to expand...
Click to collapse
Hmm...
And the drivers were installed?