Hello there my Samsung a21s is now fully upgraded and I want to install TWRP but I am facing an error, that device binary is 0x5 and recovery binary is 0x0
now, how can I fix that ??????
whats is your firmware version? and binary version?
jawad213 said:
Hello there my Samsung a21s is now fully upgraded and I want to install TWRP but I am facing an error, that device binary is 0x5 and recovery binary is 0x0
now, how can I fix that ??????
Click to expand...
Click to collapse
I succeded in port a twrp
It's see the sd card but i can't manage to make:
1.To mount and read Internal Storage
And 2 i can t solve the bootloop problem
So you have to flash the stock recovery and original vbmeta
This is for U7
I unpacked the image with
Android Kitchen
Related
How to root Galaxy J7 (SM-J700F) without tripping knox ?
5.1.1 Lolipop with Exynos 7580 Octa Core processor,
smj700f said:
How to root Galaxy J7 (SM-J700F) without tripping knox ?
5.1.1 Lolipop with Exynos 7580 Octa Core processor,
Click to expand...
Click to collapse
Try king root or pingpong
tried
messi2050 said:
Try king root or pingpong
Click to expand...
Click to collapse
i tried both , not working on the phone.
Doesn't appear to be any non Knox tripping methods. Only via TWRP and SuperSU zip that I could find, which will definitely trip it.
Plz help...when i flash the twrb and pass.i try to to get in recovery..the twrb not flash and open stock recovery....any solution
j700f osama said:
Plz help...when i flash the twrb and pass.i try to to get in recovery..the twrb not flash and open stock recovery....any solution
Click to expand...
Click to collapse
With most Samsung devices, you must boot to recovery immediately after flashing a custom recovery and before it boots into the operating system itself. This is due to a script in the original system that detects a modified recovery and rewrites the stock recovery back to it. If you boot to TWRP first and install the SuperSu zip, it should disable that script and let you keep the new recovery.
If i do that..give me..
Recovery android no reginzed
And stop on galaxy j7......
I passed TWRP successfully but when i select that suoersu zip file from sd card it bring me back at the logo of TEAMWIN...
plzzz help
It's possible to load twrp recovery using fastboot boot twrp.img then flash supersu.zip....
Sent from my SM-J700F using XDA-Developers mobile app
is it solved yet
I don't know if this is solved yet. Decided i would go ahead and add my two cents.
For Samsung j700f sets.
I have found no way yet that does not trip knox. But according to the grapevine, you could always revert back to the way it was using some Samsung tools.
You will have to take the TWRP path. Install USB drivers on PC by installing Samsung Kies. Next download odin and transfer latest supported twrp files while keeping the phone off. Now after Odin restarts your set in TWRP recovery mode, find and install the SUPERSU package you already downloaded on your phone memory. Clear data, dalvik etc caches. Reboot.
Now whenever you want TWRP, reboot using up volume + home + power.
Thanks.
smj700f said:
How to root Galaxy J7 (SM-J700F) without tripping knox ?
5.1.1 Lolipop with Exynos 7580 Octa Core processor,
Click to expand...
Click to collapse
Ｒｅｍｏｖｅ ｋｎｏｘ ｆｏｒ ｉｎｓｔａｎｃｅ， ｂｕｔ ｓｔｉｌｌ ｙｏｕｒ ｗａｒｒａｎｔ ｗｉｌｌ ｂｅ ｖｏｉｄ
Hi all! I need your help! How can I porting cwm or twrp recovery for my device and how can I root? This device is leagoo p1 with mt6580 and it runs nougat firmware! Thanks for your help!
Ferbir88 said:
Hi all! I need your help! How can I porting cwm or twrp recovery for my device and how can I root? This device is leagoo p1 with mt6580 and it runs nougat firmware! Thanks for your help!
Click to expand...
Click to collapse
Sorry for waking up an old thread, 364 days later but this can be helpfull for other P1 users and phones with similar chipset 6580
After trying to root this phone for so many days I finally did it.
First I found this video and I tried this way and it didn't work.
Thank you TAO Croatia, hvala ti druze
Most part of this video worked fine.
My bootloader was unlocked and in sp tools after trying to flash pathed boot img I coudn't make it work.
What I had to do is next. I relocked the bootloader ( with flashing last firmware from 05 sep 2018 twice ). After flashing stock firmware, I flashed my patched boot img renamed from patched to boot.img, and after first boot I have checked with root checker and yes, my device is rooted now.
After installing firmware boot device, than turn it off and with flashtool replace boot.img.
I didn't use stripped version of scatter file as suggested.
I managed to port TWRP for our device.
https://forum.xda-developers.com/showpost.php?p=78291892&postcount=96
Hi there, I hope you guys can help me. Here is the information I have, and thank you so much in advance for your help. Really hope someone will be able to help my stupid self. Haha.
SM-G925F
1.Your bootloader status if applicable - UNLOCKED
2. Rom name with complete baseband/date/version - NEMESIS NOUGAT STABLE S7E PORT V3.1 -
3. Kernel name - Linux 3.10.x
4. Any Mods you are using - None
5.If you are using Custom Rom, your flashing style i.e dirty/clean or you wiped anything else in specific - Flashed Nemesis after flashing another rom that used superSU, then attempted to restore superSU while still using the same rom. I believe this caused a bootloop and I factory wiped the phone to attempt to resolve the bootloop, which has been unsuccessful.
6. If you used any guide, link to the guide - N/A
7. Root status - ROOTED
8. Your exact problem - When attempting to power up the device, stuck in the flashing samsung logo screen. I am able to access both TWRP recovery screen and download screen, however TWRP does not recognise .tar.md5 files, so it seems I am unable to flash a recovery.
9. Any method you tried that failed - Factory wiping the device
10.Any other detail you think would be necessary - I believe am unable to use ODIN as I am using a Macbook, however I am attempting to use it via Parellel. I can still transfer zips to the sd card using the TWRP recovery. The download screen reads:
ODIN MODE
PRODUCT NAME: SM-G925
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 1 (0x030c)
RP SWREV: B:5 K:2 S:2
alexsamsungsht said:
Hi there, I hope you guys can help me. Here is the information I have, and thank you so much in advance for your help. Really hope someone will be able to help my stupid self. Haha.
SM-G925F
1.Your bootloader status if applicable - UNLOCKED
2. Rom name with complete baseband/date/version - NEMESIS NOUGAT STABLE S7E PORT V3.1 -
3. Kernel name - Linux 3.10.x
4. Any Mods you are using - None
5.If you are using Custom Rom, your flashing style i.e dirty/clean or you wiped anything else in specific - Flashed Nemesis after flashing another rom that used superSU, then attempted to restore superSU while still using the same rom. I believe this caused a bootloop and I factory wiped the phone to attempt to resolve the bootloop, which has been unsuccessful.
6. If you used any guide, link to the guide - N/A
7. Root status - ROOTED
8. Your exact problem - When attempting to power up the device, stuck in the flashing samsung logo screen. I am able to access both TWRP recovery screen and download screen, however TWRP does not recognise .tar.md5 files, so it seems I am unable to flash a recovery.
9. Any method you tried that failed - Factory wiping the device
10.Any other detail you think would be necessary - I believe am unable to use ODIN as I am using a Macbook, however I am attempting to use it via Parellel. I can still transfer zips to the sd card using the TWRP recovery. The download screen reads:
ODIN MODE
PRODUCT NAME: SM-G925
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 1 (0x030c)
RP SWREV: B:5 K:2 S:2
Click to expand...
Click to collapse
First thing... if it's just stuck on the glowing Samsung logo then it's not a bootloop. It can take a while to boot so leave it about 20 minutes.
TWRP won't recognise tar.md5 files as it doesn't flash them. It flashes .zips. Odin is the one to flash tar.md5.
TWRP is the recovery, so you can't flash a recovery through a recovery (twrp)
What I would try from here... power on the phone and leave it on the Samsung logo for a while and it should boot. If it doesn't then just reflash nemesis ROM through twrp and start again.
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Use Sharp by the old process! Dont have to use twrp made for Android 9
Is a problem with a new security patch, i have one only and functional..
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Return at the v10.xxx rom stock, and can i flash twrp or orange fox recovery, but not all the version can i flash new's rom android 10 i have the same problem about 1 month & this is my solution :crying:
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
SidRose01 said:
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
Click to expand...
Click to collapse
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
ovi2901 said:
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
Click to expand...
Click to collapse
I only used the files from that link. I did not read it anything. But Thanks, you pointed this out.
This means that the next time I wipe data in TWRP, then I should first enable "use rm -rf instead of formatting" in TWRP settings
I have never tried 'wipe data' on this phone. But I'll remember this the next time I 'wipe data'. Thanks, you just saved me.
Samsung Galaxy J6 SM-J600G Binary U9 and Android Version 10.
Rooting process please.
flash magisk in custom recovery
Hello FraSharp,
on smartphone (Samsung J600FN stock version Android10),
I install the Magisk.apk, after I download the boot.img (extracted on PC from the stockROM.zip)
launch magisk on this downloaded boot.img, then magisk returm a bootPatch.img
on PC
I pull the bootPatch.img
then flash this bootPatch.img on smartphone
At reboot, error with a corrupt message and going to a factory reset.
So, how do you install your Magisk?