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.
Related
Ok so i was on my phone when all of a sudden my home screen kept crashing and pushing the window to close it. So i closed it and powered down the phone thinking a restart would help. It subsequently went to the Encryption Unsuccessful page where it tells you that your phone will need a Factory Reset. So i power down my phone and some times itll restart to the "E.U" screen 3/4 times. When i get it to power down and not power on i try to use the Volume+&Power. It'll pull to the menu and ill scroll to the Recovery and click it but itll push right back to the " Encryption Unsuccessful" screen. On the "Encryption Unsuccessful" Page i have a "Reset Phone" button but it does nothing but turn blue from gray when i press it. I can even take screenshots on the "E.U" page. I URGENTLY need my phone because im constantly awaiting interview calls and im waiting for a certain one. Will try other things until i get a Reply from this. If I fix it over night (well morning now) ill let you know with what stwps
sorry bout your troubles man, bad timing....i dont have a Max and I dont encrypt my phone. Are you on stock ROM? what version?
You most likely will need to flash with rsd lite, a stock rom then go from there
hbenz2008 said:
sorry bout your troubles man, bad timing....i dont have a Max and I dont encrypt my phone. Are you on stock ROM? what version?
You most likely will need to flash with rsd lite, a stock rom then go from there
Click to expand...
Click to collapse
I was on the most updated STOCK ROM. And i didnt want to encrypt my phone either i think i may have hit that setting when my homescreen was crashing over and over. I was wondering if it could be heat damage because I have a laptop with a metal case (****ing Dumbass Alienware) and i was playing rust for almost the whole day and it gets like hot to the touch when i play that long and the phone was in my pocket. If you could link me to a tut for how to flash with rsd and a link to the stock ROM ill go through and try that tonight and post my results either in the am or right when i finish depending on what time it is and what im doing.
Another thing that sucks is theres no warranty and i have no carrier on it ATM (its a verizon phone without the sim, basically an android ipod)
Rsd lite 6.1.6:
http://forum.xda-developers.com/showthread.php?t=2637338
Moto firmware:
http://sbf.droid-developers.org/
How to:
http://www.howardforums.com/showthr...ellyBean-on-PagePlus-VOICE-SMS-MMS-3G-WORKING
KingHephaestus said:
I was on the most updated STOCK ROM. And i didnt want to encrypt my phone either i think i may have hit that setting when my homescreen was crashing over and over. I was wondering if it could be heat damage because I have a laptop with a metal case (****ing Dumbass Alienware) and i was playing rust for almost the whole day and it gets like hot to the touch when i play that long and the phone was in my pocket. If you could link me to a tut for how to flash with rsd and a link to the stock ROM ill go through and try that tonight and post my results either in the am or right when i finish depending on what time it is and what im doing.
Another thing that sucks is theres no warranty and i have no carrier on it ATM (its a verizon phone without the sim, basically an android ipod)
Click to expand...
Click to collapse
its possible rsd may work, but i wouldnt be surprised if it doesnt. encryption errors are bad and sometimes unfixable.
if you are able to boot the phone and tell me the system version, i can provide an end all script to try.
if you cant get the system version, have you taken an update in the last couple weeks? that will tell me what you are on if yes or no.
also, you will need to be able to get into fastboot to use any script, you can get there right?
Encryption errors are triggered by the data partition becoming unmountable (data file system corruption?).
Data and data/media wipe (factory reset) could fix it (unless the data partition part of storage device is physically damaged).
hbenz2008 said:
Rsd lite 6.1.6:
http://forum.xda-developers.com/showthread.php?t=2637338
Moto firmware:
http://sbf.droid-developers.org/
How to:
http://www.howardforums.com/showthr...ellyBean-on-PagePlus-VOICE-SMS-MMS-3G-WORKING
Click to expand...
Click to collapse
Thank you for providing the link to everything i will be trying that in the morning just to give it a try
bweN diorD said:
its possible rsd may work, but i wouldnt be surprised if it doesnt. encryption errors are bad and sometimes unfixable.
if you are able to boot the phone and tell me the system version, i can provide an end all script to try.
if you cant get the system version, have you taken an update in the last couple weeks? that will tell me what you are on if yes or no.
also, you will need to be able to get into fastboot to use any script, you can get there right?
Click to expand...
Click to collapse
No i hadn't updated it in the past weeks and yes i can get into fastboot.
kabaldan said:
Encryption errors are triggered by the data partition becoming unmountable (data file system corruption?).
Data and data/media wipe (factory reset) could fix it (unless the data partition part of storage device is physically damaged).
Click to expand...
Click to collapse
Yeah i believe it may of been heat damage because of my laptop accumulating a lot of heat on the metal casing and that combined with 17hrs of Archeage = one hot laptop
And also for all who replied i sometimes get a picture of the little android dude laying down with his stomach hatch open and a caution sybol above it. Dont know if thats something bad or if its just buggy because i can hard reset it (pwr + Vol-) and turn it back to the encryption unsucsessful page.
KingHephaestus said:
Thank you for providing the link to everything i will be trying that in the morning just to give it a try
No i hadn't updated it in the past weeks and yes i can get into fastboot.
Yeah i believe it may of been heat damage because of my laptop accumulating a lot of heat on the metal casing and that combined with 17hrs of Archeage = one hot laptop
And also for all who replied i sometimes get a picture of the little android dude laying down with his stomach hatch open and a caution sybol above it. Dont know if thats something bad or if its just buggy because i can hard reset it (pwr + Vol-) and turn it back to the encryption unsucsessful page.
Click to expand...
Click to collapse
regardless of the issue, "if it is fixable", this will do it.
there are certain situations that cant be fixed by rsd and standard fastboot. the above tool will fix any issue that is fixable.
bweN diorD said:
regardless of the issue, "if it is fixable", this will do it.
there are certain situations that cant be fixed by rsd and standard fastboot. the above tool will fix any issue that is fixable.
Click to expand...
Click to collapse
sorry i havent replied in a few days life got in the way. But i will finally be trying the rsd and fastboot fix today and to the person who posted the rar can you tell me what im supposed to do with that? Youre hand a laptop guy a bunch of phone programs without instructions.
I had some problems regarding google not syncing contacts and wanted to restore my TWRP backup I made yesterday. I have been on Official Pie with magisk. I simply restored my backup and now the phone immediatly crashes to the qualcom crash dump screen. I still have access to custom Recovery though, using latest blue_spark. Why did this happen and how can I fix it? Did I restore something wrong? I used the original settings. Is it the weird partitioning which is causing this?
So I had this happen to me a couple of times last weekend when attempting to upgrade to Pie. On a couple of occasions I couldn't get past the Dump screen, no matter what I did - just used the MSMTool to restore my phone to factory. However, in one instance, I could boot into recovery. Unfortunately, this happened to me so many times last weekend, I forget how I solved it when I could boot into TWRP. I may have just flashed the OnePlus Pie 9.0 zip again. I assume your backup was also Pie?
azsl1326 said:
So I had this happen to me a couple of times last weekend when attempting to upgrade to Pie. On a couple of occasions I couldn't get past the Dump screen, no matter what I did - just used the MSMTool to restore my phone to factory. However, in one instance, I could boot into recovery. Unfortunately, this happened to me so many times last weekend, I forget how I solved it when I could boot into TWRP. I may have just flashed the OnePlus Pie 9.0 zip again. I assume your backup was also Pie?
Click to expand...
Click to collapse
Yeah, I'm in a similar situation. I was just able to boot into TWRP several times back and forth, wiped everything and installed clean Pie.zip. Now I get a screen saying device is corrupt press power button. If I press the power button twice, it boots into the rom just fine. So the phone works and all, to bad you can't restore backups anymore though. Now I just need to remove this darn corrupt screen, its super annoying.
baxtex said:
Yeah, I'm in a similar situation. I was just able to boot into TWRP, wiped everything and installed clean Pie.zip. Now I get a screen saying device is corrupt press power button. If I press the power button twice, it boots into the rom just fine. So the phone works and all, to bad you can't restore backups anymore though. Now I just need to remove this darn corrupt screen, its super annoying.
Edit:
Reflashed TWRP and the corrupt screen disappeared. Now all is well again. Now where did I put that titanium backup...
Click to expand...
Click to collapse
I had that happen too. It was an absolute mess and I wasted my Sunday fixing it. I think the only way to get rid of that message is to use the MSMTool. I believe I read that in one of the posts on the Pie thread.
EDIT: Just read your Edit - that's good news. Wished I would have tried that.
azsl1326 said:
I had that happen today. It was an absolute mess and I wasted my Sunday fixing it. I think the only way to get rid of that message is to use the MSMTool. I believe I read that in one of the posts on the Pie thread.
Click to expand...
Click to collapse
Darn it... I'l think I'l pass for now. I briefly looked at the unbrick guide thread but there wasn't any clear instructions on how to do it.
Funny thing, this is the first timeI had so much problems with flashing stuff on, and here I thought it would be easy, that this was a "developer friendly" phone. :S
Edit: I was mistaken, probably only fixed it temporarly when I flashed new recovery.
baxtex said:
Darn it... I'l think I'l pass for now. I briefly looked at the unbrick guide thread but there wasn't any clear instructions on how to do it.
Funny thing, this is the first timeI had so much problems with flashing stuff on, and here I thought it would be easy, that this was a "developer friendly" phone. :S
Click to expand...
Click to collapse
Yea, the whole a/b partition messed up developer friendly....at least initially. I have spent more time fixing flashes gone bad than I have for all of my other android phones combined. It seems to have settled down now though. Although, I haven't tried any other ROMs outside of OOS. On my prior phones, I would have no problem switching between them often.
The MSMTool isn't that hard. The instructions look intimidating. However, here's what I did when I got the Qualcomm dump screen.
- Open MSM Tool
- Open Device Manager and looked for Ports and the phone.
- Held down Power + Volume Up on the phone
- Waited for the Port (for the phone) to change under the Ports tab in Device Manager
- MSMTool should start downloading. Just let it finish and then you should be good to go
azsl1326 said:
Yea, the whole a/b partition messed up developer friendly....at least initially. I have spent more time fixing flashes gone bad than I have for all of my other android phones combined. It seems to have settled down now though. Although, I haven't tried any other ROMs outside of OOS. On my prior phones, I would have no problem switching between them often.
The MSMTool isn't that hard. The instructions look intimidating. However, here's what I did when I got the Qualcomm dump screen.
- Open MSM Tool
- Open Device Manager and looked for Ports.
- Held down Power + Volume Up on the phone
- Waited for the Port (for the phone) to change under the Ports tab in Device Manager
- MSMTool should start downloading. Just let it finish and then you should be good to go
Click to expand...
Click to collapse
I agree.
Oh really? Because there were links to all shady chinese files all over the place. I'm refering to this thread:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Thanks a lot for your help!
baxtex said:
I agree.
Oh really? Because there were links to all shady chinese files all over the place. I'm refering to this thread:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Thanks a lot for your help!
Click to expand...
Click to collapse
Yea, I saw that thread too. I just download the tool, MsmDownloadToolV4.0InternationalVersionOxygenOS5.1 .5.rar and ran it. Didn't need anything else and everything fell into place.
azsl1326 said:
Yea, I saw that thread too. I just download the tool, MsmDownloadToolV4.0InternationalVersionOxygenOS5.1 .5.rar and ran it. Didn't need anything else and everything fell into place.
Click to expand...
Click to collapse
Again, thanks a million! Will try it next time I mess up this phone. (soon probably)
Ok here we go. I bought this new. I did a deleted Magisk which I should of not done. Somehow the root is screwed up. I am trying to get in the phone to restore it to like I bought it. There was an issue when I bought it with Magisk. Something about it needed to be an app. Anyway, When I do a reboot I have a choice of Reboot, Recovery, Soft Reboot , Bootloader. I want to flash a rom again and fix the Magisk so it has no errors. I have read and tried the different way to do this. I installed TWRP but cannot get it to come up on a boot because there is no home button on my phone. Any suggestions?
You can start from scratch and install the official ROM that's supposed to be on your phone via miflash
Then you can start fresh on ROM of your choice and clean install of twrp and magisk etc
Dash Riprock said:
Ok here we go. I bought this new. I did a deleted Magisk which I should of not done. Somehow the root is screwed up. I am trying to get in the phone to restore it to like I bought it. There was an issue when I bought it with Magisk. Something about it needed to be an app. Anyway, When I do a reboot I have a choice of Reboot, Recovery, Soft Reboot , Bootloader. I want to flash a rom again and fix the Magisk so it has no errors. I have read and tried the different way to do this. I installed TWRP but cannot get it to come up on a boot because there is no home button on my phone. Any suggestions?
Click to expand...
Click to collapse
U shouldn't do what u dont really know from beginning
Way to fix your problem: download miflash and fastboot rom file to flash it to stock rom (any region u want because of unlocked bootloader)
hungragezone said:
U shouldn't do what u dont really know from beginning
Way to fix your problem: download miflash and fastboot rom file to flash it to stock rom (any region u want because of unlocked bootloader)
Click to expand...
Click to collapse
I was wanting to unroot the phone and it was supposed to unroot it when you uninstall Magisk. There already was an issue with Magisk from the start wanting it to be an app instead of a system app. Things went down from there. I have fastboot, recovery on it now. Just want to be able to download some apps that won't install because of root detection. Now I have a corrupted root thanks to Magisk.
speedtripler said:
You can start from scratch and install the official ROM that's supposed to be on your phone via miflash
Then you can start fresh on ROM of your choice and clean install of twrp and magisk etc
Click to expand...
Click to collapse
I cannot find Hermes on the site. M11 Ultra is my phone. Redmi Note 2 .
speedtripler said:
You can start from scratch and install the official ROM that's supposed to be on your phone via miflash
Then you can start fresh on ROM of your choice and clean install of twrp and magisk etc
Click to expand...
Click to collapse
If I could find my Rom that would be nice.
Dash Riprock said:
If I could find my Rom that would be nice.
Click to expand...
Click to collapse
You don't sound like you have put in much effort tbh
You should read more and watch some of those video tutorials before doing things that break your phone
The phone is not bricked. I cannot find the firmware for this phone. Weird. I have looked a a lot of firmware and cannot find one for this phone. it says M11 Ultra and Redmi Note 2 (hermes) the Android OS is 10 but the hermes I see are 5.0. Too old os. I do watch the videos. When I got this phone it already was not right with the rooting it came with. I did not want rooting because I cannot download certain apps I use. I went through the steps to delete root through deleting Magisk but from there it went to ****. The phone works. But there is corrupted root and fastboot keeps tapping out when I boot to it. Also Magisk was updated to 23.1 at the start and there was a conflict with that. Had I known this phone was rooted I would of never bought it. Also not sure if bootloader is open. My PC sees it just fine communicating with the phone through a program I have not figure out. What I have tried does not work. I don't need an ass chewing here. I just asked for some help. Thanks
speedtripler said:
You don't sound like you have put in much effort tbh
You should read more and watch some of those video tutorials before doing things that break your phone
Click to expand...
Click to collapse
Yes I have put effort for a week now. I assume I need the fastboot rom to get this. I cannot get TWRP to even come up on the phone. Fastboot always does.
speedtripler said:
You don't sound like you have put in much effort tbh
You should read more and watch some of those video tutorials before doing things that break your phone
Click to expand...
Click to collapse
I also want to add there is no where in the developer options that I can turn on the OEM. What I watch on the videos is NOT on the phone I have. I do have debug on the computer sees the phone. thats it.
Dash Riprock said:
The phone is not bricked. I cannot find the firmware for this phone. Weird. I have looked a a lot of firmware and cannot find one for this phone. it says M11 Ultra and Redmi Note 2 (hermes) the Android OS is 10 but the hermes I see are 5.0. Too old os. I do watch the videos. When I got this phone it already was not right with the rooting it came with. I did not want rooting because I cannot download certain apps I use. I went through the steps to delete root through deleting Magisk but from there it went to ****. The phone works. But there is corrupted root and fastboot keeps tapping out when I boot to it. Also Magisk was updated to 23.1 at the start and there was a conflict with that. Had I known this phone was rooted I would of never bought it. Also not sure if bootloader is open. My PC sees it just fine communicating with the phone through a program I have not figure out. What I have tried does not work. I don't need an ass chewing here. I just asked for some help. Thanks
Click to expand...
Click to collapse
Fake phone. It Isn't a real Mi11 Ultra. Just some sh1tty phone try to fake 11U
And im sure that u will not be able to fix this phone here. Just throw it away
Dash Riprock said:
Yes I have put effort for a week now. I assume I need the fastboot rom to get this. I cannot get TWRP to even come up on the phone. Fastboot always does.
Click to expand...
Click to collapse
Check and make sure "USB Debugging" is on under Developer Options. Once this done, from the command prompt, execute "adb reboot recovery". This will take you to recovery (TWRP in your case).
Dash Riprock said:
I also want to add there is no where in the developer options that I can turn on the OEM. What I watch on the videos is NOT on the phone I have. I do have debug on the computer sees the phone. thats it.
Click to expand...
Click to collapse
When you get to Setting, in the search bar type "OEM" and it will list "OEM Unlocking" in the search result. Clicking on this should help you get to OEM Unlocking option.
Dash Riprock said:
The phone is not bricked. I cannot find the firmware for this phone. Weird. I have looked a a lot of firmware and cannot find one for this phone. it says M11 Ultra and Redmi Note 2 (hermes) the Android OS is 10 but the hermes I see are 5.0. Too old os. I do watch the videos. When I got this phone it already was not right with the rooting it came with. I did not want rooting because I cannot download certain apps I use. I went through the steps to delete root through deleting Magisk but from there it went to ****. The phone works. But there is corrupted root and fastboot keeps tapping out when I boot to it. Also Magisk was updated to 23.1 at the start and there was a conflict with that. Had I known this phone was rooted I would of never bought it. Also not sure if bootloader is open. My PC sees it just fine communicating with the phone through a program I have not figure out. What I have tried does not work. I don't need an ass chewing here. I just asked for some help. Thanks
Click to expand...
Click to collapse
How much did you pay for it?
It cannot be a Redmi note 2 and a mi 11 ultra at the same time....
It sounds like the other said, a fake phone
speedtripler said:
How much did you pay for it?
It cannot be a Redmi note 2 and a mi 11 ultra at the same time....
It sounds like the other said, a fake phone
Click to expand...
Click to collapse
Paid around $100 When I go to the settings it says device model M11 Ultra, BUT when I go to Regulatory Information it says Model Redmi Note 2 IC: hermes . Here is the link of the phone I bought. Again I cannot find the for sure Firmware for this. Not sure it is the right firmware. https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
archer797 said:
When you get to Setting, in the search bar type "OEM" and it will list "OEM Unlocking" in the search result. Clicking on this should help you get to OEM Unlocking option.
Click to expand...
Click to collapse
Did that. Nothing. Blank screen no results.
hungragezone said:
Fake phone. It Isn't a real Mi11 Ultra. Just some sh1tty phone try to fake 11U
And im sure that u will not be able to fix this phone here. Just throw it away
Click to expand...
Click to collapse
This is the phone. Check it out. Thanks https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
Dash Riprock said:
This is the phone. Check it out. Thanks https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
Click to expand...
Click to collapse
The phone works fine but its rooted and I don't want root. This all started because I followed what it said about removing root. Just do it through Magisk. That did NOT work. From there corrupt root. As for phone It works. But I cannot use my banking and investment apps on a rooted phone. That is the problem.
Dash Riprock said:
This is the phone. Check it out. Thanks https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
Click to expand...
Click to collapse
fake phone
confirmed
/btw: M11 not Mi 11 rofl
MTK6595, not much hope of resolving this without getting hold of seller and finding out the ROM producer and probably flashing again on a formatted system ( there are so many but a search on a browser may help). Flashing MTK systems are not hard, just need the correct ROM and leave it unrooted using SP flash tools. There are plenty of rooting bids for mtk's, so may be you can unroot too using the guides from a browser search. Unless you can return as an item not as described for a refund.
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone
I am a very experienced ROM enthusiast and owned plenty of Xiaomi/Oneplus devices.. This is my first pixel device. I loved the phone, more than the other mentioned companies. My pixel 7 Pro was my prized possession.. I've came close a couple of times botching a ROM flash, even once with my p7p (installing evo with February firmware instead of Jan, phone would boot to bootloader for a total of 2 seconds before dying again, had to spam flash phone in pixel flasher app until it recognized and luckily it did) but this time, trying to go from latest feb build to jan before flashing evo, my ****ing cable did something in the middle of flashing the second partition (b partition) and was almost to system, the partition it flashes before booting.. it was flashing the product partition.. literally already flashed every other partition except partition and system on the b slot. A slot was fully flashed.. phone literally wont respond to plugging into computer, into charger, holding down every combination of buttons... doesn't matter. I'm stumped how flashing a factory rom could have gone this horribly.. especially so late into the flashing process..
Beware guys; Make sure the cable you're using to flash is stable!
attached in this post is the logs I have pulled from the pixel flasher app.. if someone could bounce some ideas off of me or somehow make this make sense to me, it would be gladly appreciated.
Holding down the down volume button when starting doesn't enter bootloader? If it does, use Google's online Android Flash tool to go back to stock.
Try a different cable.
Try a different USB port.
Try another computer as well.
If any of these prompt some response, I think there's hope. Also try booting into fastboot from bootloader as well as recovery.
Prob hard brick.
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Arealhooman said:
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Click to expand...
Click to collapse
A battery for my desktop PC?
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Google for "uninterruptible power supply" ...
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Yeah, no idea.
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
The real answer to this is why google and the android community as a whole is pushing away from having a supporting third party recovery menu (implementing new partitions like init_boot and vendor_boot for recovery, also no working twrp). Why do you think Evolution ROM pushes so hard to be different and when flashing their newest build you do it not through the usual scary tedious bootloader way (THE SAME WAY WE ARE SUPPOSED TO FLASH OUR FACTORY ROMS) to making their own recovery, which obviously means only flashing one partition, and adb sideloading the rom. its like google wants you to break your phone and they are making it more convenient for third party roms to package theirs the same way. i should have never left evo.. haha.
Oh, and sorry for the late reply. I thought I would leave my phone alone for a little to see if it would help; I'm accident prone and lose things constantly, and what do ya know I just lost my phone that I can't even call to find lmao. Ill keep updated on everyones opinions on what i should try whenever i find it
krakout said:
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
Click to expand...
Click to collapse
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
EtherealRemnant said:
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
Click to expand...
Click to collapse
Ah I see, makes sense.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Oh brother, how often does that actually even happen?
HipKat said:
Oh brother, how often does that actually even happen?
Click to expand...
Click to collapse
Sure, not really often. But when it does..
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
zacattackkc said:
trying to go from latest feb build to jan before flashing....
Click to expand...
Click to collapse
It sounds like you may have tripped some anti-downgrade code.
EDIT: I can confirm that the bootloader version was changed in the FEB image as compared to the JAN image.
96carboard said:
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
Click to expand...
Click to collapse
Well, I use Samsung, so I am assuming fastboot is similar…