Related
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
What are the links to all these incorrect firmwares?
Posting the links would be more informative than suspicions.
Pp.
wallacengineering said:
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
Click to expand...
Click to collapse
Yes, could you post the links that you say have the issues?
AxAtAx said:
Yes, could you post the links that you say have the issues?
Click to expand...
Click to collapse
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
wallacengineering said:
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
Click to expand...
Click to collapse
I just put that stock rom on my wifes phone a few days ago, and it defaulted to Note 3 on hers. well, never mind, as you have seem to have got it rolling now.:good::good:
I must be taken crazy pills.
Pp. :what:
Can i ever unbrick my note 3
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
boofydon said:
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Ravoz88 said:
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Click to expand...
Click to collapse
Thank you for your time. I flashed it with a new stock from sammobile but it's still in a boot loop state even though odin always show pass. And when I flashed it with twrp my note 3 was unable to enter recovery mode.
Hey guys,
I have a HTC M9
I am trying to install the Xposed Framework on my Rooted M9 with stock ROM but inside the Xposed app it tells me that it's not installed.
I have TWRP installed.
I rooted my phone with SuperSU v2.65 (After trying a couple of versions that would result in boot loop)
I checked my phones CPU (ARM64) and downloaded "xposed-v86-sdk23-arm64" as well as "XposedInstaller_3.0_alpha4.apk".
I booted into TWRP and Installed the xposed-v86-sdk23-arm64 Framework, it gets to Placing Files and then my phone reboots (I don't know if this is normal or not).
My phone reboots and I open XposedInstaller, under Framework it says "The latest version of Xposed is currently not active, Did you install the Framework and reboot?"
Inside the Framework menu it says "The Xposed Framework is not installed. Please download the latest ZIP file from XDA and flash it manually via reocvery."
The options Install/Update, Uninstall, Recovery (Flash zip automatically) are grayed out.
When I press the Soft Reboot button the phone does restart but no change.
When I try to press the Reboot option I get this error:
Code:
sush: <stdin>[8]: /data/user/0/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed please use the device's normal reboot function.
I have restarted the phone normally a couple of times with no change.
I'm new to rooting but I don't find this stuff too difficult to understand, I had a lot of problems trying to get my phone to root in the beginning, I had to try a few SuperSU versions before I could get my phone past boot looping. When I run Root Check it tells me that my phone is Rooted.
I'm not sure what other information I can post to help yous help me but if there's anything you need to know just ask and I'll reply asap.
Cheers guys
I basically want access to Xposed so I can use the FakeGPS and the Hide Mock Location modules.
EDIT (29/07 2:00PM)
I re-downloaded xposed-v86-sdk23-arm64 and tried flashing it again, I read somewhere someone mentioning to clear the caches after the install has finished but when I start the install and it reaches "Placing Files" the phone automatically reboots itself, so I held Volume down and Power to go straight back into Download Mode > Boot Mode > Recovery Mode and cleared the caches, let the phone boot up and still have the exact same problem as the above post.
Seeing as though I haven't gotten any advice yet I am going to try an older version of the Installer app, I have 2 seperate backups of my device so if anything goes wrong I can restore, wish me luck!
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Wolf_vx said:
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Click to expand...
Click to collapse
You have described my situation perfectly.
I have a back up I can restore through TWRP if I soft brick it, which at this moment I just did.
I tried flashing the same superSU version again seeing as though it was the only one I could get to work (didn't try your version though) and then installed the latest Framework version right after without rebooting, cleared the two caches and rebooted, I get past the first boot screen, I see my mobile providers boot screen, I then get to the screen with One in big letters and it stops there, I'll try a few more reboots before I restore.
Xposed isn't stable on the m9 and is why I have avoided installing it. Some people get it running first time, no issues. Some people brick their phones. It really is a roll of the dice.
I'd stay away from it if i were you. Htc's can't be easily recovered.
Beamed in by telepathy.
it doesn't brick the phone, but there are a few tutorials with other methods of flashing xposed, should be inside software development of android forum. please try those solutions and please stop creating two threads, with nearly same problem. both things can be asked in one thread, thanks
stock rom has often problems. you need to install busybox to have it working properly
First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly
Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.
Maybe this has something to do with Keymaster?
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.
New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks
Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!
Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.
Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.
So, I got an A50, and I'm really happy that I did. However, switching from a phone that had TWRP and Magisk is something I am not finding easy, even if the phone is much faster than my old one. So, of course, after thoroughly reading my warranty, which had no mention of not covering software device damage, I decided to to go ahead and try to flash TWRP and then install Magisk. I went ahead and easily figured out that my model is SM-A505FN (which would have been all that I needed for my old phone). Seeing that there were successful attempts at installing TWRP and Magisk on this model, I decided to try it out, but quickly found myself with a soft bricked phone, so off to finding a Stock ROM I went. After booting it up again I did more digging, but that yielded no result, however, I decided to try using Magisk manager to patch the AP file and then tried patching that. Sadly, no luck. I even went as far as trying a few of those programs that would root your phone from your PC, but that proved to be a waste of time as even that didn't work (which I suspected would happen, but whatever).
While fondling with the phone, I noticed something in the recovery. It wrote a50xx and then I realized that that must have been the reason for nothing working. And now we get to the title of this post. Has anybody been successful at rooting or flashing TWRP on an a50xx device, and, if so, would you be so kind as to elaborate on how you did it?
If not, I guess I should either wait, or look into trying to port TWRP to a50xx myself.
Edit: In case I do decide to port TWRP, any help or pointers are welcome.
Hello @BrainReader,
Same problem here! I tried rooting my device (sm-a505fn as well) by flashing the ap-file using magisk manager. I kept ending in a bootloop. I tried the latest version v20.x and even tried v19.3 which should work stable according to this thread: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271.
I hope this thread gets more attention and someone finds a solution for rooting the a50!
Kind regards,
Shademaster639
I have a rooted a505fn twrp is not working but rooting with magisk works fine. Every magisk version above 19.3 is giving problems. The latest magisk give very much reboots. What I did I first installed the newest software with Odin. Then install magisk 19.3 after that I set in magisk the update channel to get no further then 19.3.
That patch the AP file and reflash everything with the patched version.
It works without problems.
You must flash complete firmware stock
Then reflash complete firmware with mm agisk ap