I like to tweak my ROMs before a flash. i.e. make changes to /system apps; framwork tweaks... etc.
However, whenever I try to replace a kernel zImage or modem binary(using 7z, so as not open archive), I get stuck at a bootloop.
I can replace .apks and .pngs no problem using this method.
Can zImage and .bin be replaced as well? Does redbend also need to be copied? Since .bin and zImage reside in same folder in ROM... which redbend to use if needed?
Thank you?
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Exactly what Br1cK'd said. Use the redband that's with the kernel. If pulling the kernel from a rom and a modem from a different one same deal. Also be careful which kernels you use ie: right kernel for phone and version of Android.
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
No sir it is not quite that simple. Proper settings have to be in the update script for everything to install properly. Replacing one file for another of the same name usually works and some files can be added but system apps and additional folders need to be in the update script.
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
1. I believe redbend is samsung tool for flashing volatile memory (NAND).
2. You can use 7zip to explore archives/apks without extracting them and breaking signings. Thus you can simple copy paste .apks/.pngs to appropriate directories without extracting
Most update zips are the actually apk and simple scripts in a flashable container. Roman form EDT has an excellent tool for creating flashable zips if interested... but yes you can manipulate file system of phone and archives. I use adb from recovery. Or android commander is a useful tool as well
EDIT: Explodingboy gives better explanation above
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
birgertime said:
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Very cool... thanks.
Also, you are going to think I am crazy... but that ugly blue splash screen can tell me if it is a bad flash or not. When it happens on the top of screen= good flash, on bottom = gonna need to flash again, cause behavior goes wonky. Maybe just bizarre coincidence???
Poser said:
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
Click to expand...
Click to collapse
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
I have no issues doing this with winrar.
Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
Br1cK'd said:
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
Click to expand...
Click to collapse
<Palm to forehead> Probably should logcat... duh.
Just flashed with with custom kernel/modem combo... seems to be booting fine, will report any anomalies.
Only thing I did different was copy zImage and redbend from Kernel.zip
Thanks peoples!
Hi
First post here, I'm new to Android and rooting but I know my way around computer systems in general so hoping you guys can help me, haven't seen a thread about this exact problem so far.
I've semi-bricked (bootlooped) my Samsung Galaxy Ace running Gingerbread, having rooted it last month using the upd_1 package and enjoying a bloatware-free phone, happily installing apps onto my second partition on my SD card. I've not changed my ROM, just the stock is good enough for me for now. However I was getting continually prompted by Homescreen Selector nags at powering up for some reason and I thought I could disable it by applying Freeze using LInk2SD, but since doing that I continually get the Samsung logo, the orange "explosion" (I'm with Orange) then a vibration and the whole cycle repeats. My guess is the operating system can't find the selector.apk app since I froze it.
I thought the solution would be simple - use adb shell to rename back from selector.fro to selector.apk. However I'm unable to find any such file in my system/app folder. There are a load of other apk and odex files but not that one. When I type su I get "permission denied", though I definitely rooted my phone but I don't think I have my bootloader unlocked.
I don't have CWM installed or any backups unfortunately (yes, I know...), so even if I took one now prior to a factory reset, surely the same problem would come back if I were to restore from any backup I were to take now. I can get into Recovery and Download screens ok but don't want to restore the whole ROM unless I have to, since I know it's only one APK that is at fault.
So, please can anyone tell me how to locate the selector.fro file to turn it back to selector.apk? Or can't I do that without unlocking the bootloader first, or is there another solution?
Many thanks in advance,
Graham
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
QNBT said:
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
Click to expand...
Click to collapse
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
gkey2112 said:
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
Click to expand...
Click to collapse
You can extract it from the ROM's zip file, just locate it as you would on your phone.
But I don't have a ROM zip file. I'm not using a custom ROM, just stock. I may go down the custom ROM route one day, but for now I just want my phone to work again in the quickest way possible.
All I need is a copy of the original stock home selector APK. Can anyone help here please?
Found the file!
Never mind, got the apk from another thread. Flashing tonight...
Hello
I've got the Note 5 SM-N9208 and I am trying not to root (tripped Knox tho as I but Phillippines system.img on it) it as the annoying Barclays App doesn't work.
I am however, trying to add my custom CA certificate into the /system/etc/security/cacerts folder. This is what I used to do in my rooted devices before and worked fine.
I have flashed TWRP and taken a full backup (thank God!) and then mounted the system as RW, copied the file, rebooted and voila, boot loop on the Samsung Note 5 screen.
The only fix is to reflash the system partition from the original TAR file which makes me wonder - is there a mechanism that prevents system from being modified if the device is unrooted? Something like Samsung's system protection or something.
Could anyone try to reproduce the issue on an unrooted phone just to see if it's just me being unlucky? Or is is simply not possible to modify system without root? If so, how come TWRP allows me to do so?
Let me know what you think guys
Looking forward to hear someone else's opinion.
mateuszd said:
Hello
Let me know what you think guys
Looking forward to hear someone else's opinion.
Click to expand...
Click to collapse
You must be rooted to make system changes.
You need to make some changes in ramdisk : remove support_scfs,verify from the fstab files for system partition
workaround found - downgrade to stock Froy 2.2.1 - IMEI back - still no idea how to use backed up efs file(s)
(c&p or s.th. else)
Still open: where to download and which version of TWRP for stock? did not find any:cyclops:
Btw.: it is my own smartphone (o-bill) and should be not a solution of all those telling stories of the mobile of a friend of a friend
It took me hours to find the wright files and I had 5x soft bricks with boot loops...
BETTER would have been a solution how to reinstall efs (write protected) if you don't have TWRP or if you copied efs file obviously wrong like me (just c&p to desktop); edit single file(s) or rename or what ever
------------------------------------------------------------------------------------------------------------------------------------------------
Hi forum,
I'm hesitated: IMEI was replaced
Backed up my efs file and installed really good roms (Omni 5.1.1., Lineage OS 11 (=4.4.4), CM12, and others)
Then I tried to exchange the small 512 MB RAM with a 32GB micro SD. Card was actually recognized as a 8GB one.
So I took it away to use it somewhere else and formatted it therefore.
Since then my IMEI has been replaced with the general one for developers - however, I need my S1 back fully.
This is the assumed root cause - maybe also it just happens sometimes if triying different roms...
Back to the facts:
I do know my IMEI
I have 5 copies of the efs file since 2013
when tried to restore from backup TWRP did do but showed failure with the efs file
Tried mobileuncle and others - failed because MTK engineer mode cannot be used (not supporten cause of other chip maybe) AND therefor
this quick win actions via dialer (#*#....) also do not work for me
root rights? Yes
SU? YES
Hex editor? YES
Must I really go back to stock (Froyo) with Odin and this stuff I forgot how to deal with it?
Or does anybody here has a proper solution how to fix this IMEI-RE-ENTRY-issue that is not too much time consuming and save? I searched for hours here and in other forums as well as in the internet...
I appreciate smart solutions and thank you all in advance
KC
Hi,
Trying to help a friend recover files (media) that were accidentally deleted on the sm-g900a. To recover those files, all signs indicate that rooting is necessary.
She tried using towelroot without mod, but it failed. I'm guessing she updated sometime in the past. So I'm guessing to root, she'll need to follow the steps (rather, I'll have to follow the steps since it might be a bit much for said friend) in the Root Guide on the General page.
(https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196)
**Q: Once the steps are complete - ie flashing the experimental firmware/OF3- will the chances of file recovery lessen (media files)? (ie will flashing the new firmware(s) override hard drive space that was occupied by said deleted files?) My first guess is minimal, since I'm guessin that part of the hard drive that'll be re-written are mainly the /system and /data files. I'm thinking about this like a traditional HD. But since this isn't my phone, I'd like to get second opinions.
**Q: She's not a tech person so any hitches w/r/t the new stock will be a hassle. Are there any glitches in the no-ship OF3? If so, I'm guessing flashing firmware from sammobile will remedy the problem. (root after this will not be necessary)
***Q: An afterthought. (It's been a while since I've flashed a phone w/ files I cared about. I'm pretty sure they aren't buuuttt) Will the files in /[user] directory affected with the flashes? (eg /sdcard, /internal (however the nomenclature works on the S5. Not the actual Sdcard)
alljokingaside said:
Hi,
Trying to help a friend recover files (media) that were accidentally deleted on the sm-g900a. To recover those files, all signs indicate that rooting is necessary.
She tried using towelroot without mod, but it failed. I'm guessing she updated sometime in the past. So I'm guessing to root, she'll need to follow the steps (rather, I'll have to follow the steps since it might be a bit much for said friend) in the Root Guide on the General page.
(https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196)
**Q: Once the steps are complete - ie flashing the experimental firmware/OF3- will the chances of file recovery lessen (media files)? (ie will flashing the new firmware(s) override hard drive space that was occupied by said deleted files?) My first guess is minimal, since I'm guessin that part of the hard drive that'll be re-written are mainly the /system and /data files. I'm thinking about this like a traditional HD. But since this isn't my phone, I'd like to get second opinions.
**Q: She's not a tech person so any hitches w/r/t the new stock will be a hassle. Are there any glitches in the no-ship OF3? If so, I'm guessing flashing firmware from sammobile will remedy the problem. (root after this will not be necessary)
***Q: An afterthought. (It's been a while since I've flashed a phone w/ files I cared about. I'm pretty sure they aren't buuuttt) Will the files in /[user] directory affected with the flashes? (eg /sdcard, /internal (however the nomenclature works on the S5. Not the actual Sdcard)
Click to expand...
Click to collapse
Okay I'll try to go in order here.
1. flashing the new firmware might lessen the chances of file recovery. I'm not exactly sure how NAND chips work, so the problem might be that it zeroes all the sectors out (unlikely) or it just uses a file index and the entries are erased. So proceed at your own risk, if the files are already lost there isn't much more to lose at this point anyway.
2. the pre-rooted OF3 is just the entire OF3 stock system but with the su files inside. Everything else is the same, so you shouldn't have any problems.
3. I'd guess no, but take that with a grain of salt since I've never really checked.
Any other questions, feel free to ask. Good luck!
AptLogic said:
Okay I'll try to go in order here.
1. flashing the new firmware might lessen the chances of file recovery. I'm not exactly sure how NAND chips work, so the problem might be that it zeroes all the sectors out (unlikely) or it just uses a file index and the entries are erased. So proceed at your own risk, if the files are already lost there isn't much more to lose at this point anyway.
2. the pre-rooted OF3 is just the entire OF3 stock system but with the su files inside. Everything else is the same, so you shouldn't have any problems.
3. I'd guess no, but take that with a grain of salt since I've never really checked.
Any other questions, feel free to ask. Good luck!
Click to expand...
Click to collapse
Thanks! Said friend got freaked out w the idea if flashing firmware. Boop