So as written in the title, i've tried flashing different Supersu versions. I also tried doing so on official oxygen os, cyanogenmod 13 and now currently using paranoid CM, it would get stuck in a boot loop everytime i tried to flash supersu. Any help there ? I'm sure i haven't got root access already !
gabytzu339 said:
So as written in the title, i've tried flashing different Supersu versions. I also tried doing so on official oxygen os, cyanogenmod 13 and now currently using paranoid CM, it would get stuck in a boot loop everytime i tried to flash supersu. Any help there ? I'm sure i haven't got root access already !
Click to expand...
Click to collapse
What version you using? You want 2.65 or higher .
Try the latest beta SuperSU and you will have no problem at all!
Thank you very much guys ! I've initially tried to flash 2.52, 2.56 and 2.65, none of them worked, it went well with 2.72 or w/e is that last one .
Try to change that supersu zip file and try other versions
If you haven't unlocked the bootloader then it won't boot into a modified system. To unlock the bootloader you need to reflash the stock recovery from here: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img. Once flashed, boot into OxygenOS, go to settings, go to About Phone, tap on "build number" until it says that you're a developer. Back to settings, go to Developer, and turn on OEM unlock. Now boot into Fastboot, and on the computer you used to flash TWRP in the first place, use the command "fastboot oem unlock". Then you can flash TWRP and use whatever rom you like or flash SuperSU on OOS.
Related
hello,
my current situation: i am on oos 2.2.3, not rooted, twrp 3.0.1-0 running.
i want to install a 3.x.x oos, version, i wanted to install 3.1.2 first, cause oneplus site i can install that directly form 2.2.3 (no such info on 3.1.3 and 3.1.4)
when i try to install with twrp, it says "this package is for "Oneplus" devices, this is a "ONE"
i think i am using the wrong twrp version. tried to install the newest (3.0.3-0), but this one doenst work, can not boot into it.
please help
Best is to fastboot flash old OOS 2 recovery
Then, with it, flash the 2.2.3. Reboot. then Flash 3.1.4. with the recovery
First you need to flash official oxygen os recovery for android 5.1 lollipop https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img Now you will be able to boot the phone. Now download and copy oxygen os 3.1.4 to internal memory http://downloads.oneplus.net/devices/oneplus-x/ Reboot into recovery and flash the rom.
Aftrr successful flash of oos3 boot into fastboot and flash latest twrp from twrp website.. This time it should work.
thanks, it work with the costum recovery.
on 3.1.4 i installed a slightly older twrp form sparkfire (3.0.2 i think), rooting and installing xposed worked fine though.
is it important to have the latest twrp?
and another question. at some point in my hours long struggel with updating my opx i softbricked it. i guess my bootloader was locked and i tried to install another recovery. i expected it to be still unlocked from my first rooting months ago. when does the bootloader lock?
dooglrig said:
thanks, it work with the costum recovery.
on 3.1.4 i installed a slightly older twrp form sparkfire (3.0.2 i think), rooting and installing xposed worked fine though.
is it important to have the latest twrp?
and another question. at some point in my hours long struggel with updating my opx i softbricked it. i guess my bootloader was locked and i tried to install another recovery. i expected it to be still unlocked from my first rooting months ago. when does the bootloader lock?
Click to expand...
Click to collapse
It is always recommended to use latest (bugs free)
You can use this one https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img latest as of now. And no u didn't brick ur phone. U flashed a new twrp for old bootloader version. Thts y u got stuck with oneplus logo. Its all oneplus things. Its always preferred to use stock recovery for updating bootloader which is safe. Check your bootloader state by giving this cmds "fastboot oem device-info"
cva_kabil said:
It is always recommended to use latest (bugs free)
You can use this one https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img latest as of now. And no u didn't brick ur phone. U flashed a new twrp for old bootloader version. Thts y u got stuck with oneplus logo. Its all oneplus things. Its always preferred to use stock recovery for updating bootloader which is safe. Check your bootloader state by giving this cmds "fastboot oem device-info"
Click to expand...
Click to collapse
Hmm isnt that for new BL as well ?
NielDK said:
Hmm isnt that for new BL as well ?
Click to expand...
Click to collapse
Yes it is. OP said that he's on OOS 3.1.3, so already on the new BL.
Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.
Hi,
there is something wrong with my Xperia Tablet Z. After upgrading from CyanogenMod 11 to CyanogenMod 12 a few Mouth ago the Custom Recovery i've installed before was replaced with CyanogenMod-Recovery. Because CM doesn't work very well i downgraded to Stock-ROM using Flashtool. Because i couldn't find a Way to root Firmware 4.2.x and higher i downgraded to 4.1.2 and rooted with towelroot. The Bootloader is unlocked (checked with *#*#7378423#*#*).
But when i try to install TWRP it failed. This is the error with Fastboot
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
All drivers are installed. I've tried this on Ubuntu 16.04 and Windows 7 with installed Flashtool and also with installed ADB Installer (https://forum.xda-developers.com/showthread.php?p=48915118#post48915118). I tried it with three usb cables and different usb ports.
It also doesn't work with TWRP Manager (https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=de) and the Official TWRP App (https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=de). TWRP Manager show me this error
Code:
Flashing recovery was unsuccessful. Either you already have thos recovery installed or another error has occuured. Would you like to attempt to recovery now?
When i try to reboot the App freeze.
The Official TWRP App seems to install the recovery ("was successfully installed"), but i can't reboot into recovery with VOL+ (also tried VOL-). The Table starts normally.
Maybe there is something wrong with my Tablet now? Is there any other Way to flash a Recovery or to flash a Custom-Rom or a pre-rooted Stock-Rom? As i said before i can't root it with a Firmware higher 4.1.x. Update with the internal Update fuction also failed. So at the moment i can use [email protected] or a higher Version without root.
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Hi,
after some years with my pollux_windy left untouched, I decided I'd install my first custom ROM. But I'm having serious trouble to do so, and it seems unsolvable to me after hours of despair (I've been trying for almost 10 hours now).
I was on Lollipop (firmware .222), first unlocked my bootloader, then rooted my tablet (using kingroot). Then I tried to install twrp, and the only way I managed to do this was through this "TabZ-lockeddualrecovery2.8.26" thing. Only, I couldn't manage to flash anything, ended up bricking my tablet.
I then flashed a stock 5.0.2 ROM (.454), retried installing twrp via the same method, and although I manage to access twrp, I get the same error each time I want to flash a new ROM (tried CM/LineageOS 14.1 and ResurrectionRemix v5.7.0), which is : "E: error executing updater binary in zip [insert name of the .zip]".
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
I'm completely lost in this... How can I get that damn recovery to work, and/or get a custom ROM ?
Edit : Alright, with a good 3 hours-long night and a lucky shot, I managed to install LineageOS ! I used twrp recovery (from the dualrecovery thingy-thing) to wipe clean the device, then tried to install the ROM. It gave me the same error message about updating binary. So I rebooted the device into fastboot (couldn't access the recovery anyway... not sure if it's normal), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device. On the bootlogo, I tried to enter recovery with Vol-, and it worked. i then flashed with ease the ROM. Maybe it will help somebody !
Hapaxx said:
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
Click to expand...
Click to collapse
yep, one just need to
fastboot flash boot boot.img
Click to expand...
Click to collapse
enter recovery and flash firmware zip, gapps, etc from it.
Root works now, but i can't install TWRP 3.0.2.0 (but XZDualRecovery works).
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Hapaxx said:
So I rebooted the device into fastboot (...), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device.
Click to expand...
Click to collapse
If i understand correct Hapaxx flashed the boot.img form the LineageOS 14.1 Image? I don't want to install a Custom-ROM. crDroid is for Nexus. Where can i download a Kernel with build-in Recovery for tabz? or can i use the same crDroid also for tabz?
how can i flash the recovery to fota? can i do this with the same *.img or do i need an other image?
i just unlocked my bootloader and i dont know what else to do, i would like to install lineage 14.1 but i dont know what path to follow, i also hit the whole command not allowed thing, and what Hapaxx said, i'm unable to understand, could someone give a clear set of commands to follow? please? what to do in order so i dont brick my tablet.
Hi PiereMallao,
i have the same Odyssey behind me! Sony Xperia Tablet Z SGP321 LTE (16GB)
1. First check Bootloader unlocked with Flashtools 0.9.18.6. Check!
2. Install SGP321_10.1.1.A.1.307_Unbranded.ftf with Flashtools 0.9.18.6. Check!
3. Developertools on. USB-Debugging on. unknown sources on. Check!
4. Root with Doomlord_Rootkit_v18.rar. Check!
5. Check with App "Root-Checker" in Google PlayStore. Check!
6. And now I try to install TWRP for 3 days !
First try with TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip its ok, but i come only once after the installation in the recovery mode. Afterwards I have it with Vol+ or Vol- tried. It always starts the normal system.
7. With Fastboot -
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
target didn't report max-download-size
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
How can i check Bootloader unlock ? In Android Tablet Z i didnt have a keyboard to put in the hex-code *#*#7378423#*#* ?
In Flashtools i checked Bootloader unlock so i have no idea at this Point.
What can I do ?
sorry, i have so solution for this problem. i have given up. theonly way i know to ceck the bl is unlocked or not is flashtool.
I'm having issues with this as well. Trying to install LineageOS 14.1, I can initially get twrp onto the tablet, flash LineageOS 14.1.. boot into it, set up (it is recommended to reboot the tablet once before flashing gapps) ...however, rebooting wipes twrp out. I'm not used to this FOTA thing (first i've ever heard of it) so not sure how to get twrp to 'stick' and not get wiped out
I got it installed this weekend. First secret was fastboot TWRP to boot, not recovery:
Fastboot flash boot twrp-------.img
Make sure you have the right TWRP image.
Then boot into recovery and TWRP comes up.
Flash lineage and gapps.
See:
https://forum.xda-developers.com/xp...de-tutorial-sony-xperia-tablet-z-lte-t3392831
bowguy said:
I got it installed this weekend.
Click to expand...
Click to collapse
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
x000x said:
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
Click to expand...
Click to collapse
I never did step 14. Looks straight forward. You should ask this question on that thread
bowguy said:
I never did step 14. Looks straight forward. You should ask this question on that thread
Click to expand...
Click to collapse
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
x000x said:
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
Click to expand...
Click to collapse
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
bowguy said:
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
Click to expand...
Click to collapse
Are you using twrp-3.0.2-0-pollux_windy?
x000x said:
Are you using twrp-3.0.2-0-pollux_windy?
Click to expand...
Click to collapse
Yes.
I never bothered with step 14 in the guide. It works fine as is.
P.S.
As per my post on the guide referenced, I installed Rashr and flashed TWRP that way. Seemed to work perfectly. TWRP now shows 3.0.2 which is correct version. No change to system boot. Nice app
Rootk1t said:
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Bro please give me link to twrp latest for sgp321 m going to unlock bootloader using" flash tool" is it ok
Please tell me how to flash recovary too
Is it ok if i root my tab after unlocking bootloader using king root ajnd flash using flashify
Is ressuraction remex stableto use tell me bugs
?
i had equal problem
FAILED (remote: Command not allowed)
i also have the same problem with my huawei chc u23 gplay mini bricked no recovery please help
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
buzzinkeegs said:
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
Click to expand...
Click to collapse
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
RNZL3R said:
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
that 1
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
While flashing the ROM through flashtool, deselect option FOTA-KERNEL, this will keep twrp as your recovery.
Also you can use X-GEN Rom which is based on latest stock rom to flash it from TWRP instead of flashtool
Should I flash TWRP now and then re-flash the UK ROM?
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
while flashing stockrom, uncheck FOTAKERNEL.sin in FLASHTOOL FIRMWARE SELECTION PANEL.
this way you can keep the twrp intact
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!