I have managed to delete the whole OS without backup and custom recovery. I also deleted the single launcher I had on my previous device. Tell me your biggest blooper you spent hours fixing.
When I was 11 yo, I saw "fastboot mode started" after a badly flashed ROM, I've decided to reflash the whole phone, which ended up in a fully bricked NAND Flash, being the partition table corrupted.
R.I.P LG-P500/h, you were a good friend.
I messed up real bad with my first Moto G. This was the time when Kikat 4.4.4 OTA came out and I should have checked the forums before updating anything(from 4.4.3 to 4.4.4) and needless to say, I had hard bricked my phone due to OTAs reacting violently with unlocked bootloaders. What's worst that my bootloader was unlocked I knew there was no way I was getting a replacement device but somehow I had fooled the warranty centre, because they couldn't boot to fastboot mode to check warranty status and in fact second they couldn't boot it at all so I got a freaking replacement device.
Sent from my XT1033 running good ol' Stock ROM
I think the worst I've done is forget to move a zip to my card before a reflash on a phone, meaning that I did a full wipe and RSD to a specific firmware then didn't have the ROM version that I needed for it. Led to yet another RSD session back to stock, getting the zip to the SD, then RSD again, then flashing the ROM.
Not too bad really, just time consuming.
My biggest mistake was buying a Samsung phone.
Trafalgar Square said:
My biggest mistake was buying an Samsung phone.
Click to expand...
Click to collapse
Yeah,i agree to that...
Trafalgar Square said:
My biggest mistake was buying a Samsung phone.
Click to expand...
Click to collapse
Don't worry. We all reach that point where we just give up on Samsung phones, because let's face it, Samsung is only worth it when you buy NOT low budget phones.
Sent from my XT1033 running good ol' Stock ROM
I told a guy I could update his rooted Kindle Fire HD. Ended up formatting the whole thing wiping the current rom, the backup and the zip I was about to flash. Tried for days and even rang in sick to work to get it working. In the end I ended up buying him a new iPad mini. Next day I sideloaded a rom on the damn thing!
Truth be told, I've still got it and it's a damn awesome little tablet.
Sent from my HTC 10 using XDA Labs
rooted my first phone the first week i got it and bricked it, panicked the whole weekend trying to fix it and thankfully fixed it by the following week
My brother Put on a tempered glass On his gionee and dropped it In the road to test it .the fall only damaged the glass and but a bike ran over it
dropped it
without unlocking bootloader properly installed random buggy ROM on Moto E and then bricked my phone.!
recovered after 1 day of internet seraching.!
Bought a cheap ass Screen Guard from a local dealer. Wanted to test it out. Dropped it from about 5 feet in air.
Goodbye Phone. Yeah it sounds noobish. But I was 12 when I did it
using it as a "personal stimulation" device on a girl. you dont wanna use that phone after that. GG
I accidentally deleted my system partition.
hehe, what a story, 4 years ago, when i was 13,5 years old. It was the first time a had an android(s7562) phone, as i had only symbian(n97) (i had some experiences with symbian as i had flashed it with JAF with some better CFWs, curruntly using a CFW made by Omar_Bazaraa).
Then i started learning android with a symbian'ish background(how to install qt? where's pips,sdl?...hhhh).
I did some foolish things, the worst thing i did is that is downgraded it to GB's cm7 (WHILE CM DOESN'T EXIST TO OUR PHONE AT ALL!, I TRIED A FOOLISH WAY TO PORT IT!).
Well, this caused it to no longer boot in recovery, so i stuck in B.L until i reflashed agin.
Thx for reading,...
Trying to unscrew a screw in order to open the phone. The screw was stucked though and I accidently destroyed the display because it was right under it.
Considering it was my first and only phone, I had to spent lots of time without an phone afterwards
Haha! Install custom Rom in my clean android
Deleted
The biggest mistake with an android phone i´ve ever made was flashing something to a device from a laptop and forgot to plug in the external power suplly. Exacly in the moment i started flashing a system img the battery from the laptop was down to 10% and it shut off itself. After that the phone was never again able to get a fastboot connection. Luckily twrp was already flashed on the device and so i could use it for more then one year xD
Related
a few days ago my fiance was complaining her basically stock Nexus was rebooting into a bootloop - where it displays the loading X and vibrates and then reboots and repeats every few moments (a few days after her doing the system update)- if I remove the battery for a few minutes then put battery back and reboot it will boot into the OS where it will stay sometimes for a few minutes othertimes an hour or more before going into the bootloop- so I told her I would attempt to flash a new rom. after many hours of messing with the phone and attempting to access the recovery it just will not work- the phone just goes into the bootloop - exactly as mentioned above. I have used fastboot to flash new images (userdata, system, boot, recovery etc) numerous times and it still does the same thing- crashes and reboots into the bootloop from the OS randomly and bootloop when trying to access recovery. I am pretty sure it is a hardware issue (the phone is only 3 months old) but the company i bought the phone from is stating it is a software issue and not covered by tehir warranty.
Problem is I unlocked the bootloader while messing with the rom's yesterday and am now concerned they wont honour the warranty anyway- does anyone have any suggestions as to anything else I can try? As far as I can tell as I cannot access recovery I cannot install any other roms..
Please help- otherwise I will be posting a yourtube video of me destroying a basically brand new nexus one- I really am that frustrated....
a bit more info- it was rooted but still had locked bootloader when this started- rooted using onclickroot or something- which after the update it wasn't rooted anymore- I am wondering if this has caused some low level conflict somehow- I have rooted again using superoneclick - and as stated have unlocked the bootloader.
is there any way to flash a rom using fastboot or adb on this thing- I would hazard surely there is but amongst all the information floating around for this phone I cannot find out how- I am thinking maybe I try and load cyanogen 6 or something if I could work out how to flash a rom using adb (because njo matter how many times I try to flash different recovery images it wont boot into recovery- I can access fastboot etc but as soon as i select recovery I get the bootloop...
and before I get flamed I have spent three days searching and reading and attempting everything short of voodoo witch magic. I thought my X10 was a P.I.A. to root and flash etc but really it was simple compared to the trouble this phone has given me..
I am wondeirng if some of the rom's are incompatible with some hardware- and I don't quite understand the whole radio thing either... can someone explain that?
BTW Im not a total noob- I have been around for a while without an account - then have had this account for a while but mostly just read the forums as I have no real input and knowledge to give...
...help!
Can no one help?
I have managed to get into recovery (by putting the phone in the freezer for ten minutes at a time to reduce the temperature and stabilise it enough to run for 15-20 minutes at a time)...
Have flashed different kernels this way and nothing is stable- it still bootloops because of heat....
I contacted HTC Hong Kong (it was purchased from a Hong Kong company) and they have told me there is a $350 fee to repair it as its a UK phone. Now the phone is exactly 55 days old not three months and I am really really frustrated.
Does anyone know if its worth contacting HTC UK?
I have friends in the UK I can have them send it in and recieve it from repair....
Someone please help- even if its just a comment of "just smash the damn thing..."
Thanks guys sorry about the long self centred posts but I am ready to destroy this phone- it doesnt have a mark on it either- any ideas what its worth for spare parts?
Ok....you have heard this many times before but Ill ask anyways in the event someone can help me.
I am a newbie to rooting although Ive had my Note for months.
This morning I rooted successfully .
I also dloaded clockwork mod and watched YouTube tutorials on it.
Then I thought id try flashing a new ROM and Paranoid Android looked the easiest. Just two files - the zip and the fix. So i downloaded them to my CD card and then booted from RomManager into recovery mode.
Here is where I truly stuffed am I am guessing.
First I went into the immediately available option of 'instal file form SD card" and tried loading both Paranoid Android rom files .
I got Signature not verified etc
So then I went a step further and went into the clockwork mod folder instead ( where all font is blue and it becomes a touch screen menu ) and both files were there also so I hit the Paranoid Android zip file and it seemed to be actually doing something so i thought you beauty ! Some white lines of text came out, it stalled for a few minutes and then the phone just turned off and that's the way it is. DOINK.
I cannot turn it on.
I cannot boot into recovery mode.
My pc doesn't recognize it as a drive.
Kies wont recognize it.
so I have two questions ;
A) Is it resuable ?
b) Of I cant do it will Samsung service center be able to re-load the OS or whatever or is the unit well and truly fried ?
thanks
You obviously did not read the OP since procedure is clearly explained. What you did is just nonesense.
Does download mode works?
Sent from my GT-N7000 using XDA
To the OP:
Did you flash Parnoid Android rom over an ICS rom, that's what I did and my Note was hardbricked. I got my Note back yesterday from the repair centre, its easy to forget to remember to read the instructions sometimes and it can happen, not to worry though...its not the end of the world, the repair centre is an option
Sell?
Sent from my LG-P999 using xda premium
you dont provide enough info..mainly exactly what rom and kernel you were on when you tried to flash Paranoid.
Maybe he should start writing in the correct forum (Q&A) and even better: read there first and find a lot of related threads and exact informations.
Take seals advice. He's an expert now lol. Btw glad to see you got your phone back! Get that rom going!
Sent from my GT-N7000 using XDA
g2tegg said:
Take seals advice. He's an expert now lol. Btw glad to see you got your phone back! Get that rom going!
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
You guys are going to keep teasing me about my bad rom aren't you's?
Btw...I didn't brick my phone due to my rom, I bricked my phone because I flashed a CM9 rom over a ICS rom (my rom was based on a ICS rom).
Can you get into download mode?
Service Center here you go!
Beretta93 said:
You obviously did not read the OP since procedure is clearly explained. What you did is just nonesense.
Does download mode works?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Actually i read up extensively on it . I am just useless at following instructions. Not all of us have propellers sticking out of our heads.
Dload mode ? What part of it doesn't turn on etc isnt clear......
SealsNavie said:
To the OP:
Did you flash Parnoid Android rom over an ICS rom, that's what I did and my Note was hardbricked. I got my Note back yesterday from the repair centre, its easy to forget to remember to read the instructions sometimes and it can happen, not to worry though...its not the end of the world, the repair centre is an option
Click to expand...
Click to collapse
I flashed from the recent android 4.0.3. Asian version ( I am in Cambodia ) . I believe the mistake i possibly made was going in to CWM files in recovery mode and doing it from there ?
Anyways....its back with Samsung RC now so hopefully they can rectify back to normal . I hope they dont see all the root files etc in the SD card. This is Cambodia so I doubt they'll care.
They'll be fixing the screen i cracked a few weeks ago too. Dropped it and it chatter like a bullet hole. So....my note will be all minty when i get it back....albeit $180 later !!
jgarnett said:
So....my note will be all minty when i get it back....albeit $180 later !!
Click to expand...
Click to collapse
Is that all, It'll cost me over $200 JUST to get the screen fixed...
jgarnett said:
I flashed from the recent android 4.0.3. Asian version ( I am in Cambodia ) . I believe the mistake i possibly made was going in to CWM files in recovery mode and doing it from there ?
Anyways....its back with Samsung RC now so hopefully they can rectify back to normal . I hope they dont see all the root files etc in the SD card. This is Cambodia so I doubt they'll care.
They'll be fixing the screen i cracked a few weeks ago too. Dropped it and it chatter like a bullet hole. So....my note will be all minty when i get it back....albeit $180 later !!
Click to expand...
Click to collapse
You cannot flash PA over ANY ICS rom. This is what caused your brick.
Sent from my GT-N7000 using xda premium
ultramag69 said:
Is that all, It'll cost me over $200 JUST to get the screen fixed...
Click to expand...
Click to collapse
Yes, i came from cambodia too, actually for that price over there it's quite expensive.
any way, good to know that some one from cambodia is using Galaxy Note, impressive!
EVERYONE is using the Note here. Especially the girls. They love it even though they can barely hang on to it
$180 is for the Screen only. I believe ill get the OS redone for free.
jgarnett said:
Actually i read up extensively on it . I am just useless at following instructions. Not all of us have propellers sticking out of our heads.
Dload mode ? What part of it doesn't turn on etc isnt clear......
Click to expand...
Click to collapse
Yeah you really suck at following instructions since you didn't do anything correctly.
You saying it does not turn on is indeed unclear, since you mention right after "it does not enter into recovery mode". So if you made the distinction., one can wonder...
So if you can't turn it on at all, including download mode, your phone is hard brick and needs to go to RMA, and since it is not due to emmc bug obviously, rma can be refused by Samsung because if they investigate they'll see that you flashed a different recovery.
Sorry dude, it's just about how lucky you are now...
Sent from my GT-N7000 using XDA
Beretta93 said:
So if you can't turn it on at all, including download mode, your phone is hard brick and needs to go to RMA, and since it is not due to emmc bug obviously, rma can be refused by Samsung because if they investigate they'll see that you flashed a different recovery.
Click to expand...
Click to collapse
Here is the rub.
Samsung rang me yesterday and said the phone needs;
New Screen at $150
New motherboard at $150
New front camera at $25.
Ouch
However....
Apart from the cracked screen (which happened weeks ago) up until I rooted and then ****ed the phone with my atrocious attempt at flashing the new ROM....the phone was working with no worries at all.
Can I ask the techs here as I have no idea ;
Would the motherboard be a victim of the flashing attempt ? If so....I am in the wrong and will pay all monies. I am guessing it is directly related as the phone was fine until the flashing attempt. If not......would the shock from the fall weeks ago have caused a failure in the MB ? Or could that just not be related at all ?
Basically, I am wondering if i have a leg to stand on with trying to claim warranty on the MB ....When they contacted me yesterday there was no mention of the phone having been rooted " you have been a naughty boy !! ". Actually what they said was " you dropped your phone and now the motherboard is broken "
thanks
jgarnett said:
Here is the rub.
Samsung rang me yesterday and said the phone needs;
New Screen at $150
New motherboard at $150
New front camera at $25.
Ouch
However....
Apart from the cracked screen (which happened weeks ago) up until I rooted and then ****ed the phone with my atrocious attempt at flashing the new ROM....the phone was working with no worries at all.
Can I ask the techs here as I have no idea ;
Would the motherboard be a victim of the flashing attempt ? If so....I am in the wrong and will pay all monies. I am guessing it is directly related as the phone was fine until the flashing attempt. If not......would the shock from the fall weeks ago have caused a failure in the MB ? Or could that just not be related at all ?
Basically, I am wondering if i have a leg to stand on with trying to claim warranty on the MB ....When they contacted me yesterday there was no mention of the phone having been rooted " you have been a naughty boy !! ". Actually what they said was " you dropped your phone and now the motherboard is broken "
thanks
Click to expand...
Click to collapse
your phone its super bricked due to wiping the phone in an ics kernel and its all samsung fault for the brick bug but you could avoid that flashing abyss kernel before wiping your phone and yes brick bug fry your motherboard.
You just superbricked a Super Phone
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Be in safe kernel if your on ics. You could check your device of the bug by downloading eMMC check in google play. Dont put your fate in that if your on stock ics rom not rooted you will not get the bug, be on the safe side.
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Just check the service job sheet whether they replaced the mobo or not before taking the delivery ? As simple As that.
got my gnote back with new mobo
Well, it is almost like the 'law of attraction'... I didn't want any problem and when I got my gnote today... guess what ? phone vibration didn't work. I had to go back to the SSC.
Fortunately, they responded immediately and the SSC guy fixed it on the spot without another round of formal servicing process. As explained to me, an insulation sticker of the vibrator was not removed while slipping in the new mobo. I didn't care less to understand if that is true as I was excited to get my phone with 11GB internal storage .
All seem to be working fine as of now with stock ICS 4.0.4 :good:
So my phone's not yet fixed since the 25th of December due to sudden death - http://forum.xda-developers.com/showthread.php?t=2585068
We had it checked again last Thursday, January 3rd. The technician said that the replacement of motherboard is not yet clear to be the best solution as the technicians from the Sony Service Center hadn't opened the phone yet. He said that it might have been a cause of a dead or death boot. Has anyone heard of it? He says not only Sony phones are experiencing this dead or death booth, even other brands. Kind of random.He said that the phone somewhat hangs, the screen isn't on but the system is still running which causes the phone to become warm or hot. And he also said that this lead to the battery getting totally drained. As per him, once the battery is totally drained it won't get charged even if I try to charge the phone for a number of hours. So what he will do when I get back to him on Monday is he will first try to shock the battery to see if it will be revived (which I hope this is just the case) and then dload some firmwares or softwares to fix the unit.
I hope this ordeal will be solved this following week as it's been so inconvenient on my part and I terribly miss my phone.
One of possibility is that they will open the back cover, pull out the battery and charge it to full, then they put it back and flash the stock firmware. With battery charged they have enough time for flashing and the phone should turn on. If it's Sony Center to do that they will also seal the phone as original to get fully working waterproof.
eclyptos said:
One of possibility is that they will open the back cover, pull out the battery and charge it to full, then they put it back and flash the stock firmware. With battery charged they have enough time for flashing and the phone should turn on. If it's Sony Center to do that they will also seal the phone as original to get fully working waterproof.
Click to expand...
Click to collapse
I really, really, really hope it'd work. For the waterproofing it would be fine to take it to the Sony service centre just to have the full waterproofness back.:good:
Just flash kernal from,any firmware by flash tool,and put your cell phone on charge.,it will charge... The same thing happen to me
Sent from my C6903 using xda app-developers app
shahzaib.khan said:
Just flash kernal from,any firmware by flash tool,and put your cell phone on charge.,it will charge... The same thing happen to me
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Flashmode not working and fastboot too the deviice is HARD BRICKED !!!
Meni30 said:
Flashmode not working and fastboot too the deviice is HARD BRICKED !!!
Click to expand...
Click to collapse
Have you managed to find a way to fix it?
I think my phone is hard bricked becuase its stuck on the Sony logo and my pc wan't detect it and none of the buttons work
SpawnCube said:
Have you managed to find a way to fix it?
I think my phone is hard bricked becuase its stuck on the Sony logo and my pc wan't detect it and none of the buttons work
Click to expand...
Click to collapse
Hey guys, do the devs a favour: NOT EVERY SIMPLE BOOTLOOP IS A BRICKED DEVICE!!!
Just go to recovery and wipe everything, it then should boot without problems.
if it doesn't, first check yourself (e.g. did you flash a 4.4 kitkat without flashing a new kernel for it?)
the answers for nearly all problems are here on xda-developers ... just read, read and read and understand ... if you don't know, what you do with flashing your device, what the partitions data / cache / system are for, what a kernel is or what the differences between stock roms, custom rom releases and nightly builds is, you simply SHOULD NOT flash your device.
If you understand what you are doing and if THAT ALL doesn't help you and you think you have a problem noone else have (i allready had such a thing with my defy+, it got bootloop and it was a dead memory chip) THEN (and just then) post your problem here. The devs simply don't have the time to help everyone who simply can't read the existing threads.
Thanks (and dont get angry on me, just saying so you can do it better the next time)
DJ_Synergy said:
Hey guys, do the devs a favour: NOT EVERY SIMPLE BOOTLOOP IS A BRICKED DEVICE!!!
Just go to recovery and wipe everything, it then should boot without problems.
if it doesn't, first check yourself (e.g. did you flash a 4.4 kitkat without flashing a new kernel for it?)
the answers for nearly all problems are here on xda-developers ... just read, read and read and understand ... if you don't know, what you do with flashing your device, what the partitions data / cache / system are for, what a kernel is or what the differences between stock roms, custom rom releases and nightly builds is, you simply SHOULD NOT flash your device.
If you understand what you are doing and if THAT ALL doesn't help you and you think you have a problem noone else have (i allready had such a thing with my defy+, it got bootloop and it was a dead memory chip) THEN (and just then) post your problem here. The devs simply don't have the time to help everyone who simply can't read the existing threads.
Thanks (and dont get angry on me, just saying so you can do it better the next time)
Click to expand...
Click to collapse
Thanks, you just said what I wanted to say.
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?
What exactly were you doing before this occured?
You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.
SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update
SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!