Hi all,
I have been flashing/testing many roms for a number of years now. I particularly enjoyed Jasjamming in my Tytn I days. Now...
Great work seen by many developers.
When I first got my Kaiser, i tried HardSPL, and had "white screen" issue, I then followed instructions on "white screen" thread....copied cab to kaiser....ran cab from kaiser..........eventually was able to flash to a new/ different ROM
However, I recently flashed my Kaiser and after using it for 6-7 hours after flash, it soft reset itself. It continued to keep soft reseting itself without geting to boot screen. It kept reading "smart mobility" and it would reset, vibrate, reset, vibrate, reset.......
I tried EVERYTHING - remove battery, flash back to original ROM, change radio (bootloader worked in safe mode - holding down camera button), but to no avail.
I then tried MTTY, and no go with this too. I eventually had to give my phone back in to HTC.
The question I ask is what is the cause of this? Is it excessive flashing? Is is HardSPL? Any comments/ suggestions would be welcomed...
Many thanks
AvinashDhaniraj said:
Hi all,
I have been flashing/testing many roms for a numer of years now. I particularly enjoyed Jasjamming in my Tytn I days. Now...
Great work seen by many developers.
When I first got my Kaiser, i tried HardSPL, and had "white screen" issue, I then followed instructions on "white screen" thread....copied cab to kaiser....ran cab from kaiser..........eventually was able to flash to a new/ different ROM
However, I recently flashed my Kaiser and after using it for 6-7 hours after flash, it soft reset itself. It continued to keep soft reseting itself without geting to boot screen. It kept reading "smart mobility" and it would reset, vibrate, reset, vibrate, reset.......
I tried EVERYTHING - remove battery, flash back to original ROM, change radio (bootloader worked in safe mode - holding down camera button), but to no avail.
I then tried MTTY, and no go with this too. I eventually had to give my phone back in to HTC.
The question I ask is what is the cause of this? Is it excessive flashing? Is is HardSPL? Any comments/ suggestions would be welcomed...
Many thanks
Click to expand...
Click to collapse
Did you try removing the sd card, some times it can cause continues soft reset.
Regards
shafez said:
Did you try removing the sd card, some times it can cause continues soft reset.
Regards
Click to expand...
Click to collapse
I tried removing SD card.
Thanks.
I know you say you have been flashing for a number of years, but the question I have is did you normally HR prior to a flash as well as after a flash before setting up your ppc?
Dude I had the same problem.
It will take you prolly a few trys, but you can force your phone into the testing screen where you can install the rom over again, or install the correct radio, then do it again and reinstall the correct rom.
Use this button combination:
Press and hold: POWER BUTTON AND CAMERA BUTTON AT THE SAME TIME....
AND WHILE THEY ARE HELD IN, CLICK THE SOFT RESET BUTTON (HOLD IT IN FOR A FEW SECONDS AND RELEASE).. DONT RELEASE THE OTHER BUTTONS TIL THE PHONE GOES INTO DIAGNOSTIC MODE.
The trick is holding in the camera and power buttons as far as they'll go, because the camera button has a "press" setting and a deeper click setting. Seriously.
oh.. and this will only work if you have spl installed
edit: if you're doing this correctly and you still can't get it fixed..... all i can say is hook it up to a car battery some how and fry it... and return it.
P1Tater said:
I know you say you have been flashing for a number of years, but the question I have is did you normally HR prior to a flash as well as after a flash before setting up your ppc?
Click to expand...
Click to collapse
Yes, I do always and have always done that. It's funny you mentioned that, as I always did do this, and thought I'm over-precautious.
Thanks
nimda0 said:
Dude I had the same problem.
It will take you prolly a few trys, but you can force your phone into the testing screen where you can install the rom over again, or install the correct radio, then do it again and reinstall the correct rom.
Use this button combination:
Press and hold: POWER BUTTON AND CAMERA BUTTON AT THE SAME TIME....
AND WHILE THEY ARE HELD IN, CLICK THE SOFT RESET BUTTON (HOLD IT IN FOR A FEW SECONDS AND RELEASE).. DONT RELEASE THE OTHER BUTTONS TIL THE PHONE GOES INTO DIAGNOSTIC MODE.
The trick is holding in the camera and power buttons as far as they'll go, because the camera button has a "press" setting and a deeper click setting. Seriously.
oh.. and this will only work if you have spl installed
edit: if you're doing this correctly and you still can't get it fixed..... all i can say is hook it up to a car battery some how and fry it... and return it.
Click to expand...
Click to collapse
Hi
I did, go into boot mode (tri-color). I did manage to flash original ROM, and flash radio, but this didn't help. The phone continued to soft reset loop
AvinashDhaniraj said:
Yes, I do always and have always done that. It's funny you mentioned that, as I always did do this, and thought I'm over-precautious.
Thanks
Click to expand...
Click to collapse
NP. I hope u didn't take offense to the dumb question, but as you know, recently noone pays attention to what they are doing to this overpriced cell phone. I just know that by doing so, it helps get rid of all hang-arounds and tid-bits from previous rom istalls as well as cabs.
AvinashDhaniraj said:
Hi
I did, go into boot mode (tri-color). I did manage to flash original ROM, and flash radio, but this didn't help. The phone continued to soft reset loop
Click to expand...
Click to collapse
Exactly what rom (version and all) and what radio (version and all) are you using?
More info please....
I think you're using either the wrong combination, or something. The problem isnt spl, it's working if you can get to the diag screen (TRI COLOR).
nimda0 said:
Exactly what rom (version and all) and what radio (version and all) are you using?
More info please....
I think you're using either the wrong combination, or something. The problem isnt spl, it's working if you can get to the diag screen (TRI COLOR).
Click to expand...
Click to collapse
I used Duttys_Official_WM6.1_Rom_5.2.19716_UC (KAIS_Radinly_1.64.08.21_CustomRUU), then I flashed to L26_WM_6.1_PRO.V5
Is this a ROM or/and RADIO issue? Is it due to excessive flashing? We need to identify this problem, or else we will all be "flashing in the dark"......hoping that this doesn't happen....
I'm pretty sure it's a radio issue in your case.
I think you should use a different radio with that Rom.
Try reflashing the radio first, using the polaris radio. That's what me, my girl, and my friend are all using and it works PERFECT. Then reflash duttys rom after you've done the radio.
It should work fine. Let me know.
Post updated rom / radio versions once your done... and use the most current polaris radio and most current duttys rom.
I'm pretty sure it's not from excessive flashing because I am sure I flash at least twice a day whether it be a rom, radio, splash screen or whatever. I think I have seriously become a flash-a-holic.
No doubt.... he's got a radio / rom incompatability issue fo sho'
nimda0 said:
No doubt.... he's got a radio / rom incompatability issue fo sho'
Click to expand...
Click to collapse
I can't understand this as there are many users with the ROM/ RADIO combo I've used in these forums, and they don't seem to be having any problems
For what it's worth.. sometimes roms/radios can be a little glitchy. If you installed the rom first, then the radio, that couldve caused the problem. Did you?
If not, just try what I said.. see if it works. If not, you'll at least know it's not rom / radio specific and it has to be a device issue.
I think you'll find it works though.
Could it maybe be faulty NAND? I ask because of the Stuck On Boot Screen thread. While the problems aren't exactly the same, they are similar and having some faulty blocks holding old flash info could definately cause a crash/reboot loop.
jarek91 said:
Could it maybe be faulty NAND? I ask because of the Stuck On Boot Screen thread. While the problems aren't exactly the same, they are similar and having some faulty blocks holding old flash info could definately cause a crash/reboot loop.
Click to expand...
Click to collapse
Hi Jarek91,
How can one prevent/ repair faulty blocks holding old flash info?
Thanks for your comment
nimda0 said:
For what it's worth.. sometimes roms/radios can be a little glitchy. If you installed the rom first, then the radio, that couldve caused the problem. Did you?
If not, just try what I said.. see if it works. If not, you'll at least know it's not rom / radio specific and it has to be a device issue.
I think you'll find it works though.
Click to expand...
Click to collapse
Thanks for the suggestion, I did flash radio first then rom, but to no avail.
You can't. Always flash radio first, rom 2nd... with spl installed. You have to watch though because some roms will require certain radios, and others won't work.. so if you flash the radio first (on occasion) the rom will act up because of the radio incompatability.
I still say give it another whirl with the rom and polaris radio and see where it gets you... flashing radio first.
AvinashDhaniraj said:
Hi Jarek91,
How can one prevent/ repair faulty blocks holding old flash info?
Thanks for your comment
Click to expand...
Click to collapse
Well if it is bad NAND, the only fix is sending the phone back for repair/replacement. As for checking it, I'd talk with GSLEON3. He helped tmac with some MTTY commands to get some diag info that helped to lead to the diagnosis on his device. I'd help with that but I haven't yet had to delve into using MTTY to probe for issues so it's out of my area of knowledge.
Related
Hi guys!!
I'm really desperate.
Today I installed copilot 8, after a while the phone when goes in standby doesn't wake up anymore. When I press the menu button it remains down.
So I tried to reflash myhero 1.1.2 but in vain, and if I try to wipe I get the boot loop on hero logo.
The rotation doesn't work.
Please help me!!!!
Format your ext partition, wipe and flash again.
I use copilot 8 and the same ROM and I haven't that kind of issues on the full version of myhero v1.1.2! On a previous version on the 2.6.29 kernel when never I closed the copilot 8 the system crashed. Then I flashed the red's HTC kernel 2.6.27 and the issue never happened to me again. On this new version, the GPS is working fine for me! I just installed a fresh and clean ROM..
Do you deleted the save folder on the copilot 8, before re-installing the app or it was a fresh install? Is mandatory whenever you re-install the app.
When you install it, be sure you don't have this folder, no matter what is the situation!
Edit: I didn't read the second part of your issue.. Evil is right.. no other solution
It was the first install!
It can be a kernel problem?
Evil, when I try to wipe it goes in loop with the hero logo, do you think that formatting will work?
eViL D: said:
Format your ext partition, wipe and flash again.
Click to expand...
Click to collapse
I did it!
I also tried to change kernel with the three different versions but the problem is still alive!!!
Something new?
daeron666 said:
Something new?
Click to expand...
Click to collapse
I had this prob too.. after my micr sd card was set as damaged by the android sys and i wasn't able to start the device as well. But, the device was able to boot without the microsd card. Try it too. If so backup the information in your pc and format and remove the partitions of the microsd card (if you didn't do it before)!
I tried it, but the bug remains, I think it's something in the OS...
daeron666 said:
I tried it, but the bug remains, I think it's something in the OS...
Click to expand...
Click to collapse
My friend, the best solution is really to try it..install other rom, just for testing! ,,at least to have something to work on it.. step by step.. I use the same ROM, the newest version of copilot (and I previously was with olders ones without prob too), swapper, overclock, 2.6.29 red's kernel (without BFS), Engineered SPL, no radio changes, bla bla..
Gives a description of what is the state of your gear..
I already started to think that it can happen that some piece of hardware on the device is broken, but lets see.. no false alarms,,
Let's try to understand the status!
Of course! I have a 32a with no radio update, engineering spl 2010 and .29 kernel bfs. I Aldo tried without bfs but in vain.
The last thing left to do is trying another ROM....but there's a low level formatting method?
daeron666 said:
Of course! I have a 32a with no radio update, engineering spl 2010 and .29 kernel bfs. I Aldo tried without bfs but in vain.
The last thing left to do is trying another ROM....but there's a low level formatting method?
Click to expand...
Click to collapse
If there is, it was never spoken here.. the only way I see the internal phone partitions formating is when applying a new room...
Remove the sdcard/copilot directory and reinstall copilot
OR
Format your SDcard and reinstall copilot
Amon_RA said:
Remove the sdcard/copilot directory and reinstall copilot
OR
Format your SDcard and reinstall copilot
Click to expand...
Click to collapse
My friend, I think he tried that!
ricardomega said:
My friend, I think he tried that!
Click to expand...
Click to collapse
Yes of course, I tried that!
I also tried several roms, but nothing changes!
What can I do?
I'm really desperate.
daeron666 said:
Yes of course, I tried that!
I also tried several roms, but nothing changes!
What can I do?
I'm really desperate.
Click to expand...
Click to collapse
But without the copilot no issues, right? I'm using the copilot v8.0.0.328 kfc3.0 and you??
Excuse me, I'll explain better:
The problem is ALWAYS, with or without copilot, with or without sd...
daeron666 said:
Excuse me, I'll explain better:
The problem is ALWAYS, with or without copilot, with or without sd...
Click to expand...
Click to collapse
No need for excuses.. Man, "just" in my opinion.. you might have some broken hardware on your device.. I can't find any other answer. Flash back everything original like it should be and send it to warranty. There's SPL collections, there's original ROM's from HTC, etc etc..
I'm sorry.. I'm unable to help you.. Maybe someone has other idea, or something, but in opinion you a broken device..
Hi all,
I've a bit of a problem with my Omnia 7. It seemed to automatically do a hard reset over the weekend. All of the content was lost, contacts, messages, apps etc. When I tried using a few things, sending messages etc I got error messages about there not being enough storage, so I checked in Settings->About and it was only reporting 15.73MB installed. I tried a few hard resets from the Settings->About screen but they made no difference. I used the camera+volume down+power button combination to force a reformat and this says that it completes successfully, but the phone will then not boot, it just displays the Omnia boot logo (have tried leaving it a few hours).
I'm pretty sure it need to go back for a replacement but just thought I'd check if there was anything else I could try first?
Thanks,
Steve.
You can try to reflash. However, it might void your warranty, so make sure you check that beforehand.
To flash, register and download from
http://www.samfirmware.com/WEBPROTECT-i8700.htm
I8700XXJK1 ## 2010 November CSC_Cetus_Europe_I8700XENJK1
You will also need the drivers (Windows), the flash guide and the program.
Good luck.
Thanks, it's tempting to try a flash alright. I suspect it will void the warranty but I'll check.
I know this goes against the whole theme of xda lol but i'd say dont risk flashing and just send it back if hard reset doesnt work
comeradealexi said:
I know this goes against the whole theme of xda lol but i'd say dont risk flashing and just send it back if hard reset doesnt work
Click to expand...
Click to collapse
Not at all, it's perfectly within the spirit. We're here to help, that's why I also warned Steve, some things just can't be fixed.
Just realised I forgot to update on this, sorry.
It went back to Samsung who diagnosed a hardware fault on the motherboard, so they replaced it (under warranty) and it's working perfectly now again.
Thanks to all for the suggestions and help.
Hurray Good to hear!
Hi, decided to make this thread since I'm not getting help from the Ask questions thread. Friend of mine had me look into a N5 she got used and it's not working and wants me to see if I can get it to work. Thing is when you boot it up, it takes you to to the startup welcome screen no problem right to the 1st step which is choose a language, as soon as I select any language the screen stutters and the coloring goes all weird and goes to a black screen and sometimes reboots and back to the same welcome select language screen. I already tried wipiing everything, unlocking bootloader and wiping so I can get it back to stock as if it were new, I have no idea what they did to the phone but after doing that thought it would fix it but still having the same issue, any clues on what else to do? should i give up?
daLareid said:
Hi, decided to make this thread since I'm not getting help from the Ask questions thread. Friend of mine had me look into a N5 she got used and it's not working and wants me to see if I can get it to work. Thing is when you boot it up, it takes you to to the startup welcome screen no problem right to the 1st step which is choose a language, as soon as I select any language the screen stutters and the coloring goes all weird and goes to a black screen and sometimes reboots and back to the same welcome select language screen. I already tried wipiing everything, unlocking bootloader and wiping so I can get it back to stock as if it were new, I have no idea what they did to the phone but after doing that thought it would fix it but still having the same issue, any clues on what else to do? should i give up?
Click to expand...
Click to collapse
Have you tried flashing the factory image with fastboot? That's the first thing I would do.
_MetalHead_ said:
Have you tried flashing the factory image with fastboot? That's the first thing I would do.
Click to expand...
Click to collapse
You mean doing this, right?
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701/
Cause I tried that with no luck.
daLareid said:
You mean doing this, right?
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701/
Cause I tried that with no luck.
Click to expand...
Click to collapse
What do you mean no luck? Did you get an error message when you flashed it? Are you sure you did it correctly?
_MetalHead_ said:
What do you mean no luck? Did you get an error message when you flashed it? Are you sure you did it correctly?
Click to expand...
Click to collapse
I was able to go through with the whole process but after the reboot, I started up the phone but I'm still stuck on the Welcome screen, as soon as I choose a language the screen stutters and goes black.
daLareid said:
I was able to go through with the whole process but after the reboot, I started up the phone but I'm still stuck on the Welcome screen, as soon as I choose a language the screen stutters and goes black.
Click to expand...
Click to collapse
That's so strange. It seems like it would be a software issue but if you're 100% sure you were able to successfully flash a factory image then I really don't know what's going on. What software version did you flash? I would try to flash a factory image for a different software version. If you're on KitKat then flash a different KitKat image, if on Lollipop then flash a different lollipop image. Make sure to either run the flash-all.bat or to flash EVERYTHING in the image file that gets flashed in the script. That way you know 100% that the phone is back at factory conditions. If you're going to do it manually just open the flash-all.bat with a text editor and follow all the steps that are in the script and in that order. Take a screenshot of the terminal screen for me when it's done flashing.
_MetalHead_ said:
That's so strange. It seems like it would be a software issue but if you're 100% sure you were able to successfully flash a factory image then I really don't know what's going on. What software version did you flash? I would try to flash a factory image for a different software version. If you're on KitKat then flash a different KitKat image, if on Lollipop then flash a different lollipop image. Make sure to either run the flash-all.bat or to flash EVERYTHING in the image file that gets flashed in the script. That way you know 100% that the phone is back at factory conditions. If you're going to do it manually just open the flash-all.bat with a text editor and follow all the steps that are in the script and in that order. Take a screenshot of the terminal screen for me when it's done flashing.
Click to expand...
Click to collapse
Phone was on kitkat so I did it with kit kat, I just flashed 5.0.1 on it and it did go through because it did boot to the Lollipop Welcome screen but same thing happened as soon as I selected a language screen stuttered and stopped working.
daLareid said:
Phone was on kitkat so I did it with kit kat, I just flashed 5.0.1 on it and it did go through because it did boot to the Lollipop Welcome screen but same thing happened as soon as I selected a language screen stuttered and stopped working.
Click to expand...
Click to collapse
So this happened on KitKat as well as Lollipop? I don't know what to tell you then, it seems like it's a software glitch but that's pretty much ruled out. I wonder if it has something to do with data... like it's freaking out when it gets to the point that it has to transmit/receive data. Try doing it with WiFi on and off, SIM card in and out, and try flashing a different radio. If it still does it every time then I guess I'd RMA it.
_MetalHead_ said:
So this happened on KitKat as well as Lollipop? I don't know what to tell you then, it seems like it's a software glitch but that's pretty much ruled out. I wonder if it has something to do with data... like it's freaking out when it gets to the point that it has to transmit/receive data. Try doing it with WiFi on and off, SIM card in and out, and try flashing a different radio. If it still does it every time then I guess I'd RMA it.
Click to expand...
Click to collapse
Unfortunately I can't set any of the setting such as WiFi on or off because as soon as I tap on something the screen goes off, I guess it might be hardware (screen) related, thanks for your help.
daLareid said:
Hi, decided to make this thread since I'm not getting help from the Ask questions thread. Friend of mine had me look into a N5 she got used and it's not working and wants me to see if I can get it to work. Thing is when you boot it up, it takes you to to the startup welcome screen no problem right to the 1st step which is choose a language, as soon as I select any language the screen stutters and the coloring goes all weird and goes to a black screen and sometimes reboots and back to the same welcome select language screen. I already tried wipiing everything, unlocking bootloader and wiping so I can get it back to stock as if it were new, I have no idea what they did to the phone but after doing that thought it would fix it but still having the same issue, any clues on what else to do? should i give up?
Click to expand...
Click to collapse
Did you ever find a fix for this ?
qzcgd said:
Did you ever find a fix for this ?
Click to expand...
Click to collapse
No, I later found that some of the hardware inside (motherboard maybe? not sure which part) but that it was most likely from some irreparable damage to it, and it seemed worthless looking for a piece of an old phone to repair.
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 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.