Related
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Go to fastboot and boot into stock recovery, don't install. Just boot to recovery, command should be something like below.
fastboot boot recovery-name.img
If you can go to opx recovery, flash stock rom and see
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Have you tried going through the steps for unlocking bootloader again?
Exodusche said:
Have you tried going through the steps for unlocking bootloader again?
Click to expand...
Click to collapse
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
tech_master said:
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
Click to expand...
Click to collapse
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
Ah no. You'll probably need to find someone who can re-sign CM so that it'll flash.
Thanks for the answer, I have no idea how to do this, how is this done? I don't seem to find much info online...
Sent from my HUAWEI TAG-L21 using Tapatalk
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
yuv93 said:
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
Click to expand...
Click to collapse
Thank you. I had tried this procedure previosuly, and didn't work. This time, since you insisted, I tried again, on another computer, and the phone was correctly detected, drivers installed and factory image installed on phone. I am happy again
Hey Guys,
i spent the last 8 hours to get my z back to life but without luck.
i was on aokp (official) as i decided to go back to stock rom, after i have seen that my device wouldnt boot a normally after the first flash, i flashed lineage os and from there it always tells me that it needs a password to start android. but i never had a passwort so i tried the one from my google account but it doesnt worked.
and now im stuck on the warning screen from the unlocked bootloader i can still go in recovery / bootloader mode but it doesnt matter what i flash it wont work.
SO PLEEASE HELP ME... i can give a small donate via paypal if you can help me the right way!
Hi.
You still have access to TWRP? if yes go to Advanced > File Manager then navigate to this path: /data/system
Look for this files:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Delete them all. if one or two of them is not exist that's Ok, skip them.
Now reboot the phone and see the password request form appears or not.
P.S. Don't panic you not bricked your phone.
Hello and thank you for your answer. But i do not have this files.
in data/system/ i have 3 ordners "dropbox-add" "heapdump" and "perfd".
nexxer92 said:
Hello and thank you for your answer. But i do not have this files.
in data/system/ i have 3 ordners "dropbox-add" "heapdump" and "perfd".
Click to expand...
Click to collapse
Then i suggest try a full wipe.
Dalvik
Catch
Data
System (By wiping this partition hole android OS will remove)
after that try to flash an custom ROM (Lingoes, RR, orginal images)
I hope this will solve the problem.
Soo, after a full night of flashing ( im seriously feeling like a pro hacker with all those command windows open ) i have managed to get back to stock reteu wit november security patch and relocked bootloader.
The only thing which bothers me at the moment is when i start the phone normally it takes me directly in the fastboot menu, but the screen for bootloader unlock is gone and it still says status: modified.
How is it possible that the phone boots normally? And can i do OTA Updates now with relocked Bootloader?
Thanks in advance!
nexxer92 said:
Soo, after a full night of flashing ( im seriously feeling like a pro hacker with all those command windows open ) i have managed to get back to stock reteu wit november security patch and relocked bootloader.
The only thing which bothers me at the moment is when i start the phone normally it takes me directly in the fastboot menu, but the screen for bootloader unlock is gone and it still says status: modified.
How is it possible that the phone boots normally? And can i do OTA Updates now with relocked Bootloader?
Thanks in advance!
Click to expand...
Click to collapse
How did you do that. I'm trying and trying to get back to stock EU firmware. No chance, I always get verification problem, need signed boot bla bla.
Btw. For normal boot try this
fastboot oem fb_mode_clear
knjigo said:
How did you do that. I'm trying and trying to get back to stock EU firmware. No chance, I always get verification problem, need signed boot bla bla.
Btw. For normal boot try this
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
hi
i flashed an RETBR Firmware.. bootet it, installed update.zip to 7.1.1 with adb sideload and then flashed again with fastboot oem lock begin.
nexxer92 said:
hi
i flashed an RETBR Firmware.. bootet it, installed update.zip to 7.1.1 with adb sideload and then flashed again with fastboot oem lock begin.
Click to expand...
Click to collapse
Great for you. Where did you get update to 7.1.1?
I get always error not signed boot.
If you could provide some step by step manual how to flash stock rom and relock bootloader it would be great.
I was also on reteu german firmware.
I have a weird issue. Not sure whats going on. Tab S3 is on Android 7.0. I'M running the stock rom but had rooted and installed twrp many months ago. Disabled updates on the device. For some reason yesterday it rebooted and now boots to a screen citing ( Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. " There is another small message on top , "Custom binary blocked by FRP. (boot.img). I did not change any OEM unlocking toggle. I'm the only one who uses the tablet so no one else did either. Any Ideas ? It does not let me boot to recovery, I cant turn the device off either it just keeps rebooting. The only screen i can get to successfully is download mode.
From some basic ideas I'm thinking maybe flash twrp again in odin and try to flash magisk again or the no-verity-opt-encrypt-6.0 file to see if it will boot up. I want to recover the device without formatting everything but if no one has nay ideas i guess I will try re-flashing the current firmware again to stock. I still have the odin files for the current firmware.
Don't panic, I had this too after upgrading the bootloader. I thougt it was soft-bricked...
- Flash a legit Samsung update with Odin
- The trick of the seven days (read further)
- Flash TWRP with Odin
- IMMEDIATELY reboot in recovery
If you use a custom ROM do as usual
- Delete DATA, wipe everything
- Flash custom ROM AND Magisk
If you want to keep Samsung OS and TWRP without Magisk, I believe you need to
- Flash a dm-verity patch.
Hope you have backup eveything as I did...
The option to disable OEM lock disappear from developper menu, even if it is activated. It seems you have to wait for seven days before the option show up again. During this time you're enable to use a custom ROM or a custom RECOVERY.
- Disable time by network
- Set date 8 days in the past
- Do a manual check update
- Reboot
- Set the actual date
- Check for updates again
Now the OEM option is present, now you can do what you want.
You're right but there's new security zip to flash together with dm-verity patch it is RMM bypass. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 .
Note: After flashing both files Data format is necessary not data wipe/factory reset.
I have similar security issues weeks back.
Tips?
samsuffit said:
Don't panic, I had this too after upgrading the bootloader. I thougt it was soft-bricked...
- Flash a legit Samsung update with Odin
- The trick of the seven days (read further)
- Flash TWRP with Odin
- IMMEDIATELY reboot in recovery
If you use a custom ROM do as usual
- Delete DATA, wipe everything
- Flash custom ROM AND Magisk
If you want to keep Samsung OS and TWRP without Magisk, I believe you need to
- Flash a dm-verity patch.
Hope you have backup eveything as I did...
The option to disable OEM lock disappear from developper menu, even if it is activated. It seems you have to wait for seven days before the option show up again. During this time you're enable to use a custom ROM or a custom RECOVERY.
- Disable time by network
- Set date 8 days in the past
- Do a manual check update
- Reboot
- Set the actual date
- Check for updates again
Now the OEM option is present, now you can do what you want.
Click to expand...
Click to collapse
Geoz said:
You're right but there's new security zip to flash together with dm-verity patch it is RMM bypass. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 .
Note: After flashing both files Data format is necessary not data wipe/factory reset.
I have similar security issues weeks back.
Click to expand...
Click to collapse
I still had the odin files from when i first rooted this. I flashed the same files ( BL, AP, HOME_CSC ). Device booted back up with all data intact but now the device is no longer rooted. Any way to root without losing data again ( Ex. Factory reset). I had to re-enable OEM Unlock even though i never disabled it don't know what happened there. Also device is still on Android 7.0
naruto.ninjakid said:
I still had the odin files from when i first rooted this. I flashed the same files ( BL, AP, HOME_CSC ). Device booted back up with all data intact but now the device is no longer rooted. Any way to root without losing data again ( Ex. Factory reset). I had to re-enable OEM Unlock even though i never disabled it don't know what happened there. Also device is still on Android 7.0
Click to expand...
Click to collapse
To root you may need to flash magisk with TWRP, I don't know if there's any other way.
If TWRP you have to format data after flashing security files so everything including internal storage will be wiped.
Is there any way to work root for galaxy a10s i tried all the methods and didn't work with me ... even the boot.img method via odin didn't work with me .... is there any other way ?????
Galaxy a10s Mediatek MT6762 Helio P22 (12 nm)
CPU Octa-core 2.0 GHz Cortex-A53
Any helps please
Good morming,
This link worked for me: https://www.full-repair-firmware.com/2019/10/how-to-root-a107m-9.0.html
Although I didn't use the BL from the (in my case TELCEL SM-A107M) firmware, I downloaded this Boot file (I don't remember from where ), it is for A107MUBU3ASI4:
https://mega.nz/#!tRgXgCTI!dHdQPB-MSQ7Znpm7d-Nme7lwwc_w2-im75putNHxgtM
SO I copied the boot file to the sdcard, ran magisk manager on the phone, selected patch boot image and selected the boot image on the sdcard for patching, after the patching is done, I copied the image back to the PC, started Odin, booted the phone to download mode (turn it off, connect the phone to the usb cable press power button to start the phone, then release the power button and press both volume buttons until it boots to download mode), then when Odin detected the phone I clicked the AP button on Odin, selected the patched boot file that I copied from the phone and then clicked on the Start button to flash the image, then when Odin finished, the phone booted automatically ... the tutorial says that the phone will ask for a factory reset and delete all the phone info, but in my case it didn't asked for nothing nor deleted my data, so I got root without losing information, as soon as the phone booted it was already rooted an root was working witout me having to do anything.
The first time I rooted my phone I installed xposed framework, then had some troubles with the beta version, got a bootloop and had to re-flash the original firmware, BUT when I tried to reflash the patched boot image I got the PreNormal message and had to wait a week to root again my phone .
So I googled and then found some info about the KG/RMM problem, but couldn't find a zip that worked for the SM-A107M, also since there is no TWRP available to this model, I wouldn't be able to flash the zip anyway, but I found that deleting this files:
libvkjni.so
libvkmanager.so
libvkservice.so
KnoxGuard.apk/Rlc.apk
will disable the service.
The first 3 are in the system/lib directory, the knoxGuard apk is in the priv-app/knoxGuard directory.
So I rooted the phone again (after waiting 7 day to prenormal to end) and in the first boot I
installed "Root Explorer" from the play store (Any file manager with root privileges will work) and deleted 4 of those files (the RLC.apk I couldn't find) and after 2 weeks of rebooting, reinstalling xposed, getting the bootloop problem again , re-flashing original firmware (without the KG/RMM prenormal state), re-rooting, and finally installing xposed without problems (in my phone the 4.6.0 beta version didn't work so I inistalled the 4.5.1 beta) I am happy with my rooted, xposed phone.
I would really like if somebody created/xported a TWRP for this model, but in the interim all is good the ends good.
Regards
:good: Thanks for the wonderful information .... But the problem I have is KGG / RM PRENORMAL STATE .... must do cancellation of the first ...
If you have already Prenormal state, then you have to wait 7 days, dont turn off your phone, don't restart and don't disconnect from the internet, then after the 7 days (168 hrs) the prenormal state should disappear!
Check this link:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Best Regards
I did not find prenormal state or normal.....
I found : KG status : checking
OEM unlock : off
Then, if not in prenormal, you should be able to flash and root your phone!
cheveguerra said:
Then, if not in prenormal, you should be able to flash and root your phone!
Click to expand...
Click to collapse
Good night
Unfortunately .... this root method did not work for me .... via Magisk ... I don't know what the problem is .... but this method did not work for me which is in many websites and it is the same way .... As follows my device info :
Ap: A107FXXU3ASJ5
CP: A107FXXU3ASJ1
CSC: A107FOJM3ASJ5
Model: sm- A107F / DS
The same method is used by everyone via Magisk ...
My device have no problem:
Unlocking the device bootloader
OEM unlock: off
Kg status: checking
I have no prenormal state
I followed all the steps on the sites
1- I downloaded Galaxy A10S Firmware
2- I downloaded and installed the latest Magisk Manager app.
3- Copied only the boot.img file from the extracted folder to a device storage.
4- opened the Magisk Manager app then clicked on on “Patch Boot Image File”.
5- when patched boot img finished from Magisk .... I renamed to boot.img and used 7zip and archived it to .tar format ....
6- I flashed via Odin in download mode but I got on fail .....
I don't know what problem ...
But this is what happened !!!!
Did you use the boot image (BL) I posted on the second post??
Download the file, copy it to your phone, use magisk manager to patch it, copy patched image to pc, flash via Odin to your phone.
Regards
No, I didn't use that boot img .... It the same : A107F .... A107M.. ???
I will try later.
I used that boot in your post .... for A107m.... l flashed via Odin in my A107F ... It's flashed in my device.... but when I boot to Magisk..... no root........ for that I think will wait someone to create twrp for galaxy A10s then I flash root.... Thanks for everything....
anybody with A107F firmware pls. i need to try to root mine.
raymihsenior said:
anybody with A107F firmware pls. i need to try to root mine.
Click to expand...
Click to collapse
You can go to sammobile there you can find it:good:
Try this for A107F
drive.google.com/file/d/1-5G6FDEzfT2oJ86aOneYGU1er7hbORIA/view?usp=drivesdk
DangVN said:
Try this for A107F
drive.google.com/file/d/1-5G6FDEzfT2oJ86aOneYGU1er7hbORIA/view?usp=drivesdk
Click to expand...
Click to collapse
....
This is TWRP 3.3.1.0 beta for galaxy A107F.... It's working????
.... Are you tested that ????
It is in img format and not in tar ... do we have to convert it to tar to flash it via odin?.
....
What do i need to do to make the oem unlock option appear again?
I've already tried the turning off updates and changing dates thing.
And I waited out the 7 days ( Which was difficult since my IP doesnt have a stable connection.)
I've started doubting if it even exists at all.
I only got my A10s for free from a carrier plan.
KG Status is Normal
OEM is still locked and nowhere to be seen
Helios007 said:
What do i need to do to make the oem unlock option appear again?
I've already tried the turning off updates and changing dates thing.
And I waited out the 7 days ( Which was difficult since my IP doesnt have a stable connection.)
I've started doubting if it even exists at all.
I only got my A10s for free from a carrier plan.
KG Status is Normal
OEM is still locked and nowhere to be seen
Click to expand...
Click to collapse
......
If you made all the attempts and didn't succeed with you ... Install the stock firmware for your country ... and you delay the date a few months earlier ... then go to update the program .... then you should have an OEM unlock
Hastoma said:
......
If you made all the attempts and didn't succeed with you ... Install the stock firmware for your country ... and you delay the date a few months earlier ... then go to update the program .... then you should have an OEM unlock
Click to expand...
Click to collapse
And how does one Install a "different/new" firmware?
I remember doing it once or twice with Odin with a firmware I got from sammobile SMA-107f.
Succeeded. Although I don't know if it actually worked, since it booted up just like the first time I got it, with the carriers default wallpaper and pre-loaded apps.
I've been trying to root the SM-A107F for weeks now but no luck.. Any help will be appreciated
cheveguerra said:
Good morming,
This link worked for me: https://www.full-repair-firmware.com/2019/10/how-to-root-a107m-9.0.html
Although I didn't use the BL from the (in my case TELCEL SM-A107M) firmware, I downloaded this Boot file (I don't remember from where ), it is for A107MUBU3ASI4:
https://mega.nz/#!tRgXgCTI!dHdQPB-MSQ7Znpm7d-Nme7lwwc_w2-im75putNHxgtM
SO I copied the boot file to the sdcard, ran magisk manager on the phone, selected patch boot image and selected the boot image on the sdcard for patching, after the patching is done, I copied the image back to the PC, started Odin, booted the phone to download mode (turn it off, connect the phone to the usb cable press power button to start the phone, then release the power button and press both volume buttons until it boots to download mode), then when Odin detected the phone I clicked the AP button on Odin, selected the patched boot file that I copied from the phone and then clicked on the Start button to flash the image, then when Odin finished, the phone booted automatically ... the tutorial says that the phone will ask for a factory reset and delete all the phone info, but in my case it didn't asked for nothing nor deleted my data, so I got root without losing information, as soon as the phone booted it was already rooted an root was working witout me having to do anything.
The first time I rooted my phone I installed xposed framework, then had some troubles with the beta version, got a bootloop and had to re-flash the original firmware, BUT when I tried to reflash the patched boot image I got the PreNormal message and had to wait a week to root again my phone .
So I googled and then found some info about the KG/RMM problem, but couldn't find a zip that worked for the SM-A107M, also since there is no TWRP available to this model, I wouldn't be able to flash the zip anyway, but I found that deleting this files:
libvkjni.so
libvkmanager.so
libvkservice.so
KnoxGuard.apk/Rlc.apk
will disable the service.
The first 3 are in the system/lib directory, the knoxGuard apk is in the priv-app/knoxGuard directory.
So I rooted the phone again (after waiting 7 day to prenormal to end) and in the first boot I
installed "Root Explorer" from the play store (Any file manager with root privileges will work) and deleted 4 of those files (the RLC.apk I couldn't find) and after 2 weeks of rebooting, reinstalling xposed, getting the bootloop problem again , re-flashing original firmware (without the KG/RMM prenormal state), re-rooting, and finally installing xposed without problems (in my phone the 4.6.0 beta version didn't work so I inistalled the 4.5.1 beta) I am happy with my rooted, xposed phone.
I would really like if somebody created/xported a TWRP for this model, but in the interim all is good the ends good.
Regards
Click to expand...
Click to collapse
This is very interesting. KG State has been non existent on my device, I can flash modified firmware since day 1. I'll try this, I tried patching the whole AP_ file and there are problems with the signal, I did not try only patching the boot.img
Thanks!
ShaDisNX255 said:
This is very interesting. KG State has been non existent on my device, I can flash modified firmware since day 1. I'll try this, I tried patching the whole AP_ file and there are problems with the signal, I did not try only patching the boot.img
Thanks!
Click to expand...
Click to collapse
when you flash the patched AP.tar you should also be flashing it with the rest of the firmware.. tjw even says somewhere on his github you shouldnt flash the patched AP by itself
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
If anyone can help that'll be great!
Phone Info:
Android Version: 10
Baseband Version: J600GDXSACVB1
Knox version: Knox 3.5 (idk if this is needed)
"OEM Unlocking" option in developer setting is enabled
"USB Debugging" is also enabled
ThatUnknownDude said:
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
Click to expand...
Click to collapse
TWRP =/= root. Root means you have SU access in Android system. Recovery mode is a separate environment; the difference between TWRP and stock recovery is that TWRP allows you to flash unsigned images.
If you just want to root your phone with Magisk, you can follow these instructions.
Otherwise, if you want to be able to flash custom ROMs, you can use this to patch your stock recovery to enable Fastbootd which will allow you to flash partitions directly instead of using Odin.
ThatUnknownDude said:
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
Click to expand...
Click to collapse
Yes, see the Magisk instructions I linked. Samsung likes to make things complicated, so when you've unlocked the bootloader, it still won't let you flash custom images until Vaultkeeper has been disabled.
Hmm ok thanks.. I saw the Magisk installation help page and I am getting stuck in this part:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Click to expand...
Click to collapse
I am long pressing volume up button in download mode however nothing is happening...
(Edit) Oh and KG State (which I assume is another word for RMM Lock) is just showing 'checking' and not 'prenormal' or anything...
I think TWRP may be the cause of the bootloop. I flashed a stock firmware of J600G to completely reset it (factory reset of sorts) and then flashed TWRP, and entered the recovery screen. After that the bootlooping issue started... is there any other good custom recoveries?
Hi TUD, fellow J600G user here, I'd recommend you to start off easy by installing TWRP 3.2.3.
Requirements -
Odin installed on your computer.
USB cable
TWRP tar file
To install TWRP -
1. Switch your phone off and hold volume up and down buttons at the same time while connecting your phone to the computer by cable.
2. Open Odin and go to options, switch off auto reboot, now click on AP and select your TWRP tar file.
3. Now after Odin says PASS disconnect the cable from your phone and hold Volume down + power button for 7 seconds and as soon as the screen goes black hold Volume up + power button. This will boot you into your newly installed TWRP.
When it comes to custom roms J6 has some limitations for a few good ones. In my opinion you can install EvolutionX 4.0 (made by @adi_ss) that is based on android 10 as its the easiest rom to install. All you have to do is follow the instructions given by the developer.
Happy Flashing.