Here's the whole story:
I was on an unofficial build of RR CM13, encrypted, using TWRP 3.0.2-1.
I wiped data, dalvik, cache, and flashed the newest Official RR 7.1.1 and open-gapps.
I boot into the new ROM and start setting stuff up.
I restore some apps' data using Titanium Backup, then reboot.
On reboot I'm greeted with the device setup screen
I reboot, wipe, reflash a bunch of times
A few times:
When I rebooted after using the system my PIN doesn't decrypt the system/data (booting into the system)
When I rebooted after using TWRP my PIN does decrypt (booting into the system)
At some point during this I try wiping everything from TWRP, but it freezes, goes black, and then the notification LED turns white. I hold the power button and boot back to TWRP.
Apparently wiping /data is the problem (everything else wipes just fine if I do them individually)
I boot back into the system, set it up, and do a full factory reset from there (after offloading my stuff from Internal Storage)
Back to TWRP, now no matter what I flash or restore, I don't end up booting into the system, only into TWRP
I've also tried TWRP 3.0.4-0 (which wouldn't decrypt my data), and I've reflash TWRP a few times.
How do I actually boot into my system? It's been 7 hours, and I'm losing my mind.
Deleted
Boot to your ROM through the power button...
Manually..
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Do what he said. You've already wiped your internal storage, so just start from scratch.
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
RustySpackleford said:
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
Click to expand...
Click to collapse
flash twrp
adb push os zip
adb push su
flash all , if needed format data.
This is what I have done yesterday,
edit: If u brick I don't take any responsibility.
Deleted
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
uttam.ace said:
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
Click to expand...
Click to collapse
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
bluuquthug said:
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
Click to expand...
Click to collapse
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
uttam.ace said:
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
bluuquthug said:
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
Click to expand...
Click to collapse
Your TWRP is working right!
go to TWRP/ Advanced/ADB Sideload
type "adb sideload /path/to/rom.zip"
Mate, recommend using ADB Sideload on TWRP itself is the only viable option you have. OR if that doesn't work and you still have the PIN issues, you should definitely use the Unbrick Tool and get everything back to Stock, and then reflash everything
Note: Using the unbrick tool will cause it to relock bootloader, so you're gonna have to start over again.
Cheers!
Related
Hello everybody,
I'm new, I hope someone can help me here ... I'm quite sure somewhere on these forums there must already be answers for my problem but I'm too dumb to find them.
I have the European? 2014 Moto X (not sure how to get the exact model now?!)
Unlocked bootloader, rooted.
Everything was fine, except today I got the 5.0.2 (?) OTA update ...
I didn't want to do it, but it kept asking. The moment I pressed "don't ask again" the phone rebooted
and now it's stuck at the white bootup screen (Motorola logo)
I somehow managed to get into the fastboot? mode once, by somehow pressing buttons at startup ... but, well
My two questions are:
1. Can I still backup my data, photos, textfiles, etc etc
2. How do I go back to a working system. (maybe without loosing my data)
Please tell me if it's possible, and how ... or please push me into the right directions.
But as I'm half panicking detailed instructions would be so fantastic.
Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Sent from my Moto X 2015 Pure Edition using Tapatalk
xKroniK13x said:
Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Click to expand...
Click to collapse
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!
psssss said:
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!
Click to expand...
Click to collapse
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Sent from my Moto X 2015 Pure Edition using Tapatalk
xKroniK13x said:
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Click to expand...
Click to collapse
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:
psssss said:
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:
Click to expand...
Click to collapse
If you've been contemplating installing a ROM, now would be a good time to do so. Just remember to wipe the data on the phone even though it doesn't boot. And CM OTA shouldn't cause issues like this, it just flashes the zip file in your recovery. Doesn't care about root or anything of course. Otherwise, if you'd like to do stock, just use MDM to get the firmware and flash away. Hope this helped!
Sent from my Moto X 2015 Pure Edition using Tapatalk
Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you
benjo22 said:
Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you
Click to expand...
Click to collapse
Try clearing your cache in a recovery/fastboot, or reflash the firmware! No guarantee the cache will fix it, but sometimes it will.
Sent from my Moto X 2015 Pure Edition using Tapatalk
Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version
benjo22 said:
Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version
Click to expand...
Click to collapse
That is answered in the FAQ thread... It is a guide for Moto G but it is applicable for this device too. http://forum.xda-developers.com/showthread.php?t=2876769
Sent from my Moto X 2015 Pure Edition using Tapatalk
@xKroniK13x
Hey, thanks for somehow guiding me through this :victory:
MDM didn't work, so I just went for the CM 12.1 nightly.
I also had concerns because in my attempts to clear cache etc etc I had "wrong partition size" etc etc
But CM installed without problems!
(Just one more question- there can't be any problems in the future because of messed up partitions, right? Does CM fix this by installing? Or should I stop caring, if it works, it works, right?!)
In fact, CM runs great, fantastic on my phone.
I lost some app data, and most annoyingly my SMS, but ...
Other than that, I'm really happy with CM :laugh:
@benjo22
Hey, I tried to fix it by clearing cache partitions from a fastboot TWRP (I don't know how you call it, I just booted TWRP without installing it)
This didn't work, so I tried to restore a nandroid backup,
but this made it even worse. (partition errors, only fastboot mode, etc etc)
Just booting with TWRP without installing also didn't work anymore,
so I put TWRP on the phone, which luckily worked, downloaded CM 12.1, installed it via TWRP,
never did it before, but I was lucky, it seems like it worked great!
Even kept my "SD CARD" data, but lost apps and some data ...
So I didn't fix the bootloop, but I hope I made it better, futureproof...
Glad you got up and running. CM shouldn't cause any future issues as far as partitions and such.
Sent from my Moto X 2015 Pure Edition using Tapatalk
I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.
Fastboot format userdata
flammenwurfer said:
I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.
Click to expand...
Click to collapse
Flash the stock recovery through fastboot. You can use the toolkit found here on xda forums.
Also you can format data in TWRP and then it should work, but you lose everything in internal storage, pics, music, all your own stuff.
Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.
flammenwurfer said:
Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.
Click to expand...
Click to collapse
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.
kinfam said:
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.
Click to expand...
Click to collapse
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?
Nobody121 said:
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?
Click to expand...
Click to collapse
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.
kinfam said:
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.
Click to expand...
Click to collapse
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:
Nobody121 said:
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:
Click to expand...
Click to collapse
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....
cultofluna said:
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....
Click to expand...
Click to collapse
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help
Nobody121 said:
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help
Click to expand...
Click to collapse
Options 1 and 2 on the toolkit is backup and restore apps and data..
cultofluna said:
Options 1 and 2 on the toolkit is backup and restore apps and data..
Click to expand...
Click to collapse
Nice haha, Ill try it later. Thank you really much
So there is currently no way to root and use TWRP without completely disabling encryption?
I'm having the same issues as the OP here. Whenever I go to use the toolkit it says "the system cannot find the path specified." Any ideas? I've tried within Android and in TWRP..
Sent from my ONEPLUS A3000 using Tapatalk
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)
Hi Friends
I just got the message from TWRP app that there is a new version available. I just installed it through the app and then rebooted the phone.
And now the problem: It boots only into TWRP. I can't boot anymore into OS! I tried to flash with adb the former TWRP version and vbmeta. But it doesn't help. It still boots into TWRP only.
One strange thingt is, when I reboot, it shows me the "relame - Powered by Android" page for afew seconds. Then the page goes away for a second or so and it restarts again, and goes into TWRP.
Please help me. I urgently Need the phone.
Thanks a lot!
https://forum.xda-developers.com/showpost.php?p=82131605&postcount=13
jhha said:
https://forum.xda-developers.com/showpost.php?p=82131605&postcount=13
Click to expand...
Click to collapse
Thank you! Unfortunately this is different problem and CN version.
Has anbody else an idea. Please!
Flash ozip stock, if it does not go up. format data and wipe cache & dalvik-cache. Reboot
zsonnguyenz said:
Flash ozip stock, if it does not go up. format data and wipe cache & dalvik-cache. Reboot
Click to expand...
Click to collapse
Thank you! Formatting data with the way, where you have to confirm with "yes" worked! Only this was necessary and it booted again to OS! Fortunately I could make a data backup with TWRP. But now the big question: I have a system with unlocked bootloader and C24 OS, as well as working FP. How to install now TWRP and Magisk, and how to get back the data?
@exadeci, @jhha
I guess you have experience in this. Would you be kind enough to share?
https://forum.xda-developers.com/showpost.php?p=81509817&postcount=78
https://forum.xda-developers.com/showpost.php?p=82131605&postcount=13
Sir Backe said:
Thank you! Formatting data with the way, where you have to confirm with "yes" worked! Only this was necessary and it booted again to OS! Fortunately I could make a data backup with TWRP. But now the big question: I have a system with unlocked bootloader and C24 OS, as well as working FP. How to install now TWRP and Magisk, and how to get back the data?
@exadeci, @jhha
I guess you have experience in this. Would you be kind enough to share?
https://forum.xda-developers.com/showpost.php?p=81509817&postcount=78
https://forum.xda-developers.com/showpost.php?p=82131605&postcount=13
Click to expand...
Click to collapse
I cannot flash magisk, it always bootloop, except the first time it is unlocked. And I am currently using the lieage rom. Did you flash it?
zsonnguyenz said:
I cannot flash magisk, it always bootloop, except the first time it is unlocked. And I am currently using the lieage rom. Did you flash it?
Click to expand...
Click to collapse
Yes I did. The canary version (see below the list on this page, section "Download"). Before I installed TWRP 3.3.1.13 and vbmeta.img, which I got from here (see section "To flash the TWRP" -> Modified VBMETA.
Hi Friends
After a long night with almost no sleeping I finally got a running system with TWRP 3.3.1.13, modified vbmeta.img, Magisk Canary and OS c24. For the first time in my life I bricked a phone just in various ways, one after the other. 2 horrible days are behind me, and i could only finally get a back a working system thanks to all of you, who supported me either in this thread or in various others where I was reading and actively asking questions, depending on the Problem I just had.
Thanks a lot to all of you. You are a great communitiy!
Last OS installed on the device was faulty and didn't boot properly and ran into alot of problems so I tried to install a new OS. Thing is, im not that good with this stuff, so I straight up went to bootloader, wiped everything there was to wipe and tried to flash gapps with the OS. It even may be in bootloop, but im not sure and don't know what that is exactly. I can't even flash a new ROM because the device is encrypted for no reason. ADB sideload didn't work, probably because there is no os on the device or because it wasn't put into developer mode. Some help would be amazing, maybe with just unlocking bootloader. I think i can handle installing OS.
mercule said:
Last OS installed on the device was faulty and didn't boot properly and ran into alot of problems so I tried to install a new OS. Thing is, im not that good with this stuff, so I straight up went to bootloader, wiped everything there was to wipe and tried to flash gapps with the OS. It even may be in bootloop, but im not sure and don't know what that is exactly. I can't even flash a new ROM because the device is encrypted for no reason. ADB sideload didn't work, probably because there is no os on the device or because it wasn't put into developer mode. Some help would be amazing, maybe with just unlocking bootloader. I think i can handle installing OS.
Click to expand...
Click to collapse
Not sure on encryption but wiping out everything should work.
I installed this ROM and it's working fine apart from couple of bugs.
If you can access TWRP give it a try.
PPGX5II said:
Not sure on encryption but wiping out everything should work.
I installed this ROM and it's working fine apart from couple of bugs.
If you can access TWRP give it a try.
Click to expand...
Click to collapse
I cannot even wipe everything, somehow it has worked before but now it doesn't. Just says that it can't wipe data and whenever I try to flash something, it can't even confirm the zip or whatever it's doing to it.
mercule said:
I cannot even wipe everything, somehow it has worked before but now it doesn't. Just says that it can't wipe data and whenever I try to flash something, it can't even confirm the zip or whatever it's doing to it.
Click to expand...
Click to collapse
Try to flash TWRP from above thread and then maybe try?
PPGX5II said:
Try to flash TWRP from above thread and then maybe try?
Click to expand...
Click to collapse
I can't flash anything, it won't let me.
mercule said:
I can't flash anything, it won't let me.
Click to expand...
Click to collapse
I mean using ADB command `fastboot flash recovery twrp.img`
PPGX5II said:
I mean using ADB command `fastboot flash recovery twrp.img`
Click to expand...
Click to collapse
the device doesn't show up on the devices list, so I don't think that will work