Related
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618
I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.
Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123
Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?
The stock recovery says it's not available anymore.
If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.
I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.
This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?
aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?
tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Would ADB be any better?
Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.
I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol
aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.
There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.
OUYA Safe Recovery v1.0.0
Because the OUYA lacks a hardware recovery button combination.​Purpose
To create a safe environment where the end user can flash their OUYA with confidence.
How This is Achieved
By switching the roles of the boot image and the recovery image, the user is presented with a customized recovery before entering the actual ROM. This gives the user a failsafe before they start to flash their OUYA. This way if something were to go wrong in the flashing process, the recovery image is still in tact and the system can be restored to a working state.
Features
Custom font size that looks better on HDTV's.
Custom color scheme that matches that of the OUYA theming.
Custom reboot options.
Installation Methods
Method 1 - Computer
Simply download the archieve containing a script that will flash your OUYA. Follow the on-screen directions based on the OS your computer is running.
Method 2 - Recovery
This method is a little more dangerous, but if you already have Clockworkmod Recovery installed on your OUYA you can flash the specified zip to install OUYA Safe Recovery.
Downloads
Computer Method: Ouya Safe Recovery Installer v1.0.0.zip - 16.08 MB
Recovery Method: update_v1.0.0.zip - 6.93 MB
Source and GPL
The source for this project is quite simple, but will continue to evolve over time. If you are interested in taking a look at the required source code or compiling your own Safe Recovery binary, you can find the requested material here.
Credits
Credit to koush for maintaining ClockworkMod Recovery which this recovery is built and compiled from, and to mybook4 for the original CWM port to the OUYA.
Donations and Thanks
If you like the work that I am doing and would like to send a donation my way, please feel free to do so, even though it is not required. Every dollar is appreciated, and will go towards future development costs.
Changelog
Will we be able to install Cyanogenmod 10 with this recovery? Or will we need to replace the boot.Img in the zip so it will gflash correctly without having to use fastboot?
Edit: Where are my manners, AWESOME! Thanks for the recovery! I remember you talking about it in the Cyanogenmod Thread and I didn't expect it to be made so fast!
qwasz123 said:
Will we be able to install Cyanogenmod 10 with this recovery? Or will we need to replace the boot.Img in the zip so it will gflash correctly without having to use fastboot?
Edit: Where are my manners, AWESOME! Thanks for the recovery! I remember you talking about it in the Cyanogenmod Thread and I didn't expect it to be made so fast!
Click to expand...
Click to collapse
To install Cyanogenmod 10 you will need to manually flash the boot.img to the recovery partition.
Code:
fastboot flash recovery 20130702-boot.img
Thanks for the nice comment!
ProfessorAnomaly said:
To install Cyanogenmod 10 you will need to manually flash the boot.img to the recovery partition.
Code:
fastboot flash recovery 20130702-boot.img
Thanks for the nice comment!
Click to expand...
Click to collapse
You're welcome!
So I'm guessing all of the roms need to be updated to install to the recovery partition instead of the boot partition?
Hi, you have done A Great Job, i flashed (via CWM) the recovery and Its working, i also flashed boot image (via Fastboot) and its booting.. Everything is working, we are safe Now!!! Finally!!!! Thanks to you!!!
This should be in Xda Portal!!!!
Only one thing remains what should we choose when we are asked to disable recovery flash... ?
Tried the installer from windows and it reset the ouya and booted back into the ouya launcher? Am I doing something wrong? So far im rooted and adb is working as its sending the files to my internal SD Card. Driver is installed correctly on the pc. Im running Windows 7 (x86).
Sent from my A210 using Tapatalk 4
Does this have any passthrough mode? I mean, is there any functionality to make it automatically boot into the rom by default, and only show the recovery screen if you are holding the power button or some key on the usb keyboard?
qwasz123 said:
You're welcome!
So I'm guessing all of the roms need to be updated to install to the recovery partition instead of the boot partition?
Click to expand...
Click to collapse
The updated fstab should allow for the existing ROMs to flash the boot image to the recovery partition granted developers are writing the image the correct way.
suruceanu.nick said:
Hi, you have done A Great Job, i flashed (via CWM) the recovery and Its working, i also flashed boot image (via Fastboot) and its booting.. Everything is working, we are safe Now!!! Finally!!!! Thanks to you!!!
This should be in Xda Portal!!!!
Only one thing remains what should we choose when we are asked to disable recovery flash... ?
Click to expand...
Click to collapse
I've been choosing no, but I doubt it makes much of a difference.
martinbrettphilo said:
Tried the installer from windows and it reset the ouya and booted back into the ouya launcher? Am I doing something wrong? So far im rooted and adb is working as its sending the files to my internal SD Card. Driver is installed correctly on the pc. Im running Windows 7 (x86).
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
It should work. I don't see why it wouldn't if adb is working correctly.
Maybe a bad download is to blame?
gianptune said:
Does this have any passthrough mode? I mean, is there any functionality to make it automatically boot into the rom by default, and only show the recovery screen if you are holding the power button or some key on the usb keyboard?
Click to expand...
Click to collapse
This is what I have planned for the next update. Shouldn't be too long before I get it worked out.
ProfessorAnomaly said:
It should work. I don't see why it wouldn't. Maybe try rebooting?
Click to expand...
Click to collapse
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
ProfessorAnomaly said:
This is what I have planned for the next update. Shouldn't be too long before I get it worked out.
Click to expand...
Click to collapse
I believe that for koush bootstrap recovery what it does is puts a certain file /system/etc on successful shut down and when it restarts the recovery checks first if the file is there and it moves into normal boot and after that it destroys the file to be rebuilt on successful shutdown.
But if the file is not found it goes into recovery mode
martinbrettphilo said:
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
Could you please screenshot the errors you are seeing?
I installed this but I'm confused on how to get into recovery. When trying to boot into recovery, it boots into a screen with a Ouya logo and an exclamation mark right under it (Ouya !")
martinbrettphilo said:
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
Sam3gX said:
I installed this but I'm confused on how to get into recovery. When trying to boot into recovery, it boots into a screen with a Ouya logo and an exclamation mark right under it (Ouya !")
Click to expand...
Click to collapse
The installation was not successful. Please try again.
Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRP recovery version on grouper. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for grouper http://techerrata.com/browse/twrp2/grouper
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/grouper) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-grouper.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
There are many tutorials online explaining this process I just thought customizing it to the grouper would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That will work. But knowing your way around adb/fastboot can't hurt. There won't always be a GUI to do everything for you.
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know of flashify, awesome. Thx, really fast and easy method. Best thing is I didn't even need my pc for it
Thanks for the tutorial but surely this belongs in q&a, help etc not android development ;p
Sent from my Nexus 4 using XDA Premium 4 mobile app
Actually it's suited to the General section (guides and all). I appreciate you advising the fastboot method (I use it too), but it can b a pain for people who don't have their devices configured (configuring it can be a pain sometimes too). Flashify, as one member said, is a great alternative. BUT you *may* brick your device if you flash something to the wrong block device (possibility of that happening to an expert user: 0.0001%; possibility of that happening to a new user: 1%). Just my two cents.
I agree guys this should be in general. I've never posted anything but a build and didn't even think about it. Do I need to get a mod to move it? As for flashify sounds like a great tool. I've never had the pleasure of using it but if it works and people are comfortable with it more power to it. Personally fastboot is what I'm comfortable with it might seem a little in depth but really its quite simple especially if you use adb for logcats and are setup.
OP No worries, moved and thank you.
To flash 4.4 ROMs one could follow this tutorial, or one could simply flash this .zip of the latest version of CWM:
http://forum.xda-developers.com/showpost.php?p=46053223
So, i've bricked it already.
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
ziffius said:
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
Click to expand...
Click to collapse
I'm sure this is not what you want to hear but if all else fails push the factory.IMG you will be starting from square one. You can try pulling your backups off but might as well start over for 4.4
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for this recommendation. Really nice. Simple and took out all the nervousness of using the computer to push these files etc.
REally truly best for flashaholics.
question
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Ergina95 said:
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Click to expand...
Click to collapse
Did you ever try just flashing it and if so, did it work?
for some reason i cannot download the twrp ..it stuck at 99%
tried 2 version of twrp..hurm
Mookie2014 said:
Did you ever try just flashing it and if so, did it work?
Click to expand...
Click to collapse
yeap! did it! worked perfectly :good: just flash zip updates through the recovery
If coming from the original JellyBean and have not updated your custom recovery since, you will need to install the recovery provided below. This step only needs to be performed once to support the newer updates.
Recovery Update
Boot into bootloader mode, connect the USB cable, and from a terminal window or command prompt type:
Code:
fastboot flash recovery recovery.img
To root an OTA, the procedure is pretty simple.
Code:
Copy the OTA from the cache folder to the sdcard.
Move the OTA zip somewhere it can be opened and unzip it
Go to system/etc/ to find the file named recovery and delete it
(extension may vary, but it is always named recovery)
Open the META-INF/com/google/android/updater-script
Delete all of step 1 and step 3 so that all that is left is the large middle portion without any steps
That's it. You have made the same files you find here.
Download the desired package below and copy it to your sdcard, along with the SuperSU recovery package.
Boot into recovery, select install from sdcard, and choose the update. Go back and repeat the install for SuperSU.
KitKat Update 98
KitKat Update 99
Lollipop Update 110
XDA:DevDB Information
Nvidia Root-Friendly Updates [No Wipe], ROM for the Nvidia Shield
Contributors
twistedumbrella
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-11-08
Last Updated 2018-07-05
twistedumbrella said:
The new update has a few things that require updating the recovery, but since a recovery is not officially developed, updating the kernel of the existing recovery will do the trick. Flash this first.
Recovery Update
The install requires removing the assert checks since there is an error that the device is a Thor but looking for a Roth (same thing, right?). Install this from the new recovery.
KitKat Update
Immediately after installing the update, install the SuperSU recovery package to restore root and you're all set.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
NapalmDawn said:
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
Click to expand...
Click to collapse
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
twistedumbrella said:
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
Click to expand...
Click to collapse
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
NapalmDawn said:
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
Click to expand...
Click to collapse
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
KitKat Update Without Complete Re-root
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
twistedumbrella said:
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
Click to expand...
Click to collapse
Ahh I gotcha. Well that's good to know. I haven't had a chance to really look at many of the files yet. Do you know if nvidia released the factory recovery packages yet?
EDIT:
Nevermind looks like 72 is out now.
Yeah, they are pretty good about that. It may be nearing the last update for this version, though
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
NapalmDawn said:
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
Click to expand...
Click to collapse
Exactly
twistedumbrella said:
Exactly
Click to expand...
Click to collapse
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
NapalmDawn said:
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
Click to expand...
Click to collapse
The OTA will restore the stock recovery. This way updates it to one compatible with KitKat.
KitKat Update Without Complete Re-root
OTA 98 has been added. No recovery update is needed coming from 72. Flash the build and SuperSU and off you go. No data wipe necessary, either.
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Neoistheone2000 said:
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Click to expand...
Click to collapse
Updated
twistedumbrella said:
Updated
Click to expand...
Click to collapse
Thanks, that worked a treat
Yeah, to clarify, in recovery, you must press and hold Shield and Home buttons for a second, then release to bring up the menu. Then use X and Y to navigate, A to select. Don't understand why the bootloader or recovery don't use the D-pad at all. They're weird. Anyway, downloading this now, and will report back in a few minutes. This is just sideloaded via the stock recovery, right? I hope so, that's how I'm doing it right now.
EDIT: Nope. Failed again.
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I think I'll try that new recovery (funny, because I had flashed the one included in the original update archive, still had issues). I shouldn't have to use that one, I was on update 92 already.
EDIT 2: Oh, I'm dumb. Here I thought this was still being done with the STOCK recovery. Didn't realize this would flash in CWM. Awesome. Flashed SuperSU 2.16 while I was at it. Rebooted, and it's at .98, with root access. You ROCK, @twistedumbrella!
Did you do this with update 99 yet? Just came out today.
GuyInDogSuit said:
Did you do this with update 99 yet? Just came out today.
Click to expand...
Click to collapse
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
twistedumbrella said:
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
Click to expand...
Click to collapse
Hmmm. It started downloading as soon as I turned mine on. I'm just gonna do the usual process.
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?
Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.
This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/
Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?
JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.
ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.
SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.