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
Related
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.
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.
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Apcoolboy said:
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Click to expand...
Click to collapse
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
There is flashable zip file which is extracted from miui rom only. So both way will be good as flash latest stable miui rom and then twrp > rom zip > gapps. Or twr0 > firmware zip (search in any custom rom thread you will get one) > custom rom zip > gapps.
Only benefit of flashing firmware zip is less time consuming and less file size (around 50mb) compare to full miui rom.
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
unlock your bootloader again it will run without problem..
Hi, I'm hoping someone can offer some assistance. I have an Elephone P9000 (normal version NOT lite) that has official Android 7.0 and I want to install LineageOS 14.1.
As per the instructions I used SP Flash Tool to downgrade the phone to Android 6 (Elephone_P9000_20170112) which worked fine.
I then attempted to install TWRP 3.2.1.0 which also appeared to work ok as I could boot into TWRP recovery and all looked good. However when I tried booting the phone normally it stuck at the white boot logo and would not progress any further.
So I reloaded the Elephone_P9000_20170112 rom again with SP Flash Tool after which the phone would boot normally and then tried installing TWRP 3.0.2.8 as I'd seen threads saying that this version definitely worked with the P9000. However this produced the same result that I could boot into TWRP fine but it would get stuck at the boot logo if I tried booting the phone normally.
I have also tried re-installing the ROM but unticking the recovery option in SP Flash Tool hoping that this would leave the working TWRP intact but this didn't work either.
When I try to boot into recovery I get the little Android laying down with a red exclamation mark.
So I don't know where to go now. I can get EITHER Android to boot or TWRP to boot but not both.
Just in case it is relevant, I am using SP Flash Tool v5.1804_Win in Windows 7 32bit. I don't have any SIM's in the phone and no SD card inserted.
Can someone point me in the right direction please.
Thanks
Russell
Try flashing stock rom with 810 at the end then twrp 3.2.1 and then aokp it is better then lineage
aljoscha81 said:
Try flashing stock rom with 810 at the end then twrp 3.2.1 and then aokp it is better then lineage
Click to expand...
Click to collapse
Thanks very much, that worked fine and AOKP looks really good. When it said install the latest Android v6 it obviously means the previous latest not the current latest
Just in case anyone else is having the same trouble I was:
Using SP Flash Tool load the 20160810 ROM available here: https://forum.xda-developers.com/elephone-p9000/development/rom-elephone-p9000-20160810-t3445897
Then, also using SP Flash Tool, load TWRP v3.2.1 which is available from here: https://eu.dl.twrp.me/p9000/
Then you can use the TWRP recovery to load whichever ROM you like (LineageOS, AOKP etc, etc)
Once again, thanks very much for your help.
:good:
EDIT: I figured it out myself, for anyone else in the same situation: I downloaded the proper Stock Rom for my phone and just flashed it with fastboot flash, no custom recovery was needed. After that I simply flashed Lineage OS and it's working like a charm.
Hello, I recently switched back to an Android phone that's why I'm a bit rusty. I successfuly installed Resurrection Remix on my Huawei P20 Lite.
After realizing there is no Notch support I decided to go back to stock or switch to Lineage OS.
Now I have two questions:
1) On the OpenKirin page it says you need stock EMUI 8.0 before you apply one of their ROMs. Does this mean if I want to switch to Lineage OS I need to go back to stock EMUI or can I go from RR to Lineage?
2) I downloaded 'Huawei P20 Lite-ANE-LX1 8.0.0.144(C432).zip' from xda which is supposed to be the stock rom. In the instructions on here it says I need to install TWRP. However OpenKirin says their ROMs don't work with TWRP. Can I just flash the stock firmware with adb fastboot, like described in the OpenKirin FAQ?
So my question basically is, what do I have to do to go from RR with stock recovery back to stock EMUI?
im in the same problem.. my fone brick in twrp logo.... i dont know how pass this logo
You can use eRecovery to download the entire ROM, you need the stock recovery and flash it with fastboot (fastboot flash recovery_ramdisk recovery_ramdisk.img) then go to the recovery mode and download the rom using WiFi and that's all, as advice I recomend you always make a system backup in the sdcard using TWRP. Sorry for my bad english. You can dowload the recovery here
Dre0x said:
You can use eRecovery to download the entire ROM, you need the stock recovery and flash it with fastboot (fastboot flash recovery_ramdisk recovery_ramdisk.img) then go to the recovery mode and download the rom using WiFi and that's all, as advice I recomend you always make a system backup in the sdcard using TWRP. Sorry for my bad english. You can dowload the recovery here
Click to expand...
Click to collapse
Thanks... i made this and everything ok now
illyx said:
EDIT: I figured it out myself, for anyone else in the same situation: I downloaded the proper Stock Rom for my phone and just flashed it with fastboot flash, no custom recovery was needed. After that I simply flashed Lineage OS and it's working like a charm.
Click to expand...
Click to collapse
What file did you flash in fastboot, the full-ota file?