Hello guys,
Just got my m9 a few hours ago, decided to root,s-off etc
Anyway, I did something stupid and Im stuck on the android logo.
Here is what I did.
-I updated the device through the stock recovery, there was another update but I didnt install i.
- unlocked the bootloader, phone rebooted and was working fine
-installed costume recovery(TWRP), I didnt boot into it because there wasnt and option like in the m8 to boot in recovery from bootloader.
-I reset the device and installed the update(stupid move I knew the stock recovery is not there)
- I got into TWRP and the updated failed so I had the SUbinary.zip so I plashed it and decided to reboot
-Here I got a note that theres no OS installed so I installed android Revolution, I placed it in the sdcard prior
- after flashing it I pressed on reboot yet I get no OS installed and now im stuck on the HTC logo.
BTW I can boot into boot loader but it says sd card not mounted (64GB)
Edit:
I entered into recovery, flashed AR again,its installs everything normally but I realized on the installation log last line : set_metadata_recursive: some changes failed
still I get no OS installed
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
mr.dj26 said:
Hello guys,
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
Click to expand...
Click to collapse
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
x51 said:
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
Click to expand...
Click to collapse
hey there, thanks for the reply.
I think ill do the s-off first then ill download the RUU like this guy http://forum.xda-developers.com/one-m9/help/tut-ota-successfully-1-32-401-15-to-1-t3091911
i wish i updated before
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
thunderwolf333 said:
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
Click to expand...
Click to collapse
Thats good to hear, sometimes TWRP will say that there isn't any OS installed but actually there is just reboot the device.
After updating through the OTA I installed ARHD and I got the same error again with the latest recovery. I think its because when I did wipe the data there root directory is changing make the phone unable to boot or there is a problem with the rom although it flashed before the update.
Here is a fix http://forum.xda-developers.com/one...h-recovery-t3066720/post59934542#post59934542
If it didn't work try to format data in the recovery and reboot. Make sure you have a ROM or back up on an SD card.
Since your phone is running I would suggest you to S-off because from what I understand is RUU (for Europe) will only work with S-off
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
hope this helps others
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
Rooting in MM includes flashing modified boot.img (modified kernel). I guess that's what you are missing. There is the modified boot.img for root in MM dev edition thread or I can recommend you the flar2 elementalX 6.0.2 kernel that I am using right now and is far better on battery life/performance vs the stock one. Cheers!
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
TheEarman said:
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
Click to expand...
Click to collapse
let us know what the outcome is. Been looking for a thread on rooting unlocked/dev edition and was unable to find any
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
I was able to root properly, with proper binaries, by using the method described here (I was missing the boot.img flashing step, as indicated by High_voltage): http://forum.xda-developers.com/htc-one-m8/development/kernel-unlocked-developer-edition-t3262823. Problem solved. Thanks!
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
jshamlet said:
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
Click to expand...
Click to collapse
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
ckpv5 said:
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
Click to expand...
Click to collapse
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot. While those were for the gpe version i shouldn't think it matters.
Your suggesting its possible without modifying the boot.img? If so are there any repercussions vs using a patched boot.img?
ShinAkira00 said:
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot.
Click to expand...
Click to collapse
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
redpoint73 said:
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
Click to expand...
Click to collapse
cool, thanks for clarifying.
Hey guys I had a couple questions regarding rooting the opportunity Find 7a. First off I have ColorOS v 2.1.5i and everytime I try to install TWRP onto it nothing happens, even though the computer says it has been flashed successfully. I restart my phone into recovery mode and the oppo recovery is still there. You guys have any ideas?
Also when I had the older version of colorOS, I could install TWRP but then SuperSU would never work. It kept saying the binaries weren't installed properly. Any ideas on that ?
Your guys help would be appreciated since I really wna root this phone
Thanks
Try fastboot boot nameofrecovery.img it should boot directly into twrp then
I couldn't root my phone in Color Os 2.0.8i untill i reflashed the rom and installed latest twrp then it asked me for root and i pressed ok.
Yea I tried what jthatch12 told me do and it worked and superSu finally installed properly
Installed trwp and flashed multiple times my wileyfox swift to lineage 14.1
Swift wont boot gets stuck in bootloader....
Found a 14.0 image (linage) somewhere.... this works with no problems but seems an older built (buggy)
Anyone has 14.1 lineage on a swift with no problems ???
You can try installing Lineage 14.1. from CM13, see posts #155/#156 in thread 'Nightly 14.1 lineageOS Rom For Crackling'
went back to cyanogen the original firmware
Found the original firmware and twrp flashed back to that one...
https://forum.xda-developers.com/showpost.php?p=70510585&postcount=19
Old firmware but was happy with that one so.... problem solved....
Same bootloop on Wileyfox Swift, how did you...
...install the old COS on your Swift?
I downloaded all the files from G4liant's MEGA cloud storage but don't know how to continue.
Please, help if you can (see my reply to his post, too (as of today 25. June 2017)).
Thanks!
jwalesch
__________________________________________________________________________
eskodisk said:
Found the original firmware and twrp flashed back to that one...
https://forum.xda-developers.com/showpost.php?p=70510585&postcount=19
Old firmware but was happy with that one so.... problem solved....
Click to expand...
Click to collapse
original firmware
jwalesch said:
...install the old COS on your Swift?
I downloaded all the files from G4liant's MEGA cloud storage but don't know how to continue.
Please, help if you can (see my reply to his post, too (as of today 25. June 2017)).
Thanks!
jwalesch
__________________________________________________________________________
Click to expand...
Click to collapse
Do you have TWRP recovery installed on your wileyfox ?
Via the twrp recovery, you can install what is in one of the zipfiles
I guess this one :
cm-13.1.2-ZNH2KAS3LG-crackling-signed-42f2b8e414.zip
MD5: 0AEF4E4A468EF34A6DA65712156ECB2C
contains the twrp installable original firmware....
Installing works the same as you would eg install a lineage custom rom.... TWRP is rather fool proof... I tried to install some of the other files, in the other zipfiles and twrp just refused... so ... try.... no need to install google apps here, everything is in the image... As you will see in the filesize of het image, it is rather big, compared to the lineage custom roms... Everthing is there....
If you are so far... Let me know, i learned that you will have to disable the wileyfox to keep looking for updates, wileyfox will download over and over again the upgrade files, was kind of annoying...
TWRP recovery cannot be loaded on Wileyfox Swift
Hi!
I had TWRP installed, in fact in different versions.
But for whatever reason I cannot boot into TWRP anymore which is precisely one of the problems I'm having now that I wanted to flash the Lineage OS again on a second Swift (I might have erased the partition that I installed TWRP to). But I cannot install TWRP again either...
All I can reach is the bootloader which does give you an option to restart recovery but it doesn't work. The phone is stuck in a bootloop returning whatever you do to the bootloader.
So, I hoped to find some help in treating the phone to a new or its original bootloader...
Thanks for helping!
jwalesch
__________________________________________________________________________
eskodisk said:
Do you have TWRP recovery installed on your wileyfox ?
Via the twrp recovery, you can install what is in one of the zipfiles
I guess this one :
cm-13.1.2-ZNH2KAS3LG-crackling-signed-42f2b8e414.zip
MD5: 0AEF4E4A468EF34A6DA65712156ECB2C
contains the twrp installable original firmware....
Installing works the same as you would eg install a lineage custom rom.... TWRP is rather fool proof... I tried to install some of the other files, in the other zipfiles and twrp just refused... so ... try.... no need to install google apps here, everything is in the image... As you will see in the filesize of het image, it is rather big, compared to the lineage custom roms... Everthing is there....
If you are so far... Let me know, i learned that you will have to disable the wileyfox to keep looking for updates, wileyfox will download over and over again the upgrade files, was kind of annoying...
Click to expand...
Click to collapse
I have found a way to install TWRP (different versions) but didn't know how to start it.
In this post I found how to:
https://forum.xda-developers.com/wileyfox-swift/help/foolproof-twrp-guide-wileyfox-swift-t3616571
It's keeping the volume down button held down until TWRP starts, then you can do everything from there.
Everything?
I installed Lineage OS 14.1 (nightly as of 2017/06/19) as well as GApps, wiped Cache/DALVIK and restarted the system.
The OS wouldn't start, only the bootloader could I get the phone to start.
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
jwalesch said:
Hi!
I had TWRP installed, in fact in different versions.
But for whatever reason I cannot boot into TWRP anymore which is precisely one of the problems I'm having now that I wanted to flash the Lineage OS again on a second Swift (I might have erased the partition that I installed TWRP to). But I cannot install TWRP again either...
All I can reach is the bootloader which does give you an option to restart recovery but it doesn't work. The phone is stuck in a bootloop returning whatever you do to the bootloader.
So, I hoped to find some help in treating the phone to a new or its original bootloader...
Thanks for helping!
jwalesch
__________________________________________________________________________
Click to expand...
Click to collapse
jwalesch said:
[...]
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
Click to expand...
Click to collapse
Try installing the system and the GApps separately:
Wipe again, install system, then boot to system, when Lineage has successfully booted for the first time (may take a couple of minutes), go back to TWRP and install GApps.
jwalesch said:
I have found a way to install TWRP (different versions) but didn't know how to start it.
In this post I found how to:
https://forum.xda-developers.com/wileyfox-swift/help/foolproof-twrp-guide-wileyfox-swift-t3616571
It's keeping the volume down button held down until TWRP starts, then you can do everything from there.
Everything?
I installed Lineage OS 14.1 (nightly as of 2017/06/19) as well as GApps, wiped Cache/DALVIK and restarted the system.
The OS wouldn't start, only the bootloader could I get the phone to start.
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
Click to expand...
Click to collapse
I had the same problem with lineage.... only bootloader when powering on.... That is the reason why I went back to the original firmware because that solved my problem.... I once found an older lineage rom suggested somewhere on the forum that worked and got me out of the bootloader but that version was buggy... Updating from there to a the latest linage got me back to the bootloader only problem....
I will stay on the cyonogenmod now.... Until perhaps someone can tell me how to really solve the bootloader only by power up problem....
eskodisk said:
[...]
I will stay on the cyonogenmod now.... Until perhaps someone can tell me how to really solve the bootloader only by power up problem....
Click to expand...
Click to collapse
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
total backup of existing system ?
kabu83 said:
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
Click to expand...
Click to collapse
Can i backup my existing system in twrp... I tried lineage a dozen times before and always got stuck on bootloader. So can I backup my current setup because at the moment everything works as it should.... ????? I formatted my sd card as system memory so... ????
If TWPR is running and you can mount the system partition, you should be able to make a back-up via TWRP. (Not of your pictures, music and so on, see TWRP disclaimer.)
Install LineageOS from a running cm-13.1.2-ZNH2KAS3LG-crackling
Hi there!
Yes, my Wileyfox Swift is running the CyanogenMOD version cm-13.1.2-ZNH2KAS3LG-crackling.
Everything seems to be OK, it just wants to keep downloading an update which I can save but when I'm asked to install it the normally automatic installation process doesn't work:
The phone reboots back to TWRP but doesn't show the just downloaded .zip file (which normally would happen) and doesn't install it either. Installation stops in TWRP, when I tap on REBOOT > SYSTEM the OS reboots normally but shows the OS version I had before.
Can you tell me where these update .zip files are saved so that I could install it maybe from the TWRP's file manager?
If that doesn't work I would try to update TWRP and after that install the current Lineage OS over the CM 13.1.2 as you suggested.
Thanks for helping!
jwalesch
________________________________________________________________________________________________
kabu83 said:
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
Click to expand...
Click to collapse
jwalesch said:
Hi there!
Yes, my Wileyfox Swift is running the CyanogenMOD version cm-13.1.2-ZNH2KAS3LG-crackling.
Everything seems to be OK, it just wants to keep downloading an update which I can save but when I'm asked to install it the normally automatic installation process doesn't work:
The phone reboots back to TWRP but doesn't show the just downloaded .zip file (which normally would happen) and doesn't install it either. Installation stops in TWRP, when I tap on REBOOT > SYSTEM the OS reboots normally but shows the OS version I had before.
Can you tell me where these update .zip files are saved so that I could install it maybe from the TWRP's file manager?
If that doesn't work I would try to update TWRP and after that install the current Lineage OS over the CM 13.1.2 as you suggested.
Thanks for helping!
jwalesch
________________________________________________________________________________________________
Click to expand...
Click to collapse
What update does it want to keep downloading? I guess it might be the official stock 7.1.1..
You probably need to download the Lineage.zip manually from official Lineage downloads.
Then restart to TWRP and install the Lineage.zip.
TWRP has a toggle button in the lower left corner, where you can switch from 'Install image' to 'Install zip'. With 'install zip', you should find the zip.
The update is cm-13.1.2-ZNH2KAS7EB-crackling.
I have it ready to be installed on the phone but it won't show in any filemanager, be it in TWRP nor the system's filemanager nor AMAZE filemanager which I also installed.
So, I assume the download either isn't actually saved properly or it's a hidden file or something of that sort.
In other threads they say that updates were saved to a folder called "cmupdater". I cannot find any folder with that name either.
I also have the latest LineageOS .zip file ready to be installed on my phone and have tried to install that from TWRP (by the way: Now running the latest version for the Wileyfox Swift, ie. twrp-3.1.1-0-crackling). All it does is it produces an error saying something like "Error 7... cannot be installed".
SOLVED for now:
From here https://cyanogenupdatetracker.com/downloads/ I downloaded the latest available CM version (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip) which seemed to be exactly the one that my phone kept downloading and couldn't install.
I copied it to my external sd card and installed it from there via TWRP.
After that the system rebooted normally, Android then updated all my installed apps and now the system is downloading yet another update:
Android 7.1.1 (Nougat) - TOS111B
As I know that version of Android on the Wileyfox it's not actually something I would want to install myself. But I shall try to install the latest Lineage OS instead.
Let's keep each other posted (in German?)!
___________________________________________________________________________________________________
kabu83 said:
What update does it want to keep downloading? I guess it might be the official stock 7.1.1..
You probably need to download the Lineage.zip manually from official Lineage downloads.
Then restart to TWRP and install the Lineage.zip.
TWRP has a toggle button in the lower left corner, where you can switch from 'Install image' to 'Install zip'. With 'install zip', you should find the zip.
Click to expand...
Click to collapse
jwalesch said:
The update is cm-13.1.2-ZNH2KAS7EB-crackling.
I have it ready to be installed on the phone but it won't show in any filemanager, be it in TWRP nor the system's filemanager nor AMAZE filemanager which I also installed.
So, I assume the download either isn't actually saved properly or it's a hidden file or something of that sort.
In other threads they say that updates were saved to a folder called "cmupdater". I cannot find any folder with that name either.
I also have the latest LineageOS .zip file ready to be installed on my phone and have tried to install that from TWRP (by the way: Now running the latest version for the Wileyfox Swift, ie. twrp-3.1.1-0-crackling). All it does is it produces an error saying something like "Error 7... cannot be installed".
SOLVED for now:
From here https://cyanogenupdatetracker.com/downloads/ I downloaded the latest available CM version (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip) which seemed to be exactly the one that my phone kept downloading and couldn't install.
I copied it to my external sd card and installed it from there via TWRP.
After that the system rebooted normally, Android then updated all my installed apps and now the system is downloading yet another update:
Android 7.1.1 (Nougat) - TOS111B
As I know that version of Android on the Wileyfox it's not actually something I would want to install myself. But I shall try to install the latest Lineage OS instead.
Let's keep each other posted (in German?)!
___________________________________________________________________________________________________
Click to expand...
Click to collapse
English is forum language I guess, you could probably send me a private message to clarify anything in German.
I also had the error 7 issue when installing Lineage, you need to wipe system (you will loose everything though, it is not possible to install Lineage over Cyanogen, like a dirty flash).
In TWRP, choose Wipe/advanced Wipe/ tick system only / repair, 2F2S. After that, format data.
Then the installation of Lineage with TWRP should run through. Let the system boot for the first time, if it runs, boot back to TWRP and install GApps.
With that method, I am on LOS nigthly 20170626 now and happy.
Hi kabu83!
Thanks a lot for your last reply - it helped me to finally get Lineage OS 14.1 installed!
At the moment the phone is rebooting the system after installing the GApps, everything seems to run smoothly and - guess what - I'm happy, too, now!
How about sending me a PM? (As I have no clue as to how that works it would be nice if you could send me that one more reply to let me know.)
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
As far as i know, trying to root stock rom isn't easy. I could be wrong but idk. You can try by:
1. Flashing stock
2. Flashing TWRP
3. Format data
4. Flash DM-Verity and Disable Force-Encrypt then flash magisk.
And i think you can't flash kernels on stock. I could be wrong but idk.
Hey, how did you even install TWRP?
Before I tried installing it my model number was "SM-J600 FN/DS" and now after the install, when I plug it into my pc it says that it's "FN-600G." Whenever I try to boot it in system mode it's stuck in a loop.
I haven't tried flashing the newest firmware yet because I can't even download it for my country.
Sorry, I am a total newbie and can't seem to fix it.
Al-Ameen Adewunmi said:
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
Click to expand...
Click to collapse
Hi Guys,
Did you manage to do this? I was experiencing the same bootloop issue and I think it is the version of Twrp (I was using 3.3.1-0).
I used Odin to flash a lower version 3.2.3 found here after which I flashed this DM Verity + Magisk.
Root Success!