This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Andriano24 said:
This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Click to expand...
Click to collapse
knox to 0x0?
DaniPS2002 said:
knox to 0x0?
Click to expand...
Click to collapse
Yeah that's what the app suppose to do
Andriano24 said:
Yeah that's what the app suppose to do
Click to expand...
Click to collapse
the app name is knox reset 0x0 (0)?
DaniPS2002 said:
the app name is knox reset 0x0 (0)?
Click to expand...
Click to collapse
Yes
Okay, let we know!
MarcusBS said:
Okay, let we know!
Click to expand...
Click to collapse
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Andriano24 said:
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Click to expand...
Click to collapse
What do you mean you can't turn systemless root into system mode?
ashyx said:
What do you mean you can't turn systemless root into system mode?
Click to expand...
Click to collapse
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Andriano24 said:
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Click to expand...
Click to collapse
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
ashyx said:
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
Click to expand...
Click to collapse
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Andriano24 said:
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Click to expand...
Click to collapse
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
ashyx said:
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
Click to expand...
Click to collapse
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Andriano24 said:
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Click to expand...
Click to collapse
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
[Deleted by me]
ashyx said:
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
Click to expand...
Click to collapse
Thank you for your time. But can you wrote the full steps below? Because I'm tired of getting into a bootloop only because I am not able to understand the instructions! You can do it only of you want to!
Secondary, the Knox Reset app has a plugin to make the success rate bigger of turning the 0x1 back to 0x0 (as far as I know) and the plugin needs system mode root :/
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Andriano24 said:
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Click to expand...
Click to collapse
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
ashyx said:
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
Click to expand...
Click to collapse
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Andriano24 said:
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Click to expand...
Click to collapse
Then you have a 50/50 chance of root working in system mode.
Also tbh I think this knox app is fake or it just fakes knox to 0x0 the same way Magisk can.
Related
I just got this in the mail today. Does anyone have any insights on how to unlock the bootloader and inject root? I had assumed 'fastboot' would work, but this has ODIN. I'm sure I could follow the steps on the original S4, but I don't know what the downstream effects will be.
Thanks!
----------------------------------------------------------------------------------
Edit: Please see this post: http://forum.xda-developers.com/showpost.php?p=44322019&postcount=70
Ok, just got done rooting my gs4 vzw dev edition. It was really pretty simple.
Steps from my win8 laptop were...
Install samsung drivers,
get adb working (android sdk doesn't seem to work on win8.. but just the adb files are all you need, google adb platform-tools or just use win7)
dl and push your superuser zip to the sdcard or external sdcard
dl odin 3.07 and extract to pc
dl and make tar.md5 of your favorite recovery. ( i personally like cwm )
Then all I did was... reboot phone in to odin mode... while phone is powered off, hold vol down + power
Start odin.exe
uncheck auto-reboot
click pda button, select the recovery file.md5
press start and let it finish, only takes a few secs...
once done.. reboot in to recovery, and flash the superuser.zip u pushed over to it.
Vol up + power to boot in to recovery. for me i just booted the phone normally... used "adb reboot recovery" then flashed superuser.zip.
reboot your phone and done.
good idea to make a backup while ur in recovery
If someone has hosting, i can send the files needed.
-r4ph
Click to expand...
Click to collapse
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
equake said:
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
It became available yesterday, and I got overnight shipping.
tithefug said:
It became available yesterday, and I got overnight shipping.
Click to expand...
Click to collapse
Is it full of VW blot ware?
rcb929 said:
Is it full of VW blot ware?
Click to expand...
Click to collapse
Yes. The only difference is that this has an unlocked bootloader by default.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
markwebb said:
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
Click to expand...
Click to collapse
Probably. But, I knew that would work.
tithefug said:
Probably. But, I knew that would work.
Click to expand...
Click to collapse
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
markwebb said:
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
The boot message you see when you power on your device means your device is rooted. I have the same exact thing when I rooted mine. I got mine from a Verizon store.
Sent from my SCH-I545 using xda app-developers app
tithefug said:
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
Click to expand...
Click to collapse
What backup method are you using: CWM or TWRP?
cmmelton2 said:
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
Click to expand...
Click to collapse
Search for the phrase used in the notification. It had to so with SEAndroid. You have to delete/rename KNOXAgent.apk, KNOXAgent.odex from /system and com.sec.knox.seandroid from /data/data
Have fun!
markwebb said:
What backup method are you using: CWM or TWRP?
Click to expand...
Click to collapse
TWRP. I installed it using the GooManager app.
tithefug said:
TWRP. I installed it using the GooManager app.
Click to expand...
Click to collapse
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
markwebb said:
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
Click to expand...
Click to collapse
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
tithefug said:
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
Click to expand...
Click to collapse
Was just wondering if you tried CM yet?
markwebb said:
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
I would also like to see the best/correct way to root the Developer Edition.
markwebb said:
Was just wondering if you tried CM yet?
Click to expand...
Click to collapse
Not yet. It's going to have to wait until tomorrow. Sorry.
Root method for 5.1.1 for the SM-G360T1 THIS WILL TRIP KNOX. If you don't want to trip knox don't use this. If you do use it and whine you tripped knox because you didn't read ,we will all point and laugh at you.
Named it TrapKernel because well its not my normal HispAsian Kernel and I listened to a crap ton of Trap Music while doing it.
Thanks to @g.lewarne and his root method with his Unibase and Unikernel for the s6 , we finally have root after I ported it over to us. So be sure to thank him for his work.
What's included:
Auto installation of root and busy box
Kernel set to permissive
Otherwise stock
So here's the deal. Stupid simple.
Before you do anything, go to settings/about device and tap Build Number til you unlock dev options. Go into dev options and make sure OEM Unlock is checked. Now you can continue.
1. Put Phone in Download mode
2. Open Odin
3. Connect Phone
4. Put Kernel in AP Slot
5.Flash it
6. Reboot and profit
Notes:
Download SuperSu from the Playstore. Its not included.
If at first it doesnt boot, pull the battery and reboot.
Video Tutorial of Installation Thanks to @TheDerekHarper
https://www.youtube.com/watch?v=RWm3auBSsU4
Download
Do NOT mirror this link. Period.
[FONT="Lucida Sans]links removed. It's outdated by years lol[/URL][/FONT]
[B][FONT="Lucida Sans Unicode"]Special thanks to:
@g.lewarne for the obvious reason of being awesome and his root method for the s6.
@bogarty for testing multiple tests
@Chainfire for SuperSU
[/B][/FONT]
Heres the kernel source that is set to permissive and will allow root if anyone wants to fork it and build a kernel:
Kernel Source Set to Permissive for the G360T1
Thank you for all your work!!!
Thanks For This Post And The Root For You And The Other Dude
ShinySide said:
Also mine
Click to expand...
Click to collapse
Glad It Works Just Tried It Out Hope We Get Some Roms And Other Stuff Like That
ShinySide said:
Also mine
Click to expand...
Click to collapse
2 in one day crazy!
please help m i could not root my samsung with this method
Deandre7452 said:
Glad It Works Just Tried It Out Hope We Get Some Roms And Other Stuff Like That
Click to expand...
Click to collapse
i could ot root mine,,root failed please help me:crying:
osk4rin said:
i could ot root mine,,root failed please help me:crying:
Click to expand...
Click to collapse
Hmmm...make sure that you have:
1) The "SM-G360T1".
2) The latest firmware: "G360T1UVU1AOFA".
3) Followed all the steps in the OP.
Sent from my SM-G360T1 using Tapatalk
osk4rin said:
i could ot root mine,,root failed please help me:crying:
Click to expand...
Click to collapse
Can't help if you're not actually going to explain how "root failed"
Root process fail (odin)
ShinySide said:
Can't help if you're not actually going to explain how "root failed"
Click to expand...
Click to collapse
Hi there!
I tried to root my Samsung g360t1 followed all the steps.
I have the latest firmware.,I attached the file on Odin and at the end at
The process fail.
Can I have your help please!!thanks
osk4rin said:
Hi there!
I tried to root my Samsung g360t1 followed all the steps.
I have the latest firmware.,I attached the file on Odin and at the end at
The process fail.
Can I have your help please!!thanks
Click to expand...
Click to collapse
Change usb ports, try different cable,make sure drivers are installed, disable/Uninstall kies if you have it installed on pc.
The flashing part went fine. then the reboot and I tried to install SuperSU. It wants to update the binary and has tried several times with no luck. then it reboots and now wont come back on..... I got this phone yesterday,
Longturd said:
The flashing part went fine. then the reboot and I tried to install SuperSU. It wants to update the binary and has tried several times with no luck. then it reboots and now wont come back on..... I got this phone yesterday,
Click to expand...
Click to collapse
Just dont update it. Su included is the absolute latest already. Its actually the 2.49 beta
ShinySide said:
Just dont update it. Su included is the absolute latest already. Its actually the 2.49 beta
Click to expand...
Click to collapse
root checker says its not rooted..... something went wrong but I have flashed a bunch of phones and Im pretty sure I did right.
.I have a notification that says "security notice" and some thing about unauthorized action. reboot to restore
Longturd said:
root checker says its not rooted..... something went wrong but I have flashed a bunch of phones and Im pretty sure I did right.
.I have a notification that says "security notice" and some thing about unauthorized action. reboot to restore
Click to expand...
Click to collapse
You are a G360T1 and not any other variant correct?
ShinySide said:
You are a G360T1 and not any other variant correct?
Click to expand...
Click to collapse
yes.... would not make that mistake
the phone is working but there is no root
Longturd said:
yes.... would not make that mistake
the phone is working but there is no root
Click to expand...
Click to collapse
Alright Ill look into it when I get a minute. Out of the 50 downloads over night no one else has mentioned.
ShinySide said:
Alright Ill look into it when I get a minute. Out of the 50 downloads over night no one else has mentioned.
Click to expand...
Click to collapse
does oem unlocking matter? in developer options
the phone is cool now. I killed the warranty and dont have root but there is hope
I'm getting an error message in download mode...
"Custom Binary(boot) Blocked by FAP Lock"
Sent from my SM-G360T1 using XDA Free mobile app
givo7192 said:
I'm getting an error message in download mode...
"Custom Binary(boot) Blocked by FAP Lock"
Sent from my SM-G360T1 using XDA Free mobile app
Click to expand...
Click to collapse
fix: open settings do a search for reavtivation lock and sign into your samsung account and disable it
error on dowload mode
ShinySide said:
fix: open settings do a search for reavtivation lock and sign into your samsung account and disable it
Click to expand...
Click to collapse
i have the same message!! on download mode
custom Binary(boot) Blocked by FAP lock
any help please master?
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
thanks, it worked for me. appreciate.
Your welcome.
What did u even use to root?
What build is this for?
It works with me....Thank you so much.
this works also on 320fn?
fraizzo said:
this works also on 320fn?
Click to expand...
Click to collapse
Sadly not
JustAnotherAndroid said:
What did u even use to root?
Click to expand...
Click to collapse
I used magisk
Sands207 said:
What build is this for?
Click to expand...
Click to collapse
I don't remember
Is this process can unlock the phone from sprint ?
No, call sprint, then ask to unlock
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
Simply turning off usb debugging will not throw your phone into a boot loop normally unless ou had some bad hardware or custom settings.. Only time ive seen that happen is by using data from other models. Easy way to get past it is to just take out your battery for a bit, replace it then boot into upload mode. Next youll have to try various combos releasing the buttons and presing again quickly to get back to the download mode. Alternatively boot into TWRP/STock recovery, use AT+ Commands or use a application that will boot back.
Awesome you found a little trick to simplify it ! Keep it up!
EDIT: Ohh i see.. you are on a custom rom / binary? I still have yet to have this happen but to a J700 with SynexOS on it.. Ill give this a try.
A lot of post are about being 5.x.x and can't access recovery mode but I am on 4.5.3 and I have flashed TWRP before on this firmware. I used the CM-11 rom and realized it's only Android 4.4.4 and needed Android 5.x.x well i flashed back to stock fire os and the stock firmware still 4.5.3
MY problem:
When i boot into recovery mode it just shows "Amazon" and reboots back to stock OS, I have root and flashify it just won't boot into recovery. Any help?
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
detesto said:
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
Click to expand...
Click to collapse
What version of FireOS?
If you're on 4.X root it and flash a working recovery with dd.
Rortiz2 said:
What version of FireOS?
If you're on 4.X root it and flash a working recovery with dd.
Click to expand...
Click to collapse
I'm on 5.6.1.0, I've found no way to root without recovery.
detesto said:
I'm on 5.6.1.0, I've found no way to root without recovery.
Click to expand...
Click to collapse
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Rortiz2 said:
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Click to expand...
Click to collapse
Not without recovery, all the guides require to flash an update via adb on recovery
detesto said:
Not without recovery, all the guides require to flash an update via adb on recovery
Click to expand...
Click to collapse
Sorry for the late reply.
There's ONE solution.. It's not easy...
You can flash recovery with aftv-tools but IDK the recovery adress. Maybe @bibikalka can help us?
detesto said:
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
Click to expand...
Click to collapse
detesto said:
I'm on 5.6.1.0, I've found no way to root without recovery.
Click to expand...
Click to collapse
Rortiz2 said:
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Click to expand...
Click to collapse
detesto said:
Not without recovery, all the guides require to flash an update via adb on recovery
Click to expand...
Click to collapse
Rortiz2 said:
Sorry for the late reply.
There's ONE solution.. It's not easy...
You can flash recovery with aftv-tools but IDK the recovery adress. Maybe @bibikalka can help us?
Click to expand...
Click to collapse
Unfortunately, the aftv-tools were patched a while ago, sneaky Amazon updated boot0 on firehd 2014 via some hidden data in either LK or TEE1. So that method won't work.
So without a recovery or root there are really no options.
Now, there is always the path to trigger the BootRom mode via some contacts (as on other models), but nobody spent the time yet to figure that out:
https://forum.xda-developers.com/fire-hd/general/diy-fire-hd-6-7-bootloader-unlock-t3894996
Pinging @k4y0z and @xyz` for completeness.
bibikalka said:
Unfortunately, the aftv-tools were patched a while ago, sneaky Amazon updated boot0 on firehd 2014 via some hidden data in either LK or TEE1. So that method won't work.
So without a recovery or root there are really no options.
Now, there is always the path to trigger the BootRom mode via some contacts (as on other models), but nobody spent the time yet to figure that out:
https://forum.xda-developers.com/fire-hd/general/diy-fire-hd-6-7-bootloader-unlock-t3894996
Pinging @k4y0z and @xyz` for completeness.
Click to expand...
Click to collapse
Dang. So there's no pic of the board? For see what points can be..
Rortiz2 said:
Dang. So there's no pic of the board? For see what points can be..
Click to expand...
Click to collapse
Plenty of good pics:
https://forum.xda-developers.com/fire-hd/help/jtag-t2933430
Also, one user tried to find the contacts, but was not successful. xyz' indicated where he thought the contacts might be:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
bibikalka said:
Plenty of good pics:
https://forum.xda-developers.com/fire-hd/help/jtag-t2933430
Also, one user tried to find the contacts, but was not successful. xyz' indicated where he thought the contacts might be:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Click to expand...
Click to collapse
Nice pics. Maybe with root you can easy brick it an enter to bootROM mode no?
Code:
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/dev/zero of=/dev/block/mmcblk0boot0
echo 'EMMC_BOOT' > /dev/block/mmcblk0boot0
md5sum /dev/block/mmcblk0boot0
Rortiz2 said:
Nice pics. Maybe with root you can easy brick it an enter to bootROM mode no?
Code:
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/dev/zero of=/dev/block/mmcblk0boot0
echo 'EMMC_BOOT' > /dev/block/mmcblk0boot0
md5sum /dev/block/mmcblk0boot0
Click to expand...
Click to collapse
But if I have root already, why would I mess with Bootrom??? I don't have amonet for this device, so I would essentially brick a working tablet
bibikalka said:
But if I have root already, why would I mess with Bootrom??? I don't have amonet for this device, so I would essentially brick a working tablet
Click to expand...
Click to collapse
Yep, you're right.. It needs to be ported to MT8135 and it qould be difficult... The only user that knows how to do it is @k4y0z.
He needs the tablet for test it.
reedradar said:
A lot of post are about being 5.x.x and can't access recovery mode but I am on 4.5.3 and I have flashed TWRP before on this firmware. I used the CM-11 rom and realized it's only Android 4.4.4 and needed Android 5.x.x well i flashed back to stock fire os and the stock firmware still 4.5.3
MY problem:
When i boot into recovery mode it just shows "Amazon" and reboots back to stock OS, I have root and flashify it just won't boot into recovery. Any help?
Click to expand...
Click to collapse
I managed to get the stock Amazon recovery on to the fire tablet on 5.6.10 using EX Kernel Manager and from there could sideload the OS i needed to get back in to TWRP.
Hi friends. Bought my one on *site name*. China version. How to install Magisk root? I tried to boot patched boot.img... didn't help
have you unlock your phone?
AmbazidA said:
have you unlock your phone?
Click to expand...
Click to collapse
Yea
Rezinochka said:
Yea
Click to expand...
Click to collapse
okay, was the flashing of patch boot image not successful? or what error did you find?
AmbazidA said:
okay, was the flashing of patch boot image not successful? or what error did you find?
Click to expand...
Click to collapse
In adb it wrote "OKAY". But in magisk root haven't installed.
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
If for some reason it’s not already installed, install it.
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
Sorry, didn't understand wdym
Sirs. With your permission, we will continue tomorrow morning. I am forced to leave you for an indefinite period for the time being.
Ok. Good morning "Vietnam"
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
I didn't understand wdym
Is the magisk app currently on your device?
If so, enter it, and clcik on the install button. Then click on”direct install”
Arealhooman said:
Is the magisk app currently on your device?
Click to expand...
Click to collapse
Yes
Arealhooman said:
If so, enter it, and clcik on the install button. Then click on”direct install”
Click to expand...
Click to collapse
I patched boot.img earlier
this video will walk you through rooting the Redmi Note 12
-
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
Thx, i will try
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Rezinochka said:
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Click to expand...
Click to collapse
it will flash to whatever your current partition is set to. some will be set to the _a partition and others will be set to the _b partition. it all depends on how many OTA updates you have installed (or if you've manually switched partitions for some reason)
the video does work, my Redmi Note 12 is rooted right now
IDK if it will work or not. But at least you could try. Someone suggested to patch init_boot.img on the Redmi note 12 4g forum.
Actual Post