[RECOVERY][ROOT][TWRP 3.3.1-1]Samsung Galaxy A3(2015) SM-A300F/FU/G/H/M - Galaxy A3, A5, A7, A8, A9 Android Development

Unofficial release -TWRP recovery for the Galaxy A3 - SM-A300F/FU/G/H/M, Qualcomm MSM8916
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html
*SEANDROID warning fix
*Recovery reboot fix
*MTP fix
*Modem, APNHLOS, EFS and Recovery partition backup
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot:
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Flash with TWRP:
Extract the recovery.img from the tar archive then in TWRP select Install>>Install image.
twrp_3.0.2-1_sm-a300
twrp_3.3.1-2_sm-a300x_101119
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
I suggest using Magisk as its a currently up to date project. Supersu is no longer maintained:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Credits: Me, Teamwin and my testers- icesehman, -CALIBAN666-, jimbomodder
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.

Hmm... could this maybe be flashed with Flashify?

King-V said:
Hmm... could this maybe be flashed with Flashify?
Click to expand...
Click to collapse
It could, but better to flash it with TWRP or ODIN.

ashyx said:
It could, but better to flash it with TWRP or ODIN.
Click to expand...
Click to collapse
Wait... what? Flash this version of TWRP, using an older version of TWRP? Does that really work?

King-V said:
Wait... what? Flash this version of TWRP, using an older version of TWRP? Does that really work?
Click to expand...
Click to collapse
Of course it does, it's been that way since about version 2.8.6.0

ashyx said:
Of course it does, it's been that way since about version 2.8.6.0
Click to expand...
Click to collapse
Never knew that; it sounds quite handy... Thanks a lot!

Well, i wish we had 5.1.1...
Thanks a lot btw.

PlutoDelic said:
Well, i wish we had 5.1.1...
Thanks a lot btw.
Click to expand...
Click to collapse
You don't need 5.1.1.
Sent from my HTC One_M8 using XDA Free mobile app

ashyx said:
You don't need 5.1.1.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Obviously.
I stumbled on an issue. TWRP boots fine, but no touch input. Reboot issue seems to remain IF one "reboot to recovery" from the system. Everything works find under the hood, connected through adb without any issue.

PlutoDelic said:
Obviously.
I stumbled on an issue. TWRP boots fine, but no touch input. Reboot issue seems to remain IF one "reboot to recovery" from the system. Everything works find under the hood, connected through adb without any issue.
Click to expand...
Click to collapse
Which device model?
Can you post the recovery.log file?

PlutoDelic said:
Obviously.
I stumbled on an issue. TWRP boots fine, but no touch input. Reboot issue seems to remain IF one "reboot to recovery" from the system. Everything works find under the hood, connected through adb without any issue.
Click to expand...
Click to collapse
hi community,
first of all very big thanks to @ashyx to support our device and port the new twrp :highfive:
i can confirm that the recovery start without problems after flashing with android 5.0.2 but sadly maybe the touchdriver not loading. touch have for now no function
my device is the a300fu with touchwiz stockrom and baseband boj4.
@ashyx, please fix the problem with touch and maybe all will be good :highfive:
best regards and thank's for support our community :highfive: :good:

Duke2010 said:
hi community,
first of all very big thanks to @ashyx to support our device and port the new twrp :highfive:
i can confirm that the recovery start without problems after flashing with android 5.0.2 but sadly maybe the touchdriver not loading. touch have for now no function
my device is the a300fu with touchwiz stockrom and baseband boj4.
@ashyx, please fix the problem with touch and maybe all will be good :highfive:
best regards and thank's for support our community :highfive: :good:
Click to expand...
Click to collapse
Yes I'll fix the issue, but I need someone to upload the recovery log from cache/recovery/last_log

ashyx said:
Which device model?
Can you post the recovery.log file?
Click to expand...
Click to collapse
A300FU
Attached.
Reflashing the .tar weirdly gets rid of the reboot to recovery issue, wonder if any flag is being reset...

PlutoDelic said:
A300FU
Attached.
Reflashing the .tar weirdly gets rid of the reboot to recovery issue, wonder if any flag is being reset...
Click to expand...
Click to collapse
hi folks,
i send my logfile too. well done :highfive:
best regards :good:

Duke2010 said:
hi folks,
i send my logfile too. well done :highfive:
best regards :good:
Click to expand...
Click to collapse
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631

ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
sorry, no my device stuck into boot recovery process. it is not possible to booting up into recocery. :crying:
try again please :highfive:
thank you and best regards :good:

Duke2010 said:
sorry, no my device stuck into boot recovery process. it is not possible to booting up into recocery. :crying:
try again please :highfive:
thank you and best regards :good:
Click to expand...
Click to collapse
Please post your device model.

Hi mate,
My device is the a300fu with boj4 bootloader and boj5 touchwiz stockrom
Best regards :good:

First of all Thanks for your work!
I´m also on the A300FU Device
ashyx said:
Yes I'll fix the issue, but I need someone to upload the recovery log from cache/recovery/last_log
Click to expand...
Click to collapse
With the TWRP from OP, I confirm TWRP starts but Touch is not working (Log old)
ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
With the "Fix" it stuck bevor TWRP Screen should appear (Log new) btw. flashed both with Odin

Jonny_Hood said:
First of all Thanks for your work!
I´m also on the A300FU Device
With the TWRP from OP, I confirm TWRP starts but Touch is not working (Log old)
With the "Fix" it stuck bevor TWRP Screen should appear (Log new) btw. flashed both with Odin
Click to expand...
Click to collapse
Looking at the recovery log it seems there is an issue loading the graphics, so I have reverted one of the flags that I think is causing the issue.
https://www.androidfilehost.com/?fid=24499762636004909
NOTE: I will not support any posts related to flashing with Flashify, this app has issues with some devices. ODIN(prefered), TWRP and the DD method is fine.
.

Related

Weird problem

Help me please, I installed TWRP 2.7.0.0 with F2FS support, flashed the f2fs tools and now TWRP wont boot and I can't connect to download mode. Please guys help me :crying:
You may need to use ADB to reflash your recovery.This thread is very useful:http://forum.xda-developers.com/showthread.php?t=2131284
Поздрави!
How did you install it? Using option 1 or 2?
#1:
1. Flash TWRP
2. Flash f2fs zips
3. Reboot; or
#2:
1. Flash TWRP
2. Reboot
3. Flash f2fs zips.
ArkThompson said:
How did you install it? Using option 1 or 2?
#1:
1. Flash TWRP
2. Flash f2fs zips
3. Reboot; or
#2:
1. Flash TWRP
2. Reboot
3. Flash f2fs zips.
Click to expand...
Click to collapse
Option #1, It turned out that the 2.7.0.0 version has that bootloop problem and somehow my device can't detect in download mode, only adb connection possible.
limnaln said:
Help me please, I installed TWRP 2.7.0.0 with F2FS support, flashed the f2fs tools and now TWRP wont boot and I can't connect to download mode. Please guys help me :crying:
Click to expand...
Click to collapse
I really hope someone will help you here in Q/A
Sorry if I didn't help you enough previously in AMCHA thread.
limnaln said:
Option #1, It turned out that the 2.7.0.0 version has that bootloop problem and somehow my device can't detect in download mode, only adb connection possible.
Click to expand...
Click to collapse
The problem is that you used #1 instead of #2. Someone in the AGNi thread also did that and had the sane problem as you, not sure how they fixed it though.
" I can't connect to download mode."
Do you mean that when you are in download mode, Odin does not detect the phone ?
Because if so, then that sounds like a driver issue.
timmtn said:
" I can't connect to download mode."
Do you mean that when you are in download mode, Odin does not detect the phone ?
Because if so, then that sounds like a driver issue.
Click to expand...
Click to collapse
The issue has been fixed and the phone is working properly with OmniRom
limnaln said:
The issue has been fixed and the phone is working properly with OmniRom
Click to expand...
Click to collapse
To help the others who are going to find the same problem, can you,please explain how you solved the problem.Best regards!
viktorak said:
To help the others who are going to find the same problem, can you,please explain how you solved the problem.Best regards!
Click to expand...
Click to collapse
It turned out that its not that complicated, my usb cable was bricked so I bought a new and a better one, flashed official 4.4.4 with Odin and I fixed the issue :highfive:

[TWRP][EXPERIMENTAL] suzuran twrp 3.0

Hello people,
I was able to successfully build twrp 3.0 for suzuran (our device, duh!) and thought I'd share the recovery.img so you can test and see what works and what doesn't.
The recovery was built in a CM13 similar environment (PAC), so there might be some issues when working with stock kernel.
Since this is an experimental build (I tested main functionalities and they work, but didn't get down to the nitty-gritty), here's a small disclaimer:
By flashing or booting the attached recovery you're risking damaging you device, or losing the data on your device!
Neither I nor anyone else but YOU is responsible should any bad unintended problems appear!
If you're feeling adventurous then feel free to flash the recovery.img (along with Androplus kernel) and try the sweetness that is TWRP 3.0 :good:
Download link:
April 3, 2016 (3.0.1)
March 25, 2016
March 21, 2016
March 12, 2016
Known issues:
Temperature reading is botched
Crypto might not be working, like AT ALL
usb connection doesn't work (only if you use this recovery with Androplus kernel)
There could be more problems, which is why this is EXPERIMENTAL for now
And now let's get to the sources!
kernel:
[url]https://github.com/oshmoun/kernel/tree/aosp/LA.BF64.1.2.2_rb4.7[/URL]
device sources:
[url]https://github.com/oshmoun/device-sony-suzuran/tree/master[/URL]
[url]https://github.com/oshmoun/device-sony-kitakami/tree/master[/URL]
[url]https://github.com/SonyCM/device-sony-common/commits/cm-13.0[/URL]
And now to thank the people who helped in this endeavor:
TWRP team for the awesome recovery!
@nilezon for the TWRP flags (which I still need to go through to check if I missed/need anything, especially crypto flags...)
FXP team for device sources, Especially @adfad666
All of the Sony AOSP contributors, they're awesome people!
It doesn't work on my Android 6.0 device:crying:
doesn't work on sony mm, stuck at sony logo
iMaeGoo said:
It doesn't work on my Android 6.0 device:crying:
Click to expand...
Click to collapse
tanto124 said:
doesn't work on sony mm, stuck at sony logo
Click to expand...
Click to collapse
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
iMaeGoo said:
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
Click to expand...
Click to collapse
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
69650eaccdd8b24a3efc0ef1b4bdffb8
The img's MD5 is right.
I'll try to boot Z5C_TWRP_152_v2_nilezon on my device later.
It worked before I upgraded to MM.
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
iMaeGoo said:
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
Click to expand...
Click to collapse
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
t4656 said:
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
Click to expand...
Click to collapse
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
oshmoun said:
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
Click to expand...
Click to collapse
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
t4656 said:
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
Click to expand...
Click to collapse
This is so freaky what the heck!!!
Could you flash bootloader from 5.1 ftf and see if it works properly then?
I'll (finally) update to MM today , so I'll witness the issues first hand.
oshmoun said:
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Click to expand...
Click to collapse
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
iMaeGoo said:
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
Click to expand...
Click to collapse
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
oshmoun said:
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
Click to expand...
Click to collapse
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
iMaeGoo said:
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
Click to expand...
Click to collapse
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
oshmoun said:
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
Click to expand...
Click to collapse
Can external storages be found in Android system?
iMaeGoo said:
Can external storages be found in Android system?
Click to expand...
Click to collapse
everything concerning external sdcard function is working here as far as i tested (both in Stock mm rom and twrp3)
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
it's E5823 running 32.1.A.1.163 . I am sure that I was just booting , downloaded file is okay .

[RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A5(2015) SM-A500F/FU/G/H/M

Unofficial release -TWRP recovery for the Galaxy A5 - SM-A500F/FU/G/H/M, Qualcomm MSM8916
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
SEANDROID warning fix
Recovery reboot fix
Modem, APNHLOS, EFS and Recovery partition backup
29/4/2016 - Time offset fix
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot:
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Flash with TWRP:
Extract the recovery.img from the tar archive then in TWRP select Install>>Install image.
twrp_3.0.2-1_sm-a500
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
http://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Credits: Me, Teamwin and my testers- icesehman, -CALIBAN666-, jimbomodder
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
I'll be keeping an eye on this thread
Thankyou.... Working Fine..
No reboot issue.. A500G
Any tried to see if aroma files now flash OK?
From the giver of stock roms
Edit..
Works fine finally [emoji122] [emoji122]
Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!
jazzzzy said:
Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!
Click to expand...
Click to collapse
Isn't there already twrp for A700FD?
ashyx said:
Isn't there already twrp for A700FD?
Click to expand...
Click to collapse
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!
only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.
icesehman said:
only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.
Click to expand...
Click to collapse
Thank you.
OK, I'll try to disable wanam's power menu and flash TWRP. I'll write the result. ...
I disabled wanam's power menu, flashed TWRP 3.0.0 without autoreboot ticked and rebooted into recovery.
Then I set time settings in TWRP and started backup. Backup completed...
Reboot from TWRP (Reboot System) - Reboot normal !!!
I will watch its behavour ... and perhaps the problem is solved.
jazzzzy said:
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!
Click to expand...
Click to collapse
I'll see what I can do, time permitting.
So Far So Good.
Good job Mr. @ashyx , I've tested this recovery and two problems fixed out of three.
SEANDROID Error: Fixed.
Recovery reboot : Didn't fixed
EFS, APNHLOS etc... partitions Backup : Fixed
I reverted back to 2.8.7.0 recovery until recovery reboot get fixed.
I'll post a recovery log soon.
I'm using A500H Duos.
Thanks.
Ahmed_Khalifa said:
Good job Mr. @ashyx
Recovery reboot : Didn't fixed
Click to expand...
Click to collapse
Others say this issue is fixed?
ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
That links for a300
Sent from my SM-A500FU
Whoops wrong thread!
Sent from my HTC One_M8 using XDA Free mobile app
Little Confused.
ashyx said:
Others say this issue is fixed?
Click to expand...
Click to collapse
Are they using A500H or other variant?
Ahmed_Khalifa said:
Are they using A500H or other variant?
Click to expand...
Click to collapse
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?
recovery reboot problem.
ashyx said:
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?
Click to expand...
Click to collapse
Here is what I did:
I flashed the recovery via flashify.
I rebooted the device normally.
After the phone restarts, it shows the Yellow colored warning Set warrenty bit: recovery.
The device boots into TWRP recovery mode.
After that I press reboot -> system.
After restart, it goes back to step 3.
Thank you.
That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app
If we reboot directly to recovery, i mean through wannam xpossed power menu, recovery reboot issue occurs.. Pls fix this too..
Otherwise all are perfect
the error still exists.
ashyx said:
That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I used the flash option in TWRP but it still reboots into recovery.
I posted a recovery log maybe it'll help you fix the problem.
by the way, can you tell me which baseband,pda,csc you're using?
my software might be a little old?
Thanks.

[Kernel] [6.0.1] [23.5.A.1.291] [Advanced stock with TWRP] [UB]

Stock kernel with TWRP recovery SGP621
Sony RIC disabled
TWRP 3.0.2
Download
From here and unzip
Flash via flashtool or fastboot
Code:
fastboot flash boot boot.img
Root
Flash this in recovery
Credits
tobias.waldvogel for his awesome tool
TWRP team
shoey63 for guiding me
there is a low interest in the devs for this tablet. So, everything is appreciated..
Thanks for your work, in an few hours I'll test it.
wulfiss said:
there is a low interest in the devs for this tablet. So, everything is appreciated..
Thanks for your work, in an few hours I'll test it.
Click to expand...
Click to collapse
you are welcome buddy!
Thanks alot, I'd love to have TWRP 3.0.2 on stock rom.
But I can seem to get it to work, tried on a customized US an a customized DE stock image, latest version.
Doesn't boot on either, screen stays black when I try to turn on the tablet.
ipharus said:
Thanks alot, I'd love to have TWRP 3.0.2 on stock rom.
But I can seem to get it to work, tried on a customized US an a customized DE stock image, latest version.
Doesn't boot on either, screen stays black when I try to turn on the tablet.
Click to expand...
Click to collapse
No boot screen at all? What's your tablet model?
SGP-612
ipharus said:
SGP-612
Click to expand...
Click to collapse
Is your bootloader unlocked? If so send me your kernel.sin from the firmware.
codfx said:
Is your bootloader unlocked? If so send me your kernel.sin from the firmware.
Click to expand...
Click to collapse
Yes bootloader is unlocked. kernel.sin for Custom DE attached (SGP612_Customized DE_1290-4946_23.5.A.1.291_R2D)
I don't get it to work either. SGP611, using SGP611_23.5.A.1.291_1290-0168_R4D customized UK. Won't boot, only flashes its red little light. Did you find any solution to it? Would be awesome to get this kernel.
Hi,
Have I sent you the correct file? Did you get the time to have a look at it?
No stress, just wonderin :angel:
is there a way to unlock bootloader using kinds of special hardware (like HTC xtc2clip)
(thanks O2 for locking the bootloader -_-)
Hey
Something new about black screen ?
Same problem here.
SGP621
Thank you
vmille said:
Hey
Something new about black screen ?
Same problem here.
SGP621
Thank you
Click to expand...
Click to collapse
If you are getting a black screen after flashing the kernel, just force restart the device. Then the device will boot fine.
Could a version of this be build with the device name "scorpion"? It won't let me install this ROM since the device name doesn't match (it seems to be empty in this image whereas that ROM requires it to be "scorpion").
Edit: nevermind, figured out I can modify the script in side the ROM to remove the check instead.
Thanks for a working TWRP for my old tablet
codfx said:
If you are getting a black screen after flashing the kernel, just force restart the device. Then the device will boot fine.
Click to expand...
Click to collapse
I get a black screen as well, tried to force reboot, same issue.
danw84 said:
I get a black screen as well, tried to force reboot, same issue.
Click to expand...
Click to collapse
what's your device model?
codfx said:
what's your device model?
Click to expand...
Click to collapse
SPG611
danw84 said:
SPG611
Click to expand...
Click to collapse
This kernel is only for SGP621. It's clearly mentioned in OP.
Think you!
Not easy for an old man, but after several times it went perfect.
Not able to tell you what I did exactly but I have SGP621, french 6.01.
SGP612 boot.img
Hi,
I made a boot.img for the SGP612 [6.0.1] [23.5.A.1.291] unlocked BL.
Sony RIC disabled
TWRP 3.0.2
(DRM fix)
Root and Xposed is NOT included. I recommend flashing Magisk v12 later in TWRP and enable Magisk Core Only Mode and Magisk Hide in the settings. Then it will pass the SafetyNet test and you can use su.
To flash the boot.img, put your SGP612 into fastboot mode (Volume Up + connect USB) and then run:
Code:
fastboot flash boot boot.img
If you have a backup of your TA partition, before you unlocked, see the rootkernel thread by tobias.waldvogel, how the DRM fix works.
Thanks to codfx for give me the idea for a SGP612 counterpart and to tobias.waldvogel for his tool :good:

Twrp latest for samsung m10 android 10 [Test 1]

hi there im looking for tester to make a full compatible twrp for samsung m10. then i made this Test 1 from scratch.
dont worry if its fail your phone wont be bricked just read carefully i case bootloop
in case bootloop:
first get logs recovery.log and dsmeg then reply i will fix it soon
if you see blue (cyan) screen just plug your phone with pc and flash via odin your stock recovery.
if your phone wont boot and see a msg in read like "could not boot blah blah.." press sound button up + down in same time and plug .. like above
if you see black screen and your phone loop turn on off ... click power + sound up.. for 5 s then your phone shut down and in same time press sound button up + down in same time and plug .. like above
i used twrp 9.0 branch
link:
Release Test 1 twrp · SA-15/android_device_samsung_m10lte
Contribute to SA-15/android_device_samsung_m10lte development by creating an account on GitHub.
github.com
if it works please say it and soon i will build ofox or shrp
not work m105G, succes flash but stay in stock recovery
Kakang_Ragil said:
not work m105G, succes flash but stay in stock recovery
Click to expand...
Click to collapse
it stays on stock hmm do you have magisk ?
SA-15 said:
it stays on stock hmm do you have magisk ?
Click to expand...
Click to collapse
when i pacthed rom with magisk. system not run normaly, (it's softbrick) screen say " only official software ....bla bla bla...",, even though i'm already open oem unlock via developer option.
Kakang_Ragil said:
when i pacthed rom with magisk. system not run normaly, (it's softbrick) screen say " only official software ....bla bla bla...",, even though i'm already open oem unlock via developer option.
Click to expand...
Click to collapse
ah yes i think its dm-verity then you should flash a disabler sorry about the twrp
SA-15 said:
ah yes i think its dm-verity then you should flash a disabler sorry about the twrp
Click to expand...
Click to collapse
how to disable dm-verity? how to do that?
Kakang_Ragil said:
how to disable dm-verity? how to do that?
Click to expand...
Click to collapse
flash this on twrp
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.1.zip
then also its recommended to flash magisk
Kakang_Ragil said:
when i pacthed rom with magisk. system not run normaly, (it's softbrick) screen say " only official software ....bla bla bla...",, even though i'm already open oem unlock via developer option.
Click to expand...
Click to collapse
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Kakang_Ragil said:
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Click to expand...
Click to collapse
no there is no devs for this phone
Kakang_Ragil said:
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Click to expand...
Click to collapse
if you can help me to revive this phone again. my telegram @rogerfortun
SA-15 said:
if you can help me to revive this phone again. my telegram @rogerfortun
Click to expand...
Click to collapse
how?? what can i help?
Kakang_Ragil said:
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Click to expand...
Click to collapse
no there is no kernel for this device
SA-15 said:
no there is no kernel for this device
Click to expand...
Click to collapse
Ok,,,, thanks info
Kakang_Ragil said:
Ok,,,, thanks info
Click to expand...
Click to collapse
can you try this twrp
https://github.com/n7105/Action-Recovery-Builder/releases/download/2974756341/recovery.img
dont forget to compress it into .tar

Categories

Resources