[RECOVERY][8-24-13]Unofficial OUDHS Recovery 1.0.3.6 for Nvidia Shield

[Ksehwail]

OK last question before I flash the boot.IMG do you know if it's OK to use the IMG from the fly one since it is the same device just different manufacturer as you mentioned,.. Thanks
Edit: after rereading your response I saw you said to fastboot not flash.... Can you run the command by me I'm a bit rusty

 

[aDigitalPhantom]

Is the superfly one just a re-branded regular Tegra Note 7? What you can do is fastboot boot (NOT FLASH) the superfly image to see if it works. I saw your other question thread if you can get root access on your Evga Tegra Note 7 then you can pull it's recovery.img.



Yes there is a way to pull your devices recovery.img, but it requires root access (Make sure you have root access on your device first. First reboot your device into recovery mode and wipe your devices cache then reboot the device into the Android OS. Then from terminal emulator or ADB shell please run the following command and upload the result of the following command:

su
cat /cache/recovery/log

This will allow me to determine which partition on your device is the recovery partition that you need to dump. As always if you have any questions let me know I'll be happy to help you out .

OK last question before I flash the boot.IMG do you know if it's OK to use the IMG from the fly one since it is the same device just different manufacturer as you mentioned,.. Thanks
Edit: after rereading your response I saw you said to fastboot not flash.... Can you run the command by me I'm a bit rusty

He did post the command...

.....fastboot boot.....

here is a more specific example of the command to boot an image

fastboot boot image.name

image.name is the name of the image to boot.
If your recovery image is named recovery.img then the command becomes

fastboot boot recovery.img

 

[Ksehwail]

This is meant for the Nvidia Shield only. However if you can provide me with your devices stock recovery.img or a link to where I can find it I can try and compile recovery for your device.

Sent from my SCH-I535 using XDA Premium 4 mobile app

Shrimp208 I have replied to your last message however i am not seeing that it was even sent in my message list sorry for trolling just wanted to make sure the messages went through.... whenever you have some free time will you give me a heads up... Thanks a lot for all the help

---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------

He did post the command...


here is a more specific example of the command to boot an image

fastboot boot image.name

image.name is the name of the image to boot.
If your recovery image is named recovery.img then the command becomes

fastboot boot recovery.img

Thank You for the clarification... I just wanted to be sure

 

[shimp208]

Shrimp208 I have replied to your last message however i am not seeing that it was even sent in my message list sorry for trolling just wanted to make sure the messages went through.... whenever you have some free time will you give me a heads up... Thanks a lot for all the help

---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------




Thank You for the clarification... I just wanted to be sure

All your messages have gone through okay and don't worry your not bother me I'm happy to help people .

 

[twistedumbrella]

All your messages have gone through okay and don't worry your not bother me I'm happy to help people .

These are for you bro-seph:

https://github.com/StarKissed/roth-recovery-oudhs/commit/d387bc0c69c75760b60b4e0d80f4275d45193c15
https://github.com/StarKissed/roth-recovery-oudhs/commit/241f856014018b67b71de2ec067176cccbfbb387

I'm feeling like Sandroid Clause. I am still looking through stuff, but it seems I have a little downtime.

 

[shimp208]

These are for you bro-seph:

https://github.com/StarKissed/roth-recovery-oudhs/commit/d387bc0c69c75760b60b4e0d80f4275d45193c15
https://github.com/StarKissed/roth-recovery-oudhs/commit/241f856014018b67b71de2ec067176cccbfbb387

I'm feeling like Sandroid Clause. I am still looking through stuff, but it seems I have a little downtime.

Thanks man I appreciate it, I was hopping to take a look at things but also have had very little time but thank you Sandroid Clause for your presents . The original post has been updated with version 2 of the recovery image that hopefully fixes some of the problems people were having earlier, as always any testing feedback is greatly encouraged and appreciated .

 

[twistedumbrella]

Thanks man I appreciate it, I was hopping to take a look at things but also have had very little time but thank you Sandroid Clause for your presents . The original post has been updated with version 2 of the recovery image that hopefully fixes some of the problems people were having earlier, as always any testing feedback is greatly encouraged and appreciated .

No problem. I stole the first part from the CWM decompile I did and the second was taking apart the SuperSU archive. I didn't test any of it, though, but it sounded like the right thing to do haha.

 

[roustabout]

Is the boot.img file from an update.zip file which is described as being the tool to use to recover a device in an emergency actually a stock recovery?

If so, the HP slate 8 has one and it's just about a poster child for OUD...

(sez he who's seeing how much of the T7 / shield work is applicable, unloved or not... turns out: quite a lot!)

 

[shimp208]

Is the boot.img file from an update.zip file which is described as being the tool to use to recover a device in an emergency actually a stock recovery?

If so, the HP slate 8 has one and it's just about a poster child for OUD...

(sez he who's seeing how much of the T7 / shield work is applicable, unloved or not... turns out: quite a lot!)

The boot.img file (Your devices stock boot image) found in your update.zip and recovery.img (Stock recovery image for your device) are two different things one contains your devices kernel (boot.img) and the other is used for recovery mode (recovery.img). Are you asking if someone can compile recovery for your device?

 

[roustabout]

The boot.img file (Your devices stock boot image) found in your update.zip and recovery.img (Stock recovery image for your device) are two different things one contains your devices kernel (boot.img) and the other is used for recovery mode (recovery.img). Are you asking if someone can compile recovery for your device?

I was looking to see if I had a copy of the recovery to share. But yes, if someone knows how to do a recovery for the platform that'd be great. Otherwise, it's possible I'll sound it out eventually

I tried

fastboot -i 0x03F0 boot thor-oudhs-1.0.3.6-unofficial-v2.img
downloading 'boot.img'...
OKAY [ 0.374s]
booting...
OKAY [ 0.016s]
finished. total time: 0.390s

but when I got back to the GUI, there were no files in /cache/recovery/log

Recovery mode on the device is minimal - there are no commands available, even the minimal ones I'm used to seeing with a stock recovery - so clearing cache before I started wasn't an option.

If /proc/mounts or /proc/partitions would help ID the recovery partion I'll post those.

 

[shimp208]

I was looking to see if I had a copy of the recovery to share. But yes, if someone knows how to do a recovery for the platform that'd be great. Otherwise, it's possible I'll sound it out eventually

I tried

fastboot -i 0x03F0 boot thor-oudhs-1.0.3.6-unofficial-v2.img
downloading 'boot.img'...
OKAY [ 0.374s]
booting...
OKAY [ 0.016s]
finished. total time: 0.390s

but when I got back to the GUI, there were no files in /cache/recovery/log

Recovery mode on the device is minimal - there are no commands available, even the minimal ones I'm used to seeing with a stock recovery - so clearing cache before I started wasn't an option.

If /proc/mounts or /proc/partitions would help ID the recovery partion I'll post those.

First off make sure to never flash anything that is not meant to be flashed on your device, the recovery image in this thread is for the Nvidia Shield not the HP Slate 8. Is your device rooted? Because if it is I can guide you on how to to dump your recovery.img that can be used for compiling recovery.

 

[roustabout]

Whoops - the oem unlock format is partial. The kingsoft-installed su persisted, so I could see the device booting in response to fastboot flash, but when I actually read the script on the github, I realized it was erroring out after the script asked the device for its name.

I am rooted, though

yes, I rooted using the tegra note root.img and fastboot boot.

Am I correct in thinking fastboot boot does not flash an image but instructs the device to boot from what's coming in over adb, somewhat analogous to pxe booting?

I hope so, or else I'm just crazy lucky

 

[Sess]

does this recovery flash OTAs?

the original CWM port stopped working and seems to have been abandoned...

 

[SkylerZio]

trying to test boot with

fastboot boot thor-oudhs-1.0.3.6-unofficial.img

but it just sits at booting downloaded image, or whatever it says at the fastboot menu

about how long should it pause there?

 

[shimp208]

does this recovery flash OTAs?

the original CWM port stopped working and seems to have been abandoned...

I used the device name thor rather then then roth when compiling this recovery, so OTA's will most likely not work, I unfortunately do not own a Shield and my friend who owned a shield that I used to test it on sold his.

 

[shimp208]

trying to test boot with

fastboot boot thor-oudhs-1.0.3.6-unofficial.img

but it just sits at booting downloaded image, or whatever it says at the fastboot menu

about how long should it pause there?

It shouldn't sit there longer then 10-15 seconds I would power off the device. Reboot back into the bootloader and use fastboot to try and flash the image again.

 

[SkylerZio]

It shouldn't sit there longer then 10-15 seconds I would power off the device. Reboot back into the bootloader and use fastboot to try and flash the image again.

2 more attempts, and 2 more lock ups...?

See, the funny thing is I used it before and actually installed it the first time, and it worked great (I loved it BTW! Good work!) But then I restored a stock official image and now I'm having this problem. Granted I didn't yestboot the first time, and didn't actually install this time. Does that give you any ideas?

 

[shabbypenguin]

Imagine my surprise when i get an email asking for help fixing oudhs recovery on a device i knew we never ported it to. glad to see it impacted people enough that they wanted to spread it, however i was the only one from the team pushing changes to the source (and dhacker was nice enough to kick in a few) so i gave up trying to keep up with selinux and 4.4 changes etc. plus all of the cool features in oudhs have been merged into regular cwm now. so for teh sake of moving forward i would highly suggest just using mainline cwm, the swipe controls are in there as is rainbow mode

regardless just so im clear, screen is rotated, the joypad doesnt work? at all in recovery? or does it work in the key test function? if it does then you just need a custom recoverykeys.c mapping them. anything else i forget?

 

[twistedumbrella]

Imagine my surprise when i get an email asking for help fixing oudhs recovery on a device i knew we never ported it to. glad to see it impacted people enough that they wanted to spread it, however i was the only one from the team pushing changes to the source (and dhacker was nice enough to kick in a few) so i gave up trying to keep up with selinux and 4.4 changes etc. plus all of the cool features in oudhs have been merged into regular cwm now. so for teh sake of moving forward i would highly suggest just using mainline cwm, the swipe controls are in there as is rainbow mode

regardless just so im clear, screen is rotated, the joypad doesnt work? at all in recovery? or does it work in the key test function? if it does then you just need a custom recoverykeys.c mapping them. anything else i forget?

The keypad mapping is standard Android gamepad maps. 108 - Start, 109- Select, A, B, X, Y, Dpad are all standard too.

It's a landscape device, so the view just needs a 90 degree offset.

It's a lot of silly stuff that people coming from phones never really had to consider when porting stuff before. I'm pretty sure the documentation wasn't there at that time either.