Related
TeamWinRecoveryProject
Changelogs from last Release from Shaaan to mine
Code:
[B]2.4.4.0[/B]
* Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
* More fixes for the file selector
* Switched from using busybox md5sum to a direct C function call
* Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
* Update exFAT to latest commits
* Added a build flag to disable using the ioctl for screen blanking
[B]2.4.3.0[/B]
* Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
* Added a scroll bar to file selectors and listboxes courtesy of Tassadar
* Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
* Added a screen dim effect 2 seconds before screen off on some devices
* Finally fixed file selector crash (one of the joys of working with multi-threaded software)
* Fixed loading of screen timeout setting during startup
* Improvements and bugfixes to screen timeout code
* Fixed persistence of the 24 hour / military time setting
[B]2.4.2.0[/B]
* Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
* Add a brightness setting (requires device specific setup and only some devices have been added)
* Add a root checker and offer to install SuperSU if the device isn't already rooted
* Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
* Check and offer to fix root permissions if broken
* Add an option for a 24 hour clock display instead of AM/PM (aka military time)
* Move stock recovery reflash check to occur during the reboot cycle
* Add support for some MTK6xxx devices
* Change libtar to vfork to help prevent memory problems
* Add a "clicked" effect to most buttons, file selector, and listbox
* Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
* Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
* Other minor bugfixes and improvements
[B]2.4.1.0:[/B]
* Fixed a problem with mkdosfs that formatted sdcards to 2GB
* Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
* Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
* Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
[B]2.4.0.0:[/B]
* Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
* Support for exFAT formatted sdcards (also thanks to bigbiff)
* Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
* Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
* Added wipe cache and dalvik after ADB Sideload
* Replaced many system calls with their native C counterparts
* Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
* Fixed AOSP recovery commands to run after decryption on encrypted devices
* Improvements for building TWRP in CM10.1
* Other minor bugfixes and improvements
[B]2.3.3.0:[/B]
* Fix renaming backups with a space in the name
* Add decrypt button to mount page if you cancel decryption during startup
* Added ignore blkid flag
* Fixed handling of MTD partitions during mount
* Fixed some keyboard mapping issues on 800x1280 layout
[B]2.3.2.0:[/B]
* Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
* Fixed a bug with deleting a backup with a space in the name
* Added highlights on keyboard key presses
[B]2.3.1.0:[/B]
* Unmount system after boot to prevent some status 7 symlink failed errors on zip install
* USB Mass Storage code improvements
* Better handling of mounting storage during boot for some devices
* Fixed a problem with sizes of images (boot & recovery) after resetting defaults
* Fixed size errors during backup for some devices on recovery, etc.
* Fixed a problem with restoring backups when multiple archives were present
[B]2.3.0.0:[/B]
* Rebased onto AOSP Jelly Bean source code
* Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
* ADB sideload functionality from AOSP is included in 2.3, see this link for more info
* Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
* Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
* Faster boot times
* Added charging indicator while in recovery (only updates once every 60 seconds)
Issues
Code:
* Maybe your USB in recovery will be broken (so no mount storage to pc)
!!!It can happen that you brick your Device any other time, but this time NOT, when you flash this!!!
Downloads (My version)
Code:
[URL="http://tinyw.in/clY8"]twrp_2.4.4.0-cooper.zip[/URL]
[B]MD5-Sum:[/B] b812c764b80b2db2d6ae53dc4eb0f9de
Your will look like that if i done all right:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B]CREDITS:[/B]
* Dees_Troy and other devs for helping me
* original recovery from TWRP team (thx all)
* shaaan for recovery kernel
Wow man You rocks.... Hope we can get stable soon.... BTW any plan to make another version of CMX as it is full of bug
Why version 2.2.0 on screenshots?
Nice, finally Galaxy Ace has 2 custom recovery
Flashed it. Stuck on teamwin splash screen.
AW: [dev][recovery] twrp 2.4.1.0
yash295 said:
Flashed it. Stuck on teamwin splash screen.
Click to expand...
Click to collapse
good to know thanks man, i`ll look later into it, im away from home now
Sent from my GT-P1000 using xda app-developers app
Its fine man.. you are doing so much hard work for ace, least we can do is test things for you. keep it up.
OldDroid said:
good to know thanks man, i`ll look later into it, im away from home now
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
same heree
Re: [dev][recovery] twrp 2.4.1.0
So you fixed the mount errors?
Sent from my GT-I9070 using xda premium
AW: [dev][recovery] twrp 2.4.1.0
no shaaan it goes more deep into the complete recovery as i thought, now im debugging it with bigbiff from twrp team
Sent from my GT-P1000 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
Been looking forward to twrp for a while. Thanks for tackling it.
Sent from my GT-S5830i using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
no shaaan it goes more deep into the complete recovery as i thought, now im debugging it with bigbiff from twrp team
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Also Dees is making some rapid changes to the source to introduce new features.
I worked with him to add basic bml support. Now the recovery atleast recognizes the partitions!
Sent from my GT-I9070 using xda premium
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
Code:
* Based on CM10 Code (Next Release or Build will be on CM10.1 Code)
* Maybe you land into a Bluescreen
(you can still boot into Download-Mode so you still can flash another Recovery ;)
Its not a [for me its still easy to fix, but you Wont brick your Device!)
Click to expand...
Click to collapse
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
blue screen or twrp screen, no one reported before that you land on a blue screen, twrp screen is still possible because of wrong loaded bml partitions :silly:
ronedogg said:
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Dont came here acting like this !!
U know that tere's risks is this wip projects ... and this dev is working on a top recovery for an almost ancient ace so bare some respects!
i can see that you're ace had problems but keep calm re-download odin files and just put phone in download mode and flashem well
the only hard brick known to ace i rom manager wich screws the partition's of it! If u can enter download mode you're ace is not bricked! keep trying if u need any help just pm me and i'll be glad to help
take care
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
blue screen or twrp screen, no one reported before that you land on a blue screen, twrp screen is still possible because of wrong loaded bml partitions :silly:
Click to expand...
Click to collapse
LoL i wasn't being rude if i came across that way. I got cwm back now.
So what was my issue then. How can i use twrp. What else do i have to do. Just flash the zip with cwm, then what?
Sent from my Nexus 7 using XDA Premium HD app
AW: [dev][recovery] twrp 2.4.1.0
Any progress or isnt it possible to run twrp 2.4.x on our Aces?
Sent from my GT-S5830 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
TeamWinRecoveryProject
Changelogs from last Release from Shaaan to mine
Code:
[B]2.4.1.0:[/B]
* Fixed a problem with mkdosfs that formatted sdcards to 2GB
* Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
* Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
* Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
[B]2.4.0.0:[/B]
* Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
* Support for exFAT formatted sdcards (also thanks to bigbiff)
* Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
* Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
* Added wipe cache and dalvik after ADB Sideload
* Replaced many system calls with their native C counterparts
* Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
* Fixed AOSP recovery commands to run after decryption on encrypted devices
* Improvements for building TWRP in CM10.1
* Other minor bugfixes and improvements
[B]2.3.3.0:[/B]
* Fix renaming backups with a space in the name
* Add decrypt button to mount page if you cancel decryption during startup
* Added ignore blkid flag
* Fixed handling of MTD partitions during mount
* Fixed some keyboard mapping issues on 800x1280 layout
[B]2.3.2.0:[/B]
* Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
* Fixed a bug with deleting a backup with a space in the name
* Added highlights on keyboard key presses
[B]2.3.1.0:[/B]
* Unmount system after boot to prevent some status 7 symlink failed errors on zip install
* USB Mass Storage code improvements
* Better handling of mounting storage during boot for some devices
* Fixed a problem with sizes of images (boot & recovery) after resetting defaults
* Fixed size errors during backup for some devices on recovery, etc.
* Fixed a problem with restoring backups when multiple archives were present
[B]2.3.0.0:[/B]
* Rebased onto AOSP Jelly Bean source code
* Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
* ADB sideload functionality from AOSP is included in 2.3, see this link for more info
* Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
* Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
* Faster boot times
* Added charging indicator while in recovery (only updates once every 60 seconds)
Current State
Code:
* Based on CM10 Code (Next Release or Build will be on CM10.1 Code)
* Maybe you land into a Bluescreen
(you can still boot into Download-Mode so you still can flash another Recovery ;)
Its not a [for me its still easy to fix, but you Wont brick your Device!)
!!!It can happen that you brick your Device any other time, but this time NOT, when you flash this!!!
TWRP-2.4.1.0-cooper.zip
MD5-Sum: None
Your will look like that if i done all right:
Click to expand...
Click to collapse
Your source?
I do not respond to tech support via PM
AW: [dev][recovery] twrp 2.4.1.0
Shaaan said:
Your source?
I do not respond to tech support via PM
Click to expand...
Click to collapse
locally, added the reboot hack + bml partition layout to preserve a bricl
Sent from my GT-S5660 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
locally, added the reboot hack + bml partition layout to preserve a bricl
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
So basically you haven't fixed anything?
I do not respond to tech support via PM
Welcome to… Project Stable Boot for ICSROM!
It all started on 05 Feb 2013 when an xda member reported that the ICSROM boot images featured in Atrix Boot Emporium V3.0: http://forum.xda-developers.com/showthread.php?t=2124668
did not work: Dreaded Big-M followed by blank screen. No boot animation, even after several minutes, and no matter where the ROM was hosted, whether EMMC (standard) or SD (custom).
I started to wonder if “Dual Boot Atrix: Simplified and Standalone” was morphing into “Complicated and Co-dependent”.
So I duplicated the problem and documented my findings here: http://forum.xda-developers.com/showthread.php?t=2124668&page=2
Then I unpacked the ICSROM 146 boot image and tore into the /ramdisk directory. Ramdisk is that part of the Android boot image that initializes your ROM at boot time via multiple “init*.rc” (run command) scripts written in the Android “init” language.
Then, several days later, it happened:
I experienced a significant breakthrough with ICSROM on my AT&T Atrix
I discovered mainly that:
Ramdisk references approximately twenty different components (functions and services) that do not exist
Ramdisk does not reference several other components that DO exist
Memory allocations in the ICSROM 146 kernel command string differ significantly from default
Perhaps some or all of the missing components are (or were) available via legacy Motorola OTA updates. But if Motorola is done with ICS for Atrix 4g, then I think we’re done with the OTA updates.
So I decided to yank most of the init*.rc code containing broken references.
Also, I noticed that init.olympus.rc launches some encryption-related functions at boot time, whereas MROM ICS does not. So I yanked these as well. Then I quickly repacked the boot image and voila… ICSROM came up. Then I put my phone (and myself) to sleep.
09 Feb, 0430 PST: Disconnected charger, woke the phone and observed battery at 99%. Put phone back to sleep. Fifteen minutes later, woke the phone and observed battery at 98% --- only a 1% drop. Repeated the same test multiple times and got the same results.
I began to dream of 24 hour battery life again, lol.
I also noticed something related --- my phone was running much cooler, even when not in sleep mode. So later in the morning, I conducted several more experiments:
CWM factory reset (wipe /data and /cache), re-flash ICSROM-146-Rebuild.zip and reboot. Big-M followed by blank screen, as expected.
Next, unpack and repack ICSROM 146 boot image. Here’s the effect: Since my “modify-boot” tool set does not include a kernel command line, it effectively wipes any pre-existing command line in boot.img. So the only functional difference between the “stock” ICSROM 146 boot.img and the repacked one is the absence of the following command string:
Code:
Command line: [email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:d00:100:800,kpanic:2100:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA20703SX2
By contrast, the kernel command line built into my ROM is:
Code:
[email protected]:/ # more /proc/cmdline
more /proc/cmdline
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=s
dmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA2070GKY6
[email protected]:/ #
Please correct me if I am wrong, but I think that if no kernel command line is present in boot.img, the ramdisk “init” function reads the ROM default /proc/cmdline string after the kernel boots.
Note that the ICSROM 146 memory allocations differ significantly from those in /proc/cmdline.
Anyway, I repeated my previous experiment: CWM wipe /cache and /data, re-flash 146, power down and fastboot the custom ICSROM 146 boot image --- the only change being the absence of a kernel command line.
Results: ICSROM came up. Power up to Welcome screen was less than 3 minutes on first boot, and 50-55 seconds on subsequent boots.
But my phone ran very warm --- even at idle.
So I decided to incorporate all the ramdisk changes I had made the previous night and to repack (again, no kernel command line) and repeated the previous experiment: CWM wipe /data and /cache, re-flash ICSROM 146, power down and fastboot the repacked image (with no kernel command line).
Results: ICSROM came up in 3 minutes (expected), but THIS time, my phone was running cool.
Subsequent to these results, I ran CF Bench (free) many times. Scores generally hovered around 5000 --- slightly below the HTC Sensation, but still quite respectable for 1.0GHz --- though I think there's a wee bit of overclockin' here.
And now, I share these initial results in the form of an image to boot ICSROM 1.4.6 on EMMC. See links and instructions below.
[UPDATE 10 Feb 2013]: I did fastboot flash Rev00 directly after another failed boot with stock 146 boot.img --- and ICSROM came up. I did not need to wipe /data or /cache.
Fastboot image: http://www.mediafire.com/?bu604jfdm2axfsv
Flashable zip: http://www.mediafire.com/?5qndqe429eu3ltu
Preliminaries:
Rooted phone with unlocked bootloader
CWM Recovery 5.0.2.0 installed (or latest version of TWRP)
Fully charged, healthy battery
Instructions:
CWM Nandroid backup of current ROM (if you want to save /data and /cache)
CWM "wipe data/factory reset" (leaves existing ROM in place but clears /data and /cache)
CWM flash ICSROM-1.4.6-Rebuild.zip (takes a few minutes)
Do NOT reboot. Power down instead.
Fastboot method: Power up to fastboot and "fastboot flash boot boot-icsrom-146-Rev00.img"
CWM flash method: Power up to Android Recovery and flash boot-icsrom-146-Rev00.zip
[UPDATE 22 Feb 2013]: I received the go-ahead from ICSROM author upndwn4par to roll my Rev00 boot image into ICSROM 1.4.6
Link: http://www.mediafire.com/?5lbdhga26azhmd7
Instructions:
Already on ICSROM 146 with Rev00 boot image? Nothing to do.
Already on ICSROM 146 with original boot image? Simply flash zip... OR flash my Rev00 boot zip linked in OP (faster)
Coming from different ROM? Nandroid backup (unless you don't mind losing /data), then CWM wipe data/factory reset and flash zip
I cannot guarantee this boot image will work for you. And because of the complexity of ramdisk, I cannot simply provide a tweak configuration file.
All I can say is that with it, my AT&T Atrix runs much cooler, battery life is dramatically improved, and touch screen issues (like a home screen app ceremoniously launching when Power button is pressed) have disappeared.
Pending success of follow-on experiments, I will make an equivalent image available to boot ICSROM on SD card (for dual boot).
Some future planned work:
Continue scouring ICSROM boot.img /ramdisk, and remove “bad actors” as necessary
Study the init memory allocations and tweak if necessary
Try to reduce boot time
Given enough positive responses to boot-icsrom-146-Rev00.img, I will consider rolling it into my next release of Atrix Boot Emporium (presently V3.0)
Blessings.
Credits: upndwn4par (ICSROM).
couldnt you just post the boot.img with proper settings to make us able of using it? lmao
would be nice if you look into it, yet, you really could do what i just said, couldnt?
edit:sorry didnt see the link before DX
can you attach it in the post? im at the work and cant download it thanks to the folks from maintenance...
(in a flashable zip if you could )
So does this theoretically fix all the issues found with the ICS leak? Well except webtop....
jeffreygtab said:
So does this theoretically fix all the issues found with the ICS leak? Well except webtop....
Click to expand...
Click to collapse
no, it MAY fix some issues, including the not booting problem in ICSROM 1.4.6
Thanks for your hard work. It sounds as though it's been quite promising.
Good luck!
Odp: Project Stable Boot for ICSROM [09 Feb 2013]
About cmdline. If kernel is set correctly it reads cmdline from bootloader. It can be overridden in both directions of course (to read from kernel or from bootloader).
Sent from my MB860 using xda app-developers app
krystianp said:
About cmdline. If kernel is set correctly it reads cmdline from bootloader. It can be overridden in both directions of course (to read from kernel or from bootloader).
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Glad you're checking this out. I hope all our devs have a look.
Boot.img
sendust7 said:
Welcome to… Project Stable Boot for ICSROM!
It all started on 05 Feb 2013 when an xda member reported that the ICSROM boot images featured in Atrix Boot Emporium V3.0: http://forum.xda-developers.com/showthread.php?t=2124668
did not work: Dreaded Big-M followed by blank screen. No boot animation, even after several minutes, and no matter where the ROM was hosted, whether EMMC (standard) or SD (custom).
I started to wonder if “Dual Boot Atrix: Simplified and Standalone” was morphing into “Complicated and Co-dependent”.
So I duplicated the problem and documented my findings here: http://forum.xda-developers.com/showthread.php?t=2124668&page=2
Then I unpacked the ICSROM 146 boot image and tore into the /ramdisk directory. Ramdisk is that part of the Android boot image that initializes your ROM at boot time via multiple “init*.rc” (run command) scripts written in the Android “init” language.
Then, several days later, it happened:
I experienced a significant breakthrough with ICSROM on my AT&T Atrix
I discovered mainly that:
Ramdisk references approximately twenty different components (functions and services) that do not exist
Ramdisk does not reference several other components that DO exist
Memory allocations in the ICSROM 146 kernel command string differ significantly from default
Perhaps some or all of the missing components are (or were) available via legacy Motorola OTA updates. But if Motorola is done with ICS for Atrix 4g, then I think we’re done with the OTA updates.
So I decided to yank most of the init*.rc code containing broken references.
Also, I noticed that init.olympus.rc launches some encryption-related functions at boot time, whereas MROM ICS does not. So I yanked these as well. Then I quickly repacked the boot image and voila… ICSROM came up. Then I put my phone (and myself) to sleep.
09 Feb, 0430 PST: Disconnected charger, woke the phone and observed battery at 99%. Put phone back to sleep. Fifteen minutes later, woke the phone and observed battery at 98% --- only a 1% drop. Repeated the same test multiple times and got the same results.
I began to dream of 24 hour battery life again, lol.
I also noticed something related --- my phone was running much cooler, even when not in sleep mode. So later in the morning, I conducted several more experiments:
CWM factory reset (wipe /data and /cache), re-flash ICSROM-146-Rebuild.zip and reboot. Big-M followed by blank screen, as expected.
Next, unpack and repack ICSROM 146 boot image. Here’s the effect: Since my “modify-boot” tool set does not include a kernel command line, it effectively wipes any pre-existing command line in boot.img. So the only functional difference between the “stock” ICSROM 146 boot.img and the repacked one is the absence of the following command string:
Code:
Command line: [email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:d00:100:800,kpanic:2100:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA20703SX2
By contrast, the kernel command line built into my ROM is:
Code:
[email protected]:/ # more /proc/cmdline
more /proc/cmdline
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=s
dmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA2070GKY6
[email protected]:/ #
Please correct me if I am wrong, but I think that if no kernel command line is present in boot.img, the ramdisk “init” function reads the ROM default /proc/cmdline string after the kernel boots.
Note that the ICSROM 146 memory allocations differ significantly from those in /proc/cmdline.
Anyway, I repeated my previous experiment: CWM wipe /cache and /data, re-flash 146, power down and fastboot the custom ICSROM 146 boot image --- the only change being the absence of a kernel command line.
Results: ICSROM came up. Power up to Welcome screen was less than 3 minutes on first boot, and 50-55 seconds on subsequent boots.
But my phone ran very warm --- even at idle.
So I decided to incorporate all the ramdisk changes I had made the previous night and to repack (again, no kernel command line) and repeated the previous experiment: CWM wipe /data and /cache, re-flash ICSROM 146, power down and fastboot the repacked image (with no kernel command line).
Results: ICSROM came up in 3 minutes (expected), but THIS time, my phone was running cool.
Subsequent to these results, I ran CF Bench (free) many times. Scores generally hovered around 5000 --- slightly below the HTC Sensation, but still quite respectable for 1.0GHz --- though I think there's a wee bit of overclockin' here.
And now, I share these initial results in the form of an image to boot ICSROM 1.4.6 on EMMC: http://www.mediafire.com/?bu604jfdm2axfsv
Code:
fastboot flash boot boot-icsrom-146-Rev00.img
I cannot guarantee this boot image will work for you. And because of the complexity of ramdisk, I cannot simply provide a tweak configuration file.
All I can say is that with it, my AT&T Atrix runs much cooler, battery life is dramatically improved, and touch screen issues (like a home screen app ceremoniously launching when Power button is pressed) have disappeared.
Pending success of follow-on experiments, I will make an equivalent image available to boot ICSROM on SD card (for dual boot).
Some future planned work:
Continue scouring ICSROM boot.img /ramdisk, and remove “bad actors” as necessary
Study the init memory allocations and tweak if necessary
Try to reduce boot time
Given enough positive responses to boot-icsrom-146-Rev00.img, I will consider rolling it into my next release of Atrix Boot Emporium (presently V3.0)
Blessings.
Click to expand...
Click to collapse
I believe one of the keys to ICS for Atrix is to remove the broken init*.rc code. I wanted to check out the changes you made.
$ ./extractboot S7boot.img
Page size: 2048 (0x00000800)
Kernel size: 3864576 (0x003af800)
Ramdisk size: 287449 (0x000462d9)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing S7boot.img-kernel ... complete.
Writing S7boot.img-ramdisk.gz ... complete.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
I had trouble extracting your image. the ramdisk folder was empty. I expected to find the default.prop, multiple init files and ueventd files. I wish you the best of luck, I believe you are on the right track.
Qe process
Check out this link http://www.reddit.com/r/Android/comments/v7dtc/carrier_iq_round_2_motorolas_android_devices_are/
"This morning, Hashcode (a major developer of ROMs for Motorola's Android devices and the Kindle Fire) posted this at droidforums.net:
I took the liberty of disabling "Qe" which logs all of the differences in the current OS compared to how it comes from Motorola. It's a lag monster on the bootup, and an invasion of privacy.
It caught my attention so I asked him more about it and this is what he said:
I first noticed it in the RAZR and Droid 4 GB ROMs. The process "qe" is started during the initial boot services. It does a full scan of the /system dir and stores the md5 of every file. It then compares that information to a file in /pds which contains the md5sum file listing of the stock ROM as it was originally from Motorola. As it diffs the 2 listings, any differences are placed in /data/misc/qer and eventually posted back to Motorola.
You can see the report on any stock phone by looking in there.
There is no way to disable it in the regular phone ROM without using a 2nd init process to change the ramdisk files as the binary "qe" is in /sbin and the service is started in the init.*.rc files.
Does anyone else find this unacceptable? I may be overreacting, but this seems disconcerting to say the least."
Disabling this service should Improve boot time dramatically. I am trying to build a better boot.img, I hope this helps. extracted original leak boot.img, Deleted xbin folder containing qe bianry, qee.dat, qem.dat, remove service calls from Init*rc files and repacking should help with boot process.
@sendust7 your phone have the same tegrapart like mine, do you have screen shaking issues?
The battery drain is the major issue I have, and the only reason not to be my daily rom!
Thanks!
Sent from my MB860 using xda app-developers app
clemare said:
The battery drain is the major issue I have, and the only reason not to be my daily rom!
Thanks!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
So, what I have to do to test the leaked rom with this modificacion?
Sent from my MB860 using xda app-developers app
Here is the flashable zip
http://db.tt/pC7GXsBP
Happy Flashing[/SIZE]
Nice detective work. One thing to keep in mind is that so many of the problems with ICS are device dependent - something that goes well beyond tegrapart. I often wonder if this played a part in Moto's decision to bail on ICS.
It is interesting to note that some users that were able to run ICSROM v1.4.4 with no problems (other than battery life) suddenly started having boot problems with v1.4.5. The only difference between the two builds is that I added init.d support. I wonder how this fits in to your research?
As always, nice work!
So if I flash icsrom and then the boot img from the post 2 above this one it will be safe? Will I then have ics with better battery life?
Thanks
xda premium hd is rubbish
blttalas said:
Here is the flashable zip
http://db.tt/pC7GXsBP
Happy Flashing[/SIZE]
Click to expand...
Click to collapse
blttalas, your CWM fix package does not work. Still cannot boot release 1.4.6 from ICSRom.
upndwn4par said:
Nice detective work. One thing to keep in mind is that so many of the problems with ICS are device dependent - something that goes well beyond tegrapart. I often wonder if this played a part in Moto's decision to bail on ICS.
It is interesting to note that some users that were able to run ICSROM v1.4.4 with no problems (other than battery life) suddenly started having boot problems with v1.4.5. The only difference between the two builds is that I added init.d support. I wonder how this fits in to your research?
As always, nice work!
Click to expand...
Click to collapse
Thank you so much. I will look into it
jhonnyx said:
blttalas, your CWM fix package does not work. Still cannot boot release 1.4.6 from ICSRom.
Click to expand...
Click to collapse
I can corroborate this. The CWM Package doesn't work, but the boot.img booted with no problems through fastboot flash.
littleemp said:
I can corroborate this. The CWM Package doesn't work, but the boot.img booted with no problems through fastboot flash.
Click to expand...
Click to collapse
So does the new boot.img really enhance battery life; cool the phone and halt reboots?!
Thanks.
jeffreygtab said:
So does the new boot.img really enhance battery life; cool the phone and halt reboots?!
Thanks.
Click to expand...
Click to collapse
littleemp said:
I can corroborate this. The CWM Package doesn't work, but the boot.img booted with no problems through fastboot flash.
Click to expand...
Click to collapse
Rev00 flashable zip: http://www.mediafire.com/?5qndqe429eu3ltu
This project is very new. At this point, all I can say is that it works on my AT&T Atrix --- Boots every time in every configuration I've thrown at it so far.
And as I recall, I have only had one random reboot, and that occurred while I was testing a makeshift variant several days ago.
** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Droid Bionic and see for yourself.
Instructions:
1. Make a Titanium Backup and/or backup in recovery of your current Android (or just keep it on another rom-slot). This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Bionic Mini-Android base for Ubuntu Touch and place it on your device:
[03/01] http://goo.im/devs/Hashcode/targa/ubuntu-phablet/ (use the newest one)
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
4. Reboot into Safestrap. Create a NEW 2GB ROM in the #4 slot.
IMPORTANT:
4a. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND.
5. Reboot and Enjoy
FIRST BOOT TAKES A LONG TIME. AND THERE'S NO BOOT ANIMATION. BE PATIENT (MAYBE 3-4 MINUTES).
WHAT WORKS:
Display
Touch screen
Wifi
Audio
WHAT DOESN'T WORK:
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
No screen timeout / auto blank -- be careful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch
thank you... let's give it a shot!
So does data work yet? Because you never mentioned data yet.
Sent from my XT875 using xda premium
silvernirvash said:
So does data work yet? Because you never mentioned data yet.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
wifi work... boot up in +/- 2minutes
So no data yet lol. Oh and where are the system settings I don't see any other then the quick toggle settings and the soft keys don't actually do anything it seems. Oh also they are always lit up...... Kinda annoying. But so far pretty cool lol
Sent from my XT875 using xda premium
Big thanks Hashcode, I will give this a try
Whaaaaaaaat!? Ubuntu touch on the locked down Bionic!? I'm happy to see your still holding it down hear hash, even with the DNA being fully unlocked and s-off we don't have even 1/4 of the development that the bionic has let alone a nexus phone. Kudos brudda.
Sent from my HTC6435LVW using xda premium
Is raring the latest build? Quantal seems downloads an empty zip, and it says it was last updated today. Thanks!
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
I had a little trouble installing. I created a 2 gig slot using #4 and on the first file I got an error message. The log went like this...
Installing update...
assert failed:getprop(ro.product.device) =="groupe
E: error in /sdcard/download/raring-pre-installed-armel+(status 7)
error flashing zip '/sdcard/download/raring-preinstall
Does anybody know what the problem could be? Bad download maybe? Thanks in advance!
Sent from my DROID BIONIC using xda app-developers app
ok so got that issue resolved an I gotta say, sweet rom can't wait til it's stable enough to use as a dd!
Sent from my DROID BIONIC using xda app-developers app
Not having any luck with this on my Droid Bionic.
SS 3.11
2GB Slot on ROM#4
raring-preinstalled-phablet-armhf.zip (6/1/13)
phablet-20130412-cm-targa.zip
Installs fine, boots up to blank screen and just sits there...
I've let it sit for 30 minutes...It does nothing...
The hw keys are lit, and the screen is backlit.
What am I doing wrong?
TIA,
Flash
..
If you updated to official rooted jellybean you are out of luck, you can try to use dd command from linux terminal to copy each partition back to .905 to your phone while in recovery but you might brick your phone while doing it, I posted what all the partitions were if you have a large enough sdcard you can put every IMG on your phone in recovery from and type
dd if=/sdcard/IMG of=/dev/block/correctimgtoreplace
Skip replacing recovery and hope you didn't brick your device. I have done it before to get back to 895 but I got pretty close to bricking my phone while doing it. I finally got it to work but wouldn't recommend doing it unless you know alot about linux/Android and your phone.
mbmloader mmcblk1p1
mbm mmcblk1p2
mbmbackup mmcblk1p3
ebr mmcblk1p4 this is the extended partition for the rest of the partition table
bploader mmcblk1p5
cdt.bin mmcblk1p6
pds mmcblk1p7
lbl mmcblk1p8
lbl_backup mmcblk1p9
logo.bin mmcblk1p10
sp mmcblk1p11
devtree mmcblk1p12
devtree_backup mmcblk1p13
bpsw mmcblk1p14
boot mmcblk1p15
recovery mmcblk1p16
cdrom mmcblk1p17
misc mmcblk1p18
cid mmcblk1p19
kpanic mmcblk1p20
system mmcblk1p21
cache mmcblk1p22
preinstall mmcblk1p23
webtop mmcblk1p24 has been linked to vendor on ICS and up lost a lot of space in update
userdata mmcblk1p25
emstorage mmcblk1p26
sgpt mmcblk1p277
Has there been any work done since this thread was made? If there's been an update I'd like to know what the update contains.
Sent from my XT875 using xda premium
I think that Ubuntu for phones will be great on Bionic. We've already got convergence, in a way, and if you could run Android apps on it, I'd be set!
Sent from my XT875 using xda app-developers app
I don't see why it couldn't run android apps on it I mean under the skinning they are both Linux so..... It's very possible. Hell the new bb10 phone allows side loading of android apps and that isn't even based on Linux LOL
Sent from my XT875 using xda premium
Does 3g work on this yet? It's the only reason I wont try it. Plus last time iI tried it it sat on the black screen for about half an hour before I pulled the battery and went back to my normal rom.
There is a new Daily Driver version of ubuntu-touch 13, old quantel is 12, now there is saucy. you should take a look at it
Has anyone managed to get this to successfully boot? If it works, I'll try it.
Has anyone managed to get this booting, or tried the latest stable? With the newer version of safestrap, is it required to have such a large partition?
I'm starting to worry. Every Lollipop ROM I've tried has problems... EXCEPT Ivan's.
Resurrection Remix - 20150418-cancrosl (stock partitions, I assume?)
The following processes crash on startup: PHONE APP, android.process.acore
XenonHD - 2015-04-18 release, stock partition version
I get this when installing...
Code:
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed: no such volume
And when I reboot the phone it's stuck in the XenonHD boot logo forever D;
The message appears anyways, whether I have TrueDualBoot enabled or not.
Euphoria OS - 20150501 -lstock (stock partitions, I assume?)
The very first thing that happens upon boot is the Clock app crashing.
Mokee - 2015-04-29 Release
MoKeeLauncher crashes on startup
BlissPop 2.2 - 20150326-1153
The following processes crash on startup: android.process.media, android.process.acore, com.android.phone, Messaging app...
_____________________________________________________________________________
- For all of them I do the 3 wipes before installing: data, cache, dalvik cache.
- I'm using CWM Recovery, v6.0.5.1(R11)
- All the installs have been made in System1
- As said, the only Lollipop ROM that works fine is Ivan's 5.4.11
Am I doing something wrong? What can I do to fix those troubles?
Huh, quick update.
I installed TWRP (at the cost of losing the ability to switch to System2), used the Repair Filesystem function and tried BlissPop. Now it works without anything crashing.
EDIT: Same with Mokee.... stupid CWM, if it had a Repair Filesystem it would've saved me a lot of time =/
wanny! said:
huh, quick update.
I installed twrp (at the cost of losing the ability to switch to system2), used the repair filesystem function and tried blisspop. Now it works without anything crashing.
Edit: Same with mokee.... Stupid cwm, if it had a repair filesystem it would've saved me a lot of time =/
Click to expand...
Click to collapse
good you solved yourself mate :d
Good for you. Btw, what repair filesystem does? Will it wipe your partition as well?
Sent from my MI 3W using xda Forum
solazz said:
Good for you. Btw, what repair filesystem does? Will it wipe your partition as well?
Sent from my MI 3W using xda Forum
Click to expand...
Click to collapse
Nope. From what I think, it's like doing a chkdsk in Windows. Nothing is wiped.
Wanny! said:
Nope. From what I think, it's like doing a chkdsk in Windows. Nothing is wiped.
Click to expand...
Click to collapse
Ok, thanks! Will try it.
Sent from my MI 3W using xda Forum
Hello and welcome to CM-13.0 Beta 1 !
first of all a BIG thank you to @Adrian DC wich had constributed also to this rom (he fixed the camera and helped me with the other stuffs )
Known bugs:
- sometimes the device will bootloop (only in starting phase )
USE THE FLASHABLE HOTFIX for that
- sometimes RIL may not start (on bootup)
if you encounter one of these bugs please press and hold vol+ and powerbutton to FORCE SHUTDOWN and then reboot again
Other "bug":
- selinux disabled until i patched it
Sourcecode can be found on my git:
github.com/sdtbarbarossa
How to install:
1. make sure your internal SDCard is formated to exfat (you can use Whiteneos TWRP to get that)
2. clean install the rom ( wipe cache & data & system ) [alternativeley dirtyflash.... but then dont report bugs!]
3. flash gapps (i use OPENGAPPS - ARM - 6.0 - PICO )
4. reboot
5. wait several times
Downloadlink:
https://www.dropbox.com/s/7tr42vcejk1u1js/cm-13.0-20160403-UNOFFICIAL-mint.zip?dl=0
link is up
Sent from my Xperia T using XDA Free mobile app
error executing updater binary in zip
SonyXperiakiasT said:
error executing updater binary in zip
Click to expand...
Click to collapse
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
?
Got that myself, it doesn't work with TWRP 3, you need an older version, i used TWRP 2.8.6.0
(fix) flash it with philz_touch_6.12.8
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
For me installation works with TWRP from 12.1 kernel. After creation of dalvik files it never ended with "apps are starting". Killed the device (Vol+ & Power) and got never ending boot animation... tried to reinstall. Now got "Operation not supported on transport endpoint". Restored "boot" from last 12.1 nand backup, rebooted to (that funny colored) revovery, wiped again, reinstalled (BTW open_gapps-arm-6.0-pico-20160403 in queue) and now..... hey, I get a PIN screen! Wifi & Google sign in works without problem. Developer options, root access, adb shell, seems alright for now - good night and many thanks to SdtBarbarossa!
vladut.alecsandru said:
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
Click to expand...
Click to collapse
From Xperia M I know it's very tricky or nearly impossible... For me the "onboard solution" for root access is okay. (did not try yet if it really works...)
Actually you are right, I didn't enable the root access from developer options the first time.. but it works and you don't need supersu
But I had no service and after a reboot it started to bootloop again..
bootloop after a reboot
Reinstalled again.. and after each app install I rebooted to see what might cause the bootloop
For me at least, it started to bootloop after I installed and gave root access to titanium backup.
1. the bootloop is a known bug lile i said ( it is that the mediaserver dont start for a unknown reason... depending on the random queue of loading librarys )
atm i prefere everyone to reboot not often x)
bootloops should be solvable by hardboot ( vol+ and powerbutton )
then there are 2 cases:
1.lib a gets loaded before lib b => it boots
2.lib b gets loaded before lib a => it loops
there is nothing how i can controll that atm
2. if you habe trouble flashing the rom please send me a log
3. guys can it be that the no service bug only appears on first boot?
Sent from my Xperia T using XDA Free mobile app
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
I'll probably test the rom today. Keep up the good work SdtBarbarossa.
mankokoma said:
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
Click to expand...
Click to collapse
yes i know... thx for the log its the same i get... this bug is just as random as i explained above... hard to find the real reason
so except for the bootup problems ... how is the rom? any other problems?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
... how is the rom? any other problems?
Click to expand...
Click to collapse
First impression's really good. Much snappier than 12.1 - expected. It was a little tricky to change the 'sdcard0' to vfat. As suggested I tried to do it with the 12.1-kernel-TWRP... first did a backup to ext-sd but after copying with TWRP-filemanager it crashed, automatically rebooted the 13-ROM, killed the dalvik and boot-looped At least sdcard0 data were transfered!
So restored kernel & data from nand backup and after successful boot, tried to format sdcard0, mentioned "corrupt" in settings-Storage&USB but ERROR occurred. So I tried with adb shell
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p15
OR
Code:
mkfs.exfat /dev/block/mmcblk0p15
BOTH returned Errors (that's why I tried both) but can't remember which one was successful
In settings-Storage&USB still "corrupt", but after reboot (without problems) there was sdcard0 with 11 GB free - yeaaaah!
Pushed back all the Osmand Map Stuff and so on and now also
Camera does not complain any longer because of missing sdcard and takes photos.
GPS fix is fast and stable... That's all for now!
Ahh and yes, I can do phone calls & sms (aber das ist ja nebensächlich)
hi!
so tried last cm13 beta, thanks for your work first of all.
had same problems as @mankokoma trying to format the sdcard to vfat via WhiteNeos latest twrp (same problem I reported multiple times in the old thread if you remember), it simply does not work, sdcard stays in ext4.
then I did run the commands mankokoma suggested in adb and then I could see vfat for sdcard in twrp. but now in twrp sdcard is not accessible at all. it doesn't mount etc had to use usb otg to install cm13. and in twrp 3.0 provided with cm13, again sdcard is not accessible at all ;(
btw, I full wiped (system, cache, data and dalvik), and thanks to otg I installed cm13 beta. upon very first reboot, phone optimized all apps, but then got stuck at "Android is starting - Starting apps message" forever. I had to force shutdown and reboot, then it booted fine and could pass the wizard.
sim was detected fine.
but I see internal sdcard always damaged in settings. rebooted countless times, didn't fix the problem. and camera app FCs, probably because I don't have any sdcards available...
If I click on the sdcard damaged, and then configure and format, I get an error message, and it doesn't work.
so the rom is still not usable for me atm very sad because the rom seems very promising and so fast!
EDIT: settings do FC here when trying to enter developer settings so can't enable builtin root?!
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
yes but how?? please tell me how to do that... in twrp 3.0 it keeps giving errors...
and by the way in twrp I see file system for sdcard is already vfat now! :silly:
nvm! trying again and again in twrp I always got error messages but now in settings it seems it is recognized! great! and camera started to work now will test it wonderful!
ps: FC in developer settings is still there... how did you get root? with supersu?
EDIT: and recording videos does not seem to work?
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
hamidmf12 said:
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
Click to expand...
Click to collapse
Try this, it worked for me :
http://forum.xda-developers.com/showpost.php?p=65265674&postcount=10