I've had my tablet for some time, and a couple months ago I decided to root the device using THIS method, which worked perfectly. That led me to doing a little more researching, and I found THIS THREAD which will allow me to install Android version 4.4 KitKat, which has several advantages. However, every time I tried following the instructions, I always had errors. When I ran this command
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
I received this
Code:
C:\adb>fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
sending 'recovery' (7934 KB)...
OKAY [ 12.963s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 15.591s
I googled that error and I found a thread that says i have to have my bootloader unlocked, but I am not exactly sure how to do that. I checked THIS THREAD out, and installed the app, and after I ran it, I had to agree to a disclosure, and after I agreed, it led me to a page that repeated the disclosure and there was nothing I could do, no links or buttons to press.
I feel like I've missed some very silly step along the way, as all the threads are full of people who had no issue. I feel confident enough to finish installing the custom ROM if I can get past this point. So, if anyone could help me, I would really appreciate it!
Thanks!
Protocol Zero said:
I've had my tablet for some time, and a couple months ago I decided to root the device using THIS method, which worked perfectly. That led me to doing a little more researching, and I found THIS THREAD which will allow me to install Android version 4.4 KitKat, which has several advantages. However, every time I tried following the instructions, I always had errors. When I ran this command
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
I received this
Code:
C:\adb>fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
sending 'recovery' (7934 KB)...
OKAY [ 12.963s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 15.591s
I googled that error and I found a thread that says i have to have my bootloader unlocked, but I am not exactly sure how to do that. I checked THIS THREAD out, and installed the app, and after I ran it, I had to agree to a disclosure, and after I agreed, it led me to a page that repeated the disclosure and there was nothing I could do, no links or buttons to press.
I feel like I've missed some very silly step along the way, as all the threads are full of people who had no issue. I feel confident enough to finish installing the custom ROM if I can get past this point. So, if anyone could help me, I would really appreciate it!
Thanks!
Click to expand...
Click to collapse
As it turns out, the font size on my tablet was set to Huge, and that made the words on the unlocking tool too large to see the buttons to actually unlock the device. I fixed the setting, successfully unlocked the device, and was able to properly install KitKat! Even though no one replied to this thread, I couldn't have done it without the help of all the people from this forum, so thank you all!
Related
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
chemicalinferno said:
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
Click to expand...
Click to collapse
Not many of the technical people have unlocked their devices uses the htcdev.co method, most of us have used the revolutionary method was it was released first and seems to unlock more of the device than HTC does.
With that said, based on your above command and error message it would appear the bootloader is not unlocked. Are you sure the HTCdev.com method worked properly?
The only other method for loading a custom recovery, which could work using the HTCdev method would be through ROM Manager in normal android mode, or using my application, Flash Image GUI.
Both these methods just mentioned will require the recovery partition write access to be allowed while booted in normal android mode. This is definitely accomplished with the revolutionary s-off method, but I'm not 100% sure the HTCdev method allows this. If the HTCdev method does not allow recovery write access from normal android mode, then the worse that will happen is the application will say it flashed correctly, but it will not have worked.
Keep us updated as I'm curious how much write access the HTCdev method provides to the internal partitions... hope that helps!
chemicalinferno said:
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
Click to expand...
Click to collapse
Did you happen to skip step 17 prior to flashing recovery by chance?
"Step 17. Put your Evo 3D in fastboot mode by first going to Settings->Power and make sure "Fast boot" is checked off. (Again, yes)."
rleonard55: when i went to turn off the fast boot option I found that it was still off. So i just continued on with the process. I don't know if that has anything to do with the error I had or not.
joeykrim: I know my device is unlocked because when i load it in hboot mode it says unlocked at the top. However I don't know if it was unlocked properly. It may bmhave been an error in my process so I'm gonna try it from the start again. If that doesn't work I will be researching the other methods you mentioned and then proceeding with them.
I also realized I did not have usb debugging mode on So I'm gonna check if that changes anything. I appreciate both of you helping me with this issue. Thanks!
ok so i have tried relocking my device and then unlocking it again and i came out with the same result. i was going to try the GUI app you suggested but you need root access to use it which i do not have. i am trying to root my device through this method which requires cwm recovery. could i possibly temp root my device and then install the recovery through android mode that way? or would that risk bricking my device? also if i can go the temp root method in your application should i have the clear the cashe and dalvik cashe options checked or not?
looking forward to hearing from you
SOLVED!!!!
ok so i figured out exactly what was going wrong. it was a very specific issue. after you have unlocked the device and you are about to flash cwm you must load up hboot (power, vol down) then BEFORE pressing any buttons you must plug in your usb cable. THEN go to fastboot and press power to select it.
the order i was doing it in (hboot, fastboot, then usb cable) was causing the issue because when i did it the other way it flashed with no problem.
thank you for your help and thanks for the app i will definately be using it
chemicalinferno said:
ok so i figured out exactly what was going wrong. it was a very specific issue. after you have unlocked the device and you are about to flash cwm you must load up hboot (power, vol down) then BEFORE pressing any buttons you must plug in your usb cable. THEN go to fastboot and press power to select it.
the order i was doing it in (hboot, fastboot, then usb cable) was causing the issue because when i did it the other way it flashed with no problem.
thank you for your help and thanks for the app i will definately be using it
Click to expand...
Click to collapse
wow! frustrating it was such a small step but definitely good to know. i have a feeling you won't be the only person running into that issue.
thanks for posting back your solution and glad everything is working now!
Yeah no problem glad no one else will have to go through that.
I did run into one other issue or a possible issue. After I installed my root it gave me an "error code:0" now I do have root but I'm questioning if its a full root. I don't know what stuff is specifically locked by HTC's unlock method so I've just been researching to see what I can find out. All I know is in the video I watched his Su install continued doing different installations where mine stopped. I'll figure out what's going on eventually but if its a known issue that has a solution it would definately save me some time.
this is the official error i got
creatng SYSTEM:xin/su symbolic link...
E:error in /sdcard/su-2.3.6.3-efgh-signed.zip
(status 0)
installation aborted
dont know if it matters or not it was the very last step in the root and like i said i have root access. thanks in advance for any response
and yet again SOLVED! lol you just have to install it 3 times in a row
CWM
@ chemicalinferno.
I tried the method of loading hboot first that worked for you but sadly didn't work for me . Any other suggestions?
This may sound like a way off question, but did you unlock using revolutionary or HTC? If HTC when the option to unlock your device appeared (lock screen where you select yes/no) did your phone reboot or did you have to take out the battery?
Thanks
UPDATE: Soooo ****ing weird. I had been trying to get cwm to flash for have the day yesterday (5 hours)
I went to this sight here: http://forum.xda-developers.com/showthread.php?t=1239821
and tried this method. It also wouldn't work. Went to bed at 3 am this morning, woke up at 9:30 this morning. Sat down, looked at the screen, typed in the adb commands and low and behold **** started working??? I didn't do anything different than I did yesterday. But hey, I'm rooted with SU.
Craziest thing every.
chemicalinferno said:
and yet again SOLVED! lol you just have to install it 3 times in a row
Click to expand...
Click to collapse
Hey, I was reading your post and I'm still stuck not able to get past the "fastboot flash recovery cwm-4.0.1.4-shooter.img" step. I'm trying to do exactly as you. Can you tell me exactly what you did that im still stuck as it is stuck in sending 'recovery' <4832 KB>.... and wont do anything else. You are right this is frustrating
IM STUCK IN A BOOT LOOP AND WHEN I TRY TO FLASH FROM FASTBOOT IT GIVE ME AN ERROR WONT LET ME FLASH cwm img FROM FASTBOOT ??? PLEASE ADVISE IM hboot 1.50 AND ext4 RECOVERY BUT MY RECOVERY GOT MESSED UP SO IM TRYING TO FLASH cwm.img FROM FASTBOOT SO I CAN FLASH A KERNNEL AND GET BACK GOING THANKS
I had updated my HTC Evo 3D OTA from 2.3.3 to Android 4.0.3 software version 3.28.707.1 then unlocked it using HTC Method. Unlock success than I flashed recovery with CWM Shooter. Flash success but when I load recovery, the phone just boot up normally. CWM screen not loaded to load custom ROM.
Option 1. ROM Manager says:
You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instruction to root your phone.
Option 2. Superuser apps says:
su binary not found
Option 3. SuperOneClick v2.3.1
Stuck at Step 7. No respond at all.
And, at the command "CheckIfRooted" my device gave result 'false'.
I already tried USB debugging mode, and flash with other .img with other version of CWM. Still not working. Is there any other method to gain superuser access?
i can't flash the unlock token i get from htc using the official method and i've tried to redo the procedures for like a hundred times now, everything is set properly on my phone like fastboot is unchecked and debug mode is toggled on but everytime i just get the same error...i'm getting desperate
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s
can somebody shed some light?
tomanlam said:
i can't flash the unlock token i get from htc using the official method and i've tried to redo the procedures for like a hundred times now, everything is set properly on my phone like fastboot is unchecked and debug mode is toggled on but everytime i just get the same error...i'm getting desperate
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s
can somebody shed some light?
Click to expand...
Click to collapse
try this
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
Did you name the file adb? Try changing the file name of the folder you have fastroot in.
Calidrifter said:
Did you name the file adb? Try changing the file name of the folder you have fastroot in.
Click to expand...
Click to collapse
mnomaanw said:
try this
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
Click to expand...
Click to collapse
thx guys but the problem is i got adb and everything setup right, just that the token cant be correctly verified by my evo 3d...
Use fastboot. It'll work
Sent from my PG86100 using xda premium
Download the fastboot drivers. Put the phone on fastboot usb. Put the unlock.bin in the right folder. Usually c:/android. Enter the command prompt on your computer and change it to the right directory then type
C:/android> fastboot flash unlocktoken Unlock_code.bin
That should do the trick
Sent from my blazing fast 3d using xda premium
I know how you feel. I re-locked mine and now it wont even send the unlock_code.bin to unlocktoken...
Hopefully someone will be able to assist you better.
http://forum.xda-developers.com/showthread.php?t=1343114 try this...
N4LG4S said:
http://forum.xda-developers.com/showthread.php?t=1343114 try this...
Click to expand...
Click to collapse
thx, i tried it ytd but yet still no luck...it doesn't S-OFF at the last step and there're many "daemon not starting" (error?)
I have HTC EVO 4G LTE with the 1.22.651.3 update. I'm trying to use the instructions here http://forums.androidcentral.com/ht...s/192777-evo-4g-lte-1-22-651-3-root-easy.html as I haven't found a working method for this update at XDA.
When trying to use Regawmod boot unlocker and it fails when it gets to the part "retrieving unlock_code.bin" from HTCDEV stating that it's probably a problem with HTCDEV's website and no changes have been made. (I've used this method twice before with no problem with 1.22.651.1?)
Is it normal for HTCDEV to have problems a week at a time? f I can't get root I might as well give up and take the OTA updates.
Thanks!
Micro Maniac said:
I have HTC EVO 4G LTE with the 1.22.651.3 update. I'm trying to use the instructions here http://forums.androidcentral.com/ht...s/192777-evo-4g-lte-1-22-651-3-root-easy.html as I haven't found a working method for this update at XDA.
When trying to use Regawmod boot unlocker and it fails when it gets to the part "retrieving unlock_code.bin" from HTCDEV stating that it's probably a problem with HTCDEV's website and no changes have been made. (I've used this method twice before with no problem with 1.22.651.1?)
Is it normal for HTCDEV to have problems a week at a time? f I can't get root I might as well give up and take the OTA updates.
Thanks!
Click to expand...
Click to collapse
Go here and do it manually. It's a known problem with the automated tool. He's working to fix it. If you looked at the last few posts in his thread you'll see many people are having the same problem.
rawintellect said:
Go here and do it manually. It's a known problem with the automated tool. He's working to fix it. If you looked at the last few posts in his thread you'll see many people are having the same problem.
Click to expand...
Click to collapse
Okay. Found your manual setup post and manually unlocked the bootloader. (http://forum.xda-developers.com/showthread.php?t=1690919&page=152) (Shows UNLOCKED on boot screen)
These files are in the root of SDcard 1
openrecovery-twrp-2.3.3.0-jewel.img
RegawMOD_Rooter.zip
Phone in FASTBOOT USB
H:\Desktop\android-sdk-windows\platform-tools>fastboot flash recovery openrecovery-twrp-2.3.3.0-jewel.img
sending 'recovery' (7536 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.019s
Then phone locks up until holding power button shuts off.
Thanks!
Problem solved....
Micro Maniac said:
Okay. Found your manual setup post and manually unlocked the bootloader. (http://forum.xda-developers.com/showthread.php?t=1690919&page=152) (Shows UNLOCKED on boot screen)
These files are in the root of SDcard 1
openrecovery-twrp-2.3.3.0-jewel.img
RegawMOD_Rooter.zip
Phone in FASTBOOT USB
H:\Desktop\android-sdk-windows\platform-tools>fastboot flash recovery openrecovery-twrp-2.3.3.0-jewel.img
sending 'recovery' (7536 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.019s
Then phone locks up until holding power button shuts off.
Thanks!
Click to expand...
Click to collapse
After searching quite a bit I found this command.... "fastboot erase cache" Executing "fastboot flash recovery openrecovery-twrp-2.3.3.0-jewel.im then works.
H:\Desktop\Root new\android-sdk-windows\platform-tools>fastboot flash recovery openrecovery-twrp-2.3.3.0-jewel.img
sending 'recovery' (7536 KB)...
OKAY [ 0.997s]
writing 'recovery'...
OKAY [ 1.832s]
finished. total time: 2.832s
TWRP now loads in recovery and loads RegawMOD_Rooter.zip
I now have root! (Strange that it didn't wipe out the phone but root is verified!)
Edit dfownloads removed as the host started serving malware.
I dont have these files anymore, sorry, please dont ask for them
For other HTC devices supported by FacePalm, please see this thread: http://forum.xda-developers.com/showthread.php?t=2155069
Welcome to Facepalm S-Off for modern HTC phones.
Credits and terms:
Exploit by beaups, full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc. Additional thanks to indirect for Evo LTE testing.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
SuperCID for HTC Evo 4G LTE:
Code:
adb shell
su
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
1)
Code:
adb reboot bootloader
2)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
3)
Code:
fastboot flash zip PJ7510000-EvoLTE.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
7) Immediately issue the following command:
Code:
fastboot boot EvoLTE-rescue.img
(this is fastboot boot, NOT fastboot flash!)
8) Allow device to boot (may not fully boot on some custom roms)
Code:
adb reboot bootloader
9) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Indirect said:
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Click to expand...
Click to collapse
Probably worked on 3.16 for you as you already had supercid, I'm guessing the recent 3.16 update prevents changing the CID.
I dont think so because we've never used CID on this phone before. Only way to find out is to test.
Thanks for bringing this to the evo lte! I have windows 8 so this is gonna make it much easier compared to dirtyracun, thanks!
Thread cleaned. Going forward let's see about keeping it respectful in here.
You guys are freaking awesome thanks to all involved
Sent from my PoS MoPho
This is super easy! You guys rock. Thanks 4 this
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] <BB15> I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
BB15 said:
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Click to expand...
Click to collapse
jcase said:
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
Click to expand...
Click to collapse
Yeah, I wasn't bricked. After waiting for some time for my phone to reboot after running FacePalm I unplugged the USB and held the power button and it booted right up. Rebooted the bootloader and verified that I was s-off. Then I ran into the activation problem. Just flashed MeanBean and ran through the activation, now all is good. Your work on this is much appreciated.
Thankkssssss S-off already
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
mildlydisturbed said:
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Click to expand...
Click to collapse
here you go:
[SUPERCID] SuperCID For EVO LTE(Ruu to older firmware(not hboots))
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Finally have s-off!!!!
Thx to Facepalm S-Off I now have s-off. Finally,after a long year and a half of trying to get s-off.....
I must have been doing a few things wrong this whole time or Facepalm S-Off has done it right...
Rxpert said:
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Click to expand...
Click to collapse
I ran it while booted. No issues.
Sent from my EVO using Tapatalk 2
Fantastic job.
Already S off but props given.
Very nice.
Wow, this was incredibly easy. Soff in less than 2 minutes. I just followed the directions and flashed stock rom to be safe. $$ coming to you guys on payday!!
I'm really new to the whole rooting scene. I've had my OPX for a while now and want to give it a try. The problem is now that a lot of the guides are really old and I'm not sure if they're valid anymore, or the newer ones assume that the user knows what the hell they're doing (which I don't) and so are quite brief. Can anyone point me to a decent guide that I can follow or give me any pointers?
Have a look here: https://www.youtube.com/watch?v=KZaajUEybNM
But actually use these links instead the ones from the video (they are not for OPX and they are outdated):
TWRP recovery: https://eu.dl.twrp.me/onyx/twrp-3.2.1-0-onyx.img.html
For SuperSU use Magisk (SafetyNet not triggered ): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
raulx222 said:
Have a look here: https://www.youtube.com/watch?v=KZaajUEybNM
But actually use these links instead the ones from the video (they are not for OPX and they are outdated):
TWRP recovery: https://eu.dl.twrp.me/onyx/twrp-3.2.1-0-onyx.img.html
For SuperSU use Magisk (SafetyNet not triggered ): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks for the reply! I've gotten to the point of flashing TWRP on to the phone in fastboot mode but I get the following:
```
C:\Users\david>fastboot flash recover ./Desktop/Phone/twrp-3.2.1-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recover' (16274 KB)...
OKAY [ 0.512s]
writing 'recover'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.525s
```
Any idea what's going wrong?
malawi89 said:
Any idea what's going wrong?
Click to expand...
Click to collapse
Have you unlocked the bootloader?
In bootloader mode, type:
Code:
fastboot oem unlock
ferk said:
Have you unlocked the bootloader?
In bootloader mode, type:
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Yep I'd done that right before and it completed fine
malawi89 said:
Yep I'd done that right before and it completed fine
Click to expand...
Click to collapse
Ahh, now I see, you have a typo.
It's supposed to be "recovery" NOT like you have typed it "recover"
Genius! Or rather I'm a dummy. Thanks a lot for spotting that
Oneplus x root
Did it work?
If it did, could you explain me the procedure, please?