Related
First ....THANKS @letama, and last but not least thanks to @tRAcE3k for .ext4 build.
Official Stock Firmware v3.2.79 => ROOT, Update : Su binary v3.0.3.2, Superuser v3.0.7 and busybox v1.19.3, Add : enables vibrator and adjust volume !
(There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/ - only for .ext4)
This ROM is only for SDE enable ( recovery) ....you can use it as a daily ROM...
These are the files you need :
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/archive/6Y9sMqJ5/initramfscpio.html
- archos_3.2.79.squashfs => http://www.4shared.com/zip/-vo5gkRr/firmware_3279squashfs.html (...version without busybox and update!)
- archos_3.2.79.ext4 => http://www.4shared.com/zip/dmrcBtJM/3279_updat.html
How install this :
- connect device via USB cable
- adb push archos_3.2.79.squashfs data/media/ ........for read-only /system
- adb push archos_3.2.79.ext4 data/media/..............for read-write /system and other stuff
- reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
letama said:
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
Click to expand...
Click to collapse
old firmware (3.2.77 etc) must be removed manually from device?
ext link is invalid "......". ciao ;-)
gegabit said:
old firmware (3.2.77 etc) must be removed manually from device?
Click to expand...
Click to collapse
When everything works, yes, you can remove the previous .ext4 from internal storage. That's the only thing you have to remove.
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
now its upload to share.
- archos_3.2.79.ext4 => /.......future upload ..... it's 512Mb ext4...........
Click to expand...
Click to collapse
Hi Folks.
Thought I'd do my bit. Here are some more sources to download the ext4 firmware.zip
http://www.multiupload.com/0OTX0D54XW
Thanks to surdu_petru for the original image and tRAcE3k for the repacking instructions in this post.
Thanks
Trev
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
[email protected] sure is right....on the ather hand, every new firmware ( ex. firmware_archos_it4.aos) has its own boot image ( boot.img = zImage + initramfs) -used to boot devices and has its own flash files / system files which are grouped in an archive ( contains - libraries, aplikations, and other stuff ) - used to run system android , and all these are closely linked ....I think you can now better understand how to use them, and why ......
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
Ok...Now is valid link : http://www.4shared.com/zip/bp7XjWzY/archos_3279ext4.html....
Good luck!
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
droobey said:
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
Click to expand...
Click to collapse
Ok! Now just upload new update .....
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
revere521 said:
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
Click to expand...
Click to collapse
OK! Try >adb shell chmod 6755 system/bin/su
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
.....after install all....try to update Superuser into Market......
Update doesn't help :-(
surdu_petru said:
.....after install all....try to update Superuser into Market......
Click to expand...
Click to collapse
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
basd82 said:
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
Click to expand...
Click to collapse
OK I know.....just wait max 1 hour and I'll uploaded the new archos_3.2.79 files...with it everything works perfectly ( I have tested all , root_explorer, es file explorer, Root Check ....it's OK !!!!!).
basd82 said:
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
Click to expand...
Click to collapse
ok! but now problem was solved.....just redownload the new firmware_3.2.79 files , unpack and enjoy*
Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance
Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.
m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.
Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!
Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks
thank you for this
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.
SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.
hi all,
I was running my TX with advanced kernel v4, rooted:
http://forum.xda-developers.com/showthread.php?t=1922925
yesterday i installed Miui Security from here:
http://forum.xda-developers.com/showthread.php?t=1663222
Then the root is gone. I checked that /system/bin/su and /system/xbin/su are still there but they are inter-linking with symbolic link when i view them with root explorer.
fixes tried:
When i use ADB push trying to replace them, it said "too many symbolic links encountered"
I cannot remove both file as i cannot su in ADB shell.
I booted into CWM recovery but ADB is not enabled in CWM.
I reflashed the flashable zip in CWM to gain root access with no error message prompted, but after reboot into system the SU files are still the same
I reflashed the kernel with flashtools and fastboot, still no change applied to the phone.
Any idea?
finally got it fixed...
I rewrite the updater-script in the CWM flashable zip for root package to force remove both /system/bin/su and /system/xbin/su and rewrite them back.
Thanks for watching...
I've the same problem
Hi guys,
I've the same problem.
I've flashed my Xperia T with MIUI-3.11.22 rom.
I've activated the root permission on Security tab, but my phone doesn't give me the root access (I've tried to install adbd insecure and BusyBox but the result is "problem with root access".
Some ideas?
Thx
Hi Guys,
This is FYI if you rooted your phone, did something to your System files and then you got the OTA update, but once you downloaded and hit INSTALL, the system reboot and you got a FAILED!!!!
To debug,
use ES File Explorer or any file system with root access to view your /device.
Open this file the fota log: /cache/recovery/fota/report
Search for ERROR
For me, I've got this error:
Info [1934] Starting operation 1
ERROR [2023] RedBend error: 0x8000013E, code = 0x13E (318)
Info [2040] Return value from RB_vRM_Update 0x8000013e
Info [2041] pCustomerPartData.updated = rest = -1
Info [2042] End of operation 1
ERROR [218] Redbend verify Error
ERROR [704] Error from ua_updater_start
Click to expand...
Click to collapse
which, if you go to === ua_updater_context === section,
You will see where the section ends. For me, I got this:
=== ua_updater_context ===
u_ctx->result: 2
u_ctx->ui_error: 0
u_ctx->redbend_error: 0
u_ctx->redbend_verify: 1
u_ctx->redbend_write: 0
u_ctx->redbend_post: 0
u_ctx->file_error: 0
u_ctx->lbm_error: 0
u_ctx->boot_error: 0
u_ctx->boot_verify: 0
u_ctx->boot_write: 0
u_ctx->boot_post: 0
u_ctx->google_error: 0
u_ctx->kid: 1 (KERNEL_NORMAL)
u_ctx->running.state: 2 (UPDATE_VERIFYING)
u_ctx->running.increment: 5
rb_file_open[0]: //system/app/socialife.odex
rb_file_open[1]: //system/app/textinput-chn.odex
rb_file_open[2]: //system/priv-app/SomcMusicSlideshow.odex
rb_file_open[3]: //system/priv-app/ArtFilterCamera.odex
rb_file_open[4]: //system/app/Home.odex
Click to expand...
Click to collapse
Which reveals it stops at Home.odex! Ok, I admit I changed my launcher file. So, what to do? Get the Home.odex or any files that you have change and replace it with stock. I am using C5503_10.5.1.A.0.283_Customized_HK.tft which i suppose most apk files are the same.
To get the file from stock tft file,
Download the 10.5.1.A.0.283 tft,
Extract the system.sin using 7zip or any archiving application. Wooping 1.5GB from the 900++mb tft archive.
Open Flashtool.exe > Tools > Sin Editor > Browse your file > Extract Data
Once you got the system.sin, run Ext2Explore as administrator and Copy out your original file. In my case, Home.odex.
Then, I just hit the Update!!! Profit!
Ext2explore 2.1 is attached if you need it. Thanks to Regmi!!!
I used this method and successfully upgraded my phone from .283 to .292 by OTA. Root is also preserved. Also I found that OTA might check other files in the system partition. Just be ready to restore them from the TFT.
Sent from my Xperia ZR using Tapatalk
itandy said:
I used this method and successfully upgraded my phone from .283 to .292 by OTA. Root is also preserved. Also I found that OTA might check other files in the system partition. Just be ready to restore them from the TFT.
Sent from my Xperia ZR using Tapatalk
Click to expand...
Click to collapse
Glad i can help!!! ～_～
Sent from my C5503 using XDA Free mobile app
thank you
I've been trying to update from 4.3 to 4.4 (.230) via OTA but i'm also getting failed to update. Because of your post, I was able to find out that it's because i changed the system font (via hifont). I reverted and will try again. Hopefully, it goes well this time. I could just update via pc companion to .283 but i didn't want to wipe my phone and lose root too.
Thanks for this! :good:
Well done.
Next, prepare for lollipop update.
Sent from my C5503 using XDA Free mobile app
Hi all, im here because i have some problem about install CyanogenMod of this tread:
http://forum.xda-developers.com/xpe.../rom-cyanogenmod-12-neo-s-homebuilds-t2984988
i hade a Xperia T, with 4.3 stock, with root, followed thsi http://forum.xda-developers.com/showthread.php?t=2798411=2333577
then i unlocked my botloader, following a italian guide by "Unlock SE xperia bootloaders", ask to Sony the hey for unclock, and all work fine.
Downloaded cm-12-20151108-NIGHTLY-mint with Gapps open_gapps-arm-5.1-pico-20160226, and pun in my microsd.
i have:
(1) Boot into TWRP recovery
(2) Do a factory reset and wipe system partition
(3) Flash latest ROM zip, but no Gapps (I'd do it later, first I wanted to see if it was loaded right to the Rom)
Reboot, configured cell phone, everything ok.
Then i try to follow step about resize partition, so i reboot phone, press "vol down", and my xperia boot into a "Cyanogen recovery", and not in the PhilZ Touch Recovery.
So I made some tests, and i have install TWRP by APK file, install ok, so i can go inside TWRP at the boot.
krasimiretov tell me to do that:
1. Install build from 08-01-2016(final)
2. You need to fastboot boot.img . There is no cyanogen recovery its TWRP. You must have done something wrong.
3. No towelroot is needed. After installing the build and flashing supersu from recovery phone is rooted.
4. You can do that with TWRP recovery no Philz needed.
so i have downloaded 08-01-2016(final), try to zip with TWRP but not able https://www.dropbox.com/s/n6do3ucbx8oju5a/2016-02-27 12.08.52.jpg?dl=0
i try to fastboot boot.img, by flashtool, istall it following this http://forum.xda-developers.com/showthread.php?t=1963961 but at the reboot xperia still "tunr off" afeter logo SONY, i should reboot (vol up+on for 10 sec, go to TWRP and reflash cm-12-20151108-NIGHTLY-mint for work again.
I am tempted to start all over from the beginning...but i shoud unlock again bootloaders, use unlocked bootloader, than i can, maybe, reflas ftf, right?
sorry if it's a little confused, but I do not know how to install the latest ROM, to be able to resize the partition
ok ..ok... i try again and now have work fine...
i just arrived to the Reboot, afetr install rom, gapps and update superSU, but screen is "stuck" at the recovery...is freeze there...i can reboot manually?
done!
redone the procedure,
I was wrong to flash the boot.img :angel:
So its working fine now ?
yep! work!!
but i have a little problem for resize...
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
say "su" not found:
/ # su
Sh: su: not found
Flash latest SuperSU from here: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Did you flash that in TWRP ?
yea... anyway im trying again... (It has a bad sensitivity TWRP )
nothing... "SU" dont work, but T work without "problem" ... i just have some lag and some closing's applications...
and this error after rebooting:
https://www.dropbox.com/s/tb4p3oykwhwglof/unspecified.png?dl=0
i would like try the latest UNOFFICIAL by Neo ... where i can download it? its cm-12-20150405-UNOFFICIAL-mint ??
maybe better version 12
ok..i have try install cm-12-20150405-UNOFFICIAL-mint, replace boot.img with flashtool, twrp change version, like this https://upload.wikimedia.org/wikipedia/commons/f/fe/TWRP_2.7.0.0.png but when i try install the .zip, i received a error ... so i try to install the cm-12-20151108-NIGHTLY-mint, ok without error, but now ROM have loop on CM logo ...
nevermind... I was able to do everything alone ...
I do always panic
buti have always the messa
https://www.dropbox.com/s/tb4p3oykwhwglof/unspecified.png?dl=0ge
Its from the google apps. Why are you unstalling CM12 when there is more optimized and up to date CM12.1. And i write again. READ EVERYTHING IN OP CAREFULLY.
krasimiretov said:
Its from the google apps. Why are you unstalling CM12 when there is more optimized and up to date CM12.1. And i write again. READ EVERYTHING IN OP CAREFULLY.
Click to expand...
Click to collapse
i have unstalling the latest 12.1 (cm-12.1-20160108-UNOFFICIAL-mint.zip), and use Build CM12 UNOFFICIAL by Neo - 5/4/2015, because 12.1 was full of lag, and some app freeze and quite without message...
Now Xperia T is more fat without lag ...
Anyway i can install other 12.1 ... except the last one that is not working well ... what would you suggest me about, version 12.1?
Ok, i have try again with this version:
cm-12.1-20160108-UNOFFICIAL-mint
open_gapps-arm-5.1-pico-20160301
BETA-SuperSU-v2.68-20160228150503
Follow always the istruction:
Flash the boot.img from ROM zip via Flashtool (use Fastboot mode)
Boot into TWRP recovery
Do a factory reset and wipe system partition
Flash latest ROM zip (check "Downloads" section)
Flash suitable GApps for CM12.1 or CM12
Flash latest SuperSU from here: Link
Reboot
i have always the same message when boot the phone about SETTINGS
nosadello said:
i have always the same message when boot the phone about SETTINGS
Click to expand...
Click to collapse
We all have that message, that's bug about CM Theme, and It's nothing to worry about.
nosadello said:
yep! work!!
but i have a little problem for resize...
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
say "su" not found:
/ # su
Sh: su: not found
Click to expand...
Click to collapse
i should give this command on recovery or enable terminal on androd??