Related
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.
I had successfully unlocked my galaxy s using the procedure suggested on the related XDA forum.. the phone worked fine with a different network later on i accidently clicked the factory reset option.. now although the phone says its unlocked but i cannot see any network signal and the phone does not work on any sim card.
Pls can someone help
PS: I can switch on the phone and perform all other functions.
asif1981 said:
I had successfully unlocked my galaxy s using the procedure suggested on the related XDA forum.. the phone worked fine with a different network later on i accidently clicked the factory reset option.. now although the phone says its unlocked but i cannot see any network signal and the phone does not work on any sim card.
Pls can someone help
PS: I can switch on the phone and perform all other functions.
Click to expand...
Click to collapse
I could not say for sure because I don't know what process you used, but I Would say you just may need to downlaod the Factory TAR file using oden into your phone. Just make sure you Don't use the PIT file when you do it. Look in the Android Development section for the Tar file and the process of using Oden.
thanks for the reply.. did try loading just the tar files using odin but still no progress... another info, when i turn on the phone the notification drop-down does show the name of the network and says no service.. does that ring a bell ??
Cracked it !!
turns out that the software factory reset isn't all that effective and i tried the the hard reset by entering the code *2767*3855#... it worked like a charm and this time I had the carrier signal !!!!
asif1981 said:
turns out that the software factory reset isn't all that effective and i tried the the hard reset by entering the code *2767*3855#... it worked like a charm and this time I had the carrier signal !!!!
Click to expand...
Click to collapse
Good to hear you resolved your issue.
Hi, is having a corrupted IMEI prohibits you from getting network signal? I have weird IMEI characters (not numbers) after unlocking SGS4G and I cannot get any netwrok signal. Hope you can advise me what to do or check. I have exactly the sasme IMEI with this post.
http://forum.xda-developers.com/showthread.php?t=1030728&highlight=imei
hey man. try this and see if it helps at all:
http://forum.xda-developers.com/showthread.php?t=1142829
jager555 said:
hey man. try this and see if it helps at all:
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
Hi Jager555, do you think it would be wise to try it out. I am not that confident to try it out because we have a different IMEI situation and I am afraid to brick another phone (bricjed captivate before). That is why I am waiting for someone to update the toher thread because that thread has the same IMEI that I have. If I won't be bricking my phone, then I would more than happy to try it out.
did you try disabling wifi calling? Same thing happened to me
Sent from my SGH-T959V using XDA Premium App
i cant guarantee that you wont brick your phone. its just something to try. as ricky said, disable the wifi and see if that helps, but if not, your phone doesnt work either way. im not sure if you can flash another rom and see if that helps too.
the thread i posted said "I recently used one of the unlocking tools that are available on the Android market, and one of them screwed up my IMEI so badly (it contained garbage characters, not just numbers)"
i figure thats the problem you have. if you dont want to try it, bump this thread and try to get a response from the smarter people. lol. im still a noob, good luck! i hope you get it fixed soon.
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.
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
fefin said:
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
Click to expand...
Click to collapse
Have you reached out to Samsung yet?
Mr. Orange 645 said:
Have you reached out to Samsung yet?
Click to expand...
Click to collapse
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
fefin said:
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
Click to expand...
Click to collapse
I mean have you called or emailed Samsung?
Mr. Orange 645 said:
I mean have you called or emailed Samsung?
Click to expand...
Click to collapse
No I haven't, I will give a try soon through web chat.
I mean, this shouldn't be happening, it's a brand new phone, all over the internet are people with the same problems as me and looks like so far there is no solution.
Maybe it's a faulty phone/hardware? My knowledge is not enough in this matter.
See you!,
Federico.
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
allenjthomsen said:
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
fefin said:
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
Click to expand...
Click to collapse
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
allenjthomsen said:
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
Click to expand...
Click to collapse
Sadly it didn't work. The phone is still loading till "android is starting" sign and then restarting again.
I will write you so you can help me through pm, could this be a faulty hardware?
I'd like to know the other solution too.
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
try installing PartCyborgRom
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone ??
Sent from my SM-G955W ??
allenjthomsen said:
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your help! Much appreciated.
DR25 said:
try installing PartCyborgRom
Click to expand...
Click to collapse
Thanks for your suggestion, I will look into it.
shaggyskunk said:
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone
Sent from my SM-G955W
Click to expand...
Click to collapse
Thanks for answering!, sorry for my late response.
Well, if you check samsung's official forum there are a few threads with 15+ pages of people complaining about wifi issues (https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/862/page/1 and https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/30601/page/1) about bootloop problems, (https://us.community.samsung.com/t5...id/GS8QA/thread-id/3920/highlight/true/page/1) also there is a post on another webpage talking about bootloops on this model and how to fix them (https://thedroidguy.com/2017/12/sol...p-issue-s8-turns-screen-remains-black-1079013).
I know it's not representative, as you said, millions of phones has been sold, but what I meant when I said "all over the internet" is that you can easily find people with this same problem. This shouldn't be happening, not on any phone even less on such an expensive phone.
I think the phone is officially dead, I took it to a well known local technician and even him couldn't fix it. My nearest official samsung service is 1600km away. On the other hand, my aunty got for herself an S8 and it's working perfect, so it's just bad luck for my mom I guess.
The phone had issues since she bought it (wifi and bluetooth didn't worked at all, but she is not really a tech person so she thought it was fine), the phone was working with some bootloops from time to time and after a while it fell from and got a little crack on the top but it didn't change the behavior of the phone, it was still ****ed up. That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
fefin said:
That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
Click to expand...
Click to collapse
If you have some 'proof' the problem existed, before the crack, and can prove when the crack occurred, or reasonable determinate approximation, small claims court will vindicate you, and Samsung will have to pay.
Sad to say would take a little time of yours to get them there, but it is an easy process, and with reasonable ability to determine/evidence those two things, a sure win.
But still a PITA.
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)