Related
I have searched a lot on the web and xda but cannot find any solutions. As far as I know I have correctly installed the Xposed framework using TWRP but when rebooting I get stuck on the Samsung logo screen and have to recover to fix. I have tried various versions of the framework and always get the same issue.
Android version - 5.0.2
Installed ROM (stock or custom ROM) - Stock ROM (Would install custom if it helps but cant decide which one yet)
Names of the file you tried to flash - I tried 3 - xposed-v67-sdk21-arm.zip, xposed-v72-sdk21-arm.zip, xposed-v86-sdk21-arm.zip
Error messages - none, but gets stuck at the samsung logo on boot
I really wanted to install the custom ROM Acheron, but dont think its compatible with my device so if anyone can recommend a good custom ROM I am all ears
DJRenegade88 said:
I have searched a lot on the web and xda but cannot find any solutions. As far as I know I have correctly installed the Xposed framework using TWRP but when rebooting I get stuck on the Samsung logo screen and have to recover to fix. I have tried various versions of the framework and always get the same issue.
Android version - 5.0.2
Installed ROM (stock or custom ROM) - Stock ROM (Would install custom if it helps but cant decide which one yet)
Names of the file you tried to flash - I tried 3 - xposed-v67-sdk21-arm.zip, xposed-v72-sdk21-arm.zip, xposed-v86-sdk21-arm.zip
Error messages - none, but gets stuck at the samsung logo on boot
I really wanted to install the custom ROM Acheron, but dont think its compatible with my device so if anyone can recommend a good custom ROM I am all ears
Click to expand...
Click to collapse
https://mega.nz/#!yMQ0ABIb!X_FrC0Uds2By-liblHEa9TTdy5v0wWIb76Jxr2JzKRo try this
Sent from my SM-A9100 using Tapatalk
Not sure I'd blindly follow a mega-upload...but maybe I'm paranoid. @DJRenegade88 I know you say you searched the web, but it sounds like you're trying to use the official xPosed. There's a huge red sign stating that if you try that on Samsung you will boot loop. For Android 5'0.x you need arter's xPosed
http://forum.xda-developers.com/showthread.php?t=3113463
If you update to 5.1 or 6 you'll need to get the Wanam version instead (I'd link, but don't wish to confuse you as you have 5.0.x (sdk21)
Nergal di Cuthah said:
Not sure I'd blindly follow a mega-upload...but maybe I'm paranoid. @DJRenegade88 I know you say you searched the web, but it sounds like you're trying to use the official xPosed. There's a huge red sign stating that if you try that on Samsung you will boot loop. For Android 5'0.x you need arter's xPosed
http://forum.xda-developers.com/showthread.php?t=3113463
If you update to 5.1 or 6 you'll need to get the Wanam version instead (I'd link, but don't wish to confuse you as you have 5.0.x (sdk21)
Click to expand...
Click to collapse
yea I was trying the official and I have seen that red text about samsung bootloops lol, dunno how I missed that the first time, thanks for the clarification. Is there a specific version I should download? I see he lists a few, I am guessing the most recent (xposed-v75-sdk21-arm-arter97-snapdragon.zip) is the correct one?
The number "75" "86" etc is the version number so everything you typed is correct 21 arter arm but you want whatever is the highest, with one caveat: if there is an 86 a few modules will not work (in short they will be forbidden from running by xPosed for bad coding); I'm guessing quite a few of the 5'0'x specific modules may get caught by this. If you find a module you can't live without that doesn't work (and gives a very specific, noticeable error in the xPosed log) you might want to stick with 85
Doesn't work
It took 5 minutes to boot and now it's optimizing all my apps. I don't think it works.
This is how alot of phones with locked bootloader get custom recovery and roms
https://github.com/mohammad92/recovery-safestrap
This is safestrap 3.1.1 I think versions going up to 4, but this one listed was the last updated. We just need to get someone to build for our device.
DroidisLINUX said:
This is how alot of phones with locked bootloader get custom recovery and roms
https://github.com/mohammad92/recovery-safestrap
This is safestrap 3.1.1 I think versions going up to 4, but this one listed was the last updated. We just need to get someone to build for our device.
Click to expand...
Click to collapse
Safestrap was patched long ago. Its a waste of time.
There is newer versions of safestrap, we can write over the recovery I have done it with enyox version of twrp it doesnt boot but it flashes with flashfire,
we can also set selinux to permissive I believe this is all we need to get a safestrap to work. booting normaly might not work, might have to boot into "recovery mode"
everytime and let the safestrap boot into system for a custom recovery and roms to work, but it is a possibility.
there is also a newer similar version of recovery like safestrap called Fish I believe
someone should look into Fish and or at least compile a safestrap version before you go and say its not possible.
DroidisLINUX said:
There is newer versions of safestrap, we can write over the recovery I have done it with enyox version of twrp it doesnt boot but it flashes with flashfire,
we can also set selinux to permissive I believe this is all we need to get a safestrap to work. booting normaly might not work, might have to boot into "recovery mode"
everytime and let the safestrap boot into system for a custom recovery and roms to work, but it is a possibility.
there is also a newer similar version of recovery like safestrap called Fish I believe
someone should look into Fish and or at least compile a safestrap version before you go and say its not possible.
Click to expand...
Click to collapse
There are newer version but for old hardware. The exploit safestrap used in the first place was patched on lollipop. It won't work on versions after that. Unless it's been renamed. But safestrap is not for newer devices. It won't work.
Ive tried fish already. It kinda works. Kinda not though. Cant get it to load the new ramdisk.
If anyone was looking here is the note 8 kernel released by Samsung
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=N950
N950U is on the second page
I also noticed that if you use flashfire you can flash over the boot.img and system.img,
I know someone will say it's because I used a boot.img from an update.zip, but you need to realize that the flashfire apk doesn't check a signature so it can't tell if it was a custom boot.img or a stock boot.img
I also noticed in the root directory a default.prop file that shows oem_unlocked=1
I have the snapdragon with stock rooted firmware.
Safestrap? Wow. Talk about a flashback to the Droid Razr days.
I bet we will soon see a "Help! I Bricked my Note 8!" Thread from the OP soon. LOL
Lol nope I am not going to brick my phone
Sent from my note 8
I was waiting to get another Note 8 that I could chance bricking...but haven't jumped on it yet...I was trying some of the same and almost bricked my main device so I took a breather...it would be nice...the unlock tools also show that we have oemunlock=1...it's pretty neat but so far away...
Not sure if anyone care or still want to go back to 5.0.1.
It is possible if you download COMBINATION_VZW_FA50_G925VVRU4AOJ1 (Google it yourself its free out there.)
After flashing combination file you can root it with kingroot then replace it with superuser ( https://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 ), then you can use flashfire to flash 5.0.1 rom.
You will need to keep the sboot/bootloader from combination file i order to boot with 5.0.1 kernel.
Anyone know if theres good rom that will still work with this method? I tied some stock root rom ( https://forum.xda-developers.com/ve...ment/rom-stock-rooted-g925v-vru1aoc3-t3115121 ), it seems to be missing some file after flashing. It boots up gets signal, but it is buggy. If anyone know if bugs from flashing this way cannot be fixed then let me know so I can stop trying .
I flashed the COMBINATION_VZW_FA50_G925VVRU4AOJ1 tar file but how do it install apks so i can use kingroot. unless you have forum to share with me
I haven't used the XDA forums in over a year. I don't know if I have the courage to downgrade from 7.0 to 5.X
Snowby123 said:
I haven't used the XDA forums in over a year. I don't know if I have the courage to downgrade from 7.0 to 5.X
Click to expand...
Click to collapse
Something similar for me honestly. I just downloaded the firmware stated, did the steps and it seems to have worked fine. Even with root, I honestly liked 7.0 on this device. Dang locked BL. :/
3Cubed27 said:
I flashed the COMBINATION_VZW_FA50_G925VVRU4AOJ1 tar file but how do it install apks so i can use kingroot. unless you have forum to share with me
Click to expand...
Click to collapse
You can install apks using ADB -- I think you can get it from Android Studio or try https://www.xda-developers.com/install-adb-windows-macos-linux/
Once you have ADB installed, just connect your S6 to your PC, open terminal, and run "adb devices" to confirm your phone is visable
Then to install an apk, have it downloaded on your PC and run
"adb install {path/to/apk}"
Example:
adb install Downloads/NewKingrootV5.3.7_C197_B451_xda_release_2018_06_19_20180620193529_242043.apk
I don't really think there was a 5.0.1 ROM designed for the Revision 4 bootloader outside of the Combination Firmware. I think this may be a reason.
Delgoth said:
I don't really think there was a 5.0.1 ROM designed for the Revision 4 bootloader outside of the Combination Firmware. I think this may be a reason.
Click to expand...
Click to collapse
I know this is old. But I come from a s8. So we should be able to even though rev4 bootloader flash any 5 System IMG. The bootloader from the fa50 combination should suffice to boot any lolipop system since they are not incremented
TheMadScientist said:
I know this is old. But I come from a s8. So we should be able to even though rev4 bootloader flash any 5 System IMG. The bootloader from the fa50 combination should suffice to boot any lolipop system since they are not incremented
Click to expand...
Click to collapse
Correct, you just need the bootloader and kernel capable of booting the system up. This is how I was able to use any of the LP AP Build/System on my rev 3 Note5.
All the LP builds were rev 2. But I had a LP bootloader and kernel. Realistically someone should try, but you might need to root the combo firmware first and use flash fire/flashify/safestrap to flash the system image. Because ODIN might not let you.
Delgoth said:
Correct, you just need the bootloader and kernel capable of booting the system up. This is how I was able to use any of the LP AP Build/System on my rev 3 Note5.
All the LP builds were rev 2. But I had a LP bootloader and kernel. Realistically someone should try, but you might need to root the combo firmware first and use flash fire/flashify/safestrap to flash the system image. Because ODIN might not let you.
Click to expand...
Click to collapse
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
TheMadScientist said:
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
Click to expand...
Click to collapse
The question is, what did you do to.modify your stock rom to be able to boot on the combo bootloader? I'm still a little lost on that.
Delgoth said:
The question is, what did you do to.modify your stock rom to be able to boot on the combo bootloader? I'm still a little lost on that.
Click to expand...
Click to collapse
I didn't on the j3.
TheMadScientist said:
I didn't on the j3.
Click to expand...
Click to collapse
Maybe not on the j3 haha.
Delgoth said:
Maybe not on the j3 haha.
Click to expand...
Click to collapse
Wrong device ****. I got so many phones lying around. I haven't really messed with the s6 much. I got a few other on the front burner
TheMadScientist said:
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
Click to expand...
Click to collapse
This is what I was asking about though. I still can't get anyone to explain how to make the stock ROMs work on the newer more locked devices. It's like a big secret or something. But it is possible on the S6, Note5, and S8. Probably the S7 too.
But 5.0.1, 5.1.1, and 7.0 are built a lot differently and I imagine the method is different.
TheMadScientist said:
Wrong device ****. I got so many phones lying around. I haven't really messed with the s6 much. I got a few other on the front burner
Click to expand...
Click to collapse
Before the S9 Line most everything has been built pretty similarly.
So I have spent a lot of time messing around with roms and roots on nougat but I have recently restored my device to factory to use the recent official 8.0 OTA update and I now want to root the device. However with the new kernel Im not sure if I should use a different twrp or I just install the same as I used before with the modified flash command (recovery_ramdisk).
I used to use twrp-3.1.1-0-vtr.img or twrp-3.1.0-0-vtr.img, can I just flash this or do I need an oreo version?
If so what new twrp should I be using?
Jyndon said:
So I have spent a lot of time messing around with roms and roots on nougat but I have recently restored my device to factory to use the recent official 8.0 OTA update and I now want to root the device. However with the new kernel Im not sure if I should use a different twrp or I just install the same as I used before with the modified flash command (recovery_ramdisk).
I used to use twrp-3.1.1-0-vtr.img or twrp-3.1.0-0-vtr.img, can I just flash this or do I need an oreo version?
If so what new twrp should I be using?
Click to expand...
Click to collapse
Bump!
no one knows what recovery works on 8.0???
Jyndon said:
Bump!
no one knows what recovery works on 8.0???
Click to expand...
Click to collapse
I guess you should go for 3.2.1-0
I use this since @espaciosalter20 posted it and it works very good, I never noticed any issues. Data encryption works well.
Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links):
EU NE2213_11_A.12
Stock boot.img - link
EU NE2213_11_A.10
Stock boot.img - link
Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come.
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.