Hi all,
I downloaded the modaco update-nexusone-FRF50-signed.zip, and flashed my stock 2.1 (out of the box) nexus one rom, it worked well for about 9 hours, i plugged it into my car charger and when i took it off, it froze, and the touch screen disabled. Now im trying to reflash the rom and keep getting stuck at E: Can't mount /dev/block/mmcblk0p1, then E: Can't mount SD card
Any ideas on how i can get this working again?
Thanks
reinsert your sdcard, I have issues where the sdcard doesn't sit properly. This is assuming your using a2sd
i have a few times, same thing keeps happening, is there anything else I can try before I chalk it up to hardware malfunction and send it in to get a new one.... i reaallly dont want to do that
im also tried different sd card, and none of them have worked.
Ted926 said:
i have a few times, same thing keeps happening, is there anything else I can try before I chalk it up to hardware malfunction and send it in to get a new one.... i reaallly dont want to do that
im also tried different sd card, and none of them have worked.
Click to expand...
Click to collapse
Well..... I wouldn't consider it to be a hardware malfunction yet.
1. Have you tried a non-apps2sd rom, like Stock Froyo
2. Have you tried completely reformatting your SD card on your desktop, while using a MicroSD to SD to USB converter or something of that sort. You'll need to delete all the partitions as you won't be able to see the EXT partiton in explorer, use disk manager
3. Have you tried using a different SD card?
4. Maybe you should completely wipe all the device in fastboot, maybe something is screwy, maybe even reinstall your recovery image
Try these things, then come back with results. We can diagnose issues after some of these troubleshooting techniques
i haven't tried formatting the card, but i have tried other cards with the update.zip flash, do you have a link to the stock froyo file
i think the problem is that the one i downloaded wasnt legit, and i have wiped the device in fastboot, the problem is that something is wrong with the touch screen, when it relaods from rebooting, it will get to the touch the android welcome screen and wont register any touch screen input, only volume up/down, trackball, and power button
okay, i tried formatting the sd card, and putting the update.zip file on it, and the same error occurred, when i tried to flash in recovery mode.
any update on what i can do to fix this?
Flash the original recovery image. You can find it http://forum.xda-developers.com/showthread.php?t=614057
You would do this through fastboot. Its easy, try that out
how do you do it through fastboot, i've only flashed through recovery
Ted926 said:
how do you do it through fastboot, i've only flashed through recovery
Click to expand...
Click to collapse
Put the img file on your sdcard, boot into fastboot, it should automatically check for the image and you should get a prompt asking for you to continue installing the image
no luck, it doesnt search for the image. When i enter fastboot, it just shows four options: bootloader, reboot, reboot bootloader, and power down
Ted926 said:
no luck, it doesnt search for the image. When i enter fastboot, it just shows four options: bootloader, reboot, reboot bootloader, and power down
Click to expand...
Click to collapse
Then I would say something is faulting with your SD Card or your SDcard slot. I would try and take a very small ammount of rubbing alcohol and a q-tip to the contacts of your SD card, but there is no way to get into the slot without damaging it. If you have to do a warranty replacement just state that yes your device is bootloader unlocked but you're a developer and it is necessary to unlock in order to better serve the android platform
Related
i have a class 6 adata 8gb 2gb ext4 64mb swap rest fat32
im running cyanogen 4.0.2 or 4.0.4 whichever one i load up from sd at the time, but both are stable. i have newest radio and spl also. the issue is simple. i can get into recovery mode and bootloader menu. everytime i reboot it goes to bootloader menu(3 skateboards). camera button is not held down either or stuck. the only way to get past this screen is to evertime i reboot to factory wipe and install new rom which is a pain. i was wondering if by having the original image DREAIMG file in a folder on my sd is whats causing this. but now that i cant get past this screen i cant remove it from sd. i also already tried mounting sd to comp from console using: "ums_enable" it does nothing(tried it on 3 computers). im tired of reseting and reflashing. pls some assistance.
Have you tried to reflash the SPL? You could just redo the entire root process and replace everything.
New Isuue, Same Problem
Sorry it took so long to get back here. No I haven't tried that. How could it be the SPL? Im asking it in a meaningful way, like why and/or how could it be?
I will reflash the SPL tonight and edit post if it works.
I also erased my sd card and re partioned in in "parted" it booted fine. The battery died today and i rebooted it and BAM! bootloader screen again. So i factory reset and flashed a new ROM image. then it worked fine. now only problem is the private apps i have installed wont work and they get stuck on uninstalling....Whats the fix for that?
Thanks XDA!!
You need to start over and replace everything. It sounds like you have multiple problems. Use THIS guide starting with the downgrade bacause it will reflash EVERYTHING on your phone. If the problem persist then it's hardware issues. Redownload everything, don't use anything you already downloaded because these files might be bad too.
Being stupid and mildly curious, I formatted the system partition and now the phone won't boot passed the model screen, not the galaxy s logo, but the first screen that I would call the manufacture splash screen.
Serves me right for being curious.
Recovery mode is disabled on this phone and cannot use odin since the computer doesn't see the device.
The viable solution is to have it re-flashed at samsung repair center and learn from my mistake, but I was also wondering about the boot process.
In traditional computers, the bios will search for bootable media in the order set in the bios. The question is, does the android boot process do the same? Has anyone tried? I was thinking of making the micro SD bootable with the android system volume on it, hoping that the phone will see the system on the external sd, for which then I can then mount and restore the system on the internal SD.
Is this possible?
you might be able to get the 3buttons working by heating up the phone with a hair dryer trick
remove battery, sim card, and SD card
then heat up the phone, and try to power it up with the 3 button download mode
never heard of such a thing, but what do I have to lose...other than a 560.00 phone.
AllGamer said:
you might be able to get the 3buttons working by heating up the phone with a hair dryer trick
remove battery, sim card, and SD card
then heat up the phone, and try to power it up with the 3 button download mode
Click to expand...
Click to collapse
lol, would you mind explaining a bit how this is even rational?
it's not rational at all, even i was skeptical about it at first
but many have got it to work that way, and that's more than enough proof
even if it's not logical at all
abd reboot recovery
I've had the same issue with an unsuccesfull lagfix.
No 3 button recovery.
I've connected the phone to my computer (I have the android sdk installed) and I ran "abd reboot recovery". The phone rebooted in recovery and i did a factory restore.
It went great.
Try this. Good luck.
that doesn't work if they are bricked already
I bricked my CDMA Hero. I rooted it with the super one click, and installed a early version of froyo, and had some issues with it. I wanted to get it off, so I used CWM recovery, and formatted everything. Now when I turn it on it goes to the HTC opening screen, and stays there for hours until the battery dies. It will charge, but my computer doesn't recognize it, and it will not boot. What can I do?
Bricked means it is a brick and that is it, your phone still turns on so the good news is that it is not bricked.
Need some more info before anyone can help:
1. You reformatted everything using clockwork recovery
2. Did you re-install a new ROM?
3. Did you restore a nandroid backup?
I would recommend booting into recovery and wiping everything (factory reset and dalvik-cache) in recovery, then reinstall froyo - once you are booted and running you can figure out what you want to put on it. At least your phone would work then.
stonemad said:
I bricked my CDMA Hero. I rooted it with the super one click, and installed a early version of froyo, and had some issues with it. I wanted to get it off, so I used CWM recovery, and formatted everything. Now when I turn it on it goes to the HTC opening screen, and stays there for hours until the battery dies. It will charge, but my computer doesn't recognize it, and it will not boot. What can I do?
Click to expand...
Click to collapse
Just what Heaterz16 said...
I'm also pretty sure your phone isn't bricked, as long as you can still get into Recovery, it Most Likely can be Fixed!
I also Recommend trying to Wipe Everything, then Reinstalling a New Rom, Also as a Suggestion... If it were me I'd Probably Choose a Different ROM to install! My Very First ROM I Flashed was a Cyanogen one, and I had Trouble with it Booting Also!!
Try LiquidSense... its Only 2.1, but its Stable, It Boots Fast, and just plain out Fast as Hell!
You can always Switch to Whatever you want... Once you get your phone back to a Working Condition!
Good Luck!
Sent from my HERO200 using XDA App
I cannot get it into recovery now. It will turn on, but it stops at the initial HTC screen, and stays there until the battery dies. When I connect my phone with my computer, the computer recognizes it, but I can't seem to get the 2.1 exe from HTC.com download to the phone. My guess is I wiped the thing clean. Unfortuneately, I didn't back anything up.
I can't even get into recovery, it just sits on the HTC startup screen until the battery dies. It does recognize when I connect it to my computer, but running the 2.1 exe doesn't do anything.
Can you adb into the phone and flash a recovery?
I think that would be a helpful start.
stonemad said:
I can't even get into recovery, it just sits on the HTC startup screen until the battery dies. It does recognize when I connect it to my computer, but running the 2.1 exe doesn't do anything.
Click to expand...
Click to collapse
Pull the battery, hold volume down and power and you should boot into bootloader. I believe it is *home* to get you back into recovery. Then reinstall a new rom and you should be good to go.
kwahomba said:
Pull the battery, hold volume down and power and you should boot into bootloader. I believe it is *home* to get you back into recovery. Then reinstall a new rom and you should be good to go.
Click to expand...
Click to collapse
kwhomba,
he can't get into the recovery.
mtran2988 said:
kwhomba,
he can't get into the recovery.
Click to expand...
Click to collapse
t-y, got it. Yeah, then adb a new recovery image may be the only thing. But he may not even be able to get in then.
Just a matter of waiting right now.
He did say his computer was recognizing his device, so he might be ok.
If he can flash a new recovery, or even just adb.. then he can start rebuilding it.
stonemad:
You'll want to grab a recovery, and try to connect to your phone via ADB when it's on.
Then do adb shell
then : flash_image recover [name of recovery].img
let us know
Ok, I can get to the CWM recovery, there is no backup files, no recovery files, and no files on my sd card. I cannot seem to get an opperating system on. I mounted my phone to my computer and downloaded .zip files, but it still says no files available.
How do I flash a recovery, I can't find any files anywhere.
i have .zip files on my sd card to flash, but when I try to apply them it says no files found.
Ok, I have been working on this all day. Thank you to every body who answered. This is the situation as best as I see it. I can use the power and the down volume buttons to go to recovery mode. I have ClockworkMod 2.5 and can mount my computer to my sd card. It appears that I don't have an opperating system at all, or anything else on the phone. I have downloaded several .zip files and tried to install them, I can mount them, but when I try to apply them it states that there are no update.zip files on the sd card. I have deduced that I need an opperating system for an update to work, but I could be wrong. I am having a hard time finding the right files to use to get my phone to go. It seems salvageable, but I'm not sure how. People have sugested a couple of Mods to instal, but I don't know how to do that with what I have. CWM is asking for a update.zip, or a recovery.zip, but I don't know wich one at which time, or even how to get it to flash. That is what I think I know, but that is subject to change depening on what you all know.(showing just how foolish I really am) Thanks again people for you time and advice, I really do appreciate it.
Don't select "install update.zip", select "install zip from SD card" or whatever the option is called.
I've tried that too, it seems like all the software is gone. HTC, Sprint, Google, and Android. Does anybody have a download they think will work. I'm at the point to try anything.
stonemad said:
I've tried that too, it seems like all the software is gone. HTC, Sprint, Google, and Android. Does anybody have a download they think will work. I'm at the point to try anything.
Click to expand...
Click to collapse
What software are you talking about? Sprint, Google, and Android what, specifically? A download for what?
Mount usb storage in recovery, put rom of your choice on there, and flash?
what about kernals, how do I know that I have everything I need?
ROMs generally have kernels in the zip builds already. From the sounds of it, you're kind of lost at what you're doing.
Do you have a SD card reader? if so, plug in the SD card to your computer and pull over a ROM zip, like Cyanogenmod or whatever is to your liking.
Then in recovery, go to "install zip from sdcard"
go to "Choose zip from sdcard"
then search for the ROM zip you put on the sd card.
State exactly STEP BY STEP, what you are doing. Your phone is perfectly fine, you just dont have a ROM on your phone, which is why you cant boot. You're not missing kernels, or anything, you simply dont have the baseline of a ROM on your phone yet.
Post back
I don't know where or how to find a rom, I have heard good things about cyanogen, but can't seem to find where to download it. Is ClockworkMod a rom, and if so how do I use it. You're right, I got way in over my head, and now I just want my phone back the way I bought it. What is your favorite rom, and can you give me a link. Thanks again everyone.
Hi all,
I was hoping someone would be able to help me out as I am seemingly in a bad situation. I received my Nook 2 days ago and rooted and tried out a few different ROMS to get a feel for the choices. In any case, for some reason my Nook no longer appears to be booting anything from internal memory. Any ROM I have tried (stock included) has failed to boot, but I can get the Nook to load CWR with the memory card in. When I say failed to boot, I mean a black screen. Like no response from the device at all.
Please if anyone can help it would be greatly appreciated, I really dont know what else to do or what the problem is.
Thanks,
Michaelangelo
mad1100 said:
Hi all,
I was hoping someone would be able to help me out as I am seemingly in a bad situation. I received my Nook 2 days ago and rooted and tried out a few different ROMS to get a feel for the choices. In any case, for some reason my Nook no longer appears to be booting anything from internal memory. Any ROM I have tried (stock included) has failed to boot, but I can get the Nook to load CWR with the memory card in. When I say failed to boot, I mean a black screen. Like no response from the device at all.
Please if anyone can help it would be greatly appreciated, I really dont know what else to do or what the problem is.
Thanks,
Michaelangelo
Click to expand...
Click to collapse
Get the nook restore to stock zip and the boot restore zip. Flash those both back to it. Also, make sure you are wiping, System, then Data, then Boot beforehand. And wipe both Dalvik and cache. Nook Color is nearly impossible to hard-brick (in the sense of being unable to recover from it).
mad1100 said:
Hi all,
I was hoping someone would be able to help me out as I am seemingly in a bad situation. I received my Nook 2 days ago and rooted and tried out a few different ROMS to get a feel for the choices. In any case, for some reason my Nook no longer appears to be booting anything from internal memory. Any ROM I have tried (stock included) has failed to boot, but I can get the Nook to load CWR with the memory card in. When I say failed to boot, I mean a black screen. Like no response from the device at all.
Please if anyone can help it would be greatly appreciated, I really dont know what else to do or what the problem is.
Thanks,
Michaelangelo
Click to expand...
Click to collapse
This happens because the boot partition is corrupt. This is usually the result of you formatting the SD card with CM7. Due to a bug, when you try to format the SD card, it will wipe out the boot partion as well. Just restore the boot partion and you will be OK.
neozen21 said:
This happens because the boot partition is corrupt. This is usually the result of you formatting the SD card with CM7. Due to a bug, when you try to format the SD card, it will wipe out the boot partion as well. Just restore the boot partion and you will be OK.
Click to expand...
Click to collapse
Is there a way to do that when the screen is not working?
An automated install or do we just push buttons as per the same task on another nook and hope
Okay, so I understand that the problem is that CM7 changed around the boot partition files, that makes sense as that was the last thing I could get running on internal memory. When I was flashing HC v4 to EMMC I also flashed a boot repair, and that still did not work. I cannot seem to find a boot repair file for stock, where do I get that.
Sorry for the noob questions, and I am definitely trying to use search the forums for answers before i ask these questions!
We have life!!! I found a stock boot restore file and it turned out to work, I am back to stock again. Man this is sure a learning experience. I have been flashing my Evo for a while now, but the nook is a different beast all together.
Thanks for your help all, I think I am good from here on out!
chrysilis said:
Is there a way to do that when the screen is not working?
An automated install or do we just push buttons as per the same task on another nook and hope
Click to expand...
Click to collapse
You get a microSD card with CWR and the both .zip files for the stock 1.1 and the boot partion, then pick install .zip from SD card and flash both files. When done, take out the microSD card and your NC should be able to boot normally...
neozen21 said:
You get a microSD card with CWR and the both .zip files for the stock 1.1 and the boot partion, then pick install .zip from SD card and flash both files. When done, take out the microSD card and your NC should be able to boot normally...
Click to expand...
Click to collapse
And if the screen isn't turning on but SD cards seem to boot?
chrysilis said:
Is there a way to do that when the screen is not working?
Click to expand...
Click to collapse
The solution I am trying now is to leave it for a few days so tonight/tomorrow we'll see if it comes back!
chrysilis said:
And if the screen isn't turning on but SD cards seem to boot?
The solution I am trying now is to leave it for a few days so tonight/tomorrow we'll see if it comes back!
Click to expand...
Click to collapse
How do you know it's booting into CWR on the SD if the screen is not working?
If your screen is not working when booting from a SD card, then.. maybe there is something wrong with your nook???
neozen21 said:
How do you know it's booting into CWR on the SD if the screen is not working?
If your screen is not working when booting from a SD card, then.. maybe there is something wrong with your nook???
Click to expand...
Click to collapse
If I boot nooter 0.2 then the USB plug goes green which apparently indicates booting. Oh and OMAP3630 shows up for a second on booting too.
Thing is I didn't do anything to break the screen and there is no physical damage to the unit. so it's just weird
chrysilis said:
If I boot nooter 0.2 then the USB plug goes green which apparently indicates booting. Oh and OMAP3630 shows up for a second on booting too.
Thing is I didn't do anything to break the screen and there is no physical damage to the unit. so it's just weird
Click to expand...
Click to collapse
I thought I had the same issue because of the screen being blank. That said it is highly unlikely your hardware ( ie screen ) is bad. I was able to get mine working correctly last night doing what is mentioned above. However to get it to work right booting into CWR via a bootable sdcard I had to make a new bootable sdcard from the one I had. Not sure if something was corrupted on the card I was trying to use or what. But as soon as I made a new bootable sdcard and put it in the device and powered on it boot right up to CWR off the sdcard like I needed so I could fix it. So my suggestion if you can is take a totally different sdard fro the one you have been using and make a new bootable sdcard and give it a shot.
BTW with no card in the device hold the power key down for about 20 secs to make sure it is fully powered off. Even tho your screen is blank does NOT mean it is fully powered off as I learned real fast last night when I tried working on mine. I thought it was off from the night before but it must not have been because I put a bootable HC sdcard in it and when I plugged it in I got a msg saying battery to low to power on plz try again in 15 mins. About 10 mins later I came back and it was finally powering itself on and booting into HC off the sdcard. So I let it fully charge and then start playing with it to finally get it back up and running again.
Well it finally died. I got the infamous SD card failure message. For the past few days It was getting slower and slower and I was getting odd Force Closes everywhere. Then the red exclamation mark and a message about the SD card.
The very weird thing is that the failure was about the EXTERNAL SD card. Cannot find mount point... cannot read... Not the ususal INTERNAL SD card message.
Sure enough, if I try to read the Transcend 16Gb MicroSD on my pc or laptop, it appears completely fried. (Cr*p, that's were my backup was!).
But the phone wont boot on wihout the external card! Why? All I can get to is the Download mode. No boot and no recovery.
I'm in Montreal so it appears easy to get it fixed... but should I try flashing it first?
davidke said:
Well it finally died. I got the infamous SD card failure message. For the past few days It was getting slower and slower and I was getting odd Force Closes everywhere. Then the red exclamation mark and a message about the SD card.
The very weird thing is that the failure was about the EXTERNAL SD card. Cannot find mount point... cannot read... Not the ususal INTERNAL SD card message.
Sure enough, if I try to read the Transcend 16Gb MicroSD on my pc or laptop, it appears completely fried. (Cr*p, that's were my backup was!).
But the phone wont boot on wihout the external card! Why? All I can get to is the Download mode. No boot and no recovery.
I'm in Montreal so it appears easy to get it fixed... but should I try flashing it first?
Click to expand...
Click to collapse
Sound you have some data corruption (or suffering the Bell BUG http://forum.xda-developers.com/showthread.php?t=883820)
First try to retreive the data from your external Sdcard with your PC, using the tool "testdisk 6.11". Maybe you'll be lucky enough to retreive all your data with it (repairing your FAT).
If the repair is a succes, then backup the data on your PC and do a low format of the ext sdcard to start clean.
When it's done, try to clean everything on your phone (if you can boot it in recovery), clean the Dalvik, clean the cache, do a factory reset, disable all extra tweaks (if you use a custome kernel already: lagfix etc).
If all process is ok, now you ready to flash a stock and clean rom with the usual tools (no external or sim card in it during the flash and first boot).
Report back when it's done.
GL.
TestDisk is now hard at work. Thanks for that. There's hope for the data!
Phone wont go into recovery. I had 3BR but it's not working now.
Download mode is all I have. I could theoretically try reflashing with ODIN. Repartitioning might not be a bad option considering the state the phone is in. Should I try?
davidke said:
TestDisk is now hard at work. Thanks for that. There's hope for the data!
Phone wont go into recovery. I had 3BR but it's not working now.
Download mode is all I have. I could theoretically try reflashing with ODIN. Repartitioning might not be a bad option considering the state the phone is in. Should I try?
Click to expand...
Click to collapse
Yes you can try that, but be sure to flash a stock rom first (go for a 2.1).
GL .
All data recovered thanks to TestDisk!!!
As for the phone...
It flashes with Odin no problem. (used JH2, which is what I had on there anyway)
But still wont boot. The problem appears to be in the boot partition.
Should I try "Phone Bootloader Update"? (I'm a bit afraid of that because I might lose my 3BR fix)
What does "Phone EFS Clear" do?
Additional symtom: Cant recharge it either (no problem I have external charger so I can always have a full batt for this process). It starts to display the battery charge graphic and then just boot cycles.
davidke said:
All data recovered thanks to TestDisk!!!
As for the phone...
It flashes with Odin no problem. (used JH2, which is what I had on there anyway)
But still wont boot. The problem appears to be in the boot partition.
Should I try "Phone Bootloader Update"? (I'm a bit afraid of that because I might lose my 3BR fix)
What does "Phone EFS Clear" do?
Additional symtom: Cant recharge it either (no problem I have external charger so I can always have a full batt for this process). It starts to display the battery charge graphic and then just boot cycles.
Click to expand...
Click to collapse
Good news for your data!
No doubt if you do a bootloader update with a stock one, you'll lose the 3BCombo (or maybe flash a stock bootloader with the 3BC enabled, not sure if it exist btw??). Try to reflash the 3BC fix only first and see how it work.
Anything that involve EFS is a: DO NOT TOUCH IT =), hope you did a backup of it btw (your EMEI is stored in that folder: No EMEI = No network).
Waiting your feedback.
ttf said:
No doubt if you do a bootloader update with a stock one, you'll lose the 3BCombo (or maybe flash a stock bootloader with the 3BC enabled, not sure if it exist btw??). Try to reflash the 3BC fix only first and see how it work.
Waiting your feedback.
Click to expand...
Click to collapse
Tried a couple of things...
A) Updated bootloader with 3BR fix only: No change, Galaxy-S logo then Off.
B) Flashed JL2 (bootloader not checked): Slight change, now it boot cycles.
C) Flashed JL2 + bootloader: Slight change, now it just hangs and the Galaxy-S logo (waited 60 minutes, phone was getting pretty hot so I stopped it).
At all steps I can get back to Download mode but not recovery.
At this point I assume it's hopeless?
davidke said:
Tried a couple of things...
A) Updated bootloader with 3BR fix only: No change, Galaxy-S logo then Off.
B) Flashed JL2 (bootloader not checked): Slight change, now it boot cycles.
C) Flashed JL2 + bootloader: Slight change, now it just hangs and the Galaxy-S logo (waited 60 minutes, phone was getting pretty hot so I stopped it).
At all steps I can get back to Download mode but not recovery.
At this point I assume it's hopeless?
Click to expand...
Click to collapse
Not sure but really sound like a defect internal SD/or more.
Last hope?: repartition + pit 512 + bootloader and Stock 2.1
That killed it for good. Now it's a paperweight!
No nothing. It's like the on#off button was unplugged!
Oh well. It's really nice to have gotten back the data.
davidke said:
That killed it for good. Now it's a paperweight!
No nothing. It's like the on#off button was unplugged!
Oh well. It's really nice to have gotten back the data.
Click to expand...
Click to collapse
Well that's a bad news, maybe pulling out the battery during one or two hours will help to revive it.
Otherwise if it's really the internal sd issue you might check that thread about internal SD bug (if not done yet) http://forum.xda-developers.com/showthread.php?t=902724 and RMA it.
Don't worry they'll change it with a brand new one. Ring samsung directly if you can.
No worries. I am five minutes away from the service center. Mobo replaced for tomorrow morning they said.
Had I come in before 3PM they left we with the impression they would have changed it while I wait!
Having followed all these threads, I was well aware of the issue long before it actually happened to me. The only thing that surprised me was that it broke the fat table on my external SD.
I was holding back because of the instabilities; with a better unit in hand I'll pop in a fancy rom.
External SD card causes reboot loop
I think I have a similar problem as yours. Just yesterday when I did a restart on my SGS, it suddenly went haywire. The boot loop was continuing for almost 30 mins until it suddenly became stable and reboot as normal.
However, something didn't work out right. I can't view all my pics and videos from gallery, and even my mp3s are not detected inside the music player.
But the very same files are still readable from My Files when I manually dig into these folders.
Same thing happened again just now when I was on my way to work in the subway. I finally had the sense to remove my external sd card and voila, my phone reboots smoothly without a hiccup.
So the question here is, is it that my external sd card is failing or is it that the phone's external sd card reader is failing.
Could anyone with the similar problem share with me their findings?