Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
EDIT: New OTA [YNG1TAS17L]:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS17L-bacon/e816218e8a/cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Credits to @julian_klode:
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Note: I initially wasn't aware about the source of the base zip file that I used to pack the necessary files until julian_klode mentioned it in the Q&A thread.
There is no difference between this one and his, just the fact that I update mine manually. So, I think you should follow his thread instead.
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Outstriped! I was thinking to make Debug kernel, but they released it sooner
Thank you so much. Puzzle and Dragons doesn't like Supersu, but works perfect with CM's superuser.
works fine here, thanks!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
thank you , works perfectly!
inscythe said:
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
Click to expand...
Click to collapse
thx:good:
Works great please keep this updated with each OTA if possible!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
That did not work for me
droidextra said:
That did not work for me
Click to expand...
Click to collapse
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
srgudhka said:
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
Click to expand...
Click to collapse
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
inscythe said:
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
Click to expand...
Click to collapse
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
All good here! I went into the Supersu settings and did a FULL UNINSTALL OF ROOT. Once that was done, I went into TWRP and flashed CM zip provided by OP... Bam. Done and no problems. Thank you, OP!
Wisiwyg said:
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
Click to expand...
Click to collapse
I perhaps wasn't very clear about my above suggestion.
What I meant is that, there is an official insecure boot.img (the kernel) which I linked above and included in my zip package. I'm not telling him to install both SuperSU and the built-in root.
SuperSU has some features that is not present in the built-in root though, like logging or tapjacking protection. Privacy Guard is pretty nifty, but I still miss the old interface of SuperSU.
inscythe said:
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Click to expand...
Click to collapse
Is there any way to make this work with franco kernel r41? Thanks...
ten_tickles said:
Is there any way to make this work with franco kernel r41? Thanks...
Click to expand...
Click to collapse
I think it's the issue with Franco's own kernel... Even the nightly CM12 users with the built-in root enabled also had the root access disabled.
SuperSU works in this case because it relies on an init.d su-enabling service.
Just wait for Franco to fix it, since the CM11S versions works well with the built-in root. I am also a FK paid user, so this is a bad situation for me as well...
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
I uploaded it here sorry it's not a better host but I'm on my phone ATM lol. http://uploadmirrors.com/download/R8ADOYOG/icial-12.0-signed-YNG1TAS17L-bacon-superuser.zip All I did was get the ota URL from here and changed the ending to cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img I guess the system automatically makes the debug images when the ota rolls out. So I imagine the same thing would work for next ota. You just rename it to boot.img and replace the one in the zip from this thread and rename the zip and flash.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Not that hard to make, right? But super practical to keep this if you often jumping ROMs.
SimonTS said:
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
Click to expand...
Click to collapse
Sorry, was doing overtime at work. I've updated the OP too.
Related
This bump thing is confusing the hell out of me. Then again I haven't slept in 20hrs... regardless.
My phone is rooted and I installed TWRP from the TWRP app in the play store. Do I need Bump to install CM 12.0 or can I just flash CM 12.0 from TWRP? I've been googling for awhile and reading threads here on Bump but I have no clue what it is...
You must follow directions in THIS post. If your not comfortable using adb commands, you can flash the IMG file from that post using flashify from Google Play. Then flash THIS updated zip version of bumped TWRP in TWRP.
sent from my LG G3
drekalots said:
This bump thing is confusing the hell out of me. Then again I haven't slept in 20hrs... regardless.
My phone is rooted and I installed TWRP from the TWRP app in the play store. Do I need Bump to install CM 12.0 or can I just flash CM 12.0 from TWRP? I've been googling for awhile and reading threads here on Bump but I have no clue what it is...
Click to expand...
Click to collapse
I didn't use the twrp app to install twrp but looking through the app the LS990 is listed so I don't really know. The method I used is as follows and works without a hitch. If you are already rooted, grab flashify from the play store and flash the BUMPED LS990 Twrp from flashify. Make sure to flash it as a recovery image. If you try to put a recovery on there that hasn't been BUMPED yet you will probably end up in a bad situation. After you have the bumped recovery on your phone go-ahead and flash whatever rom you want. They will all be bumped before they are uploaded to a server.
Not to sound like an a$$ but you really should read the bump thread in the original development and followed that. That would have been the safest way of doing this. With these phones you really shouldn't deviate from the instructions that are posted.
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_ls990-signed.img
whoppe862005 said:
I didn't use the twrp app to install twrp but looking through the app the LS990 is listed so I don't really know. The method I used is as follows and works without a hitch. If you are already rooted, grab flashify from the play store and flash the BUMPED LS990 Twrp from flashify. Make sure to flash it as a recovery image. If you try to put a recovery on there that hasn't been BUMPED yet you will probably end up in a bad situation. After you have the bumped recovery on your phone go-ahead and flash whatever rom you want. They will all be bumped before they are uploaded to a server.
Not to sound like an a$$ but you really should read the bump thread in the original development and followed that. That would have been the safest way of doing this. With these phones you really shouldn't deviate from the instructions that are posted.
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_ls990-signed.img
Click to expand...
Click to collapse
I'd read that but not much was clicking last night.
I ended up following this http://www.droidviews.com/install-twrp-recovery-on-lg-g3-all-variants-using-bump/ to flash the bumped TWRP img. I still have no clue what the difference is though. lol. Right now I'm running CM12.0 and I'm not so much a fan of Lollipop. May need to find another ROM.
drekalots said:
I'd read that but not much was clicking last night.
I ended up following this http://www.droidviews.com/install-twrp-recovery-on-lg-g3-all-variants-using-bump/ to flash the bumped TWRP img. I still have no clue what the difference is though. lol. Right now I'm running CM12.0 and I'm not so much a fan of Lollipop. May need to find another ROM.
Click to expand...
Click to collapse
Essentially your recovery and boot.imgs need to be "bumped" which tricks the bootloader into thinking the file was signed by LG. Otherwise you get a secured boot error after flashing. If you are using a TWRP file or custom kernel from here in the threads, it's already been bumped(or definitely should be) so all you have to do is install it.
I know it may seem confusing because it is very different from other android models but really the devs are the ones that have to bump things, for the end user, there isn't really a difference.
whoppe862005 said:
I didn't use the twrp app to install twrp but looking through the app the LS990 is listed so I don't really know. The method I used is as follows and works without a hitch. If you are already rooted, grab flashify from the play store and flash the BUMPED LS990 Twrp from flashify. Make sure to flash it as a recovery image. If you try to put a recovery on there that hasn't been BUMPED yet you will probably end up in a bad situation. After you have the bumped recovery on your phone go-ahead and flash whatever rom you want. They will all be bumped before they are uploaded to a server.
Not to sound like an a$$ but you really should read the bump thread in the original development and followed that. That would have been the safest way of doing this. With these phones you really shouldn't deviate from the instructions that are posted.
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_ls990-signed.img
Click to expand...
Click to collapse
HPTesla said:
Essentially your recovery and boot.imgs need to be "bumped" which tricks the bootloader into thinking the file was signed by LG. Otherwise you get a secured boot error after flashing. If you are using a TWRP file or custom kernel from here in the threads, it's already been bumped(or definitely should be) so all you have to do is install it.
I know it may seem confusing because it is very different from other android models but really the devs are the ones that have to bump things, for the end user, there isn't really a difference.
Click to expand...
Click to collapse
Ah. Got it. Thank you for clearing that up.
Hey Folks,
I am totally new to this but I want to put CM 12.1 on my SPG621. I have unlocked the bootloader so far and I was looking for hours for a step by step guide that is noob-safe.
There are many guides and tutorials that tell different things and it is very hard for me to get the essence of it.
What I understand is as follows:
- I have an unlocked bootloader (and lost my DRM Keys, good job)
- get root
- install custom recovery
- install CM 12.1
Is that the correct order? How do I do that in detail? I don't understand how to install a custom recovery without root and I don't understand how to get root.
I have downloaded Flashtool so far. I would be glad if I got any helpful advices. Thanks a lot!
These are what I did to have root and twrp:
1. Check what version you are on right now. If you are on 5.0.2, you can root it by using Kingroot 4.5 (here)
2. If not, you can download stock 5.0.2 from here and flash it via Flashtool; then you can install Kingroot 4.5 and get root
3. Turn on usb debugging and unlock the bootloader again as you have converted to stock
4. Install twrp - download from here
5. Download CM12.1 and Gapps and install via twrp here
Hope it helps!
Thanks for your quick answer.
I now obtained root access via Kingroot. I would like to install TWRP Recovery now. I downloaded it via PlayStore. I chose my device and tapped on Install Recovery.
It now asks me to confirm a partition /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel else I would risk bricking the device. How can I make sure that this is the correct partition? I can't see this path in my file commander.
Cheers,
ArctiCMooN
Edit: Never mind, I didn't click on the link. I will install it with your link then and post the result here.
Mocha7 said:
These are what I did to have root and twrp:
1. Check what version you are on right now. If you are on 5.0.2, you can root it by using Kingroot 4.5 (here)
2. If not, you can download stock 5.0.2 from here and flash it via Flashtool; then you can install Kingroot 4.5 and get root
3. Turn on usb debugging and unlock the bootloader again as you have converted to stock
4. Install twrp - download from here
5. Download CM12.1 and Gapps and install via twrp here
Hope it helps!
Click to expand...
Click to collapse
I have a few problems now that I try installing the dual recovery.
Root Checker says I successfully have rooted my device. BUT: I cannot find the KingUser App anywhere.
When I try to install TWRP via this dual recovery method, it asks me if I want to use SuperSU or SuperUser method, but I don't have anyone of the, is that correct?
Did something go wrong?
ArctiCMooN said:
I have a few problems now that I try installing the dual recovery.
Root Checker says I successfully have rooted my device. BUT: I cannot find the KingUser App anywhere.
When I try to install TWRP via this dual recovery method, it asks me if I want to use SuperSU or SuperUser method, but I don't have anyone of the, is that correct?
Did something go wrong?
Click to expand...
Click to collapse
Look at this thread: http://forum.xda-developers.com/z3-tablet-compact/general/how-to-root-easy-t3115418
You'll have the answers of your questions.
It worked perfectly for me.
guizmogwai said:
Look at this thread: http://forum.xda-developers.com/z3-tablet-compact/general/how-to-root-easy-t3115418
You'll have the answers of your questions.
It worked perfectly for me.
Click to expand...
Click to collapse
Thanks a lot for the help.
I managed to get CM12.1 on my Sony Xperia Z3 Compact Tablet.
I basically did what Mocha7 told me, although I wasn't sure about KingRoot 4.5 (trustworthy or not?). I gave it a try, the first time it failed, the second time the root was successful.
I did not install SuperSU or SuperUser and directly continued with the installation of XZDualRecovery and chose SuperSU method in the Windows Command Terminal.
This worked perfectly and the tablet directly started into TWRP. From there I started the installation of CM 12.1.
After that, I did a factory reset of CM 12.1 to erase all data of the old system and reinstalled XZDualRecovery.
I downloaded the latest Gapps from CM Wiki and installed it via Recovery.
The system works fine and I am extremely happy that I got rid of Sony's Stock Android. There are some very small bugs in CM 12.1: Rebooting erases some shortcuts on the homescreen and the lowest brightness setting is still quite bright.
Thanks again for the help!
ArctiCMooN said:
Thanks a lot for the help.
I managed to get CM12.1 on my Sony Xperia Z3 Compact Tablet.
I basically did what Mocha7 told me, although I wasn't sure about KingRoot 4.5 (trustworthy or not?). I gave it a try, the first time it failed, the second time the root was successful.
I did not install SuperSU or SuperUser and directly continued with the installation of XZDualRecovery and chose SuperSU method in the Windows Command Terminal.
This worked perfectly and the tablet directly started into TWRP. From there I started the installation of CM 12.1.
After that, I did a factory reset of CM 12.1 to erase all data of the old system and reinstalled XZDualRecovery.
I downloaded the latest Gapps from CM Wiki and installed it via Recovery.
The system works fine and I am extremely happy that I got rid of Sony's Stock Android. There are some very small bugs in CM 12.1: Rebooting erases some shortcuts on the homescreen and the lowest brightness setting is still quite bright.
Thanks again for the help!
Click to expand...
Click to collapse
Sorry I was out of town for the labour day long weekend so I didn't see your replies.
So glad to hear that you nailed the CM 12.1! Enjoy!!:good::good:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
wow, man! I read your post and think this is ME!! haha I just got my Z3 Tablet a few days ago and had the same struggle. I got it with 4.4.4 installed and jumped right to CM12.1. Also tried crDroid and like it actually much better^^ I got a big problem though. With these custom roms my camera would not focus! the back camera is useless. front is ok though. Have you anything like that??
Schuan said:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
Click to expand...
Click to collapse
It works really well so far. No crashes or anything. very nice! :good:
Schuan said:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
Click to expand...
Click to collapse
Hi, CM 12.1 is quite stable but has a few bugs.
Restarting the device deletes most of my homescreen shortcuts.
The adaptive brightness options seems a little bit buggy. It switches brightness way too fast and too often, is not smooth, so I turned that off.
Besides that, I did not experience any further bugs.
knauji said:
It works really well so far. No crashes or anything. very nice! :good:
Click to expand...
Click to collapse
Now there is a problem. I tried to update to a more recent nightly of CM 12.1. I did it via the settings menu and let everything happen.
Now I can't boot my device anymore nor can I boot into recovery. The device just tries to boot, shows the Sony symbol and then turns off and tries to boot again. So it is in a boot loop.
Can anybody help with this?
This happened to me a few times. Try to flash the recovery again and the flash the rom from there. If it works, good, if not....
It happened to last night when I tried the latest nightly. I could not do anything so I flashed the sony stock rom with flashtool. After that I could flash TWRP again. Not sure of any other way.
Yeah I had huge problems getting recovery on my device. I reinstalled stock 5.0.2, rooted it and tried to get the same dual recovery on it I used before, but it didn't work. So I downgraded to 4.4.4 and managed to get Custom Recovery on it and from there I managed to install CM 12.1 again. Now everything works fine, but my nerves need a rest now^^
glad it works. take a rest and enjoy haha
I have to wait some more or maybe even sell it because of the camera bug.... I don't like sony stock os ....
This is for the Sprint SM-T587P "gtaxlqltespr" Galaxy Tab A 10.1 variant only.
As far as I can tell, the Nougat update came out for the Sprint Variant sometime around the 20th of September 2017. Update to the T587PVPU1BQI1 Nougat update if you have not already.
1. Read all instructions, there are no known issues. Be on 7.0.0 official. (QI1)
2 Enable Developer Options. Settings, About Device, Software info, tap on build number until it is enabled.
3. Enable OEM unlock and USB Debugging in the Developer Options menu.
There are a couple options here. You can do any combination of the following:
install TWRP
root via superuser (requires installing TWRP)
disable dm-verity (requires installing TWRP)
root by flashing magisk patched bootimage (does not require TWRP)
disable force-encryption (requires installing twrp)(required if you want TWRP to see /data/ files)(not required for flashing zips such as superuser through TWRP)
To install TWRP:
1. Boot into download mode
2. Launch ODIN, Uncheck "Auto Reboot" in the options tab. Flash included TWRP file in the AP section of ODIN.
To Disable Force-Encryption (if want to see /data/ in twrp)
1. Install TWRP recovery
2 Boot into TWRP recovery
3. Format Data
4. Reboot into TWRP from TWRP reboot menu, without rebooting into system.
5. Flash the included superuser.zip to disable force-encryption and dm-verity
To Root via superuser or disable dm-verity
1. Install TWRP recovery.
2. Boot into TWRP recovery
3. flash superuser.zip (this needs to be done with ADB if you have not disabled force-encryption and are unable to see /data/)
Superuser root provided as-is. Magisk is the recommended root. If you prefer the outdated, beta, un-updatable phh superuser binary which breaks safetynet that's all you. However it is the only way i have found to disable dm-verity.
Magisk v16 root:
Device is stock
If you have not installed twrp, disabled dm-verity, or disabled force encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-dm-patched_boot.img.tar"
Disabled dm-verity, but NOT force-encryption
If you did not format DATA in TWRP and have installed superuser.zip using ADB:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-patched_boot.img.tar"
Disabled Both
If you disabled dm-verity AND disabled force-encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "Magiskv16_patched_boot.img.tar"
WIFI IS NOW WORKING AFTER ROOT/BOOT PATCH
Recovery: twrp-3.1.1-0-gtaxlqltespr.tar
phh's Superuser.zip
fe-dm-patched_boot.img.tar
fe-patched_boot.img.tar
Magiskv16_patched_boot.img.tar
Magisk Manager 5.6.1(105)
XposedInstaller_3.1.4_Magisk.apk
Stock 7.0.0 boot image
Stock 7.0.0 Recovery
phh's Superuser
Nougat Firmware
AP
BP
CP
CSC
Gonna try it now!!! Been waiting for along time.... thanks
Sent from my Sprint Samsung Galaxy Note5 using XDA Labs
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
T587P need stock firmware and recovery
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Ok what i did being i just didnt have recovery and wifi , i restored the tablet in samsung smart switch now everything works again as it should..i will hold out until we have a safe root for our T587P devices. Thank you
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Any updates on WiFi fix?
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Rpartin04 said:
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
Click to expand...
Click to collapse
A stock kernel has to be built from source.
Rpartin04 said:
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
Click to expand...
Click to collapse
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
DavidBeckett.db said:
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Click to expand...
Click to collapse
I didnt realize the firmware was behind a paywall, the correct link has been posted.
This is a proper root via the magisk patched boot. There is no reason to flash the recovery at all.
Rpartin04 said:
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Click to expand...
Click to collapse
Anyone who doesnt read the first post closely enough to locate locate the stock firmware being made to pay for it seems like a form of natural selection. Edit: or that would be the case were this the case, however, i posted the wrong link in the OP ( i had visited a lot to find the firmware, i misremembered which one was correct.)
ashyx said:
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Click to expand...
Click to collapse
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
arlyn said:
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
Click to expand...
Click to collapse
This as well is not a free deal. It would help out a ton if you just link these files to your account via Google drive, mediafire, ect....
EDIT!!!!
I didn't scroll all the way down... ignore me
arlyn said:
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
Click to expand...
Click to collapse
Did you edit it? If not must be going blind.
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Rpartin04 said:
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Click to expand...
Click to collapse
Haha, I didn't realize you had to subscribe to your own threads, I didn't know people were even replying in here for weeks. Thank you for attempting to compile, i know there are some tutorials on xda, i'm pretty sure an flashing an SELinux permissive kernel will fix the wifi issue with the magisk root. I do not know that I'll ever have the time or motivation to compile it myself, but I can help to test.
Thanks arlyn! Will definitely be trying this out.
Says root is not properly installled.... any ideas? I followed directions to a T... even flashed back to stock nougat and tried a 2nd time...
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
nmyshkin said:
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
Click to expand...
Click to collapse
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
Does this work on 16GB only or does this include 8GB version?
It should work on both, they run the same ROMs, only requirement is Lollipop+.
Edit: I'm making the assumption users know which ROMs accommodate the 512mb models. Obviously, the ROM needs to be functional for Magisk to work.
fddm said:
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
Click to expand...
Click to collapse
OK, no joy here. After waiting for a couple of hours to download a ROM (!) I finally put it all together. The system hangs at the "N" screen, never getting to the Cyanoboot screen. I tried this on an 8 GB tablet because I didn't want to mess majorly with my 16 GB one, but as you say, the result should be the same
BTW, there were no error messages I detected as the Magisk zip installed.
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
fddm said:
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
Click to expand...
Click to collapse
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
nmyshkin said:
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
Click to expand...
Click to collapse
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
fddm said:
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
Click to expand...
Click to collapse
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Your right, sorry, after testing again I can reproduce this error. Going to have a closer look, see if I can correct it. Thank you!
Edit: problem found, fix incoming
nmyshkin said:
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Click to expand...
Click to collapse
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
fddm said:
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
Click to expand...
Click to collapse
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
Anyway, I now have questions as I'm no magiskan I read about Magisk before and even tried it on a similar ROM (to no avail, of course), but there are many things I don't fully understand.
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
2. I need to install an SU manager, yes? MM seems to indicate that it can't find any. Seems like I recall it was based on the phh su so can I just install the manager app for that? Is that what I need to effect "root" or do I already have it?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
nmyshkin said:
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
Click to expand...
Click to collapse
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
fddm said:
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
Click to expand...
Click to collapse
Things are looking up I searched the AdAway issue and see there is a newer version that seems to solve the problem for people using Nougat ROMs (including someone running Magisk!). Worked like a charm. ES File Explorer seemed to have root access issues but I went into MM to see what the issue was and managed to manually turn on root access. Seems OK now.
As you say, part of this is getting used to it. I'm not seriously thinking this ROM is going to be good for the 8 GB tablet (for one thing I cannot tolerate the shutdown bug) but it's fun to see what's going on and try out this approach. Who knows? Someday there may be an Unlegacy AOSP 8.1 "mini-me" that will run (and maybe even shut down...) and I'll have the know-how to deal with it.
Thanks for your efforts. Sorry to have been a bit of a pain.
nmyshkin said:
Thanks for your efforts. Sorry to have been a bit of a pain.
Click to expand...
Click to collapse
No, you were perfect. You provided essential information and kept trying when you hit a wall, and we got working Magisk in the end. Couldn't be happier, thank you!
Updated OP since this thread became useful to track if magisk works with our stock ROM.
The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.
I suggest that you change the update channel to custom and set the address to 127.0.0.1
For the most recent Magisk version:
mickey36736 said:
I tested 19.3 on B01 oreo and it still bootloop.
Click to expand...
Click to collapse
Thanks for checking @mickey36736
rzarectha said:
It bootloops
Click to expand...
Click to collapse
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
raystef66 said:
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
Click to expand...
Click to collapse
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
rzarectha said:
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
Click to expand...
Click to collapse
You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
Not only on stock...
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Prophet 5 said:
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Click to expand...
Click to collapse
use the uninstaller zip first
Try 17.1. supposedly solves the bootloops.
bootloops are easily fixed by using the uninstaller first.
koftheworld said:
Try 17.1. supposedly solves the bootloops.
Click to expand...
Click to collapse
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
KwesiJnr said:
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
Click to expand...
Click to collapse
You have to use the uninstaller first and then flash 17.1.
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
pnin said:
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
Click to expand...
Click to collapse
Did you use the magisk uninstaller? If not, just reflash your bootloader
koftheworld said:
Did you use the magisk uninstaller? If not, just reflash your bootloader
Click to expand...
Click to collapse
Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?
I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.
That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]
Dark ROM. FTW. [emoji41]
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image).
Click to expand...
Click to collapse
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
Using stock anything above and v17.0 will bootloop using stock,
Just my 2cents, if that your issue just do the following:
-Download v16.7 first in case you don't have it yet, and move it to the SDCard.
* Head back to TWRP
* Flash v16.7 or your preferred release.
* You're good to go.
pnin said:
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
Click to expand...
Click to collapse
Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...
/data/magisk
/data/magisk.img
and files in /data/adb/
Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.
Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
pnin said:
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
Click to expand...
Click to collapse
I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
New beta version released. Still bootloop