Not sure if this is the right place to post this, but anyway, to the point. I rooted a Xperia SP with towelroot, checked with rootchecker and it was okay, after that I installed CWM and then flashed a ROM and probably CWM changed to TWRP with the ROM. Then I ran some debloater script the ROM maker had done and forgot to flash gapps (lol), or more like debloater script made the phone to reboot, so I let my phone to reboot and try to go back to TWRP and it just doesn't work... Touches won't get recognized. Also I just noticed that the root is gone. Looking for some help here now. Not so used to this stuff.
Things I've tried:
root again with towelroot, didn't work
flash gapps, didn't work
try to install recovery.img again with adb, didn't work(I just may aswell not know how to use adb anyway)
Ask if more information is needed. Thanks! Hope someone could help me.
zirhaze said:
Not sure if this is the right place to post this, but anyway, to the point. I rooted a Xperia SP with towelroot, checked with rootchecker and it was okay, after that I installed CWM and then flashed a ROM and probably CWM changed to TWRP with the ROM. Then I ran some debloater script the ROM maker had done and forgot to flash gapps (lol), or more like debloater script made the phone to reboot, so I let my phone to reboot and try to go back to TWRP and it just doesn't work... Touches won't get recognized. Also I just noticed that the root is gone. Looking for some help here now. Not so used to this stuff.
Things I've tried:
root again with towelroot, didn't work
flash gapps, didn't work
try to install recovery.img again with adb, didn't work(I just may aswell not know how to use adb anyway)
Ask if more information is needed. Thanks! Hope someone could help me.
Click to expand...
Click to collapse
1.You should have posted this in Q&A section
2.Never use towel root on lollipop because all ROMs are rooted by default.
To enable root Settings->Developer options->Root access->Apps and ADB
3.Dont try debloater script just yet. Use it when you are settled with ROM working.
4.Now what you need to do is
a.Boot into recovery and flash the latest TWRP zip.
b.Reboot into TWRP and wipe everything(data,cache,system but not external)
c.Flash ROM zip and gapps.
Hope this works:good:
Phoenix854 said:
1.You should have posted this in Q&A section
2.Never use towel root on lollipop because all ROMs are rooted by default.
To enable root Settings->Developer options->Root access->Apps and ADB
3.Dont try debloater script just yet. Use it when you are settled with ROM working.
4.Now what you need to do is
a.Boot into recovery and flash the latest TWRP zip.
b.Reboot into TWRP and wipe everything(data,cache,system but not external)
c.Flash ROM zip and gapps.
Hope this works:good:
Click to expand...
Click to collapse
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
zirhaze said:
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
Click to expand...
Click to collapse
Here, use this one:
http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230
Please remove the previous TWRP beforehand. If you are not sure on how to do so, can you attach me a link of where you followed the methods?
zirhaze said:
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
Click to expand...
Click to collapse
Since you said TWRP does not recognize touches. Here I present you 2 solutions:
1.Flash stock ftf and start over.
2.Flash FOTA and then flash tangerine kernel with TWRP recovery support via fastboot (v6.3 because newer versions cant be flashed using Fastboot)
zirhaze said:
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
Click to expand...
Click to collapse
Phoenix854 said:
Since you said TWRP does not recognize touches. Here I present you 2 solutions:
1.Flash stock ftf and start over.
2.Flash FOTA and then flash tangerine kernel with TWRP recovery support via fastboot (v6.3 because newer versions cant be flashed using Fastboot)
Click to expand...
Click to collapse
6.6 is the last version that contains the elf AFAIK, they should have kept one on cubeserver.eu
Here's the link: tangerine_v6.6
Zenith said:
6.6 is the last version that contains the elf AFAIK, they should have kept one on cubeserver.eu
Here's the link: tangerine_v6.6
Click to expand...
Click to collapse
There are 2 of them zips at my cubeserver folder
http://dl.cubeserver.eu/TechnoSparks/tangerine-stuffs/
TechnoSparks said:
There are 2 of them zips at my cubeserver folder
http://dl.cubeserver.eu/TechnoSparks/tangerine-stuffs/
Click to expand...
Click to collapse
Lol! My bad
I only checked Tomom's folder for tangerine.
Thanks
Related
Hi using the guide i've tried on both PC and terminal emulator and also flashing the zip in cmw but it still keeps booting to CMW 6.0.3.5
Any help?
thanks
Jamie
cramhead said:
Hi using the guide i've tried on both PC and terminal emulator and also flashing the zip in cmw but it still keeps booting to CMW 6.0.3.5
Any help?
thanks
Jamie
Click to expand...
Click to collapse
try flashtool > fastboot mode > flash recovery via select kernel to hot boot
edit:flash .img file
yeah i forgot to mentipon i also tried that.
fastboot flash recovery recovery.img
didnt work
oops my bad
the install recovery + option is gray on my flashtool. I cant see that option
mostafaz said:
try flashtool > fastboot mode > flash recovery via select kernel to hot boot
edit:flash .img file
Click to expand...
Click to collapse
cramhead said:
oops my bad
the install recovery + option is gray on my flashtool. I cant see that option
Click to expand...
Click to collapse
sorry for late responce
i did try some method and this one is good
try this hack and by flash via recovery and then flash your own recovery
latest recovery is here
installed both .............Nothing happened
I'll try an old TWRP
Which rom are you on?
try flashing TWRP 2.8.5 the official version and you should be able to boot to TWRP Recover.
http://forum.xda-developers.com/showpost.php?p=57718351&postcount=2
check the link, thats what Oliver has to say about the ROM, boot.img file
I tried flashing version TWRP 2.5 and that still did nothing. I'm using ANDROID 5.1. XPERIA Z(YUGA)
:crying:
cramhead said:
I tried flashing version TWRP 2.5 and that still did nothing. I'm using ANDROID 5.1. XPERIA Z(YUGA)
:crying:
Click to expand...
Click to collapse
Sorry only last question, who's ROM are you using and build date.
Hey, I believe it's the 5.1 version for this
build says full_c6603-userdebug 5.1 LMY47D eng.adrian.20150312.205659 test-keys
cramhead said:
Hey, I believe it's the 5.1 version for this
build says full_c6603-userdebug 5.1 LMY47D eng.adrian.20150312.205659 test-keys
Click to expand...
Click to collapse
Ok, so the ROM by pabx, This rom does not have in built arrangement for TWRP, you will have to compile it on your own.
You will find the steps here http://forum.xda-developers.com/xperia-z/general/turorial-add-twrp-to-boot-img-t2951658
and then flash TWRP to Fotakernel first and then flash boot.img
learn something new everyday
could I flash a philz recovery?
I can't find a .zip and can't do "fastboot recovery.img "the philz.img
thanks
I have not tried Philz, so i cannot give you an answer.
you may want to head over to this link http://forum.xda-developers.com/xperia-z/general/z-xzdualrecovery-qa-t2477769
Had the same problem.
TWRP Recovery wasn`t available after I flashed yuga.
Used "TWRP Manager" (only with root) which worked for me even when the app said that the installation failed.After rebooting I was able to enter TWRP again.
SO I installed This and I now have TWRP 2.8.
0! My rom won't boot any more, but who cares I can now install CM!..............I hope
have you tries the hack that oliver has on his thread http://forum.xda-developers.com/showpost.php?p=57718351&postcount=2
flash Olivers TWRP to FotaKernal and then from cm recovery flash the hack, reboot and enter recovery and check
I have not personally check but give it a try if you like.
Hi,
Well, I do have one recovery - cyanogen recovery, all others are gone.
With cyanogen I can't flash gapps or tangerine kernel,so I need my old ones back.
How it happened? Flashed FlexOS,after reboot they were gone, replaced by cyanogen recovery.
Any help would be appreciated.
Thanks
jaretti said:
Hi,
Well, I do have one recovery - cyanogen recovery, all others are gone.
With cyanogen I can't flash gapps or tangerine kernel,so I need my old ones back.
How it happened? Flashed FlexOS,after reboot they were gone, replaced by cyanogen recovery.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Use Rashr app from playstore to flash twrp or philZ
don't have app store, in fact don't have any gapps as cannot install them in cyogen recovery. when download apk. file get "Cant open" message.
jaretti said:
don't have app store, in fact don't have any gapps as cannot install them in cyogen recovery. when download apk. file get "Cant open" message.
Click to expand...
Click to collapse
you have to install tangerine if you use lollipop ....go into fastboot mode flash the kernel via fastboot ..reboot and you have twrp or philz
Is it possible that I've lost root? Cause that what root checker says.
P.s. managed to install gapps,will try flashing kernel like suggested tomorrow. Any links on how to do it?
Thanks guys
jaretti said:
Is it possible that I've lost root? Cause that what root checker says.
P.s. managed to install gapps,will try flashing kernel like suggested tomorrow. Any links on how to do it?
Thanks guys
Click to expand...
Click to collapse
i have did this from a long time so forgive if it didn't work for you>>> form pc download this zip that i uploaded it for you(https://mega.co.nz/#!y51TmaJR!gSWCWbF_6d3JKbkyjgNzhdfBoKakFvNCCFFvBfRl-cY) extract to C:\fastboot then move the kernel.elf if is it tangerine it will be like this (tangerine.elf)>>>press ctrl+shift on the keyboard and then press open command window here then type: fastboot flash boot (the kernel name.elf) when it's done type fastboot reboot
example: fastboot flash boot tangerine.elf
p.s you have to install the drivers for you phone google it or maybe(Connect your Xperia SP via USB. (Don't forget to enable USB Debugging)
Then run the Software (http://adbdriver.com/downloads/) and choose ur phone, which should be listed in the list.
i hope i helped with this if it didn't work so i'm sorry my friend for wasting your time
good luck :good:
Hi, it's all sorted now.
if someone have same problem this is what I've done:
installed gapps aroma as other packages wouldn't install from cyanogen recovery, then flashed super su also from recovery. after that I was able to install phillz recovery using rashr app from Google store. then from phillz installed tangerine kernel. all good now,
thanks everyone!
Using PRFCreator, I've just created a flashable zip for the latest stock ROM 5.1.1 (C5503) 10.7.A.0.222 & 10.7.A.0.222 Nordic Combined.
The flashable zip will install the followings:
1. C5503 Generic NCB firmware
2. Pre-rooted using SuperSU 2.49 Beta
3. XZDualRecovery 2.8.23
I've tested it on my ZR originally running 5.02 rooted stock LB ROM. I used TWRP 2.8.7.0 to flash it and I just wiped Dalvik and cache so data partition is untouched.
If you're also using Xposed, boot your phone for the first time, then reboot your phone into TWRP again to flash the official Xposed framework (http://forum.xda-developers.com/showthread.php?t=3034811, sdk22). For unknown reason, I need to uninstall and re-install the Xposed Installer to run it successfully.
Download:
10.7.A.0.222 https://mega.nz/#!BV5giBqQ!12WjY76wt9CayhsLV12ucSHnTxaBOuO7ufVbAz88xCc
10.7.A.0.228 https://mega.nz/#!Fcgj1YAZ!6S9-h2nzUOmm0yCfcGY_2tlTobcEZPwo-N9BUYkwMdc
** this firmware comes with Asian keyboard/IME which is not found in the earlier Russian version **
Hey please can you tell me how to fix the system mount issue? Or if you could post a flashable zip of the fixed revovery or something.....
Or does only cmw have the System mount issue, and twrp doesn't?
Even twrp has it
neildalal said:
Hey please can you tell me how to fix the system mount issue? Or if you could post a flashable zip of the fixed revovery or something.....
Click to expand...
Click to collapse
You can download the fixed dual recovery here.
https://mega.nz/#!gUIRgR4T!m7h13h0ZJ-ZHyR4AvIuLXbasNdigg-RpzLOs40Wd_hw
Who fixed it, or how did you do it?
itandy said:
You can download the fixed dual recovery here.
https://mega.nz/#!gUIRgR4T!m7h13h0ZJ-ZHyR4AvIuLXbasNdigg-RpzLOs40Wd_hw
Click to expand...
Click to collapse
Thanks a lot!!
wihushae said:
Who fixed it, or how did you do it?
Click to expand...
Click to collapse
It's not my work. I just downloaded it here.
http://forum.xda-developers.com/showpost.php?p=62792317&postcount=41
i need to root my xperia zr 10.7.A.0.222 but my save games will be delete
can you tell me away to save my saves games to recovery them when finishing my root
noorman said:
i need to root my xperia zr 10.7.A.0.222 but my save games will be delete
can you tell me away to save my saves games to recovery them when finishing my root
Click to expand...
Click to collapse
If you upgrade from 5.02 using this flashable zip, then you don't need to wipe data so your save games can be retained.
Will nuts built a new recovery with this fix?
wihushae said:
Will nuts built a new recovery with this fix?
Click to expand...
Click to collapse
Hi already have. Look at his site under dual recovery and beta.
I have stock 5.1.1 (10.7.A.0.222) installed, and the phone is in its original condition after a factory reset, with no root, no unlocked bootloader, etc. What should I do if I want to have root? So far I could only find complicated instructions involving downgrading to older android, etc. Any help would be appreciated.
Is it possible to flash this with flashtool?
I am unable to install it through TWRP, it finishes installing very quickly without any error, but apparently does nothing.
igvk said:
Is it possible to flash this with flashtool?
I am unable to install it through TWRP, it finishes installing very quickly without any error, but apparently does nothing.
Click to expand...
Click to collapse
What's your version of TWRP? I'm using the latest version of XZDualRecovery and TWRP should be 2.8.7.0.
http://forum.xda-developers.com/showthread.php?t=2261606
TWRP is from XZDualRecovery 2.8.21.
Its version is 2.8.6.0.
Will try to find a newer TWRP for Xperia ZR.
Actually, the recovery was installed with the whole system image, and I am unable to update it to 2.8.7.0 yet.
I finally managed to update to 5.1.1 with this package by updating the kernel image with TWRP.
Still TWRP version 2.8.6.0 was sufficient.
I try Your zip and not working for my ZR. In CWM i got error with UUIDs ("uuid link to system partition does not exist"). Then I create zip by myself with PRFCreator and all is working fine.
igvk said:
I finally managed to update to 5.1.1 with this package by updating the kernel image with TWRP.
Still TWRP version 2.8.6.0 was sufficient.
Click to expand...
Click to collapse
WeafyrCZ said:
I try Your zip and not working for my ZR. In CWM i got error with UUIDs ("uuid link to system partition does not exist"). Then I create zip by myself with PRFCreator and all is working fine.
Click to expand...
Click to collapse
I have no idea why the zip file doesn't work for you guys. But I'm glad you work it out yourself.
I'm on stock 4.4.4, UB, with xzdualrecovery 2.7.... Is it safe to flash this 5.1.1 rom? Or do I need to update the recovery first? Or should I upgrade first to 5.0, then this? Thanks for the help!
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
ExclusiveBFS said:
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
Click to expand...
Click to collapse
Through any recovery is the most easy way, but you have to unlock bootloader first.
Do you even know what it does?
Bigrrd225 said:
Do you even know what it does?
Click to expand...
Click to collapse
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
HUEguy said:
Through any recovery is the most easy way, but you have to unlock bootloader first.
Click to expand...
Click to collapse
My bootloader is unlocked. And I have the twrp. Thanks!
ExclusiveBFS said:
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
My bootloader is unlocked. And I have the twrp. Thanks!
Click to expand...
Click to collapse
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
XenolithicYardZone said:
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
Click to expand...
Click to collapse
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
ExclusiveBFS said:
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
Click to expand...
Click to collapse
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
XenolithicYardZone said:
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
Click to expand...
Click to collapse
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
XenolithicYardZone said:
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
Click to expand...
Click to collapse
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Tomoms said:
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
Click to expand...
Click to collapse
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Tomoms said:
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Click to expand...
Click to collapse
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
XenolithicYardZone said:
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
Click to expand...
Click to collapse
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
ExclusiveBFS said:
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
Click to expand...
Click to collapse
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
XenolithicYardZone said:
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
Click to expand...
Click to collapse
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
ExclusiveBFS said:
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Click to expand...
Click to collapse
Your welcome man. As a famous author once said, "Help will always be given at XDA to those who ask for it. "
XenolithicYardZone said:
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
Click to expand...
Click to collapse
Because CM recovery sucks
Tomoms said:
Because CM recovery sucks
Click to expand...
Click to collapse
True that!
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?
redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance
Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0
redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
mannulko said:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine
mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.