Related
Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
rafatz said:
Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
Click to expand...
Click to collapse
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
rafatz said:
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
Click to expand...
Click to collapse
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
shimp208 said:
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
Click to expand...
Click to collapse
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
rafatz said:
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
Click to expand...
Click to collapse
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
shimp208 said:
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
Click to expand...
Click to collapse
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
rafatz said:
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
Click to expand...
Click to collapse
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
shimp208 said:
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
Click to expand...
Click to collapse
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
rafatz said:
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
Click to expand...
Click to collapse
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
shimp208 said:
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
Click to expand...
Click to collapse
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
rafatz said:
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
Click to expand...
Click to collapse
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
shimp208 said:
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
Click to expand...
Click to collapse
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
rafatz said:
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
Click to expand...
Click to collapse
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
shimp208 said:
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
Click to expand...
Click to collapse
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
rafatz said:
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
Click to expand...
Click to collapse
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
shimp208 said:
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
Click to expand...
Click to collapse
Thanks man! I was able to get a working CWMR.
The GITHUB I created for the device is at:
https://github.com/rafatzbr/android_device_asus_A66
I was able to build CM10.1 to Padfone, but it simply wont boot
stucked in the initial screen (not the bootanimation).
Any help is much appreciated.
Thanks!
** UPDATE **
Still stucked in boot screen
Any ideas?
rafatz said:
** UPDATE **
Still stucked in boot screen
Any ideas?
Click to expand...
Click to collapse
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
shimp208 said:
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
Click to expand...
Click to collapse
Thanks!
The problems is that the device is not in a bootloop. It is stucked in the first screen (on nexus devices it's the first google screen).
How I can get any logs from there, and which logs I would need?
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
IsoRec: Isolated Recovery for the Exynos 4210 / Galaxy S2 Family
UPDATE: This change has been merged into official CyanogenMod 11, 12.1 and 13 !!!
UPDATE: Official IsoRec TWRP 3 for i9100 is now available !!!
UPDATE: You can now use official i9100 TWRP on d710, i777 and n7000 !!!
UPDATE: Unofficial CM13 for i9100g by adxamg now supports IsoRec !!!
What is this about?
For too long the owners of Exynos 4210 family devices have been forced to use whatever recovery was chosen by their ROM or kernel provider of choice. These devices have a dedicated recovery partition that is apparently vestigial, and their bootloaders are seemingly unable to boot it. For this reason, the recovery ramdrive is typically bundled together with the kernel and the Android boot ramdisk in a monolithic binary, usually referred to as simply "the kernel" (both ramdrives share a single embedded kernel image).
This means that using your choice of recovery is a practical impossibility:
To change the recovery you must also replace the kernel and the Android boot ramdrive, possibly introducing issues with your ROM.
If you update your kernel or kernel-bundling ROM, you will loose your custom recovery if you had one.
If the kernel bundled with your choice of custom recovery does not boot, your Android will probably not boot either, and you will need a PC to debrick.
This already bad situation was exacerbated with CM 12.1, which includes a severely restricted recovery in official releases, to the point that some official maintainers have had to release semi-official kernels with alternate recoveries just to keep the XDA crowd from lynching them and ripping their limbs off.
What is IsoRec?
IsoRec (Isolated Recovery) is a very simple proposal aiming to solve this problem once and for all. ROM and kernel maintainers can keep on bundling their preferred default recovery, and users gain the freedom to override. Your kernel maintainer has to merge the IsoRec patch (or implement their own compatible solution) for you to be able to use an isolated recovery.
Kernel maintainers are kindly asked to respect their users' freedom by merging this simple patch. Your rate of adoption will make or break this initiative.
How does it work?
It is extremely simple. The IsoRec-patched boot sequence is as follows:
The bootloader loads the kernel and the unified ramdrive, then fires up the kernel.
The kernel starts and then invokes the unified ramdrive.
If booting Android, the unified ramdrive replaces itself with the nested Android boot ramdrive and invokes it.
Else if booting recovery, the IsoRec-patched unified ramdrive chooses the recovery ramdrive as follows:
if the raw recovery partition (/dev/block/mmcblk0p6) contains valid lzop-compressed data
and said data is a valid cpio archive
then use that cpio archive as the recovery ramdrive;
else use the default recovery ramdrive that comes nested within the unified ramdrive.
Finally the unified ramdrive replaces itself with the chosen recovery ramdrive and invokes it.
Where can I find the IsoRec patches?
These links are of interest only to kernel maintainers:
CyanogenMod patch: https://github.com/CyanogenMod/andr...mmit/9bfbaf337207359ef6aefe0a329a3b760054a6b7
Dorimanx patch: https://github.com/Lanchon/IsoRec-D...mmit/fe2288665fca2eb33426b71086fc7282ee687e68
Where can I find some IsoRec-compatible kernels?
In the future, hopefully everywhere. For now you can use my CM 11/12.1/13 TRIM-IsoRec kernels:
https://www.androidfilehost.com/?w=files&flid=47607
UPDATE: Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible !!! (link)
UPDATE: Unofficial Dorimanx builds by gsstudios are now IsoRec-compatible !!! (link)
Where can I find some IsoRec-compatible recoveries?
https://www.androidfilehost.com/?w=files&flid=47550
(The "disabler" files just clobber the contents of the isolated recovery partition so that the default recovery bundled with the kernel boots instead.)
UPDATE: Unofficial IsoRec TWRP 3 for i9100 by arnab has been released !!!
UPDATE: arnab and Dees_Troy teemed up to give us official TWRP 3 !!!
NOTE: TWRP 3 incompatibilities with CM 12.1 kernels have been fixed as of TWRP 3.0.2.0.
Note: I did not build any of the TWRP recoveries myself, I just bundled images shared by other developers. Big thank you to @arnab, @cyril279 and @dimoochka for the TWRP images! Recovery developers are welcome to reuse my flashing zips, just please remove my name from the filename AND the flashing script. Use lzo -9 compression and remember to sign your zips!
TWRP 3 for n7000, i777 and d710
You can use official i9100 TWRP on d710, i777 and n7000 with TWRP Patcher.
Installing TWRP 3 the Easy Way
There are many ways to skin a lolcat. You can easily flash a TWRP .img file (or any IsoRec recovery .img file) on the Exynos 4210 S2 family via adb from your PC. (Prerequisite: working adb connection and tools.) Try it out:
Download the 'twrp-X.X.X.X-i9100.img' file.
Switch to adb root by typing this in your PC:
adb root(Requires root on your phone. In CM, enable adb root in developer settings.)
Flash the recovery by typing this in your PC:
adb push twrp-X.X.X-X-i9100.img /dev/block/mmcblk0p6
WARNING: DO NOT MISTYPE ANYTHING !!!
If you do, you can HARD-BRICK your phone FOREVER. Better copy/paste to be sure.
WARNING: DO NOT TRY THIS IN ANY DEVICE EXCEPT EXYNOS 4210 S2 PHONES !!!
If you do, you can HARD-BRICK your device FOREVER. The 4210 devices are: i9100, n7000, i777, d710 and sc02c.
XDA:DevDB Information
IsoRec, Tool/Utility for the Samsung Galaxy S II
Contributors
Lanchon
Version Information
Status: Stable
Created 2016-01-12
Last Updated 2016-06-22
Reserved
Reserved
Sounds great. If this works reliable without side effects and if @Lysergic Acid merged your patch later (after it has proven that), this would make a dream come true for many here.
Thank you so much!!!
hi @Lysergic Acid,
i entered a change on gerrit:
http://review.cyanogenmod.org/#/c/127877/1
tests on the i777 are still pending.
http://forum.xda-developers.com/showpost.php?p=64778749&postcount=149
@Lanchon you are awesome. What a cool idea to fix a Samsung problem of putting the recovery and kernel together.
Sent from my Nexus 6P using Tapatalk
@Lanchon is there a possibility of some compatibility check? I mean, what happens, if the isolated recovery somehow does not match the kernel, e.g. I (hypothetically) start with CM12.1 plus isolated recovery and want to switch to CM13 with corresponding feature, but the kernels have to differ in some way so that the isolated recovery still in the partition fails. Can the isolated recovery be invalidated somehow?
Could this be done with Odin?
Have found a hilarious bug, don't worry, don't need support but if someone else can confirm, that would be fun.
Xposed 79, if Gravitybox is enabled (its settings don't matter.), and the screen is off, receiving a Skype message, reboots the phone. Completely reproducible here. LOL
Klaerchen said:
@Lanchon is there a possibility of some compatibility check? I mean, what happens, if the isolated recovery somehow does not match the kernel, e.g. I (hypothetically) start with CM12.1 plus isolated recovery and want to switch to CM13 with corresponding feature, but the kernels have to differ in some way so that the isolated recovery still in the partition fails. Can the isolated recovery be invalidated somehow?
Could this be done with Odin?
Click to expand...
Click to collapse
simple, if that happens then the person goes into android and clobbers the recovery partition from there. or writes a different recovery from there. or overwrites the kernel (manually or flashify style). or goes to download mode and uses odin or heimdall to flash a kernel or recovery or just to clobber. basically you are describing a situation of flashing the wrong kernel: the standard cure is using download mode.
that said, i thought of disabling the alternate check by pressing VOL DOWN during boot. but...
a) this affects several devices and, though IsoRec is compatible with all, the button setup could be different; that means investigating and testing, testing, testing with owners of obscure devices.
b) i don't know how to read button state directly using the kernel so i would have to research that.
c) most importantly, i don't have time to do a) nor b)! the patch took a few minutes; then building the kernels, packing the recoveries, testing, entering the change on gerrit, and writing all this down took a couple of hours already, hours that btw i shouldn't have spent on this AT ALL.
this is the best i could make it in the time i didn't have. IMHO the missing VOL DOWN functionality does not justify stopping people from having this. let's see what the CM gerrit people think. one thing is for sure: i don't have the time to make it better.
@Lanchon
Hi,
many thanks and much respect for your great work!
Im gonna test the IsoRec now, seems its working good so far,
hopefully the trim will not destroy my phone..
(Im still would be feel much more safe when kernel dont have trim functionality!)
Best regards
Lanchon said:
IsoRec: Isolated Recovery for the Exynos 4210 / Galaxy S2 Family
Click to expand...
Click to collapse
Badass. This is a really elegant solution - no need to reflash on every boot. Great job!
PS. It's awesome that you're also ripped. Are you a luchador in your day job?
dimoochka said:
Badass. This is a really elegant solution - no need to reflash on every boot. Great job!
PS. It's awesome that you're also ripped. Are you a luchador in your day job?
Click to expand...
Click to collapse
lol no, i'm just heavily invested in not looking the nerd i am
UPDATE: new devices, kernels, recoveries..
added:
CM 11 IsoRec-compatible kernels
CM (CWM-based) 6.0.5.1 IsoRec-compatible recoveries
for all supported devices:
d710
i777
i9100
n1000
this time i built the recoveries myself. these recoveries are the run-of-the-mill, old-style CM recoveries we all love and miss that used to come bundled with CM in the Kitkat days. they are compatible with CM 11 and CM 12.1 kernels, so you can use them with your Lollipop ROMs.
finally, i also added IsoRec disablers for the newly supported devices.
please note:
the (previously) published TWRP-i9100 recovery has a bug: adb sideload does not work.
EDIT: adb sideload works correctly on the newest i9100 TWRP (by arnab).
Wow, slick.
It seems I have a patch to add to the slim builds.
Happy flashing
-Cyril
@Lanchon
I read the OP, but it's not fully clear to me how it works. Where should I put the preferred recovery after having flashed the isorec compatible kernel?
Anyway thank you for the great job you did.
Sent from my GT-I9100 using XDA Free mobile app
@Lanchon
Latest twrp ramdisk as requested.
https://drive.google.com/file/d/0Bx_upRk6Kfw9MUU4UGdBel9xbDQ/view?usp=sharing
chrisXL said:
@Lanchon
I read the OP, but it's not fully clear to me how it works. Where should I put the preferred recovery after having flashed the isorec compatible kernel?
Anyway thank you for the great job you did.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
you flash it whenever you want, independently of the kernel. it has to be an IsoRec-compatible recovery; it CANNOT be a "legacy" (non-IsoRec; lol) monolithic kernel+recovery. look for some recoveries in the OP of this thread.
UPDATE: new TWRP for the i9100 contributed by @arnab.
thank you so much arnab!!!
cyril279 said:
Wow, slick.
It seems I have a patch to add to the slim builds.
Click to expand...
Click to collapse
thanks, that would be awesome!
Using
'kernel-Lanchon-TRIM-FreezeFix-TWRP-20160111-cm-12.1-i9100.zip'
right now.
In which order shall I flash:
1. kernel-Lanchon-TRIM-IsoRec-20160112-cm-11-i9100.zip
2. recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
3. Lanchon-IsoRec-Disabler-i9100.zip
- Which zip's will i have to put into CyanDelta to flash along with upcoming nightlies?
- Will I be able to go back to older TWRP etc. anytime?
- What is the benefit in one sentence?
I downloaded and installed (from twrp.me the new version 3.2.0-0 of the TWRP recovery for our Honor 7 and installed it using version 3.1.1-0. Installation OK but the device remains locked on bootlogo. I reinstalled version 3.1.1-0 with fastboot and the phone started without problems. I reinstalled version 3.2.0-0 with fastboot, the installation was successful but the phone remains locked on bootlogo. Has anyone tried?
yes, I did today and the same problem. I'm using 3.1.1.0
i wrote a message to Team TWRP and they removed v3.2.0.0 from the download site.
The TWRP team has released version 3.2.1-0-plank.img for the H7. Same problem as 3.2.0-0 except that this time the phone succeeds in rebooting in normal mode, but can not reboot in recovery (locked on bootlogo)... Back to 3.1.1-0 ... wait & see
p.s: I warned them
I thought the twrp team was a serious team. But do the recovery tests before publishing them?
no they don't test every release....
i assume there is an automatic build structure - as soon there are a new 'core'-version of twrp the changes are pushed to the device specific trees and at night the build will produce a new recovery for all devices....
TWRP 3.2.1-0 removed from the download site.
Hi, TWRP team response: "Thanks for the report. I will disable the job until the device tree is fixed. The files have been removed."
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Dattel01 said:
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=818070582850504177
thanks for your reply...
in the meantime i switched the device and my old H7 will have its eventide in the hand of my wife
Is you link a working copy or is it still the old version that crashes?
Twrp
Why there is no option for honor 7x in twrp?
Hi all,
I have been looking into compiling the kernel and TWRP for this device.
For the kernel, it compiles but does not boot (Will invvestigate later ).
The TWRP does not boot, most likely related to boardconfig.mk. I am unable to find the kernel base or offsets. Can anyone assist in discovering this information? I have tried unpacking boot.img and the current tools does not show this information.
Shaky156 said:
Hi all,
I have been looking into compiling the kernel and TWRP for this device.
For the kernel, it compiles but does not boot (Will invvestigate later ).
The TWRP does not boot, most likely related to boardconfig.mk. I am unable to find the kernel base or offsets. Can anyone assist in discovering this information? I have tried unpacking boot.img and the current tools does not show this information.
Click to expand...
Click to collapse
Hello. I manage to create TWRP for this device.
It is currently tested on a device running the laster firmware RUI 4.0_C.13 but it should work in RUI 3.0. Decryption works, MTP didn't yet.