Related
Hi guys!!
NEW UltraJack-Recovery 6.2.2!!Codename:Cappuccino
NO MORE BLUE SCREEN!!!!
Changelog:
FIX: Backup/restore of /cust partition (Bug present in all releases of Ultrajack -up 5.2.2 too- and Clockworkmod too!! )
Added:
mount and umount /cust partition
WIPE /cust
Amend support to CUST partition (Edify is supporting CUST alredy)
Amend/Edify are both supported! (the oldest and newest and future roms can be flashed )
New Base (RA_Recovery 2.2.2!)
FULL EXT4 support (read-write and formatting partition!)
Backup/restore menu (and scripts) updated
Backup/restore google apps
New menù colors
ADB Updated
Kernel sources Modded and compiled to solve an issue on toggle USB function
Download it now!! (6.2.2)(IMG only)
guide and zip file with fastboot binary and scripts here:
http://forum.xda-developers.com/showpost.php?p=11771509&postcount=39
If some1 liked my work and want donate me a beer (or a new micro-SD), there is the link link, or just say tnx
Thanks to:
Me, Myself and I!
Udk ( my best compiler-friend )
Maja (beta tester, and many great ideas! )
Amon_RA(this recovery was based on him RA_Recovery 2.2.1 sources, and many thx about compiling tips!)
JackTheVendicator (without his modded tools the boot.img and recovery wouldn't be possible)
Old versions:
Hi guys there was a problem on some devices with amonra 1.6.2 for the pulse mini.
The BSOD!!!! (windows like)
But now this issue has been SOLVED!!!!
NEW VERSION!!
NO MORE BLUE SCREEN!!!!
Download it now!! (4.6.2)
Changelog:
Fixed SD-MassStorage function
Fixed all Wipes!
Ext2/3/4 support
if some1 liked my work and want donate me a beer (or a new micro-SD), there is the link link
Thanks to:
Me, Myself and I!
Udk ( my best compiler-friend )
Maja (beta tester, and many great ideas! )
Amon_RA(this recovery was based on Amonra pulse mini v1.6.2, and many thx about compiling tips!)
JackTheVendicator (without his modded tools the boot.img and recovery wouldn't be possible)
UltraJack-Recovery_v2.6.1
you are f***ing great!!!
Now is the time for the dedicated section
NVM fastboot install. Nice.
I hope you don't mind but I linked this to the IDEOS group over at www.simply-android.com
THANKS!
What i should do with this .img file?
This recovery won't allow you to do a boot or system wipe. just data/cache and dalvik. If you do the wipes included you can still boot the phone afterwards...that's not a full wipe.
Just FYI.
nobreak1970 said:
This recovery won't allow you to do a boot or system wipe. just data/cache and dalvik. If you do the wipes included you can still boot the phone afterwards...that's not a full wipe.
Just FYI.
Click to expand...
Click to collapse
So are you saying this is just like Googles own recovery?
It wont actually allow you to wipe the phone like AmonRA does?
Then thats useless wouldn't you agree?
@ Ultrakiller
plz plz plzzz somebody teach me how to Flash a custom recovery like the one above for my Ideos U8150-B......
I've been all around the forums and internet ....but nothings working for me ..... im using Windows7 x86 Ult Ed .....
i've even tried 1.6.2-pulsemini-amonrarecovery Instructions for windows ......but still no luck !!!
i Even tried to Flash Image through Terminal .... but for some reason it said " Flash_image not found" .....even though the filename was accurate !!! ........
Kindly Kindly Kindly guide me through the process ..... im so frustrated now .... and im dying to try new ROMS on my Ideos .....
(Also wat ROM u think is better DjDroid's or Sudomod ??????)
Plz Help ASAP !!!!
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
stevenmirabito said:
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
Click to expand...
Click to collapse
well awesome man ....it worked this time .....u ppl are awesome !!!
GOD BLESS !!!
btw what Ideos ROM is Best in your opinion !! ????
Great, I'm glad it worked out for you!
I am currently using the stock ROM, simply because I currently see no reason to install any of the currently available custom ROMs for the Comet. As soon as someone has created a stable port of Cyanogen however, you better believe I'm going to be one of the first people on board!
Sent from my Comet using XDA App
fvckyougooglescammer said:
So are you saying this is just like Googles own recovery?
It wont actually allow you to wipe the phone like AmonRA does?
Then thats useless wouldn't you agree?
Click to expand...
Click to collapse
It has a Wipe option but it only wipes the caches it seems and not the boot and system areas.
stevenmirabito said:
Great, I'm glad it worked out for you!
I am currently using the stock ROM, simply because I currently see no reason to install any of the currently available custom ROMs for the Comet. As soon as someone has created a stable port of Cyanogen however, you better believe I'm going to be one of the first people on board!
Sent from my Comet using XDA App
Click to expand...
Click to collapse
+1
Sent from my Comet using XDA App
Nand + Ext backup doesn't work properly, an error messages with regards to :adb something .
New version done!
First post updated.
Well done!
stevenmirabito said:
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
Click to expand...
Click to collapse
Can this be uninstalled? I need to send mine back so I need to get the phone back to it's original state...
I'm not an expert, but you probably need to find an IMG of the original recovery image and flash it to the phone.
Anyone have it?
Sent from my Comet using XDA App
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, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: HTC One S, EVO 4G LTE, EVO 3D CDMA and GSM, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Nexus 7, Samsung Google Galaxy Nexus (GSM & CDMA), Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Credits for HTC One S Testing:
Special Thanks to: Smokem_I
Tecardo, orenfl and mteezy
Confirmed Compatible Hboot Versions:
1.06, 1.09, 1.13, 1.14 (US and EU), and 2.15 (thx DisruptiveMind)
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
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 kernel /sbin, etc).
Custom Recovery
Supports both CWM and TWRP!
Future Support:
Will continue to test kernels as they are released to ensure compatibility!
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. Use Kernel Manager!
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 Official HTC method
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, 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) 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.
2) Download kernel zip file to /sdcard.
3) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
3) Flash Image GUI will validate the kernel zip file is contains the minimum required files
4) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
5) Reboot
Basic Troubleshooting:
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 (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot 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.
Glad to see you post it for everyone to try. Always loved this apk.
Just to show working on one s
Sent from my HTC One S using Tapatalk 2
Thanks mate looks like a handy tool. Salt I had no time to help test this, would have loved to. seems you have gotten it to work decently now. Very good. Thanks a lot!
sent from a bugged One s....
Awesome bro! It's great to finally be able to flash a rom on the go without the need of fastboot! Flashed several roms with this so far and haven't had any issues. We were in desperate need of something like this! Thanks for taking the time to add support for our device!
Sent from my BluMagic Viper One S using Tapatalk 2
Can't say thank you enough! Works like a dream, hell you even put a smile on my miserable old face
So once we know that the ketnal is supported by a Rom we can just flash away once its unlocked and rioted obviously
New favourite app lol good job on this.
snwman said:
So once we know that the ketnal is supported by a Rom we can just flash away once its unlocked and rioted obviously
Click to expand...
Click to collapse
It supports all roms available for the One S. The Viper Beta Team tested it extensively before release. We didn't encounter any issues or roms that weren't compatible. Also don't forget to hit joeykrim's thanks button or better yet show him support by buying from the Play Store
Darknites said:
New favourite app lol good job on this.
Click to expand...
Click to collapse
Soon to be everyone's favorite app once they find it! This is the must have app for the One S.
Sent from my BluMagic Viper One S using Tapatalk 2
Smokem_I said:
It supports all roms available for the One S. The Viper Beta Team tested it extensively before release. We didn't encounter any issues or roms that weren't compatible. Also don't forget to hit joeykrim's thanks button or better yet show him support by buying from the Play Store
Soon to be everyone's favorite app once they find it! This is the must have app for the One S.
Sent from my BluMagic Viper One S using Tapatalk 2
Click to expand...
Click to collapse
I think if it states on the title 'for ALL hboot versions' or something similar it may help attract people. I can't understand how this is staying so quiet! I've been flashing boot.img using this app from stock roms to asop and different recovery version like there was no tomorrow. Its just all so easy off to buy the market version now to show the dev some love.
This won't stay quiet for long. Once more users realize they don't have to use fast boot to flash kernels or use a workaround like htc dumlock which takes alot more work. They will all be using this. Its a must have app for any device that does not have s-off this app was a lifesaver for me on my evo 3d. Even once it got s-off I still used regularly to flash kernels on the fly. I have low hboot but still been using this for the past couple weeks since we started testing. All I have to say for those that don't know is NO MORE FASTBOOT!
Sent from my HTC One S using Tapatalk 2
If you have any feature suggestions, please let me know! Appreciate all the positive support!
shadowch31 said:
I think if it states on the title 'for ALL hboot versions' or something similar it may help attract people. I can't understand how this is staying so quiet! I've been flashing boot.img using this app from stock roms to asop and different recovery version like there was no tomorrow. Its just all so easy off to buy the market version now to show the dev some love.
Click to expand...
Click to collapse
Good comments. I listed in the OP and copied below for convenience, which hboot versions were confirmed. If I'm missing any hboot versions, please let me know.
Confirmed Compatible Hboot Versions:
joeykrim said:
1.06, 1.09, 1.13, 1.14 (US and EU)
Click to expand...
Click to collapse
This is directed to anybody/everybody, in regards to methods that can spread the news, it might be worthwhile to write up a simple guide post explaining the steps, very similar to what I have in the OP.
Another method would be to reach out to the ROM/kernel developers and ask them to link back to this thread, or a guide thread, on the various methods to load their software including using this application as one of the methods.
Just throwing out ideas! Appreciate all the help and support!
snwman said:
So once we know that the ketnal is supported by a Rom we can just flash away once its unlocked and rioted obviously
Click to expand...
Click to collapse
If you refer to the last section of the OP with the guides, they explain step-by-step process that answer your question. I've pasted below for your convenience. Thanks for the support!
joeykrim said:
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using Official HTC method
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, 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) 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.
2) Download kernel zip file to /sdcard.
3) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
3) Flash Image GUI will validate the kernel zip file is contains the minimum required files
4) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
5) Reboot
Click to expand...
Click to collapse
Get the rom devs to put the info in there threads should help out a bit.
Edit, dam it didnt see there was a 2nd page seem you have that idea already.
Hi there , let me understand if for example i want to change the rom ? Right now i am on aokp , if i download the kernel from viper 1.2.0 and flash it and then after reboot i will remain on twrp and flash his 1.2.0 rom will WORK?
I kind of tired of using computer to change roms and kernels etc ...
Ps : i wanted to sell my phone becouse of this (i really mis my old sgs/sgs2 method to flash roms/radios/kernels)
Good work
Sent from my HTC One S using Tapatalk 2
scufutz said:
Hi there , let me understand if for example i want to change the rom ? Right now i am on aokp , if i download the kernel from viper 1.2.0 and flash it and then after reboot i will remain on twrp and flash his 1.2.0 rom will WORK?
I kind of tired of using computer to change roms and kernels etc ...
Ps : i wanted to sell my phone becouse of this (i really mis my old sgs/sgs2 method to flash roms/radios/kernels)
Good work
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Even easier than that.
Simply download the rom and direct the program to it on your sdcard it will then extract the boot.img and any other files it may need such as wlan.ko - flash the kernel and an option to boot normally or boot to recovery is offered, boot to recovery and flash the rom and hey presto. Who needs s-off when we have this method!
Yes I know S-Off would be nice for other things but for now this is by far the lesser of two evils.
I was thinking is it possible to have it just point to the boot.img file so that i can still delete it from the rom zip to speed up install of the rom? Which takes over 5 mins if it has it.
Darknites said:
I was thinking is it possible to have it just point to the boot.img file so that i can still delete it from the rom zip to speed up install of the rom? Which takes over 5 mins if it has it.
Click to expand...
Click to collapse
Well it does that? Maybe I'm not understanding but you select the rom and it extracts the needed files and flashes them, then simply remove the boot.img from the zip and flash it to see if it works. Never tried flashing a rom without the boot.img so cannot say.
IMO removing the boot image isn't gonna cut off any time. In the long run u spent more time navigating through your file manger to go and delete it than it would for it to just flash. Were talking a matter or seconds in recovery. That's just my thoughts though do as you please.
Sent from my HTC One S using Tapatalk 2
mteezey said:
IMO removing the boot image isn't gonna cut off any time. In the long run u spent more time navigating through your file manger to go and delete it than it would for it to just flash. Were talking a matter or seconds in recovery. That's just my thoughts though do as you please.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Em its takes me over 5 minutes to flash a rom with the boot.img in the zip but if i remove the boot.img its less then a minute. With that in mind i would like to remove the boot.img from the zip and then when i copy the rom to sd i copy over boot.img as well.
Why is the HTC One S not listed in supported devices if its posted in HTC One S Apps & Themes?
I love you! This is great! Going to test it soon, next time I need to flash my rom.
We need to make you App look sexy as well!
Sent from my HTC One S using xda app-developers app
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus One P500 (p500)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/p500
Click to expand...
Click to collapse
XDA:DevDB Information
[p500][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the LG Optimus One P500
Contributors
Phil3759
Version Information
Status: Testing
Created 2014-04-21
Last Updated 2014-04-21
Cool.
Upon which CWM version is this based? Note fundamental differences between newer 6.0.* after June 16 -- can flash new Kitkat ROMs and older 5.* which flash older ROMs.
Because of space limitations -- whole business must fit < 5 meg, functionality such as partitioning SDcard was removed from the 6.0.* versions.
What do we have in this version?
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
ujilraj said:
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
Click to expand...
Click to collapse
If you can't read OP and follow links, just do not test
I am fine with this
Unable to flash!
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
I suggest that the first link needs to highlighted... My mistake, but honestly i didn't notice a link below the title...
sumansur2008 said:
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
Click to expand...
Click to collapse
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Dovidhalevi said:
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Click to expand...
Click to collapse
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
indigobv said:
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image
Click to expand...
Click to collapse
This should be the error. Then flash_image the 6.0.4.6 which fits. Do it immediately or else .... I believe I had that happen once. I posted about that 5meg limit above. Did not try this because of the limit.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
Click to expand...
Click to collapse
Maybe the op should post a proper flashable zip instead. Problem is that status 7 itself might mean a brick.
Dovidhalevi said:
Problem is that status 7 itself might mean a brick.
Click to expand...
Click to collapse
Thanks for the heads up, I actually didn't try booting in recovery after the status 7 error. Now I can confirm that it tries to flash it even if it shows the error and then forces the phone to go in fastboot mode until the problem is solved.
I built using official p500 armv6 repo
They should fix the device recovery size in that case!!
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
eran32 said:
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
Click to expand...
Click to collapse
I believe this is simple a nice GUI for flash_image. Aint no such thing as no risk so beware.
The method I suggested should be safe if one flash_image's a valid recovery immediately after any error (but I make no guarantee!).
I advise against flashing this recovery version at this point because it is clearly too big for our device. We can get along just fine without a touch interface if need be. Never had one.
Changing board partition sizes is not a readily done simple matter by any means.
TWRP Recovery
For Galaxy Fit
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: Hosting & for providing Compatible flags
Me: Compiling
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.mediafire.com/view/?xum64uit9a43q6s
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
About the current build:
STABLE.
Reboot to system bug now fixed.
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
TpupLpasa said:
One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works.
Click to expand...
Click to collapse
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
1st - install PhilZ Touch Recovery 6.40.1.
2nd - install twrp.
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Ok, thanks.
update
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
I would advise against this. I tried it and it soft bricked my phone.
I will wait for the official release, which I hope will be soon. I really like TWRP.
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
iSanechek said:
Ok, thanks.
update
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Click to expand...
Click to collapse
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: remooved
belyava said:
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: http://yadi.sk/d/IAr6Z_OvQohqq
Click to expand...
Click to collapse
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
No success I am afraid.
jemail
Click to expand...
Click to collapse
sorry, I must have made a mistake. I''ll check tomorrow. Sorry for the inconvenience
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
Click to expand...
Click to collapse
Ok, try this one
belyava said:
Ok, try this one
Click to expand...
Click to collapse
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
jemail said:
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
Click to expand...
Click to collapse
There are a lot of method nowadays for unpack-repack and most of them fails to make a proper repack, so you'll have booting problems like you had when you tried to do it yourself. I just told @belyava to do unpack-repack because he did this with the recovery (TWRP - had same reboot to system issue) of his device successfully. Thanks @belyava for this help.
Everything expected to work. However, you can always report bugs with a proper recovery logfile.
Updated download link with a new mediafire link. The latest build can be now labelled as STABLE build.
hi anyone have got it if possible in rar zip for this recovery.
ahmetakin said:
hi anyone have got it if possible in rar zip for this recovery.
Click to expand...
Click to collapse
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
swat4samp said:
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
Click to expand...
Click to collapse
I can't speak for your ROM, but for me back up ( 3 1/2 mins max) and restore (3 1/2 mins max).
jemail
Ok yesterdeay install with terminal emulator thanks.
Code:
[CENTER][COLOR="Red"]Your warranty is now void.[/COLOR]
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research before asking help and reporting bugs and please read the entire OP.
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.[/CENTER]
All suggestions and helps are welcome here so please help me in improving this thread by suggesting your ideas.
This guide will work for any SPRD phone (any SPRD chip) from Old versions of android to latest Oreo but recoveries that I provided in this thread will work for devices from KitKat to Marshmallow no guarantees for older or newer versions.
Buckup! Backup! Backup!
Before modifying system it's highly recommended to have full dump of your device. So don't forget to take backup.
It's simple to get custom recovery for rooted users as they can directly backup, modify and flash recovery or boot images on the go with the help of root. But non-rooted users need to do some extra which will be explained later. Follow the below steps:
=>Download and setup AIK (Android Image Kitchen)
=>Grab your stock_recovery.img
For rooted usersInstall Flashify, Rashr, Partitions Backup or like apps (available on play store for free) and backup the stock recovery. If you are using Flashify to backup you have to rename the backed up image with .img extention
For non-rooted usersDownload your stock firmware which will be in .pac extension extract it using this guide and copy the recovery.img
=>Now download custom recovery (for downloads see 2nd post)
=>Port recovery
For PC version of AIK
• Extract the AIK on desktop in a folder (extracting inside other folder(s) is not recommended)
• Place stock_recovery.img (use the name recovery.img only I added stock to refer the image) in earlier extracted folder
• Now double click on 'unpacking.bat'
• Now you'll see two folders 'ramdisk (mostly executables)' and 'split-img (kernel to boot recovery) rename those folders like this 'ramdisk.s' and 'split_img.s' (renaming is used to avoid copying/moving needed files)
• Now delete the earlier pasted stock_recovery.img and paste custom_recovery.img (rename it to recovery.img)
• Unpack it just like stock_recovery
• Delete the split-img and rename the 'split_img.s' to split_img
• Open recovery.fstab from /ramdisk.s/etc (stock recovery's fstab) and /ramdisk/etc (custom recovery's fstab) using Notepad++ or with your favorite note editor. In case of TWRP recovery this file will be named as twrp.fstab if there is recovery. fstab you can ignore it.
• Edit the partition names and mount points in custom recovery with your stock recovery's fstab. But in most cases the mount points will be shown like this 'mmclbk0p17 for system partition' in that case you need to change custom recovery.fstab with the mount points of your device, to find out mount points of partitions install Diskinfo from play store and enable all options in it which will show complete information regarding each and every partition on your device
• At last double click on 'repackimg.bat' now you'll see 'image-new.img' which is ported custom_recovery.img for your device
• The final step is flashing the recovery. It's easy for rooted users simply use Flashify app to flash. For non-Root users you need to flash it over fastboot mode for this look at this thread.
For mobile version of AIK
You can also port the recovery on-the-go using AIK-Mobile unfortunately to use this needs your device must be rooted with BusyBox (Stephen (stericson) is recommended) installed.
It's a flashable zip but you can extract the zip and place the files manually. Follow below steps for setup:
• Extract the AIK-Mobile.zip
• Paste the AIK-Mobile folder under data/local of extracted zip to /data/local
• Paste files under /bin of extracted zip to /data/local/AIK-Mobile/bin
• Make sure all files including folders are having these permissions "-rwrx-xr-x-".
For placing files, changing permissions and executing scripts 'Explorer' by speed software is recommended.
For porting follow above steps (steps in PC version of AIK) the only difference here is .bat files of PC version will be as .sh in mobile version which are to be executed as root for unpacking and repackaging images.
Note:Follow the instructions properly, don't quote entire OP while asking for help. Due to some touch related drivers missing in kernel of recovery in some devices touch recovery won't work in that case please use Non-Touch recovery. In lollipop or later versions don't flash <3.x.x versions which may result in SD card mounting issues and even flashing errors. First test the recovery that you ported by flash a simple mode (I prefer AIK-Mobile since it doesn't modify the system partition hence there is not chance of bootloop. Also see whether wipe options works properly or not in some devices wiping (even cache) takes ~10m in that case goto settings check the option "use rm -rf instead of formatting".
Hit thanks button instead of posting thanks it'll boost me to create more threads like this.
Credits:
Advan S4P [Official] (fb group), SuDroid Tech (fb group), @@ki , @Jitheshwar (it's me), and some aliens from other universe.
Created: 27-09-2017
Last Updated: 27-09-2017
Custom recovery downloads
1) TWRP recovery images
2.7.0-0
2.8.5-0
2.8.5-0
3.0.0-0
3.0.2-0
3.0.2-0
3.0.2-0
3.1.1-0
2)Cyanogen recovery (for lollipop)
3)Cyanogen recovery (for kikat)
4)MIUI recovery
5)Ultra CWM
6)Temporary CWM (only for KitKat and older
7)Temporary Philz (only for KitKat and older)
Temporary recoveries provided here are not for porting. You can flash those zips directly from you stock recovery these recoveries will have basic functions like flashing ROMs, Wiping (in some devices it'll take too long to wipe so just use factory reset option of stock recovery and then flash this recovery finally the ROM. Back up option of recovery might not be fully functional. Scrolling is glitchy but it'll work when you press button. These are more for users who are unable get working recovery
Reserved for FAQ.
Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp
Jitheshwar said:
Click to expand...
Click to collapse
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??
Jitheshwar said:
..
Click to expand...
Click to collapse
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?
HemanthJabalpuri said:
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?
Click to expand...
Click to collapse
Read again carefully you have to pack custom recoveries ramdisk with stock split_img and reversing the process will mess up the recovery and then you have to flash the stock recovery. So read the guide carefully step-by-step and follow the process exactly unless you know different working method.
unknown said:
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??
Click to expand...
Click to collapse
Give it a try it may work. But none of the recoveries that are provided here will work for your device, you need to find Android 7.0 and later recoveries which will be compatible with your chipset model.
kaew158 said:
Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp
Click to expand...
Click to collapse
TWRP has nothing to do with boot.img. If you are not able to boot to recovery try different key combination. Is you messed up recovery too then flash it via fastboot and then flash the stock Rom.
Jitheshwar said:
Click to expand...
Click to collapse
Sir finally the process is to pack
⇛split_img of stock recovery ......
⇛ramdisk of custom recovery you listed by replacing recovery.fstab file
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....
HemanthJabalpuri said:
Sir finally the process is to pack
⇛ramdisk of recovery you listed by replacing recovery.fstab file
⇛spit_img of stock recovery right......
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....
Click to expand...
Click to collapse
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.
Jitheshwar said:
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.
Click to expand...
Click to collapse
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore
HemanthJabalpuri said:
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore
Click to expand...
Click to collapse
I clearly stated all the steps in an easy and simple way. My kind request to you to read the post again. And one more thing if you want to use apk version use it I don't have any issues but don't ask me if anything goes wrong.
i ported twrp 3.2.1 to sc8830 sucessfully but touch is not working , can you help?
where can i find non-touch recovery
I'm using android 5.1
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones
Please fix the twrp links!!!
@Vortex said:
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones
Click to expand...
Click to collapse
No custom recovery will work on bootloader locked devices...
denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
Kernel architecture is ARM.