Hello.
I couldn't find any good information on how to safely test SystemUI.apk and framework-res.apk to minimize chances brick the phone?
For instance I've soft bricked my phone by misspelling a word in layouts/status_bar.xml
Is there a safe way test it before push it to the phone?
Thank you.
U can't possibly brick your phone because of wrongly modded framework_Res.apk or systemui.apk.
Ok, maybe not exactly brick, but boot loop with lost of root - yes I can. I've done it twice already, first time when copied recourses.arcs from freshly compiled resources-res.apk to original file (because apktools doesn't support .apk from LG Nitro HD, or ICS, it creates new folder and removes others making different file tree structure from original) and second time messing up systemui file, with the later boot loop the re-root that worked the first time didn't work I had to manually root the phone to brink it back.
Just backup working one, copy modded to it's directory and if not work change it with working one via adb during boot.
Ok, that's what I've been doing, but this phone is wierd, when boot loop happens it looses root access (I still can adb shell, but su would return segment fault error), so I have to re-root. Then when all fixed and done, after first boot it forgets my google account...
It's rather time consuming to go through all this on each failure, so I hoped there is a way do it more safely...
If that's the only way, so be it, if I brick my phone I'll blame it on BHuvan goyal
j/k
CWM full backup, flash new systemui and framework-res, bootloop? then CWM advanced restore /system only, should still have root. This is what usually works for me when flashing these .apks
Good idea. Unfortunately we still waiting for CWM on LG Nitro, we got root in no time, but can't get CWM to work just yet. There are quiet a few weird issues with this phone...
I'm getting weird results. Right now I'm using modified SystemUI.apk and framework-res.apk on stock rom. When I flash this same stock rom and replace these two files thrle phone gets into boot loop. How can I trace what causing it?
Thanks.
[email protected] said:
I'm getting weird results. Right now I'm using modified SystemUI.apk and framework-res.apk on stock rom. When I flash this same stock rom and replace these two files thrle phone gets into boot loop. How can I trace what causing it?
Thanks.
Click to expand...
Click to collapse
Rom deodexed?
Sent from my SCH-I400 using xda premium
No, it's a stock rom, not deodexed.
It's just the same method I used to push these files that do work now, don't work anymore when I try it on a "fresh" same rom...I don't recall doing anything else or different...
[email protected] said:
No, it's a stock rom, not deodexed.
It's just the same method I used to push these files that do work now, don't work anymore when I try it on a "fresh" same rom...I don't recall doing anything else or different...
Click to expand...
Click to collapse
To my knowledge rom needs to be deodexed to mod
Sent from my SCH-I400 using xda premium
Yes, but somehow I managed make it work on this rom several times, now for some reason it doesn't work anymore..can't wrap my head around it, very strange.
just place your current untouched systemui and framework apks in a themers update.zip if all goes wrong just boot into recovery and flash the zip to return to working APKS
Related
Are the framework-res and SystemUI apk's the only files that are involved in the boot process?
I only ask because I am currently stuck in a boot animation loop. I am able to communicate with my phone via adb during the animation loop and while in the bootloader recovery. Wiping the data and and factory resetting doesn't solve the problem.
I am thinking about pulling those two files from my wife's phone which is the same phone (Samsung Proclaim) and pushing them to mine.
Does this seem like a good idea?
Flash up the orginal firmware via odin
If the phone isn't rooted, then just take it to the verizon store amnd they will take care of it
Sent from my HTC One using Tapatalk 2
Shrihari007 said:
Flash up the orginal firmware via odin
Click to expand...
Click to collapse
I have the two root kernels that are out there and the original that they put out with one of them to fix a network connection issue. I have reflashed all of them with odin but nothing changes.
Do you know if it would help to just replace the entire system folder with a non-rooted phone's system folder? Or is that even possible? I've actually tried this already but now it says my device is out of room. I thought it would overwrite the other files but perhaps it isn't.
My next thought is to try to delete all of them and push the working phones system in. Not sure if that is a good Idea either.
At this point I'm sure I am only making things worse.
Well now I've really gone and messed things up. Pretty sure it's out of my realm of possibilities now.
After pushing the other bin folder into mine i have lost all permissions due to system/bin/sh.
Now I can't do anything with adb except connect to the phone. So technically its all still there.
I just need to write over the bin with my original bin and then I might hopefully be back at the previous problem.
Also, it's looping at the Samsung logo now so I've definitely gone backwards.
This is what I get for messing with things that I don't fully understand.
Hello everybody. I recently flashed my phone with the latest Cyanogenmod rom for the HTC one, using the wHil recovery flasher. However after playing with the rom for a bit I decided I want to swap back to stock everything that came with my phone. What is the process to go about doing this?
Thanks!
Did you make a nandroid before flashing the Rom, if yes then just flash it then flash stock tmobile recovery img then relock the bootloader..just do a quick search and you find out how to do it... But it will still say tampered on bootloader... But ota will work cause that only requires stock recovery and stock Rom
Sent from my HTC One using Tapatalk 2
I did not, however I downloaded someone else's stock nandriod dump.
So all I need to do is flash the stock rom, flash the stock recovery, relock the bootloader and I should be able to get OTA updates and all that good stuff again?
GeePM said:
I did not, however I downloaded someone else's stock nandriod dump.
So all I need to do is flash the stock rom, flash the stock recovery, relock the bootloader and I should be able to get OTA updates and all that good stuff again?
Click to expand...
Click to collapse
Yes, that's what I did, and OTA updates work perfert
That's great to hear. So I shouldn't experience any issues when I return to the stock rom like loosing any kind of features and such?
I've been having issues trying to adb push this backup to my phone since 4.2 andriod has things locked down in regards to backups. Been getting the device not found issue, so I'm going to try and push it using a different PC soon hopefully. With where I work I can't live without WiFi calling/texting that Cyanogenmod lacks
So I have the stock backup through clockwork mod and I have it in the proper /clockworkmod/backup folder. Problem is, clockwork mod touch isn't detecting that I have any backups to restore. So I decided to make a fresh backup just to see where it was placed so I could put this other backup I downloaded in there.
Problem. I can't find it anywhere. I don't know where to put it. I don't know where clockworkmod touch wants it to go. Any ideas?
EDIT: Apparently there are two of these folders? *looking more*
EDIT 2: Clearly, If I try to restore from the saved backups, it shows the backup I made, but no amount of searching is finding it through any of my file managers. I'm finding the backup I downloaded, but not the one I made. wtf? Are there hidden folders or something? I have root access.
EDIT 3: There are apparently two clockwork mod folders on my phone. Clockwork mod is saying that it sees the test backup I made on 6-10, but when I check in my file manager for a backup, it shows me the folder with a 4-26 backup which is what I want to restore. The FILE MANAGER sees a folder with 4-26, whereas clockworkmod sees a folder with a backup of 6-10. Both folders are apparently clockworkmod/backup. Does anyone have any idea what's going on here?
So I just flashed the stock rom, reinstalled the stock rescue image, and relocked my bootloader.
How long does it take for me to be able to get the 4.2 update?
change yearThe
GeePM said:
So I just flashed the stock rom, reinstalled the stock rescue image, and relocked my bootloader.
How long does it take for me to be able to get the 4.2 update?
Click to expand...
Click to collapse
Nevermind! Just went to the upgrade section and got it
GeePM said:
Nevermind! Just went to the upgrade section and got it
Click to expand...
Click to collapse
4.2?????
blackangst said:
4.2?????
Click to expand...
Click to collapse
Nevermind, I still don't have it. Was 4.2 pushed out yet?
GeePM said:
Nevermind, I still don't have it. Was 4.2 pushed out yet?
Click to expand...
Click to collapse
No. Not on TMobile.
Hi all! I have a slight issue.. So my sisters phone is rooted and on offical kit-kat NAB.
I tried to install @kevinrocksman's hypnotoad boot animation, flashable through twrp. http://forum.xda-developers.com/showthread.php?t=2467543
It didnt work and after the Note 3 screen it stays black till it boots up. I figure it is because the phones only on stock rooted, and that uses a bunch of weird .qmg files. I cant restore the nandroid for several reasons so thats not an option. So I tried the following troubleshooting steps to either get the hypnotoad to work or restore the default sprint sound and animation.
1. I manually pushed the hypnotoad bootanimation.zip into system/media and changed permissions. no go
2. Then in hypnotoad aroma installer I installed it again. Still no go
3. In aroma I tried restore default feature, the sounds back but no yellow sprint animation
4.I deleted the bootanimation.zip in system/media. no go
.5.On the thread @shabbypenguin commented. Posting an enable bootanimation.zip to have the phone look for .zips instead of .qmg. I flashed it. (http://www.mediafire.com/download/xlbsop29q44vlco/Enable-Bootanimation.zip)
6. Then I tried twrping the hypnotoad aroma boot ani again, hoping shabbypenguins enable bootani will make it work. Nada
7. I tried restoring default again through aroma, still boots with sound but no yellow sprint animation.
So if anyone has an idea to either get the hypntoad to work or get back the defualt boot animation, that would be GREATLY appreciated.
I know it was probably dumb to try on stock rooted sorry, but my sister is stuck with no bootanimation, and she does not want to flash a new rom
So thanks
what thread was this??
shabbypenguin said:
what thread was this??
Click to expand...
Click to collapse
All was found on @kevinrocksman s thread. Your comment was at the bottom of the page
Thread: http://forum.xda-developers.com/showthread.php?t=2467543
I hope you have a fix mr. shabbypenguin sir! :fingers-crossed:
Do you know of any fixes @kevinrocksman??
I would think there would be a flashable. Zip laying around but i couldn't find any
if you read to the second page, you would have seen that zip doesnt work
shabbypenguin said:
if you read to the second page, you would have seen that zip doesnt work
Click to expand...
Click to collapse
Ive read the whole thread, and the comments. I believed it would work because I have been on several stock Samsung based roms, and all of either the flashable.zips or manually pushing to /system/media have worked fine. Im even currently on AOSP and pushing the monster attack bootanimation.zip to system/media worked perfectly. So I believe my error lies in possibly two things. Either..
A.these bootanimaton.zips are not NAB compatible; which would seem odd because as far as I know bootanimation.zips are fairly universal. It worked on AOSP just fine
B. Or since this is stock STOCK rooted, the system files have not been configured by a dev to allow changing bootanimation.zips.
If it is scenario B, which i think is more likely, then a solution would be to flash a custom built Nab rom, right? I would think if I flashed Freezas stockISH rom it would be too stock and the boot ani system files would be the same situation. Which is why im thinking @sac23 s kit-kats v1 nab rom would allow me to change bootanimation.zip. Do you think this would be accurate?
I did some further digging and I believe I may have found a way to be able to push bootanimation.zips and have them work even on stock stock roms.
What do you think of this? http://forum.xda-developers.com/showthread.php?p=50218786
I gather if I push the bootanimation.bin in OP and replace it with the current one in /system/bin it will enable me to change bootanimations just like normal. You probably would have a better idea then me, do you think this is an accurate conclusion?
Thanks :good:
kevinrocksman said:
samsung has been using qmg files since before the SGS1, this http://www.mediafire.com/download/xl...tanimation.zip should enable it. it swaps out the bootanimation binary for one looking for .zip's. it may not work if they are still using samsungani
Click to expand...
Click to collapse
this is what it does in adb when u execute bootanimation
CANNOT LINK EXECUTABLE: cannot locate symbol "_ZN7android21SurfaceComposerClient
14getDisplayInfoEiPNS_11DisplayInfoE" referenced by "bootanimation"...
Click to expand...
Click to collapse
as for all the other zips idk, but mine doesnt. as for figureing it out etc, youll have to ask someone who is up to date on samsung software and/or owns a note 3.
shabbypenguin said:
as for all the other zips idk, but mine doesnt. as for figureing it out etc idk, youll have to ask someone who is up to date on samsung software and/or owns a note 3.
Click to expand...
Click to collapse
okay thanks anyway, I happen to have an extra replacement note 3 for a little bit so ill run some tests!
thanks
You've probably heard this song and dance before, but my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
siren_shadows said:
my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Click to expand...
Click to collapse
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
siren_shadows said:
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
Click to expand...
Click to collapse
What happens if you just type in a URL, without going through Google search results?
redpoint73 said:
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
What happens if you just type in a URL, without going through Google search results?
Click to expand...
Click to collapse
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
siren_shadows said:
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
Click to expand...
Click to collapse
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
redpoint73 said:
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
Click to expand...
Click to collapse
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
siren_shadows said:
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
Click to expand...
Click to collapse
Did you modify build.prop?
redpoint73 said:
Did you modify build.prop?
Click to expand...
Click to collapse
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
siren_shadows said:
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
Click to expand...
Click to collapse
WNC just posted the 4.28.502 version of his ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I assume the build.prop is stock; and kernel is insecure.
unfortunately, I am s-on.
siren_shadows said:
unfortunately, I am s-on.
Click to expand...
Click to collapse
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
redpoint73 said:
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
Click to expand...
Click to collapse
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
siren_shadows said:
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
Click to expand...
Click to collapse
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
redpoint73 said:
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
Click to expand...
Click to collapse
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
siren_shadows said:
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
Click to expand...
Click to collapse
Can you still get into bootloader?
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
redpoint73 said:
Do you mean you can't get into bootloader?
If so, that doesn't actually make any sense, bootloader is write protected with s-on. So there is no way this can be corrupted or over-written.
This seems scary. But just take a breath, as I don't think this is as bad as it looks.
What happened after you copied the file?
Does the screen come on at all?
Click to expand...
Click to collapse
i got a black screen after a reboot. but holding power and volume up did the hard reset and i had to really quickly press volume down. like a split second window
siren_shadows said:
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
Click to expand...
Click to collapse
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
redpoint73 said:
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
Click to expand...
Click to collapse
I was a genius and decided I would save space by moving onto my computer. However, I am restoring now. That'll fix my black screen issue, right?
siren_shadows said:
I am restoring now. That'll fix my black screen issue, right?
Click to expand...
Click to collapse
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
redpoint73 said:
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
Click to expand...
Click to collapse
who knows. My issue isn't fixed regarding mobile data, either. At least I have a usable phone tho!
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?