Database Info

[Recovery] [09-Feb-2011] RA-supersonic-v2.3

[ 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

[Release]FeaMod Recovery 1.4 - based on CWM Recovery v. 5.5.0.4.

I've ported the CWM Recovery v. 5.0.2.7 to the Samsung Galaxy I9001 device.
Download it here and follow the instructions to install it. I will post any changes or updates again in this very first post.
Disclaimer: Flashing software onto your device might void your guarantee and may brick your phone. Use the attached software on your own risk. I am not responsible for any bricked device due to this software. You've been warned.
Credits and huge thanks go to:
Koush - for writing the original ClockworkMod Recovery
Ilarrain- for patching graphics.c for the Galaxy Ace device
YardE - providing init.d support to the custom kernel
Riversource - for providing scripts which make the handling of smd files super easy
All the users on this forum who have tested my former versions and helped to debug it - you're great
Are there any differences to "stock" CWM recovery which I can see?
Yes, there are. I've removed additional "No"'s in some functions. I've also changed the background logo and the name of the recovery (though "CWM Recovery" is still there due to make proper credits and copyright thing things). And of course there is the custom kernel included!
How to install/update
If you already have a FeaModRecovery version on your device it's simple:
Download one of the update.zip packages (starting with version 1.3) and copy it to one of your sdcards. Reboot into recovery and install the package (install zip from sdcard -> choose zip from ...).
If you're still on stock recovery or another one follow the the step-by-step instructions on the bottom of the post.
What about the version numbers?
The first number represents major updates (for example update to CWM 6 thus FeaMod v. 2)
The second number represents minor updates. For example if CWM goes up to 5.0.2.8 or I change something on my version.
The third number on some versions represents the kernel since it's a custom one and included in the whole package. So if only the last number changes, I have made "only" changes to the kernel.
Downloads
SMD files to flash via Odin
download FeaMod v1.1: http://www.mediafire.com/?oxxn0676fikkdaw
download FeaMod v1.2: http://www.mediafire.com/?u9996yn6i7rc92z
Hint:
For those who experience boot loops. Before you flash a new version copy the content of your external sdcard onto your pc and format it afterwards. This should help. After you've successfully flashed and rebooted into your system you can copy the files back on your external sdcard.
zip files OC/UV kernel to flash via FeaMod Recovery
WARNING:
Applying the FeaMod Recovery with the FeaCore_OC/UV kernel is dangerous and may brick your phone. In any case it will drain your battery faster when running on 1.8 GHz all the time. Only install it when you know what you are doing! Otherwise install a package without a OC/UV supporting kernel.
FeaMod Recovery 1.3.1 with FeaCore Phoenix OC stable release: http://mediafire.com/?al9s0abvdjrmg6e
FeaCore Phoenix includes:
-BFQ I/O scheduler 2 r1
-SIO I/O scheduler
-OC up to 1.8 GHz
-smartassV2 governor (ondemand is default)
-JFS and CIFS support
-tun included
-bootanimation support
-new boot sound
- I8150 GPU librarys
-cleancache
FeaMod Recovery 1.4 with FeaCore Phoenix OC stable release: http://www.mediafire.com/?jqfbvxflev1jcoz
zip files without OC/UV kernel to flash via FeaMod Recovery
FeaMod Recovery 1.3.1 with FeaCore Phoenix nonOC stable release: http://mediafire.com/?5unogie5i58x85r
FeaMod Recovery 1.4 with FeaCore Phoenix nonOC stable release:http://www.mediafire.com/?ben9s5a8bz1d3gc
if you wanna change your bootanimation, copy your downloaded bootanimation.zip to /system/media/sanim.zip (yes you have to rename it to sanim.zip). Change the modus to 644 (rw-r--r--).
How to change the bootanimation:
Copy the bootanimation.zip to your sdcard and start adb shell:
Code:
mount -o rw,remount /system
cd sdcard
dd if=bootanimation.zip of=/system/media/sanim.zip
chmod 644 /system/media/sanim.zip
Changelog:
FeaMod v.1.1:
+ Performing a factory reset aka wipe data now doesn't delete the external sdcard anymore.
+ Performing a backup with no changes in the mount menu will automatically backup .android_secure as well.
+ The external sd card will no longer be "backuped" unless you manually mount the sd-ext in the mount menu.
FeaMod v.1.1.1:
+Kernel changes: initd support - implemented by YardE. BFQ I/O Scheduler implemented by me
FeaModRecovery v.1.2:
-Included the rest of the changes made by Koush
-You can now select wheter you wanna make the backup onto internal or external sdcard
-I've decided to let go the backup of the external sdcard (save .android_secure of course). Because it can destroy your internal sdcard when not properly handled and backing up the external sdcard on the external sdcard doesn't make any sense at all.
FeaModRecovery v.1.3:
- fixed a bug which led to a md5 mismatch when recovering only single partitions (advanced recovery).
- reimplement the reboot into recovery option. This option now makes sense again (see next point).
- I provide you from now on with update.zip packages to update FMR from within an already installed FMR.
FeaModRecovery v.1.4:
- https://github.com/CyanogenMod/android_bootable_recovery/commits/ics/
Kernel (FeaCore_1.0 and FeaCore_1.0_OC/UV):
- update to jhash3 (for better reliability on data connections)
- implemented BrainFuck Scheduler as main scheduler (CFS is gone for the moment)
- implemented interactive governor (ondemand is still default and already very aggressive)
- implemented BFQ I/O
- init.d support (thx to YardE)
Kernel FeaCore Phoenix (OC and nonOC):
-jhash (battery drain is too high with jhash3)
-CFS as CPU scheduler
-SmartassV2 as new governor (ondemand is default)
-CFQ, BFQ, SIO and Deadline as I/O schedulers (SIO is default)
-supports Boot animation
-custom Boot sound
-cleancache patches
-I8150 GPU libraries
How to use
Start the FeaMod Recovery by pressing your Power Button and the Volume Up button simultaneously. Hold both keys until the Samsung Logo appears. Release both keys after additional 2-3 seconds and wait. The system now boots into FeaMod Recovery.
Navigate in the menu: Volume Up/Volume Down buttons
Select item: Menu Button
Return to start screen: Return button
Additional hints
Old versions (all versions until v.1.1.1): To backup your external-sd too, you need to mount the sd-ext partition in FeaMod Recovery:
Select mounts and storage -> mount /sd-ext.
Warning:
Don't backup your external sdcard if its content is larger than the space on your internal sdcard left!!!
If not manually mounted only your apps on the sd-ext will be saved.
In case the system won't recognize your external sdcard: Copy the content of your external sdcard to your PC and format it within your ROM. Copy the files back onto the newly formatted external sdcard. Thx to Igor_999 for stumbling across that problem
Sources on github:
https://github.com/manveru0/FeaMod-Recovery
Have fun with it!
Do it step by step ;-)
For Odin related things, look also at the attached image.
Important: You have to install busybox under /system/xbin/ in order to get the init scripts working.
Get "Busybox Installer" from the market. That version let you choose the location to install it.
1. If you don't have at least XXKP4, download it from samsungmobile (you need to register, but it's worth it)
Browse through the forum and go to our devices, there you'll find the ROMs. If your comfortable with your ROM
go to step 3.
2. Download Odin 4.43 from here and flash the files. If you have a one package file, download AriesVE.ops from this post and select that one in Odin
under OPS file. If you downloaded XXKP4 select the bootloader.tar as the BOOT file, the MODEM file as the phone file, the PDA file as the PDA file and the CSC file as the CSC file. Flash it and wait until your phone has rebooted back into the system.
3. Download FeaMod Recovery v.1.2.
4. Open Odin again and select the AriesVE.ops as the OPS file. Tick the one package option under OPTION. The select the FeaMod file as the One Package file. Flash it! After 10 to 15 secs your device will reboot into your system.
6. Copy the Universal Adrenaline v.13 zip file (download it from here: http://forum.xda-developers.com/showthread.php?t=1236779) to your internal or external sdcard.
5. Shut your device down and reboot into FeaMod Recovery v.1.2. by holding the Volume up and Power Button simultaneously until the Samsung Logo appears, hold it for 2,3 seconds longer and release both buttons. Welcome to FeaMod zone :-D
6. Make a full backup either to your external or internal sdcard (look at the options you got) just to be sure.
7. Go to mount and storage -> mount /system
8. Go to advanced and select fix permissions.
9. Go to install zip from sdcard and select your fresh copy of adrenaline shot v. 13.
10. Reboot into system.
you got it! You now have FeaMod Recovery v.1.2. with the latest kernel from YardE and me which supports init.d and has BFQ as the default I/O scheduler. And you should have the applied adrenaline shot by now. Test it either with a terminal (you should have the /system/etc/init.d folder) or by the quadrant benchmark (you should get at least 2500 points). In case there are any questions left, ask for.

Nice. I just flashed it and its backing up right now. It seems to work like a charm. Thanks!

it's looks like this right??

hi. sorry i don't get it. what is the function for this? is it to backup my current ROM?

OK, I had a bad day today, but this made my day!
Thank you sooo MUCH!
So, now... Custom ROMs much more easily?

budakmaran said:
it's looks like this right??
Click to expand...
Click to collapse
Yes, thats correct!

AWESOME
I've said it before and i'm saying it again You are awesome!!! Thnx a lot.
And also a big thank you to netchip without whom i dont think we could have had this
I'm soooo happy! now cyanogen mod to look forward tooo

Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001

Blumdum said:
Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001
Click to expand...
Click to collapse
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext

sweeeeeeet ill try this later looking forward to cyanogen mod now we have working cwm

manveru0 said:
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext
Click to expand...
Click to collapse
ok the ext-sdcard seems to work after i formatted the card
just have to copy back the files

Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.

traedre said:
Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.
Click to expand...
Click to collapse
you are welcome. Thank you, good to hear

Am I right that there is init.d support included?
Sent from my GT-I9001 using XDA App

Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.

Works like a CHARM! LOVing it!

Very nice work! There is one problem. Members from the site 4pda.ru actively using CWM. Only for Skype both cameras are becoming as rear, front camera disappears. The guys were asked to write about this issue. It is strange that this is not who did not notice. Itself is not using Skype. Check it out please.

quest221 said:
Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.
Click to expand...
Click to collapse
Yep, that's perfectly okay because I have uploaded a new file with a fixed bug yesterday evening. See also the first post

manveru du bist ein konig
thanks for one package
i will test it today
btw what for a cpu government was there setted up before?

problem this cwm in skype. 2 back camera, no working front camera, only back... fix it please.
sorry my english...

[RECOVERY][18/8/2012] TWRP v2.2.1.5

Hi all,
My port of TWRP. I know berni posted a build already, but mine is newer and I've tested it for a few days, haven't seen any buggy behaviour other than buggy restore (see bug hunting).
Features (copied from TWRP list):
Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)
Prerequisites:
Rooted phone
P920 recommended, untested on P925
How to install:
1. Download recovery.img which is attached.
2. Copy it to the folder containing adb.
3. Shift+Right click in the folder, select open command window here
4. Enter the following commands (hit enter after every line):
adb push recovery.img /sdcard/recovery.img
adb shell
su (you might have to accept a Superuser prompt)
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
exit
exit
Click to expand...
Click to collapse
5. Enter adb reboot recovery and hit enter
6. ???
7. Profit!
Screenshots:
Follow the instructions above and you get interactive and functional "screenshots"
Credit for this goes to TeamWin for their very cool recovery and the CyanogenMod team for all that they do. Thanks also to berni for giving me the motivation to port it myself due to nonfunctional cache wiping
Bug hunting:
EXT4 backups don't restore properly (have a theoretical fix for this, stay tuned. In the meantime, rename all files which look like *.ext4.win to *.ext3.win by mounting USB storage on your computer and do the same for the md5 files)
If there are any bugs please tell me about it.
Changelog:
18/8: initial release

Hi, is it works on optimus 3D MAX?
Thanks in advance

Not sure. This is entirely untested on that, but I doubt it works
Sent from my LG-P920 using Tapatalk 2

Hi pandaball, we allready pm each other. Can u make twrp for O3D Max? I can provide u the stock recovery and the mountpoints!
Lots of people would be thankful.
I tryed myself but didnt get it to work.
Thanks in advance
Kind regards,
Sent from my LG-P720 using xda app-developers app

No. The phone has to be supported by CyanogenMod first.

[SCRIPT] Multiboot via loop file, completely rewritten [25/10]

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

OTA update bootloop fix [S-ON] [BU] [Stock Rooted ROM]

Hi, I found a way to fix this bootloop which happens after you flash the latest ota update if you have unlocked and rooted your stock rom.
I own a HTC E8 China Unicom [M8Sw - dual sim], but I think it will work on other variants.
It is the SU binary/files which are preventing the phone from updating correctly.
You can also restore a clean unrooted TWRP backup and do the OTA update.. it will work just fine.
This tutorial is for those who don't want to lose their app data and modifications.
To be able to update... you need to fully unroot the phone before. Well, this was previously not possible due to system write protection.
(There are also other methods of unrooting. (deleting the SU files manually with the file manager of TWRP recovery) This doesn't work, I have tried it myself..often cause bootloops.)
But now we have a custom recovery mod which enables us to write to the system partition and thus can fully unroot with SuperSU app itself.
Requirements:
-some expertise with adb/flashing/twrp recovery management will be needed.
-stock firmware.zip, inside the OTA zip file, where you will find you stock recovery,boot image, etc
-Stock ROM, rooted with no modified existing system files
-TWRP Recovery from @Captain_Throwback works fine. I used the 2.8.6.0 one. http://forum.xda-developers.com/one-e8/orig-development/recovery-twrp-touch-recovery-t3060188
-untouched Stock Kernel Modules (IMPORTANT)
-SchKernel Extra 3.3, to gain write permission to /system http://forum.xda-developers.com/one-e8/general/schkernel-extra-3-3-t3200090
[UPDATE: SchKernel Extra has been updated to 3.5 and the old one is not available for download on the other thread. You can find attached at the bottom of this section ver3.3 which I had used. Please don't use ver3.5 as a user has reported having bootloop with that.)
-Battery +80 charge recommended...the process gonna demand a lot of power.
-Patience... loads of it....
Disclaimer: I am not responsible if you brick or damage you phone!!
Before you flash anything, be sure to have a working twrp full backup of you phone! In case anything goes wrong.
STEPS:
1. Copy the untouched kernel 'modules' folder [found in system/lib/ in your phone] to another location ( for e.g. to your internal phone memory), you're gonna need it later.
2. Flash the twrp recovery if you haven't already and boot into TWRP recovery.
3. flash SchKernel Extra 3.3 kernel mod. It will launch the aroma installer. There will be options as overclocking/underclocking etc..
I left everything on STOCK option, disabled Swipe2sleep, unselected the everything in the optional addition page. Then went to install it.
4. Reboot, and open SuperSU app, go into setting, tap the FULL UNROOT option, this might take a while. The first time, when the unrooting notice shows and it seems that the app is not doing anything, you might be required to exit the app by pressing home button. Then open the app again and redo FULL UNROOT option. If you exit the app and when re-opening it, the "unrooting notice" is still there, then it means it is working. This might take a bit of trial and error.
5. Ultimately, SuperSU app will close. Then you will need to reboot. You will see that SuperSU is gone and that you have no root access.
6. Now, turn it off again to go to fastboot. Connect to PC and flash the stock boot.img via adb to restore the stock kernel.
8. Then, in twrp recovery, mount /system partition and got to advanced >> file manager..
9. Now browse to /system/lib/ and delete the 'modules folder'.
This is because the SchKernel Extra 3.3 kernel mod flashed previously has modified your kernel modules and when you will try to update the OTA, the stock recovery will report that the kernel modules (xxxxx.ko) has be modified and it will stop the OTA update process.
10. Remember the previous untouched stock 'modules' folder you copied previously, now move it to /system/lib/HERE , to replace the deleted folder.
[DO STEP 9 BEFORE - Don't try to overwrite the folder, it won't be possible. It said operation failed for me. ]
Optional: You might also want to delete su.d folder in \system and init.d folder in system\etc
these files were for the custom kernel and won't be needed anymore.
11. Reboot into fastboot mode, connect to PC (if not already), flash stock recovery.
12. Now, you're good to flash the OTA updates. :good:
-Download it, if not already done.
If ever you have downloaded from PC and copied it to phone, and for whatever reason the phone is not detecting the zip file and asking for install.
Just move it to you exeternal SD card and rename it to "ptt.zip" , go into stock recovery and go down the list to "apply update from SD card"
and it should flash the zip file. When done, select the reboot option and it will say reboot to flash firmware.zip and the will boot. :fingers-crossed:
When booting it will take some time (3 to 8 mins), and then go to the "Android is updating - optimizing apps" screen. This might take a lot of time if you have a lot of apps installed. The phone might get really hot during this process.
When the OS finally boot completely there will be an "HTC" screen and an exclamatin mark in the notification bar. NO WORRIES, it is the just the update working. It will go away when the update is fully processed.
After OTA update is done, you can make a twrp backup of the unrooted system, so that you can restore it for future OTA updates.
If some steps are confusing, feel free to ask for any clarification
Hope I helped you. Don't forget to hit thanks

problem
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?

neekless said:
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?
Click to expand...
Click to collapse
how did you flash it exactly?
Did you flash it thought TWRP recovery?
also...what variant of HTC e8 are you using?

Thank you for this guide. :good:
For the newbies, here are exact instructions for each step. TWRP is required; presumably you have this because you've rooted your phone. (If you haven't rooted your phone, what are you doing here?)
Note that rebooting to TWRP can be accomplished in several ways:
Long-press the power button; when prompted choose Reboot. When the screen goes black, press and hold the Volume Down key. This will take you to hboot; from there choose Recovery.
Enable developer mode from settings, plug in to a computer, and issue the command adb reboot recovery.
Also note that it is prudent to do a full TWRP backup to external storage (microSD, USB OTG) before anything else, so you have a good recovery point if things go wrong.
To copy the system/lib/modules directory, you can use a root-enabled file explorer or TWRP. To do it in TWRP:
Reboot to TWRP.
In TWRP, select Mount. Make sure that system is checked.
Back to the main TWRP menu, select Advanced.
In the advanced menu, select File Manager. Then navigate to /system/lib/modules.
Tap on Select, then Copy Folder. Navigate to a new location - I used /sdcard/Backup - and tap Select again. Don't use your external SD or USB-OTG, they may not preserve permissions correctly.
To flash the SchKernel Extra, copy the ZIP file to your device, reboot into TWRP, and select Install. From there, navigate to where you copied the ZIP file and select it; then follow the prompts as sanijsnj specified.
Removing SuperSU works exactly as described. Don't forget to reboot at the end (although it may not be necessary).
To flash the stock boot, in a cmd window where you have the Android SDK, typically in the sub-folder platform-tools enter: fastboot flash boot boot.img (boot.img from the OTA ZIP).
To delete and restore /system/lib/modules, follow the steps above, starting of course from your saved 'modules' directory and copying to /system/lib.
To flash the stock recovery, again in the cmd window enter: fastboot flash recovery recovery.img (recovery.img from the OTA ZIP).