Related
Hello. I have a ATT S4. I rooted and flashed this custom rom, http://forum.xda-developers.com/showthread.php?t=2356276. It was working fine no problems for a few months. Today I thought I wanted to try 4.3 and Paranoid Android and flashed the ParanoidAndroid 3.99-RC2 rom from this thread, http://forum.xda-developers.com/showthread.php?t=2314559. My recovery is TWRP. When flashing the new ROM I did get a warning of "no file_contexts". After this my phone has refused to boot. It will turn on, load the Samsung S4 screen, and then stay stuck with this image and never start up. I can still enter recovery. I have tried flashing my original rom which worked perfectly fine before and it acts the same way. I tried to recover a backup I made in TWRP but it fails every time. I have searched in the forums and a common suggestion for bootlooping is to reflash a stock image in ODIN, but most of these people were unable to enter recovery. I would like to get the photos I have on my phone off if at all possible, however it is not a big deal. Anyone know what the issue might be so I don't have to resort to trying ODIN.
It's sounds like you got a bad download of the pa rom. In the future always check the md5 of the files you down load.
If you wiped system, data, dalvik, cache, and android secure prior to flashing your nandroid and it's still not working you're going to have to use odin.
Thanks for replying. I restored it to stock and although it was frozen at the same spot at first, it booted up properly after waiting a bit and a reset from the stock recovery. I would say I'd be more careful next time, but I still don't really know what went wrong.
goldynchyld said:
Thanks for replying. I restored it to stock and although it was frozen at the same spot at first, it booted up properly after waiting a bit and a reset from the stock recovery. I would say I'd be more careful next time, but I still don't really know what went wrong.
Click to expand...
Click to collapse
Having to do a factory reset after Odin to get it past the boot loop is normal. I'm guessing it was a bad download that got you in the problem in the first place. It occurs more frequently than you'd think. That's why it's always good to check the md5 of the file you downloaded
I was suprised since i've flashed countless roms since my s2 and have never checked a single md5. Now I've found out how to check the md5 check sum of what I have downloaded, but for future reference how do I know the reference checksum to verify they are the same? I know it may be a stupid question, but I honestly feel like I am missing something.
goldynchyld said:
I was suprised since i've flashed countless roms since my s2 and have never checked a single md5. Now I've found out how to check the md5 check sum of what I have downloaded, but for future reference how do I know the reference checksum to verify they are the same? I know it may be a stupid question, but I honestly feel like I am missing something.
Click to expand...
Click to collapse
When you download the rom there should be the md5 there. I usually just check the last 5 characters, that's as good as my memory is lol. If they're the same it's highly unlikely the others won't check too.
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
I'm currently running @Danvdh / @ktoonsez Google Play Edition on my S4 (I9505 jfltexx) .. and have been for a while. Since they've just released a new CM based rom I was going to give it a shot. So, first things first I went to reboot into recovery to do a backup of my current ROM.
However, instead of recovery mode I end up in download mode. Figuring I'd pressed the wrong option on the advanced reboot menu I rebooted and tried again. Ended up in DL mode again. It doesn't matter what method I used to try and get to recovery I can't... it constantly goes to DL mode. I used to be able to get to revocery without a problem (TWRP).
My question is, is this a common occurance and would reflashing TWRP (using Nandroid Manager - the way I did it originally) fix my problem.. or is there a more fundamental issue at play here. For what it's worth Nandroid Manager detects that i'm running TWRP 2.7.0.1 already
Just try to reflash it with Odin.
Or you could try entering it from the terminal:
su
reboot recovery
Lennyz1988 said:
Just try to reflash it with Odin.
Click to expand...
Click to collapse
I would but I'm concerned there may be an underlying issue that would potentially brick my device if i tried a reflash. How can it be that it suddenly won't reboot into recovery anymore when previously it did ?
update:
I've just tried your sugestion via terminal emu which has the same result unfortunately. However, I noticed that after entering the su command it returns [email protected] in the command prompt. I would have expected this to be [email protected]jfltexx right? I'm assuming now that flashnig the Google Edition ROM has changed what my device is reporting itself as ? (forgive me me if I'm talking bollocks at this point.. I'm just guessing)
So, now if I flash the twrp that already have (for jfltexx) will this cause a problem ?
If I had to guess, and I'm just shooting in the dark here, but this sounds like an error in the ROM. And I'd bet that changing the rom solves the problem.
What happens if you try to reboot into Download mode? Does it go to Download mode? The only time I've experiences this, download and recovery were reveresed in the ROM I was using. So trying to boot to 1 always gave me the other. So I'd try to reboot into Download mode and see if that puts you in recovery.
If all else fails, use Odin to return to stock. It will not brick your phone because of this.
davey.lad said:
I've just tried your sugestion via terminal emu which has the same result unfortunately. However, I noticed that after entering the su command it returns [email protected] in the command prompt. I would have expected this to be ro[email protected]jfltexx right? I'm assuming now that flashnig the Google Edition ROM has changed what my device is reporting itself as ? (forgive me me if I'm talking bollocks at this point.. I'm just guessing)
So, now if I flash the twrp that already have (for jfltexx) will this cause a problem ?
Click to expand...
Click to collapse
Sounds to me like you are already running a jftexx recovery with a jgedlte ROM. That probably is the source of the problem - Since the rom replaces the entire system, it also replaces the basic stats the device has about itself. If the Google Play edition is different in hardware, I would suspect it would also damage the kernel function (for example by asking an amount of ram the phone does not have).
I would just install a jftexx rom. These things are pretty sensitive when it comes to versions.
NetaA said:
Sounds to me like you are already running a jftexx recovery with a jgedlte ROM. That probably is the source of the problem - Since the rom replaces the entire system, it also replaces the basic stats the device has about itself. If the Google Play edition is different in hardware, I would suspect it would also damage the kernel function (for example by asking an amount of ram the phone does not have).
I would just install a jftexx rom. These things are pretty sensitive when it comes to versions.
Click to expand...
Click to collapse
The google version is the same hardware. Its the same device with a different rom installed. The google rom is totally interchangeable with other s4s. All it is is an aosp rom.
This is not his problem.
Sent from your phone. You should be more careful where you leave that thing.
Skipjacks said:
The google version is the same hardware. Its the same device with a different rom installed. The google rom is totally interchangeable with other s4s. All it is is an aosp rom.
This is not his problem.
Sent from your phone. You should be more careful where you leave that thing.
Click to expand...
Click to collapse
Alright, thanks for the info.
Since I'm not really familiar with the process of getting into recovery mode, the help I can offer is limited.
Good luck
Thanks for the updates guys.. sorry about the delayed reply - been on holiday.
In the end I just used Nandroid Manager to reflash the original twrp.img that I had.
Sorted. Guess I was worried about nothing.
cheers :good:
Hey guys,
I searched the web already but I can't find a solution. My S5 won't turn bluetooth on anymore. It's rooted but after rootprocess, BT worked fine. I can't remember that I've done something around BT. I've deleted Data and Cache already and rebooted the phone afterwards but still no Bluetooth. I opened Quick Connect and a Toast appeared which said "Bluetooth activated" but there wasn't the logo in the status bar and the icon in the notification center was also grey. Hope that you can help me.
Pozdrav
Croatia1
Any solutions?
Hey mate..
Any solution yet..?
Mine wont turn on still.
Galaxy S5 LTE
Reinstall ROM
Maybe the cause of the problem is that you downloaded an invalid root and it did something to the bluetooth. I highly recommend reflashing a stock rom. See if anything changes. Thank you :victory:
la2o said:
Maybe the cause of the problem is that you downloaded an invalid root and it did something to the bluetooth. I highly recommend reflashing a stock rom. See if anything changes. Thank you :victory:
Click to expand...
Click to collapse
This can't be the reason, becausw after I rooted it, BT worked fine.
Pozdrav
Croatia1
Yes.. Mine worked for a while as well and then it dsnt now....
I have the stock rom.
Galaxy S5 LTE
For the gentleman with the stock rom - you can try rebooting into service mode (holding home+volume up and then pressing power) and wipe your cache there - and then try to switch on bluetooth. If that does not work - warranty claim.
As for the rooted phone - you cannot be sure how stable the implementation of bluetooth drivers etc on that rom is. It could have worked at first and later - due to any number of reasons - could stop. I'd really suggest flashing a stock rom and checking - that way you'll be sure the hardware is ok. If not ok - warranty claim.
rnrnrn said:
For the gentleman with the stock rom - you can try rebooting into service mode (holding home+volume up and then pressing power) and wipe your cache there - and then try to switch on bluetooth. If that does not work - warranty claim.
As for the rooted phone - you cannot be sure how stable the implementation of bluetooth drivers etc on that rom is. It could have worked at first and later - due to any number of reasons - could stop. I'd really suggest flashing a stock rom and checking - that way you'll be sure the hardware is ok. If not ok - warranty claim.
Click to expand...
Click to collapse
First, thanks for the tip, sadly it didn't work.
Second, I'm already on Stock Samsung Rom, it's only rooted, I didn't even flashed a custom recovery.
Pozdrav
Croatia1
Hold on, I remember that I've done something around BusyBox with the app from Steven Stericson. Could Busybox brake my bluetooth?
croatia1 said:
Hold on, I remember that I've done something around BusyBox with the app from Steven Stericson. Could Busybox brake my bluetooth?
Click to expand...
Click to collapse
Yes, it could although that wouldn't be a normal result. But yes, it's possible. Depends on what you did with the Busybox configuration.
.
fffft said:
Yes, it could although that wouldn't be a normal result. But yes, it's possible. Depends on what you did with the Busybox configuration.
.
Click to expand...
Click to collapse
Just installed the 1.22.1 version of Busybox with the pro app that's all. Maybe it killed some symlinks.
Well if you practice safe mods.. you'll have made a backup before installing Busybox. So temporarily restore your backup and see if the issue resolves?
If you don't make backups, then you have a lot more work as you have to look for a pattern and /or guess at the cause.
.
I usually always make Nandroid Backups but in this case not. I'm afraid that Busybox will kill my S5 if I deinstall it. What if I flash a Stock Custom rom via CWM? Of course with a full wipe
I doubt Busybox is the cause, but I cannot rule it out. Only because it was a recent change does it move up the suspect list.
Still way too many variables in my mind. I'd probably start by installing a 100% stock firmware temporarily, just for troubleshooting. Confirm that bluetooth works i.e. not a stock issue or hardware failure. Then install your core apps one by one.. see if you can narrow down the conflict fairly rapidly.
But that is hardly the only way to go about it. As you like.. you have to start somewhere and either cull a lot of possibilities or wait for a pattern to emerge. Search the forum too, just in case it's some issue affecting a larger number of people - which might offer more clues.
Good luck.
.
fffft said:
I doubt Busybox is the cause, but I cannot rule it out. Only because it was a recent change does it move up the suspect list.
Still way too many variables in my mind. I'd probably start by installing a 100% stock firmware temporarily, just for troubleshooting. Confirm that bluetooth works i.e. not a stock issue or hardware failure. Then install your core apps one by one.. see if you can narrow down the conflict fairly rapidly.
But that is hardly the only way to go about it. As you like.. you have to start somewhere and either cull a lot of possibilities or wait for a pattern to emerge. Search the forum too, just in case it's some issue affecting a larger number of people - which might offer more clues.
Good luck.
.
Click to expand...
Click to collapse
Thanks mate, I'll post if I have success.
Pozdrav
Croatia1
Good news!
Before I flashed a new firmware with Odin I decided to flash a Custom Rom. Flashed new bootloader + modem and performed a "Wipe for new Rom" in Philz CWM, flashed the rom, set up my apps and settings and, BT works again. Thanks for your help
Pozdrav
Croatia1
Great to hear that so it was just a bit of software acting up - good to know
Please do change the title of your thread to solved
I need help, my phone went into a Bootloop. I have tried to flash the factory image (7.0 and 6.0.1) using NRT and manually and still does not pass the Google logo. It does not let me enter the recovery, it only restarts continuously. When flashing the factory image did not give me any error, even the computer detects it in fastboot mode.
All this happened when I was about to open an application and suddenly I shut down and began to restart continuously. I had using android 7.0 stock.
Exact thing happened to me and I flashed both 7 and 6.0.1 and wiped data and caches multiple times.. nothing seems to work.. any ideas?
Tried everything but still bootloops.
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Seanmiz said:
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Click to expand...
Click to collapse
Your Nexus 6P uses Samsung eMMC doesn't?
I've seen countless threads here and on reddit about this.
My phone hard bricked last week and I suspect the Samsung emmc is to blame, too many people are having the exact same issue without a solution in sight. I am absolutely unable to access the recovery or anything on the emmc for that matter.
See if you're still covered under warranty (mine was 5 days past its warranty, and Google refused to help), otherwise you're SOL. I think we need to make some noise about it and have AP or another site pick up on this.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
I believe it was Samsung, yes. I RMA'd it right away after exhausting all flashing efforts.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Rafsxd said:
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Click to expand...
Click to collapse
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
brichardson1991 said:
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
Click to expand...
Click to collapse
You can find this information on the Bootloader screen listed under eMMC about halfway down the list.
Same problem, samsung memory here
Same for me too,i send my phone back to amazon
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
seco2004 said:
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
Click to expand...
Click to collapse
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Seanmiz said:
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Click to expand...
Click to collapse
When this first started for me I was on the latest beta build, October security patch.
Same issue here - 64MB Samsung memory.
Google support are aware of the issue, they sent out a replacement no questions asked. For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Regardless, I'm in a position where I can access fastboot, but nothing else. Can anyone think of any data recovery options at this point?
---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------
To follow up on my previous post - just before I hit a reboot that threw me into the bootloop, I encountered a hard freeze. I received a bug report after the hard freeze and this is now sitting in my gmail drafts. Would this bug report have any pertinent information here?
thisisgil said:
For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Click to expand...
Click to collapse
I know exactly why it's relevant!
He's trying to make sure it's not a shoddy power button. My Galaxy SII back in the day had a common power button failure where it would think that you are just constantly hitting/holding the power button if you even breathed on it. My phone would bootloop or suddenly reboot constantly because it was getting power button commands from the poor quality button. Better quality buttons along with other methods of locking/unlocking the phone to reduce power presses have mostly prevented this sort of thing these days.