So I just tried something stupid, and I was wondering whether there was a faster fix than the one I'm imagining. I downloaded an altered screen state script for the Glitch kernel (would allow me to set my own governor) and instead of incorporating it into the script and flashing that, I just pushed it directly into the system/etc/init.d folder and rebooted. Now I'm stuck at the Glitch boot load screen.
My question is, can I reflash just the kernel to my soft bricked phone, or will I have to go completely back to EB01+atlas pit and reflash CM7, GAPPs, kernel, etc?
Thanks!
Ritchell said:
So I just tried something stupid, and I was wondering whether there was a faster fix than the one I'm imagining. I downloaded an altered screen state script for the Glitch kernel (would allow me to set my own governor) and instead of incorporating it into the script and flashing that, I just pushed it directly into the system/etc/init.d folder and rebooted. Now I'm stuck at the Glitch boot load screen.
My question is, can I reflash just the kernel to my soft bricked phone, or will I have to go completely back to EB01+atlas pit and reflash CM7, GAPPs, kernel, etc?
Thanks!
Click to expand...
Click to collapse
*Warning - I'm not an expert*
That said, the problem is going to be getting in to the proper CWM. If you can get into blue, I would try flashing the kernel. If you can only get into red, you might be able to get away with just reflashing the CM7 ROM. I'd try that first before going all the way back.
Great idea! I was practically allergic to the three finger recovery because I'd been told to avoid it, but when I did it I got to the blue recovery, flashed the kernel, and now I'm back up and running. I don't know if there's a world of pain and glitches for what I did, but I'm happy to just have something usable again.
Now the question is whether I want to retry this script with a legitimate flashing.
has anyone successfully done this? i have a rooted fascinate running aokp milestone 4. i have read all the forums and have studied for hours. i finally got the nerve to try it....and....brick. lol i tried using heimdall. installed the drivers properly, opened the program, flashed the hacked param.lfs, program ran, phone booted into a blank screen for about 25 sec then went into recovery. tried wiping and restoring but right back to recovery i went. lol . had to odin to stock and build back up.
was just wondering if someone got this to work and could maybe give me a clue of what i may have done wrong..thanx.
Are you just wanting to replace the boot animation? In the case of AOPK, this would be the Unicorn animation. I do this all the time, directly from the phone. I use ES Explorer, although Root Explorer or an equivalent should work just as well. You'll need to go to /System/Media and delete the pre-exisiting bootanimation.zip. You can then replace this file with your preferred boot animation and be good to go. You can also move the old bootanimation.zip to your SD card before replacing it, allowing for easy recovery if you decide you want it back. You can also place your preferred boot animation in /data/local and supposedly a re-flash won't overwrite the boot animation. I haven't done this, as I prefer to see what animation is included in the ROM, then change it out if I wish. I'm sure there's other ways to accomplish this, but this procedure is quite simple. My preference at the moment is the rockets animation from makelegs' CM7 Kang, but there are lots available for download. Or, you can make your own if you are so inclined. I have a folder on my SD card that has a half-dozen boot animations in it, allowing me to choose which one I'd like to use.
If you need to download ES Explorer, there are a few options you'll need to enable to be able to manipulate the local filesystem. They are "Root Explorer" and "Mount File System" I think it goes without saying, but you'll need to grant ES Explorer with root permissions when prompted.
WARNING: If modifying your file system like this, BE CAREFUL what you delete. Delete the wrong file, and you could be starting over. I am not responsible for you bricking your phone.
I believe bdogg is referring to the boot splash screen. If you are following the directions that I think you are, I have not yet been successful at getting it to work yet either . If you figure it out let me know.
Sent from my SCH-I500
It is quite possible that I misunderstood which screen it was he was wanting to change. On my phone, all I get during the boot sequence is the black & white "Samsung" screen twice (once when the phone first powers on, and then it flashes quickly and reappears for what I assume is the Glitch kernel), and then the AOKP Unicorn boot animation. Once the Unicorn boot animation finishes, I get the unlock screen, at which point I consider the boot process finished. To my knowledge, you can't change the B&W Samsung screen. I could very much be wrong here, I've just never seen anything stating differently. The Glitch "logo" is set in the kernel, although I'm guessing if you edit the right thing in the .zip before you flash it that could be changed. It's not something I care to attempt, it's not on screen long enough for me to really care, and I have no preference to go messing around in the kernel. That leaves the Unicorn boot animation, which I know can be quite easily changed out to whatever different boot animation you prefer.
I'm currently running AOKP Build 28 with Glitch 14 B6.
EDIT: After a quick Google search, it appears I am wrong and that it is possible to edit the default "Samsung" screen. I didn't fully read up on the process, as I don't care to do it myself, but I did glean enough to know that I probably posted instructions here to something that you already knew, and that didn't help you one bit. I'll do better next time.
Yes, we are talking about the initial samsung logo. It is fun to change it to other things i admit. I only was able to do it per the instructions on the gb roms. I thought I saw new ones for ics but can't remember where I saw them.
Sent from my SCH-I500
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?