Hi any advice please. I have tried a couple of times to upgrade my bluspark twrp from the older one to the latest 9.91 version and I keep getting a soft brick. Whenever I flash it and try to boot to it screen goes black and white led is displayed. I am not sure but could this be something to do with the fact I am still on Oreo Aicp rom.
once flashed did u reboot back to recovery and reflash magisk
Thats where the brick happens once i flash twrp 9.91 and reboot recovery its a brick.
Happened to me too, had to use the unbrick tool. Now I am on codeworkx's twrp.
codeworks twrp what is taht is it the official. I thought bluspark was the best
mmmm happen somenthing similar im on OOS Pie but i will test custom rom (8.1 Oreo) flash firmware 5.1.7 reboot to bootloader then to recovery but only black screen and blue light flashing not sure what happen here any ideas? i used blu_spark 9.91 recovery now on work so no phone and my pc is dying too.
I realised why it was happening. I'm on Pie stock rom now and flashed it again and it works. It has to do with being on the correct fw.
Related
Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?
Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.
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 !
Hey all, so I did a stupid thing and did the OTA while I still had TWRP for recovery. Now I can only boot to recovery and am getting the dm_verity error. I have attempted to flash the stock recovery via fastboot, but no difference, still reboots into TWRP. I also tried flashing the full 4.0.2 and full 4.0.3 images, but same result. Any ideas?
which version of twrp were you on? try reflashing the latest modded twrp by eng.stk or the 3.0.4.1.
I am on twrp-3.0.2-1.28-oneplus3.img
rosswil said:
I am on twrp-3.0.2-1.28-oneplus3.img
Click to expand...
Click to collapse
Try flashing the latest one by eng.stk and then do a clean flash of the ROM you want.
Sent from my OnePlus3 using XDA Labs
I flashed the 3.0.4-1 TWRP from here https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 before I saw your last message. Then flashed the 4.0.3 full OTA (can be found in the same thread). One bootloop and everything started up (took about 5 min for first boot). Thanks for your help!
Hi dude, try this recovery (TWRP 3.0.4-1).
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
OOS 4.0.3 works well on my device with this recovery.
That happened to me once. All i did is turned the phone off completely and let it sit there for couple of seconds and turn it back on. No more recovery bootloop.
And if everything does not help... flash official recovery again and it will work fine. After one boot you can hop back to a RECENT TWRP
I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.
do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.
Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot
Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!
AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes
indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now
After trying to flash twrp 3.x in the twrp recovery menu, my screen does this funny thing on reboot. Has anyone seen this before?
When I try to flash [ROM][Official] AICP - 12.1 - N 7.1 amami from twrp 2.8.70 pretty much the same happens. I am not sure if this is a fault of hardware or software, I had to replace the screen multiple times now, but it works just fine on any stock rom...
Yes, BL is unlocked.
Any Ideas?
Maybe you should try a newer TWRP: v3.1.1-0
https://androidfilehost.com/?fid=961840155545588613