Database Info

[q] is there any solution for error 120 at all???

Hello friends,
I'm using att one x sim unlocked. So I won't get att OTA. I'm on 4.0.3 from last august. Tried several times to update manually to 4.0.4 but will end with the annoying Error120. Applied many workarounds like draining batt fully and recharging and leaving it for some time but still no use.
As we know JB is rlzed after a long wait, I want to update it badly and I want your help in resolving this...
I read many posts and articles but they are not of much help. Please post any working solutions so that I can update my phone. Also don't suggest me to root the phone. I don't wanna root it!
thanks in advance,
MHK.

RUU Error [120] means insufficient battery power, but I guess you know that. Have you tried a factory reset? Something may be borked with your battery management.

iElvis said:
RUU Error [120] means insufficient battery power, but I guess you know that. Have you tried a factory reset? Something may be borked with your battery management.
Click to expand...
Click to collapse
No, I haven't. Many complained that even factory reset didnt solve the prob! Which is the reason I skipped it.

This phone unfortunately has some sort of defect with power management, in which it seems to lose track of how much juice it's got, such as abruptly going from 100% charge to 1%. Could be something like that is going on.

iElvis said:
This phone unfortunately has some sort of defect with power management, in which it seems to lose track of how much juice it's got, such as abruptly going from 100% charge to 1%. Could be something like that is going on.
Click to expand...
Click to collapse
As I said it didnt work. Im getting the same error even when I factory reset.. thanx now I hav to install all my apps allover again.
I just want to giv it a try after these many months. So Im stuck up with 4.0.3 I guess.

mhk1678; said:
.. thanx now I hav to install all my apps allover again.
Click to expand...
Click to collapse
I'm sensing a bit of sarcasm there ... Why don't you just root it and flash a stock rooted Rom...

a box of kittens said:
I'm sensing a bit of sarcasm there ... Why don't you just root it and flash a stock rooted Rom...
Click to expand...
Click to collapse
This seems to be the easiest way. But if you want you can go to an AT&T location (official store, Costco, Sam's club, etc.) and let them help you. It might even be a hardware problem.

[Q] Did my M8 self-destruct?

Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.

Settings and command prompt pics showing problem

bb1981 said:
Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.
Click to expand...
Click to collapse
bb1981 said:
Settings and command prompt pics showing problem
Click to expand...
Click to collapse
Do you always run it in airplane mode?
?

I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.

bb1981 said:
I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.
Click to expand...
Click to collapse
Which method did you use for the RUU? Exe or sd?

Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.

bb1981 said:
Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.
Click to expand...
Click to collapse
Did you try a factory reset from stock recovery/hboot yet?

I'll try that next. I just tried it but it seems like I don't have a recovery installed. Instead of saying recovery booting, it just bootloops.

just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.

bb1981 said:
just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.
Click to expand...
Click to collapse
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.

dottat said:
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.
Click to expand...
Click to collapse
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:

bb1981 said:
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:
Click to expand...
Click to collapse
Did you try flashing the newest twrp 2.8.0.3 recovery ?

Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.

Roefastford said:
Did you try flashing the newest twrp 2.8.0.3 recovery ?
Click to expand...
Click to collapse
Twrp does work although I haven't tried it this time just to see if I could try a factory reset to maybe get back my lost baseband and IMEI.
smeejaytee said:
Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.
Click to expand...
Click to collapse
I wish I could. The phone once booted will reboot itself after a few minutes.

Oh ok sorry that didn't help.

smeejaytee said:
Oh ok sorry that didn't help.
Click to expand...
Click to collapse
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?

bb1981 said:
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?
Click to expand...
Click to collapse
Partitions can get corrupted but as far as I'm aware the only way to fix it is with soff I'm not positive because there is an option in twrp to repair partitions also you may be able to use that without soff.

_)(_(45466_!!$$%[¥|[]®]«¥°]<<° xda app...why do I not have permission to post? [/rant]
I picked up a replacement gunmetal gray m8 on swappa and am considering putting the red one up on the boneyard there to give someone a chance to poke around with it. I was wondering if a partition that twrp doesn't have in the repair section like the one for radio/modem for instance could get damaged. The RUU should take care off any problems like that though so I'm officially stumped and haven't really had any extra time to do any troubleshooting.

bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse

dottat said:
bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse
I finally got wise and did a copy and paste after something like 5 times saying I didn't have permission lol....that sounds like a great idea. More (and better) support and understanding is always good.
Click to expand...
Click to collapse

[Q] [Help] Random Reboots after Corrupted EFS partitions.

TL: My efs partition got screwed so my phone doesn't get service which is sad, But when I turn it on, after just working for a few minutes, it just reboots, which is very annoying, does anyone have a solution for this?
Long Version:
I was on the bus home when my phone went out of charge and died, after getting home I plugged it in, but it was stuck on a Loop, which led to me flashing a bunch of Kernels, and ROMs, later one ROM did work and the phone booted up, but my IMEI was gone so I knew my efs partition was screwed, and I just gave up, I still want to use my Nexus 5 as a normal but without the phone feature, which is somewhat okay,
and One weird problem that came to mind is I cannot install any ROM with version 5.0.2, it just won't boot up, but 5.0.1 is okay...but my phone just Reboots every 1-10 mins, I don't know what the problem is, and I don't know how to check whether or not its the power button, anyone have a good idea for solving this ?

You must have corrupted persist partition. Same as here: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-bootloop-t3047895 the strange thing you both have is that you experience reboot. Are you on lollipop rom?
Also to fix persist follow this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

bitdomo said:
You must have corrupted persist partition. Same as here: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-bootloop-t3047895 the strange thing you both have is that you experience reboot. Are you on lollipop rom?
Also to fix persist follow this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
Yes I'm on a Lollipop rom, and I already applied the presist fix, it didn't change anything.

Did you try to flash stock google image?

Sharo93 said:
Yes I'm on a Lollipop rom, and I already applied the presist fix, it didn't change anything.
Click to expand...
Click to collapse
kirmr said:
Did you try to flash stock google image?
Click to expand...
Click to collapse
Try to flash cache.img in fastboot. If it still does not help, then your EFS is indeed corrupted. I wish I knew a method to fixing efs.

kirmr said:
Did you try to flash stock google image?
Click to expand...
Click to collapse
Yes I already did, I have almost tried everything, short of sending it to repairs which I can't because where I live there is no such place.
bitdomo said:
Try to flash cache.img in fastboot. If it still does not help, then your EFS is indeed corrupted. I wish I knew a method to fixing efs.
Click to expand...
Click to collapse
I already did that...I know the efs is corrupted...the only fix i think is using something like Octoplus Box or something

Sharo93 said:
TL: My efs partition got screwed so my phone doesn't get service which is sad, But when I turn it on, after just working for a few minutes, it just reboots, which is very annoying, does anyone have a solution for this?
Long Version:
I was on the bus home when my phone went out of charge and died, after getting home I plugged it in, but it was stuck on a Loop, which led to me flashing a bunch of Kernels, and ROMs, later one ROM did work and the phone booted up, but my IMEI was gone so I knew my efs partition was screwed, and I just gave up, I still want to use my Nexus 5 as a normal but without the phone feature, which is somewhat okay,
and One weird problem that came to mind is I cannot install any ROM with version 5.0.2, it just won't boot up, but 5.0.1 is okay...but my phone just Reboots every 1-10 mins, I don't know what the problem is, and I don't know how to check whether or not its the power button, anyone have a good idea for solving this ?
Click to expand...
Click to collapse
I have pretty much the same issue you do so I'm going to stay posted here.

Do you have an old TWRP backup?
Try to restore any TWRP backup you made of your phone.
Unless you unchecked If you checked that option before making the backup, the EFS partition should be present in the backup.
Best of luck

Anjo_Smash said:
I have pretty much the same issue you do so I'm going to stay posted here.
Click to expand...
Click to collapse
The efs is not gonna get fixed unless you have special tools for it, but the random reboots have spotted ever since I installed the Pure White ROM
joegestes said:
Try to restore any TWRP backup you made of your phone.
Unless you unchecked that option before making the backup, the EFS partition should be present in the backup.
Best of luck
Click to expand...
Click to collapse
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..

Sharo93 said:
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Click to expand...
Click to collapse
Do not try to restore an efs from another device. It won't work and you'll make your problem worse.
Sent from my Nexus 5 using XDA Free mobile app

Sharo93 said:
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Click to expand...
Click to collapse
Man that sucks
Lesson learned I guess, always make a full backup of your device in its original factory state when you buy it.
Sorry for your loss

Oneplus 7 Pro sensor problems

Hi, I'm desperate need of some help guys. :crying:
I had been flashing my device between a couple roms like the android Q beta to check them out but afterwards I noticed none of my sensors were being detected. Gyro, Magnetic, Proximity etc.
Aida64 shows no sensors at all under the sensors tab. The front camera doesn't retract under free fall. *#808# reveals no readings from the Gsensor and some others.
Everything else about the device seems fine, wifi, bt, cell reception.
I've flashed some stock roms like 9.5.3 and 9.5.10 and the android Q beta but the problem still carries on in any rom I try.
I've tried using the all in one tool to flash a stock fastboot rom and I tried the MsmDownloadTool as well.
I can't seem to get the sensors to work and they were fine days ago, any advice?

Woah! flashatitis...I think your phone is overcooked Here's a suggestion, did you fastboot flash your phone back to stock? This will be the last resort..if this doesn't work, then you can use your phone as a nice paperweight or head to the nearest repair centre...

Flash back to stock os,Relock bootloader & take it to service centre

amirage said:
Woah! flashatitis...I think your phone is overcooked Here's a suggestion, did you fastboot flash your phone back to stock? This will be the last resort..if this doesn't work, then you can use your phone as a nice paperweight or head to the nearest repair centre...
Click to expand...
Click to collapse
Overcooked? Like how?
I can lock the bootloader and send it back, what will gearbest do?

pdscoelho said:
Overcooked? Like how?
I can lock the bootloader and send it back, what will gearbest do?
Click to expand...
Click to collapse
Before sending to the repair centre..try to fastboot flash to complete stock and lock the bootloader...if the sensors work then it could be a bootloader issue...if the issues still persist, you can send it back to the repair centre...oh btw, they will know how many times you have unlocked the bootloader and how many times have you flashed your device simply by plugging your device to their software....Oneplus really doesn't care if you have unlocked the device or if you have played around with your phone...but most repair centres try to scare customers using this tactic...keep a straight poker face...

amirage said:
Before sending to the repair centre..try to fastboot flash to complete stock and lock the bootloader...if the sensors work then it could be a bootloader issue...if the issues still persist, you can send it back to the repair centre...oh btw, they will know how many times you have unlocked the bootloader and how many times have you flashed your device simply by plugging your device to their software....Oneplus really doesn't care if you have unlocked the device or if you have played around with your phone...but most repair centres try to scare customers using this tactic...keep a straight poker face...
Click to expand...
Click to collapse
Thanks for the reply. Mauronofrio advised me to flash a persist.img file and it sorted it out. My phone use to take 20-30 seconds to boot up every time, now it does it in less than half that time and all the sensors are working.
The only weird thing I've noticed today is if I power down the device and plug it into the charger the phone starts booting then freezes at the bootloader unlocked warning screen.
Sent from my GM1910 using Tapatalk

pdscoelho said:
Thanks for the reply. Mauronofrio advised me to flash a persist.img file and it sorted it out. My phone use to take 20-30 seconds to boot up every time, now it does it in less than half that time and all the sensors are working.
The only weird thing I've noticed today is if I power down the device and plug it into the charger the phone starts booting then freezes at the bootloader unlocked warning screen.
Sent from my GM1910 using Tapatalk
Click to expand...
Click to collapse
Can you try to do a fastboot flash back to stock rom? See if the issue persists..

amirage said:
Can you try to do a fastboot flash back to stock rom? See if the issue persists..
Click to expand...
Click to collapse
If I go back to stock and lock the rom I don't think it will happen. I did find another thread here where someone mentioned this happens to them as well. What scares me is what happens if you're battery dies? Will the phone be able to charge? I guess if you can reach recovery/flashboot you can always charge?
Sent from my GM1910 using Tapatalk

Same problem
pdscoelho said:
Thanks for the reply. Mauronofrio advised me to flash a persist.img file and it sorted it out. My phone use to take 20-30 seconds to boot up every time, now it does it in less than half that time and all the sensors are working.
The only weird thing I've noticed today is if I power down the device and plug it into the charger the phone starts booting then freezes at the bootloader unlocked warning screen.
Sent from my GM1910 using Tapatalk
Click to expand...
Click to collapse
Where can I find or obtain that persist.img file, I find myself in the same situation as my sensors don't work and would really like it sorted out.

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.