Database Info

[Q] OTA Update got me stuck in semi-bootloop...

I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.

pintyguy said:
I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Because you installed it over a rooted phone (which is strange, as it shouldn't work) you're best bet is to flash it back to stock KK, especially if it already applied the trusted zone updates.
Of course, updating to KK 4.4.2 will then allow you to unlock your bootloader.
So, the first step is to flash to KK 4.4.2. Go here and follow the steps (it should keep your data so you won't lose what is on your internal SD card but you WILL lose all other app settings) -> http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
Once you have followed all the directions (read, read and read again BEFORE you attempt to do anything), then go here to root and unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-info-status-of-root-for-kitkat-build-182183/
Hopefully, you didn't get the latest OTA, If so, you might be hosed as far as getting your bootloader unlocked, but I don't think they've pushed out the latest patch to KK for the XT926.
That should get you back up and running. Again, you will lose your app data (that is not stored on the internal SD card), but your internal and external SD cards will be left alone and intact.

I'm going to try, only problem i foresee is that i need to boot into AP Fastboot to be able to flash, but everytime I try it brings me back to the same error screen. Since that screen is technically AP Fastboot Flash Mode, Im going to try an flash it from there, but Im not sure. Will let you know what happens.

update
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.

pintyguy said:
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.
Click to expand...
Click to collapse
do you have xt926 or xt925

Sorry, but what's the difference?

1 :angel:

pintyguy said:
Sorry, but what's the difference?
Click to expand...
Click to collapse
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?

Yes it does

pintyguy said:
Yes it does
Click to expand...
Click to collapse
then you must have previously done the modem unlock you will need to redo it that is all
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
pintyguy said:
Yes it does
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2389740
that should be the thread for how to do it tell us how it goes, i have no experience with this i am still on Verizon but others say after writing to the phone wait 5 minutes not seconds sorry i rembered wrong before rebooting other wise the settings will not stay

Awesome I was just about to ask for a link, thank you. And I actually got this phone pre-rooted and everything, so the guy before me must have flashed the modem. When I got it I just dropped T-Mobile sim in and it worked just fine. Luckily I'm not new to any of this, I just had a Galaxy s3 running CM11 I believe, but got rid of it and got this. Again, appreciate all the help. Gonna give it a go now and I'll report back soon.

billycar11 said:
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?
Click to expand...
Click to collapse
Well I'm about at my wits end on this one. I couldn't get the Moto Diag driver to correctly install to port, so I went with the RadioComm method instead. I followed a tutorial off this site, which I can't link to just yet asbi do not have enough posts. But followed it to a tee, and it seemingly was successful. But after reboot I only showed bars for about a minute, then right back to no service, T-Mobile could not be registered at this time. Nowhere in the comments or in the guide did they mention to wait the 5 minutes after writing with this method, could that possibly be why? I'm really starting to get frustrated at this point...

Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.

pintyguy said:
Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.
Click to expand...
Click to collapse
it is worth it also i told you about the 5 minute thing

billycar11 said:
it is worth it
Click to expand...
Click to collapse
I thought I was going to lose my data, didn't realize motopoc would do it without losing everything, so I figured might as well.

Frp lock help plz!!!!!!

Hello & Happy Holidays. I have my t-mobile galaxy note 5 (n920t) that i bought off someone but its frp locked. I can't get an otg cable right now to use that bypass method. I tried to flash the stock rom but didn't work. Tried to flash individual parts of another stock rom (the bl and ap files from the PAC Firmware), still nothing. Tried to flash custom recovery, but blocked by frp. Adb only picks up my phone when it's in recovery mode as sideload, not even being able to reboot or anything from adb. I've been tearing my head out get this damn lock off for 3 weeks now, and i can't find the person i brought it from so i'm feeling hopeless right now. Can anyone please help? Any assistance is greatly appreciated.:fingers-crossed:

I can remove it send me a pm
Sent from my SM-N920T using Tapatalk

re: FRP
mannyfresh2k4 said:
Hello & Happy Holidays. I have my t-mobile galaxy note 5 (n920t) that i bought off someone but its frp locked. I can't get an otg cable right now to use that bypass method. I tried to flash the stock rom but didn't work. Tried to flash individual parts of another stock rom (the bl and ap files from the PAC Firmware), still nothing. Tried to flash custom recovery, but blocked by frp. Adb only picks up my phone when it's in recovery mode as sideload, not even being able to reboot or anything from adb. I've been tearing my head out get this damn lock off for 3 weeks now, and i can't find the person i brought it from so i'm feeling hopeless right now. Can anyone please help? Any assistance is greatly appreciated.:fingers-crossed:
Click to expand...
Click to collapse
If you can get into download mode here is good news for you:
Odin Flashing the official stock 5.1.1 Samsung N920T Tmobile
firmware will get your phone running properly again..
You can download the official stock firmware at http://sammobile.com
Be sure to flash using Odin v3.10.7 (older versions may not work.)
Good luck,
Have a great day!

I flashed the stock firmware, the latest one to be exact. It is still locked. Do i have to wait 3 days for frp to be removed like i've heard on previous forums? Should i just try to flash it again? Im dying over here. lol

mannyfresh2k4 said:
Hello & Happy Holidays. I have my t-mobile galaxy note 5 (n920t) that i bought off someone but its frp locked. I can't get an otg cable right now to use that bypass method. I tried to flash the stock rom but didn't work. Tried to flash individual parts of another stock rom (the bl and ap files from the PAC Firmware), still nothing. Tried to flash custom recovery, but blocked by frp. Adb only picks up my phone when it's in recovery mode as sideload, not even being able to reboot or anything from adb. I've been tearing my head out get this damn lock off for 3 weeks now, and i can't find the person i brought it from so i'm feeling hopeless right now. Can anyone please help? Any assistance is greatly appreciated.:fingers-crossed:
Click to expand...
Click to collapse
same thing happened to me too about 2 weeks ago. couldn't get past the google log in screen. The only way i was able to get around it was to use the Samsung bypass apk that is floating around on the web. I just bought an otg flash/usb drive for about $12 and used that to install the apk on the phone. worked perfectly. Hopefully you can get your hands on an otg flash drive soon and your problem should be solved my friend.
Good luck.

mannyfresh2k4 said:
I flashed the stock firmware, the latest one to be exact. It is still locked. Do i have to wait 3 days for frp to be removed like i've heard on previous forums? Should i just try to flash it again? Im dying over here. lol
Click to expand...
Click to collapse
Have you fixed it ?

Don't panic. You're not screwed.
This happened to me. Odin flash the correct firmware (so if you were on COI5, you need to flash official T-Mobile COI5). It will reboot into Android and when you're going through the setup wizard it will say something like "this phone was previously locked, please enter your Google account to unlock it." Put in the google account you had on the phone before and the password and voila; it will work.
In the future keep OEM unlocking enabled to avoid this
Disregard that, I can't read

brashmadcap said:
Don't panic. You're not screwed.
This happened to me. Odin flash the correct firmware (so if you were on COI5, you need to flash official T-Mobile COI5). It will reboot into Android and when you're going through the setup wizard it will say something like "this phone was previously locked, please enter your Google account to unlock it." Put in the google account you had on the phone before and the password and voila; it will work.
In the future keep OEM unlocking enabled to avoid this
Click to expand...
Click to collapse
He bought the phone from someone, how would he know that?
Sent from my SM-N920T using Tapatalk

darkjedi said:
He bought the phone from someone, how would he know that?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Whoops I can't read

I still didn't fix it, no. I had a good feeling that i can do it without that damn otg cable, but it seems like i don't have a choice. Spent money, now i gotta spend some more. Smh.....

I can remove it for you.

Misterjunky said:
If you can get into download mode here is good news for you:
Odin Flashing the official stock 5.1.1 Samsung N920T Tmobile
firmware will get your phone running properly again..
You can download the official stock firmware at http://sammobile.com
Be sure to flash using Odin v3.10.7 (older versions may not work.)
Good luck,
Have a great day!
Click to expand...
Click to collapse
mannyfresh2k4 said:
I still didn't fix it, no. I had a good feeling that i can do it without that damn otg cable, but it seems like i don't have a choice. Spent money, now i gotta spend some more. Smh.....
Click to expand...
Click to collapse
Did you do what @Misterjunky posted? You do not need an OTG for this.
Can you get into recovery?
Sent from my SM-N920T using Tapatalk

OTG cable and the apk is the best route to go on this one. cheap too. I just did this.

So what needs to be done to deter this from happening??

recepo1 said:
So what needs to be done to deter this from happening??
Click to expand...
Click to collapse
Avoid buying phones from people via Craigslist. If they aren't stolen, chances are the former owner is scamming some other way.
Simple way to tell the seller's motivation: If they know what they're doing, they'll use Swappa, if they've stolen or otherwise borked the phone, they'll use Craigslist.

I've had that same error , ended up i believe. ...that time (been so many soft bricks ) ...I actually used smartswitch emergency recovery mode. Try that or odin
Sent from my SM-N920T using Tapatalk

help with lg and samsung frp lock
I have sboot.bin files i can help you just flash with odin and bam its unlocked.....

You can splice some old USB cables together together a working otg cable. I've had one I did work for years now hooked up to my nexus player

the OTG and apk method was patched already.

gimmemiggy said:
the OTG and apk method was patched already.
Click to expand...
Click to collapse
Just downgrade firmware to October update of lollipop and it should work

Unlocked T-Mobile Note 5 not getting signal

Hello everyone!
I bought a Unlocked note 5 like a week ago and it was working perfect I was using it with At&t, since I root every phone I buy I decided to root this one, after rooting; the phone started rebooting by itself ( I used Max's High on android root process ) since it was buggin me out and rebooting too many times I decided to flash another stock image ( being this 6.0 Marsmallow test http://forum.xda-developers.com/tmo...eral/note-5-t-mobile-marshmallow-tar-t3250744 ) to see if it fixed the issue, gues what? it didn't! And on top of that I got this message:
"Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost"
So it gave me the option to restart, I did, but I had signal and my messages were coming through, after it rebooted ( by itself ) like a 3rd time I stopped getting signal, when I have my at&t sim in it stays (Searching), I've tried everything I can think of, Changing apn's, I downgraded to 5.1.1 Stock and still get the same Security Error and still have no signal.
Please anyone that can help me, I've never had this issue when rooting any other phone, does this have a fix?

iYuseffitou said:
.
Please anyone that can help me, I've never had this issue when rooting any other phone, does this have a fix?
Click to expand...
Click to collapse
Robot to recovery. Backup your stuff to an otg USB and then wrote the phone completely. Flash COD6 with Odin and see what happens
Wait, before you rooted the device, did you turn on OEM Unlock in developer menu?
Sent from my SM-N920T using Tapatalk

Jammol said:
Robot to recovery. Backup your stuff to an otg USB and then wrote the phone completely. Flash COD6 with Odin and see what happens
Wait, before you rooted the device, did you turn on OEM Unlock in developer menu?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Yes I did my good sir, will try this now.
Edit: COD6 is for Note 4 lol or at least I can't find it.

iYuseffitou said:
Yes I did my good sir, will try this now.
Edit: COD6 is for Note 4 lol or at least I can't find it.
Click to expand...
Click to collapse
Crap my bad. Note 4 was last device I had before this. COD6 was pretty popular and most likely still is. Good thing you caught that! @TEKHD has a thread that has instructions on how to Odin the latest firmware for the Note 5. It's in the General section I believe. Do a full wipe first though before you flash with Odin.
Oh yeah, and I advise staying away from the Marshmallow Beta build for now.

bricked s8+ trying to root

ive tried to root my s8+ following the step by step guide but now its a brick
i have never rooted before and tried it for the first time, everything seemed to be going correctly until i pressed wipe and swiped to confirm, i got error message unable to mount storage, now i have a continuous loop of samsung s8 logo
i have tried connecting to odin again and no joy.
is there any hope or is it for the bin ?
gutted

What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....

i have model SM-955F

Download the stock ROM and download mode should be reachable, where you can then flash it

Pedroc1999 said:
Download the stock ROM and download mode should be reachable, where you can then flash it
Click to expand...
Click to collapse
i need more information if possible ? i have no idea how to do it, its my first and probably last attempt at rooting

It's probably not binned, don't worry. Can you get into Download mode again?
- Press and hold the Bixby, Volume down and Power buttons together until you see anything on screen.
- When you see a warning screen, hit Volume Down to continue to download mode.

GibMcFragger said:
What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....
Click to expand...
Click to collapse
Come on man, if you had a snapdragon version, you can't root or even get that far.

yes i can get into the screen where it says downloading do not turn off

It does look like it's the usual snapdragon variant, yeah. You need the Exynos version for its unlocked bootloader, if you want root and whatnot.
Honestly unless you have specific reasons for root, you probably don't need it.
I was pleasantly surprised at how much I don't miss it so far, but I can't speak for everyone else. I know Brava27 wouldn't dare.
Edit: Okay good. So the Stock ROM is basically the factory image always intended for your phone, from Samsung. You just have to find and download that, then flash it as usual via Odin.
PLEASE triple check around and do your research on whether this link provides you the right one, but here is a first-hit I found when searching for a stock rom for your model. https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022

brilliant thank you i will give it a try
does it unroot it also if i flash it back to stock and put knox back to normal or is that history now ?

That's right, it's completely stock, so it'd be like you got the phone fresh. It'll be unrooted if you get it working.
So that said, ensure your SIM is in the phone before you set it up, or it'll reset on you again when you insert it later.
I'm not sure what Knox's status would be and if the e-fuse has triggered... you'll know when you're powering on the device, I think. It's no real matter, unless you're concerned about warranty. In which case, you were going to stop caring about that right after attempting to root anyway.
I'm still not certain on what firmware file you want. Might want to search around for something that matches your carrier.

once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.

galarond said:
once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.
Click to expand...
Click to collapse
can you use them on rooted devices with knox triggered ?

No, I was not able to use Samsung Pay on my Note 5 after I tripped knox. It does some sort of security check on start-up of the app.

The bigger question is whether it "rooted" yet or not. With some luck, the e-fuse has not triggered yet and it's a clean device still.

widget2k13 said:
can you use them on rooted devices with knox triggered ?
Click to expand...
Click to collapse
yes with custom roms can be done or with some build.prop mods too.

So the snapdragon version is not rootable? Damn, I didn't know that.

woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here

widget2k13 said:
woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here
Click to expand...
Click to collapse
For the "Security notice" try this:
root explorer go to /system/app/SecurityLogAgent delete folder
For "S-Health" to work, follow this:
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Good luck.

Totaly different sittuation but I think I have this right from what you say in this thread.
That Knox being tripped cant be reversed? and that Knox is a fuse so it cant be bypassed with otg cable backup?

Defective ONnePlus 7 ? Help me out pls

Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .

The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.

@PriPhaze is your device stock(bootloader locked) or modified in any way?

aaycce said:
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
Click to expand...
Click to collapse
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
strongst said:
@PriPhaze is your device stock(bootloader locked) or modified in any way?
Click to expand...
Click to collapse
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.

PriPhaze said:
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
Click to expand...
Click to collapse
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?

strongst said:
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
Click to expand...
Click to collapse
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.

PriPhaze said:
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
Click to expand...
Click to collapse
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.

strongst said:
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
Click to expand...
Click to collapse
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS

PriPhaze said:
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
Click to expand...
Click to collapse
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.

strongst said:
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
Click to expand...
Click to collapse
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.

PriPhaze said:
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
Click to expand...
Click to collapse
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...

strongst said:
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
Click to expand...
Click to collapse
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US

PriPhaze said:
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
Click to expand...
Click to collapse
Yes, everything is on board. It's the worst case for, sadly...
Or you buy a device with broken screen and exchange the board /display. Depends how much you have to spent for this at all.

PriPhaze said:
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
Click to expand...
Click to collapse
Ah yes, the common misconception that power shuts it off. Nope, not this phone. You have to hold power and volume up together to power off the phone when it crashes. Make sure you're using the latest platform tools (adb/fasboot) to unlock your phone. Make sure oem unlocking is enabled in developer settings after you've unlocked, having it disabled for some reason does screwy things. Mine was disabled once when I downgraded to Android 9 using the all in one tool available on xda, I thought I bricked the phone because it wouldn't boot after a reboot. Flash the latest oos twice through the system local upgrade feature, this will put the current oos on all partitions. Use the correct twrp, the unified versions found on xda 3.3.1-75 and 3.3.1-76 work well for me. The installer zip for those can be used in magisk to flash twrp after an OTA update before reboot. So, local upgrade 100% -> magisk modules "+" twrp 3.3.1-75 unified installer zip -> reboot to recovery -> flash magisk 20.3 at least (20.4 is available now). Do this twice so that everything is the same version on all the partitions. Lastly restore apps with swift backup without data, I know it's not ideal but may be necessary because some app's data may be corrupt and causing this. Good luck. Of course at any time you have it running you can reboot in safe mode (touch and hold restart until the dialogue pops up) and see how long you can use it without any third party apps to confirm that it is an app you installed.

Man I had the exact same problem as you and I got it fixed this morning after nights of fastboot commands trial and error found this thread forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Tried a few times before it worked but saved my phone all I had was fastboot mode and no recovery make sure to manually flash all fastboot commands you will then get stock recovery back wipe using all 3 options go 1st 2nd 3rd and then 1st wipe again after reboot phone might hang just force reboot and fixed

I really appreciate all the replies really but hmm im guessing there's a misunderstanding on what im saying.
I do know how to flash and recover one plus devices using MSM tool if neccesary, also to flash the fastboot rom .
The thing here is that everytime i recover the phone and all seems stable and working good , after a2 days more less it will random freeze of death and you cant even reboot holding power button NOTHING! is completely freezed.
So yea, thats pretty much it, i have tried already all that you said so far :c.