Related
Since installing Raidroid 1.1 I had the concern of an extremely LOUD boot sound.
I decided to find out how to turn it off and let everybody know how.
It turned out to be much simpler than I thought. The method, I believe, will work with all ROMs.
There is a file in /system/media/bootscreen called boot_animation.xml - this contains the script that runs on startup.
First you need to copy that file off your phone for editing. Use any method you wish, I used adb
adb pull /system/media/bootscreen/boot_animation.xml boot_animation.xml
Now, in your current folder, you will have a copy of that file. You can edit it in notepad.
Here is mine:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright © 2008 HTC Inc.
*
-->
<!-- For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
screenX="100" (optional)
screenY="130" (optional)
useAudio="0" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
<!-- For cropped version -->
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
screenX="40"
screenY="0"
useAudio="0"
/>
</BootConfiguration>
<!-- For full screen version -->
<!--BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
loopimage="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
useAudio="0"
/>
</BootConfiguration-->
Click to expand...
Click to collapse
You will see, I've highlighted the changes I made in bold.
I've disabled the audio completely but I could, for example, change the image or audio to anything I wanted. If you choose to change the image or sound file, be careful. This script runs at startup and I'm guessing that if you configure it wrongly that you may not be able to boot the phone.
Once your phone is edited, you now need to upload the amended file back to the phone. Again, I used adb. (thanks DarthOps for the remount help)
adb remount
adb push boot_animation.xml /system/media/bootscreen/boot_animation.xml
All done, now reboot your phone to test.
Thanks for sharing..works for me..
It looks like there is a universal registry tool somewhere on either the phone or available during update. I extracted this from my logs during the Mango Update:
Code:
**** Starting Registry Update @ 16:47:36 ****
Checking to see if shadow order changed.
Checking to see if any reg files changed.
Shadow order has changed, Registry files have changed. Registry update required.
building new ROM hives
succeeded
copying default.hv (simulation)
copying user.hv (simulation)
copying default.hv
copying user.hv
completed ROM hive file update
importing RAM hive changes
exporting/reimporting RAM hive changes to maintain key enumeration order
RegUpdate succeeded
Update Application - Completed Registry Update @ 16:47:55
I have yet to extract a rom successfully with a full file structure. If someone could prodive me with one or instructions on how to do it I could find out more. I have a feeling we have more access to the phone when you start the phone in update mode by holding down volume down, camera, power. But that is just a thought.
nice try...!!
Well it looks like the *.hv files are the registry files. I just need to get a rom dump from my dell venue pro. I still can't figure out how.
Ok, How would I get a cab file with a provxml file containing
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
sorta like the one attached. The one attached is supposed to allow you to upgrade to mango (dont try it). If we can inject that code there we could inject any registry update we wanted.
MJCS said:
Ok, How would I get a cab file with a provxml file containing
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
sorta like the one attached. The one attached is supposed to allow you to upgrade to mango (dont try it). If we can inject that code there we could inject any registry update we wanted.
Click to expand...
Click to collapse
PM xboxmod
may be able to help
Well I pm'ed him...anyone else know how to. I think this could really work. I might also be able to fix the DVP's missing compass driver by adding it to a cab and using a file copy command!
Please keep trying, but as an expectations-management step, I have to tell you: The phone probably requires that update/install packages (orther than XAPs) be signed. This can be worked around on HTC phones because the bootloaders are (or until recently, were) unlocked, but LG/Samsung/Dell don't seem to have this advantage and will only load signed images.
That said, it's possible this installer avenue doesn't have that protection. Good luck!
Yeah I was afraid of that...A certificate chain could not be built to a trusted root authority
[Q] 816-dual- Rooted - tried "wp_mod: disable system write protection "- corrupted OS
Hello Team, I am a Android Newbee... my first device is HTC816 dual....
1) I have Rooted the device and succeed
2) still, the profile.xml was giving issue not letting the apps to write to external SD
3) found out about the HTC system protection.....
so as per the threads " KERNEL MODULE] wp_mod: disable system write protection by flar2 for 816 "
I downloaded and updated the kernel.... succeed in disabling the system write protection....
but the patient 816 started side effects......
after that, my phone started weir-ding.....
1) none of the application is working.....
2) internet is not connecting
3) sd cards not detecting...
4)errors like below repeating.....
""""""""""""" youtube has stopped
com.google.process.gapps has stopped
com.android.phone has stopped send report to HTC.com """"""""""""""""
so How much damage am i looking at ????
any one any suggestions ????
getting a stock ROM and flashing will resolve the issue ?
any other options ( i cannot claim warranty )
HTC 816 dual ::::
Android -ver 4.4.2 htc sense 6 sftwar - 1.25.720.1 , 6.21 htc sdk api
baseband 1.31.50.0503 built 1.25.720.1.CL334435
@SivasankarC Factory reset your cell bro...
jithumon said:
@SivasankarC Factory reset your cell bro...
Click to expand...
Click to collapse
hey Jithu, yes i did try factory reset also... still the issue Continues....
the SDcard is not mounting UP..... and same above errors....
I cannot even, do the initial registration steps.... after factory reset....
jithu ,
it will be really helpful,
please uploaded the CWM backup of your HTC desire 816 dual....
our devices are similar regional devices.... so it should resolve my issues....
SivasankarC said:
jithu ,
it will be really helpful,
please uploaded the CWM backup of your HTC desire 816 dual....
our devices are similar regional devices.... so it should resolve my issues....
Click to expand...
Click to collapse
I'll upload it till 2moro afternoon.
Please wait till then.
I know your problem dude.... Please give me some time.
I totally appreciate jithu...... thanks so much... looking forward.....
SivasankarC said:
I totally appreciate jithu...... thanks so much... looking forward.....
Click to expand...
Click to collapse
Twrp backup done... Will upload from office tomorrow.
jithumon said:
Twrp backup done... Will upload from office tomorrow.
Click to expand...
Click to collapse
thank you !! please attach the twrp app too....
SivasankarC said:
thank you !! please attach the twrp app too....
Click to expand...
Click to collapse
Flash from here
http://forum.xda-developers.com/showthread.php?t=2782543
jithumon said:
Flash from here
http://forum.xda-developers.com/showthread.php?t=2782543
Click to expand...
Click to collapse
YOU the MAN.. dude...
SivasankarC said:
YOU the MAN.. dude...
Click to expand...
Click to collapse
[emoji6]
SivasankarC said:
jithu ,
it will be really helpful,
please uploaded the CWM backup of your HTC desire 816 dual....
our devices are similar regional devices.... so it should resolve my issues....
Click to expand...
Click to collapse
Done bro.
Instruction are in below link.
http://forum.xda-developers.com/desire-816/general/rombackup-t2811252/post54042669
jithumon said:
Done bro.
Instruction are in below link.
http://forum.xda-developers.com/desire-816/general/rombackup-t2811252/post54042669
Click to expand...
Click to collapse
Jithu, Excelent.................
It worked !!!!!!!!!!!!!!!!!!!
Thank you so much Bro..................
My mobile is back to Good Condish........... 1000Likes & Thanks for you !!
SivasankarC said:
Jithu, Excelent.................
It worked !!!!!!!!!!!!!!!!!!!
Thank you so much Bro..................
My mobile is back to Good Condish........... 1000Likes & Thanks for you !!
Click to expand...
Click to collapse
Thanks bro....
Always happy to help
jithumon said:
Thanks bro....
Always happy to help
Click to expand...
Click to collapse
Jithu, How to modify the permission.xml file ?????? overcoming the System write protection ?????
that will be my next activity !!!
SivasankarC said:
Jithu, How to modify the permission.xml file ?????? overcoming the System write protection ?????
that will be my next activity !!!
Click to expand...
Click to collapse
You don't need to edit xml file.
Follow the instruction in the below thread to get system write access
http://forum.xda-developers.com/showthread.php?t=2707378
Please do a backup before this.
To get a permanent access, do the below steps(not mine - from m8 forum)
1 install TWRP
2 Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh*
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time
Do step by step very carefully. If missed one, you'll have to restore backup again.
jithumon said:
You don't need to edit xml file.
Follow the instruction in the below thread to get system write access
http://forum.xda-developers.com/showthread.php?t=2707378
Please do a backup before this.
To get a permanent access, do the below steps(not mine - from m8 forum)
1 install TWRP
2 Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh*
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time
Do step by step very carefully. If missed one, you'll have to restore backup again.
Click to expand...
Click to collapse
Jithu my frnd..... Because of this module I bricked my phone.......... i did do all the steps in it... still it crippled the phone....
here is the workaround i Did yesterday.....
1) I made a copy of platform.xml in my sd card
2) edited the card using note++ in my pc like below...
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
<group gid="media_rw" />
</permission>
3) copied the modifed file again to sd card
4) rebooted the mobile to twrp recovery
5) using mount option mounted system & sd card
6) using advanced option, renamed the original platform.xml to platform.xml.org
7)copied the platform.xml from sdcard to system location
8) using chmod i changed the permission to 644 ( check the owner information too )
9) reboot the mobile...
10) Now I can see my applications are not annoying about the write permission on the internal mem...
How is it ????? :good::good::good::good::good::good:
SivasankarC said:
Jithu my frnd..... Because of this module I bricked my phone.......... i did do all the steps in it... still it crippled the phone....
here is the workaround i Did yesterday.....
1) I made a copy of platform.xml in my sd card
2) edited the card using note++ in my pc like below...
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
<group gid="media_rw" />
</permission>
3) copied the modifed file again to sd card
4) rebooted the mobile to twrp recovery
5) using mount option mounted system & sd card
6) using advanced option, renamed the original platform.xml to platform.xml.org
7)copied the platform.xml from sdcard to system location
8) using chmod i changed the permission to 644 ( check the owner information too )
9) reboot the mobile...
10) Now I can see my applications are not annoying about the write permission on the internal mem...
How is it ????? :good::good::good::good::good::good:
Click to expand...
Click to collapse
You would have missed something in wp_mod.ko tutorial. 1st time, problem happened with me also. I missed a step & cell got acting wierd, I did a factory reset & did it again.This time, I suceed.
Now no problem with writing in SDcard.
& Your platform.xml work is great. Post a thread with this tutorial.
jithumon said:
You would have missed something in wp_mod.ko tutorial. 1st time, problem happened with me also. I missed a step & cell got acting wierd, I did a factory reset & did it again.This time, I suceed.
Now no problem with writing in SDcard.
& Your platform.xml work is great. Post a thread with this tutorial.
Click to expand...
Click to collapse
done Bro....... http://forum.xda-developers.com/desire-816/general/htc-816-how-to-modify-platform-xml-file-t2812543
SivasankarC said:
done Bro....... http://forum.xda-developers.com/desire-816/general/htc-816-how-to-modify-platform-xml-file-t2812543
Click to expand...
Click to collapse
Great :highfive:
Hello!
I have a Samsung Galaxy S4 mini, i9195. I wanted to get rid of knox, however, in my lack of knowledge, I messed up my stock firmware and I haven't created any sort of backup. I then downloaded and flashed a custom ROM to replace the stock firmware so the phone could be used again. Is there any way I can reset my phone to its original stock firmware?
If there already exists a forum that can solve my problem, please let me know. I'll delete this one and submit my problem on the already existing forum. So far I haven't found a forum for this specific device.
Any help is appreciated,
Thank You!
trollcat37 said:
Hello!
I have a Samsung Galaxy S4 mini, i9195. I wanted to get rid of knox, however, in my lack of knowledge, I messed up my stock firmware and I haven't created any sort of backup. I then downloaded and flashed a custom ROM to replace the stock firmware so the phone could be used again. Is there any way I can reset my phone to its original stock firmware?
If there already exists a forum that can solve my problem, please let me know. I'll delete this one and submit my problem on the already existing forum. So far I haven't found a forum for this specific device.
Any help is appreciated,
Thank You!
Click to expand...
Click to collapse
U can "reset" it by downloading a rom from sammobile and flash it with Odin Factory reset before flash and do not let it boot , enter download mode imediatly
If u DO NOT have Knox bootloader on your phone now, try to download an older rom made before nov 2013
Something like MH2 3 or so
Hello and thank you for your reply!
Can you please tell me what the difference is between flashing an OS with Odin and installing it via CWM?
So far, I've only installed CWM bootloader with Odin and installed all my OS through CWM recovery.
Thank you.
Hello!
I did as you asked. Flashed this firmware through Odin, from Sammobile (can't post links yet):
Model: GT-I9195
Model name: GALAXY S4 mini LTE
Country: Romania (Vodafone)
Version: Android 4.4.2
Changelist: 1646188
Build date: Tue, 27 May 2014 08:17:05 +0000
Product Code: CNX
PDA: I9195XXUCNEA
CSC: I9195VFRCNE4
MODEM: I9195XXUCNEA
When the process is almost complete, I get the following errors:
On my Phone:
Odin: Invalid ext4 image
On the Odin Interface:
[....]
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
trollcat37 said:
Hello!
Thanks
Click to expand...
Click to collapse
http://www.s4miniarchive.com/2014/07/solution-what-to-do-when-odin-fails-at-hidden.img.ext4.html
Solved
SOLVED!
Hello and thank for your quick replies!
Indeed, CWM seems to solve this error.
Now to see how I can remove read only restriction from my SD card, but that's a problem for a different post
Thank You!
trollcat37 said:
SOLVED!
Hello and thank for your quick replies!
Indeed, CWM seems to solve this error.
Now to see how I can remove read only restriction from my SD card, but that's a problem for a different post
Thank You!
Click to expand...
Click to collapse
U can fix it with root and an root browser / editor like Solid Explorer
Replace in : system/etc/permissions/platform.xml
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
With
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Hello and thank you for the continued assist!
My /system is read-only.
CWM asks you to restore root privileges should they have been lost, what does that actually do? I don't seem to have root access on my phone.
Do I absolutely need SuperUser to bypass the read-only restriction on /system?
//Since the thread has changed subject, I will change title to add "read-only sd card" problem as well, after I find a solution.
Thanks
Hello and thanks again,
Nvm the post above. I was just trying to understand how rooting works.
I solved my problems. Installed SuperSU (zip) through CWM. Had to update to newest version to solve "SuperSU has stopped working" problem.
I then granted superuser to Solid Explorer to modify platform.xml (FX file explorer couldn't do it). I did the modifications as you said.
Now, apps can modify sd card
Thanks a lot!
First and foremost I apologize if this happens to be the wrong forum for this thread. I also apologize if this has been covered, which i'm sure it has; but I've been googling and searching these particular forums for a while and cannot find this exact problem addressed. Not saying it's not there, simply that I cannot find it.
Second I'd like to ask: Is it inadvisable to upgrade beyond Kit-Kat on an SGH-M919? I have been thinking about checking out lollipop or even marshmallow, but I don't know if I would be shooting myself in the foot, what with the phone being several generations old and having dated phys. specs and hardware.
Now to the meat of my inquiry:
Recently I rooted my phone. As a newbie I wanted to take the path of least resistance. So KingRooot was the route I ended up going. I was very happy with it initially, but then realized the mistake I had made; while attempting to update my phones OS I was alerted to the fact that changes made to the OS prohibited me from going the normal route within the phones settings.
So my plan is to restore my phone to factory defaults, update as far as I can, then root using CWM/ODIN. I'm using this guide at androidrootz which seems to be very comprehensive and laid out in laymen's terms. ( attempted to link the tutorial but was thwarted by anti-spamming measures)
What I am wondering though, is if I find a way to upgrade my phone beyond KitKat, will this same root process work once the operating system has been fundamentally changed?
Additionally I'd like to know if there Is a possibility that I can flash the factory reset to revert to a fresh, rooted version of my new chosen OS? I understand that the aforementioned CWM will do exactly that, but presumably with the current installation of Kit-Kat, and not with whatever I manage to update it to, with rooting included.
I appreciate any input you may have, and once again apologize for my noobish nature
I would also like to add that I have never used Odin previously. I understand that it would allow me to flash whatever I wanted for the most part, but as someone who is new to modifying phones (and who is rather poor and with bad credit) I am overly cautious to do anything that might harm my phone. I understand that odin is well known and trusted, but it's my own lack of knowledge and experience in this field that I do not trust. Once again, thanks in advance for your patience and for any help provided.
Here is my recommendation:<br />
Download AOKP 6.0.1, which is what I am using every day on my M919.
http://forum.xda-developers.com/showthread.php?p=67161650
Then, follow these instructions:
<br />
If you use Windows instructions<br />
<br />
Go to: https://dl.twrp.me/jfltetmo/<br />
and download 3.0.2-0 tar<br />
<br />
Then, download this:<br />
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip<br />
<br />
-Unzip Odin.<br />
-Turn on your phone (normal turn on) boot up into the stock system.<br />
-plug in your phone, let Windows find the drivers.<br />
-Once Windows found your drivers, unplug the phone, turn your phone off.<br />
-open Odin.exe<br />
-Click on PDA, and choose the TWRP file you downloaded.<br />
-With your phone unplugged and off, Now press and hold the DOWN volume button and the power button.<br />
-When the phone vibrates, you can release the power button, but keep holding the down button.<br />
-You will see a warning screen. Release the down button, and press the volume up button to enter "download" mode.<br />
-Plug your phone into the computer.<br />
-Press start/ok button on Odin.<br />
<br />
You should see a blue bar on your phone screen that fills up from left to right. Odin should say "pass" or "success". Your phone should automatically reboot itself. If this did not happen, seek help. Seriously. <br />
<br />
-Plug your phone into the computer again, and copy the Gapps and Rom from post #1 to your external sdcard of your phone.<br />
-Now, turn off the phone again.<br />
-Hold the UP volume button, and the power button.<br />
-When the phone vibrates, you can release the power button, but keep holding the UP volume button.<br />
-You will enter TWRP. Now you can release the UP volume button.<br />
-You should now MAKE A BACKUP TO YOUR EXTERNAL SDCARD. -With this, you can always go back!<br />
-After making a backup, you should wipe your phone. Select wipe, slide the slider to wipe your phone. This will not wipe your external sdcard.<br />
-Install Rom.<br />
-Wipe Cache and Davlik.<br />
-Install Gapps. - Optional<br />
-Reboot to system and enjoy!<br />
Click to expand...
Click to collapse
<br />
<br />
If you use Linux instructions<br />
<br />
Go to: https://dl.twrp.me/jfltetmo/<br />
and download 3.0.2-0 img<br />
<br />
and download this:<br />
http://www.mediafire.com/download/6bbr7f9049uh338/m919.pit<br />
<br />
Then, <br />
$ sudo apt-get heimdall heimdall-frontend -y<br />
<br />
$ sudo heimdall-frontend<br />
<br />
-This will open up heimdall. Click the tab called "Flash"<br />
-Under "pit" click browse.<br />
-Choose the pit file you downloaded.<br />
-Under partitions(files), click "add"<br />
-Under Partition Details, click partition name, and click recovery.<br />
-Under File (recovery.img), click browse.<br />
-Choose the 3.0.2-0 img you downloaded.<br />
-Click on the "Utilities" tab.<br />
-With your phone unplugged and off, Now press and hold the DOWN volume button and the power button.<br />
-When the phone vibrates, you can release the power button, but keep holding the down button.<br />
-You will see a warning screen. Release the down button, and press the volume up button to enter "download" mode.<br />
-Plug your phone into the computer.<br />
-Under Detect Device, click "detect" - the Output box will say something like, detected.<br />
-Click on the Flash tab.<br />
-Under Session, click "start"<br />
<br />
You should see a blue bar on your phone screen that fills up from left to right. Heimdall should say "pass" or "success". Your phone should automatically reboot itself. If this did not happen, seek help. Seriously. <br />
<br />
-Plug your phone into the computer again, and copy the Gapps and Rom from post #1 to your external sdcard of your phone.<br />
-Now, turn off the phone again.<br />
-Hold the UP volume button, and the power button.<br />
-When the phone vibrates, you can release the power button, but keep holding the UP volume button.<br />
-You will enter TWRP. Now you can release the UP volume button.<br />
-You should now MAKE A BACKUP TO YOUR EXTERNAL SDCARD. -With this, you can always go back!<br />
-After making a backup, you should wipe your phone. Select wipe, slide the slider to wipe your phone. This will not wipe your external sdcard.<br />
-Install Rom.<br />
-Wipe Cache and Davlik.<br />
-Install Gapps. - Optional<br />
-Reboot to system and enjoy!<br />
Click to expand...
Click to collapse
<br />
<br />
Let us know if you need more help! If anybody else sees an error here, then let us know so we can get this guy on the right path.
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
Okay thank you very much for the prompt reply. I just have a few further questions,s then I will try it when I get home.
As far as the first thing you mentioned downloading, The aokp 6.0.1... am I correct in my assumption that this version number is referring to the version of android? I.e. will it install marshmallow?
Also you say to transfer gapps and some other files to my sd card. Must it be in Abby specific dinner
Folder/partition? Or is it just the root directorY I'm shooting for?
xer0615 said:
Okay thank you very much for the prompt reply. I just have a few further questions,s then I will try it when I get home.
As far as the first thing you mentioned downloading, The aokp 6.0.1... am I correct in my assumption that this version number is referring to the version of android? I.e. will it install marshmallow?
Also you say to transfer gapps and some other files to my sd card. Must it be in Abby specific dinner
Folder/partition? Or is it just the root directorY I'm shooting for?
Click to expand...
Click to collapse
Great questions!
First, AOKP 6.0.1 is Marshmallow, however, some ROMs have version numbers that do not correlate with Android versions, but in this case it does.
Second, you can put the files anywhere on your phone, however, keep in mind that after you backup your old system (so you can always go back) the next step is to wipe the phone, so you should put the files on the external sdcard, because you will not wipe that.
Clear as mud?
Also, there are other great ROMs to use, but AOKP is very stable and everything works. Post #3 of that thread has some great tips for any problems with Bluetooth, if you run into any, and there are many people there (including me) who can answer any questions you have. We don't discriminate against newcomers.
Let me know if you have more questions!
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
Edit: Also, sorry the above instructions have the line brakes (br) in there, I copied from my post in the AOKP thread, and it came out that way. It is post #153 of the AOKP thread, if you want to read it without the br's in there.....
AlaskaLinuxUser said:
Great questions!
First, AOKP 6.0.1 is Marshmallow, however, some ROMs have version numbers that do not correlate with Android versions, but in this case it does.
Second, you can put the files anywhere on your phone, however, keep in mind that after you backup your old system (so you can always go back) the next step is to wipe the phone, so you should put the files on the external sdcard, because you will not wipe that.
Clear as mud?
Also, there are other great ROMs to use, but AOKP is very stable and everything works. Post #3 of that thread has some great tips for any problems with Bluetooth, if you run into any, and there are many people there (including me) who can answer any questions you have. We don't discriminate against newcomers.
Let me know if you have more questions!
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
Edit: Also, sorry the above instructions have the line brakes (br) in there, I copied from my post in the AOKP thread, and it came out that way. It is post #153 of the AOKP thread, if you want to read it without the br's in there.....
Click to expand...
Click to collapse
Yes quite clear, thanks again for the quick response.
I understand that it's stable, per your response but I wonder what its impact on my performance might be?
I find that this phones battery capacity is a bit underwhelming. Draining sometimes less than eight hours. Will upgrading to marshmallow make things worse?
I've Been thinking about buying an extended internal battery but am reluctant to ditch my otterbox.
Thanks again
xer0615 said:
Yes quite clear, thanks again for the quick response.
I understand that it's stable, per your response but I wonder what its impact on my performance might be?
I find that this phones battery capacity is a bit underwhelming. Draining sometimes less than eight hours. Will upgrading to marshmallow make things worse?
I've Been thinking about buying an extended internal battery but am reluctant to ditch my otterbox.
Thanks again
Click to expand...
Click to collapse
It runs smooth as butter, check out the thread if you would like. Runs great, but you are welcome to choose any ROM you like. That's the best part about Android!
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
I just went through your step 100% to the T. The process was pretty smoothe, until I got tot he GAPPs bit. Upon atempting to install GAPPS, I was alerted that there was not enough space . Now it's booting up. I loved the AOKP splash screen. Currently getting the "Android is startnig.. Optimiznig app ##x out of ##y".
So this whole process not only got me on marshmallow, but also granted me root access and replaced the restore point with one of the image I jut installed? Am I correct in my understanding?
EDIT: Could not find means to delete.
xer0615 said:
I just went through your step 100% to the T. The process was pretty smoothe, until I got tot he GAPPs bit. Upon atempting to install GAPPS, I was alerted that there was not enough space . Now it's booting up. I loved the AOKP splash screen. Currently getting the "Android is startnig.. Optimiznig app ##x out of ##y".
So this whole process not only got me on marshmallow, but also granted me root access and replaced the restore point with one of the image I jut installed? Am I correct in my understanding?
Click to expand...
Click to collapse
Great work!
As for the gapps, there is not enough room for the bigger gapps package, because those are huge, once uncompressed. I use arm, 6.0, pico or nano, personally. If you have trouble installing these gaps, go to twrp, wipe, install ROM, then wipe davlik/cache, then install pico or nano gapps.
As for your questions, yes, you are now marshmallow with root permission. You can test this with any app that needs root, it will pop up and ask if that app can have root permission, to which you can click yes or no, or just this once, etc.
Welcome to the AOKP!
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
AlaskaLinuxUser said:
Great work!
As for the gapps, there is not enough room for the bigger gapps package, because those are huge, once uncompressed. I use arm, 6.0, pico or nano, personally. If you have trouble installing these gaps, go to twrp, wipe, install ROM, then wipe davlik/cache, then install pico or nano gapps.
As for your questions, yes, you are now marshmallow with root permission. You can test this with any app that needs root, it will pop up and ask if that app can have root permission, to which you can click yes or no, or just this once, etc.
Welcome to the AOKP!
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
Click to expand...
Click to collapse
Thanks very much once again for your help
After a couple of hours of toying around with Marshmallow I ended up trying out slimkat, which I find to be a lot more ot my liking. But I used the same steps you provided me for that intsallation as well.