Related
i ve tried doomlord and superoneclick but they all give me an error like '/dev/log/main : No such file or directory an it doesnt root.
Logging must be enabled...
http://forum.xda-developers.com/showthread.php?t=1369783
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip or the superoneclick v2.3.1
DooMLoRD_v3_ROOT-zergRush-busybox-su.zip From here http://forum.xda-developers.com/show....php?t=1321582, and superoneclick from here http://shortfuse.org/
Unzip, connect usb (dont mount SD) and run runme.bat to dooMlord
Let it do the magic, and when phone reboots, its rooted
devil_costa said:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip or the superoneclick v2.3.1
DooMLoRD_v3_ROOT-zergRush-busybox-su.zip From here http://forum.xda-developers.com/show....php?t=1321582, and superoneclick from here http://shortfuse.org/
Unzip, connect usb (dont mount SD) and run runme.bat to dooMlord
Let it do the magic, and when phone reboots, its rooted
Click to expand...
Click to collapse
done it
my X5 is live n kickin!!
sanpsa said:
Logging must be enabled...
http://forum.xda-developers.com/showthread.php?t=1369783
Click to expand...
Click to collapse
thanks i forgot about logging. its rooted now
Tnx, only bad thing now is that i cant replace recovery.img
Tried with atleast 4-5 programs on the market. Gief my pink screen back xD
Sent from my U8800 using XDA App
This post may help a few people:
[U8800] [How To] Root, Install ClockworkMod + Remove Bundled Apps from Official 2.3.5
the rootexplorer maybe help you
If, like me you can't open the hidden menu with the *#*#2846579*#*#, install the Hidden Menus app from the Play Store. Once there, go to .ProjectMenuReceiver ... and just continue to follow the howto in the first page of this post using SuperOneClick 2.3.3. My U8800 only rooted at the second attempt, the first one didn't run to the end, but the second one went just fine and ended with "Device rooted" message.
Good luck
Note: My U8800 was bought in Portugal through the operator TMN and the rom is the 2.3.5 Official from Huawei
I am running CM
So I disabled the slider unlock, but it stopped recognizing my gesture for some reason and I cannot figure out how to login to my phone. Running stable build of CM7.1, not sure if I can change that setting somehow from ADP or do something from a terminal... Any ideas?
When I say gesture, I am not referring to the password based on the motion with the dots, I am saying the screen where the unlock / silent toggle was has been disabled and I cannot get passed there.
Your help is appreciated
Did u try unlock with menu button?
I remember that from cm7
Sent from my MB525 running 4.5.1-134 DFP 231 DEFY+ ROM...
using XDA App
No menu button doesn't do anything....
Do you know WHERE this "Slider Disabled" setting is stored? I could go in thru ADB and change it but I don't know where to look.
Here are the things I have tried already
----
Attempt 1:
$ ./adb -d shell
# cd data/data
# sqlite3 ./com.android.providers.settings/databases/settings.db
sqlite> update system set value=1 where name='lockscreen_disabled';
sqlite> .exit
# reboot
Attempt 2:
adb shell
input keyevent 82
---
Neither of these worked. I think the solution should be in the updating the settings.db, but maybe its a different row/record that contains "ENABLE slider"?
Help would be appreciated!
could deleting the the offending theme restore to normal?? Just thinking out loud here ^^
don't know much about adb
Okay. No help here, but I found a fix and I thought i would share it since I have seen that apparently other people have had this problem with no help as well other than "Wipe and reinstall rom"
This app fixed it!
https://market.android.com/details?id=se.curity.android.screenlockbypass
Just make sure you follow the instructions, you have to install the app, than install any other random app and BAM- unlocked phone! Sweet
BACKSTORY
* had root, used (djrbliss exploit I think)
* had ICS custom rom installed
* didn't use for a week or so
* went back to it and it was puting out 'not responding' errors constantly
* decided to install OTA ICS and maybe upgrade to JB
STORY
* Can't install OTA ICS because get errors
* Tried to install OTA ICS without removing CWM: http://www.thinkpadtabletforums.com...tall-cwm-nstall-ota3-ics-row/msg5980/#msg5980
* Tried to install OTA ICS by removing CWM:http://forums.lenovo.com/t5/ThinkPad-slate-tablets/OTA2-US-Root-CWM-update-instructions/td-p/682841
* Tried this thread, seemed to be working: http://forums.lenovo.com/t5/ThinkPa...users-having-trouble-with-the-ICS/td-p/785959
also here:
http://www.thinkpadtabletforums.com...s-if-you-are-having-problems-updating-to-ics/
* FIRST MISTAKE:* didn't check to make sure that rootkeeper looked right after installing the nadroid backup (though I'm sure it wasn't completely disabled). When I did go in there it showed **4** buttons: "protect su" "backup su" "restore su" and "delete backup su" (I think)
*Now I'm between a rock and a hardplace
* I had a su-backup file, but no matter what--renaming, moving to different place, pulling and pushing to/from local computer I could not actually run su-backup to get root. I kept getting 'permission denied' errors. It was owned by root:root
* SECOND MISTAKE: Did a factory reset. This removed my non-working su-backup. but...
* now I'm between a rock and a hard place*
* I successfully removed CWM
* since I don't have root, I couldn't get in and copy over the proper busy box version
* since I couldn't copy over the proper busybox version, I get assert errors (I think that's why) so I can't upgrade to the OTA ICS
* since I don't have root I can't restore nandroid or any older version (I'm stuck on 0089)
WHAT I'VE TRIED
* Installing almost any available US version on lenovo's FTP site
* Rerooting:
* the djrbliss exploit doesn't seem to work (I get 'exploit failed) I assume the exploit was pached on 0089?
* the opdecikel (yareftpt) exploit doesn't work either, it goes though all the steps but when I try and test if I have root (adb shell; su) I gett 'permission denied'
* Installing the OTA ICS doesn't work because of these assert/busybox errors
I've been dealing with this for 10 hours straight and I'm just about to sell it on ebay for parts and buy a nexus 7.
Any suggetions you may have would be a big help as I'm at the end of my rope right now.
jack
jacksmind said:
BACKSTORY
* had root, used (djrbliss exploit I think)
* had ICS custom rom installed
* didn't use for a week or so
* went back to it and it was puting out 'not responding' errors constantly
* decided to install OTA ICS and maybe upgrade to JB
STORY
* Can't install OTA ICS because get errors
* Tried to install OTA ICS without removing CWM: http://www.thinkpadtabletforums.com...tall-cwm-nstall-ota3-ics-row/msg5980/#msg5980
* Tried to install OTA ICS by removing CWM:http://forums.lenovo.com/t5/ThinkPad-slate-tablets/OTA2-US-Root-CWM-update-instructions/td-p/682841
* Tried this thread, seemed to be working: http://forums.lenovo.com/t5/ThinkPa...users-having-trouble-with-the-ICS/td-p/785959
also here:
http://www.thinkpadtabletforums.com...s-if-you-are-having-problems-updating-to-ics/
* FIRST MISTAKE:* didn't check to make sure that rootkeeper looked right after installing the nadroid backup (though I'm sure it wasn't completely disabled). When I did go in there it showed **4** buttons: "protect su" "backup su" "restore su" and "delete backup su" (I think)
*Now I'm between a rock and a hardplace
* I had a su-backup file, but no matter what--renaming, moving to different place, pulling and pushing to/from local computer I could not actually run su-backup to get root. I kept getting 'permission denied' errors. It was owned by root:root
* SECOND MISTAKE: Did a factory reset. This removed my non-working su-backup. but...
* now I'm between a rock and a hard place*
* I successfully removed CWM
* since I don't have root, I couldn't get in and copy over the proper busy box version
* since I couldn't copy over the proper busybox version, I get assert errors (I think that's why) so I can't upgrade to the OTA ICS
* since I don't have root I can't restore nandroid or any older version (I'm stuck on 0089)
WHAT I'VE TRIED
* Installing almost any available US version on lenovo's FTP site
* Rerooting:
* the djrbliss exploit doesn't seem to work (I get 'exploit failed) I assume the exploit was pached on 0089?
* the opdecikel (yareftpt) exploit doesn't work either, it goes though all the steps but when I try and test if I have root (adb shell; su) I gett 'permission denied'
* Installing the OTA ICS doesn't work because of these assert/busybox errors
I've been dealing with this for 10 hours straight and I'm just about to sell it on ebay for parts and buy a nexus 7.
Any suggetions you may have would be a big help as I'm at the end of my rope right now.
jack
Click to expand...
Click to collapse
Try this it helped me with the similar problem
http://www.thinkpadtabletforums.com...er-not-working-after-ota3-ics-update-(fixed)/
moom999 said:
Try this it helped me with the similar problem
http://www.thinkpadtabletforums.com...er-not-working-after-ota3-ics-update-(fixed)/
Click to expand...
Click to collapse
So I ended up fixing this. The thread is here:
http://forums.lenovo.com/t5/ThinkPa...can-t-upgrade-can-t-downgrade-any/td-p/851227
CM10.2 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz5.18.4 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM10.2 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). More desired may be the new privacy manager features that allow you to control, on a per app basis, which information you wish to share. Other improvements include an improved lockscreen cLock and a new integrated Superuser.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera/Camcorder
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* When unlocking the screen, sometimes only the capacitative buttons light up, and the screen doesn't come on. This seems to happen about 80% of the time.
Solution: This can be fixed by locking the screen, then unlocking it again. In about 5% of these cases the screen does not come on again. Just repeat the steps again until it does.
This has been fixed as of build 20131029
* You may notice a screen flicker when you first flash this ROM. This is due to a bug where the system can't decide whether to render the graphics with the cpu or the gpu, thus the flicker.
Solution: This is fixed by turning on Settings -> Developer Options -> Disable HW Overlays (You must first enable Developer Options by pressing 7 times on Settings -> About Phone -> Build Number). This will be reset on every boot. if you install Universal Init.d, my 91fixoverlays script will run on each boot and fix this automatically.
This has been fixed as of build 20131029
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 flashable zip which is compatible with CM10.1/CM10.2
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140224 (Latest)
ROM: cm-10.2-20140224-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20140224-signed.zip (106.5MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A dirty flash should work for upgrading , but a clean flash is highly recommended
Build: 20140120
ROM: cm-10.2-20140120-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20131231-signed.zip (103.8MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with CM10.1/CM10.2
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with CM10.1/CM10.2
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]December 23, 2013 - Build 20131223[/B]
* Revert build.prop to use dyn instead of gpu (less problems)
* Added back 91fixoverlays to /system/etc/init.d to disable hw overlays and fix screen flicker on boot
* Re-worked 91fixoverlays script so that it now runs in it's own shell to stop it from blocking other startup scripts and causing a laggy boot
* Fixed up device tree code including adding the correct definitions for boot animation size and update to the build fingerprint
* Synced latest changes from CyanogenMod
[B]December 1, 2013 - Build 20131201[/B]
* Force gpu rendering in build.prop
* Improve fix for screen on delay
* Synced latest changes from CyanogenMod
* Updated GAPPS
[B]October 29, 2013 - Build 20131029[/B]
* Tweaked build.prop to fix screen flicker and notification drawer lockup
* Fixed screen unlock bug - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/5e163ff0c5d90a4518cbc9e14c86dceec095c70a"]Commit 5e163ff0c5d90a4518cbc9e14c86dceec095c70a[/URL]
* Added SmartAssV2 Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/511e45206bb9a1454a0c43b3d626749c1fa2c241"]Commit 511e45206bb9a1454a0c43b3d626749c1fa2c241[/URL]
* Added Adaptive Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6"]Commit 7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6[/URL]
* Added Lagfree Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/d1392017601d27303fbce9da18d2af718e7e1a65"]Commit d1392017601d27303fbce9da18d2af718e7e1a65[/URL]
* Restore Advanced Device Settings - [URL="https://github.com/titanic-fanatic/android_device_samsung_msm8660-common/commit/3126c17c6165c7d96abde4cd7459769e165aa195"]Commit 3126c17c6165c7d96abde4cd7459769e165aa195[/URL] / [URL="https://github.com/titanic-fanatic/android_packages_apps_Settings/commit/9031ffb1f4e4185f397724a27e3d75afe7fd67e4"]Commit 9031ffb1f4e4185f397724a27e3d75afe7fd67e4[/URL]
[B]October 5, 2013 - Build 20131003[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market, and also make sure you have Universal Init.d installed and active. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. When your phone reboots, recovery will warn you that your device may possibly be unrooted. This is because of the install-recovery.sh script that is required to start the superuser daemon which allows SuperSu to manage superuser permissions. You are not unrooted ;-)
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. This needs to be set on every boot unless you are running Universal Init.d and my 91fixoverlays script is present in the /system/etc/init.d folder.
Q. When I unlock my screen, my menu/home/back/search buttons come on but the screen is black?
A. This is a known bug in this ROM and is on the list of things that need to be fixed. For now, when this happens, just lock the screen, then unlock it again and the display should come back. If it does not, repeat until it does (the most number of times i had to do that was 3).
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM10.2 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-10-05
Last Updated 2014-02-23
Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Wow! Thanks so much. Downloading now.
iDynamics said:
Wow! Thanks so much. Downloading now.
Click to expand...
Click to collapse
Wow, you already found it and I wasn't even finished putting everything up... make sure you use the new CWM, very very very important!
Followed the instructions ( to the best of my ability ) but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
iDynamics said:
Followed the instructions but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
Click to expand...
Click to collapse
I totally forgot to update the build.prop with the build type, it is responsible for the red border. Either use a build.prop editor or open the /system/build.prop with a text editor and change the following line:
ro.build.type=eng
Click to expand...
Click to collapse
Change it to:
ro.build.type=user
Click to expand...
Click to collapse
You will need to reboot after making this change.
In regards to the 91fixoverlays script, I do appologize. I forgot to include it in the zip... Please download the attached 91fixoverlays.txt file and rename it to 91fixoverlays and move it to /system/etc/init.d and change it's permissions to match the other files in that directory.
Sorry for missing these two things. I will update the packages ASAP and will post a note when it's done so you know that there is no need to follow the steps in this post.
Much appreciated! No more red flickering. Thanks!
Wow! Thank you!
Sent from my SGH-I757M using xda app-developers app
This. Is. Amazing!!!!!
Downloading now, will install and report back in a bit with findings.
Thanks so much!!
Awesome. Downloading. Will report back. Thanks!
Sent from my SGH-I757M using xda premium
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will do more testing.
Thanks
Zippy Dufus said:
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will so more testing.
Thanks
Click to expand...
Click to collapse
I think this is due to our oddly small cache partition. Only 100MB as compared to the skyrocket at 300MB. Currently, I only moved four apps in the gapps package to the data partition do that their dex files don't end up in the /cache/dalvik-cache dir and instead end up in /data/dalvik-cache. I think I need to move others. I also think that it happens only on first boot without side effects because a couple of the installed apps only run on first boot, then their dex files can be deleted (I think this happens automatically).
Sent from my SGH-I757M using XDA Premium 4 mobile app
Thanks titanic_fanatic, you've breathed new life into an old phone
Sent from my SGH-I757M using Tapatalk 2
Only issue I've run into so far is that auto rotate doesn't seem to work :-/
Sent from my SGH-I757M using XDA Premium 4 mobile app
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
rukusx7 said:
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
Cool, I'll give that a try. Anyone else having auto-rotation issues?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Rotation is not working for me, though I always keep it on portrait anyway so I am not complaining.
Rotation doesn't work here, and every so often I run into spells where the only button that works is the home button and haptic feedback stops working all around. A reboot fixes it and it seems random. Other than those few things this is soooooo smooth. I'm happy. Thanks so much!
Sent from my SGH-I757M using xda premium
Fix for Sensors
Hey guys, to fix the sensors, download this attachment sensors.default.so.txt and rename it to sensors.default.so, move it to /system/lib/hw and give it the same permissions as the other files in that directory, then reboot and your sensors should be working
Works now! Thanks ya muchly.
Sent from my SGH-I757M using xda premium
Although the Xiaomi Mi 2 is almost five years old, and it seems there would never be a working nougat/oreo ROM after ivan stopped the development of his AOSP project, but it's not the truth. As the issue of light and proximity sensor have been fixed, I think most of the system components are stable enough for dialy usage after my couple days tests, so I decide to release the AOSP 8.0.0 to you today.
Install:
Please make sure your phone haven't modified the stock partition. It means my rom only work with the latest miui-dev partition table, so you have to Download lastest Mi 2 Developer tar file and flash using fastboot before install my oreo/nougat ROM . This process will earse all data on you phone, so backup all data before you getting start.
1. flash stock miui developer by fastboot update (http://en.miui.com/a-234.html)
2. flash twrp recovery use fastboot and reboot
3. hold power and volume up key to boot into recovery mode
4. install oreo or nougat ota package
5. wipe data and cache (you have to do this even if you are using ivan's aosp marshmallow/lollipop)
Working:
(Note: I use Mi 2SC with CDMA network support, but I don't have an available CDMA SIM card right now for test, so users with CDMA network might have trouble with RIL)
- Audio (bluetooth headset not test)
- Bluetooth
- Camera
- RIL
- WIFI
- FM
- Sensors
- GPS
Credit/Thanks
Special thanks to ivan for the initial device source tree and his preview works on Mi2 device.
Many Thanks to @AdrianDC @Ziyan for their great work to bring Android Oreo to MSM8960 platform.
Also thanks to @m11kkaa (M1cha) @zaclimon for their projects.
- Xiaomi Opensource Project
- Google Android Opensource Project
- Team LineageOS/CyanogenMod
- Team Omnirom and Team TWRP recovery
- Team Unlegacy Android
Source:
device tree: https://github.com/windbellx/android_device_xiaomi_aries
https://github.com/windbellx/android_device_xiaomi_msm8960-common
kernel source: https://github.com/windbellx/android_kernel_xiaomi_msm8960
vendor: https://github.com/windbellx/proprietary_vendor_xiaomi
Screenshot:
Download
https://mega.nz/#F!naRFGQDR!d9Uv-Maw56vyYsphAj00Kw
Known issues
1. APN needs setting manually to use CDMA data network. (?, not sure, need more tests).
2. Selinux status is on permissive status.
Root
1. download all files under superuser
2. reboot to fastboot, flash boot.img
Code:
fastboot flash boot boot.img
3. boot into recovery, mount /system, push su binary and superuser.rc to your phone
Code:
adb push su /system/xbin/su
adb push superuser.rc /system/etc/init/
4. reboot
Gapps
select one way of below
1. flash MindTheGapps-9.0.0-arm-20181119.zip
2. download OpenGapps Pico (Not support other version due to limited space of /system
upload gapps-config.txt and opengapps zip file to the same folder and flash opengapps
Changelog
2019-01-01
* fixed wrong 1080p parameter in AOSP camera, both rear and front camera support 1080P record now.
* fixed wifi hotspot and usb tethering cannot open.
* fixed echo reappear after first call.
* rebase kernel, improve wakeup speed and stability.
* add percent text for offline charging.
* reimport MHL releted code, try to bring up MHL. (not tested)
* QS UI improved for small-size screen.
* keep the crypto name same with AOSP, try to make disk encryption work. (not tested, format /data and storage before encryption if too many files, or get out of memory error and system reboot).
* stop maintaining this device if no critical bug in this update.
2018-11-19
-> Upgrade to Android Pie(CAF 9.0.0), tag: LA.UM.7.2.r1-05300-sdm660.0
-> Features added:1. Privacy Guard(with optional su support, thanks LineageOS)
2. App Firewall(data, wlan and vpn, thanks LineageOS)
3. Showing Network Speed(thanks Jon Haus, ezio84 and other commiters)
4. Launcher with icon pack support(thanks tfitts1212, maxwen, eldainosor and other commiters) -> Fix hidden wireless connection
-> Add DRM support (For Netflix, L3 level, not support HD and higher)
-> Try to fix echo in calls again(not tested, report if not working)
===========================================================
Android Nougat/Oreo start
Download Link:
Only twrp >= 3.2.1 works with ROM >= 20180101
https://mega.nz/#F!VKRggSoL!WAFIK45_IFKhnvlK1eyY4w
Known issues:
1. Hidden network cannot connect.
2. APN needs setting manually to use CDMA data network. (?, not sure, need more tests).
3. Not support 1080P camera record due to outdated kernel driver.
4. Selinux status is on permissive status.
Changelog:
2018-11-01
* md5sum: b957fa0274819a09fd81d2af2958cc69
* echo in calls should fix now, only tested VOIP, need more tests(headset, bluetooth etc).
* with echo fixed, an issue related ES310 chip sleeping that make battery draining fast is also fixed.
- Standby battery time estimate: > 5 days.
- Normal Screen on usage: 5~6 hours.
2018-10-21
*md5sum: 8cbfdceb23c3aa6f382f1a9a79c29004
* fix noise in headset mic
2018-10-19
* md5sum: 9304de676e0dd6428db566b072488e3f
* fix echo audio during calls
* performance tweaks, fix too hot when too many heavy background tasks, now enable all 4 cpu cores by default
* HALs and blobs changes prepare for P
2018-09-01
* md5sum: b7e60c0033b526278468a38cb00f373e
* minor updates and stability improved.
* last update as I'm going to remove all 8.1 source, source will update to github as soon as possible.
* I will try to bring up pie once I get free, but no guarantee and no ETAs.
2018-06-16
* md5sum: da677903b4c5092d57e91f0dc2210a90 aosp-caf-8.1.0-20180616-aries-arch.zip
* bring back Privacy Guard and synchronize to latest LineageOS version.
* fixed sometime the device is too hot while too many background apps and optimize screen-on battery usage.
full battery usage estimated:
>5 hours online surfing with wifi opened(moderate usage, no gaming).
2 days standby (45-50 hours).
3-4 hours(?) using cellular data.
2018-05-06
* md5sum:
- b7121d3f95e91350722da01c8dfdea22 aosp-caf-8.1.0-20180506-aries-arch.zip
- 6988262c9f99c00371a1bc238ffbdf26 aosp-caf-8.1.0-20180506-aries-arch-gapps.zip
* fix gps and compass broken in last build.
* revert media profile changes so screen record now works normally.
* bring back Xiaomi usb otg driver. (Not tested, tell me if it not work)
* enable doze correctly.
* reduce battery usage when WIFI turned off.
* thermal and some kernel tweaks.
2018-04-20
* md5sum: e8fc7f3793d820f279580726f2c34e93 aosp-caf-8.1.0-20180420-aries-arch.zip
* this version is NOT compatible with previous ROM, SO CLEAN DATA/CACHE OPERATION IS REQUIRED.
* switch to CAF source(tag: LA.UM.6.6.r1-07200-89xx.0) instead of Google generic repository. This build contains Qualcomm specific enhancements plus some comunity optimizations, so it gives some improved performanence to this old device (especially pictures slipping and system animation). Thanks to AOSPA and AOSP-CAF.
* fix WiFi hotspot, tethering should work fine now.
* fix audio call volume cannot adjust.
* add firewall(app wifi/data restriction) support to oreo(App info -> Data Usage -> Disable all cellular data access/Disable all Wi-FI data access). Port from Lineage/CM, thanks again for their great works.
* add multiple pointers patch.
* add fake signature patch, for some MicroG users.
* update media profiles, remove 1080p option from camera records.
* now the build type is "user", which will disable adb debugging by default, "adb root" also disabled.
* repatch telephony framework for CDMA users(NOT TESTED).
* it's the final update if no serious issues(this update is to resolve the call volume issue).
2018-03-17:
* This version is expected to be the final version and wouldn't update anymore if no critical issues. I hope you can enjoy this one without obstacles. Source will be updated to github in a few days.
* update to 8.1.0_r17
* update audio configuration files so audio should work flawlessly now.
* update power hal and tweak cpu scheduler, try to make a better battery life.
* remove Privacy Guard (seem have unnormal power usage when data connection opened), revert Apps data path tweak, remove addtion Internet/Sensor permissions(it makes Google Setup Wizard FC).
* fix device hangs while trying power on machine in offline charging mode.
2018-01-27:
(NOTE: new kernel might have problems with some device, please attach your logcat, dmesg and top command result(adb shell -> top -> take a screenshot), plus you device model)
(NOTE 2: If you have installed gapps and don't want to clean data, flash gapps after flash the new ROM, before your first boot, or some app will get a FC, unless reinstall the app)
* Revert to old audio hal so that calling audio works with old configs
* Fix some storage access permission issues. Move all Apps data to /sdcard/AppData, so external storage path that apps got will be /sdcard/AppData/<package name>/
2018-01-19:
* fix system crash when openning gps with IPv6 network
* fix the audioserver crash when using a headphone
* fix app crash when not granted WRITE_STORAGE permission
2018-01-17:
* update to 8.1.0_r7
* switch to new kernel base. After almost one month dialy use test, I decide to abandon the old kernel tree and enable new kernel source tree, so Xiaomi aries now share the same kenel base code with sony huashan(https://github.com/AdrianDC/android_kernel_sony_msm8960t). Adrian DC have been working on AOSP/LineageOS of Sony msm8960 platform for a long time, he also is a recognized and trusted developer of LineageOS. With new kernel, I believe it will be more quickly to bring a features-ready and more stable aries ROM to you. Thanks @AdrianDC for his great work.
* switch to new audio/display/media HAL, report if you have any trouble to aduio, video play and records.
* new kernel support new auto sleep and wakeup (instead of earlysuspend), and many other changes to improve deep-sleep in oreo, so it will be a better battery life when phone is idle.
* adopt some code from Lineage to support CDMA data connection. if you want to report RIL releated issues, please attach both full logcat(adb logcat) and radio logcat(adb logcat -b radio)
* fix power menu not shows correctly
* fix some app cannot open again after force stop
* make lockscreen swipe more easier to unlock
* magisk now can boot properly
2018-01-01:
* fix UI performance. (NEED MORE TESTS)
* port Privacy Guard to aosp-8.1, thanks to team Lineage/CM/SlimROMs (Settings > App & notifications > Privacy Guard)
* superuser now is optional
* isolate app data/files on /sdcard (app now saved data to /sdcard/<package name>/ install of /sdcard/, It make external storage root more neat and more secure in some cases)
* fix alarm not work
* disable permission review, or permissions will reset after every updates
* disable liveshot in case of crashing when touched in video record mode
* secondary try to fix CDMA data connection. (Need feedbacks, plus model)
* fix setting lockscreen pin/pattern nonresponse
* update battery data, try to fix battery value reset. (NEED TEST and FEEDBACK)
* update twrp to 3.2.1
2017-12-09: (Download from here #65)
* Update to 8.1.0_r1
* Enhance security and privacy settings (many thanks to thestinger and CopperheadOS)
** I have added Internet permission and enable permission review for app with targetSdkVersion < 23, If you are not a clean installation, some app might get a FC. Reinstall app and give the permissions(PHONE OR INTERNET) can solve problem.
* Fix Mi2s 32gb with 13MP camera. (NEED TEST)
* Revert kernel gpu driver. Try to solve UI unsmoothly sometime. (NEED FEEDBACK)
* Add CDMA dummy APN patches. Try to solve data connection with CDMA network. (NEED TEST)
* Use old power and charger driver. It works better.
2017-11-19
* initial 7.1.2 and 8.0
Download: OUTDATED! FIND UPDATES FROM CHANGELOG
twrp recovery 3.1.1: https://mega.nz/#!RewDnB5Z!1JaIxJ2-wQpd9BmY1MoqIrt0z9rI2pLg6lKL5Z2lsKg
aosp 8.0.0: https://mega.nz/#!FHpTRCQL!j_Z-XirV12iPhxmnIAWA33W5HB1ca0Mep8lsKSiB10g
aosp 7.1.2: https://mega.nz/#!hTIgGT5a!gfap1JU95VeyfYauYcvlaR-VnHwRLRzklLENMwS2jgs
Great!:highfive:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
lol，cdma 1x can be load ，but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
huo zhuo huda
ziiimy said:
lol，cdma 1x can be load ，but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
huo zhuo huda
Click to expand...
Click to collapse
You are the first one to make the ril work after M. I think this is exciting.
great！
Can't not connected to hidden WiFi
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
Yes
ziiimy said:
lol，cdma 1x can be load ，but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
huo zhuo huda
Click to expand...
Click to collapse
Sorry, it wouldn't be fixed as I don't have a CDMA SIM card right now.
UI is very unsmooth. After installing gapps got 'setup wizard has stoped' error. Can it be fixed?
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
great my big brother
我是中国用户，小米2太厉害了，居然能用上功能正常的安卓8.0，感谢xda论坛
I am a Chinese user, millet 2 is too powerful, actually able to use the normal function of Android 8.0, thank xda forum
duplicated
-Tex- said:
UI is very unsmooth. After installing gapps got 'setup wizard has stoped' error. Can it be fixed?
Click to expand...
Click to collapse
if you open logcat and got error like this:
Code:
I zygote : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.NativeCrypto>: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/com.android.media.remotedisplay.jar", zip file "/system/framework/com.android.location.provider.jar", zip file "/system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk"],nativeLibraryDirectories=[/system/priv-app/PrebuiltGmsCore/lib/arm, /system/lib, /system/vendor/lib, /system/lib, /system/vendor/lib]]] couldn't find "libgmscore.so"
this is a temporary solution.
1. extract Phonesky.apk and PrebuiltGmsCore.apk from Core/vending-arm.tar.lz Core/gmscore-arm.tar.lz (320/priv-app/PrebuiltGmsCore) in opengapps zip file.
2. extract Phonesky.apk to Phonesky and extract PrebuiltGmsCore.apk to PrebuiltGmsCore use any zip software, or you can run:
Code:
unzip PrebuiltGmsCore.apk -d PrebuiltGmsCore
unzip Phonesky.apk -d Phonesky
the Phonesky and PrebuiltGmsCore folders should like this:
Code:
➜ ls Phonesky
AndroidManifest.xml
android-support-multidex.version.txt
assets
build-data.properties
classes2.dex
classes.dex
com
lib
libs
META-INF
org
res
resources.arsc
Code:
➜ ls PrebuiltGmsCore
AndroidManifest.xml
assets
build-data.properties
classes2.dex
classes3.dex
classes4.dex
classes.dex
com
googledata
HACKED-META-INF
lib
META-INF
org
res
resources.arsc
3. then, push the lib to your phone by adb:
Code:
adb root && adb remount rw
adb shell mkdir -p /system/priv-app/PrebuiltGmsCore/lib/arm/
adb push PrebuiltGmsCore/lib/armeabi-v7a/* /system/priv-app/PrebuiltGmsCore/lib/arm/
adb shell mkdir -p /system/priv-app/Phonesky/lib/arm/
adb push Phonesky/lib/armeabi-v7a/* /system/priv-app/Phonesky/lib/arm/
it should works now, tested with gapps nano.
It seem like an uncorrectly odex/install problem, I need more time to investigate it.
windbells said:
it should works now, tested with gapps nano.
It seem like an uncorrectly odex/install problem, I need more time to investigate it.
Click to expand...
Click to collapse
Should i do this after installing gapps or do it instead of installing gapps? What about ui smoothness?
-Tex- said:
Should i do this after installing gapps or do it instead of installing gapps? What about ui smoothness?
Click to expand...
Click to collapse
After installing and reboot to system.
If you are still facing ui Smith less after solve the gapps opening, try clean data and cache, if still exists, please attach logcat log and describe you r usecase in a more detailed way, and also, what's your phone model name? 2? 2S? 2S with 13m camera?
I just tried on my Mi2S 16G with 8MP camera,
Almost everything works well, but UI is very unsmooth.
I have 32GB with 13MP camera, but this is my daily use phone, so I don't want try on it.
Update:
I tried to grab logcat and dmesg to try to find the reason about UI unsmooth.
But the information is too much that I have no idea to find...
So I upload them to my mega.co.nz
logcat:
https://mega.nz/#!KYMVHByT!Mytx_PG8BqhOrMauhr-NtcsqO7Qw7RIw7i2ydJsNj-4
dmesg:
https://mega.nz/#!6UF30KRS!4qzlNs0UFMBHacNX_WsJIrlVmINNsqzVHCYAdkvkaAI
windbells said:
After installing and reboot to system.
If you are still facing ui Smith less after solve the gapps opening, try clean data and cache, if still exists, please attach logcat log and describe you r usecase in a more detailed way, and also, what's your phone model name? 2? 2S? 2S with 13m camera?
Click to expand...
Click to collapse
I will try tomorrow. My phone model mi2sc 16 Gb with 8m camera.
joe820730 said:
I just tried on my Mi2S 16G with 8MP camera,
Almost everything works well, but UI is very unsmooth.
I have 32GB with 13MP camera, but this is my daily use phone, so I don't want try on it.
Click to expand...
Click to collapse
It seems that my kernel not working on 13MP camera, according to the feedback.
I think Mi2S with 8MP camera should work fine as I using 2SC 16GB with 8MP camera. I think it's really smooth after had a data cleaned boot. Even after I installed the opengapps, it's smooth as usual. Can you describe you usecase or record a short video that shows UI stucked.