Develop Bugs

[MOD] Hulu Hack 10.3/GB

Ok guys, so I absolutely love Hulu and other legit TV sites, some of which prohibit mobile devices based on a "flash id" similar to what you have with a User Agent string for the browser. It is based on this ID that it prohibits mobile phones from accessing content such as hulu and HBO (I think?). With this mod your phone will appear as though it is a PC running flash and I believe it also modifies your version number to be something like 99.9.999.99 for sites that try and check the version number. I also must make sure to give credit where credit is due. Credit goes to imneveral0ne who posted the modified lib files in the Thunderbolt forums http://forum.xda-developers.com/showthread.php?p=12433036#post12433036.
His mod stopped working because Gingerbread (and 10.3) copies the lib files from the APK itself back into the lib folder (/data/data/com.adobe.flashplayer/lib/) on boot, thus require the mod be redone every reboot. I simply took his mod, wrote a simple script that installs the hacked lib files to /data/flash/ at first for storage, modifies permission of /data/data/com.adobe.flashplayer/lib/ so that it can be written to by the script, and also installs a "run on boot" script at /system/etc/init.d/01-fixflash.sh which will copy the hacked lib files from /data/flash to /data/data/com.adobe.flashplayer/lib/. It also adds Hulu Bookmark app (1.0) to /data/app.
For whatever reason, I've been having trouble replicating a "start from stock, flash, and you're good" situation. Something about my setup isn't quite perfect yet (this is my first "mod"/script, and first flashable zip so any suggestions would be greatly appreciated), as I've had some issues getting it to run on its own the first time. That being said my launcher pro also force closes on every reboot so the leaked EF02 and nagging (ef10 to ef02) downgrade screen may be responsible. The GOOD news is that it does seem to work like clockwork once the script has been run manually for the first time. Enough explaining why, now to the how:
REQUIREMENTS:
Kernel with init.d support (most custom kernels with root support) and root
Busybox (for running the copy commands. If you don’t have it, install ‘busybox installer’ from the market once you are rooted)
Root explorer (recommended, not required)
NOTE: I have developed this file FOR gingerbread, however I BELIEVE it should also work on froyo. Please let me know if it does/doesn’t work on Froyo. If it doesn’t work and needs troubleshooting let me know and I’ll downgrade again to see if I can get it worked out.
INSTRUCTIONS:
EDIT: I'm such a moron, I almost forgot:
Install latest flash player (10.3.185.25) from the market FIRST and be sure to uncheck automatic updates (and don't manually either)
Make sure busybox is installed. One way to test this is to type cp –help in ADB and see if it can run the command. If it does, you’re good to go.
Next, simply flash gbflash.zip. Wipe cache/dalvik if you want (I don’t believe it’s necessary, although again, this is my first time and for whatever reason the script doesn’t seem to want to run on its own the first time)
Upon first reboot, you MAY be lucky enough that it simply just works and you’re all set. I was not this lucky, either due to my semi-lockup (FC of launcher pro) on boot and/or the EF10->EF02 downgrade screen. Anyways, if you still get the "Hulu not available for your platform" error, simply use either root explorer or adb to run the script for the first time manually. In root explorer, navigate to /system/etc/init.d, tap on S98fixflash and select "execute". In ADB, navigate to /system/etc/init.d and type "sh S98fixflash". Wait a sec for it to run, then try Hulu again. It should be working immediately (without a reboot required) AND the script should then run correctly on subsequent reboots.
Like I said this is my first "product" I've been able to make available to the community and am more than open to suggestions, criticisms and ideas of how I can make this script better. Enjoy guys!
EDIT: If you do have issues with the script not running on every reboot, simply install "Script Manager" from the market, navigate to /system/etc/init.d, select S98fixflash and check the "run on boot" checkbox.
NOTE: I believe this hack is EXCLUSIVE to Gingerbread (and maybe Honeycomb). Froyo will not work
http://www.multiupload.com/E9GP7V1QJ1 - update 10/4//2011 for 11.0.1.152 AND hopefully fixed data mounting issues on certain devices so it works easily on CWM on more devices
NOTE: Latest update includes a brand new flashplayer.so files freshly edited, so no more issues with youtube in the browser, and uses TRUE flash 11.0.1.152 libraries for increased performance (no longer based on 10.2) (LOL, flash 11 was only released 4 hours ago, hehe
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
)
Note: after more feedback it seems using busybox installer from the market helps if running the script, even manually does nothing.

Cool
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.

Wait I'm a little confused...are you saying that your launcher pro FCs and EF10 downgrade are indepenent of this, or is this script causing those problems?
As of right now, Launcher Pro has never FCed on me on EF02, and the downgrade prompt never pops up (it used to but it stopped for some reason).
Jus trying to get all the info before I flash this.
Btw, I assume that simply deleting the .sh file would uninstall this mod, thereby preventing anything from being done at boot? If not, what would be the proper way to uninstall this?
Sent from my SPH-D700 using XDA Premium App

You are correct on uninstall procedure. Delete 01-fixflash.sh from /system/etc/init.d. It also places a 'flash' folder in /data that can be deleted. It also modifies permissions for /data/data/com.adobe.com/libs to make it writable (shouldn't cause any issues if left) but can be undone by uninstalling and reinstalling flash. Yes my launcher pro fcs because of the ef10->ef02 downgrade question (I think). Hope to check again on official release. Please let me know if this a) works b) doesn't or c) (like me) mostly works on most reboots, but script aways work when run by hand.
Another option is to install script manager because you can then tell script manager to run 01-fixflash.sh on boot, and then it should DEFINATELY work, although I know most people prefer not to install additonl appliations...
EDIT: I believe my launcher pro FCs INDEPENDENT of this script (ie it happens whether or not the script is installed) Also, Launcher Pro works, just FCs once on boot, then works like a charm the rest of the time
Sent from my SPH-D700 using XDA App

The flashable zip did not work. It flashed but did not successfully write anything usable to phone. However, the apk on the original posting worked great!

Yes, the APK I pulled from should work UNTIL you upgrade to gingerbread (correct me if I'm wrong). Did you happen to try the script manager trick? Sometimes the script won't run on boot on its own (particularly if you have a stock kernetl). This will probably be of more use to GB users who really require the boot script.

Ran the script, but the file is not in the init.d directory.....
In root explorer, navigate to /system/etc/init.d, tap on 01-fixflash.sh and select “execute”.

tazman19 said:
Ran the script, but the file is not in the init.d directory.....
In root explorer, navigate to /system/etc/init.d, tap on 01-fixflash.sh and select “execute”.
Click to expand...
Click to collapse
There will only be 1 file in /system/etc/init.d, 01-fixflash.sh. It copies files from /data/flash to /data/data/com.adobe.flashplayer/lib/. When you execute it, then visit Hulu In dolphin, set to desktop it still doesn't work?
Are you saying the 01-fixflash.sh doesn't exist? Or that's the only file you see in there. Also note you must install flash from the market first. It should Always work when being run by hand. How about running the script, choosing execute, then the hulu app? Sorry, trying to figure out what the issue is.
Also, I'm on EF02 odex (stock), ef02 plus kernel, cwm 3.1.0.1. U same?

compuw22c said:
There will only be 1 file in /system/etc/init.d, 01-fixflash.sh. It copies files from /data/flash to /data/data/com.adobe.flashplayer/lib/. When you execute it, then visit Hulu In dolphin, set to desktop it still doesn't work?
Are you saying the 01-fixflash.sh doesn't exist? Or that's the only file you see in there. Also note you must install flash from the market first. It should Always work when being run by hand. How about running the script, choosing execute, then the hulu app? Sorry, trying to figure out what the issue is.
Also, I'm on EF02 odex (stock), ef02 plus kernel, cwm 3.1.0.1. U same?
Click to expand...
Click to collapse
Same as your setup, can't get it to work, still getting unsupported device message on hulu.com. The apk won't work for me either since it wants to find com.adobe.flash (or whatever it's called), and the one that exists on my phone has number "1" attached at the end. And I do have the latest flash, I just installed it for this very reason.
One question though, the stock browser doesn't seem to have an option to turn off mobile view?
EDIT: one difference I just noticed is that I'm deodexed, not odexed. I wouldn't think that would matter though...
Sent from my SPH-D700 using XDA Premium App

LoO
squshy 7 said:
Same as your setup, can't get it to work, still getting unsupported device message on hulu.com. The apk won't work for me either since it wants to find com.adobe.flash (or whatever it's called), and the one that exists on my phone has number "1" attached at the end. And I do have the latest flash, I just installed it for this very reason.
One question though, the stock browser doesn't seem to have an option to turn off mobile view?
EDIT: one difference I just noticed is that I'm deodexed, not odexed. I wouldn't think that would matter though...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
You could change the script if you can't find that file. So your libflashplayer.so file is located where, /data/data/com.adobe.flashplayer-1/lib ? Also are you on ef02 or ec05? Have you tried running the script via adb to see what errors it gives? You may need to run busybox installer from market to make sure the cp (copy) command itself works.
Edit: Also, I know there's an apk with -1 at the end, this is different. Its a folder with lib files in it. I may need to downgrade back to froyo to dbl check but I believe they're in the same place. Deodexed should't make any difference I don't think... thanks for hangin in there, I'd love to get this figured out so others can actually benefit from my aggrivation with it lol
And no, stock browser has no option to disable mobile view.
Sent from my SPH-D700 using XDA App

Updated to latest flash and fixed script file a bit* (gb only)
Sent from my SPH-D700 using XDA App

Just flashed. everything opens and runs. But when show loads it says not supported on this device... Ran the root explorer command and still the same. feels like I'm close. Any ideas? Running ef02 plus
Grapes

Kif420 said:
Just flashed. everything opens and runs. But when show loads it says not supported on this device... Ran the root explorer command and still the same. feels like I'm close. Any ideas? Running ef02 plus
Grapes
Click to expand...
Click to collapse
Double check /data/flash/ exists and has 4 files. Make sure you have installed flash 10.3.185.25 from market and uncheck auto updates. Install busy box installer, and run to install IF and only if it still isn't working at that point.

You are the man! Thought I had busy box installed but.... I didn't.... Installed, ran the script, bam! Hulu! big thanks compuw22c. I owe u a fatty!
Grapes

Thanks! It worked after I rebooted it. Hulu app and Hulu.com working (dolphin in desktop mode)

Awesome! Just glad to hear it finally working for people. I actually just got a gsII but will try to continue posting here as well as we all know the epic needs all the help it can get! btw this should work on any gingerbread its with root (which usually comes with init.d support)

After running this I have a Lego looking block with a ? in it like flash is not installed. Verified in my browser with other flash sites that this is the same. Any Idea as whats going on?

formula84 said:
After running this I have a Lego looking block with a ? in it like flash is not installed. Verified in my browser with other flash sites that this is the same. Any Idea as whats going on?
Click to expand...
Click to collapse
Never mind, it was because i use titanium backup to integrate system app updates into ROM, this saves space...
I had to restore an old backup of.24 then do the market update (did not integrate this time) booted into CWM and flashed worked great.
My only issue now is when i do fullscreen from hulu app its off center, half screen is just white (left) and part of the video is on the right?
Anyway to fix this or maybe an app update?

Its basically just a browser, tap and drag or pinch and zoom. Also, install Dolphin HD, set it to desktop user agent and tap full screen button as on a desktop.
Gone on vacation for two weeks*

I got this working on AA i3 with script manager.
It Does not make Hulu Plus app work.
It does play nicely in default web browser if you change the user agent to desktop. The full screen button works properly as well.
-Roger

[MOD][RECOVERY][2011-08-19] Custom CWM-based 4.0.1.4

This modified recovery is basically a re-compilation of j_r0dd's clockworkmod (CWM) recovery modifications for the Nexus S, with a few minor tweaks. His major changes are the reorganization of the menu items and removal of the multiple "No" entries on the confirmation screens (which are a PITA without a trackball/optical pad like the Inc1 has). You can see the details in his thread here: http://forum.xda-developers.com/showthread.php?t=988686
Additionally, I have added the following tweaks:
- removed "Go Back" from main menu (cosmetic, but it bugged me)
- added "Reboot Bootloader" option to Advanced menu (thx zyonee)
- added "Wipe Everything" option to Wipe menu
Due to popular demand, I have compiled it in a few different colors. If there's a custom one you'd like, PM me with the request.
All zips are flashable via the BOOTLOADER/FASTBOOT -- NOT FROM RECOVERY! Simply copy the file to the root of your sdcard, rename to PG32IMG.zip (just delete the '_version_date_color' part from the filename), then reboot into the bootloader. AGAIN, DO NOT FLASH THESE FROM RECOVERY, IT WON'T WORK. Reboot into the BOOTLOADER (hold VOL-, press Power while turned off), hit Power to select BOOTLOADER, then follow the prompts.
When finished, delete/rename the P32IMG.zip file or next time you boot into the bootloader it will try to flash it again.
MD5 sums:
orange: AF1B547F003A81C4BB167DFEDD0A70C6
cyan: 512D4D8123541E44AE9E8FDBD7890C0A
green: 7CD19F527BC4C3131459EA547B227748
blue: 68B0038520B7CD06285F7FE8E409FD4D
white: B0B7F0E23BE41DF4E3DBF8F9D4A67800
red: C4C276CDD9B0CB054E7109EAD4F44A05
and of course, full source/changes are available at my github here: https://github.com/MattDevo/android_bootable_recovery
** Screenshots**
main menu (cyan)
install menu (cyan)
wipe menu (cyan)
advanced menu (cyan)
main menu (orange)
main menu (green)
main menu (blue)
main menu (white)
**Changelog**
2011-08-19
- added red version
2011-08-04
- added white version
- updated screenshots w/all colors
2011-08-02 (2)
- fixed charging when powered off (resync with CM source)
- edited 'Wipe Everything' menu text for clarity
2011-08-02
- fixed 'Power Off' not working
- added 'Wipe Everything' menu option
- posted screenshots
2011-07-31
- added 'Reboot Bootloader' menu item
- posted additional colors
- zips now flashable in bootloader
2011-07-25
- initial release

So do I just unzip then rename to PG35 or somthing like that n then flash in fastboot
Sent from my ADR6350 using XDA Premium App

great work man!
think you could make a green version for me.
Like a darker forest green, not too dark, just not light either

Looks awesome thank you for this very much.
Sent from my Droid Incredible 2

pol45 said:
So do I just unzip then rename to PG35 or somthing like that n then flash in fastboot
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Any help ?
Sent from my ADR6350 using XDA Premium App

pol45 said:
Any help ?
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
You need to use fastboot.exe on your computer and type something like:
fastboot flash recovery filename.img
-- Sent from my DROID Incredible 2 --

pol45 said:
Any help ?
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Do this :
-Extract it to the root of your sdcard
-Rename it whatever you want
-Go into a terminal app on your phone
-Type these commands:
su (press enter)
flash_image recovery /sdcard/[insert name here].img (press enter)
reboot recovery (press enter)
Sent from my Droid Incredible 2

ruvort said:
Do this :
-Extract it to the root of your sdcard
-Rename it whatever you want
-Go into a terminal app on your phone
-Type these commands:
su (press enter)
flash_image recovery /sdcard/[insert name here].img (press enter)
reboot recovery (press enter)
Sent from my Droid Incredible 2
Click to expand...
Click to collapse
It keeps telling me its not found
Sent from my ADR6350 using XDA Premium App

You're probably not in root of SD card. Just phone root. If you have file explorer or titanium you can see what path you need to CD to to run those commands. Hope this helps.
Sent from my Incredible 2 using Tapatalk

jamesonelam said:
You're probably not in root of SD card. Just phone root. If you have file explorer or titanium you can see what path you need to CD to to run those commands. Hope this helps.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Ok I finally got it but I used a different method that's way easyer I just flashed it threw Rom manager..Thanks anyways
Sent from my ADR6350 using XDA Premium App

put this file on root of SD card. and turn off phone, turn back on by vol down and power, install in hboot.
http://www.multiupload.com/BQRN4NWOCZ

I like the menu but could you make the font blue. I think 4.0.0.4 had it.
-- Sent from my DROID Incredible 2 --

Meltdown03 said:
I like the menu but could you make the font blue. I think 4.0.0.4 had it.
-- Sent from my DROID Incredible 2 --
Click to expand...
Click to collapse
+1, but green first

I'm out of town for the week so won't be able to compile any more til the weekend, but just LMK the RGB value of the color you want and I'll knock them out when I get back (and make them HBOOT flashable too)

+1 Thanks!
This is much better for the DInc2
Its not too bad on my aria with the track ball but using the volume rocker to mover around multiple menus stunk.
wouldn't mind a color like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
R 10
G 214
B 154
C 67%
M 0%
Y 57%
k 0%
#0ad69a

Thanks. The pile of No's was driving me nuts.

Question... Will this fix my problem with my stock backups not restoring? I've tried ver 4.0.0.4 & 4.0.0.8. restores boot ok then script fails when restoring "system" in recovery. Never even gets to data.. Really pissing me off! I backed up with 4.0.0.4 I got from alpharev during s-off method, & backup files are big enough to be full backup but just will not restore... :/
Sent from my Incredible 2 using XDA App

peanut 475 said:
Question... Will this fix my problem with my stock backups not restoring? I've tried ver 4.0.0.4 & 4.0.0.8. restores boot ok then script fails when restoring "system" in recovery. Never even gets to data.. Really pissing me off! I backed up with 4.0.0.4 I got from alpharev during s-off method, & backup files are big enough to be full backup but just will not restore... :/
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
no idea, this is essentially a "nightly" build, and you'd have to look at the commits on github to see if there's been any changes/bugfixes that affect backup/restore. I haven't heard of anyone else having issues with restoring backups made with the AlpharevX-provided CWR 4.0.0.4. though, and I don't have any older backups to test here.

Well I guess I should've clarified..
I backed up stock immediately after rooting, opened rom manager & it said update available. Without thinking I updated. I flashed an unstable beta rom then couldn't restore backup.
Went back to rom manager & downgraded to older recovery that matched one I got from alpharev but I don't know if it's the "same" one. Still no luck, flashed cm7 & everything was fine, restored latest recovery & backedup
Cm7.
Tried to restore stock again, no luck, then couldn't restore cm7 backup? Started from scratch & left it alone.
I just thought with these custom vivow recoveries being made maybe this system is just unstable with others? Sorry to be a pain I'm learning as I go here so eventually I won't be a pain anymore ;D
Sent from my Incredible 2 using XDA App

Answer will prob still be the same just thought I'd throw it out there in case it helps. I really want to understand all this rooting flashing & modding stuff, I'm eager to learn just looking for a little help
Sent from my Incredible 2 using XDA App

[RECOVERY][Xperia S] DooMRecovery (CWM-based recovery){GB}[Rel:v05]{Dt:21/MAY}

------[ UPDATE ]-------
DooMRecovery v05 released! changelog here
------[ UPDATE ]-------
DooMRecovery for Sony Xperia S is based on ClockworkMod recovery source (GB 5.0.2.x).
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(the video is a bit older one from my Xperia Play but gives u an idea how it will work on device)​
[ info ]
firstly i want to thank all the users of this community who donated the device to me! thanks everyone!
so friends i present to u DooMRecovery! its based on CWM 5.0.2.x sources... i have done some additions which i feel makes the recovery a lot smarter... i am still working on the recovery and will be actively maintaining it, so there will be updates as and when i get things working/add new features...
Touch capabilities are added by my teammate (Team UtterChaos) Napstar....
For posting BUGS/issues related to my kernel post them in kernel thread:
http://forum.xda-developers.com/showthread.php?t=1557452
For posting BUGS/issues related to my recovery post them in recovery thread:
http://forum.xda-developers.com/showthread.php?t=1594828
For general discussion regarding my kernel/recovery OR if u want to request for new features, post them in discussion thread:
http://forum.xda-developers.com/showthread.php?t=1596041
RECOVERY IS CURRENTLY AVAILABLE AS PART OF DooMKernel & Advanced Stock Kernel
THE RECOVERY IS STILL WORK IN PROGRESS AND I AM WORKING TO IMPROVE IT!!!
THE RECOVERY IS COMPATIBLE WITH ROM MANAGER!
Start the ROM Manager APP
Click on Menu
Select Manual Flash Override
Click OK at the next prompt
Confirm phone model as "LT26i"
Confirm version as "ClockworkMod 3.x+"
Click OK at the next prompt
thats it ROM Manager is now configured to use this recovery
[ disabled for this device ]
Advanced Menu -> Partition SDcard
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
Napstar - for doing most of the work on Touch capabilities for CWM recovery (not fully implemented it)
Frosty666 for the Vibration triggers
FreeXperia Team (Bin4ry & jerpelea) - for tooo many things!!
[ features ]
added a new menu "More Options"
AROMA File Manager is NOW directly accessible via this new menu
current ROM details can be retrieved via this new menu
fixed some internal sdcard (/emmc) related bugs
fixed advanced backup option
fixed this bug
fixed display of "build timestamp" and battery level
some more changes in font color to make it more readable
replaced background with my old favorite (thanks to Soheil)
implemented detection of internal sdcard as /emmc (if required)
slight changes in font color to make it more readable
now features larger XHDPI fonts (thanks to koush)
replaced the bottom "on-screen navigation buttons" with bigger buttons
fixed SDCARD mounting to PC as mass-storage
now recovery can backup/restore kernels and users can flash kernels (kernel.elf)
FULL TOUCH interface
swipe gesture support!!! - the hotspot for this is across full screen
swipe left to GO BACK/ Scroll UP
swipe right to Scroll Down
Honeycomb themed
haptic feedback
incase the recovery "hangs" or incase some unwanted event starts u can press the POWER button to restart the recovery (the device wont reboot, only recovery will restart)
shows current time (time when the recovery was entered/started)
shows the current battery percentage (CURRENTLY BUGGY)
uses new Roboto FONT (from latest CWM repo)
new "select update.zip menu": it will give u a new option - "show file details" - which will display the size (in bytes) and the MD5SUM of the selected file
when any update.zip is selected its complete file name will now be displayed (right at the top) and full path to that file will be printed before flashing begins
added prompt to display the "backup folder name" when user starts restoring a backup
added a warning and option to abort backup if space on sdcard is < 150 MB
removed Wipe cache partition from main menu (u can format /cache from "Mounts & Storage" menu)
removed those tons of "No"s
add confirmation to "backup" option in Nandroid menu... it used to keep getting pressed by mistake and start making backups immediately... now it will ask u before starting backup
replaced "reboot system now" with new menu "reboot options"... now with this new menu u can:
reboot sytem
reboot into recovery
reboot into fastboot mode
Power Off
added "advanced backup" menu (based on amit.bagaria implementations for his CF-Root kernel for SGS-SL)
now u can selectively choose which partitions to backup
its like a toggle
once u have finished choosing which partitions u want just click on "perform backup" and only those partitions will be backed up!!!
revamped layout for recovery menu (to improve navigation) [renamed few options and changed their order]
changed "wipe data/factory reset" option to just "factory reset", and detailed the partitions which will be wiped
changed text of most menus to fit the new honeycomb inspired design
the Nandroid backups & restore now show/displays which files were used to restore/what the backup is called (folder name)
[ known bugs ]
all backups are done get time stamp of year 1970 dont know why this happens but i am trying to sort it out some how
the recovery sometimes hangs - just press power button it will restart recovery without rebooting device
there are some graphics glitches
backups created with v01 recovery might give errors while restoring using v02 recovery... work around is posted here
if you encounter any other bugs/issues DO LET ME KNOW ASAP by posting them in THIS THREAD
[ requirements ]
UNLOCKED BOOTLOADER
fastboot binaries
[ how to install? ]
The recovery in integrated into the kernel! so when u flash the kernel it will contain the recovery!
[ how to enter recovery? ]
the recovery entry key is VOLUME UP button... so when you see the bootlogo watch out for the following notification which will tell u when u press the entry key (VOL UP):
the LED will turn BLUE
the device will vibrate for short duration
the bottom strip will be illuminated
if u press the entry key within this timeframe of the notifications (3 seconds) the device will enter into recovery
[ how to use recovery? ]
hardware keys
VOL UP/VOL DOWN key to move Up/Down in menu
HOME key to SELECT item
BACK key to GO BACK
OR
On-screen Navigation buttons
OR
Full Touch capibility!
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
ENJOY!!

DooMRecovery v01 released!
details, changelog at first post!!!
DooMRecovery is currently available ONLY as a part of DooMKernel!
please test out and let me know if u have any bugs/issues in THIS THREAD...
for general discussions use the following thread:
http://forum.xda-developers.com/showthread.php?t=1596041

I have just made an very old recovery backup as it says
Current Time:
12:03:27 GMT Mon 23 Feb 1970
but it feels good to have recory backup back again, thanks.

Hi Doom,
One quick question - is it possible to disable vibration in the recovery?

harfot said:
I have just made an very old recovery backup as it says
Current Time:
12:03:27 GMT Mon 23 Feb 1970
but it feels good to have recory backup back again, thanks.
Click to expand...
Click to collapse
ya i know
its like back to the future
kazuni said:
Hi Doom,
One quick question - is it possible to disable vibration in the recovery?
Click to expand...
Click to collapse
nope i have implemented it as a feature so its easier to check if the "touch response" was registered...

@DooMLoRD
Have you considered to get your CWM based recovery actually on CWM ROM Manager?
Auto Installation would be sweet for something like this for allready rooted users. and much easier to update aswell.
Might be a consideration. I would certainly donate for that to happen. ;D

Just flashed this. Runs good, su works as expected, overclocking is good to have, but I'll probably stick to default or even underclock a bit.
Sent from my LT26i using XDA
Edit: wrong thread, derp.

How about make console runs in recovery mode? With console, we can browse and delete apps in recovery!
The OpenRecovery for Motorola Milestone has this feature!
Thank!

juzz|NOR said:
@DooMLoRD
Have you considered to get your CWM based recovery actually on CWM ROM Manager?
Auto Installation would be sweet for something like this for allready rooted users. and much easier to update aswell.
Might be a consideration. I would certainly donate for that to happen. ;D
Click to expand...
Click to collapse
we dont have dedicated recovery partition... so we cant use any app to flash it...
also only officially supported devices get official CWM from ROM Manager (its limited only to releases by Koush)...
K900 said:
Just flashed this. Runs good, su works as expected, overclocking is good to have, but I'll probably stick to default or even underclock a bit.
Sent from my LT26i using XDA
Edit: wrong thread, derp.
Click to expand...
Click to collapse
yes even i underclock to max 1Ghz
keunhuvac said:
How about make console runs in recovery mode? With console, we can browse and delete apps in recovery!
The OpenRecovery for Motorola Milestone has this feature!
Thank!
Click to expand...
Click to collapse
interesting can u share some details?
PLEASE KEEP THIS THREAD FOR REPORTING ISSUES/BUGS
FOR GENERAL DISCUSSION/FEATURE REQUEST USE THIS THREAD

DooMLoRD said:
we dont have dedicated recovery partition... so we cant use any app to flash it...
also only officially supported devices get official CWM from ROM Manager (its limited only to releases by Koush)...
Click to expand...
Click to collapse
Something I came up with the other day: maybe put the recovery fs in a separate file? Then we can change the ramdisk to either load android normally or mount the recovery image like a ramdisk and boot it. This way any kernel (as long as it supports this method) can coexist with any recovery. Also means we could probably use recovery to flash kernels because it runs from RAM so there's no risk of breaking the recovery.
Sent from my Transformer TF101 using XDA

__ delete

K900 said:
Something I came up with the other day: maybe put the recovery fs in a separate file? Then we can change the ramdisk to either load android normally or mount the recovery image like a ramdisk and boot it. This way any kernel (as long as it supports this method) can coexist with any recovery. Also means we could probably use recovery to flash kernels because it runs from RAM so there's no risk of breaking the recovery.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
we already did those things for X10, ARC... point is where will u keep the recovery file? if u keep it on /system then its not a true recovery as formatting /system will remove it... and in case of "bad flash" u will be left with no access to recovery...
so we have done the next best thing... integrated recovery into kernel... we use this for all xperia devices...

If I install the recovery with ROM Manager, also install automatically the Kernel?
Are there any requirements to install it?
Thank you!!

treoking said:
If I install the recovery with ROM Manager, also install automatically the Kernel?
Are there any requirements to install it?
Thank you!!
Click to expand...
Click to collapse
installing recovery from ROM Manager is ONLY supported for devices which have dedicated recovery partition and the ones which officially supported by Koush...
only way to get recovery is to flash kernel containing recovery via fastboot

DooMLoRD said:
we already did those things for X10, ARC... point is where will u keep the recovery file? if u keep it on /system then its not a true recovery as formatting /system will remove it... and in case of "bad flash" u will be left with no access to recovery...
so we have done the next best thing... integrated recovery into kernel... we use this for all xperia devices...
Click to expand...
Click to collapse
The idea is to keep the recovery on /boot, but make it possible to run a custom image from /system.
Sent from my Transformer TF101 using XDA

K900 said:
The idea is to keep the recovery on /boot, but make it possible to run a custom image from /system.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
/boot is the kernel partition, which is not accessible... so essentially its going to be in kernel ramdisk

DooMLoRD said:
/boot is the kernel partition, which is not accessible... so essentially its going to be in kernel ramdisk
Click to expand...
Click to collapse
That's what I meant. I still getting used to the Xperias' internals after three years of HTC/Samsung
Sent from my Transformer TF101 using XDA

K900 said:
That's what I meant. I still getting used to the Xperias' internals after three years of HTC/Samsung
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
hehe...
Xperia are a bit of a pain in the a**...
anyways u all will be happy to know that we can finally flash kernels from recovery/OS to boot partition of this device (Xperia S)...
i have tested and it works well!!

Creating a new file called .hidenandroidprogress in the clockworkmod folder should speed up the nandroid backups eg:
/sdcard/clockworkmod/.hidenandroidprogress
-smc

DooMLoRD said:
hehe...
Xperia are a bit of a pain in the a**...
anyways u all will be happy to know that we can finally flash kernels from recovery/OS to boot partition of this device (Xperia S)...
i have tested and it works well!!
Click to expand...
Click to collapse
Great news Also HTCs can sometimes be even more pain, especially locked ones
Sent from my Transformer TF101 using XDA

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Works with HTC Unlock Method (And s-off methods):
Tested after using htcdev.com's bootloader unlock method.
Please see the guides at the bottom of this post!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directoy, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: International HTC One, T-Mobile HTC One, Sprint HTC One, HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Let me know if there are any issues. Feel free to post the encountered issue and a link to the exact file that was flashed. Thanks for the support!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No.
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using the HTC method and gain root access.
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, wipe data as ROM requires and load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including WiFi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Unlock using the HTC method and gain root access.
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate the kernel zip file is contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

Great!!! Was waiting for it to work with the One
Thanks!!!

great!
(bookmark)

buy it and love it! no pc no more!

this looks awesome. Will this work on unrooted phone (i.e stock rom, stock recovery but unlocked and s off)
reason being i need to flash CWM but away from pc and also as on stock rom, no SU of course :good:

exocetdj said:
this looks awesome. Will this work on unrooted phone (i.e stock rom, stock recovery but unlocked and s off)
reason being i need to flash CWM but away from pc and also as on stock rom, no SU of course :good:
Click to expand...
Click to collapse
I do understand the convenience factor of not having to hassle with all the steps, including a computer, drivers, cables, etc.
Yes, to everything except root access is required by Android in order to have security access to write to the kernel or recovery partitions.
Reviewing the Android security model: if any installed application had access to replace the kernel or recovery without root access, this would seem a bit concerning!
Once root access is setup on the device, Flash Image GUI will allow you to flash custom recoveries and kernels without being at a computer!
Hopefully that makes sense and helps! Thanks for the feedback!

joeykrim said:
I do understand the convenience factor of not having to hassle with all the steps, including a computer, drivers, cables, etc.
Yes, to everything except root access is required by Android in order to have security access to write to the kernel or recovery partitions.
Reviewing the Android security model: if any installed application had access to replace the kernel or recovery without root access, this would seem a bit concerning!
Once root access is setup on the device, Flash Image GUI will allow you to flash custom recoveries and kernels without being at a computer!
Hopefully that makes sense and helps! Thanks for the feedback!
Click to expand...
Click to collapse
Thanks for clearing that up!!!! il make a purchase from the market when I can

exocetdj said:
Thanks for clearing that up!!!! il make a purchase from the market when I can
Click to expand...
Click to collapse
Of course. I do like the thread of thought you were on. Feel free to make any other suggestions or ideas for features and improvements as you use the app. I'm always open to improving and making a better experience!

joeykrim said:
Of course. I do like the thread of thought you were on. Feel free to make any other suggestions or ideas for features and improvements as you use the app. I'm always open to improving and making a better experience!
Click to expand...
Click to collapse
that would be f#cking awesome if possible but would be a pain in teh arse to implement im sure hahaha!!!! il have a play and keep you posted
however this would have helped me out in the past a few time in sticky situations had i heard of this lol

bcmon run?? htc one
HTC One cihazımdan Tapatalk ile gönderildi

Uninstalled Rom, don't have zip on sd. Help!

Ok, so I thought I still had the zip on my device after not being able to recall my gesture pattern lock. I could still access the device by logging into through my google account however I couldn't change the lock itself without doing a system wipe.(To my knowledge)
So now I'm stuck in TWRP with no rom to flash to my device, when I connect my nexus 7 to a notebook (win7) I do not get the MTP connection to drag and drop a rom over.
Everything I seemed to try in the ToolKit as well has been unsuccessful, can someone give me a step by step on how to push,flash,install PAC back onto my device and remove this headache of mine.
Thanks in advance!

DeeSlivers said:
Ok, so I thought I still had the zip on my device after not being able to recall my gesture pattern lock. I could still access the device by logging into through my google account however I couldn't change the lock itself without doing a system wipe.(To my knowledge)
So now I'm stuck in TWRP with no rom to flash to my device, when I connect my nexus 7 to a notebook (win7) I do not get the MTP connection to drag and drop a rom over.
Everything I seemed to try in the ToolKit as well has been unsuccessful, can someone give me a step by step on how to push,flash,install PAC back onto my device and remove this headache of mine.
Thanks in advance!
Click to expand...
Click to collapse
For future reference, I think you can send and email to your google account to reset your gesture lock.
If you want to flash a rom onto your device just use the toolkit. Should find what you need in Advanced utilities.

Where is the advanced utilities in the tool kit? you must have the wording wrong.
Wish I knew about the reset prior to the this mess >.<

DeeSlivers said:
Where is the advanced utilities in the tool kit? you must have the wording wrong.
Wish I knew about the reset prior to the this mess >.<
Click to expand...
Click to collapse
He is referring to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are the 4 items you will need to sideload P.A.C if you don't have them already.
http://goo.gl/QBnwND
http://goo.gl/jG0M9a
http://goo.gl/DEUHBC
http://goo.gl/WvFjl6

TWRP works with adb. Plug it in to your computer with the adb tools installed, run adb devices, you should see it listed. Change to the folder with your ROM zip, do adb push <rom>.zip /sdcard and it'll be on your device. No fuss, no muss.
Sent from my Nexus 7 using Tapatalk 4

This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager.

Username invalid said:
This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager.
Click to expand...
Click to collapse
Thanks I'm wiping the drivers and attempting your method! I'll be back with questions if I have any.:cyclops:

There we go, I had to use a different link in order to download the Minimal ADB And Fastboot Kit.
From there I was able to push the rom onto the device no problem what so ever thanks everyone!

DeeSlivers said:
For some reason the link you provided for ADB and Fastboot doesn't work. My device does show up as a ADB device in the device manager. However I'm still unsure how exactly I push or flash a rom from the notebook to the device itself.
Also his verison of ToolKit isn't what I been using, I have the terminal like green font'd 2013 toolkit by skipsoft is what I have outdated and no longer used or?
Click to expand...
Click to collapse
Yust use this command:
Code:
adb push (your rom file name) /mnt/sdcard/
Then go to flash menu and you will se your rom in your internal sd card

Ok, so I managed to re-flash my rom back on no problems at all. But problem with that is the gesture lock is still active.
Can someone give me a method to remove this from the account?

Try aroma file manager to delete gesture. Key
Sent from my GT-P3100 using xda app-developers app

sukkukikku said:
Try aroma file manager to delete gesture. Key
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Can you further explain this method?

Your device is rooted or not
Sent from my GT-P3100 using xda app-developers app

sukkukikku said:
Your device is rooted or not
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Have you read the thread what so ever..?
Yes the device is rooted, it's running PAC Rom newest Nightly.
The issue is, everytime I load the device I get the gesture lock which I don't have the correct information to. I want to reset the password back to a pattern or pin. Cause as of this point it requires me to login to my google account every time I fail to put the gesture in, meaning unless I have access to the wifi zone my device can't be logged into.

You need to install cwm recovery mode. You need to download aromafm1.80.zip file from net. It will be 1.4 mb. Place the file in external SD card. Go into recovery mode. Mount all partitions in advanced section. Then go to the file in SD card in recovery mode and flash the zip file there. Aroma file manager will open. Then go to data/system/gesture.key and delete that key. And reboot device. Pattern will appear but if you draw any pattern., the device will be unlocked
Sent from my GT-P3100 using xda app-developers app

i kinda get ya ,least ur not stuck in recovery same day buyin the bloody thing. my lil mistake of puttin folder instead of zip into internal storage now has me pullin hair out. why cant u just plug bk into pc and it opens the internal folder up.

sukkukikku said:
You need to install cwm recovery mode. You need to download aromafm1.80.zip file from net. It will be 1.4 mb. Place the file in external SD card. Go into recovery mode. Mount all partitions in advanced section. Then go to the file in SD card in recovery mode and flash the zip file there. Aroma file manager will open. Then go to data/system/gesture.key and delete that key. And reboot device. Pattern will appear but if you draw any pattern., the device will be unlocked
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
You're telling me a several step process to "work around" the issue, instead of actually fixing it which isn't what I been asking.

It will remove the pattern lock
Sent from my GT-P3100 using xda app-developers app