Related
[ Description ]
This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
[ Features ]
Detailed description of every menu item
[ Known Issues ]
v2.3.3 has some screen tearing/color weirdness going on. This is just a graphical bug in the recovery kernel, nothing to worry about. I'll try to fix it in a next version.
[ Download ] - ALWAYS check the md5sum to make sure the file isn't corrupted!
recovery-RA-supersonic-v2.3.img - MD5Sum: c00243750cc79e4a1dd4888db175b19f
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Mirror to all my recoveries (Click a few adds to keep it up and running - Thanks DrMacinyasha ^^)
[ Install ] - There are several ways to install a custom recovery, feel free to pick the one that suits you best :
- the Bootloader way - - Thanks Tiffany84 ^^
Place PC36IMG.zip on the root of your sd card.
Boot the phone into the bootloader by powering the phone down, then press the power and the volume down buttons at the same time.
Once the phone boots into the bootloader the phone will automatically recognize the zip file. It will ask if you would like to update, select yes and let it do it's thing and you will be good to go
- via Rom Manager - - STILL NEEDS TO UPDATED TO v2.3!!
Download "Rom Manager" from the Android market
Start "Rom Manager"
Select "Flash ClockworkMod Recovery" and wait for it to finish
Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.
- via terminal app or adb - (Make sure your rom contains flash_image!!)
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
[ Important notes ]
Don't restore wimax nandroids between different phones! If you still plan to do it make sure to remove the wimax image from the nandroid backup before restoring!!
I'll only answer to posts with a real problem description and a pastebin log. All other "issues" will be skipped/ignored.
Make sure have enough free space available on your sdcard when making a nandroid backup!!
Always check recovery.log before posting your issues!
You can do this by doing :
"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.
[ Special Thanks ]
http://www.androidspin.com for hosting ^^
Tiffany84 for the PC36IMG's ^^
DrMacinyasha for the mirror ^^
jhansche for the initial port of the evo recovery and his menu navigation and verification code.
joncfoo for the menu loop code.
toastcfh for testing and all his awesome work on the Evo (root, unlocked nand, ..) Thanks ^^ Buy him a coffee!!
flipzmode for testing, screenshots and feedback, Thanks ^^
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for his awesome work on recoveries and ROM manager ^^
Cyanogen for his dedicated work! , buy him a beer!
Chris Soyars for the new Apps2SD method ^^
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
rikupw for the ideas and toggle_ums script.
Change-log
v2.3
Nandroid will skip sd-ext backup when it's not present.
Nandroid will not check the battery percentage anymore.
Switched off signature check by default (Stop asking now, ok?).
Cache is not selected as part of a default Nandroid backup anymore.
Added wipe Boot, System and sdcard to the wipe menu.
Re-ordered some items in the wipe menu.
Switched to a CM android-msm-2.6.35-unified kernel (should stop the endless dots).
v2.2.1
Fixed Nandroid ext backup/restore. It now backups/restore the entire ext.
v2.2
Nandroid backup is now selective, boot/system/cache/data are selected by default.
Nandroid checks if there's at least 500MB free on SDcard before starting a backup.
Kernel min freq is set to max freq to speed up things (tip of toastcfh).
Added/updated error/warning messages.
v2.1.1
Updated kernel to 2.6.32.17 , this should fix the partition issues on newer hboots
Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms.
Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu.
Re-ordered the wipe menu.
Added SDEXT support for update scripts.
Added "filebrowser" support when you select a zip to flash.
Added "/.." support to the filebrowser so you can navigate up.
Added a mount menu so you can manually (u)mount stuff.
Added a toggle verification switch so you can flash those awesome unsigned winrar rom releases...
Fully re-wrote the wipe menu (it's not using a script anymore), added a few new wipe options.
Added "/sdcard/.android_secure" support , nandroid now backups/restores .android_secure (Froyo a2sd apps) by default.
Added a few new Google apps to the Google app backup script.
v1.8.0
updated Nandroid so it also backups and restores the wimax partition.
made the recovery 400kb smaller so it fits most recovery partitions with bad blocks.
added a return option (instead of pressing vol-up+down) to the menu (by jhansche).
completely ignore verification (by jhansche).
added menu loop (by joncfoo).
v1.7.0.2
Reduced the overall size so it can still be flashed when having lots of bad blocks.
v1.7.0.1
Initial release (port from my Nexus One recovery)
awesome I was waiting for this i was tired of having to go home to change roms!
Nice, i'm going to try this out right now and report back if there are any problems.
It works nicely. I don't like having to press both volume-keys to go back to the previous menu, but it's not a deal breaker. Good job Amon_RA. =]
trying to flash the image its telling me not found when i tried every which way to flash it any ideas? Ugh sorry maybe i need to read...a little more next time sorry!
Arthur101 said:
trying to flash the image its telling me not found when i tried every which way to flash it any ideas? Ugh sorry maybe i need to read...a little more next time sorry!
Click to expand...
Click to collapse
How are you flashing it? the fastboot method worked fine for me
Edit:
1) Get fastboot.exe here
2) Place recovery-RA-evo-v1.7.0.1.img in the same dir as fastboot
3) boot your phone into fastboot (Volume Dwn+ Power) Select fast boot
Then follow
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.7.0.1.img(press enter)
I keep getting a error opening /sdcard/recovery-RA.img no such file or directory.
Fixter said:
I keep getting a error opening /sdcard/recovery-RA.img no such file or directory.
Click to expand...
Click to collapse
It's recovery-RA-evo-v1.7.0.1.img , not recovery-RA.img ...
Amon_RA said:
It's recovery-RA-evo-v1.7.0.1.img , not recovery-RA.img ...
Click to expand...
Click to collapse
I got the error with both names. I renamed the file to see if I was making mistakes with the file name since it was so long.
Hey, Ra, you do realize we ARE going to need Care Bears on our Evo recoveries just like you spoiled us with on our MT3G's... I'm just saying!
I've tried downloading the file a couple of times to make sure it wasn't corrupted but I keep getting "sending 'recovery' (5032 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)"
Also thanks for the new recovery, was hoping you'd release one for our Evo's
And I know I have flash_image because I did Toasts Nand Unlock yesterday. And I checked and the file is on the root of the SD Card.
Fixter said:
And I know I have flash_image because I did Toasts Nand Unlock yesterday. And I checked and the file is on the root of the SD Card.
Click to expand...
Click to collapse
it should be in /data
once you restore a rom that didn't have it, it's no longer on the phone where it should be. if you put it back in /data and chmod 755 it you should have no problem.
Cordy said:
it should be in /data
once you restore a rom that didn't have it, it's no longer on the phone where it should be. if you put it back in /data and chmod 755 it you should have no problem.
Click to expand...
Click to collapse
Yup. I just did. I was thinking about this and went ahead. Thanks for the information though.
PS: I get a Build Not Set on the End of the Recovery.
Amon_RA said:
Features
Fix apk uid mismatches :: Does extacly that
Click to expand...
Click to collapse
thanks for this great recovery! im excited to try it!
two quick questions:
does the fix apk uid mismatches uses the common fix_permissions.sh script?
do you have a github or location where the source code is viewable?
thanks again!
Fixter said:
I got the error with both names. I renamed the file to see if I was making mistakes with the file name since it was so long.
Click to expand...
Click to collapse
How are you flashing? Fastboot, flash_image? Are you sure you mounted /sdcard? Do an "ls /sdcard/recovery*" to make sure the sdcard is mounted and that the recovery image can be found.
Cordy said:
I've tried downloading the file a couple of times to make sure it wasn't corrupted but I keep getting "sending 'recovery' (5032 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)"
Click to expand...
Click to collapse
Did you unlock NAND?
joeykrim said:
thanks for this great recovery! im excited to try it!
two quick questions:
does the fix apk uid mismatches uses the common fix_permissions.sh script?
do you have a github or location where the source code is viewable?
thanks again!
Click to expand...
Click to collapse
Erm, I'm using the same fix_permissions.sh script as in my other recoveries, check github :
Scripts : http://github.com/packetlss/amonra_recovery_scripts
Recovery : http://github.com/packetlss/amonra_bootable_recovery
Still need to push the evo recovery.
Amon_RA said:
Did you unlock NAND?
Click to expand...
Click to collapse
Yes, I'm able to flash toasts recovery.img through fastboot no problem.
How do I check if I loaded the recovery correct? I get a Build : Not Set when I entered the recovery on the lower end where its suppose to say the build number.
You should work together with Koush and make one great recovery. He has some features such as the ability to flash a zip from ANYWHERE on the SD Card. The two of you should be able to work some miracles.
Ceger
this was a work-in-progress development project for porting CyanogenMod 9 (ICS/4.0.4) and ClockworkMod Recovery 5 to Allwinner A10 devices.
but my CM9 is obsolete now. if you want to get CM9, please refer other active projects.
currently here is only for my miscellaneous work for Allwinner A10 devices. if you have a question about development work for A10, you may post it on here. but I can't guarantee any answer.
* links to other active CM9/CM10 projects
http://forum.xda-developers.com/showthread.php?t=1821398 CM10 for many A10 tablets by Christian Troy
http://forum.xda-developers.com/showthread.php?t=1760929 CM9 for many A10 tablets by Christian Troy
http://www.slatedroid.com/topic/33820-ics-404-ivi-cm9-firmware-for-novo7-advanced-btgpsusb-audio/ for NOVO7 Advanced(1) by tsynik
* links to other active AOKP projects
http://forum.xda-developers.com/showthread.php?t=1760931 for many A10 tablets by Christian Troy
* How to install ClockworkMod Recovery 5
1. (if you don't have official ROM and flash tool,) make backup of recovery partition
2. download recovery.zip and unzip it
3. put install-recovery.sh and recovery.img(recovery.cpio for GB ROM) on /sdcard/ *1 *2
4. run install-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/install-recovery.sh
* How to boot recovery
1. put reboot-recovery.sh on /sdcard/ *1 *2
2. run reboot-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/reboot-recovery.sh
*1 if you are using CM9, install-recovery.sh and reboot-recovery.sh are already installed on /system/bin/. if you are not using CM9, you can put these scripts on your ROM.
*2 /sdcard/ is referred as "SD card" on Android, but it may not be physical/external "SD Card". please make sure files are placed on /sdcard/.
* How to boot recovery (alternative)
for ainol NOVO7 AdvancedII/Aurora/Elf
BACK + POWER
for other tablets, please find the way to boot recovery.
* How to control ClockworkMod Recovery 5
for ainol NOVO7 Advanced
VOL-: down, VOL+: up, POWER/MENU: select, BACK: back
for ainol NOVO7 AdvancedII/Aurora/Elf
VOL-/MENU: down, VOL+/HOME: up, POWER: select, BACK: back
* How to install CyanogenMod 9
1. download update.zip and put it on internal NAND flash or SD card (don't unzip it)
2. install ClockworkMod Recovery 5
3. reboot recovery
4. install update.zip
5. wipe data/factory reset *3
6. reboot
*3 only if you are upgrading from non-CM9 ROM (CM9 1st install)
reserved
reserved
Hi,
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
T
saulmrt said:
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
Click to expand...
Click to collapse
thank you for your message.
but I don't recommend to buy it because of my CM, unless you like/want to do porting work. my CM is not perfect at all.
I ordered it because I thin it is a good piece of hardware, you don't have to be afraid that it was only because of this port.
Well as soon as I have this tablet I will try to help with porting as good as I can.
Great work so far OP!
I have the Ainol Advanced waiting for me at the post office. There's already a healthy community over on slatedroid but it's always good to see CM getting ported!
thank you for your comments.
I wish I'll re-upload my files in this weekend...(it's not technical reason at all)
FILES! FILES!! My Kingdom for FILES!!!
i have been longing for it and i suggest to launch a new board for it. it's been a popular device in PRC, taiwan & hong kong already! please note that the 2.0.3 & 2.0.4 firmwares are quite buggy, and i would advise all to flash 1.8 modified version which is stable and can score 18XX at quadrant.
I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.
FezzFest said:
I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.
Click to expand...
Click to collapse
sorry, I need some time to prepare my site. it seems I don't have enough time on this weekend but I hope I'll get some time on next week.
I guess you are talking about this tool: http://www.mp4nation.net/forum/viewtopic.php?f=24&t=20476
I'll try it when I get enough time
and thank you for your information. if you want to add your tablet to my support list, I need more detail info (please see post#4). if you can do it yourself, please just wait for some day... I'll uploaded my git repo too.
(nothing is secret, just I need my free time!)
I found it on a different website, but I think it's the same tool.
This is a dump I made of the original partitions with dd:
boot.img: http://dl.dropbox.com/u/28680222/XDA/tablet/boot.img
misc.img: http://dl.dropbox.com/u/28680222/XDA/tablet/misc.img
rootfs.img: http://dl.dropbox.com/u/28680222/XDA/tablet/rootfs.img
recovery.img: http://dl.dropbox.com/u/28680222/XDA/tablet/recovery.img
system.img: http://dl.dropbox.com/u/28680222/XDA/tablet/system.img
I haven't included cache, data and internal sdcard because I don't think they are of any use for ROM development.
Edit: attached required output from commands in post #4. Find /sys doesn't work because adb can't find find
Hi fun thanks for the pm found my way here at last
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
cheers
Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working
Mitred said:
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
Click to expand...
Click to collapse
hi.
stock recovery should work because it's necessary to run "factory reset" from setting menu on stock rom. (it's done automatically so we can't use it to enter recovery mode. I just explained about functionality)
and recovery is not necessary for now. what I need is not complete dump image. I just want to know hardware related things so tar archive is enough.
permanent root is not necessary too. sometimes rooting app makes brick, so I don't recommend it. I don't recommend to modify stock rom unless you have official rom and flash tool.
if adb shell is root shell, then rooting is not necessary at all. if adb shell is not running, or non-root user shell, temporary root is necessary to get root shell.
then, you already got root shell, right?
then, please check following commands are available in your rom, "tar" and/or "busybox".
FezzFest said:
Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working
Click to expand...
Click to collapse
"adb recovery" doesn't work. I'll post how to enter recovery. please wait for a moment.
anyway, please tell me name of your tablet, or link to web, or photo.
if busybox is in your rom, "busybox find /sys" will work.
It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.
FezzFest said:
It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.
Click to expand...
Click to collapse
i'm guessing you are referring to the Bmorn V11 rebranded for Promedia ?
If so, keep in mind that there are 2 versions of this tablet, one with 3600 battery and one with 3200 battery, the 3200 version has the goodix_touch drivers.
The script is now completely rewritten and a lot easier to use.
This is the general walkthrough for this script, if you have more questions than this answers please ask in this thread.
Download and unpack the script to the root of your sdcard, the easiest way to do this is to download it to the root of the sdcard and do the following:
1. start terminal session
2. cd /sdcard
3. tar xvf MakeLoopROM-Android-V11.tar
===============================================================================================================================
NEW! READ THIS! - The original ROMs and Packages are now stored in /sdcard/MakeLoopROM/original-roms and /sdcard/MakeLoopROM/original-packages. Copy the ROMs and packages
that you want to convert into those folders!
===============================================================================================================================
Ok, once you're done there you're ready to start the script, it's now completely menu driven.
1. start terminal session
2. cd /sdcard/MakeLoopROM
3. sh startup
That will start up the menu, for a new ROM work your way from 1 - 4 to make your first loop ROM, at the end of 4 it will be ready for installation, for upgrades that install into
existing loop files (that you have made once with step 1) start at step 2.
The menu options and how they work:
1. Make system, data or both loop files
This option will allow you to do just what it says, make the system and data images you'll install your ROM into, it's very
straightforward but i'll give a brief summary of how
it works.
"Do you want to make an image file to hold the system for this ROM? (not neccessary if it's an upgrade from a previous ROM) Y
for yes N for no."
Pretty straightforward, if you don't have a system loop file enter y for yes, if you're going to upgrade then running this
step is completely unneccessary but since you have
chosen to run it, press no.
"What do you want to call your system image? (give it a name you'll remember, like cm-7-system for a cm-7 loop install)"
Name the system loop file, call it whatever you want but make it something relevant to the ROM or you'll end up wondering what
that file is for when you stumble upon it at a
later time. it'll be stored under /multiboot/system-loop-files when it's done.
"What size do you want your system image to be (in MB's)? (WARNING: if you make it too small your ROM +other packages like
gapps might not fit, make it 250)"
The size of /system for the loop ROM, read the thread you downloaded the ROM from to find out what size is ok, i just use 250
for everything in case i want to reuse it with full
at a later time.
"Do you want to make an image file to hold the data for this ROM? (not neccessary if it's an upgrade from a previous ROM or
you want to share a data image with another ROM)
Y for yes N for no."
Same as with the system loop file, if you don't have one, you'll want one, if you're upgrading you shouldn't be running this
step but there is another time when you want to say
no to this, when you want to share a loop file with another installation (not with NAND ROMS). Like for example if you want to
share the data partition between CM-10 and PA-JB.
"What do you want to call your data image? (give it a name you'll remember like cm-7-data for a cm-7 loopinstall)"
Same as for the system loop file, just name it something relevant, the name is of no importance to it's function.
"What size do you want your data image to be (in MB's)? (This file will hold all of your data, don't skimp on the size)"
How many apps do you plan to install? 10 - 50 - 500?
Make it a size that you can live with and that will fit on your sdcard, it really depends on how many apps you'll install.
2. Make a Loop ROM
It's exactly what it says, this will make your loop ROM ready for installation.
"Available ROMs:"
just enter the number that's next to the ROM you want to convert, if it's not there it's because you didn't copy it to /sdcard
/MakeLoopROM/original-roms, you can do so now and
hit r to refresh the list.
"You previously created the system loop file [nameofyourfile], do you want to use it for this ROM? (y/n)"
You'll only get this question if you created a system loop file by going through step 1. If you did so and that's the file you
want to use (check the [nameofyourfile]) then
answer y for yes, otherwise you answer n for no and the following question comes up.
"Available system loop files:"
This choice will only come up if you answered no to the previous question or didn't make your system loop file with the script
in step 1 during this session. Anyways, just enter
the number next to the file you want to use as a system loop file.
"You previously created the data loop file [nameofyourfile], do you want to use it for this ROM? (y/n)"
See the system loop file above, this is the same but for the data loop file
"Available data loop files:"
See the system loop file above, this is the same but for the data loop files
Do you want this installation to format the data image used with this ROM?
Answer Y for yes if it's a new installation and N for no if you are upgrading
and want to keep the data on the data image. (Say yes if you would run wipe
data/factory reset in recovery if this was a normal install)
Y if this is a new install or you're reusing an old data loop file that you want to wipe.
when done hit enter to get back to the menu.
3. Make a loop package (such as gapps)
This, like it says, is for converting non-rom packages (not kernel packages though) such as gapps or bravia or what have you.
"Available packages:"
type the number that is next to the package you want to convert, if the package isn't there you didn't copy it to /sdcard
/MakeLoopROM/original-packages
"You previously created the system loop file [nameofyourfile], do you want to use it for this ROM? (y/n)"
You'll only get this question if you created a system loop file by going through step 1. If you did so and that's the file you
want to use (check the [nameofyourfile]) then
answer y for yes, otherwise you answer n for no and the following question comes up.
"Available system loop files:"
This choice will only come up if you answered no to the previous question or didn't make your system loop file with the script
in step 1 during this session. Anyways, just enter
the number next to the file you want to use as a system loop file.
Repeat No. 3 for all your packages
4. Make (or update) NAND boot image.
This will read the information in your boot partition and store it as boot.img under /sdcard/multiboot so you can boot back to
your NAND installed ROM by running step 6 or
flashing nandboot.zip (also stored under /sdcard/multiboot) from cwm.
Run this every time you update your NAND ROM so the boot.img is fresh.
"This script will update your nand boot.img in the multiboot folder to the version of boot.img you're currently running, make
sure you're running the updated ROM and not
a loop ROM before hitting Y for yes here. If you're not sure type N for no."
If you updated your NAND ROM or haven't run this option before you have to say y for yes here, you have to run this option at
least once or you can't boot back to NAND. Just
make sure you've got your NAND ROM booted and not a loop rom because this will take the boot partition content of your
currently running ROM.
5. Remove a loop installation
If you've come this far you know what you're doing in this option. I'm not going to go through all combinations but they are
self-explanatory.
6. Boot an installed ROM.
Exactly what it says, just remember that even non-installed ROMs may be listed here, if you happen to try to boot to one of
those it will hang at boot, in that case, pull the
battery, reboot to recovery (press and hold vol down while you press power) and use the boot zips that have been created for
your roms.
the Boot zips are located in /sdcard/multiboot/nandboot.zip for the NAND and /sdcard/multiboot/loop-roms
/[namofyoursystemloopfile]/[nameofyourROM]boot.zips
I think that's all, if there is any questions, feel free to ask.
Android version: MakeLoopROM-Android-V11.tar
MD5: 1b33ad6c3078711444c01867e436b65a
===============================================DEPRECATED==============================================================
It took a while but i managed to sort out how to boot to loop filesystems stored on the SD-card.
This means that you don't have to partition anything and you can have as many ROMs installed as you can fit on your SD-card.
You don't have to worry about a2sd/S2E/mounts2sd or anything like that (just make your data partition large enough to hold your apps, you can share the data partition between as many loop ROMs as you like) but this doesn't prevent it either, your sd-ext partition will be untouched and mountable by any ROM you install into a loop file (if the ROM supports sd-ext, that is). Swap will work just fine too.
The script is self explanatory but there are a few things it doesn't explain so i'll explain it here.
Here we go:
1a. Download the MakeLoopROM(version).zip and unpack it to any directory of your choice, just remember where you put it, if you're going to do this under cygwin i suggest you put it in a directory that is easily accessible from the cygwin terminal (IE cygwin/home/"yourusername") and if you're using Linux, just unzip it to your home directory.
1b. Download the MakeLoopROM-Android.tar and unpack it to the root of your sdcard or copy the file to the root directory of your sdcard, open up a terminal session and run tar -xvf MakeLoopROM-Android.tar.
2. Copy the rom and gapps and whatever other package you want to convert to the MakeLoopROM directory that was created during the unzipping above.
3a. In Linux, open up a terminal, cd to the MakeLoopROM directory and type sudo ./makelooprom (losetup requires root permissions).
3b. In windows, open up the cygwin terminal, cd to the MakeLoopROM directory and type ./makelooprom-cygwin
3c. On Android, open up a terminal session, type su and hit enter, type cd /sdcard/MakeLoopROM and hit enter and then sh mkrom and hit enter.
4. Follow the instructions, it should be easy enough to understand.
5. If you want to convert a gapps package and/or other packages you repeat step 3 but type ./makeloopgapps instead of ./makelooprom it'll work for any package you want to install into your loop files, root is not needed for this step.
5a. For android you type sh mkgapps to make gapps and other packages.
6. To be able to reboot back to NAND (the ROM on your phones internal storage) you need to copy the boot.img of your current ROM into the multiboot directory.
6a. The android version now copies the running boot.img if you answer yes when you get the question if you want it to so there is no need to copy it in another way.
After you're done converting your ROM and the packages you'll find all important stuff in the multiboot folder within the MakeLoopROM directory, just copy the whole folder to the root of your SD-card (if you are running on android this step is unneccessary, the script will copy the files for you). You'll find your image files under multiboot (if you created them) along with the "nameofyourrom"boot.img and boot"namofyourrom".sh that you'll need to boot into the ROM from another ROM and finally under loop-roms/[nameofyoursysimage] you'll find all your converted ROMs and packages, ready for installation.
Now you're ready to install the loop ROM and the loop packages, it installs like any other ROM/package via your recovery of choice (I recommend my CWM Touch 6.0.1.1, it's what this is tested on but it should work fine on any recovery).
To switch between ROMs you open up a terminal window, type su to get root permissions, cd to the multiboot folder (cd /sdcard/multiboot) and type sh bootnand.sh to switch to your internal ROM or boot"nameofrom".sh (bootcm-7.2.0-blade.sh if you installed cm-7.2.0-blade for example) for any of the loop roms. You can also install script manager and script manager widgets and make widgets for those scripts on your homescreen, that way rebooting to another rom is as easy as pressing the icon on your homescreen.
I'm sure there'll be a lot of questions about things i haven't thought of, but if you should fail or do something wrong then just hit ctrl-c and start over, the script cleans up and restarts the build.
Thanks to:
[email protected] for some ideas.
championswimmer for some scripts from his Kernel Kitchen.
Tilal for suggestions that helped fix running this script on the phone itself as well as the app he's making to make reboots between the different installs much easier and better.
[email protected] for being a very patient tester.
Files:
Linux version: MakeLoopROM-Linux.tar
MD5: 8907e2519276f4abcbb5bab0de168ae5
Windows Cygwin version: MakeLoopROM-Windows.zip
MD5: 096921e7a08eba98329bb7ec486068f0
Android version: MakeLoopROM-Android-V8.tar
MD5: f4ee326faf65bd032a95a1e2b4e8bc9f
25/10:
* Completely rewritten, it's now entirely menu driven with choices so you don't have to type filenames.
* Fixed faulty boot flashing
* Now copies a flashable zip of each loop ROM and NAND ROM boot images to /sdcard/multiboot for NAND and /sdcard/multiboot/loop-roms/[nameofyoursystemloopfile/[nameofyourrom]boot.zip so you can flash it via CWM if you need to.
* Includes a cross compiled version of bash for arm to fix a lot of scripting problems.
12/10:
* Streamlined, a LOT faster now.
* Possible fix for the random faulty boot.img flashing when switching between ROMs, need feedback on this.
* Removed unnecessary file creation (all of it runs within one loop file and questions (if you create the system and data images you won't get the question twice, it checks if your ROM is a JB rom without your interference).
* Added cleanup script, to use it run sh cleanup as su and follow the instructions.
* Lots of other bits and pieces that makes it safer and faster to use.
3/9:
* Fixed the Android version to work with CM7 roms [changed let=size to size=$(expr], thanks to Sulthekk for the heads up on that
* Added a failsafe to the Android version on creation of system loop file if it already exists and on giving the script a name for system and data image that doesn't exist. You get one retry, if you can't get it right after that... It is possible to multitask on android, just open a file manager if you forgot the name of the system or data image.
* Fixed the Linux and Windows versions to work with JellyBean ROMs, thanks to jpeg729 for the heads up on that
* Change the file names to reflect which version is which
1/9:
* Finally fixed the problems with no permissions running the script on some ROMs.
1/9:
* Added the choice to copy your currently running roms boot.img to your multiboot automatically, no user interaction needed for the process.
31/8:
* Changed the android version to a tar to keep file permissions intact.
* Fixed it up so it runs on CM-10 and PA as well as all other roms (i hope).
30/8:
* Release of the Android version, now runs completely on your phone.
28/8:
* Changed the Linux version to tar format to ensure that permissions are correctly set.
* Fixed the Cygwin version so it can make the data and system image files, they will be formatted on install and if it's a new installation you have to choose y to format the data image file or it will not have a filesystem.
* Changed a few misspellings in user interaction texts and tried to make it easier to understand.
Woah. Cwm and Multiboot in a week's time?
When you getting your RD status?
Good work man
Sent from my Ouya
QuantumFoam said:
Woah. Cwm and Multiboot in a week's time?
When you getting your RD status?
Good work man
Sent from my Ouya
Click to expand...
Click to collapse
I've got one third project that i'm about to wrap up and after that i'll just do incremental updates on those three while devoting my time to kernel development which is sorely needed.
Found a util for windows called winDD, i'll check it out and include it in the next version if it's of any use. That will fix the problem with not being able to create the loop files on windows.
I've built makebootfs and makebootimg for android and will include them along with a script that works on android in the next release.
I'll make the next release a tar version along with a zip version for windows users, this is to preserve file permissions.
Any other suggestions are most welcome.
After a lot of issues i finally got the Android version ready, i've tested it and it works fine on my phone, both the makelooprom-android and the makeloopgapps.
I had to cross compile perl and the mkbootfs and mkbootimg files to run on armv6l which took a while because i kept getting errors, both are included with the script.
Then there was a problem with running split-bootimg.pl on the sdcard, fat32 doesn't support symbolic links so i had to make three different loopfiles within the script to use for bootimg-contents ramdisk-contents and output.
Anyway, now it runs just fine, try it out.
New version up and running.
Only for zte blade ?
Sent from my B15Q using XDA Free mobile app
Hey Motorola Fire owners!
Here's ClockWorkMod for our beloved QWERTY phone [With nandroid backup minor issues]
Any damages, you're responsible of it.
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download Pimp My Rom from playstore, open it, click > Universal init.d support, then click > activate
3- Download latest zip (bootmenu 3-12-12.7z)
4- Extract it, and run Install-boot-menu.bat
If you want to know what the script does:
5- Download latest bootmenu folder, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
6- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
7- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
7- b- inside this file paste this code and save it:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
-Then Reboot
Now focus, while you're seeing motorola logo, the capacitive keys' leds will light up at certain timing, quickly press VOL- button before the lights go off, if you later, don't want to boot to bootmenu, just don't press the VOL- button, the phone will boot normally to system
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------To restore backed up nandroid system.yaffs2.img
In terminal emulator or adb shell type:
cd /sdcard/clockworkmod/backup/YYYY-MM-DD.HH.MM.SS/
md5sum *.img > nandroid.md5
Where <YYYY-MM-DD.HH.MM.SS> is the folder of your backup.
Then go to cwm again and restore ( i prefer advanced restore > system )
Or with fastboot: By typing: "fastboot flash system system.yaffs2.img"
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Now the most important part, press thanks button, it motivates me
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'd like to thank those who made this dream come true: GentryLamp - 7amdoun (Thanks alot bro) - Aweosomeabhijeet - Mr. indigo - Andrewidya - AndYRo - Chen2011521
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Changelog:
3-12-12
-Added automatic installer (abhijeet's idea)
1-12-12
-Booting to bootmenu through volume down button (Thanks alot 7amdoun!)
-Now you don't have to delete 97bootmenu at all
-Unified bootmenu-recovery background
30-11-12: Very old build
-Removed ability to backup data via clockworkmod since it probably is corrupted, causing bootloops when restoring, you can backup the whole rom using onandroid backup instead
-Ability to restore nandroids
28-11-12: Very old build
-Fixed font size of the recovery, (Thanks chen2011521)
-Changed wallpaper because i got bored
25-11-12: Very old build
-Modified Stock.sh so when you select [+boot] > [stock] it boots normally to stock system, Without needing pc. (Thanks aweosomeabhijeet)
-Fixed some mounting issues, may be able to backup .android_secure
24-11-12: Very old build
-First alpha release
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Downloads:
Removed old builds, for the user not to download them and use the new incompatible steps.
Just registered!
---------- Post added at 04:40 PM ---------- Previous post was at 03:43 PM ----------
Only just created a bunch of commands to mount secure.android. After normal backup of system and data, gave me this error:
Backing up .android_secure...
Freeing space...
sh: dedupe: not found
Done freeing space.
sh: dedupe: not found
Already did it!!
Waiting for more to come
:good::good::good::good::good:
No more dedupe error, tar generated correctly! but more mounting problems! The last logs lines:
Backing up .android_secure...
com.joelapenna.foursquared
com.google.android.youtube
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
So fstab is sill umcomplete!
---------- Post added at 05:59 PM ---------- Previous post was at 05:42 PM ----------
Im startint to think that every sbf has diferents mounts...
xt316 chinese 2.3.5
97bootmenu permission 744
and reboot into bootmenu
but not full permission.
Backup stuck at /system
....
Did you port the recovery from source? You can change it font smaller.
Mazen.kh said:
Hey Motorola Fire owners!
Here's CWM for our beloved QWERTY phone [Still have issues with nandroid backup]
Okay so first of all this is not only my work
I only built CWM6 and put it inside the bootmenu, also helped in discovering init.d support, and when you nandroid backup, i fixed the creation of system.img and data.img (with help of dear friends from taringa.net) :angel:
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download PimpMyRom.apk from attachments and install it, because the one in the market have some errors causing FCs
3- From Pimp my rom, click > Universal init.d support, then click > activate
4- Download bootmenu.zip, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
5- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
6- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
6- b- inside this file paste this code and save it:
HTML:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
7- Reboot
After reboot, android bootmenu will appear, choose recovery, then select custom recovery
Now you entered CWM 6 :cyclops:
Please don't select the "mounts" section, still needs fixes, might be dangerous
If you take nandroid it will successfully backup system.img and data.img without sd-ext.
You may not be able to restore them through cwm.
But you can restore them through FASTBOOT.
I flashed many zips through this recovery successfully.
PS: to boot again to system, normally connect the device through adb, and type:
adb shell
rm -r /system/etc/init.d/97bootmenu
Then reboot using "adb reboot" or reboot function in bootmenu
Now the most important part, press thanks button, it motivates me to keep up the good work
I'd like to thank those who helped in getting this bootmenu to work:
- Gentry Lamp
- 7amdoun
- Aweosomeabhijeet
- Mr. indigo
- Andrewidya
- AndYRo (from Taringa.net)
probably others that i forgot to mention
I'll keep updating the recovery until it becomes perfect
Click to expand...
Click to collapse
Hey Mazen I would like to suggest you something.
Open bootmenu folder go to script folder and open stock.sh
and add
Code:
rm -r /system/etc/init.d/97bootmenu
reboot
Then if you select boot>Stock your phone will reboot twice and boot normally.
then no need of using adb in PC.
I make everything as u say and restarted it above 6 times but nothing happens and my device starts normally!!!
EDIT: try to change permissions of 97bootmenu to rwxr-r- & restart 2 times but nothing happened!!
chen2011521 said:
xt316 chinese 2.3.5
97bootmenu permission 744
and reboot into bootmenu
but not full permission.
Backup stuck at /system
....
Did you port the recovery from source? You can change it font smaller.
Click to expand...
Click to collapse
I built it online and modded some files, couldn't build from source, the font is not so important right now so i'm working on fixing the nandroid backup
aweosomeabhijeet said:
Hey Mazen I would like to suggest you something.
Open bootmenu folder go to script folder and open stock.sh
and add
Code:
rm -r /system/etc/init.d/97bootmenu
reboot
Then if you select boot>Stock your phone will reboot twice and boot normally.
then no need of using adb in PC.
Click to expand...
Click to collapse
I tried that once and it booted to the bootmenu again but i will retry, thanks :laugh:
wrong :|
I follow ur steps and I fail in problem! just tell me what shoud I do NW?
and nothing wrong in my device!
EDIT: I change some permissions and it's work but I forgot what I do and I reboot without need PC!
I advice u guys to make that suggest by aweosomeabhijeet it's awesome
Ok remember to use reboot after rm command.
Sent from my XT530 using xda app-developers app
european sbf
Hey guys has anyone an european sbf for the xt311, i really need it.
Hey Mazen,
How did you manage to get CWM to make a full backup. I tried everything but it just freezes on system. I edited recovery.fstab to point to /dev/block/mtdblock* for every partition but it keeps complaining that it can't find that volume to mount.
7amdoun said:
Hey Mazen,
How did you manage to get CWM to make a full backup. I tried everything but it just freezes on system. I edited recovery.fstab to point to /dev/block/mtdblock* for every partition but it keeps complaining that it can't find that volume to mount.
Click to expand...
Click to collapse
I added mkyaffs2image
and AndYRo fixed a couple of mounting errors, if you build CWM 6 online you can take our xt311's modded files and only replace "recovery" file in /recovery/sbin/, with the corresponding one in your CWM 6
Mazen.kh said:
I added mkyaffs2image
and AndYRo fixed a couple of mounting errors, if you build CWM 6 online you can take our xt311's modded files and only replace "recovery" file in /recovery/sbin/, with the corresponding one in your CWM 6
Click to expand...
Click to collapse
Edit: I ported CWM6 to my phone manually and it loads and backs up boot and recovery but still gets stuck on /system
Any ideas?
Moderator warning.
Thread has been cleaned. Remember forum rules when posting.
Mazen.kh said:
Hey Motorola Fire owners!
Here's CWM for our beloved QWERTY phone [Still have issues with nandroid backup]
Okay so first of all this is not only my work
I only built CWM6 and put it inside the bootmenu, also helped in discovering init.d support, and when you nandroid backup, i fixed the creation of system.img and data.img (with help of dear friends from taringa.net) :angel:
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download PimpMyRom.apk from attachments and install it, because the one in the market have some errors causing FCs
3- From Pimp my rom, click > Universal init.d support, then click > activate
4- Download latest bootmenu.zip, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
5- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
6- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
6- b- inside this file paste this code and save it:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
7- Reboot
After reboot, android bootmenu will appear, choose recovery, then select custom recovery
Now you entered CWM 6 :cyclops:
Please don't select the "mounts" section, still needs fixes, might be dangerous
If you take nandroid it will successfully backup system.img and data.img without sd-ext.
You may not be able to restore them through cwm.
But you can restore them through FASTBOOT.
I flashed many zips through this recovery successfully.
PS: to boot again to system, normally:
In bootmenu select [boot] > [stock]
OR
Connect the device through adb, and type:
adb shell
rm -r /system/etc/init.d/97bootmenu
Then reboot using "adb reboot" or reboot function in bootmenu
Now the most important part, press thanks button, it motivates me to keep up the good work
I'd like to thank those who helped in getting this bootmenu to work:
- Gentry Lamp
- 7amdoun
- Aweosomeabhijeet
- Mr. indigo
- Andrewidya
- AndYRo (from Taringa.net)
probably others that i forgot to mention
I'll keep updating the recovery until it becomes perfect
Click to expand...
Click to collapse
Thanks for creating a thread!
I'm trying with UAE sbf, unfortanelly I have to reflash it, since there's a problem with my Init.d support.
*Can we able to change the font size in the recovery not in the bootmenu? cuz it's looks bigger
PS. i make oNandroid backup and I delete it to try the backup section in the recovery when I make it it's stuck on
backup system.....
and no progress bar like any CWM recovery!
If build from source,android.mk in bootable/recovery can change font.
smaller font looks well on xt311/6
I have built one, but some problem not solve.
chen2011521 said:
If build from source,android.mk in bootable/recovery can change font.
smaller font looks well on xt311/6
I have built one, but some problem not solve.
Click to expand...
Click to collapse
Upload it so i can mix things and fix the font
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.