Related
To my understanding (which isn't much) is there no way to fix a bricked phone? yes i mean bricked. no power, notta...
dyefalcon1 said:
To my understanding (which isn't much) is there no way to fix a bricked phone? yes i mean bricked. no power, notta...
Click to expand...
Click to collapse
no power = bricked
give us details on what happened
and btw questions like these go in general and is not dev related
Do you know for sure that it is bricked? I assume youve done a battery-pull?
What event preceded the bricking?
EDIT: DS36 beat me to it
i was gonna try the new updated radio just posted so i powered off to do a nand backup and there was just an android on the screen. pulled battery out now the phones dead. i flashed droid does 1.1 last night...
leave the battery out for 10-15 minutes and try again.
ban_dover said:
leave the battery out for 10-15 minutes and try again.
Click to expand...
Click to collapse
+1
and maybe pop-out the SD card, boot without it or at least make sure its seated properly.
Have you tried to boot into recovery (VOL-UP + power)? I know this wont work if its truly bricked, but just try everything.
Oh and if you do get it to boot, perhaps wait on flashing that new radio -- admonishments in other threads re:flashing the radio discuss the real (albeit small) risk of bricking after a bad radio flash.
I want to give that new radio a try to, but I will probably give a bit more time.
dyefalcon1 said:
i was gonna try the new updated radio just posted so i powered off to do a nand backup and there was just an android on the screen. Pulled battery out now the phones dead. I flashed droid does 1.1 last night...
Click to expand...
Click to collapse
aaahhhhhh !
You pulled the battery while flash the radio ???????
Fyi never ever pull a batter while flashing anything son
droidJW said:
+1
and maybe pop-out the SD card, boot without it or at least make sure its seated properly.
Have you tried to boot into recovery (VOL-UP + power)? I know this wont work if its truly bricked, but just try everything.
Oh and if you do get it to boot, perhaps wait on flashing that new radio -- admonishments in other threads re:flashing the radio discuss the real (albeit small) risk of bricking after a bad radio flash.
I want to give that new radio a try to, but I will probably give a bit more time.
Click to expand...
Click to collapse
I HAVE THE NEW RADIO TOO
ITS WORKS JUST FINE
dont be scared
DS36 said:
I HAVE THE NEW RADIO TOO
ITS WORKS JUST FINE
dont be scared
Click to expand...
Click to collapse
HA ! I need that pep talk.
I downloaded the radio earlier and was about to flash when I saw this thread ( I know the radio isnt the issue here, but made me second-guess).
I am the guy that routinely flashes BIOS updates on my PCs, in spite of the "dont fix it if aint broke" warnings on BIOS updates. I have done 100+ BIOS flashes on various PCs -- never had an issue. Funny, my PCs are all worth more than my Eris...and yet, I hesitate on flashing this radio. I'll get to it !
droidJW said:
HA ! I need that pep talk.
I downloaded the radio earlier and was about to flash when I saw this thread ( I know the radio isnt the issue here, but made me second-guess).
I am the guy that routinely flashes BIOS updates on my PCs, in spite of the "dont fix it if aint broke" warnings on BIOS updates. I have done 100+ BIOS flashes on various PCs -- never had an issue. Funny, my PCs are all worth more than my Eris...and yet, I hesitate on flashing this radio. I'll get to it !
Click to expand...
Click to collapse
Thats the spirit
and befefit from a faster wifi
ha thats how I bricked my phone got the little android guy on my phone and pulled the battery. To get off that screen so just for future ref. if that happens when flashing a radio what should I do? Wasnt too big of a deal since under warranty but just curious if I should have just waited before pulling the battery and all would have been fine?
Yeah when the little android guy comes up wait cuz after a bit it will reboot and go jnto recovery then just reboot again then u good
Sent from my Eris using XDA App
I guess I should have waited instead I freaked out instantly all is good though new eris re-rooted no problems I will have more patience next time flashing a radio though.
edgeupgx said:
I guess I should have waited instead I freaked out instantly all is good though new eris re-rooted no problems I will have more patience next time flashing a radio though.
Click to expand...
Click to collapse
Yep just be pantient, everything with flashing be patient lol good to hear ur back up and going
Sent from my Eris using XDA App
yeah idk whats going on but its still under warranty so ill just send it in for a new one
I am currently unable to boot into anything, no RSD, no Fastboot nothing. I try holding down up volume and down volume. Here's what it says when i try to power up.
SVF 105:1:2
Failed to boot 0x1000
Here's what i did.
I followed the steps exactly to install the stock 2.3.4 ATT update. Everything was fine. Then i decided to start over and install kennethpenn's custom rom. So i tried to flash the 1.8.3 sbf.
i foolishly started surfing other websites and didn't pay any attention to my phone. then when i looked back it was completely black screen and RSD lite said:
Failed flashing process. Failed flashing process. Phone {0000}: Error switching phone to BP Pass through mode (0x70BE); phone disconnected
Thats it. now i can't do anything. Please help.
It's called "bricked". Now search for that term and you'll find answers!
Yeah, I think you're screwed their man... Kennethpenn had the same issue with his Atrix I think.... $600 brick
doesnt sound good...
where in the process exactly did you decide to start over and install kenneths custom rom?
i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
b3nman said:
i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
Well you got nothing to lose.
i
i have the same problem gonna play dumb and get a new one today under warranty
yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
Nice. Tell us how it works out, good luck!
yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
What did you do to cause it? Same thing as OP?
I'm tellin ya I think there is something wrong with that damn 1.83 sbf itself! The older ones never had any problems! I'm done with it!
LayzeeEyez said:
What did you do to cause it? Same thing as OP?
Click to expand...
Click to collapse
yeah, has anyone else tried to flash back to 1.83?
b3nman said:
i know its bricked. i'm just wondering how bricked...
Click to expand...
Click to collapse
If it does not go to the moto logo screen that means something messed up your IPL/Bootloader, which means you are pretty screwed.
b3nman said:
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
You could just say that you never got around to updating to 1.8.3 (kind of a long shot since it reminds you every hour), and when you installed the update it would not restart. If you have a backup phone, you could just wait till the new update releases and use the same excuse.
If you hard bricked, there is most likely no way they can check if you were messing around with anything. It is worth a shot, but like you said just play dumb
http://forum.xda-developers.com/showthread.php?t=1160408 <- For future reference
im sorry this happend to you guys, i hope everything goes well with insurance and what not. i made a warning on the guide for people not to flash back until a safe method is found!
i had ur problem a few seconds ago!
rsd stoped at " switching phone to BP Pass through mode " at 33%.
and after a hour nothing happend!
i decided to disconnect the phone but after that i lost RSD,fastboot,.....
i removed the battery for a while and after that i powerd the phone up but it was the same as before.
i left it on moto red logo and after a few second it said:
failed to boot 4
starting RSD mode
and now its working!
but i didnt get " Failed flashing process " like you!
i got one coming through warranty be here no later then tuesday
i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.
b3nman said:
i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.
Click to expand...
Click to collapse
anyone have a cwm backup pre 2.3.4 they can try?
att is sending a new one. it was easy since i'm still within the 30 days of opening my account. lesson learned:
THOROUGHLY READ ALL WARNINGS!!! I hope my fail can prevent others from going through it. THANKS EVERYONE!
is this 4.5.91 specific? I flashed between 4.5.40 and 1.83 sbf a few times without problem.
I've been ROM-hopping, trying Synergy, Alliance, Myn, and several others. On the last one, MikG 2.3, I had it loaded up and working fine. I started installing apps from the Android Market. That, too, was going fine, until it suddenly rebooted in the middle of an app download/install.
It went to the white screen with HTC EVO 4G on it, and then went black, then back to the white screen, over and over.
Six hours later, I'm still stuck in the loop. To make matters worse, I accidentally lost root (I see "S-ON" at the top). So now I'm stuck without root until GB is rooted successfully, which hopefully isn't tooooo far off in the future.
But that's the least of my concerns. I would be extremely happy with a stock install of any sort at this point, but I can't get anything to load. No recovery, no ROMs, but I can get into HBOOT so I'm able to try to load any PC36IMG.zip files. The last one I tried was the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed.zip" (renamed to just PC36IMG.zip, of course). It appears to load just fine and in the end says "Update Complete... Do you want to reboot device?"
I choose yes, it reboots... and we're back in the loop. I have no idea what to do or try at this point. Any help anyone can provide would be greatly appreciated! My next step is to take it to the Sprint store, but that's over an hour away and will have to wait till the weekend.
Thanks everyone!! If you need any more information, let me know. Believe me, I'll be monitoring this thread closely!
/Kevin
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Papa Smurf151 said:
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Click to expand...
Click to collapse
Yeah, I tried. I have several SD cards of varying sizes (4GB, 8GB, and my primary 16GB). Formatted the 4- and 8GB ones and tried from each, but no go. Thanks for the try though!
/Kevin
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
trim81 said:
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
Click to expand...
Click to collapse
Just did it and the process went well, said it was successful... but it's still stuck in the same loop. I'm thinking the phone is beyond repair. Thanks for trying, though. It really looked like it might work for a second.
/Kevin
what was the app?
That's what I want to know and how do you get accidentally to S-On?
Put the phone in a refrigerator ... as crazy as it sounds, it might be the infamous overheating issue.
Put in refrigerator, for about 5min
The app was "Kid Zone" (Zoodles), but I'm not blaming the app by any means. I've used it for a long time, it's highly-rated in the market, etc. I'm sure it's just a coincidence.
As far as getting back to S-ON, I think it must have been when I flashed the stock recovery. I was flashing so many things out of desperation that I can't swear to that, but I'm pretty sure that's what did it. Now that it looks like I'm heading to the Sprint store tomorrow, I guess it's a GOOD thing it's back to S-ON. Heh.
Pretty sure it's not heat-related. My phone was off all night (since it's not usable) in an air conditioned room, so it's cool to the touch. I tried the RUU process again with the same results. (I'm not sticking it in the refrigerator, because I'm afraid of activating the water-damage sensor -- I don't want any excuses from Sprint when I bring it in tomorrow!)
Appreciate the help!!
/Kevin
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
HipKat said:
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
Click to expand...
Click to collapse
I hear ya. I haven't run into any techs at my local stores that are knowledgeable about this kind of stuff. (I know others have, so you never know, but I have yet to see one.)
/Kevin
To conclude this: I went to the Sprint store today where they assured me they would reload the software but it would take 1.5 hours. I came back 1.5 hours later... and they handed me a new (refurb) EVO. They said they weren't able to load anything on the phone.
So, no surprise with the outcome there. I was fairly certain they were going to have to replace the EVO, and they did.
Thanks to everyone who tried to help, but it was just beyond help!
/Kevin
I had that same problem with my phone back in November. Continues boot loop. Finally, having boot loop for 8hrs, I took it to Sprint and they replaced my phone. They called it a power cycle issue. $35 new refurbished phone works well. Never had a problem since.
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
chip102 said:
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
Click to expand...
Click to collapse
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
TheMadScientist said:
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
Click to expand...
Click to collapse
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
chip102 said:
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
Click to expand...
Click to collapse
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
TheMadScientist said:
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
Click to expand...
Click to collapse
Replaced Daughter board and battery. No improvement :/ bummer
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
chip102 said:
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
Click to expand...
Click to collapse
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
TheMadScientist said:
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Click to expand...
Click to collapse
chip102 said:
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/development/root-t3904613. This thread can help you at least get pie back up and running. I wouldn't mess with no more. I haven't had much luck with mine. But I did get it booting again