Related
So I rooted my tablet and flashed it with twrp. But it was a long time ago that I did that. And rit running on Android 4.4.2. But to day I wanted to update it to android 5.0. It gave me an error and it said that I had to try downloading the update with keis and I did. Everything was going smoothly until it rebooted and now I'm stuck on bootloop with no backup. When I tried to boot into recovery I gave me the original samsung recovery can anyone help with this fix
MadMac19 said:
So I rooted my tablet and flashed it with twrp. But it was a long time ago that I did that. And rit running on Android 4.4.2. But to day I wanted to update it to android 5.0. It gave me an error and it said that I had to try downloading the update with keis and I did. Everything was going smoothly until it rebooted and now I'm stuck on bootloop with no backup. When I tried to boot into recovery I gave me the original samsung recovery can anyone help with this fix
Click to expand...
Click to collapse
Don't use Kies, it is literally awful. Use one of the SM-T530NU firmware files from this thread and flash it with Odin v3.10 (I would recommend factory resetting in stock recovery before you use Odin). Then you can root again using TWRP, just follow this method
Note: I have the exact same model as you and everything I just said worked fine for my tablet.
Thank you
thisisapoorusernamechoice said:
Don't use Kies, it is literally awful. Use one of the SM-T530NU firmware files from this thread and flash it with Odin v3.10 (I would recommend factory resetting in stock recovery before you use Odin). Then you can root again using TWRP, just follow this method
Note: I have the exact same model as you and everything I just said worked fine for my tablet.
Click to expand...
Click to collapse
one quick question is Factory Reset the same as data wipe with recovery
MadMac19 said:
one quick question is Factory Reset the same as data wipe with recovery
Click to expand...
Click to collapse
Correct
thisisapoorusernamechoice said:
Correct
Click to expand...
Click to collapse
thanks it worked
thisisapoorusernamechoice said:
Correct
Click to expand...
Click to collapse
is there any good Rom for my device like CM-12.1
MadMac19 said:
is there any good Rom for my device like CM-12.1
Click to expand...
Click to collapse
Go to the development section and check out either BlissPop or Resurrection remix. Both are based off CM12.1. The versions made for the SM-T530 work on our SM-T530NU. I use BlissPop, it's great.
Update: Links, BlissPop and Resurrection Remix. Use TK Gapps (either nano or micro) or jajb's minimal gapps, and whichever you use you might want to check out the debloat script on the minimal gapps thread
Hi guys.
First of all sorry if this question is asked before. But i habe tried every method to fix this issue reading other threads.
Today i tried rooting my s7 edge sm-g935fd (indian version) first using cf-autoroot method and then using this method <URL>http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 </URL>.
I followed each and every step properly and also tried two-three times. But after rebooting the phone (first boot) it always gets stucked at Samsung Logo. I have let the phone sit alone for more than 2-3 hours every time but phone is not booting up.
Also tried to flash no-verity-opt-encrypt (as mentioned in 2nd thread point no 11) but its not booting up. Also did format dat when booted recovery for the first time.
Do i have to unroot and flash the stock indian firmware and start the root again? But for that i need to have that SECURE STARTUP THING and for which i have to boot into my phone .
So plz guys tell me how to fix this issue? I dont have that secure start up pin for unrooting.
Things i used:
Odin 3.12.3, 3.10.6
CF-autoroot for hero2lte
Twrp -3.0.2-2
Thanks for your help.
The step you're missing here is your phone is encrypted (i did the same thing)... Flash TWRP and go to Wipe then hit the advanced button. You will have to type "yes" and TWRP will wipe the entire partition and rebuild it without encryption. You can then flash any ROM with TWRP and then flash dm-verity, and not get the secure verify issue.
dude9946 said:
The step you're missing here is your phone is encrypted (i did the same thing)... Flash TWRP and go to Wipe then hit the advanced button. You will have to type "yes" and TWRP will wipe the entire partition and rebuild it without encryption. You can then flash any ROM with TWRP and then flash dm-verity, and not get the secure verify issue.
Click to expand...
Click to collapse
Thanks dude for your reply. But as i mentioned i did FORMAT DATA and clicked typed YES when i booted recovery for the first time after flashing it with odin. Also i did swipe to allow modifications when i was asked in recovery.
In the settings > developers options did you allow or tick OEM unlock?
Sent from my SM-G935F using XDA-Developers mobile app
blu3angel said:
In the settings > developers options did you allow or tick OEM unlock?
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for your reply. Yes i ticked both oem unlock and usb debugging.
If you used the proper cf root for your phone it should of worked.
the second method is not for the S7 edge. which is stated very clearly like this
Do not flash on S7 Edge or Qualcomm models!
Click to expand...
Click to collapse
I believe the only way to fix this is to download the Samsung drivers to your computer and use recovery on smart switch device initialization to restore your phone to original. To use device initialization you need to know the model of your phone (which you have) and the serial number which you should be able find from the box the phone came in.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Cosmic Blue said:
If you used the proper cf root for your phone it should of worked.
the second method is not for the S7 edge. which is stated very clearly like this
Do not flash on S7 Edge or Qualcomm models!
Click to expand...
Click to collapse
I believe the only way to fix this is to download the Samsung drivers to your computer and use recovery on smart switch device initialization to restore your phone to original. To use device initialization you need to know the model of your phone (which you have) and the serial number which you should be able find from the box the phone came in.
Click to expand...
Click to collapse
Oops i actually did not read that it does not work on s7 edge. But in the youtube video by max lee it was mentioned that the method works on s7/s7 edge exynos versions.
Edit: there is a same method for s7 edge also. Here is the link. http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Can you provide me the link for rooting s7 edge with cf-auto root and also step by step procedure to do so.
And also provide me the link for indian firmware for s7 edge. The one memtioned in one thread is corrupt.
Thanking you.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
first get your phone restored using the smart switch method, that will put the correct uncorrupted firmware for your region.
then we willl talk about rooting. As long as you are in a boot loop on an unrooted phone very little can be done,
Cosmic Blue said:
first get your phone restored using the smart switch method, that will put the correct uncorrupted firmware for your region.
then we willl talk about rooting. As long as you are in a boot loop on an unrooted phone very little can be done,
Click to expand...
Click to collapse
Done with restoring can you tell now what i have to do to root?
Done rooting. But not cannot install xposed
I did the rooting by first using cf auto root and then flashing twrp. But when i flashed xposed v86 sdk23 from twrp the phone is again stucked at samsung logo. Cant get over it from last 1 hour. Is there any fix for it?
You need to flash the wanam custom build xposed version not the regular xposed..
jayas.mayank said:
I did the rooting by first using cf auto root and then flashing twrp. But when i flashed xposed v86 sdk23 from twrp the phone is again stucked at samsung logo. Cant get over it from last 1 hour. Is there any fix for it?
Click to expand...
Click to collapse
can you get into twrp, if yes then do a factory restore to remove xposed from your phone.
if you cannot get into twrp you will need to use smart switch again.
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.
Hi,
I have a S8+, SM-G955F and I cannot have Android Oreo and TWRP (and then root). I only can have Android 7 and TWRP (and then root).
Current situation is: I have Android Oreo, Build G955FXXU1CRB7 is installed. Once I go to Download Mode and flash TWRP, I can boot into TWRP, but my device is not booting into Android anymore. It starts up, shows me the Samsung logo and reboots, then it shows samsung logo again and reboots.
It reboots and reboot and reboots...If I go to TWRP and make a factory reset or format data, it does not help, it only reboots when trying to start Android.
Even if I restore an older backup of boot, systems partition, it does not work...
So what do I do? I flash original Android Oreo firmware once again via Odin and get it back working, but: I loose TWRP again (and cannot flash SuperSU).
Any idea? I would like to have latest Oreo as well as TWRP recovery
Many thanks!
tobyffm said:
Hi,
I have a S8+, SM-G955F and I cannot have Android Oreo and TWRP (and then root). I only can have Android 7 and TWRP (and then root).
Current situation is: I have Android Oreo, Build G955FXXU1CRB7 is installed. Once I go to Download Mode and flash TWRP, I can boot into TWRP, but my device is not booting into Android anymore. It starts up, shows me the Samsung logo and reboots, then it shows samsung logo again and reboots.
It reboots and reboot and reboots...If I go to TWRP and make a factory reset or format data, it does not help, it only reboots when trying to start Android.
Even if I restore an older backup of boot, systems partition, it does not work...
So what do I do? I flash original Android Oreo firmware once again via Odin and get it back working, but: I loose TWRP again (and cannot flash SuperSU).
Any idea? I would like to have latest Oreo as well as TWRP recovery
Many thanks!
Click to expand...
Click to collapse
Hello, which instructions did you follow to flash again the firmware? ( i assume the firmware was the official )
StonebridgeGr said:
Hello, which instructions did you follow to flash again the firmware? ( i assume the firmware was the official )
Click to expand...
Click to collapse
Yes, it was the official one. Just searched the site, but cannot find it anymore. However, flashing the firmware does not need many steps. DOwnload the zip, extract the .tar files in it, open ODIN, load .tar files into Odin and click flash. Then it was flashed and Android was booting again.
tobyffm said:
Yes, it was the official one. Just searched the site, but cannot find it anymore. However, flashing the firmware does not need many steps. DOwnload the zip, extract the .tar files in it, open ODIN, load .tar files into Odin and click flash. Then it was flashed and Android was booting again.
Click to expand...
Click to collapse
you are right, when you flashed the official firmware, on odin did you select the Home_CSC or the CSC ?
StonebridgeGr said:
you are right, when you flashed the official firmware, on odin did you select the Home_CSC or the CSC ?
Click to expand...
Click to collapse
I think it was the CSC, but as far as I remember, I also tried the HOME_CSC in the past (not today) but the behaviour was also the same.
As far as I know difference is that with one of these files internal storage is wiped, with the other one it isn't, correct?
But what could this have to do that I get a restart-loop when flashing TWRP? I dont have a problem to flash original firmware, it works. But once I flash TWRP I cannot start Android anymore and have to reflash Android firmware again.
tobyffm said:
I think it was the CSC, but as far as I remember, I also tried the HOME_CSC in the past (not today) but the behaviour was also the same.
As far as I know difference is that with one of these files internal storage is wiped, with the other one it isn't, correct?
But what could this have to do that I get a restart-loop when flashing TWRP? I dont have a problem to flash original firmware, it works. But once I flash TWRP I cannot start Android anymore and have to reflash Android firmware again.
Click to expand...
Click to collapse
which guide did you follow to flash TWRP?
also yes the CSC not the HOME CSC wipes the internal storage
StonebridgeGr said:
which guide did you follow to flash TWRP?
also yes the CSC not the HOME CSC wipes the internal storage
Click to expand...
Click to collapse
I followed this guide: https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But also not much to follow...Download correct TWRP for S8+, load into Odin and click flash. TWRP is correct version and it works for me. But at same time, phone is not booting into Android anymore. This is why I end in reflashing original Android firmware again. I am in a loop :silly:
tobyffm said:
I followed this guide: https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But also not much to follow...Download correct TWRP for S8+, load into Odin and click flash. TWRP is correct version and it works for me. But at same time, phone is not booting into Android anymore. This is why I end in reflashing original Android firmware again. I am in a loop :silly:
Click to expand...
Click to collapse
Dude thats guide to flash and root S8 not S8+.. thats why you get bootloop, make sure to follow the correct guide next time
Here is the best guide i found for you https://www.androidinfotech.com/2018/02/root-samsung-galaxy-s8-plus-sm-g955f-oreo.html
StonebridgeGr said:
Dude thats guide to flash and root S8 not S8+.. thats why you get bootloop, make sure to follow the correct guide next time
Here is the best guide i found for you https://droidfeats.com/root-galaxy-s8-plus-variants-android-8-0-oreo-cf-auto-root/
Click to expand...
Click to collapse
thanks, but I dont think so.
From the thread I mentioned, yes, I can download TWRP for S8, not S8+, but I went to TWRP site and downloaded correct TWRP for my device. Loading into odin and flash is the same, doesnt matter which device I have.
CF Autoroot does not work for me as it is not available for Oreo firmware. I checked all this previously, I am not a that stupid guy :laugh:
tobyffm said:
thanks, but I dont think so.
From the thread I mentioned, yes, I can download TWRP for S8, not S8+, but I went to TWRP site and downloaded correct TWRP for my device. Loading into odin and flash is the same, doesnt matter which device I have.
CF Autoroot does not work for me as it is not available for Oreo firmware. I checked all this previously, I am not a that stupid guy :laugh:
Click to expand...
Click to collapse
then follow this guide, i am sure you did a wrong on the instructions, follow then without stress and do not rush . I never said you a stupid guy
https://androidjungles.com/root-samsung-galaxy-s8-plus-install-twrp-recovery-android-oreo-sm-g955f/
Download this TWRP image for your S8PLUS(twrp-3.2.1-0-dream2lte.img.tar 38.2M 2017-12-09 03:01:59 ES)
https://dl.twrp.me/dream2lte/
StonebridgeGr said:
then follow this guide, i am sure you did a wrong on the instructions, follow then without stress and do not rush . I never said you a stupid guy
https://androidjungles.com/root-samsung-galaxy-s8-plus-install-twrp-recovery-android-oreo-sm-g955f/
Download this TWRP image for your S8PLUS(twrp-3.2.1-0-dream2lte.img.tar 38.2M 2017-12-09 03:01:59 ES)
https://dl.twrp.me/dream2lte/
Click to expand...
Click to collapse
I used exactly that TWRP version today.
The only difference between my steps and the steps mentioned in your mentioned guide is that they use an older Odin version. But I already used different Odin version too
Ok, aynway, I will try it again with this guide tomorrow and will let you know about the result tomorrow. Thx so far
tobyffm said:
I used exactly that TWRP version today.
The only difference between my steps and the steps mentioned in your mentioned guide is that they use an older Odin version. But I already used different Odin version too
Ok, aynway, I will try it again with this guide tomorrow and will let you know about the result tomorrow. Thx so far
Click to expand...
Click to collapse
alright i will be waiting for you reply to my post here !!
StonebridgeGr said:
alright i will be waiting for you reply to my post here !!
Click to expand...
Click to collapse
Hi again,
I got an OTA Update this morning, so current build on phone was G955FXXU1CRC7.
I now downloaded the TWRP file you mentioned and followed the guide you mentioned.
TWRP was installed using latest Odin Version 3.13, then I tried to install SuperSU, but this failed, red error messages like failed to mount /data, unable to mount storage.
same for factory reset, does not work. I formated data, it worked. then I installed Super Su, it was possible. then I rebooted device and what shall I say, it booted into Android
Dont know what I did different now, maybe not trying to boot up Android before installing supersu.zip?
However, Now I have latest Oreo with TWRP and phone is rooted
Now I will go on and install xposed framework :good:
Many thanks for your help.
tobyffm said:
Hi again,
I got an OTA Update this morning, so current build on phone was G955FXXU1CRC7.
I now downloaded the TWRP file you mentioned and followed the guide you mentioned.
TWRP was installed using latest Odin Version 3.13, then I tried to install SuperSU, but this failed, red error messages like failed to mount /data, unable to mount storage.
same for factory reset, does not work. I formated data, it worked. then I installed Super Su, it was possible. then I rebooted device and what shall I say, it booted into Android
Dont know what I did different now, maybe not trying to boot up Android before installing supersu.zip?
However, Now I have latest Oreo with TWRP and phone is rooted
Now I will go on and install xposed framework :good:
Many thanks for your help.
Click to expand...
Click to collapse
Update: Just tried to flöash xposed framework via TWRP but it fails because of unable to mount data. Do you know why this appears?
tobyffm said:
Update: Just tried to flöash xposed framework via TWRP but it fails because of unable to mount data. Do you know why this appears?
Click to expand...
Click to collapse
Hello dude, u are gonna need to flash dm-verity 5.1 find it on google , flash it and then flash immediately flash Xposed , if the error appear again then format data, and there is a option to wipe cache and Data, wipe them too, flash dm-verity and flash immediately the Xposed, if I helped you please press thanks buttons
StonebridgeGr said:
Hello dude, u are gonna need to flash dm-verity 5.1 find it on google , flash it and then flash immediately flash Xposed , if the error appear again then format data, and there is a option to wipe cache and Data, wipe them too, flash dm-verity and flash immediately the Xposed, if I helped you please press thanks buttons
Click to expand...
Click to collapse
Hi,
I had to format data, then I wiped Cache and Data again. Tehn, I flashed dm-verity, directly after that SuperSU again and directly aafter this I flashed xposed.
Finally, all works
Many thanks for your kind help!
tobyffm said:
Hi,
I had to format data, then I wiped Cache and Data again. Tehn, I flashed dm-verity, directly after that SuperSU again and directly aafter this I flashed xposed.
Finally, all works
Many thanks for your kind help!
Click to expand...
Click to collapse
I told you you were missing something with the instructions, I am happy now everything is fine
Hello, I was trying to root my phone last night, I unlocked the boot loader that worked perfectly, easy. Nothing else went well, I was fighting with it TWRP for hours and then Magisk wouldn't install. I gave up on that and tried SuperSu... now the phone just stays on the loading screen instead of booting, It won't boot into recovery either just fastboot. Can it be fixed?
Your phone is soft bricked and can only boot to bootloader, correct?
The only solution is flashing the stock ROM of the device. You can get your device (Tissot) stock ROM from here.
I just got it to boot into TWRP, after it cycled a few times.
Well that may make it easier, you can try wiping dalvik cache then wiping data and see if that works. Needless to say wiping data is going to delete all your personal data, but since you're in TWRP recovery you can back it up.
Wiping it didn't work, I'm trying to use MiFlash I have downloaded "Tissot_9.0_V10.0.10.0.PDHMIXM_Fastboot" my phone is in fastboot. MiFlash detects it but when I try to flash I just get "can not found file flash_all_lock.bat"
How do you tell is MiFlash has successfully installed drivers, it gives me a window in Chinese?
If it's not working - I never thought it would anyway - then your only option is to flash stock ROM.
You can try using fastboot commands through cmd window, if it returns <waiting for device> or something similar then the driver isn't installed properly. Alternatively you can install the driver from here.
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
galaxymini1 said:
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
Click to expand...
Click to collapse
You can use any version as long as it is meant for your device. Flashing the latest version might be best option.
Happy to help.
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
galaxymini1 said:
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
Click to expand...
Click to collapse
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
XDHx86 said:
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
Click to expand...
Click to collapse
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
galaxymini1 said:
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
Click to expand...
Click to collapse
You can find that in an XDA revised article here.
I got TWRP and Magisk installed no problem. I don't know if I was just tired or it was the crap guides but nothing wanted to cooperate on my first attempt.
Thanks for all the help.