Related
This method doesn't rely on any root exploits & will work with any Android version on the ZTE Blade (and all variants). It should work on any phone with an unlocked bootloader (all zte android devices are sold with unlocked bootloaders).
Software needed:
adb (windows/linux/mac versions available as part of the android sdk - http://developer.android.com/sdk/index.html You will find adb in the tools directory.)
fastboot (windows/linux/mac versions available here: http://koushikdutta.blurryfox.com/G1/ )
windows drivers for the phone (if you use windows: http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442 )
ClockworkMod (http://clockworkmod.com/rommanager - download zte blade clockwork recovery image)
SuperUser ( http://androidsu.com/superuser/ Download Eclair/Froyo/Gingerbread/Honeycomb (2.1 – 3.2) version) - Alternatively you can use any rooted custom rom
If your phone is running Android 2.1, then it is probably a 'gen1' device, search for "Mr Pigfish" on Android market if you're unsure. Gen1 blades will need an older version of clockworkmod, 3.0.1.4 - http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.1.4-blade.img
Method:
Download/install adb & fastboot. Install drivers for the phone if needed (on Windows).
Plug your phone into your pc using the usb cable, mount usb storage, then copy the Superuser or custom rom zip onto it & unmount usb storage.
Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging).
Open a command terminal window & change to the directory that you downloaded recovery-clockwork-[version]-blade.img to. Type...
Code:
adb reboot bootloader
This will make the phone reboot, wait for the android logo (or custom splash screen) on the phone then type...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
You have just installed ClockworkMod recovery. Your phone will reboot back into android, when it has done that turn it off, then turn it on with the vol- button held to start clockworkmod. Use vol+/- to navigate, home button to select an option, back button to go back. You should create a backup now before you flash anything, when that backup is complete use 'install zip from sdcard' to either install superuser to root your stock rom, or install a custom rom. If you're installing a custom rom then you'll need to wipe data/factory reset too (you will lose all data). reboot, you're done.
I'm not sure if this is the right section for the thread, it'd probably be better in blade general. I forgot that newbies can't reply here.
Anyway, for those that can reply, can you suggest any improvements? I'll find links for adb, fastboot & windows drivers later.
Everything is clear except where to find adb and fastboot for noob users... (like me).
I did a little search and found out that adb is installed with the Android SDK... so, i installed it, installed the android platform-tools package, the usb driver but i am stuck with fastboot...
There is no fastboot in the Android SDK installation directory... and i can't find it on the web... so, i can't install clockworkmod recovery and i'm stuck...
Can u help me plz ?
Yeah, as I said, I'm still looking for links. you get fastboot when you compile android from source, but that is a bit of a long & complicated way.
Here is a pre-compiled version of fastboot for windows, linux & macos http://koushikdutta.blurryfox.com/G1/
adb works without the sdk too, I'll see if I can find links for that.
The windows driver is on zte's site somewhere, but that's a pain to find anything on. I'm not sure if the Google driver works. I don't even run windows, so if anybody can help write that part...
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
unrandomsam said:
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Click to expand...
Click to collapse
Not everybody is running the official 2.3.5 rom, it's probably a tiny fraction of users. 2.1 roms don't have the driver iso. I found the drivers & updated the first post. The drivers on the phone should work fine, if you are running an unmodified 2.2 or 2.3 stock rom, just plug the phone in & it should mount a driver cd image over usb to install the drivers.
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
Click to expand...
Click to collapse
It's superuser, it's a clockworkmod zip file & no, it doesn't change default.prop. It installs superuser & su.
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
Click to expand...
Click to collapse
Tell ChainsDD, it isn't my software, I just wrote a quick idiot's guide.
Hi wbaw....
nice to see you posting helpful stuff here....
Can I ask what is perhaps a silly question, about the rooting process for ZTE devices, without relying on root exploits?
How is this different, or better, than using the z4Root modified by kallt_kaffe App, which I have linked (MoDaCo).
Is it just the use of the exploit, or is there another reason?
I have used it on my OSF/Blade, and never lost root or had any other problem, AFAIK.
Also, I see you are not showing your previous GEN1/Gen2 all-in-one TPT for GSF any more...is it available any more for ppl who may want to try it?
Thanks in advance
The exploit that z4root uses doesn't work on newer versions of Android (2.2.2 & above), ZTE are selling some phones with these newer versions of Android.
If z4root works for you, then that's fine, there's nothing wrong with it. It just doesn't work for everybody.
If you are using a version of Android that z4root (or other root exploits) do work on, then you should update Android asap. Otherwise a malicious app could use the same exploit to take over your phone. Root exploits themselves aren't bad (as long as you're doing it to your own device, or with permission of the owner) - the fact that root exploits work is bad & a sign that you need to update the software asap.
GSF has it's own thread. You can get the same effect by using the gen1 to gen2 tpt & then installing gsf. It is buggy & old, I think there is a nasty remote root exploit out there for 2.3.4 too. Just use CyanogenMod, it's much better, less buggy, more secure, they keep up with the latest Android fixes & it has more customisation options.
Thank you for the explanation...I will go ahead and do what you have advised.
I am just continuing to use good old Swedish Spring RLS5, which I think was kallt_kaffe (Cold Coffee) also......GEN 2 thanks to your Gen 1>Gen 2 TPT.
I think t is 2.2.
If I want to proceed to permanently root as you describe, should I use z4root to unroot first?
I will probably move to CyanogenMod, so I should use your exploit-free root instructions first.
BTW, I will be sad to move on from SS, as it does seem to be as near a perfect fit as I have found for the Blade.
I did put on GSF ,some time ago, and to be very honest, I just lasted a night with it, then restored the SS Nandroid.......it didn't feel at all as satisfactory a UI experience as SS.
Perhaps it was me, you know, you get used to an old pair of sneakers, etc.
As you said, it was and is always beta...it was an early version!!!
Thanks again, and keep up the good work in these calm(er) waters
Custom roms are already rooted. You don't need to root a custom rom, you just install it with clockworkmod.
If you already have a custom rom installed then you don't need any of this guide, you've already got clockworkmod. All this guide does is tell you how to install clockworkmod.
This is for people with phones on a stock rom who want to be able to install clockworkmod to root their stock rom or install a custom rom.
You shouldn't still be using Android 2.2 because the root exploit in z4root works on it, therefore other more malicious apps could use a similar exploit without asking you first.
Hi..... does this work on any Android phone?
I have in mind the new Samsung W i 8150.
Getting one for Xmas.... AFAIK
Sent from my ZTE-BLADE using Tapatalk
It should work on some other android phones, but they'll need adb & an unlocked bootloader, so it wont work with every phone. It should work on any ZTE android phone or tablet (except maybe the tureis?).
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
stanangel said:
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
Click to expand...
Click to collapse
You need to download clockwork recovery & be in the directory that you downloaded it to, to run that command.
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
stanangel said:
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
Click to expand...
Click to collapse
You can put clockworkmod on, but cm7 might not work without a bit of fixing, it is designed for 2.2 blades, zte's 2.3.5 has a different radio firmware.
Is this a 2.3.5 blade? where did you buy it?
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
stanangel said:
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
Click to expand...
Click to collapse
I see, you'll need to use another image.bin to go back to 'gen2' - the zte froyo radio firmware. Otherwise you wont get any phone signal, 3g or gps on CM7 because the 2.3.5 image.bin that you installed contained new radio firmware.
You don't need to root it first, you can install clockworkmod with a gen2 radio firmware using a custom image.bin like this one that http://www.mediafire.com/?jb4crw3em2m4r4x Amphoras made.
The 2.3.5 image.bin contained another new version of the radio firmware, which isn't compatible with CM7.
Uhuuu, it works.Thank you a lot! CM7.1 is awsome.This forum is awsome.
Hey I cant acess adb after doing adb reboot bootloader. When I come to the chinese letter I cant do nothing. So i cant fastboot flash recovery recovery-xxx.img.
What im i doing wrong?
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
some news...
some news... i have successfuly install TWRP and maked a backup of system/data/boot if anyone want to play with backup or try to flash it i can upload it (it's a 5gb folder, tell me wich file hosting you want)
i have try after backup to flash the CM rom and some Flyme but i have always the same error: "could not find 'meta-inf/com/google/android/update-binary' in the zip file"
Any suggestion?
ps: if anyone has a TWRP backup of his pro 5 i can try to restore on my...
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Toroman said:
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Click to expand...
Click to collapse
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
mobilezonerm said:
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
Click to expand...
Click to collapse
In this thread there is a link:
http :// forum.xda-developers. com/meizu-pro-5/development/rom-cyanogenmod12-1-temasek-unofficial-t3358744
http :// xep.8800.org/ pro5/
But also on the Canonical site:
https ://wiki.ubuntu. com/Touch/ Devices
(Sorry for the spaces the policy doesn't allow me to post urls yet.)
I somehow thought that we can use official Flyme download from the Meizu website and the official Ubuntu turbo image without the need of installing TWRP or anything - and flash both via USB.
Functionality with TWRP would be a plus.
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Pleytos said:
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Click to expand...
Click to collapse
Well the power + up gives (a kind of) recovery that shows a screen with the Ubuntu logo in the center - nothing else. I believe the android version has a different recovery?
Ah I never saw that screen. Yes Android/Flyme has a different screen: like this
You can try to to use the Ubuntu recovery to flash a Flyme Rom. I did it with TWRP, but never tried it with the Ubuntu recovery.
The Flyme Rom replaces the recovery and boots with both TWRP and the Flyme recovery, maybe even with a Ubuntu recovery (I can't image it to be that different.).
Edit:
You might want to back up your current recovery. I just flashed the recovery from Canonicals website, and its just the English/Chinese Flyme one.
just a moment... thank's Pleytos, but we need the TWRP backup folder... on yours link there are the CM rom and on the Canonica site there are only the update.zip....
Keep in mind, also the partitons are different on Pro 5 Ubuntu, for this the best is to have the entire backup of an android phone, both CM rom and Update.zip are not flashable by TWRP (i have try)
and Toroman the recovery that you see is the original recovery, if you flash the recovery on Canonical website you have the screen posted by Pleytos BUT with this recovery you obtain only the unlock of ADB in recovery and, as you can read from the screenshoot to make an update you have to put a "update.zip" on root directory of the phone that, unfortunally in ubuntu edition, is read-only file system... i have just unlock it from linux terminal with a "remount,rw" but if you try to copy update.zip (many versions) to root fonder there aren't space enough...
I've make lot of try in this day and i have find two possible solutions:
- flash a rom with MultiUpgrade 4.8.5 (official software used by Meizu, that not start because some token is missing)
as reported in a big russian forum
- make a total erase of internal memory and rewrite it with a image from android Pro 5 phone (TWRP Backup)
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
All done... guide in details:
- on windows install driver: Samsung_USB_Drivers_for_Mobile_Phones_1.5.9.0
- on linux: run from terminal "$ sudo add-apt-repository ppa:ubuntu-sdk-team/ppa" and "$ sudo apt-get install phablet-tools"
- download from here (http://people.canonical.com/~plars/touch/recovery-turbo.img) the recovery image with unlocked ADB
- turn off the phone and turn on with volume down pressed to enter in fastboot mode
- in windows go to the folder where you have fastboot / in linux open the terminal and give "sudo -s"
- make a flash of recovery (fastboot flash recovery recovery-turbo.img)
- now download the TWRP recovery (i've used the 3.0.0 on this forum) and from terminal flash it (fastboot flash recovery "nomerecovery")
- now you have to copy first a CM rom on the phone or sd, before flash the CM rom erase completely the system partition, flash it whit TWRP and only after you are able to flash Flyme rom
keep in mind to make a full backup by TWRP and save it on external archive before operate. (it's less complicate for future restore and help you if something goes wrong)
if someone need the backup of Ubuntu for his phone, ask me...
Ubuntu Dump
mobilezonerm said:
if someone need the backup of Ubuntu for his phone, ask me...
Click to expand...
Click to collapse
Hello, can you provide me full Ubuntu dump? Im very interesting to install native Ubuntu touch on Meizu Pro 5. Share the link, for example, on Mega or Google Drive
Need you help
mobilezonerm said:
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
Click to expand...
Click to collapse
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
mobilezonerm said:
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
Click to expand...
Click to collapse
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
tamyou2020 said:
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
Click to expand...
Click to collapse
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Hi , Am running Ubuntu over windows ( virtual box ) we can go with team viewer , or if you want i can install Ubuntu in separate machine , Please let me know how we can communicate
Pleytos said:
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Click to expand...
Click to collapse
Hi,
I've been away for some time, and I can see some nice progress in making Android work on the Ubuntu edition.
I might be repeating myself but it would be ideal if we (who own the Ubuntu edition) can go back and forth seamlessly. Unfortunately my flashing skills are buried in the ancient time of the HTC HD2 so I need some assistance (as probably more of us do). Here are some questions, I appreciate the effort and the help (assume I'm using Ubuntu on the desktop) (if something is easier in windows - please note). This would be a full circle:
1 Is it possible and how to make a COMPLETE backup of the Ubuntu edition phone (including the recovery and everything) to be able to get back to the factory condition (and using what tools/steps). I think I have read somewhere that OTA updates does not work with custom recovery or something similar.
2 after making the backup from question 1 - assume flashing official flyme to make it like a factory android device. (orig.recovery, OTA and so)
3 flash ubuntu back using backup provided with one.
I guess the ubuntu edition has the bootloader unlocked factory default.
Info on flashing CM or similar can than be like flashing it on original android - assuming (2) is working
As already said, just a remainder - Ubuntu recovery screen that came with the original phone is just ubuntu logo on the center on the screen - I don't know if it is important for any feature (OTA or something)
Best regards!
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Toroman said:
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Click to expand...
Click to collapse
Actually this is most interesting! I would love to buy this phone, ubuntu edition. But since it would be my primary device and ubuntu touch not quite there yet, I'm not. That page about dual boot seems outdated though. And it is about nexus devices
Being able to have dual boot with android or even as someone said above have a back up and every 2 months restore ubuntu and check the progress would be great.
I bought a shield tv 2015 16gb. It was already rooted running full android lollipop. The person I bought it from said this is the best way to run it. I want to upgrade to latest full android. Because I ran out of storage. I believe with update I can add external hard drive and convert it to internal. Since I'm already rooted on full android how would I do it. I also have retroarch with many emulators and hyperspin set up. When I upgrade can I keep it set up or will I lose it. Thanks for any help
Hi, you need to flash stock Nvidia Lollipop recovery image for you SHIELD model (always make sure stock firmwares you download is for your device model).
Once in stock you need to manually upgrade little by little until you get the final prompt to install latest Nvidia Experience 5.1 which is Nougat based via OTA (Over the Air). Why you have to do all that? Because Nvidia also updates bootloader, kernel which are important, mostly bootloader (Warning: never mess or play with the bootloader) and using Nvidia OTA updates service is easy and safe to do.
Usually for Full Android firmware provided by @zulu99 which I bet is the one you have installed is required to flash only system.img and vendor.img so is safe to flash and you can't brick your Shield that way, but to update to latest Full Android Nougat as I said you MUST have to go back to equivalent stock (lollipop in your case) then manually update via Nvidia OTA and once you be in 5.1 stock firmware you can then flash full Android Nougat 1.2 to your device which only contain system.img and vendor.img.
That is why you need to flash full stock updates because you also need to update bootloader, kernel, recovery, etc etc not only system and vendor so that is the CORRECT and SAFE way to upgrade.
Do never try to skip important steps, is not worth it, you will safe yourself many headaches and your money won't be wasted because you device won't brick if you do things right.
Last word of advice, once you are in latest Nougat or above do not attempt to downgrade to MM or LP, otherwise you can brick your device.
From LP to MM to Nougat there are massive changes done, starting for the bootloader and so far there is NO safe way to reverse from Nougat to MM or below, only upgrade. I've seen around 6 users now that have bricked their devices for trying to FULLY downgrade from Nougat.
As always research, ask before doing flashing tasks.
Here is the website where you can read and find instructions. In Full Android Nougat thread you can also find my super video tutorial for step by step instructions to flash that ROM from stock:
http://www.videomap.it/forum/viewforum.php?f=25&sid=7939d87e6e7dd7f1110c20f8cdd28a6f
Everything you need can be found on that forum section.
Enviado desde mi Moto X mediante Tapatalk
Thanks for reply. Watched your video very informative. Do you have a video for me to follow to flash back to stock. I've never done this before but feel confident if I can follow along. Also I have retroarch with emulators , roms and hyperspin that took a long time to setup. What is the best way to back it up and reinstall after upgrade. Is there an backup app I should use
Gknyfd said:
Thanks for reply. Watched your video very informative. Do you have a video for me to follow to flash back to stock. I've never done this before but feel confident if I can follow along. Also I have retroarch with emulators , roms and hyperspin that took a long time to setup. What is the best way to back it up and reinstall after upgrade. Is there an backup app I should use
Click to expand...
Click to collapse
I also have RetroArch and hyperspin setup but for hyperspin all your setup should be in a folder called Hyperspin, all including Roms should be on that folder. I have it like that and I just have to copy that single folder to back it up, very simple. As per RetroArch I think the app has a setting to export the config, check that out. I have very little changes in RetroArch so I don't back up that app config.
Post a screenshot of Settings > About showing off Build, Kernel and Shield Android TV SW version to see if you really have @zulu99 ROM.
I don't have a video about how to flash back to stock but is the same in the way that you have to flash .img files via fastboot, the difference is that you flash stock images not custom.
If you go to the thread of full Android Lollipop for Shield TV, in second post there is a link to Stock Nvidia LP firmware. Download that package, verify the download and uncompress, then ONLY copy system.img to C:\ADB (Did you check my YouTube's video Description to download the tools?) because only system was flashed to have full Android Nougat, the rest is plain stock, it should be, unless the guy you purchased the Shield from also flashed custom recovery. Based on that use the following commands:
fastboot flash system system.img
fastboot flash recovery recovery.img (copy it to C:\ADB too and flash it just in case)
fastboot -w
fastboot reboot
Once done you should be back to stock, let it boot and if everything went well continue with the instructions upgrading via Nvidia OTA until you get to install Nougat 5.1
Write back if you run into an issue.
Edit: links in second don't point to 2.1 LP recovery image anymore. Use this link instead:
http://developer.download.nvidia.com/mobile/shield/ROM/SHIELD_ATV/Upgrade-2.1 - 707MB
Enviado desde mi Moto X mediante Tapatalk
I'm not sure how to post a screenshot on here. In settings my android version is 5.1. My kernel version is 3.10.61-ge817e80 [email protected] u64-396#1. My build number is lmy47d.35739_609.6420.. in my device storage I have a zip file named nv-recovery-image-shield-arc-upgrade2_1_dev_rooted.zip. Is this the image I need to go back to stock. It has the blob ,boot, flash all bat,flash all sh,flash base sh,recover Img,system img, tegra210-foster-e-p2530-0930-e02-00 dtb, and user data img
Gknyfd said:
I'm not sure how to post a screenshot on here. In settings my android version is 5.1. My kernel version is 3.10.61-ge817e80 [email protected] u64-396#1. My build number is lmy47d.35739_609.6420.. in my device storage I have a zip file named nv-recovery-image-shield-arc-upgrade2_1_dev_rooted.zip. Is this the image I need to go back to stock. It has the blob ,boot, flash all bat,flash all sh,flash base sh,recover Img,system img, tegra210-foster-e-p2530-0930-e02-00 dtb, and user data img
Click to expand...
Click to collapse
At the end of Build info says Full Android 2.2 or something similar, details are important.
I also have [email protected] in kernel info so I yes could be zulu99' ROM but I want to make sure, so confirm the build info.
So you have the developer image which comes rooted. I think if you flash the dev image it will upgrade to dev stock firmwares. Thing is I'm not sure if dev images differ in other things than normal stock images because Nvidia tried to screw zulu99 blocking many things so he had to do alot of hacking to have a fully functional full Android Nougat firmware. So, is better if you stick to the instructions, better download stock recovery image and continue:
http://developer.download.nvidia.com/mobile/shield/ROM/SHIELD_ATV/Upgrade-2.1 - download the one with 707MB , the other 709MB is for PRO model.
You may also go ahead and read the .txt file in that link with the instructions to flash back to stock.
Enviado desde mi Moto X mediante Tapatalk
It doesn't say anywhere in the build info full android with a version number. It is exactly like I posted it. The recovery zip I have in my devices storage was left there by person I bought it from. Is that the same as the one you directed me too. Did he leave that file there in the event it would need to be flashed back to stock. I want to make sure I get this right before I have a go at it. I do appreciate your patience thanks
Gknyfd said:
It doesn't say anywhere in the build info full android with a version number. It is exactly like I posted it. The recovery zip I have in my devices storage was left there by person I bought it from. Is that the same as the one you directed me too. Did he leave that file there in the event it would need to be flashed back to stock. I want to make sure I get this right before I have a go at it. I do appreciate your patience thanks
Click to expand...
Click to collapse
No, the files are not the same. Then one you have in your storage has dev_root in package name. Nvidia provides normal stock recovery images and developer recovery images as well for each new OTA release in all models.
The one I linked you to is the normal stock Android TV 16gb recovery image. Download and use that one better and flash (The one in the link I posted).
Enviado desde mi Moto X mediante Tapatalk
Got it, will do. Do you think you could list the steps in a way a noob would understand. Want to make sure I don't brick this
Gknyfd said:
Got it, will do. Do you think you could list the steps in a way a noob would understand. Want to make sure I don't brick this
Click to expand...
Click to collapse
Do this step by step. First let's get you back to stock:
Download the recovery firmware I linked you to, then follow my video but just use system.img and recovery.img of the downloaded firmware, NOTHING ELSE.
Once successfully flashed, reboot your device and report back.
Enviado desde mi Moto X mediante Tapatalk
Ok I'm ready I downloaded all necessary files. My queation when I click on fastboot or add it opens a window and quickly shuts. Should it stay open or not until I plug in shield tv and put it in fastboot mode. Want to make sure everything is right before I start
lavero.burgos said:
No, the files are not the same. Then one you have in your storage has dev_root in package name. Nvidia provides normal stock recovery images and developer recovery images as well for each new OTA release in all models.
The one I linked you to is the normal stock Android TV 16gb recovery image. Download and use that one better and flash (The one in the link I posted).
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
Ok I believe I'm ready I downloaded all all I need from your links. In c drive I have adb folder with fastboot adb , system img and recovery img. And adbwinapi.dll and adbwinusbapi.dll. If I click on fastboot or adb a windows opens and quickly shuts. Is this normal. Does it only stay open once I'm in boot loader . Want to make sure everything is right before I start
Gknyfd said:
Ok I'm ready I downloaded all necessary files. My question when I click on fastboot or add it opens a window and quickly shuts. Should it stay open or not until I plug in shield tv and put it in fastboot mode. Want to make sure everything is right before I start
Click to expand...
Click to collapse
Hmm seems you're not following the video. I asked before did you check my youtube's video description? because there i provide some links and the first link is to download the proper tools... https://bit.ly/satvtools, then in C:\ADB you have to double click the command line shortcut named ADB and NOT fastboot.exe
I suggest to first watch the entire video at least 3 times before proceeding, so you start understanding better the procedure.
Ok I will want to make sure I understand and do this right. I didn't connect shield yet for that reason. If shield isn't connected and I and I double click adb should window stay open or only when shield is connected
Gknyfd said:
Ok I will want to make sure I understand and do this right. I didn't connect shield yet for that reason. If shield isn't connected and I and I double click adb should window stay open or only when shield is connected
Click to expand...
Click to collapse
Use the ADB.Ink shortcut that is inside ADB folder (from the .zip tools i provided)
If you click on ADB.Ink, WIndows will then open the CMD/ Windows Shell/ Terminal Console or whatever you want to call it and remain open
Thanks for your patience got it I put it in c:/ adb folder. That's where it should be right. If yes I'm gonna go for it
Having a problem my computer isn't seeing the shield tv not able to install drivers
Gknyfd said:
Thanks for your patience got it I put it in c:/ adb folder. That's where it should be right. If yes I'm gonna go for it
Click to expand...
Click to collapse
Yes, everything (tools, .img files,etc) should be under C:/ADB folder
Gknyfd said:
Having a problem my computer isn't seeing the shield tv not able to install drivers
Click to expand...
Click to collapse
Try with other USB cables
Thanks for all your help and your time. I got it done. I'm back to stock and fully upgraded tomorrow I'll follow your video and root to full nougat. Couldn't have gotten it done without your guidance. Hopefully I'll be able to help out others in my situation now. It was the USB cable. I had 2 that didn't work. Finally the third I tried worked. Thanks
Hello guys,
I'm about to sell my Nvidia Shield TV (2015, 16 gb) because honestly, it doesn't get any use lately.
I wanted to flash the stock Nvidia ROM (I had an old custom rom) but I have no success so far. I must say that I always had problem with and fastboot on my computers, because they all fail to see my android devices, including the Nvidia Shield TV (or my Nexus, or my Xiaomi...). I tried using Windroid Toolkit but it's the same (device is always OFFLINE). I tried every driver out there and it's the same...
On my Shield, I still have access to the bootloader, but "recovery" option freeze the shield. Somehow I managed to get access to TWRP twice but I don't know how. And finally android 6.0 won't boot anymore (I think I flashed it by mistake). To sum up : things are getting complicated...
At some point I accessed TWRP but couldn't flash the image I had (nv-recovery-image-shield-atv-5.2.0-dev_rooted) that I downloaded on Nvidia server. It told me something about some file (containing "update" something) it couldn't find. I wonder if I didn't get the right ROM (is it just for updating ? it's already 1.2 GB...)
I tried flashing img manually (recovery.img, boot.img, system.img), but had no partition to flash system.img to
Could anyone out there help me ? I'd just like to get done with it and finally sell it...
Edit : Okay nevermind I finally got it working after reinstalling all drivers and trying again several different drivers. I reinstalled the rom using adb and it works fine.
I can only use TWRP, I don't have a PC
I'm guessing that you never got flashing on TWRP to work?
Marchombre said:
Hello guys,
I'm about to sell my Nvidia Shield TV (2015, 16 gb) because honestly, it doesn't get any use lately.
I wanted to flash the stock Nvidia ROM (I had an old custom rom) but I have no success so far. I must say that I always had problem with and fastboot on my computers, because they all fail to see my android devices, including the Nvidia Shield TV (or my Nexus, or my Xiaomi...). I tried using Windroid Toolkit but it's the same (device is always OFFLINE). I tried every driver out there and it's the same...
On my Shield, I still have access to the bootloader, but "recovery" option freeze the shield. Somehow I managed to get access to TWRP twice but I don't know how. And finally android 6.0 won't boot anymore (I think I flashed it by mistake). To sum up : things are getting complicated...
At some point I accessed TWRP but couldn't flash the image I had (nv-recovery-image-shield-atv-5.2.0-dev_rooted) that I downloaded on Nvidia server. It told me something about some file (containing "update" something) it couldn't find. I wonder if I didn't get the right ROM (is it just for updating ? it's already 1.2 GB...)
I tried flashing img manually (recovery.img, boot.img, system.img), but had no partition to flash system.img to
Could anyone out there help me ? I'd just like to get done with it and finally sell it...
Edit : Okay nevermind I finally got it working after reinstalling all drivers and trying again several different drivers. I reinstalled the rom using adb and it works fine.
Click to expand...
Click to collapse
What drivers did you find worked?
Hi, i am new to this forum. I have a nvidia shield TV from 2018 with stock rom 8.0.1. it shows to update to 8.0.2. I would like to flash lineage OS on it. Is this possible? Can someone point me on the correct thread if possible please?
Thy, ray
Nvdia shield Falsh Lineageos or Debian
h, i try to flash with trwp foster but nothing work.
only nvidia logo and must poweroff.
same with different kernel to start OS debian on microsd card.
In developer forum there is a thread about Lineage, to successfully install Lineage you need to downgrade to experience 7.1 and use last oficial twrp for shield, this is the only know way to install Lineage
zecabra said:
In developer forum there is a thread about Lineage, to successfully install Lineage you need to downgrade to experience 7.1 and use last oficial twrp for shield, this is the only know way to install Lineage
Click to expand...
Click to collapse
Thy for the answer. I ll figure out, howto do this.
no way
thanks for your answer
i try to downgrade with nv recovery 7.1 dev rooted. but nothing work. only nvidia logo freeze.
i reflash nv recovery 8.0.1 dev rooted version, and all return ok. nvdia reboot normaly
bst regards.
AldoReset said:
thanks for your answer
i try to downgrade with nv recovery 7.1 dev rooted. but nothing work. only nvidia logo freeze.
i reflash nv recovery 8.0.1 dev rooted version, and all return ok. nvdia reboot normaly
bst regards.
Click to expand...
Click to collapse
I did not have any success in changing Operation system. I decided to switch to odroid N2. This suits perfect. No Google and kodi is working flawless via emmc. Software =Coreelec. Perfect and i dont give a **** in nvidia shield.greetz, Ray
Ps** On Top, low cost with 115€