I was using my Galaxy S7 (G930W8) to profile an app I was working on a couple of days ago and my Developer Options menu disappeared somehow, I enabled it again and went and enabled USB debugging but I failed to notice that the OEM Unlock setting had reset itself (How is this even possible to do on a custom rom?!)
Now my phone was rebooted and it can't boot due to TRP lock (Was running TWRP and custom rom)
I managed to flash the stock recovery via ODIN and I am able to boot into it, but now I'm not sure what to do.
How can I backup my data from this device? I have some photos that aren't backed up to the cloud, my signal message history, and most important MY GOOGLE AUTHENTICATOR DATA! I know it was stupid to not back most of this up and I won't make that mistake again.
Can I somehow flash the stock rom and boot it without wiping data? Is there some magic recovery software that will work in this case? I can't seem to connect with ADB while in recovery mode (unless I choose sideload but then it only shows up as a sideload device to ADB). I also tried fastboot boot twrp.img but fastboot isn't detecting my device while it's in download mode.
I don't know how to attach a bounty to this but I will pay for a solution that allows me to save my data.
Paid app that works fine.
I am desperate, some of the photos and videos relate to a car accident I was in so I really need them, the rest are my kid and dogs and I can't make those memories come back.
I'm also open to spiderboard solutions to get my data back, if that's the only viable solution will do it..
you cant boot into twrp ?
Chesminty said:
I don't know how to attach a bounty to this but I will pay for a solution that allows me to save my data.
Paid app that works fine.
I am desperate, some of the photos and videos relate to a car accident I was in so I really need them, the rest are my kid and dogs and I can't make those memories come back.
I'm also open to spiderboard solutions to get my data back, if that's the only viable solution will do it..
Click to expand...
Click to collapse
what recovery is it? maybe there is a solution
I can't boot into TWRP because of the FRP custom binary lock, I can flash a recovery through ODIN but my understanding is only stock recovery will actually load due to the OEM lock but if I'm wrong please tell me.
It's currently on the stock samsung recovery.
Chesminty said:
I can't boot into TWRP because of the FRP custom binary lock, I can flash a recovery through ODIN but my understanding is only stock recovery will actually load due to the OEM lock but if I'm wrong please tell me.
It's currently on the stock samsung recovery.
Click to expand...
Click to collapse
no no no, go to stock recovery and enter "adb pull /sdcard/"
Related
So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?
coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?
Hello, Im hoping that someone with Huawei expertise can assist me. I was trying to customize my rooted device by download and installing Xposed Installer / Framework and a multiwindow zip file. All was well until I entered recovery mode and used TWRP to flash the zip file. After reboot, I wasn't able to get to my home screen. The screen flickered multiple times as if it was trying to pull it up but was unable. I wasn't able to enter TWRP mode and my adb/fastboot program wasn't able to recognize the phone. The only options I was able to access were the internet and the Settings of the phone. The menu options were available but limited as well. The phone would not read the SIM card but was able to read the SD card. Trying to back up data was not possible as HiSuite was unable to detect the phone. As a last recourse, I did a hard reset BUT the phone is still flickering when trying to access the home screen. The only positive is that I am now able to access TWRP and adb/fastboot are detecting the phone. Any suggestions as to how to get my phone back operating like normal again would be greatly appreciated!!
childress said:
Hello, Im hoping that someone with Huawei expertise can assist me. I was trying to customize my rooted device by download and installing Xposed Installer / Framework and a multiwindow zip file. All was well until I entered recovery mode and used TWRP to flash the zip file. After reboot, I wasn't able to get to my home screen. The screen flickered multiple times as if it was trying to pull it up but was unable. I wasn't able to enter TWRP mode and my adb/fastboot program wasn't able to recognize the phone. The only options I was able to access were the internet and the Settings of the phone. The menu options were available but limited as well. The phone would not read the SIM card but was able to read the SD card. Trying to back up data was not possible as HiSuite was unable to detect the phone. As a last recourse, I did a hard reset BUT the phone is still flickering when trying to access the home screen. The only positive is that I am now able to access TWRP and adb/fastboot are detecting the phone. Any suggestions as to how to get my phone back operating like normal again would be greatly appreciated!!
Click to expand...
Click to collapse
You'll have to fastboot flash back the boot.img, system.img, and userdata.img from the stock B006 rom. I don't have a link to it but you can probably find it by searching this forum.
ajsmsg78 said:
You'll have to fastboot flash back the boot.img, system.img, and userdata.img from the stock B006 rom. I don't have a link to it but you can probably find it by searching this forum.
Click to expand...
Click to collapse
I figured I may be able to fastboot flash firmware 702-L B006 but cant seem to find a download for it anywhere. Does anyone have straight forward instructions/link? I tried the 702L B003 by letchsky download but it had a note that you couldn't use TWRP. Can I use ADB instead?
UPDATE: I did a hard reset using TWRP and accidentally wiped the internal drive. It still has TWRP and can be recognized when connected to my pc but it cycles during booting since there isn't an OS on the phone now. When I hook up my phone though, it now shows 703L vs 702L. Any thoughts/suggestions???
I just got the phone and booted up once and then installed TWRP and this happened.
like the title says phone is stuck in bootloop (when in Odin patching TWRP i forgot to root it first which i think is the cause) and i cannot do anything to it :\
When i try the "hard power-off" power+voldown it does nothing since it loops pretty fast. Also i cannot get into recovery or download for some reason (holding voldown/up+power just when the phone rumbles).
So there the phone has been looping and rumbling for 2 hours now... Anyone has any fix for this? Or any help is much appreciated! :]
DARKKi said:
I just got the phone and booted up once and then installed TWRP and this happened.
like the title says phone is stuck in bootloop (when in Odin patching TWRP i forgot to root it first which i think is the cause) and i cannot do anything to it :\
When i try the "hard power-off" power+voldown it does nothing since it loops pretty fast. Also i cannot get into recovery or download for some reason (holding voldown/up+power just when the phone rumbles).
So there the phone has been looping and rumbling for 2 hours now... Anyone has any fix for this? Or any help is much appreciated! :]
Click to expand...
Click to collapse
Keep the Download mode button combo held in until the phone reboots twice, hopefully the 2nd time into download mode
Vol Down & Home & Power
*Detection* said:
Keep the Download mode button combo held in until the phone reboots twice, hopefully the 2nd time into download mode
Vol Down & Home & Power
Click to expand...
Click to collapse
Thanks a lot! Now i am out of the bootloop and and seems like it is booting up too (hopefully, gotta edit this after that)
Did not boot (waited for 30+ minutes) but now i am transferring mod via adb and hopefully after installing that it works
I forgot to "Enable OEM Unblock" from developer options though, hopefully that does not screw things up :\
Yes you need to enable OEM Unlock before flashing anything custom, otherwise your bootloader is locked
And you need to keep OEM unlock enabled while you are running custom
If you can get into download mode, you might need to flash stock again before continuing so you can enable OEM unlock
*Detection* said:
Yes you need to enable OEM Unlock before flashing anything custom, otherwise your bootloader is locked
And you need to keep OEM unlock enabled while you are running custom
If you can get into download mode, you might need to flash stock again before continuing so you can enable OEM unlock
Click to expand...
Click to collapse
Damn, i could not get into stock anymore. I tried to install root and other things mentioned in TWRP guide and installed mod and saw an error trying to access /data but installed and wiped and it wont start. So i could not made an image from stock. Did not saw or remembered about the OEM unlock before starting at guides :\
Damn this is an mess i made since that was an new option for me and i have been flashing roms and other stuff for a while :\
Is there an way to fix this?
DARKKi said:
Damn, i could not get into stock anymore. I tried to install root and other things mentioned in TWRP guide and installed mod and saw an error trying to access /data but installed and wiped and it wont start. So i could not made an image from stock. Did not saw or remembered about the OEM unlock before starting at guides :\
Damn this is an mess i made since that was an new option for me and i have been flashing roms and other stuff for a while :\
Is there an way to fix this?
Click to expand...
Click to collapse
You can get into Download mode though?
Flash stock with ODIN 3.12.3 or newer
http://updato.com/firmware-archive-select-model
*Detection* said:
You can get into Download mode though?
Flash stock with ODIN 3.12.3 or newer
http://updato.com/firmware-archive-select-model
Click to expand...
Click to collapse
Yeah i can and i also can use TWRP with USB OTG. Thanks for the link but there is no Finland there, can/should i choose something else from there?
DARKKi said:
Yeah i can and i also can use TWRP with USB OTG. Thanks for the link but there is no Finland there, can/should i choose something else from there?
Click to expand...
Click to collapse
Choose any you like for your model S7, regions only seem to restrict different things like VoLTE etc
*Detection* said:
Choose any you like for your model S7, regions only seem to restrict different things like VoLTE etc
Click to expand...
Click to collapse
Thanks for this! Worked fine and now i got to boot and enable OEM Unlock :]
Now i will read carefully how to install TWRP, MOD, etc.
And really big thanks for helping me with all this stuff!
In TWRP it does say "Failed to mount '/data' (Invalid argument) in lots of places, anything to worry about?
DARKKi said:
In TWRP it does say "Failed to mount '/data' (Invalid argument) in lots of places, anything to worry about?
Click to expand...
Click to collapse
TWRP is not equipped to decrypt Samsung encryption yet. It's normal. You'll most likely end up disabling encryption anyway
CurtisMJ said:
TWRP is not equipped to decrypt Samsung encryption yet. It's normal. You'll most likely end up disabling encryption anyway
Click to expand...
Click to collapse
Hmm. After i flash TWRP along with the instruction that were here (i tried with only applying both or only dm-verity) the phone started to "start" flashing the Samsung logo but nothing happened and after 15-25minutes i tried to install this ROM and it also shows "Starting up please wait" but it also seems to start up indefinately.
Can you tell what is wrong now? It seems i can flash the stock ROM and boot to it but cannot install TWRP/Root nor any custom ROM's :\
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.