Related
Hi guys,
I have a full working TWRP for the G3 mini, G3 Beat, G3s, D722, D744, F470
install with an simple apk.
Only problem i cant bind in the sdcard, only normal storage.
If someone could help to activate the sdcard also, this were nice.
SonyBraviaEngine3:
http://www.mediafire.com/download/6z9yg1d3gooyz37/Sony_Bravia_3.zip
Bravia uninstaller: https://mega.co.nz/#F!cosCFALZ!-TxAUzHi9Aq-jJp2fj4OjQ
D722 V10D Firmware: http://www.mediafire.com/download/28a06j2d30wa9uh/D72210d_00.kdz
TWRP Recovery: http://www.mediafire.com/download/9bz3qq38z31zz4h/recovery.img
HTC Beats:
http://www.mediafire.com/download/fxzedlun5l9oi4n/AwesomeBEATSv3.zip
Downloadlink
http://www.mediafire.com/download/9bz3qq38z31zz4h/recovery.img
Great, now we need bypass for the bootloader.
Hello,
Thank you for your work, i'm not a develloppers but i'm really insterested by TWRP recovery Lg G3s
hoping that you will find assistance
Good luck
Okay so we now have root and a custom recovery which hopefully works. Now to the next steps for our G3 S (Mini, Beat.)
xGMERZ said:
Okay so we now have root and a custom recovery which hopefully works. Now to the next steps for our G3 S (Mini, Beat.)
Click to expand...
Click to collapse
I found in the samsung forum a flashable Sony Bravia Engine 3. I tested on our LG and it works.
The colors a more .....colored - and a little sharper.
I have also a Bravia away flashable zip that remove the Bravia3 if someone dont like the colorfull display.
btw i load up the V10D Firmware to download. A user from here want to reflash his phone
http://www.mediafire.com/download/28a06j2d30wa9uh/D72210d_00.kdz
Hi, I've already installed TWRP but when you say zip file, there's an img file, so can't flash it this way, also tried to flash via flashify but I'm on LB and I guess that's the problem.
That's ok for me with flashify and recovery Sony Bravia.
Now I will test the D722 V10D Firmware with twrp or flashify.
I shared my reviews later ^^
Edit :
Except a little problem with my account office 365,
everything is fine even my sd card is mount correctly
Have you flash the TWRP recovery with FLASHIFY ?
click flash recovery.
click choose file and pick the recovery.
thats it. in recovery you can flash zip files.
oh sry. i see the link for sony zip was wrong.
i correct it and put a link for the HTC Beats Update in the first post.
I tried to flash, halts on error, downloaded beats and when I open it also some sort of error occurs, besides, apk its like 1.7 mb, and zip is 200 kb, is that right?
thanks for the effort! going to try new beats mod with my drums!
tried home flash program Run ADB(comp.) and using FLASHIFY(phone). The same result, the phone boot in Fastboot!!!
where is the APK file ?
please write a detailed instruction ?
Which one are you trying to flash? With flashify I could not flash any but a twrp version that's not here, beats just used the apk and that was enough. Bravia could not flash, I guess there's something wrong with the upload..?
konsolen said:
click flash recovery.
click choose file and pick the recovery.
thats it. in recovery you can flash zip files.
Click to expand...
Click to collapse
OK i did it ! and it's work fine
Only a problem...TWRP DON'T READ MY SD CARD...! any help ?:crying:
konsolen said:
Hi guys,
I have a full working TWRP for the G3 mini, G3 Beat, G3s, D722, D744, F470
install with an simple apk.
Click to expand...
Click to collapse
And so. About recovery.
I found it through a program Flashify (with Play Market). wrote all ok. Prompted to restart in recovery - OK.
Next on the splash screen LG written on top of the text, something like fastboot command waits ... and so on. in recovery not entered.
Try to boot via adb - the same thing.
Write detailed instructions !!!
hi, sorry to step in, but I couldn't flash this twrp, I have d855, found a "signed" version and finally got it working, if this works for you I can uploade it
Nigel_Spur said:
hi, sorry to step in, but I couldn't flash this twrp, I have d855, found a "signed" version and finally got it working, if this works for you I can uploade it
Click to expand...
Click to collapse
Hi, please be careful. This device isn't similar to the LG G3 which is the device you have. Its a lower model. So it wouldn't have worked with your device. Thanks for the info though This is the LG G3 Mini or S or Beat.
xGMERZ said:
Hi, please be careful. This device isn't similar to the LG G3 which is the device you have. Its a lower model. So it wouldn't have worked with your device. Thanks for the info though This is the LG G3 Mini or S or Beat.
Click to expand...
Click to collapse
Ooops! as I get here from the lg g3 general didn't realize, though now I read it's all over.. (d'oh) well, the apk works for d855 too.. haha, would be awesome to see some bravia working too. cheers!
Konsolen....!!!! did you solved the sd problem ?!?!?!?!
pleaseee !
Hi to everybody
I'm doing this thread because I've seen that there's a lot of confussion about how to install all this things properly, and I think that concentrating the wide-spread information could help you to get rid of this. First of all I have to thanks @aaawqw and @Moyster for their great efforts.
This is going to be a recopilatory of several sources and personal tips to help you to do this the easiest way. I'm not responsible of bricked phones nor your personal problems.
Please, read the full tutorial before doing anything, to avoid bricks and those things.
PREPARE THE RECIPE
Download these files:
- Unlocking bootloader tool: HERE
- TWRP image from Moyster (creator of LOS14 for our device): here
- If you want to install a modified version of FlymeOS, use this one from Romul35 from 4PDA: here. Original post
- Last LineageOS 14 build: from this thread. PLEASE DON'T FORGET TO THANK THE DEVELOPERS
- GApps: here I recommend the nano option. Choose ARM64 and Android version 6.0.
Put those three last files into your internal memory. If you've got an microSD card, I recommend you to put them into it (it's safer and easier).
UNLOCKING THE BOOTLOADER
To unlock the bootloader go to:
- Kevin.MX @aaawqw) post: here
Finally we have a guide to unlock the bootloader of Meizu m2 note. We need Mediatek SP Flash Tool, MTK phone drivers and the images/bin files for unlocking. No modaco superboot, no fake tutorials any more
Now here's the guide:
1. Download the files I provide
Then unzip it. You'll get a folder with FlashTool, Phone drivers and unlock images.
2.Install drivers for Mediatek platform.
3.Flash the temp-unlock-secro.img via Flashtool. (secro row)
4.Flash secro.img, lk.bin, preloader_meizu6753_65c_l1.bin via Flashtool. (secro, lk and preloader rows respectively)
5.Disconnect USB data cable and power on the phone. If you see the "=>Normal boot" sign(it's quite small.......) in the left bottom cornor of the screen, then the unlock is done. You can now flash things in whatever way you like. The guide is over~~~
The full tutorial is here
The unlock tool is here
Thank you for testing&trying!
If you've seen this spoiler and didn't thank Kevin, please go to here and thank him. This motivates him and gives him the recognisement he deserves.
- Robot Hijau 97 Youtube video: here It isn't in English, but may help if you find any problem or get lost during the unlocking. Leave him a like if it helped you.
This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights )
THIS METHOD DOES WORK FOR M571H MODEL. DON'T WORRY, THE ONLY ONE THAT GIVES SOME ISSUES IS THE M571C.
The great user @aaawqw states "And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions"
Tips to unlock the bootloader easily:
- If you're going to do it from a Windows 10 or 8 pc, have in mind that to install unsigned drivers you'll have to unlock the feature in your pc. A guide to do this: here
- Select the images to flash and hit the Download button before connecting your Meizu (pressing Vol Down button). This will help you if it turns on and off and makes the flashing impossible.
- Download the guide or see the video to correctly follow all the steps. You don't want to lose your phone, don't you? Don't try to mix guides, because you may skip a step and brick your phone. The video and Kevin.MX guide are the same procedure, they both are safe.
INSTALLING TWRP
Once done this part, we'll proceed with the installation of TWRP recovery image. There are two ways, choose the easier to you:
- Flash TWRP from SP Flashtool (original idea from @widagdag. The post: here)
+Turn off your device
+ By using your pc or laptop, extract the TWRP zip for meizu m2 note, there's a file "recovery.img"
+ You can flash it via SP flash tool (clicking the recovery, then select the file)... then click Download, wait until finished!! (Check symbol)
+ You can reboot ur device now, unlocked bootloader and installed twrp!
*The profit is u didn't need to root first and install any flash tool such as Rash, FlashFire, Flashify, etc. saving you some time
Click to expand...
Click to collapse
- Flash the recovery image from Flyme:
+ Get root access (if you do, skip this step). You can get it downloading Kingroot: here. Just install this apk and follow the steps
+ Unzip TWRP zip into a known folder
+ Download Flashify from the Playstore
+ Grant superuser access
+ (Optional) make a backup of your current recovery going to backup tab
+ Tap Recovery Image
+ Choose a file
+ Find TWRP img that you unzipped before and flash it
Click to expand...
Click to collapse
INSTALLING CM AND GAPPS
We're close to the end of this post. The final step: installing your desired ROM and GApps. I will flash CM from the thread whose link is at the download section.
I hope you've put it into your memory (internal/external) as we said
Ok so:
- Turn off your phone
- Go into the TWRP recovery (Vol up+power)
- (Optional but recommended) Make a backup of Flyme, just in case you don't like the new ROM and would like to go back to Flyme. If it takes up too much memory, move it to your pc after making the backup.
- Go to Wipe menu
- Go to advanced wipe
- Select these:
+ System
+ Cache
+ Dalvik Cache
+ Data
- Swipe to do the wipe
- Go to install.
- Select your zip image (in my case the cm13 I downloaded).
- Install also the GApps zip file you downloaded
- Restart to System, and check what you've done.
Some final tips:
- Make the backup, seriously, it takes 10 min and you'll have a Flyme backup if you don't like CM.
- If you want to transfer all your apps and their data from Flyme to your new ROM, use Titanium Backup.
- If you want to install Xposed Framework, it's the same procedure: enter into TWRP, tap install, select the zip and swipe.
- This won't delete your images or videos, but I would recommend to transfer them to a microSD card or your PC.
- Yes, you need to do all this to install a custom ROM. Yes, even unlocking the bootloader. Don't try to skip a step if you aren't sure about what you're doing.
I think that's all, I'll update this post if I lost anything.
I hope this helped you to move into CM world. If you have any doubt don't hesitate to ask.
I know this seems exhausting, but trust me, it worths it. Welcome to the custom ROMs world in your Meizu M2 Note. Let the magic begin.
ADDITIONAL GUIDES
RELOCKING THE BOOTLOADER
If you want to relock the bootloader just follow this simple steps:
Flash the original recovery image from Flashtool of from Flashify (the steps are the same as installing TWRP). You can find this image here
From there, install an update.zip (download them from the official flyme web: here and put it into the storage )
Now you have flyme again with a locked bootloader.
INSTALLING FLYME WITH TWRP
It's very important that you don't install an update.zip from the original Flyme page, because you will cause a bootloop. To get the flyme updates, you can follow one of these two methods:
METHOD 1: 4PDA
-Download the modified zips from 4PDA: here]. Translate it to English. It's on custom firmware>Flyme
-Flash them from TWRP
METHOD 2: DO IT YOURSELF
-Download the update.zip file from the Flyme page
-Open it and remove the preloader- files
-Flash it from TWRP. It will give you an error: IGNORE IT.
Reboot and done, you've got Flyme and TWRP.
UNBRICK A PAPERWEIGHT
BIG THANKS TO @numpea FOR THIS:
This just a firmware that has all the partitions and can be used to unbrick to device using SPFlashtool
Here is the link:
FIRMWARE
- Flash temp_unlock_secro.img with sp flashtool like you do when unlocking the bootloader.
- When done, disconnect the device and add the firmware to sp flashtool. You need to select "format all+download", click on "Download" and connect the device. The flashing process will start. After it finishes, the device will start again.
You wil notice that you lost your imei number you can add it back by:
Using MTK Engineering Mode (does not requires root)
Open engineering mode » Click on Engineer Mode (MTK) » Swipe left to Connectivity » click on CDS Information » Radio Information
Click on phone 1 if you want to change your sim 1 or choose Phone 2 to change sim 2 IMEI, follow this guide:
For Phone 1: “AT+ EGMR=1,7,â€YOUR NEW IMEI NO†(make sure you add a space in between AT+ & EGMR)
For Phone 2: “AT+ EGMR=1,10,â€YOUR NEW IMEI NO†(make sure you add a space in between AT+ & EGMR)
Using Chamelephon (requires root, but much more easier)
Just copy the IMEIS from the phone's box and put them into the app.
hope this is helpful
Click to expand...
Click to collapse
I'll keep updating the info!
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !
Moyster said:
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !
Click to expand...
Click to collapse
Moyster xDD :laugh::laugh: Thanks to you, without you this wouldn't have been possible
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
Xtian Rey said:
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
Click to expand...
Click to collapse
Very true, thanks a lot. I introduced the platform and the Android version of GApps
Thanks nice guide... Very useful for everyone who want play and modified the M2 note.
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.
Mr0oHo0 said:
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.
Click to expand...
Click to collapse
I include this on the guide. I read it bricked the phone in several cases, but I'm glad yours didn't.
Thanks for your guideline , it helps a lot !
Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Another thing is, Kingroot is not suggested. It cannot be detected by Flashfire and some other tools. And cannot be replaced by SuperSU. So Kingo Root+SuperSU might be better.
aaawqw said:
Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C shoukd use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Click to expand...
Click to collapse
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers
This unlocking guide only works for M571 model.
Click to expand...
Click to collapse
Mine is M571H, can I proceed?
Qeemi said:
This unlocking guide only works for M571 model.
Mine is M571H, can I proceed?
Click to expand...
Click to collapse
Mine too and it worked. I can't assure you anything, but I think that the problem are m571C which are different. Good luck if you're going to give it a try!
Moyster said:
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers
Click to expand...
Click to collapse
See it. I'll give a try on m2 note(M571C, China Telecom). At least try to build twrp But seems my pc's hdd is not enough No space for source code
little problems.
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
dinkan01 said:
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
Click to expand...
Click to collapse
hi,which build of cm 12 you put in phone?
M571U
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much
venturaj said:
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much
Click to expand...
Click to collapse
It won't, the only problematic model is the M571C, have fun
LBA97 said:
It won't, the only problematic model is the M571C, have fun
Click to expand...
Click to collapse
How can I check which model my m2 note is..?
[email protected] said:
How can I check which model my m2 note is..?
Click to expand...
Click to collapse
Check the store page you bought it from. If you bought it from China, then probably it's a M571C. Good luck
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
HOW TO ROOT YOUR XIAOMI REDMI NOTE 4X MTK aka NIKEL
DISCLAIMER:
There might be more than 1 way to root this phone, this tutorial is based off of the procedure I used to root my phone. For your device's safety do not mix resources (downloads) from other threads with this thread. I first rooted when my phone was on MIUI 8.2 and Android 6.0.1 (It still works on higher versions of the software). Before continuing with the procedure, you are responsible for your phone and what you do to it, this thread worked for me but doesn't necessarily mean it will work for you as well if you don't follow the steps correctly or use different files. Nonetheless, I take no responsibility for what happens to your phone if anything goes wrong.
Requirements:Unlocked Bootloader (Click here for the procedure)
Custom Recovery "TWRP" (Click here to download)
ABD Drivers (Click here to download)
SuperSU (Click here to download)
(Download the latest .zip file called "Recovery Flashable" NOT any APK's)
Procedure:
1) Unlock your Bootloader (skip if already unlocked)
2) Download all the required files
3) Install the ADB Drivers
4) Move the downloaded SuperSU zip file to your phone's SD CARD or internal memory
5) Open the .bat file inside the NIKEL FLASHKIT folder
- Οnce the batch opens select the first option (FLASH ZCX-TWRP 3.0.2-X FOR Redmi Note 4 MTK)
6) Enable USB Debugging
- Enable developer options by clicking couple of times on the MIUI Version (Settings > About Phone)
- After you've enabled the developer options, go to additional settings and find "developer options"
- Enable USB Debugging
7) Connect your phone to your PC
8) Follow the instructions being printed on the NIKEL FLASHKIT batch file you've previously opened
9) After your phone has entered TWRP go to Install and find the .zip of SuperSU
10) Select the file then swipe to install and reboot, DONE!
norskaa said:
Hello everyone, I recently purchased a Xiaomi Redmi Note 4X and I'd like to root it,
Android Version : 6.0 MRA58K
MIUI Version : MIUI Global 8.2 | Stable 82.1.0 (MBFMIDL)
Is there currently any possible / safe way to root this phone? If so, please be kind and link me to a thread. Thanks in advance! <3
Click to expand...
Click to collapse
Well, you need an unlocked bootloader inorder to get root access.
Go apply for permissions if you haven't applied yet!
sachin n said:
Well, you need an unlocked bootloader inorder to get root access.
Go apply for permissions if you haven't applied yet!
Click to expand...
Click to collapse
Hello, thanks for your reply. I've just requested a bootloader unlock. What do I do after that in order to root my phone?
norskaa said:
Hello, thanks for your reply. I've just requested a bootloader unlock. What do I do after that in order to root my phone?
Click to expand...
Click to collapse
Flash the custom recovery (*.img) through fastboot command. For RN4 MTK there's limited custom recovery available, but you may consider trying Cofface TWRP or ZCX TWRP. After that you can install SuperSU or Magisk from custom recovery. There are plenty tutorials of flashing custom recovery and rooting device using TWRP in RN4 MTK device, search this forum or Google.
Devaz01 said:
Flash the custom recovery (*.img) through fastboot command. For RN4 MTK there's limited custom recovery available, but you may consider trying Cofface TWRP or ZCX TWRP. After that you can install SuperSU or Magisk from custom recovery. There are plenty tutorials of flashing custom recovery and rooting device using TWRP in RN4 MTK device, search this forum or Google.
Click to expand...
Click to collapse
Thanks for your reply, I've searched for video tutorials regarding flashing etc. All the videos I've found are about RN4 and NOT RN4X (which I own), does that make any difference?
norskaa said:
Thanks for your reply, I've searched for video tutorials regarding flashing etc. All the videos I've found are about RN4 and NOT RN4X (which I own), does that make any difference?
Click to expand...
Click to collapse
Doesn't matter sir, Xiaomi released 4/64GB MTK variant as wells, I assume you've the same.
Get TWRP for MTK variant of Redmi-note-4 and flash it. Nothing to worry.
sachin n said:
Doesn't matter sir, Xiaomi released 4/64GB MTK variant as wells, I assume you've the same.
Get TWRP for MTK variant of Redmi-note-4 and flash it. Nothing to worry.
Click to expand...
Click to collapse
Thank you so much for all your help! Ill post once I've tried it and successfully flashed my device, so other people with the same device could maybe find help here.
norskaa said:
Thank you so much for all your help! Ill post once I've tried it and successfully flashed my device, so other people with the same device could maybe find help here.
Click to expand...
Click to collapse
So, is it worked?
joppendaro said:
So, is it worked?
Click to expand...
Click to collapse
Yes
mr
mr flash twrp it is alive what mode fastboot
Thanks...
Sir.. Thanks a lot, I completed the whole process to install TWRP and root my redmi note 4x (Nikel) Ram 4GB internal 64 GB but I had to press volume down and power to force fastboot to come up then continue your step doubleclick the .bat file inside the NIKEL FLASHKIT folder...
MIUI Global 8.5 Stable 8530 (MBFMIED)
Yes, sometimes it works with the first try, other times you have to manually enter fast boot, and other you may need to reconnect your USB while in the process. It can be tricky at some point but it eventually works out
i tried few times and it is just not working for me. i dunno what n how... i unlocked bootloader from mi site. and nothing i try seems to work for me.
Kenannp said:
i tried few times and it is just not working for me. i dunno what n how... i unlocked bootloader from mi site. and nothing i try seems to work for me.
Click to expand...
Click to collapse
Could you give a more detailed explanation? Such as telling if you receive any errors , if the prerequisites installed correctly etc.?
norskaa said:
Could you give a more detailed explanation? Such as telling if you receive any errors , if the prerequisites installed correctly etc.?
Click to expand...
Click to collapse
nothing special. just when it says ur in twrp,nothing happens. i kept waiting even 20 mins n nothing.
repeated procedure few times and nothing.
but it worked,i changed usb cable and i went through,which is weird,usb works normal. copy/paste,charging...everything. but i didnt work for flasher.
however changed it and its all ok now
Kenannp said:
nothing special. just when it says ur in twrp,nothing happens. i kept waiting even 20 mins n nothing.
repeated procedure few times and nothing.
but it worked,i changed usb cable and i went through,which is weird,usb works normal. copy/paste,charging...everything. but i didnt work for flasher.
however changed it and its all ok now
Click to expand...
Click to collapse
Well at least the problem is solved now. Even though I think I mentioned in the thread that it might not work at all times and that you may have to disconnect the USB at some point. Anyways , good work
im glad that i found this thread.. sadly when i download the files.. its corrupted.. download several times.. same issue.. pls help.
xda111114 said:
im glad that i found this thread.. sadly when i download the files.. its corrupted.. download several times.. same issue.. pls help.
Click to expand...
Click to collapse
I've reuploaded the resources again. Here you go https://www.dropbox.com/s/52wb2dm1ludtfz8/Xiaomi Root.rar?dl=0
can someone help me. it's not booting into recovery mode. what should i do?
Does it still work in the latest version of MIUI 9.5.1.0? I have successfully installed TWRP but the .zip file might be outdated.
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
You don’t unzip the .tar files. Keep them as is.
secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.
is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse
fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.
framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY
framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.