Related
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
remember i have not .zip file in media folder
Mr Hassan said:
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
Click to expand...
Click to collapse
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
-spektor- said:
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
Click to expand...
Click to collapse
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Mr Hassan said:
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Click to expand...
Click to collapse
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
-spektor- said:
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
Click to expand...
Click to collapse
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Mr Hassan said:
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Click to expand...
Click to collapse
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
-spektor- said:
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
Click to expand...
Click to collapse
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Mr Hassan said:
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Click to expand...
Click to collapse
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could help it deals with modifying samsung rom and flashing it. If you want to read more on it here's the link: http://android.stackexchange.com/questions/85703/modifying-samsung-rom-and-flashing-it-on-a-device if you wanted to remove apps or add custom apps to your phone you would modify system file.
But what I thought was important was this;
(I did not write this thread)
< "You should be able to use an archive program on PC and recompress to .tar, .gz, and others. Dont forget to re-sign the archive. Keep a copy of your untouched ROM until you have the modified ROM tested and running.
The ROMs are signed with a signature. When repacking if they don't get signed they will fail in flashing. This link will help explain it.
So basically after downloading the firmware you have to rename it so you can extract the files, change them as you need, recompress them again and re-sign them, so you can flash them using Odin." >
This thread was dealing with modifying CM rom;
< "There are multiple solutions available:
Re-Zip the Image
Advantage: You do it once, and can use the resulting image for multiple devices. That's what I did with CM7.2 for my Milestone 2. Easy enough to do:
create a temporary (empty) folder
unzip the zip file to it
remove unwanted *.apk files from /system/apps (be careful of what you remove, of course)
zip up the directory contents again
Using a graphical ZIP manager (like WinZip or the like), steps would be even easier:
open the zip file with the archive manager
remove the unwanted .apk files
if the ZIP manager requires it, save the manipulated zip
Manually cleanup after flashing, using the shell
This is what ce4 recommended in the comments. It requires you using a terminal emulator on your device:
Flash the image as-is
remove superfluous stuff from the system partition by hand (like rm /system/big/junk/example.mp4)
Manually cleanup after flashing, using other tools
Almost the same as the previous method, but a bit more user-friendly. Disadvantage: this won't do for superflous ringtones and the like:
Flash the image as-is
Use a tool like Titanium Backup or Root Uninstaller to remove unwanted system apps" >
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
-spektor- said:
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
Click to expand...
Click to collapse
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Mr Hassan said:
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Click to expand...
Click to collapse
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
-spektor- said:
.
Click to expand...
Click to collapse
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Mr Hassan said:
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Click to expand...
Click to collapse
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
Ok apps done
Bulid done
Now final thing need . repack in ext4 format
I'll check these things tomorrow
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
brother did you found anything for repack ext4 img?
Mr Hassan said:
brother did you found anything for repack ext4 img?
Click to expand...
Click to collapse
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
-spektor- said:
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
yes but its for linux , and for window 99% unsuccessfully rates , have you try in window ? this ?
now i,m in next step if you have the time so kindly share your experience
https://forum.xda-developers.com/android/help/repack-img-giving-error-odin-invalid-t3577719
Hmmmmm ? I think you want to change the boot animation (white Verizon logo red background? ) if so your gonna need to either need to flash a pre-made zip with Flashfire (can't seem to get it to apply from twrp) or your gonna need to manually copy into the appropriate directory (mount system directory r/w copy then change permissions of the file you copied to 644 and reboot) presumably with a root explorer though doable from terminal
---------- Post added at 07:47 PM ---------- Previous post was at 07:29 PM ----------
-spektor- said:
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
Click to expand...
Click to collapse
Try flashing with flasfire enabling the option mount system r/w and use common paths (probably not necessary but won't hurt) I have had difficulty getting anything other than ROM and gapps to apply from twrp but flashfire seems to work . I'm thinking its due to the fact that flashfire flashes after boot loader and then resets prior to os load.
"NOST" - short for "No Service Tool" (or "Nokia Service Tool" but that sounds too official and boring ) is a small hobby project I've been working on in the last couple of days.
It aims to make the service tool for Nokia 8 (and HMD Phones in general) more useable, user-friendly, and straigtforward to use, and after having to test it myself, and also
making a small beta test in the Telegram group for Nokia 8, I feel like posting it here so others can try it out too if they want.
First, to be clear: NOST is not completely my work. It is based on OST LA 6.0.4, which was made by HMD/Foxconn. Unlike the previous OST Patches, NOST does not replace
the executable with a hacked one, but instead wraps it and patches the methods that need patching at runtime. The result is that the changes are completely opensource
and readable by others, while the underlying OST files are not modified at all. I tried to base it on a different (i.e. newer) version of OST, but those are pretty much unpatchable,
at least not with a serious amount of reverse engineering, which brings not only time issues but legal ones as well.
NOST changes a couple of things, compared to the unmodified OST LA:
It removes the need for authentification against HMD/FIH servers (really, shoutout to the one who made the original hack, even though I could not use their code)
Moved the logs folder to the same folder as the application, as opposed to somewhere on the system to make debugging easier
The options for flashing firmware images appear reliable now. (At least for me they only appeared sometimes if not never on the original OST).
Removed one of the options that if it appeared crashed the flashing process ("Check System AP Status")
One user of the Telegram group had issues where OST would crash because it detects an invalid locale setting in Windows. NOST just catches that issue and defaults to english
Removed the "Edit Phone Information" button. It never worked and it's only purpose was to make the "Next" button appear, which works like it should now as well.
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Perhaps the most important change: NOST allows to flash modified firmware images without the need to extract and modify them by hand.
With the original OST, people who wanted to reflash their phone had to download a firmware bundle, extract and edit it to be able to use it with OST LA 6.0.4, since the newer versions
had unpatchable issues that prevent using them. Repacking the images in a format OST expects wasn't possible either since that enabled some sort of signature algorithm on the modified
images and caused the flashing to fail. NOST solves this problem by allowing the use of a different packaging format. Those binaries still need to be extracted but it is done transparently in
the background without the user having to download any other tools. The formats that can be used in images are .zip and .qlz
.zip Firmwares:
.zip firmware files are simply archives of the (edited) files that would normally be extracted from an .nb0 file. This means, if you extract a .nb0 with the extractor found on XDA, the contents
of the *_unpacked folder it creates should be the contents of your .zip.
.qlz Firmwares:
.qlz files are based on QuickLZ compression, which gives them a small size but also a low decompression time.
The tool to generate them is called exdupe. Generating these images is pretty straigtforward. Assuming you are on windows, download the exdupe
tool from the link above (or take it from the NOST Tools/ folder) and copy it into the folder that contains the unpacked .nb0.
Code:
- exdupe.exe
- <nb0 name>_unpacked/
- <nb0 name>.mlf
- ....
Open a commandline in that folder, and run the following command:
Code:
exdupe.exe <name of the folder to compress> <name of the firmware file>.qlz
You should already see how fast it compresses the firmware folder now. As a reference: Compressing the latest Nokia 8 firmware (about 4GB) takes maybe 30 seconds and yields a 2GB file.
Repacked Firmware Bundles:
I created .qlz images of the May and November firmwares, as well as one of the various Pie Maintainance Releases.
You can find them here: https://tmsp.io/fs/xda/nb1/firmware
I already successfully reverted from December Security Patch to November using NOST, and then updated back using OTA Sideloading without problems.
As always when working with flashing tools, proceed with caution!
How to unlock to critical:
KonikoO said:
For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Download:
The actual tool: https://github.com/StollD/NOST/releases
Drivers: https://github.com/StollD/nokia-driver-installer/tree/master/out
Source Code: https://github.com/StollD/NOST
License:
OST LA 6.0.4 is copyrighted by the respective authors. It is not modified permanently.
The custom NOST code is licensed under the GNU General Public License.
Icon by Freepik © Flaticon
I tried this is working,nice tool.
Thanks dev.
Thank you THMSP! very cool?
Sent from my TA-1004 using XDA Labs
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Lee Castro said:
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Click to expand...
Click to collapse
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
THMSP said:
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
Click to expand...
Click to collapse
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Lee Castro said:
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Click to expand...
Click to collapse
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
THMSP said:
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
Click to expand...
Click to collapse
Thanks again,This is really a big help.
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
hey there! wonderful tool to have. Thank u so much
Not working in my laptop say a software need a to update
Blackhacker07 said:
Not working in my laptop say a software need a to update
Click to expand...
Click to collapse
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
THMSP said:
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
Click to expand...
Click to collapse
Could you perhaps figure out how to get rid of the unlocked bootloader message?
ironman38102 said:
Could you perhaps figure out how to get rid of the unlocked bootloader message?
Click to expand...
Click to collapse
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
THMSP said:
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
Click to expand...
Click to collapse
Actually its in splash.img that can be dumped. Its the hex editing possibly that might be a problem for someone not familiar with it
How to flash it's says this...
Blackhacker07 said:
How to flash it's says this...
Click to expand...
Click to collapse
What do you mean?
KonikoO said:
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Thank you so much for this advice. I wouldn't have ever figured out how to unlock critical on my own and that was the thing that was preventing me from flashing. I tried searching the other OST LA flashing threads as well but this info seemed to have been missing, or then i completely missed it. Thank you so much anyways. If anybody else is trying to figure out why their OST LA or NOST is giving them the se_err_adb_cmd_get_fail_result error, this should help. I just used the unlock.key in place of the *unlock.bin* in your command and it worked.
Can you please upload Oreo December update stock and patched boot image. TIA
Yesterday I noticed that my Pie Image was still not quite useable, since it contained a corrupted system partition.
This seems to have happened because of my Magisk Setup and me only replacing the boot partition image and not uninstalling Magisk completely.
I rebuilt the image, to be fully stock, and also included the latest B07 update that @hikari_calyx uploaded yesterday. You can get it from the drive link in the OP.
BeyondRom V5.8
Based on Android 9.0 - G975FXXU3ASK1
Devices Supported: G973F(D), G975F(D)
ROM Features
<*>Aroma choices: full/dirty wipe, debloating, Bixby key remapping, Emoji</*>
<*>Supports G973F(D) and G975F(D)</*>
<*>Base SM-G975F G975FXXU3ASK1 odex/deodex November 2019 patch level</*>
<*>CSC features (camera sound menu, call recording, LTE only mod, camera during call, etc)</*>
<*>Knox removed, 1170 fonts by Winb33, AppLock</*>
<*>Included the security bypass from Ian’s multidisabler</*>
<*>build.prop tweaks: multiuser, Bluetooth Aptx driver, call ring delay, SHealth fix, WiFi and BT passwords remember</*>
<*>Dual SIM + SD Card, allow ss in secure apps, disable sig verification, SecureFolder</*>
<*>Reboot directly into rooted system from power menu, disable high volume warning</*>
<*>Possibility to choose in aroma to remove the boot warning</*>
Added/fixed in v5.8
<*>November ASK1 sw level</*>
Credits
- John Wu for Magisk
- Ianmcd for his multidisabler
- Ianmcd & Geiti for the TWRP
- Winb33for the fonts app
- SuperR for his kitchen
- fOmey for his smali patcher
- Khongloi for Secure Folder fix
- Corsicanu for his help and advices
- Sannoc for his help and support
- All people from Telegram group for testing (especially Nathan, Carlos, Raphael, Jay, Alan
Download Link
Google Drive
Digi Link
Flashable patched TWRP S10 (G973F)
Flashable patched TWRP S10+ (G975F)
Installation procedure for upgrade from BeyondROM v5.4 / v5.5
- Take a full TWRP backup
- Dirty flash or clean flash is ok
Installation procedure for upgrade from BeyondROM less than v5.4
- If you are on stock ROM, follow the attached guide
This ROM version needs minimum ASIG BL and ASIG TWRP/recovery or it won't boot !!!
1. Boot in TWRP and take a full backup before flashing BeyondRom 5.8 ROM zip
2. Copy the ROM zip to your phone (Ext SD preferably)
3. Download Ian’s Multidisabler v1.6 or higher and copy it to your phone
4. Download Ian’s TWRP 3.3.1-11, copy it to your phone and patch it with Magisk Manager or use the patched TWRP from gdrive folder
5. Download the stock FW for your device (S10 or S10+) – Frija is a good tool to use
6. Extract the AP from stock FW, copy it to a temp folder on your internal SD
7. Patch in Magisk Manager the AP
8. Copy the patched AP to your PC and replace the recovery.img inside the AP with the patched TWRP from point 4. Rename the patched TWRP to recovery.img before replacing it into the patched AP
9. Open Odin 3.13.1 or 3.13.3 and fill all slots with: patched AP, BL, CP and HOME_CSC. Uncheck the automatic restart and start flashing.
10. Once flashing completed, long press VOL DOWN + POWER until screen becomes black. IMEDIATELY the screen gets black, press VOL UP + BIXBY + POWER BUTTON to enter to TWRP recovery.
11. Once in TWRP, flash the Multidisabler v1.6 and right after flash BeyondROM v5.8 No need to reboot in between.
12. After flashing the ROM zip, save the aroma log, go back to TWRP root menu and select Reboot --> Recovery
13. Wait for the boot up (5-7 minutes) and setup your ROM to your liking
14. Enjoy the release of BeyondROM
Advises
1. Clean install if you have issues with dirty flash; don't start flashing BR5 without a twrp backup of your existing rom
2. If you have flashing issues: check rom zip MD5 hash
3. If you consider that the moded services are the culprit for your SnapChat ban, use stock services.jar provided in the download folder
4. If you like my work, consider buying me a coffee (PayPal link)
Helpful links
Telegram chat
Happy flashing good people!
Always good to see a new rom for the S10(+)
:good::good:
i dont have LTE, only 4G.
what CSC should I chose when flashing?
mcn1970 said:
i dont have LTE, only 4G.
what CSC should I chose when flashing?
Click to expand...
Click to collapse
They're the same thing. It's just the way your phone is reporting the connection.
Regards,
Nathan
sevsman said:
They're the same thing. It's just the way your phone is reporting the connection.
Regards,
Nathan
Click to expand...
Click to collapse
features of the ROM presents LTE instead of 4G mod.
this is what I mean
mcn1970 said:
features of the ROM presents LTE instead of 4G mod.
this is what I mean
Click to expand...
Click to collapse
You have to choose it in the aroma. You may well have missed the option and a dirty flash will fix it.
Regards,
Nathan
sevsman said:
You have to choose it in the aroma. You may well have missed the option and a dirty flash will fix it.
Regards,
Nathan
Click to expand...
Click to collapse
i don't have this in Aroma
another one
??? Good luck with flashing it guys!
I can confirm it is working well on S10 G973F.
Thanks a lot @Andrei1973 @starbucks2010
Thank you for the update! :good::good::good:
Wow July update. !!!
:fingers-crossed::fingers-crossed::fingers-crossed:
Installed. So far working fine. Thanks OP.
how can I install TWRP for Galaxy S10+
and kernel?
tried this at least half a dozen times and get stuck at the same spot. I can root and get Magisk and be fine. Then I patch the appropriate TWRP file for my kernel (S10+ twrp-beyond2lte-3.3.1-3.1_ianmacd.img) and then I open the .tar file. I exchange out the recovery.img with the newly patched one. Then I repackage as a tar using B1 free archiver (this may be the issue, but it seems fine). It creates a new AP file. I insert that into Odin (the same version that worked previously) along with the corresponding BL, CP, and CSC files (I have tried both CSC and Home CSC). I boot into download, hook up my phone, hit flash and VOILA...NOTHING!!!! It says, "file analysis" and crashes every time. After a while I got sick of trying so I made an attempt to flash the recovery.img file straight through TWRP app by itself. All that did was cause an infinite boot loop. Can anyone please help me? Here are my rom file names.
AP_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_low_ship_meta_OS9.tar.md5
BL_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_low_ship.tar.md5
CP_G975FXXU1ASE5_CP12748354_CL16003457_QB23792291_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_G975FOXM1ASE5_CL16003457_QB23792291_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_G975FOXM1ASE5_CL16003457_QB23792291_REV01_user_low_ship.tar
MM Pre-patched AP + TWRP name is "magisk_patched + TWRP.tar."
The TWRP file I downloaded was: twrp-beyond2lte-3.3.1-3.1_ianmacd.img which I of course renamed to recovery.img.
THEN AFTER I GET THIS WORKING, DO I JUST FLASH STRAIGHT THE ZIP FOR THE CUSTOM ROM INSIDE TWRP AND THAT'S IT?
TIA
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
kevinjmoore said:
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
Click to expand...
Click to collapse
I think your archive editor isn't up to scratch, install 7zip from here Download
Try using this recovery, its a working pre magisk patched image G973F_magisk_patched3.3.1-3.1.img
Rename it to recovery.img and replace the one inside your magisk patched version of AP_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_ low_ship_meta_OS9.tar.md5 using 7zip. Then flash with odin.
Hope this helps
kevinjmoore said:
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
Click to expand...
Click to collapse
Just delete md5 extension, you don't need that. Odin will flash *.tar file without any problems
Thank you for the reply. There are three things that I'm not sure about. All the versions of 7zip that I have used can't create or edit tar files. The second is my device is 975F not 973. Finally, what are the exact steps to replace the recovery file in 7ZIP? That seems to be where it's having the hangup.
@oggi21 I only added that extension as a last resort. It won't flash the regular tar file once I add the patched AP with TWRP recovery using the B1 archiver. Any help would be appreciated.
Any chance of US CSC's like TMB could be implemented?
kevinjmoore said:
Thank you for the reply. There are three things that I'm not sure about. All the versions of 7zip that I have used can't create or edit tar files. The second is my device is 975F not 973. Finally, what are the exact steps to replace the recovery file in 7ZIP? That seems to be where it's having the hangup.
@oggi21 I only added that extension as a last resort. It won't flash the regular tar file once I add the patched AP with TWRP recovery using the B1 archiver. Any help would be appreciated.
Click to expand...
Click to collapse
The best way is to take any tar file (AP or whatever) and open it in 7zip. Then put yours files in it and delete all others that was inside
Just to add my experience here, I flashed MARS_SOM magisk rom module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using UnSIN, use to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking the img, copying a folder etc see here:
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
This worked for me and so hope it helps someone out too!
cd993 said:
Just to add my experience here, I flashed MARS_SOM magisk rom module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using UnSIN, use to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking the img, copying a folder etc see here:
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
This worked for me and so hope it helps someone out too!
Click to expand...
Click to collapse
With Unsin (on windows at least) you can just drag your file over the cmd without having to mess with command lines
AJHutchinson said:
With Unsin (on windows at least) you can just drag your file over the cmd without having to mess with command lines
Click to expand...
Click to collapse
Yeah that's a handy little feature, makes converting it super simple!
cd993 said:
Just to add my experience here, I flashed MARS_SOM magisk rom module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using UnSIN, use to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking the img, copying a folder etc see here:
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
This worked for me and so hope it helps someone out too!
Click to expand...
Click to collapse
Hi there; I was in the same situation, flashing a corrupted magisk boot image from standard firmware for XQ-AT51, provided by same author for simple rooting Xperia 1 II; my phone was without xposed, it was in clean factory state. the magisk boot image was taken from another thread "[ROOT] Magisk patched Boot Images & Instructions" designated for rooting of Xperia 1 II;
unfortunately is the same author who build your ROM, he delivered also corrupted magisk image.
It was not enter in bootloop if you flash only one image on phone, not both; his instructions are wrong. the correct flashing instruction is below, at end of my comment.
I solved in smilar way like you: using flashtool to obtain XQ-AT51 ftf file: XQ-AT51_58.0.A.3.39_1321-7706_R13A.ftf;
Attention: the name of file depends of region firmware you want to flash and type of phone (single or dual sim); the given names are with title of example.
Then from download folder of flashtool form your disk C:\Users\username\.flashTool\firmwares\Downloads (username is your username on pc); check for file: boot_X-FLASH-ALL-2389.sin ( applicable for XQ-AT51) and convert the file to .img using unsin; check on xda for unsin, extract unsin archive in exe file and then drag & drop over unsin.exe the file boot_X-FLASH-ALL-2389.sin; will be generated boot_X-FLASH-ALL-2389.img file.
This name file can be other, is just an example, if you have another phone with firmware for other region, pay attention to this!
This can be flashed then back to phone using adb comands; fastboot flash boot boot_X-FLASH-ALL-2389.img;
The same image can be transfered to phone and used later to generate correct magisk image and root the phone.
Best to you all!
daphix said:
Hi there; I was in the same situation, flashing a corrupted magisk boot image from standard firmware for XQ-AT51, provided by same author for simple rooting Xperia 1 II; my phone was without xposed, it was in clean factory state. the magisk boot image was taken from another thread "[ROOT] Magisk patched Boot Images & Instructions" designated for rooting of Xperia 1 II;
unfortunately is the same author who build your ROM, he delivered also corrupted magisk image.
It was not enter in bootloop if you flash only one image on phone, not both; his instructions are wrong. the correct flashing instruction is below, at end of my comment.
I solved in smilar way like you: using flashtool to obtain XQ-AT51 ftf file: XQ-AT51_58.0.A.3.39_1321-7706_R13A.ftf;
Attention: the name of file depends of region firmware you want to flash and type of phone (single or dual sim); the given names are with title of example.
Then from download folder of flashtool form your disk C:\Users\username\.flashTool\firmwares\Downloads (username is your username on pc); check for file: boot_X-FLASH-ALL-2389.sin ( applicable for XQ-AT51) and convert the file to .img using unsin; check on xda for unsin, extract unsin archive in exe file and then drag & drop over unsin.exe the file boot_X-FLASH-ALL-2389.sin; will be generated boot_X-FLASH-ALL-2389.img file.
This name file can be other, is just an example, if you have another phone with firmware for other region, pay attention to this!
This can be flashed then back to phone using adb comands; fastboot flash boot boot_X-FLASH-ALL-2389.img;
The same image can be transfered to phone and used later to generate correct magisk image and root the phone.
Best to you all!
Click to expand...
Click to collapse
Thanks for that, glad you managed to fix your situation too!
cd993 said:
Thanks for that, glad you managed to fix your situation too!
Click to expand...
Click to collapse
What to posted you is very very usefull; it helps you to fix after flashing wrong magisk module.
:good:
DISCLAIMER* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.PRE REQUIREMENTS:- SDK Platform-tools (Get it here)
-boot.img from Stock Rom
-Patience
LET'S BEGIN!
Extract the SDK Platform tools folder to an easily accessible directory
UNLOCKING THE BOOTLOADERNOTE: THIS WILL ERASE ALL DATA FROM YOUR DEVICE SO MAKE SURE TO TAKE A BACKUP IF NECESSARY
-Extract the SDK Platform tools folder to an easily accessible directory
- Go to Settings > About Tablet > Tap build number 7 times. Go back to main page of Settings > System > Developer
options and enable OEM unlocking and USB Debugging
- Reboot the system to bootloader (Press Vol - and Power key or type "adb reboot bootloader" by opening a command prompt window in Platform tools directory)
- To unlock bootloader type the below code
fastboot flashing unlock
- The device will do a factory reset and restart itself
-After Setting up your device install the magisk app from here
ROOTING [MAGISK]METHOD-1 (FASTBOOT)- Transfer your boot.img to Internal Stroage
- After installing the magisk app Go to Install > Select and Patch a File
- Select the boot.img you transferred to Internal Storage. Magisk will patch your boot.img and display the output folder after the process.
- Transfer the Patched boot.img to SDK Platform tools folder and rename it to boot.img
- Reboot to Bootloader and type the below command:
fastboot flash boot boot.img
-Reboot the device by typing:
fastboot reboot
-Check Magisk manager and the device must be rooted now
METHOD-2 (TWRP)- Install TWRP by following this guide
- Download the magisk apk. Transfer it to SD-Card and flash it from twrp
- Reboot your device
CREDITS@topjohnwu Magisk
@adazem009 For TWRP recovery
Press Thanks button if this guide was useful to you!
@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.
PATCHED BOOT IMAGE FROM YT-X705FThis is a magisk patched boot.img from the latest firmware for YT-X705F. Please don't use it for other models (YT-X705L, YT-X705X)
TNSMANI said:
@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.
Click to expand...
Click to collapse
Noted sir. It won't happen again
what version of ROM you use .
the last one is not work with magisk
I use this version YT_X705F_S001135_210909_ROW
yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?
Loserintheend said:
yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?
Click to expand...
Click to collapse
You just have to make sure you use the boot.img from the exact firmware you are on now. Let me know if it worked.
Johannj22 said:
I use this version YT_X705F_S001135_210909_ROW
Click to expand...
Click to collapse
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release OTA-Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install OTA Update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS
Loserintheend said:
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS
Click to expand...
Click to collapse
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.
Johannj22 said:
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.
Click to expand...
Click to collapse
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .
Loserintheend said:
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .
Click to expand...
Click to collapse
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img
Johannj22 said:
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img
Click to expand...
Click to collapse
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9
Loserintheend said:
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9
Click to expand...
Click to collapse
Waiting?. I am sorry I think its the language barrier ..I don't understand certain things you say.
Any help provided for X705X tab,It got A10 update.How can I get stock rom and boot image for the latest update?
Finally I find out RSA mentioned in this threads and able to download stock firmware
vygavedha said:
Finally I find out RSA mentioned in this threads and able to download stock firmware
Click to expand...
Click to collapse
Yes use RSA and flash the stock firmware. This stock firmware you flashed should be saved in your system's C:\ProgramData\RSA\Rom Files folder. Just get the required image files from there/
I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?
vygavedha said:
I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?
Click to expand...
Click to collapse
Send me a screenshot
Johannj22 said:
Send me a screenshot
Click to expand...
Click to collapse
Sure. I have deleted the downloaded file. I will redownload the same and update the screen shot tomorrow