Related
Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
seabhac said:
Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
Click to expand...
Click to collapse
Wipe in clockwork. factory reset/cache/dalvik cache to do a full wipe. the kernel, depending on which one it is, is slightly over clocked. also rom manager does cause problems when installing roms. download them on your pc, or browser via the phone, place on teh root of the sd card (not in a folder) and flash in clock work
seabhac said:
Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
Click to expand...
Click to collapse
Sounds like you read up on the topic. Thank you. My only advice is that the gb roms all have tiny little bugs in them. Read up and if you don't care go for it.
If you want a completely stable phone... Stick with a group Rom. If you want all the cool new features and don't mind working around a few bugs... Go gb. Also make.sure to use the correct radio. Probably the MR 2!
Good luck.
seabhac said:
Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
Click to expand...
Click to collapse
I only use ROM Manager to reboot into ClockworkMod Recovery. It is the second option when you open ROM Manager. My method of flashing a new ROM (performing a full wipe plus a few steps):
1. Reboot into ClockworkMod Recovery from ROM Manager.
2. Use Nandroid to backup your current configuration. Select backup and restore and then backup.
3. Select wipe data/factory reset. This will wipe all applications, contacts, text messages, bookmarks, etc. There are ways to back this information up (Titanium Backup for applications), but I will not go into full detail here.
4. Select wipe cache partition.
5. Select advanced and then wipe dalvik cache. (Most people recommend doing steps 4 and 5 three times in order to ensure it was done.)
6. Also in the advanced menu, select wipe battery stats. (You should do this when charged 100%, recommended for any new ROM flash.)
For some reason, if you flash in ROM Manager it can corrupt the ROM/flash. To avoid this, always use ClockworkMod Recovery.
If the ROM you flash utilizes one of Imoseyon's kernels (which BAMF does), you can use the speedtweak.sh method in terminal emulator (download from Market) descriped in Imoseyon's kernel thread. With a BAMF ROM, none of this is required. You can utilize the included BAMF Toolkit to overclock/underclock and set the governor. The Toolkit also includes a terminal emulator if you wish to try the speedtweak.sh method.
The above steps should be followed when flashing a new ROM. When upgrading versions of the same ROM, you can generally perform a minimal wipe. My understanding of a minimal wipe is the cache and dalvik cache only (three times).
Hope I didn't leave anything out. If so, others can correct me.
Thank you for describing this.. I watched several videos and read up alot but I don't want to mess up anything and do ti right.. I've got the BAMF remix 2.05 version 6 on my root directory on the SD card now and I'll wait till the phone is at full charge before running thr0ough this procedure. Thank you once more wool!
seabhac said:
Thank you for describing this.. I watched several videos and read up alot but I don't want to mess up anything and do ti right.. I've got the BAMF remix 2.05 version 6 on my root directory on the SD card now and I'll wait till the phone is at full charge before running thr0ough this procedure. Thank you once more wool!
Click to expand...
Click to collapse
You will also have to flash the MR2 radio. There is a thread in the Development Forum. If you search the thread, you should be able to come up with the method to do this.
http://forum.xda-developers.com/showthread.php?t=1115714
I flashed the ROM first, pulled the battery, and then booted in hboot (volume down plus power button). From there, hboot should find the radio and update. Most importantly, make sure the radio file you put on the root of your SD Card is named 'PG05IMG.zip' If you have Windows 7, make sure the .zip is not in there twice. By default, Windows 7 does not show file extensions.
to be safe with ur download make sure to check the md5
command in terminal and adb is
# /system/xbin/busybox md5sum /sdcard/so-so
i think.. lol
checking the md5 ensures ur download is legit.. i had a couple bad downloads causing bootloop.
Sent from my ADR6400L using XDA App
alluzzion2o9 said:
to be safe with ur download make sure to check the md5
command in terminal and adb is
# /system/xbin/busybox md5sum /sdcard/so-so
i think.. lol
checking the md5 ensures ur download is legit.. i had a couple bad downloads causing bootloop.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Easy way with the MD5 I found is to download AFV (Android File Verifier) from market. I download the ROM from xda app onto phone, run AFV on ROM from phone and verify MD5 while also having thread up on computer. Seems easier with those long numbers.
I have discontinued support for this since S-OFF is available.
New Update! Easier Than Ever!
How To Install You New Kernel!
With drellisdee's Main Version Fix
Instructions
DEVS: New versions are added. Two zips are attached. One is for flashing zImages, one is for flashing boot images.
Just put the contents up the updater script into your rom along with the kernel folder.
For the zImage one, put a zImage named "zImage" in the kernel folder. For a boot image, put a boot.img named "boot.img" in the kernel folder. Each zip has the appropriate scripting for that type of file. For a rom, it is likely you want the boot image version.
This fixes the main version so that will no longer be an issue with rom installations thanks to drellisdee
OLD NOTES: (Ignore )
-1)Flash the rom of your choice and the boot image distributed with it via a PH98IMG.zip. If it doesn't come with one, just move on.
0)Flash the kernel you want's zip file in recovery. Also make sure there are no existing PH98IMG.zip files on your sdcard
1)Download AutoKernelInstaller.zip attached to my post.
2)Extract the zip
3)If you want ziggy's kernel, move to step 4. If you want another kernel, find the zImage file in the kernel's zip folder and copy it to the kernel folder from my zip file. It should overwrite the zImage file in there now.
4)Run buildFlashable.bat
5)Flash the flashmeinrecovery.zip in recovery
6)My scripts in flashme.zip will perform all of the work to create a PH98IMG.zip and then will automatically reboot to HBOOT
7)Press the power button in HBOOT to select bootloader
8)Select Yes for installing the new boot.img
9)Done Your kernel is installed!
To users, you can now use this to flash your own kernels without needing someone else to make it a boot.img specific to a certain rom. You will still need to flash the kernel's zip file in recovery to get the extra stuff the kernel comes with, such as a wifi module. These steps are in addition to that process.
To devs, feel free to add this script to your kernel zip files so S-ON devices can use it without boot.img creation knowledge and so that you don't have to distribute hardcoded boot.img files.
Why is all this necessary? You most likely didn't have to jump through these hoops to install kernels on your other devices...
As most of you have figured out, installing kernels is a multi-step process on the Rezound. First, files for the system partition need to be flashed in recovery. Then a boot.img needs to be flashed that contains the kernel and the ramdisk.
Unfortunately, since the ramdisk changes from rom to rom, kernels cannot be distributed as boot.img files. Therefore, they are impossible to flash without conversion. If you have installed ziggy's kernel, you have probably used my premade flashables. Those are fine for now, until ramdisks begin to change from rom to rom. This flashable zip will insert a kernel into a rom's boot image and then package it into a PH98IMG.zip that is flashable from the bootloader (HBOOT) without fastboot,adb, or PC knowledge required. This saves a ton of work for the user and allows kernels to be compatible with ANY rom.
Click to expand...
Click to collapse
Returning to stock
http://forum.xda-developers.com/showpost.php?p=20990402&postcount=2
Good lookin out on all of this Con...you along with the other developers have been awesome in getting dev for the Rezound off the ground. Thank you!
Marcismo55 said:
Good lookin out on all of this Con...you along with the other developers have been awesome in getting dev for the Rezound off the ground. Thank you!
Click to expand...
Click to collapse
I am no dev. I have no idea how to make a kernel/rom (for the most part). I just know what with and why users struggle with things and I try to simplify and automate as much as possible. It is better to leave the "real" work for the devs so they don't have to waste time doing things that I can help with.
Just out of curiosity, does flashing that first file wipe the internal memory? Not the one with ROM and stuff on it, but the one where your TiBackups are stored and such, because after I flashed the kernel, all my Titanium backups were gone and the internal memory was wiped. I didn't lose anything because I made copies to my desktop computer, but if I hadn't, I would have lost all that stuff. Maybe I did something wrong, but I don't think so, because I followed instructions, and the kernel is installed and working fine.
Evo4gLI said:
Just out of curiosity, does flashing that first file wipe the internal memory? Not the one with ROM and stuff on it, but the one where your TiBackups are stored and such, because after I flashed the kernel, all my Titanium backups were gone and the internal memory was wiped. I didn't lose anything because I made copies to my desktop computer, but if I hadn't, I would have lost all that stuff. Maybe I did something wrong, but I don't think so, because I followed instructions, and the kernel is installed and working fine.
Click to expand...
Click to collapse
This flashable wipes nothing. It just creates a new flashable boot image from what is already on your device.
con247 said:
This flashable wipes nothing. It just creates a new flashable boot image from what is already on your device.
Click to expand...
Click to collapse
Any insight into what may have happened then? Because it was all there before I flashed the kernel, and then it was gone afterwards.
Did you do a data wipe or something? Did you install a new rom?
I actually had the same thing happen to me. Almost all my apps were missing one I installed the kernel. It was odd
sent from my newly unlocked Rezound
pwned3 said:
I actually had the same thing happen to me. Almost all my apps were missing one I installed the kernel. It was odd
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Fixed the issue. It was in the PH98IMG.zip it just happened to me also. Sorry guys! Files in 1st post are fixed!
complete noob!!!!!
CON247, you are a huge help with all this and I appreciate your work. Your step by step directions are helpful but sometimes still confusing for noobs. Are there step by step instructions for this that explains what each steps does and why it need to be done? I want to flash a kernel but I'm not sure how to perform all the steps listed here but wish to learn.
Even better knowing so much of this is being done by a fellow Wolverine fan.
Thanks Con. I knew it couldn't have been something I did...I've done my fair share of flashing and I hadn't done anything different, I just wanted to make sure it didn't happen to anyone without a copy of their files.
Sent from my HTC Rezound via Tapatalk
Thanks for the hard work on this, one question..what does boot into Hboot mean exaclty? this is not recovery right? is this remove the batter and hold down volume down and power boot thing?
thanks
---------- Post added at 04:17 PM ---------- Previous post was at 04:03 PM ----------
nvm got it
Yessir. It will ask you if you want to update then you hit yes
Sent from my ADR6425LVW using XDA App
Just had my first issue with mismatching ROM and boot.img.... all the current roms are based on the original kernal, so if a user has flashed Ziggy's kernal then flashed over any of the existing rom's, functionality becomes lost (such as Wifi in my case). The fix is easy just flash Ziggy's kernal and not touching the boot.img in hboot, but this did cause some confusion.
Anyway, this is a great idea, and I believed it should be stickied (and the title changed from [idea] to [boot.img Standard] !!!!
Found this from your reply on the other post and followed these instructions. I happened to get my issue fixed and I am back up and running! Thanks!
-mxair2001
Just noticed that the Amon Ra recovery has an option under the Developer menu option to build a boot image from a zimage. Anyone tried that, and does it also fix the ramdisk files too?
Marine6680 said:
Just noticed that the Amon Ra recovery has an option under the Developer menu option to build a boot image from a zimage. Anyone tried that, and does it also fix the ramdisk files too?
Click to expand...
Click to collapse
That would be awesome, but we can't flash the boot image from recovery. I have a newer version of this tool coming soon I think (assuming it works lol)
New version up. It is really easy now. It is only a few clicks.
Thank you for making this a little easier. I used it flawlessly to try ziggy's kernel again
sent from my newly unlocked Rezound
pwned3 said:
Thank you for making this a little easier. I used it flawlessly to try ziggy's kernel again
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Are the instructions clear enough? I wish this would get stickied. People who keep flashing a boot.img from the stock roms on a custom rom will eventually boot loop.
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options. It is also relevant to know just how much information you want to recover.
File replacement:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- will retain all existing data & customization. Maybe worth a try, but I don't recommend it
Dirty-flash:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You will be able to flash a (custom) samsung-based firmware, which WILL overwrite /system, but will NOT overwrite your /data partition, likely allowing you to boot and properly back-up the stuff you want to keep, or even create a nandroid of the existing setup. <-- Will retain all existing data, will lose /system customisations. I have used this method.
Start-fresh:
Use desktop-Odin to flash the official firmware may be your only other option, which will retain everything in internal memory (photos, downloads, music, nandroid backups), but not messages, or any app data.
-Cyril
Mr. Barker said:
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
Click to expand...
Click to collapse
cyril279 said:
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options.
Click to expand...
Click to collapse
Well I do have CWM installed, but am curiously (and annoyingly) unable to boot to it now, for whatever reason. It boots to stock recovery instead, every time.
cyril279 said:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- maybe worth a try, but I don't recommend it
Click to expand...
Click to collapse
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Mr. Barker said:
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Click to expand...
Click to collapse
I would be glad to provide more detailed information, but I prefer to do so from a desktop computer, and I won't be near one for several days, so this may be a slow process unless one of our peers steps in to help.
In the meantime, you should gather:
-Odin 1.85 or 3.07
-A Siyah s2-v5.x or s2-v6.x .tar.md5 kernel (for the i777 or i9100)
The latter you can find at http://www.gokhanmoral.com
I will outline the process in a later post, explaining the purpose of each step.
Sure, I'm OK waiting a few days. I appreciate the help, I haven't done any flashing in quite some time and don't want to make a mistake, especially with all the important data that's at stake.
Thanks.
File Replacement Method
1) Use desktop Odin to flash Siyah kernel
-Installs a kernel that will allow you to perform a nandroid backup, and MAY allow you to adb push the missing file to the device.
-This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
-If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Adb push missing file to /data/path_file_belongs
5) Shell chmod XXX the missing file
-to correct file permissions; that 0.xml file has -rw------ on my device, which translates to 600 (I think)
6) Flash appropriate ajk kernel
-for stock jb, use "NoSwap" http://forum.xda-developers.com/showthread.php?t=2110542
-custom kernel that will boot stock rooted android.
7) Attempt Reboot into android
-If successful, reboot to recovery and perform another backup.
-If not successful, then we use a different method.
This is the trickier method of the three, but will retain all customization if it works. I have not tried it, and we're assuming that the missing file is actually the problem.
Please be sure that you are comfortable with all of the steps before attempting any of them. I will be able to provide step by step instructions, but not for several days.
Happy flashing,
-Cyril
Well, that was fun. Followed the instructions to a "t" and even learned some things. But, sadly, did not achieve the results I'd hoped for.
I was indeed able to push the wallpaper file over to data\system\users\0 and CHMOD it. But after flashing AJK "NoSwap" the phone shows the "Android is upgrading..." message, with "Starting apps." trying to process. But it doesn't. The little circle swirls a bit, then the screen goes black. The "Starting apps." message appears again, then the screen goes black again. And then it repeats this cycle forever. I eventually got irritated and yanked the battery.
So... *sigh*... what's my next best option?
The Nandroid backup completed successfully? If so, that's great, any APP customization is likely captured in the backup. How well they will restore is a different concern, but we need to get the device booted completely into android first.
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
cyril279 said:
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
Click to expand...
Click to collapse
I say wipe caches and fix permissions first. If that doesn't work format /system, and install a ROM of the same version of android.
After that if it's still not booting suck it up do a full wipe and start from scratch.
Sent from my SGH-S959G
@Mr. Barker
If the cache wipes / permissions fix doesn't help, then our next attempt is:
**this assumes that you were running stock Android 4.1.2 when the trouble began**
get i777UCMD8 cooked v2.2 onto a flashdrive, (or prepare it for sideload)
reboot to recovery
format /system
install cooked v2.2
attempt to boot into android
OK, I'll give it a try, thanks.
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM is needlessly flashy.
Mr. Barker said:
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the black notification pull-down menu? This ROM sets it transparent by default, which doesn't work for me.
Click to expand...
Click to collapse
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
To change the notification background go to the mods section of the installer, and just install the black notification background.
Sent from my SGH-S959G
mr-cook said:
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
Click to expand...
Click to collapse
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
"needlessly flashy"
Simply asking 'how to change the icon' is sufficient, and inherently implies that you prefer something different.
Cooked v2.2 is definitely quicker than stock;
The premise of both cooked and shostock are that they have taken the stock firmware, and stripped it down of unnecessary junk, and run it over a well-optimized kernel for the best touchwiz experience that you could possibly have on this device.
If your firmware desires are different than what cooked v2.2 provides, then I suggest creating a nandroid backup, wiping /system, and giving shostock a try. It's the other touchwiz favorite for the i777, packaged with a different very good kernel, and also runs quicker than stock.
Mr. Barker said:
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
Click to expand...
Click to collapse
To close the loop, now your initial boot screen is a yellow triangle with an exclamation point? It doesn't affect the functionality of the firmware at all, but if you prefer to have the correct initial boot animation, then you'll need to follow an additional procedure.
Summary:
Nandroid-backup desired setup
Flash official stock-firmware to the device via Desktop-Odin (clears the warning)
Root & recovery via Framaroot/Mobile-Odin (a method that does NOT trip the custom-flash monitor)
Restore nandroid to return to the established custom setup
Procedure:
gather onto internal memory, or micro-sd:
-Framaroot
-Mobile Odin APK
-Mobile Odin flash kernel for i777
-Boot.img (extracted from your chosen firmware.zip)
boot to recovery
perform nandroid backup
^^ this MUST complete successfully
perform factory reset
boot to download mode
flash official UCMD8 using Desktop ODIN
^^ clears the custom-flash warning
install and use framaroot
^^ uses an exploit to establish and manage root access
install mobile Odin and the mobile Odin flash-kernel
^^ the method that will NOT trip the custom-flash monitor
flash the boot.img via Mobile Odin
^^ flashes the kernel and recovery of the firmware that you are going to restore
boot to recovery
restore nandroid backup
enjoy
-Cyril
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup? Or could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards) My point is, are nandroid backups firmware-specific?
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Before all this I've never flashed anything but stock firmware, and never had to create nor restore nandroid backups. So most of this is all new to me. But I enjoy the learning process.
Mr. Barker said:
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup?
Click to expand...
Click to collapse
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Edit: As Mentioned below, a CWM nandroid will restore the entire backed-up firmware installation, which can be done over ANY firmware.
If the goal is to keep your App data across different firmwares, then a Titanium backup restoration may be what you're after. /Edit
Mr. Barker said:
[...]could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards)[...]
Click to expand...
Click to collapse
I don't think that the stock recovery allows to restore nandroid backups at all. The restrictive nature of the stock recovery is one of the more practical reasons to root the device & use a custom kernel.
Mr. Barker said:
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Click to expand...
Click to collapse
Mobile Odin will flash a zImage, no need to rename it. I didn't check to see that shostock or cooked use a zImage instead of boot.img.
cyril279 said:
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Click to expand...
Click to collapse
?? I thought that because a nandroid copied (backup) and then formatted/recopied the 5 partitions (restore), that it didn't matter what firmware you had installed?
So I was using an old fw with jmz kernel and as a device, it worked great with minimal bugs but found out today I wasn't receiving a lot of phone calls and texts. After rebooting I got all my missed calls & messages!
So obviously I have to make a change. I just ran the newest ruu. I'm wondering if anyone is actually using JMZ still and if so what type of behavior are you experiencing?
I know I can buy s-off but I still can't justify $25. Plus sometime in the next six months I'm getting a new phone and I think if I go with HTC I'll need to pay another 25 for s-off (think that's how it works?)
Thanks.
KLit75 said:
So I was using an old fw with jmz kernel and as a device, it worked great with minimal bugs but found out today I wasn't receiving a lot of phone calls and texts. After rebooting I got all my missed calls & messages!
So obviously I have to make a change. I just ran the newest ruu. I'm wondering if anyone is actually using JMZ still and if so what type of behavior are you experiencing?
I know I can buy s-off but I still can't justify $25. Plus sometime in the next six months I'm getting a new phone and I think if I go with HTC I'll need to pay another 25 for s-off (think that's how it works?)
Thanks.
Click to expand...
Click to collapse
I've been using JMZ kernel for 8 months straight, combined with a stock asia rom that has all htc and google bloat removed and then deodexed. I have not had any problems at all, but for the last six months I am using a JMZ kernel that I compiled myself from his sources. I don't think that has made any difference but there are 3 versions of his source on his github so the 1 I compiled may be a little different. I also set up a phone fore a freind who wanted to keep running stock kernel but with a modified stock asia rom. We just extracted the JMZ kernel zip then boot to twrp(to keep his stock recovery in place we did this buy putting the phone in fastboot mode, then with TWRP****.img file in your fastboot directory run
fastboot boot TWRP****.img
which reboots the phone to TWRP without flashing it). Then from TWRP do a full backup for safety and to be able to return to full stock easily. While still in TWRP connect to the phone via ADB and run
adb push \path_to_extracted_jmz_kernel\system\lib\modules /system/lib
(this just adds modules from jmz kernel to you system so it can load propery)
I don't think this step is nesesary but next from in TWRP we did Advanced Fix Permisions to ensure the modules we just added have the corect permisions set.
Now you can boot to JMZ kernel (without flashing it and keeping stock kernel and recovery on your phone)when you want to make changes to your system that will stick after reboot (like sdcard fix,wifi tethering fix,supersu,xposed) by putting your phone in fastboot mode then with the boot.img extracted from JMZ kernel in your fastboot directory run
fastboot boot boot.img
this will reboot running JMZ kernel and when you make changes to the system then reboot the changes will stick but you reboot back to stock kernel.
Hope this helps someone
MiniBlu
MiniBlu said:
I've been using JMZ kernel for 8 months straight, combined with a stock asia rom that has all htc and google bloat removed and then deodexed. I have not had any problems at all, but for the last six months I am using a JMZ kernel that I compiled myself from his sources. I don't think that has made any difference but there are 3 versions of his source on his github so the 1 I compiled may be a little different. I also set up a phone fore a freind who wanted to keep running stock kernel but with a modified stock asia rom. We just extracted the JMZ kernel zip then boot to twrp(to keep his stock recovery in place we did this buy putting the phone in fastboot mode, then with TWRP****.img file in your fastboot directory run
fastboot boot TWRP****.img
which reboots the phone to TWRP without flashing it). Then from TWRP do a full backup for safety and to be able to return to full stock easily. While still in TWRP connect to the phone via ADB and run
adb push \path_to_extracted_jmz_kernel\system\lib\modules /system/lib
(this just adds modules from jmz kernel to you system so it can load propery)
I don't think this step is nesesary but next from in TWRP we did Advanced Fix Permisions to ensure the modules we just added have the corect permisions set.
Now you can boot to JMZ kernel (without flashing it and keeping stock kernel and recovery on your phone)when you want to make changes to your system that will stick after reboot (like sdcard fix,wifi tethering fix,supersu,xposed) by putting your phone in fastboot mode then with the boot.img extracted from JMZ kernel in your fastboot directory run
fastboot boot boot.img
this will reboot running JMZ kernel and when you make changes to the system then reboot the changes will stick but you reboot back to stock kernel.
Hope this helps someone
MiniBlu
Click to expand...
Click to collapse
Wow! That's really clever. So essentially you're just borrowing the kernel as a tool to make the system s-off, make changes, then go back to stock. I've gotta do this when I have a chance. Hopefully you'll be around if I have questions. Thanks.
EDIT-Thing is though. with the exception of tethering I can get everything else working without using the kernel. KK sdcard fix doesn't stick but I found one to flash in recovery and it's working for me. Same thing with busy box and flashing in recovery is the only way I know of to get SU working.
Is there anything else useful I might be missing?
Turns out the bugs (missed phone calls) were related to the kernel. I thought it might be the audio jack but after lots of testing i narrowed it down.
KLit75 said:
Wow! That's really clever. So essentially you're just borrowing the kernel as a tool to make the system s-off, make changes, then go back to stock. I've gotta do this when I have a chance. Hopefully you'll be around if I have questions. Thanks.
EDIT-Thing is though. with the exception of tethering I can get everything else working without using the kernel. KK sdcard fix doesn't stick but I found one to flash in recovery and it's working for me. Same thing with busy box and flashing in recovery is the only way I know of to get SU working.
Is there anything else useful I might be missing?
Turns out the bugs (missed phone calls) were related to the kernel. I thought it might be the audio jack but after lots of testing i narrowed it down.
Click to expand...
Click to collapse
su can be installed by the above method but apart from that, only really to install exposed framework and modules.
The tethering fix can also be done from twrp, you just boot to twrp, press MOUNT and check box System, connect to it via adb ,"adb pull" the file you need to edit,edit it with notepad++,"adb push" the file back to the phone,run Advanced Fix Permisions in twrp, then Reboot and edited file will stick.
The method I descibed in last post is best suited to people in other regions who can't get RUU as it leaves original kernel and recovery in place so all you need to do is restore the original twrp backup of system partition and lock bootloader and your all good to get ota updates. And no red text at boot.
MiniBlu
MiniBlu said:
su can be installed by the above method but apart from that, only really to install exposed framework and modules.
The tethering fix can also be done from twrp, you just boot to twrp, press MOUNT and check box System, connect to it via adb ,"adb pull" the file you need to edit,edit it with notepad++,"adb push" the file back to the phone,run Advanced Fix Permisions in twrp, then Reboot and edited file will stick.
The method I descibed in last post is best suited to people in other regions who can't get RUU as it leaves original kernel and recovery in place so all you need to do is restore the original twrp backup of system partition and lock bootloader and your all good to get ota updates. And no red text at boot.
MiniBlu
Click to expand...
Click to collapse
Xposed now has the option to flash in recovery (after v2.5 something, I think) Never had problems with that.
However, I didn't even think about mounting system in recovery then editing the text. That's smart. I don't use tethering but wanna try this.
So since I can run the ruu which means no red text, I can write to ext sd, and whenever I want to make changes I can use mount in twrp--is there any reason to buy s-off?
Edit-- would I be able to edit the text and reboot to recovery THEN mount system and fix permissions?
I'm just wondering because I'm not sure exactly when changes made to the system get changed back...
Does it happen when we boot into the ROM, meaning if I boot recovery the changes haven't been reversed?
Or do they go away as soon as I boot to recovery, meaning there's nothing new to save?
***I know its not critical. Using my Mac to make the changes is easy enough but for future modifications it does save time.
Thanks for the info
KLit75 said:
Xposed now has the option to flash in recovery (after v2.5 something, I think) Never had problems with that.
However, I didn't even think about mounting system in recovery then editing the text. That's smart. I don't use tethering but wanna try this.
So since I can run the ruu which means no red text, I can write to ext sd, and whenever I want to make changes I can use mount in twrp--is there any reason to buy s-off?
Edit-- would I be able to edit the text and reboot to recovery THEN mount system and fix permissions?
I'm just wondering because I'm not sure exactly when changes made to the system get changed back...
Does it happen when we boot into the ROM, meaning if I boot recovery the changes haven't been reversed?
Or do they go away as soon as I boot to recovery, meaning there's nothing new to save?
***I know its not critical. Using my Mac to make the changes is easy enough but for future modifications it does save time.
Thanks for the info
Click to expand...
Click to collapse
The changes made to /system aren't wriiten to disk at all so they will be gone when you reboot to recovery. But you can edit the file and save it to /sdcard, then in twrp use Advanced File Manager to copy the file from /sdcard to /system.
MiniBlu said:
The changes made to /system aren't wriiten to disk at all so they will be gone when you reboot to recovery. But you can edit the file and save it to /sdcard, then in twrp use Advanced File Manager to copy the file from /sdcard to /system.
Click to expand...
Click to collapse
Didn't even think of that. Thanks again!
...But what I'd need to do is basically replace the file completely, right? Never done anything like that in recovery. Everywhere else it'll say something like "This file already exists, would you like to overwrite it?" Doubt TWRP will give that heads up...have you ever made modifications in this manner?
KLit75 said:
Didn't even think of that. Thanks again!
...But what I'd need to do is basically replace the file completely, right? Never done anything like that in recovery. Everywhere else it'll say something like "This file already exists, would you like to overwrite it?" Doubt TWRP will give that heads up...have you ever made modifications in this manner?
Click to expand...
Click to collapse
Yes. Its the same as when you do it with adb. It just overwrites the file. You can always rename the original with a .orig extension first so you have original file backed up.
MiniBlu said:
Yes. Its the same as when you do it with adb. It just overwrites the file. You can always rename the original with a .orig extension first so you have original file backed up.
Click to expand...
Click to collapse
I tried it and it worked! This is really cool. Makes me wonder what else could modified. Thanks again!
I seem to have ran into a problem. I am rooted, and everything. but, once I modified this file and fixed permission I am now spammed with "unauthorized device"
Help?