Database Info

[Q] Inspire 4G Need help flashing rom with S-ON

Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag

You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.

bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag

Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again

RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.

http://forum.xda-developers.com/showthread.php?p=31211732

ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.

turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.

ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?

[Q] Can't reboot system without going through fast boot.

Like the title says, my Nexus 5 won't boot unless I manually plug it in, hold down volume buttons and power, then wait 15 seconds for fast boot to appear, and then select "start."
Thats the problem. Now for some more information:
1. Nexus 5 32 gb
2. ROM: CM 11 Dec 13s Nightly
3. Kernel: Bricked 3.4.0
4. The phone is totally functional. The only thing wrong with it is that it can't reboot. From the system, TWRP recover, or anything, it simply will not reboot. Every time I must go into fast boot then press the power button when it says "start." After this, the phone works just as I would expect it to. I can still flash kernels and backups through recovery, it just must be restarted manually through the fast boot. This is a problem for me because I don't always want to have to plug it in when I want to reboot it.
When did it start:
Let me start off by saying that I thing the root of all my problems was the TouchControl app that allows the knock to wake function to work. I downloaded the app and was told to install the developers custom kernel. I did and not only did the app not work, it also seemed to brick my phone. I was scared, but, after doing some research, I found the method of plugging it in and holding down all buttons for about 15 seconds and my phone was saved. Ever since then there has been the problem. I must always do this to reboot my phone. Since the app didn't work I decided to install the Bricked Kernel and everything went fine except that I wasn't prompted with the interactive installer. The kernel works fine and I am now using the Knock to wake feature built into the kernel and am very happy.
Seems to be caused by swipe2wake aka knock 2 wake aka knock knock (but not totally sure)
What I've Tried (don't assume I've tried something I haven't. I could have missed something obvious.):
1. Resetting permissions through TWRP (just thought I'd try)
2. Putting back CM 11 Kernel
3. Restoring to a time when my phone did restart
Any help would be greatly appreciated. I will try to keep the original post updated with everything I try.
FIXED with the help of jd1639 and meangreenie
------------------------------------------------------------------
1.Follow jd1639's link in 3rd comment to the page and
A. Install adb and flashboot drivers
B. Install your version of factory images from google (if you are running 4.4.2 get the image for 4.4.2)
2. Plug in phone to AC CHARGER and hold down power and volume buttons for up to 20 seconds. This should put it into fast boot mode
3. After getting phone in fast boot mode, plug it into your mac or pc.
4. Out of all the instructions in the "How to flash a factory image" thread go to method 2 and ONLY DO THE FIRST TWO LINES OF CODE. All that needs to be flashed is the bootloader.img
5. After it says complete and your phone restarts you should be able to push "start" on your phone and be good!

I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.

jd1639 said:
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
Click to expand...
Click to collapse
So that's essentially flashing the stock ROM?

benaside said:
So that's essentially flashing the stock ROM?
Click to expand...
Click to collapse
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064

jd1639 said:
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.

benaside said:
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
Click to expand...
Click to collapse
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4

jd1639 said:
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
Click to expand...
Click to collapse
I downloaded the folder for 4.4.2 from the link developers.google .com/android/nexus/images#hammerhead

try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too

meangreenie said:
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
Click to expand...
Click to collapse
Will this'd elite all my files and unroot?
Btw thanks so much for the help

benaside said:
Will this'd elite all my files and unroot?
Btw thanks so much for the help
Click to expand...
Click to collapse
no it won't delete your data.. but please triple check your files and fastboot commands before executing
the last resort is to format data if all else fails

Thank you both so much. I have (with both of your help fixed it). I will post how in the original post. Thanks again.

Restart loop after update

Hello,
Yesterday there was an update for the Moto G, I confirmed to do the update. Since then the phone is in a reboot loop. I mean it doesn't matter what ever I do,the phone restart itself in every 2-3 minutes. The phone is rooted.
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
I've got a tip that I should remove the update file from the /chace directory,however I don't know how to do so,as the phone keeps reboot itself.
The only place,where the phone is not restarts is in the bootloader.
Is there any way to somehow solve this problem without flash a stock rom ?
Thanks for your help!
Regards,
Péter

The same here. Help!

Tussky said:
Hello,
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
Click to expand...
Click to collapse
You have to press volume up instead of power to choose something in fastboot menu.
Unroot and if used custom recovery go back to stock recovery.

mokkami said:
Unroot and stock recovery.
Click to expand...
Click to collapse
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Yes I know I have to press volume up,however if I chose recovery it's reboot itself,so I'am not able to select Recovery from the bootloader.

Tussky said:
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Click to expand...
Click to collapse
My is rooted and cwm 6.0.4.6
May be we must do something with fastboot command

my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
Here is the forum link to install CWM Recovery for your Moto G:
http://forum.xda-developers.com/showthread.php?t=2563599
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.

eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Recovery menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
Click to expand...
Click to collapse
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots

You mean this.
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
if you used the modified recovery method:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tussky said:
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
Click to expand...
Click to collapse
Thats strange.

eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
The general command to install a custom recovery in Fastboot is:
fastboot flash recovery your_recovery_image.img
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
Click to expand...
Click to collapse
Thanks MAN! It works perfect!

mokkami said:
You mean this[/URL].
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
if you used the modified recovery method:
Thats strange.
Click to expand...
Click to collapse
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot

@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
Tussky said:
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
Click to expand...
Click to collapse
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.

mokkami said:
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
Click to expand...
Click to collapse
I used the method to root the phone what is on that site,I followed that description and it worked. I'am not an expert in it,so I just followed PaulOBrien guide,so I can't answer for it for sure.
At this point I'am really desperate as the phone is completely useless, so I don't care even if I had data loss,as I can't access it anymore,nor save it to my PC.

In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)

mokkami said:
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
Click to expand...
Click to collapse
Thanks! However I can try it out only after 20 UTC.
However I have an idea,but maybe I'am wrong.
What happens if I try the chace wipe via in command line, I mean:
mfastboot erase cache
This should delete the cache right ? Shouldn't this command remove the problematic update file ?

Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!

mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I want to give it a try. Yes,however I don't have to install the update. But I think I will flash a stock rom,make the update and then re-root the phone.

Thank you guys, I was going crazy with this rebooting problem. So now it is fixed, but how can I get the update? Noway?

mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I was able to enable the usb debugging,and then to start the bootloader. However If I connected the phone and tried to execute the adb reboot-bootloader command it didn't worked. So I restarted the phone and entered into the bootloader,then I've done the following:
fastboot reboot-bootloader
fastboot erase cache
After the first command,the phone rebooted into bootloader,then the second command finally cleared the chace. Now my uptime is more then 8 minutes,so the phone is working great now
However I will do the complete process on the weekend,but not now as I'am really tired,but I will flash a stock rom at the weekend.

Possible solution...
Just started a thread with a possible solution
http://forum.xda-developers.com/showthread.php?t=2663205
Hope it helps...

Power & vol down no longer loads bootloader after flashing

Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help

Fireflynj said:
Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help
Click to expand...
Click to collapse
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372

andybones said:
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372
Click to expand...
Click to collapse
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.

Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
Download the .exe and click open. Follow directions on the screen. It doesn't get easier, trust me you'll be fine. Wouldn't steer you wrong.

Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk

dottat said:
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:

Fireflynj said:
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:
Click to expand...
Click to collapse
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.

dottat said:
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.
Click to expand...
Click to collapse
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.

Fireflynj said:
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.
Click to expand...
Click to collapse
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yup , that was it, the older one worked.
So dumped the idea of getting KitKat back and I flashed the Marshmallow custom s-off RUU with TWRP that you provided. so far good now I just need to re-root it.
Thank you

I need help. I relocked my bootloader, and now my phone (OP7P) won't even turn on

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.