Related
My device: HTC Desire, CM7 RC1, unrevoked root, s-on
As a Chinese mainland user, I need to edit hosts to access certain websites like twitter and wordpress.(And because it seems that cm7 have some problems with vpn and ssh.)
but i tried various method (root explorer, adb, terminal), the only result is that origin hosts file come back after reboot. none of those methods mention s-off, so do I need s-off?
someone said it can be done in recovery mode,but I don't find that function in RA recovery 2.0. someone said it must be done through flashing a zip which contains new hosts file. Are they right?
Thanks
From fastboot (not recovery) without s-off OR with s-off in recovery OR with s-off with most file browsers with phone booted normal.
HTC desire has read only where hosts file reside without s-off
Sent from my HTC Desire using XDA App
From fastboot is new to me and I highly doubt that is true. From recovery means you boot in to recovery and then use a adb shell. This should work.
If it's just about the add blocking I believe this is the flashabel zip.
place the host file you want in system/etc in this zip then flash from recovery, its unsigned so you will have to turn off verification in the options first.
In Recovery you'll have read/write access to /system, regardless of your phone being S-OFF or S-ON. S-OFF is basically the ability to have the same level of access as you would have in Recovery, even when booted.
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
I had the exact same problem but I re-did it all and the file is there with all the entries. However, none of the entries are being blocked. The file format is all right, it's one of the above. Also on CM7 RC1.
------------------------------
- Sent via HTC Desire -
luciffer said:
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
Click to expand...
Click to collapse
Just push it to the correct position after ROM install through Recovery. It'll be there.
------------------------------
- Sent via HTC Desire -
luciffer said:
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
Click to expand...
Click to collapse
Here's how I'd change my hosts file:
1. Boot in recovery, load up adb shell and mount both system and sdcard partitions.
2. Push the hosts file in your sdcard.
3. Remove the old hosts file (and check with ls).
4. Copy the new hosts file (and check with ls).
5. Reboot phone.
6. ???????
7. PROFIT
I edited a configuration file for Bluetooth(main.conf) in which i changed the device discoverable for value to be 0 (by default 120). then i left the folder as is (r/w) mode and saves and rebooted.
rescue mode is available(volume up - home -power)
boot loops continously
Kies not recognising when connecting when the device is turned off
there is a backup of the file at the same folder..
if you can provide me too ..how do i upload to my phone.
need help ASAP.
try installing firmware with odin
Other better ideas!
I am pretty sure that this matter was triggered because of that tweak..(editing of the file). I hope that restoring the original file would help.
Do you know about adb...?
Also i forgot where the actual bluetooth configurations file was in the root folder structure
adb will not work on device in recovery/download mode
to use adb mobile needs to be running
you can flash cwm in your mobile then upload the file and send me the link i will make a flashable zip and upload it then you can flash it
adb is running...just
Adb is running (while the phone keeps on showing boot animation-samsung logo-bootanimation-samsung logo-bootanima....) but it seems that it has permissions issues..i unrooted my phone before using adb .
i can access adb shell and list root directories but cannot enter further directories such as data\ permission denied
I donot have the file that i changed and quiet cannot remember it..
Check on your mobile and see for
data/misc/bluetoothd/
if it has files such as music.conf,main.conf etc etc..then this is the needed folder..
can you create a update.zip
like i used for rooting/ unrooting .that doesnt need CWM
that empties the directory ,because it has some backup files .bak created by root explorer
loads files from your mobile
i am currently unrooted ..do i need root?
actually adb works during splashscreen
get the original file and push it through the system, set permission and it should work
if all else fails,..... odin
download update.zip from http://dl.xda-developers.com/attach...5498d4d803e6a/4fcc0dd2/7/6/3/0/8/8/update.zip and place it in the root of your sdcard
go to recovery flash it you will get root then you can use adb
if it is not flashing first flash cwm through Odin then flash this update.zip through cwm
The file you sent is invalid. corrupt..?
what does this do..exactly.
i already have a update.zip and update-unroot.zip to root unroot my device
so
do i need root permission to use adb..because commands like
adb root gives"error not available in production devices"
&
adb shell
$ su
etc are showing permission denied.
if you have the original files on your galaxy y.. can you make update.zip with the above instruction
if adb works..i dont exactly remember the file path that i changed..so using the hints above please can you send me the file path
My aim here is to use odin or factory reset only at the last.
just root the device by flashing the root.zip in recovery and then use
adb shell
su
and it will work
No still get permission denied.... like always.
cd data
ls
open directory failed, Permission denied.
1. flash cwm recovery through odin
2. then upload the original file
3. I will create a update.zip and will upload it
4. you will need to flash it in cwm recovery
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
y2k2r2d2 said:
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
Click to expand...
Click to collapse
http://db.tt/2NStXBF8
flash it in recovery but it may not work as I don't have galaxy y I have a different mobile
it didnt allow installation both through cwm and recovery mode
& now
i messed up with CWM
backup-restore feature
create backup
edited the system.tar
put the original file
calculated md5 for new system,tar
edited the nandroid.md5 with appropriate editor and filled with the new calculated md5 of system.tar
advance restoore....select system files...
md5 check pass
restore fail
now boot stuck at initial screen
pretty sure even wipe data wont work
So i Had to resort to ODIN..Thanks for your time mate...
humm
I also think Odin is the last choice
EDIT: This root method has been outdated, see the newer guide instead https://forum.xda-developers.com/android/general/tutorial-root-oppo-f1s-flashtool-6-0-t3651220
Why I made this tutorial:
Recently some members claimed that KingRoot is not working for Oppo F1s(A1601) anymore, I assume it's because Kingroot uses cloud based root method, means Kingroot downloads root package and command from cloud and execute on your phone. Maybe the problem was caused by the change of their server, some configuration has been replaced? At this time, I still have a working root method working now, so I would like to share it with everyone Also, you can follow this guide to get rid of the superuser App from those android root exploit app and use SuperSU.
In short, this tutorial tells:
1.How to Root Oppo F1s(A1601) with KingoRoot.(Though cloud based root App Kingroot is not working at this period but KingoRoot the offline one is still working)
2.Though KingoRoot prevent you to switch to other superuser App, we can still replace it with SuperSU with few steps, no custom recovery needed.
****NOTE****
There're various version of KingoRoot apk over the Internet, use the APK version I provided at attachment can guarantee there're no unexpected errors.
The script to replace kingo root was based on the one here but with a little modification, I've added a infinite loop for the script because KingoRoot cause a force reboot(soft reset) right after you delete root from the app, I assume its because KingoRoot want to prevent you to replace it. A infinite loop can make sure the file copying action has been done before your phone reboot.
Steps to Root F1s and Install SuperSU:
1.Install android terminal from Google Play: https://play.google.com/store/apps/details?id=jackpal.androidterm
2.Download the attachment, extract the zip archive, you get an APK "KingoRoot.apk" and a folder "rmkingo", copy the APK and the folder to your Internal storge(Sdcard)
3.Use any file management App to open KingoRoot.apk and install KingoRoot.apk
4.Open KingoRoot and click "one click root" then wait it to obtain root
5.After root succeeded, Open previous installed "Terminal Emulator for Android" and type
Code:
su
. Now KingoRoot's Superuser should pop up and ask you if you want to grant root access, allow it.
6.Now change terminal directory to the script folder, terminal type
Code:
cd /sdcard/rmkingo
7.Now execute the first script, terminal type
Code:
sh step0.sh
8.If there's no error on the previous action, Now proceed to execute the second script which is an infinite loop, you might see infinite error message after you executed it, terminal type
Code:
sh step1.sh
9.Now make sure the Terminal emulator is still open and the script is still running in background, just open SuperUser(installed by KingoRoot), find and click "Remove root" in the option of the App.
10.Your phone should be forced reboot now, after reboot, install SuperSU from google play: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=zh_TW
11.Open SuperSU and update su binary file with normal mode and wait, it should finish in 2-3 minutes.
12.Hit thanks(My pleasure)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
above method has been confirmed working with the latest rom from my region,(date 2017/02/12 still working)
Rom: A1601_TW_11_A.17_161003
I am on build a1601ex_11_a27_170111
its currently letest update in india
sagargjasani264 said:
I am on build a1601ex_11_a27_170111
its currently letest update in india
Click to expand...
Click to collapse
Wow, Taiwan haven't receive any update since October........Looks like the rom of our region is terribly outdated,lol
A lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?
evilhawk00 said:
wow, taiwan haven't receive any update since october........looks like the rom of our region is terribly outdated,lol
a lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?
Click to expand...
Click to collapse
kingoroot is on 90% since last 20min
---------- Post added at 12:22 PM ---------- Previous post was at 12:10 PM ----------
sorry bro but kingoroot faild...
Sorry kingoroot failed error code : 0x196514
Lyes2 said:
Sorry kingoroot failed error code : 0x196514
Click to expand...
Click to collapse
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier
Failed
Directory not found bro
evilhawk00 said:
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier
Click to expand...
Click to collapse
what kind of modification do you exactly need to do to the update package to not loose root after update?
ngoralph said:
what kind of modification do you exactly need to do to the update package to not loose root after update?
Click to expand...
Click to collapse
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment OPPO_F1s_twrp3.0_modified_devicemodel.zip
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.
Ananaqil12 said:
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.
Click to expand...
Click to collapse
If you want stock recovery image, check my reply here https://forum.xda-developers.com/showpost.php?p=71006625&postcount=26
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
There are no lines that say apply patch
diosdetiempo said:
[/HIDE]
There are no lines that say apply patch
Click to expand...
Click to collapse
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
It worked!
Here's a little guide
1) Put your TWRP, SuperSU and Android 6.0 Oppo F1S ROM onto SD card
2) Use Flashify to flash TWRP
3) Reboot into TWRP recovery
4) Flash Android 6.0 F1S ROM
5) Flash SuperSU
6) Reboot phone and you should be good to go
evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
update: the only issue i find is that SIM card isn't recognized
diosdetiempo said:
update: the only issue i find is that SIM card isn't recognized
Click to expand...
Click to collapse
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup
evilhawk00 said:
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup
Click to expand...
Click to collapse
have you tested with 6.0?
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me
ngoralph said:
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me
Click to expand...
Click to collapse
6.0 would work if the sim card issue could be fixed. i can't work it out :/
diosdetiempo said:
6.0 would work if the sim card issue could be fixed. i can't work it out :/
Click to expand...
Click to collapse
did you try restoring the nvram using twrp as stated before?
and did you wipe your data before flashing?? i think the transition from 5.1 to 6.0 may have broke some things read about it somewhere that wiping was necessary for LP to MM
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.
Hi Guys,
For some reasons, my kernel got updated without any change from me, not sure how this is possible.
Now, because of that, I lost root, is there a quick way to restore root (magisk) ?
Thanks in advance !
Yep. Just download the matching factory image zip for your currently installed build of Android. Then, extract the boot.img file, copy it over to your phone, patch it within the Magisk app and it will spit out a patched boot.img file into your "Download" folder. Next, copy that patched boot.img file back to your computer and flash that patched boot file using fastboot.
That may look like a lot of different steps, however, the process usually takes less time than it has taken me to type this comment, haha. Enjoy your root access =)