Nexus 7 (2013) Wi-Fi Auto Updater with Root Restore
Nexus 7 Flo Auto Updater with Root Restore by Unfathomable
Build: Nexus 7 (2013) Flo Wi-Fi
Android 4.4.4
Recovery img: TWRP
Compatible only for Windows PC
Compiled from Modified Factory Images on Google Developers.
This kit is designed to update Stock rooted Nexus 7 devices to Android 4.4.4 while retaining all user data as well as root permissions. This will also work on non-rooted devices with an unlocked Bootloader.
Before you Start:
# This toolkit is designed to update without wipe but anything is possible, so I strongly urge you
to back up all data. Also I am not liable for any lost information.
# Please configure all ADB drivers
# Place phone in Fastboot mode. Power down the device; (Press and hold Power + Volume Down)
until the device boots into Fastboot.
# Extract all files, open the EXE file in the provided folder and follow the prompts Carefully.
VERY IMPORTANT!
After your device reboots, boot your Nexus into recovery. TWRP recovery should boot. Select the reboot option and reboot system.
You will be prompted "Swipe to flash SuperSU". This will restore all Root permissions.
*Also in the event that your device is stuck in a bootloop, just wipe the cache and you should be good to go!
I am open to feedback and if this helps please give me a thumbs up!
I am not liable for any harm that may come to your device but I am open to help.
Thank you all.
This is a tutorial video on using the updater
http://youtu.be/Hjk76S1XBa4
The Kit can be downloaded at this Dev Host URL
[http://d-h.st/alh
[Nexus 7 Auto Updater 4.4.4 By Unfathomable.zip - 445.99 MB]
Please post all "Help" related questions here in the forum.
For personal messages not pertaining to this post please contact [email protected]
Can this be used on n7 2013 WiFi that was rooted via towelroot? Ie boot loader still locked I guess.
Sent from my Nexus 7 using XDA Free mobile app
Which .exe? I see fastboot.exe and adb.exe in the .zip file. But there's no other executable. it just appears like this is the full 4.4.4 image files, but no "kit" that I can determine. I don't see how this would specifically save userdata.
iluvatrix said:
Can this be used on n7 2013 WiFi that was rooted via towelroot? Ie boot loader still locked I guess.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
As long as the boot loader is unlocked you will be ok
danman7 said:
Which .exe? I see fastboot.exe and adb.exe in the .zip file. But there's no other executable. it just appears like this is the full 4.4.4 image files, but no "kit" that I can determine. I don't see how this would specifically save userdata.
Click to expand...
Click to collapse
extract the "Nexus 7 Auto Updater 4.4.4 by Unfathomable.zip"
then in the extracted folder extract the "image.zip"also
the press "Nexus 7 Updater 4.4.4 by Unfathomable.exe"
and follow the instructions
thats it
press thanx if I helped:good::good::good::good::good:
cheers
danmaman said:
extract the "Nexus 7 Auto Updater 4.4.4 by Unfathomable.zip"
then in the extracted folder extract the "image.zip"also
the press "Nexus 7 Updater 4.4.4 by Unfathomable.exe"
and follow the instructions
thats it
press thanx if I helped:good::good::good::good::good:
cheers
Click to expand...
Click to collapse
Ah, I see what's going on. My AV is identifying it as infected. I'll pass, thanks.
Your computer is recognizing the EXE as infected?
danmaman said:
extract the "Nexus 7 Auto Updater 4.4.4 by Unfathomable.zip"
then in the extracted folder extract the "image.zip"also
the press "Nexus 7 Updater 4.4.4 by Unfathomable.exe"
and follow the instructions
thats it
press thanx if I helped:good::good::good::good::good:
cheers
Click to expand...
Click to collapse
Did everything work for you? Please leave feedback thank you.
Tried it but got 0MB storage and bootloop, so ended up doing it manually. thanks anyway
Unfathomable said:
Your computer is recognizing the EXE as infected?
Click to expand...
Click to collapse
Yes, Quarantined it as quickly as it was unzipped. Symantec was recognizing it referred to as "Suspicious.Cloud.5"
SomosLuz said:
Tried it but got 0MB storage and bootloop, so ended up doing it manually. thanks anyway
Click to expand...
Click to collapse
Did you try clearing cache? If there are any bugs please inform me so I am able to revise. I tried on four devices with success before uploading.
I tried clearing cache, but it failed, so I had to format storage
danman7 said:
Yes, Quarantined it as quickly as it was unzipped. Symantec was recognizing it referred to as "Suspicious.Cloud.5"
Click to expand...
Click to collapse
That's strange I apologize for that, I will definitely look into the issue for you. But I can assure you there's no malicious files compiled in the Zip. Check your security settings and make sure your PC allows for Batch files to run. The EXE was compiled from a bat file.
SomosLuz said:
I tried clearing cache, but it failed, so I had to format storage
Click to expand...
Click to collapse
I apologize about the situation. Did it fail immediately or was it successful in flashing certain files?
for me it works great
danmaman said:
for me it works great
Click to expand...
Click to collapse
Thank you for the feedback!
Hey
No problems at all
see the screen
Thanx for the image
cheers
Suspicious.Cloud.5
danman7 said:
Yes, Quarantined it as quickly as it was unzipped. Symantec was recognizing it referred to as "Suspicious.Cloud.5"
Click to expand...
Click to collapse
Hi Dan,
Suspicious.Cloud.5 is a detection technology designed to detect entirely new malware threats without traditional signatures. This technology is aimed at detecting malicious software that has been intentionally mutated or morphed by attackers.
Here is the technical write up on Suspicious.Cloud.5
Best Regards,
Chetan
Worked fine for me, went from 4.4.2 to 4.4.4 on my stock unlocked / rooted N7.
http://i.imgur.com/wh6eLZF.png
http://i.imgur.com/72qU8hw.png
edit: okay I think I chose the wrong button under reboot in TWRP and that didn't give me the supersu install option (whoops)
but all was good after booting back in to twrp and selecting the right button
You may want to make a note in the OP that seeing "no update found" is normal, kept thinking it was an error.
Related
Hello mates,
this morning my nexus 7-wifi (unlocked bot not rooted. w/ CWM) said me there is a system update for new android os. Kitkat.
Then i install the update without getting any CWM backup.
Zip file started to be installed in CWM and it processed all install. steps successfully.
However when the progress bar reach to %100, it said something like "...status 7.... installation aborted" (do not remember clearly).
And after reboot i come across a new boot animation (kitkat's new animation i think) which does not end up to a system start or an error message.
Now,
what should i do to complete installation of kitkat?
Thanks in advance.
cozgun said:
Hello mates,
this morning my nexus 7-wifi (unlocked bot not rooted. w/ CWM) said me there is a system update for new android os. Kitkat.
Then i install the update without getting any CWM backup.
Zip file started to be installed in CWM and it processed all install. steps successfully.
However when the progress bar reach to %100, it said something like "...status 7.... installation aborted" (do not remember clearly).
And after reboot i come across a new boot animation (kitkat's new animation i think) which does not end up to a system start or an error message.
Now,
what should i do to complete installation of kitkat?
Thanks in advance.
Click to expand...
Click to collapse
OTA Update cannot be flashed using CWM,you will need to use stock recovery.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Ben Ling said:
OTA Update cannot be flashed using CWM,you will need to use stock recovery.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi Ben,
what should i do now ? i downloaded a file of 360 MB into my PC, should i flash this file?
or
can i flash the file (~180 MB) which my nexus downloaded over wi-fi? if i am capable of using this file, in which directory should i look for this file ?
Thanks in advance.
cozgun said:
Hi Ben,
what should i do now ? i downloaded a file of 360 MB into my PC, should i flash this file?
or
can i flash the file (~180 MB) which my nexus downloaded over wi-fi? if i am capable of using this file, in which directory should i look for this file ?
Thanks in advance.
Click to expand...
Click to collapse
What file have you downloaded ?
Ben Ling said:
What file have you downloaded ?
Click to expand...
Click to collapse
tgz file of android 4.4 for nexus 7 2012 wifi. nakasig-krt16s
cozgun said:
tgz file of android 4.4 for nexus 7 2012 wifi. nakasig-krt16s
Click to expand...
Click to collapse
you downloaded the factory image ?
yes Ben, the factory image.
Ben,
by the way i cannot open stock recovery. when i push power + v.down, n7 opening in CWM. it will be great if you can help on this as well.
Ben,
by the way i cannot open stock recovery. when i push power + v.down, n7 opening in CWM. it will be great if you can help on this as well.
I did the same
cozgun said:
Ben,
by the way i cannot open stock recovery. when i push power + v.down, n7 opening in CWM. it will be great if you can help on this as well.
Click to expand...
Click to collapse
I did the same exact thing that you did and experienced the same error. Luckily, I came across a stickied thread, ""Flashing a factory image with fastboot / return to stock" and followed the instructions EXACTLY and.. it worked! It took me back to 4.3 which was great because at lease tablet was working again! (I had tried everything else I could think of!) What was funny was that within 2 minutes of the tablet up and running again I received the OTA push for 4.4!
I would strongly suggest following the instructions posted in the thread I mentioned above as they worked perfectly.
Boeing787Guy said:
I did the same exact thing that you did and experienced the same error. Luckily, I came across a stickied thread, ""Flashing a factory image with fastboot / return to stock" and followed the instructions EXACTLY and.. it worked! It took me back to 4.3 which was great because at lease tablet was working again! (I had tried everything else I could think of!) What was funny was that within 2 minutes of the tablet up and running again I received the OTA push for 4.4!
I would strongly suggest following the instructions posted in the thread I mentioned above as they worked perfectly.
Click to expand...
Click to collapse
Hello buddy,
thank you for the feedback. But i do not want to lose my data in the tablet. So, first i will try to fix this without wiping data.
Currently i install adb files to my pc.
And i managed to find the zip file i need to upgrade from 4.3 to 4.4 without losing any data.
If i can flash this zip file via adb i will be ok. but i cannot flash it via adb, because of the recovery i am using (i think ). With CWM i could not do that. after adb sideload **********.zip command, it says "error: device not found"
now i am looking for a solution to this error.
But if i could have had my tablet open in stock recovery, it might already be solved.
PROBLEM SOLVED.
HERE IS THE STEPS TAKEN:
DOWNLOAD OTA FILE FROM 4.3 TO 4.4 (NOT FACTORY IMAGE).
DOWNLOAD LATEST SDK, RUN SETUP.
PUT THE OTA FILE IN sdk\platform-tools DIRECTORY.
SIDELOADING THE OTAFILE:
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
IF YOUR DEVICE IS NOT RECOGNIZED DURING SIDELOADING CHECK THIS:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
AFTER SIDELOADING, IF YOU GET STATUS 7 ERROR, TRY THIS:
http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26&nocache=1&z=7376160805579275
NO DATA LOST IN THIS METHOD.
cozgun said:
PROBLEM SOLVED.
HERE IS THE STEPS TAKEN:
DOWNLOAD OTA FILE FROM 4.3 TO 4.4 (NOT FACTORY IMAGE).
DOWNLOAD LATEST SDK, RUN SETUP.
PUT THE OTA FILE IN sdk\platform-tools DIRECTORY.
SIDELOADING THE OTAFILE:
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
IF YOUR DEVICE IS NOT RECOGNIZED DURING SIDELOADING CHECK THIS:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
AFTER SIDELOADING, IF YOU GET STATUS 7 ERROR, TRY THIS:
http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26&nocache=1&z=7376160805579275
NO DATA LOST IN THIS METHOD.
Click to expand...
Click to collapse
i try to do that
but when i trying to adb sideload ...zip says error:closed
its maybe im on twrp?
what can i do
plz help me im stuck in bootloop too
plz
pediashkavar buddy,
I am sorry, i have never used twrp.
cozgun said:
PROBLEM SOLVED.
HERE IS THE STEPS TAKEN:
DOWNLOAD OTA FILE FROM 4.3 TO 4.4 (NOT FACTORY IMAGE).
DOWNLOAD LATEST SDK, RUN SETUP.
PUT THE OTA FILE IN sdk\platform-tools DIRECTORY.
SIDELOADING THE OTAFILE:
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
IF YOUR DEVICE IS NOT RECOGNIZED DURING SIDELOADING CHECK THIS:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
AFTER SIDELOADING, IF YOU GET STATUS 7 ERROR, TRY THIS:
http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26&nocache=1&z=7376160805579275
NO DATA LOST IN THIS METHOD.
Click to expand...
Click to collapse
Does this work on a rooted nexus?
Only reason I'm asking is cause the sideloading link states "..to update nexus without root..."
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...
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
WiFivomFranMan said:
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I'm on the same boat, but I think our answer will come soon. Today I found out that WugFresh will be updating the NRT Toolkit to support the Nexus Player. See this post.
Why not just download the image and flash it? Plenty of guides on how to do this
lafester said:
Why not just download the image and flash it? Plenty of guides on how to do this
Click to expand...
Click to collapse
I didn't know that there were difficulties with 5.1.1. I used Wugfresh's tool to install 5.1.1 with the "no wipe" option and I had 5.1.1 just fine - but can't figure out how to get root back!! And I need root to expand the storage!! Right now I have a fresh, clean, 5.1.1 install on my NP.
I tried Wugfresh's tool, I sure wish it told me that it didn't work with the firmware that it had already detected!!
I also tried the Chainfire root.img that I used back on 5.0 and it seems to work until I tell SuperSU to update the binaries. At that point it basically times out and asks me to reboot.
What next?! Wait for Wugfresh? Is there another way to root?
I flashed the cm recovery from dhacker and used it to flash the newest beta of supersu. After that the app didn't show up until I installed it from the store but now it works fine
I just want to upgrade it without losing all my stuff (Saved games for my NES ROM, etc...)
Why don't you locate the save data in es file explorer and copy it to the cloud. Reimage nexus player and set up es file explorer, cloud and copy the saved data back to where you stored it.
would anyone be so kind to point me to one of the guides on how to use factory image/OTA to update from 5.0 rooted to 5.1.1? I don't care about keeping my settings, and I don't care about root. just want the latest and greatest.
thanks in advance
The Nexus Player is a Nexus device, and you can always upgrade to the latest version by using the factory images found here: https://developers.google.com/android/nexus/images. The procedure to flash a factory image on any Nexus device has not changed since the Nexus One was released, so you can look at any of the guides for Nexus devices.
Essentially it boils down to this: The factory image contains a few files in an archive format. There are a few images within that you need: bootloader (I can't remember what the name of the file is but it's something like xxxxbootloaderxxx.img), system.img, boot.img, recovery.img). Extract those images from within the archive and flash them. You do this by booting into the bootloader, opening a command prompt in the same folder that you downloaded the image files) on your PC and type the following commands:
fastboot flash bootloader bootloader.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
If you also want to start fresh and wipe all your data, execute the following command: fastboot format userdata
Then execute: fastboot reboot
Done.
Notes:
1) You need to extract these files in the same directory as where you downloaded the images before proceeding.
2) if you are using Windows, you need to install the the driver (found here: http://developer.android.com/sdk/win-usb.html)
3) The procedure above assumes your bootloader is unlocked. If not, you will need to unlock it (using: fastboot oem unlock) and it will wipe all your data.
efrant said:
1) There is currently no way to get root on 5.1.1 without modifying the kernel (so that it boots SELinux in permissive mode).
Click to expand...
Click to collapse
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
etnpnys said:
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
Click to expand...
Click to collapse
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
efrant said:
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
Click to expand...
Click to collapse
Ok - whew! I know that I went through the process but I couldn't be 100% sure because I have tried so many things to get expanded storage working to no avail that I've kinda given up for the time being...
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Toneman07 said:
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Click to expand...
Click to collapse
Not necessarily... You still need a modified boot.img to get the whole thing working...
etnpnys said:
Not necessarily... You still need a modified boot.img to get the whole thing working...
Click to expand...
Click to collapse
Thats interesting considering both my nexus phone and samsung tablet are running stock kernels (boot.img) and rooted just fine using the above method.
Credit goes to kaku85 for finding the link.
http://www.hihonor.com/uk/support/search-result/?keywords=Honor 4X Quick Start Guide
Installing the Huawei firmware is an easy job as you don’t need a special software or an tedious installation of ADB and/or fastboot like stuff. It just involves extracting the Software folder from the firmware and then transferring the dload folder (contains UPDATE.APP file) inside the Software folder to your device, and then using the Update menu in Settings app to install the firmware (it’s UPDATE.APP file).
Click to expand...
Click to collapse
Wow.. nice. Downloading now
MvP77 said:
Credit goes to kaku85 for finding the link.
http://www.hihonor.com/uk/support/search-result/?keywords=Honor 4X Quick Start Guide
Click to expand...
Click to collapse
Backup!
Backup necessary stuff. In case your device is wiped off while following the guide below, it’s good to have a backup of contacts, photos, videos and other files already saved on PC.
How to Install Huawei firmware
Step 1. Download the official firmware for your Huawei Honor Android device first, and make sure it’s meant for your device by verifying the model no. of your device.
Step 2. Extract the firmware file to a separate folder. Upon doing so, you should get a ‘Software folder, in which you would have a dload folder with Update.APP file inside it.
Step 3. Connect your Huawei device to PC, and transfer the dload folder to your internal storage of your Huawei device. The dload folder must have Update.APP file inside it. Then disconnect the device from PC.
(Use external storage if internal storage doesn’t wok for you.)
Step 4. Now, open the Update menu under Settings app.
Step 5. Tap on Menu key at bottom and select Local Update option.
Step 6. Your Huawei device will look for UPDATE.APP file inside the dload folder and upon finding one, will present you a pop-up menu.
Step 7. Choose Install. The firmware will begin installing.
Step 8. Wait till the process is finished, after which your device will take a nice reboot.
That’s it. You have successfully installed the firmware on your Huawei Huawei device.
Damn they killed fastboot boot recovery
Thanks for posting this..
I'll update the repository and the back to stock guide
clsA said:
Damn they killed fastboot boot recovery
Thanks for posting this..
I'll update the repository and the back to stock guide
Click to expand...
Click to collapse
Did they? I was able to reinstall TWRP using the exact same instructions.
janejunx said:
Did they? I was able to reinstall TWRP using the exact same instructions.
Click to expand...
Click to collapse
My fastboot was out of date
I was able to boot with new fastboot
Fastboot boot twrp_recovery.img
Sent from my SM-N920C using Tapatalk
No KIW-L24 update available for Marshmallow from the link
Can you verify this link as there in update for KIW-L24 on this page? Thank you
ftenorio said:
Can you verify this link as there in update for KIW-L24 on this page? Thank you
Click to expand...
Click to collapse
Go to the US Support page, you will find the update for the KIW-L24 US version and just follow the detailed instructions on the above post to install. I just upgraded mine.
I did all the instructions but when I restart after pressing install it takes me to TWRP? I dont know what to do there.
anyone have tried to install Xposed???
http://forum.xda-developers.com/show...3&postcount=35
tvchannel500 said:
I did all the instructions but when I restart after pressing install it takes me to TWRP? I dont know what to do there.
Click to expand...
Click to collapse
You need to flash stock recovery to install. Go here to find stock recovery and use fast boot to install that first.
tvchannel500 said:
I did all the instructions but when I restart after pressing install it takes me to TWRP? I dont know what to do there.
Click to expand...
Click to collapse
the update requires stock system and stock recovery ... as do all vendor updates
I am having trouble with installing update. Running rooted stock rom with stock recovery. Able to download update successfully, however, when EMUI shows installation at 25%, it gives installation failed message. Even tried wiping cache and factory reset prior to update with same result. Any thoughts/assistance greatly appreciated.
spunky168 said:
I am having trouble with installing update. Running rooted stock rom with stock recovery. Able to download update successfully, however, when EMUI shows installation at 25%, it gives installation failed message. Even tried wiping cache and factory reset prior to update with same result. Any thoughts/assistance greatly appreciated.
Click to expand...
Click to collapse
Flash TWRP back to your phone and use this nandroid backup - https://www.androidfilehost.com/?fid=24588232905720643
The update will work after that
Sent from my SM-N920C using Tapatalk
clsA said:
Flash TWRP back to your phone and use this nandroid backup - https://www.androidfilehost.com/?fid=24588232905720643
The update will work after that
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Unfortunately, unable to install your zip file through TWRP.
Error message (even after turning off zip signature verification): "Could not find 'META-INF/com/google/android/update-binary' in the zip file"
Also zip signature verification failed.
spunky168 said:
Unfortunately, unable to install your zip file through TWRP.
Error message (even after turning off zip signature verification): "Could not find 'META-INF/com/google/android/update-binary' in the zip file"
Also zip signature verification failed.
Click to expand...
Click to collapse
its a nandroid backup
unzip it to your desktop and copy it to your TWRP/BACKUPS/yourserialno/put folder here
clsA, help me please.
clsA said:
its a nandroid backup
unzip it to your desktop and copy it to your TWRP/BACKUPS/yourserialno/put folder here
Click to expand...
Click to collapse
When I try to restore, now it gives me "No partitions selected for restore." (in red in TWRP when using restore function).
I am so frustrated!!! I got out of bootloop from hell, then adb the TWRP which I can boot into successfully. I unzip your nandroid backup on desktop and moved to my TWRP/backups/myserialno/. Ran TWRP restore function, selected the nandroid folder and boom, this comes up.
Thanks in advance if you can give me any more advice before entertaining buying another KIWI.
spunky168 said:
When I try to restore, now it gives me "No partitions selected for restore." (in red in TWRP when using restore function).
I am so frustrated!!! I got out of bootloop from hell, then adb the TWRP which I can boot into successfully. I unzip your nandroid backup on desktop and moved to my TWRP/backups/myserialno/. Ran TWRP restore function, selected the nandroid folder and boom, this comes up.
Thanks in advance if you can give me any more advice before entertaining buying another KIWI.
Click to expand...
Click to collapse
well I'm not sure how to help you if you can't do a simple TWRP restore
Show me pictures of where the file is located on your phone
when you choose restore in twrp was my backup in your list ?
when you choose it did you actually check the boxes of the partitions you want to restore ? All of them ?
restoring a TWRP backup is one of the simplest procedures you can do to a smart phone.
clsA said:
well I'm not sure how to help you if you can't do a simple TWRP restore
Show me pictures of where the file is located on your phone
when you choose restore in twrp was my backup in your list ?
when you choose it did you actually check the boxes of the partitions you want to restore ? All of them ?
restoring a TWRP backup is one of the simplest procedures you can do to a smart phone.
Click to expand...
Click to collapse
Belay my last clsA.
I made a bunch of silly mistakes, ended up in bootloop hell, then somehow wipe the OS out altogether but after working backwards, I got every resolved and successfully updated to MM. Thanks for everything.
I am going to write a guide up of everything I did wrong and not to do and how to undo them later. In the mean time, let me enjoy my MM.
spunky168 said:
Belay my last clsA.
I made a bunch of silly mistakes, ended up in bootloop hell, then somehow wipe the OS out altogether but after working backwards, I got every resolved and successfully updated to MM. Thanks for everything.
I am going to write a guide up of everything I did wrong and not to do and how to undo them later. In the mean time, let me enjoy my MM.
Click to expand...
Click to collapse
I'm glad you got it fixed
Sent from my SM-N920T using Tapatalk
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?