Related
Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!
if you have 3.0.2 i think there was a problem with early build causing this. there was a link posted for the new one that supposedly fixed it. or just use the 3.0.0 build.
Mike02z said:
Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!
Mike02z said:
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!
Click to expand...
Click to collapse
Here is the direct link for TWRP_dragon_3.0.2.0.img:
https://onedrive.live.com/?authkey=...&id=479EB75F5DD9DA59!131&cid=479EB75F5DD9DA59
Here is the complete folder: (TWRP flashable stock kernel)
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.
redukt said:
Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.
Click to expand...
Click to collapse
And connect everytime with PC to do a manual reboot via fastboot .. seems a little bit too much for a simple reboot. At least for me
A proper TWRP with proper vboot will boot always correctly, like the one from xceed.
Did you ever had to do a manual reboot on his version ?
Should be fixed at the root cause .. Hope you agree ?
Cheers
I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...
redukt said:
I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...
Click to expand...
Click to collapse
Interesting .. I did not have any reboot issues with xceed TWRP versions .. I had to use the fix fastboot option once, but this is another topic.
But thanks for your information ...
followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.
Annan Denis said:
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.
Click to expand...
Click to collapse
Wrong device thread .. anyway just restore "stock" ROM/recovery to make it working again.
Good luck !
Hi everyone,
I've a little problem with my OP3, Yesterday I removed my OOS 3.2.6 with TWRP, I flashed the stock recovery back and then I've sideloaded the last OOS 3.5.3 Community Build. Today i'd like to flash the TWRP, i launched the Fastboot menu, nothing seems to go wrong by flashing but when i tried to boot into the recovery, the "1+ powered by android" appears for 5 sec and then a black screen, no TWRP screen... Same problem by trying to restore the OnePlus stock recovery..
I tried "fastboot -w" (wipe) this bring back the stock recovery.
I tried to sideload, OOS 3.5.3, OOS 3.5.3, ResurectionRemix 2.7.4 and CM14 but all of them failed at 47% of work...
I'm thinking that there is a problem caused by an encryption...
"fastboot format userdata" didn't solve the problem..
I'd like to know wich partition i can format/erase to remove this encryption (Loss of data is not a problem for me)
Thanks in advance
Have you tried to flash the modified TWRP ?
Dushaine said:
Have you tried to flash the modified TWRP ?
Click to expand...
Click to collapse
Yes, same problem as TWRP
Same thing happened to me on flashing twrp after sideloading CB 3.5.2 through stock recovery. But flashing the modified twrp 3.0.2-19 solved the issue.
It is newer firmware that won't let you boot into TWRP.
Flash modified TWRP 3.0.2-19 recovery through fast boot.
Then flash <=3.5.0 firmware from here using TWRP.
Then flash this TWRP 3.0.2-0 image again from fast boot.
Then flash a ROM of your liking.
If all else fails, you can try this (flash stock recovery and 3.2.4 FW) WITHOUT relocking and then flash TWRP 3.0.2-0 from the above link to see if that works.
AJay27 said:
Same thing happened to me on flashing twrp after sideloading CB 3.5.2 through stock recovery. But flashing the modified twrp 3.0.2-19 solved the issue.
Click to expand...
Click to collapse
kgs1992 said:
It is newer firmware that won't let you boot into TWRP.
Flash modified TWRP 3.0.2-19 recovery through fast boot.
Then flash 3.5.0 firmware from here using TWRP.
Then flash this TWRP 3.0.2-0 image again from fast boot.
Then flash a ROM of your liking.
If all else fails, you can try this (flash stock recovery and 3.2.4 FW) without relocking and then flash TWRP 3.0.2-0 from the above link to see if that works.
Click to expand...
Click to collapse
I've been able to Flash the Modified recovery, and it booted. By flashing the patch, no problem detected, but after flashing the 3.0.2-0 same black screen as earlier...
So I flashed the modified back, and by trying to flash ResurectionRemix for exemple, no error happenned but, when boot begin, same problem as twrp ...
EDIT : Sorry guys, i didn't read correctly.. I was flashing the same patch ! The 3.5.3 and not the 3.5.0 !!! Normal TWRP is booting corectly now, i'll see for ROM !
Thank you very much to you !!
EDIT 2 : RR 2.7.4 BOOT !!! Thank you so much !
hi'
i have flashed cm14 nightly with aroma (gapps) on cm13 on my oneplus 3
now i couldn't go neither to recovery mode nor to current cm 14 rom to change my rom
i am out of ideas i tried in every possible way to my knowledge pleasee help me ........................
Flash the modified twrp 3.0.2-22 via fastboot.
Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
I had the same problem. Flashing modified twrp worked for me, thanks! But now if I to flash stock recovery (to install otas), I can't boot to recovery. E: oxygenos otas can be installed with twrp, so no problem anymore
plz send me the link of modified twrp
i coudnt find it on google properly plz
Try the link given by Demian3112. It works
THQ thq soon much.. Its working
Demian3112 said:
Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
Yes its working
Thank q very much
THQ thq soon much.. Its working
AJay27 said:
Try the link given by Demian3112. It works
Click to expand...
Click to collapse
THQ for ur valuable suggestion
My killer is back
Demian3112 said:
Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
Hii,
Still the problem remains same I will explain in detail
I am back to cm14.1 when I flashed twrp from the above link
When I tried to flash some other ROMs they are flashed but screen goes blank after oneplus boot animation,
If I flash 14.1 ROM it is working fine
From cmd non of the recovery where flashed only the above is working
Plz help me
I want to go back to stock soon
It's because of the system partition rewriting issue. People in the cm and other communities are already working on it. Basically the boot partitions get rewritten when we install the cm 14.1 . It happens to some variants while others works fine. Just the issue because of not enough testing. Will be sorted out within time.
What you can do is. Use flashify app or fastboot from your pc and flash your twrp back after installing and booting into the cm 14.1. You can use any twrp no modified versions needed as far as it is supported by your device model. Ciao. Hit thanks if i helped.
sanjumalik720 said:
It's because of the system partition rewriting issue. People in the cm and other communities are already working on it. Basically the boot partitions get rewritten when we install the cm 14.1 . It happens to some variants while others works fine. Just the issue because of not enough testing. Will be sorted out within time.
What you can do is. Use flashify app or fastboot from your pc and flash your twrp back after installing and booting into the cm 14.1. You can use any twrp no modified versions needed as far as it is supported by your device model. Ciao. Hit thanks if i helped.
Click to expand...
Click to collapse
ohhh
then what is the solution ?????
Thank you very much
Demian3112 said:
Get modified twrp here i assume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
I had the same problem as OP, got stuck with the CM 14 and did not like it (to early, to many bugs)
Wanted to go back to CM 13 but was unable to get into TWRP, and unable to flash CM13 back. Tried with fastboot and adb sideload, nothing worked.
The modified TWRP let me do i full wipe of the phone, (wiped Data, Dalik/ART, and system.) then copied the CM13 Stable release from here onto the phone, together with Gapps, and now everything is back to normal.
Again thank you, and thanks XDA! Somehow you always manage to save my ass after i messed with my device
Balaji Dasari said:
ohhh
then what is the solution ?????
Click to expand...
Click to collapse
Just flash the twrp image file again. The one you used before. Just flash it again. The same way you did back then.
HI,
Every time I flash a custom rom, it doestn't boot. it goes back to TWRP..
The only time it boots is when I flash rom with official twrp. And it boots with few things missing like magisk and other apps. Bluspark and codeworks doesn't boot.
Stock rom downloaded from oneplus also doesn't boot if the recovery is not official TWRP or the stock one..
Is there something I am missing?
Thanks...
Any ideas?
bibekdwa said:
Any ideas?
Click to expand...
Click to collapse
Try wipe data after reboot to recovery
Sent from my ONEPLUS A5010 using Tapatalk
I wiped data.. it boots.. but, without magisk. so had to flash magisk.. then, it doesn't boot..
MsuatafaKhatab said:
Try wipe data after reboot to recovery
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
bibekdwa said:
I wiped data.. it boots.. but, without magisk. so had to flash magisk.. then, it doesn't boot..
Click to expand...
Click to collapse
No problem to flash later
Sent from my ONEPLUS A5010 using Tapatalk
Did you try flashing stock ROM and the Magisk uninstall zip? This removes everything Magisk related. Then boot, only flash Magisk and see if that works for you
Macusercom said:
Did you try flashing stock ROM and the Magisk uninstall zip? This removes everything Magisk related. Then boot, only flash Magisk and see if that works for you
Click to expand...
Click to collapse
I am now back to stock OB1. Whatever custom rom I flash, it has been troublesome.
Last flash was successful, Audax rom. It had nothing missing. I flashed speaker mod, it worked. Then, I tried a custom kernel, blu-spark for nougat. it bootlooped to Qualcomm loader mode..
I have flashed many phones in the past without any problems for 4 years.. but this time it's not working for me..
Is there any 5T specific step that I am missing?
1. Unlock bootloader.
2. Flash Custom recovery. And boot it.
3. Wiped everything including internal storage.
4. Reboot to recovery.
5. Flashed Rom and then magisk and no-verity.
6. Wiped cache ( only sometimes)
7. After this step, the rom doesn't boot. It comes back to recovery using blu_spark and codeworkx... Stock twrp lets it boot but without magisk.
Then, I flashed magisk... It did the same thing, reboots to recovery.
I tried using magisk uninstaller. It didn't work.
Everytime it goes in to loop, I always had to format data because internal storage was not shown. (0mb)
I have never felt this noob...
Correct me if I'm wrong but is the no-verity zip necessary? Doesn't Magisk do that automatically? Just asking as I have stock ROM with Magisk and Xposed and never any issues.
Flash ROM and Gapps and then boot into system. After setting up, flash twrp again and Magisk. No-verity is needed only if you wanna flash certain unencrypted ROMs, in which case formatting data would also be required.
Did you do both fastboot OEM unlock, as well as enabling the option in developer options?
Macusercom said:
Correct me if I'm wrong but is the no-verity zip necessary? Doesn't Magisk do that automatically? Just asking as I have stock ROM with Magisk and Xposed and never any issues.
Click to expand...
Click to collapse
I don't know but without flashing no-verity zip, i haven't been able to boot any of these custom roms for 5t.
Flashing magisk on stock rom has also worked for me, but strangely I can't boot the custom roms on XDA. Liquid rom was successful but I wanted OOS custom roms. So far, I am unsuccessful.
Stock rom with magisk does fulfill my requirements.
But, I am curious about the problem I am having..
bibekdwa said:
I don't know but without flashing no-verity zip, i haven't been able to boot any of these custom roms for 5t.
Flashing magisk on stock rom has also worked for me, but strangely I can't boot the custom roms on XDA. Liquid rom was successful but I wanted OOS custom roms. So far, I am unsuccessful.
Stock rom with magisk does fulfill my requirements.
But, I am curious about the problem I am having..
Click to expand...
Click to collapse
exactly same situation here sir..
so many rom flashes in many htc devices and never ever had those problems
what's the missing point?
sardelisp said:
exactly same situation here sir..
so many rom flashes in many htc devices and never ever had those problems
what's the missing point?
Click to expand...
Click to collapse
I was having same issues so i flashed blu spark twrp and im golden hope this helps
forty9er said:
I was having same issues so i flashed blu spark twrp and im golden hope this helps
Click to expand...
Click to collapse
The only twrp I have tried is blu_spark anyway.
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://sourceforge.net/projects/resurrectionremix-ten/files/instantnoodlep/
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Changelog: https://get.resurrectionremix.com/ten/changelog/Changelog.txt
Be on OOS 10(both slots)(local upgrade last OOS 10 for slot b)
Flash twrp both slots(https://downloads.sourceforge.net/p...=cfhcable&r=https://forum.xda-developers.com/)
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
**UPDATE** this flash instructions work. I use these and ONLY these instructions. If you have a better way, good for you, but if you can't get it to boot, use these.
***UPDATE 2*** if you have installed Android 11 prior to installing this rom, you must msm back to OOS 10 and local upgrade OOS 10 again to slot b and only use Android 10 recovery
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
dladz said:
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
Click to expand...
Click to collapse
I've had no issues using latest twrp
jamescable said:
I've had no issues using latest twrp
Click to expand...
Click to collapse
Does it have oos cam?
areyouanand said:
Does it have oos cam?
Click to expand...
Click to collapse
Honestly, don't know. I don't use OOS can, but I don't think so
jamescable said:
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://get.resurrectionremix.com/?dir=ten/instantnoodlep
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Be on OOS
Flash twrp both slots
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
Click to expand...
Click to collapse
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Kollachi said:
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Click to expand...
Click to collapse
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
cultofluna said:
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
Click to expand...
Click to collapse
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
jamescable said:
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
Click to expand...
Click to collapse
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Kollachi said:
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Click to expand...
Click to collapse
[Mod Edit] Telegram link removed.
jamescable said:
[Mod Edit] Telegram link removed.
Click to expand...
Click to collapse
He is blind building from latest los source that's all. Respect him for doing that, but it's not 100% guarantee for a fully working rom.
jamescable said:
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
Click to expand...
Click to collapse
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. I think he meant to say reboot to recovery and not boot the twrp.img.
2. Yes you can boot twrp only. That's what im doing since OP7. But you will need to do this everytime you wanna flash something with twrp.
jamescable said:
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
Click to expand...
Click to collapse
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
cultofluna said:
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
Click to expand...
Click to collapse
It's in the pic I uploaded. Even the twrp dev said to flash it. So you won't have to fastboot boot anymore. Once you flash it. It's on your phone and won't go away when you reboot recovery
Every phone used to have a boot(kernel) partition, system partition, modem/radio partition, bootloader, userdata, and a few other INCLUDING recovery partition. Recently, the recovery was missing but now it's back. So we no longer have to have to boot twrp but flash it
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
oscarmaldonado said:
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
Click to expand...
Click to collapse
That is strange. I also have 2025. Try moving the rom to phone instead of usb device. Since this is an updated twrp may be an issue. However. I did NOT have OOS installed on both slots. I flashed latest OOS full rom, used OOS recovery to wipe data. Booted and then flashed twrp to both slots, flashed RR, reboot recovery and flashed magisk