[ICS][.13] emwno's.kernel w/ Dual Recovery - Discontinued - Xperia Arc Android Development

Discontinued
TWRP Version: 2.4.3
CWM Version : 5.5.0.4
E Kernel Version: Build 3 - U2
Presenting the first Dual Recovery Kernel for Arc/S and Pro. Your warranty is now void bla bla bla. I'm working on bringing TWRP to ICS based kernels (not cm9) and have been successful, worked on this alone for hours. Thankyou to @Rachit Rawat for allowing me to use some ramdisk files from his sources and Teamwin for creating TWRP. Ill write the rest of the thread later on. Both of the kernels are attached. And for those wondering, yes its been reported to be fast, pretty responsive with great battery life.
To use TWRP hit the volume down button when the led lights up pink. And to enter CWM hut the volume down key at the next led light up and vibration.
Note: TWRP and CWM are not the same when backing up or restoring, you will not be able to restore ones backup from another.
What works:
Twrp
Cwm
Flashing
Backup
Restore
Mount device partitions
Mount external partition
Boot
___________________________________
What Doesn't Work:
ADB sideload (twrp)
___________________________________
Whats There:
Init.d support
CWM
Built with Linaro
TWRP
Newest .13 kernel sources from Sony
Many Governers / IO schedulers
Overclocking support
Cache Compresion
___________________________________
Download:
Arc/S - Build 3 | Modules -- LIVE
Pro - Build 2 | Modules
___________________________________
Changelog:
Build 3 - U2
--boot--
Updated to TWRP 2.4.3
Minimal ramdisk changes
Better sleep
Build 3 - U1
--No boot--
Updated to TWRP 2.4.3
Minimal ramdisk changes
Better sleep
Build 2
TWRP updated to 2.4.1
Attempted fix for adb issues with twrp (need to test)
Fixed specific partition layouts (twrp)
Build 1
Xperia Arc/S boot
Official public release
Fillers added
Update 2
Removed fillers
New init.rc
Pro boot fixed
Modified mount points (pro / arc)
Arc/S still no boot
Update 1
Initial beta release
Much not working

Old stuff. not required.
Since I've got the 2nd post, let me point out the things which are working / not working in TWRP:
Working:
Flashing zips
File Manager
Backup (Haven't tried Restore)
Terminal Command (Little buggy keyboard)
Not Working:
ADB Sideload via TWRP
ADB and Mount USB Storage
(Bug) Aroma Installer works only half screen
A note on backup:
If you got any issue while making a nandroid backup, download the attachment, extract the file and move it to /sdcard/TWRP
If the check-box of .android_secure does not get displayed in Backup menu, go back and enter Mount Menu, unmount SD Card and mount it again. Go to Backup menu again and select Refresh Sizes. .android_secure will be visible now.

soumya_digi said:
Black screen for me. No bootlogo or anything.
Device : LT15i
Click to expand...
Click to collapse
Link updated for Arc. try the new one.

this is based on @Rachit Rawat kernel ???

Re: [.13] E Kernel w/ TWRP [Pro/Arc]
[noob] what is TWRP ?

leo_nidas said:
this is based on @Rachit Rawat kernel ???
Click to expand...
Click to collapse
not based on, just some ramdisk files acquired. for (.13) base.
steliosvola said:
[noob] what is TWRP ?
Click to expand...
Click to collapse
its a recovery like cwm. you can read more here: http://www.teamw.in/project/twrp2

download wow 11MB wifi modules includet or must be downloaded ???

leo_nidas said:
download wow 11MB wifi modules includet or must be downloaded ???
Click to expand...
Click to collapse
Oops, forgot to upload them. uploading now. will update op when done.

Same with e_anzu.img too.

i have a black screen on new link - i have ARC/S

leo_nidas said:
i have a black screen on new link - i have ARC/S
Click to expand...
Click to collapse
soumya_digi said:
Same with e_anzu.img too.
Click to expand...
Click to collapse
try this one. it should work. http://d-h.st/hqg

Guess ur replacing the link for new one ? Coz, ur arc link, is deleted.

vashta said:
Guess ur replacing the link for new one ? Coz, ur arc link, is deleted.
Click to expand...
Click to collapse
Links working
---------- Post added at 11:54 AM ---------- Previous post was at 11:48 AM ----------
Kernel is Working TWRP working Wifi working GPS working Good
test on my Xperia T mod by zohaib0001

Boot successful! :good:
Testing other things now.
BTW, the /vendor partition is not /system/vendor. Need to modify init.semc.rc or else people will have issues with sound enhancements.
Vermagic string is indicating Serene-ICS!
EDIT: Damn, this thing has dual recovery! :cyclops:

Is this dual boot ? After I install modules(1).zip, after i touch 'reboot system', I end up in cwm again.
But after i reboot system (from that cwm menu), its back to TWRP again when i press vol down.
Anyway.. the wifi works, so far no facing problems. no bootloop etc.
In the info, it's still serene kernel.
* Kinda not used with this touch screen menu in twrp .
Nice work mate.
Test on 4.1.B.1.13 ROM by Jader

vashta said:
Is this dual boot ? After I install modules(1).zip, after i touch 'reboot system', I end up in cwm again.
But after i reboot system (from that cwm menu), its back to TWRP again when i press vol down.
Anyway.. the wifi works, so far no facing problems. no bootloop etc.
In the info, it's still serene kernel.
* Kinda not used with this touch screen menu in twrp .
Nice work mate.
Test on 4.1.B.1.13 ROM by Jader
Click to expand...
Click to collapse
Yeah itll say that. I needed the .13 kernel as I wanted to base it on that, was away from my pc so I asked Rachit Rawat if I could use some files from his source and kernel. Its not supoosed to go into dual boot, may have added them by mistake to the new update. (Too early)

vashta said:
Is this dual boot ? After I install modules(1).zip, after i touch 'reboot system', I end up in cwm again.
But after i reboot system (from that cwm menu), its back to TWRP again when i press vol down.
Anyway.. the wifi works, so far no facing problems. no bootloop etc.
In the info, it's still serene kernel.
* Kinda not used with this touch screen menu in twrp .
Click to expand...
Click to collapse
When the notification light glows pink, Vol down enters TWRP, else when blue light+vibration, CWM Recovery.

Backup and Restore Workin GOOD on TWRP - Thanks for your work

Installing as well..
but mass storage doesn't. my PC didn't see my sdcard..

divest said:
Installing as well..
but mass storage doesn't. my PC didn't see my sdcard..
Click to expand...
Click to collapse
Working:
Flashing zips
File Manager
Backup (Haven't tried Restore)
Not Working:
ADB Sideload via TWRP
ADB and Mount USB Storage
Working on CWM recovery

Related

[01/06/11] ClockworkMod Recovery 3.2.0.0

ClockworkMod Recovery 3.2.0.0
Note:
Amend scripting (update-script) is no longer supported, was deprecated by Google in Android 1.5. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Current version: 3.2.0.0-(01.06)
Recovery_Optimus_2x_3.2.0.0-(01.06).zip
MD5: 1e97b2c8a0d4b84e11ec2f31e51f83ca
SHA-1: 2f7cd8cdf8e239886e31497dcffc9e5026606155
Installation:
Unzip the archive
Plug-in the USB cable and select enable the "debug mode"
Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
Done!
If you want to thank me, click the Thanks button.
Old versions:
Recovery_Optimus_2x_3.2.0.0.zip
Changelog: http://goo.gl/MAuLi (2011-05-30)
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!
All Ok with this version!! no /cache umount
Perfect ....
As always one step ahead....
When entering Recovery menu, device vibrates all time long. =/
Good to see you here. Gonna try tomorrow!
Sent from my LG-P990 using XDA App
Just installed. This version is perfect. Thanks.
how come i cant find it in rom manager?
Sorry for a noob question, but with previus version I cannot install CM7 #31.
Can I install this rom now?
ranrick said:
When entering Recovery menu, device vibrates all time long. =/
Click to expand...
Click to collapse
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
initrd said:
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
Click to expand...
Click to collapse
Yeah, 3.0.2.8 didnt work either. Only 3.0.1.4 works without vibrations.
Works like a charm.
Anyway to add this aswell: http://forum.xda-developers.com/showthread.php?t=1098745
So you have 2 option.
Internal Sd and External Sd?
That would be awesome!
USB mount doesn't work. Is it me?
Recovery shows 3.2.0.0 but the app still reports it as 3.0.2.8 - is this for compatibility?
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
75markus said:
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
Click to expand...
Click to collapse
yep. same thing (like at 3.1.0.1)...
just made a nandroid restore and recovery can't mount /boot during restore.
It's probably why we can't ( for exemple ) flash a CM rom ( after nandroid stock rom ) play with it and if you want to return to stock rom using your backup you get a bootloop
Quite common (and annoying), that. Happens each time I've restored a CM NANDroid, have to restore, then reflash CM.
hi. just a noob question
can i use this recovery to flash all the roms for the optimus 2x. like modaco, cm7 and other modaco based custom roms. ?
i been reading the forums and there are so many recoveries. im kinda confused.
Yes you can.
There are only 2 types of recovery in reality, this type (external SD) and the one I built for internal SD use. If you're not sure what you need, pick the external one (unless you don't have an SD card).
bit of a noob..but cant seem to be able to install it. can someone give me a guide to install this with a mac thanks in advance

[RECOVERY]Unofficial ClockworkMod Recovery v4.0.0.2(WIP)

Hi
Clockwork Recovery v 4.0.0.2 for Galaxy Ace
v2:
- working nandroid backup/restore!
For now i've disabled backup/restore of boot and recovery partitions. Restore of DATA, CACHE and SYSTEM is working fine.
If you have JTAG and want to test restore of boot/recovery please PM me!.
- it's based on KPH firmware + root in adb (both in normal and recovery mode)
v1:
Tested:
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens). It'll be fixed - thanks to tj_style!!
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested!!!.
How to flash (v2):
1. Download file from here .
2. flash it as PDA with odin
Mirrors:
Multiupload (thanks to peeter123)
I've removed recovery.zip - it was recovery.img packed with zip, not update for apply using stock recovery.
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.
Where did you get this?
Lovetz said:
Where did you get this?
Click to expand...
Click to collapse
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.
PabloPL said:
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.
Click to expand...
Click to collapse
You are elite, dude!;-) (Hackers)
This opens so many oppertunites to our Ace CyanogenMod being one of them. Have you got any further with these bugs? This is great. Thank you
Sent from my GT-S5830 using XDA App
awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!
I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua
PabloPL said:
Hi
Today i managed to run the newest Clockwork Recovery on my Galaxy Ace. It has some problem with graphics (as you can see on screenshots).
I've tested following options (and for me they are working):
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens)
I've also managed to create nandroid backup of all partitions (boot,recovery,data and system) but not tried yet to restore them.
Phone info
In recovery mode (sorry for terrible image quality)
I've attached packed recovery.img. it's based on KPH firmware + root in adb (in both boot and recovery mode) + su binary.
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested.
How to flash:
1. take KPH firmware
2. extract CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
- tar xvf CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
3. replace recovery.img with attached file
4. pack it back
- tar -H ustar -c boot.img recovery.img data.rfs system.rfs >ODIN_FILE.tar
- md5sum -t ODIN_FILE.tar >>ODIN_FILE.tar
- mv ODIN_FILE.tar ODIN_FILE.tar.md5
5. flash it with odin
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.
Click to expand...
Click to collapse
GREAT JOB MAN!
Go ahead, you are on it!!!
CHEERS!
The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App
kills999 said:
awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!
Click to expand...
Click to collapse
For now i've tested it only with creating backup of boot/recovery/data/system partitions and it generated without errors.
Jekle_Ace said:
The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine
PabloPL said:
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine
Click to expand...
Click to collapse
Can you upload ready-to-flash KPH file with CWM integrated?
Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App
tj_style said:
I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
View attachment 623281
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua
Click to expand...
Click to collapse
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.
Lovetz said:
Can you upload ready-to-flash KPH file with CWM integrated?
Click to expand...
Click to collapse
I have PDA file for odin with it, but i've messed something with Superuser.apk and you must install it by hand (only Superuser.apk, su binnaries are fine). Maybe when i'll have some free time - i'm working and studying (now have exams) - i'll upload it, if someone won't do this before .
Jekle_Ace said:
Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
For now i've tested wipe only on following options (and it worked fine):
- battery stats
- cache
- data (factory reset)
Sorry for double-postings
PabloPL said:
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.
Click to expand...
Click to collapse
Sure, You can see on my github soon. I'm not yet pushing to my github now.
because the project of Cyanogenmod port and Clockworkmod port for Galaxy Mini is pending now until i have the Galaxy mini back, you can see the progress in this thread.
I've add the double buffering to clockworkmod source, since Galaxy mini kernel doesn't suppot that.
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.
thx dude, i really need this.
tj_style said:
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.
Click to expand...
Click to collapse
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.
PabloPL said:
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.
Click to expand...
Click to collapse
Yup, i'm waiting to someone borrowing the galaxy mini to me and also waiting samsung to get released the 2.6.35.7 kernel source.
The source will come after 2.3 is offically released but we may be waiting a few weeks for it
Sent from my GT-S5830 using XDA App
Great work mate. Maybe you can work together with nprussel who is also trying to run cwm on g ace
@formatting partitions, there is indeed no support for ext4 in kernel
Sent from my GT-S5830 using XDA App

[RECOVERY][TWRP&CWM][Updated: 6-Feb-2013]Stock Kernel on Official Jellybean

Note: This has been deprecated in favour of LK for Xperia T
This kernel image is based on stock using the FreeXperia ramdisk method of loading stock and recovery. It also includes the new FOTA partition trick by Dees_Troy for easy updates in the future to TWRP.
Dees_Troy and I worked on figuring out the reason recovery binaries would not load on the stock kernel without patches, fixed this up in bionic, and rebuilt recovery linked against the fixed bionic.
F.A.Q
Q. The title says TWRP and CWM but when I boot recovery I only see TWRP. How do I get CWM?
A. TWRP is the default recovery, if you want CWM you should download the CWM update.zip in the second post and flash it with twrp.
Technical Info​
In 3.4 Qualcomm have changed the fb_var_screeninfo struct slightly. They have added an extra field called colorspace which increases the size of the stuct by __u32. When a binary linked against bionic tries to pass a struct the size of the old fb_var_screeninfo to kernelspace the application breaks as the kernel is expecting more data than it was given.
The patch to fix this in kernel solves the problem by removing one of the reserved fields, bringing the struct back to the same size it was prior to the new field being added. While this keeps compatibility with older recovery binaries, it does introduce the problem of needing a custom kernel to run recovery. Sony have not yet released source for 9.1.A.0.489 which means the kernel cannot be rebuilt without issues such as WiFi not working. The patch that Dees_Troy applied to the build system was to add the new colorspace field into the header for bionic which means the new recovery binary can run on an unmodified stock Sony kernel.
Flashing​
Boot device in fastboot mode:
Code:
adb reboot bootloader
Flash image with fastboot:
Code:
fastboot flash boot mint489stock.img
Source for TWRP available from here.​
Updates:
1. Updated image in first post to fix bug where creating a backup would fail and crash twrp.
2. Updated first post to show CWM in title and answer questions about how to get CWM.
Flashable zips:
In the first post it is mentioned about using the FOTAKernel trick by Dees_Troy to offer easy updates. The 2 zips attached to this post are examples of the ease of use.
flashCWM.zip - This will flash CWM to the FOTAKernel and replace TWRP as your recovery.
flashTWRP.zip - This will flash TWRP to the FOTAKernel and replace TWRP that is built into the image that was flashed to your device by fastboot, or to replace CWM with TWRP again if you used the flashCWM.zip
This also makes updates easier as you do not need to replace the kernel image you currently have flashed to your device.
Re: [RECOVERY][TWRP]Stock Kernel on Official Jellybean
Many thanks, can you just clear up one thing please, does Wi-Fi work on this image?
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
gregbradley said:
Many thanks, can you just clear up one thing please, does Wi-Fi work on this image?
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
Click to expand...
Click to collapse
Yes, wifi does work because it is just the stock kernel with TWRP added. I am running it right now with no problems.
I thought so, but I just wanted to make it obvious to all users as it was not 100% clear from the OP. I didnt have time to flash myself and check as I was just abbout to leave for work, now I am at work I will also flash it....
lilstevie said:
This kernel image is based on stock using the FreeXperia ramdisk method of loading stock and recovery. It also includes the new FOTA partition trick by Dees_Troy for easy updates in the future to TWRP.
Dees_Troy and I worked on figuring out the reason recovery binaries would not load on the stock kernel without patches, fixed this up in bionic, and rebuilt recovery linked against the fixed bionic.
Technical Info​
In 3.4 Qualcomm have changed the fb_var_screeninfo struct slightly. They have added an extra field called colorspace which increases the size of the stuct by __u32. When a binary linked against bionic tries to pass a struct the size of the old fb_var_screeninfo to kernelspace the application breaks as the kernel is expecting more data than it was given.
The patch to fix this in kernel solves the problem by removing one of the reserved fields, bringing the struct back to the same size it was prior to the new field being added. While this keeps compatibility with older recovery binaries, it does introduce the problem of needing a custom kernel to run recovery. Sony have not yet released source for 9.1.A.0.489 which means the kernel cannot be rebuilt without issues such as WiFi not working. The patch that Dees_Troy applied to the build system was to add the new colorspace field into the header for bionic which means the new recovery binary can run on an unmodified stock Sony kernel.
Flashing​
Boot device in fastboot mode:
Code:
adb reboot bootloader
Flash image with fastboot:
Code:
fastboot flash boot mint489stock.img
Source for TWRP available from here.​
Click to expand...
Click to collapse
Such a good news!I will port it to TX JellyBean firmware if you don' mind
gregbradley said:
I thought so, but I just wanted to make it obvious to all users as it was not 100% clear from the OP. I didnt have time to flash myself and check as I was just abbout to leave for work, now I am at work I will also flash it....
Click to expand...
Click to collapse
only for unlocked bl, correct?
hi,
i wanted to create with this version a backup, but it doesn't work.
it was just created the folder system,
the other folders such as data and boot not.
the created folder system, that was created after backup, is empty.
the 'backup' also takes only a few seconds, then the 'backup' is done.
what have i done?
installed the .img with instructions above.
boot xt into recovery, push backup, select system, data & boot, choose destination folder and start backup.
where is my failure?
hkjr said:
only for unlocked bl, correct?
Click to expand...
Click to collapse
Yes
MysticEnforcer said:
hi,
i wanted to create with this version a backup, but it doesn't work.
it was just created the folder system,
the other folders such as data and boot not.
the created folder system, that was created after backup, is empty.
the 'backup' also takes only a few seconds, then the 'backup' is done.
what have i done?
installed the .img with instructions above.
boot xt into recovery, push backup, select system, data & boot, choose destination folder and start backup.
where is my failure?
Click to expand...
Click to collapse
Same here....seems backup is not working
MysticEnforcer said:
the 'backup' also takes only a few seconds, then the 'backup' is done.
Click to expand...
Click to collapse
Updated first post with a fixed image.
Thank you very much, this is the best message of day.
Just flashed new image
Doing a backup and it seems to work...will update in few minutes when it is finished
EDIT:
It works
Backup complete in 385 seconds
FYI,
both times on rebooting system from recovery I initially got the grey triangle, both times it was only for 10-15 seconds before the phone rebooted...
Testing it now ....
Edit:
[Backup completed in 461 seconds] External SD card with compression on. No Grey triangle for me.
[Restore completed in 192 seconds] Restored backup without any problems. No grey triangle on second reboot either.
Seems to work great for me.
(only clock seems to be incorrect. 7 hours and 16 minutes behind)
Edit 2: thirth boot up seems to get stuck on grey triangle for about 15 seconds
Edit 3: Seems only the first time reboot after using the recovery the grey triangle is there. Rebooted the phone 4 times and only got the triangle 1 time.
Updated first and second post
USB storage does not work at all both on TWRP and CWM
tested 2nd version, works fine for me & no grey triangle :good:
romcio47 said:
USB storage does not work at all both on TWRP and CWM
Click to expand...
Click to collapse
Noticed that to
romcio47 said:
USB storage does not work at all both on TWRP and CWM
Click to expand...
Click to collapse
This appears to be more of a technical limitation.
The internal storage space is formatted ext4, so only linux would be able to mount that by default so it doesn't offer that.
With the MicroSD the issue seems to be a little more complex and may possibly need a custom kernel.
lilstevie said:
This appears to be more of a technical limitation.
The internal storage space is formatted ext4, so only linux would be able to mount that by default so it doesn't offer that.
With the MicroSD the issue seems to be a little more complex and may possibly need a custom kernel.
Click to expand...
Click to collapse
Thanks for the reply I guess we just have to wait for the kernel sources to be published
Besides another issue - in CWM wiping dalvik-cache does not work.
romcio47 said:
Besides another issue - in CWM wiping dalvik-cache does not work.
Click to expand...
Click to collapse
I can't reproduce this, if I wipe dalvik-cache in CWM it removes /data/dalvik-cache as it should.

TWRP v2.8.3.0

Hey there! It has been a while..
You may have noticed Team Win Recovery Project (short: TWRP) is available, but still not for our device,
and it seems I am the only one who spends time on making TWRP fully compatible
for our device which includes some bug fixes and modifications.
Both, TWRP and the kernel were compiled on my pc, using OS X Yosemite (10.10) as host system
from CM sources.
Use at your own risk.
I am not responsible for any damages on your device.
Click to expand...
Click to collapse
What is TWRP?
A fully touch driven custom recovery developed by TeamWin with a nice and easy to use user interface.
You can install your ROM's, backup it or restore it from/on your internal or external storage.
Backups can be compressed which saves alot of storage space and backups can have an individual,
user chosen name. Some unique features are an integrated filemanager, shell access,
rooting and the option to set a display timeout and display brightness.
TWRP includes alot of more features that I listed.. just explore yourself.
Download (also check the #Download page):
recovery263.img => TWRP 2.6.3.0 (STABLE)
recovery283_1.img => TWRP 2.8.3.0 (BETA)
For developers and for GPL reasons:
gkernel_x3_defconfig.zip => Used kernel defconfig (no kernel sourcecode changes have been made except mac os x specific kernel building fixes)
Sources (using cm10.2 sourcecode with cm p880 kernel):
p880_device: https://bitbucket.org/supergordon/device_lge_p880
p880_recovery_twrp: https://bitbucket.org/supergordon/twrp_lge_p880
p880_kernel: https://github.com/CyanogenMod/lge-kernel-p880
How do I install TWRP on my unlocked device?
Option 1: Fastboot
Code:
adb reboot oem-unlock
fastboot flash recovery recovery263.img
fastboot reboot
Option 2: ADB (put first the recovery image to the root directory of your internal storage)
Code:
adb shell
su
cat /sdcard/recovery263.img > /dev/block/mmcblk0p1
What device specific changes have been made?
Reboot options now properly working
Use CM's device specific fix to blank the display
Add missing external storage display name
Add missing screen brightness path
Modified display dimming delay
Fix rendering bugs that caused high battery consumption and device heat-ups
Add proper handling of the quadcore. Reduces backup time by about 10%.
UMS support (external storage only)
Since 2.6.3.0:
Using cm10.2 source
Using cm kernel
Exclude wiping sd-ext (bugfix for 2.6.1.0)
Since 2.8.3.0:
Now using twrp.fstab
Remove UMS support (TWRP has now MTP support. both internal and external storage are shown on the PC)
Add data/media[/0] button in Advanced page. Pressing the button toggles between /data/media and /data/media/0
Added missing option to (not) backup/restore recovery partition.
SD-Ext support (secondary partition of your microsd has to be ext4 formatted)
Using twrp sources from 30 december 2014
Click to expand...
Click to collapse
For changelogs on TWRP itself visit http://www.teamw.in/project/twrp2
My submitted patches on TeamWin's gerrit:
http://review.teamw.in/606
http://review.teamw.in/607
[July 1st] --> Both patches have been now reviewed and merged into the official TWRP sources.
Please report any bugs to help improving TWRP on our device.
Bug reports can be submitted here.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG Optimus 4X HD
Contributors
gordon0001
Version Information
Status: No Longer Updated
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-12
Current Beta Version: 2.8.3.0
Beta Release Date: 2014-12-31
Created 2013-09-17
Last Updated 2015-01-16
Reserved
Finally!!!...Thanks..Thanks..Thanks..
I follow you and your work and i hope that soon you release a gbootmenu 0.2 with twrp 2.5...
Or via terminale put the recovery.img in your sdcard and write:
1) su and agree superuser request
2) flash_image recovery /sdcard/recovery.img
Sent from my Wildfire S using xda app-developers app
gave thanks as appreciation =)
Sent from my LG-P880 using Tapatalk 4 Beta
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
saenta said:
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Click to expand...
Click to collapse
no, thats fine. twrp uses its own way to fix permissions.
Gesendet von meinem LG-P880 mit Tapatalk 2
@tiflao
Recovery.img is not in your fastboot directory. I'm 100 percent sure
Sent from my LG-P880 using xda app-developers app
tiflao said:
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
Click to expand...
Click to collapse
be sure you change to the directory where you stored recovery.img at your terminal(linux, osx)/command prompt(windows) with the "cd" command.
Thx guys
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
tool_king said:
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Click to expand...
Click to collapse
Hey!
Nice to see you like my work, but this thread is about TWRP and not GBootMenu. Post your questions about my other work in the correspondending release thread.
gordonbennet said:
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
Click to expand...
Click to collapse
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
gordon0001 said:
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
Click to expand...
Click to collapse
I forgot to add that I replaced the old one with your one in the toolkit's data files (just renamed the v2.5 to whatever the toolkit was using and deleted the old one).
Thanks for the concern though. Currently loving archived backups
TWRP is damn good! more functions, faster backup/restore etc., thanks!
Thanks for your work .. I love the recovery so much .. Thumbs up
Loving the touch,everything works as it should
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
http://review.teamw.in/606
http://review.teamw.in/607
Click to expand...
Click to collapse
gordon0001 said:
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
Click to expand...
Click to collapse
works perfect here
Sent from my LG-P880 using xda app-developers app

[RECOVERY] [NEW: CWM Graphics] CTR Recovery for Galaxy A5

CTR Recovery for Galaxy A5​
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support
you welcome brother
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro
Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?
corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands

Categories

Resources