Database Users

Regular (Forced) Reboots After Unlock/Root?

Anyone out there having the same experience as me?
After unlocking and rooting my N1 I now get frequent, if not regular, soft reboots. It seems that it only when reading or writing a lot of data to or from the SD card (e.g. search the SD card for applications, a full data or app backup to the SD card, reading a large playlist off the SD card etc). It seems to be easy to reproduce and certainly didn't happen before unlocking/rooting.
Part way though an operation the screen will go dark and the phone will reboot from the static Nexus logo.
Am using himem. Allocation problems?
Any thoughts?

Wipe , format sd card. Start over with latest stable ROM.

Thanks, I'll try that.
Is this advice offered because it's a known problem or because it's just the default advice for random problems?

Ive never had any random reboots on mine (running cyan latest right now) I did with some roms on my G1, what rom are you using?

Stock...
10

[Q] Nook freezes After boot if sd card is inserted?

I am running cm7 nightlies 120 and Dals 6/30 kernel, but I've had this problem for a while now with previous nightlies. Everytime I boot up my nook I have to remove memory card or else it will freeze after boot. Any ideas?

Yes. You're card has something hosed on it, and for whatever reason the NC is trying to boot from it (when it should not). I had this happen to my first mircoSD, and I wonder if it wasn't something to do with reimaging it several times to flash various nightlys/updates/whatever. I never bothered to track it down as I upgraded to a higher capacity card.

OK. I thought it was something with the card. I will try to reformat it and start from scratch. Thnx for your help.

I am having a similar problem, my nook freezes on startup and shows a little SD card icon that looks like it is exploding then it changes to a exclamation point. It will also do this even after I remove the SD card and try to boot it.
It will eventually boot up and function if I keep restarting it.
Running cm 7.1.0-rc1-encore
Anyone experience this before?

Clean format your SD-Cards or try changing them.

gurs2323 said:
I am running cm7 nightlies 120 and Dals 6/30 kernel, but I've had this problem for a while now with previous nightlies. Everytime I boot up my nook I have to remove memory card or else it will freeze after boot. Any ideas?
Click to expand...
Click to collapse
Next time, do indicate you boot off uSD card itself or from eMMC.
Assuming you did boot from eMMC, then remove your uSD, reformat it (FAT32)

siddhantfriends said:
Clean format your SD-Cards or try changing them.
Click to expand...
Click to collapse
I have tried formatting the card, this happens even if there is no SD card inserted. I wonder if it is something I have installed that is causing this issue.

w0nker said:
I have tried formatting the card, this happens even if there is no SD card inserted. I wonder if it is something I have installed that is causing this issue.
Click to expand...
Click to collapse
Re-format your eMMC partition

votinh said:
Re-format your eMMC partition
Click to expand...
Click to collapse
Alright, I think I completed this, I booted up with the clockwork mod and went to /format emmc....is that what you were talking about?
Anyway, the issue still exists, any other ideas? I appreciate your help so far.

Try that first, if still don't work then re-install OS, do a clean installation.

So I think Beautiful Widgets was causing the freezing, I uninstalled it and now when it boots, the little SD card symbol shows up for a few seconds and it does not freeze.
So who knows lol...anyway, thanks for the help

Good
w0nker said:
So I think Beautiful Widgets was causing the freezing, I uninstalled it and now when it boots, the little SD card symbol shows up for a few seconds and it does not freeze.
So who knows lol...anyway, thanks for the help
Click to expand...
Click to collapse
Sorry I was out of station, so couldn't reply. and good u figured it out

I thought I was going nuts...god damn beautiful widgets!

I too have the same problem for past 3 days. my phone freeze after loading icons of the apps from the memory card
I tried formating the card twice, uninstalled the recent apps , but it didnt help
Without card the phone doesnt freeze, the few minutes after the card is inserted the app icons load and freezes my phone n i have to pull out battery again
I dont want to go through process of reinstalling all apps again .. could someone please help how to find which particular app freezes , if u have already met with dis type of prob
thanks in advance

[Q] Help pls: Nook booted from SD w/CM7 good 4 3 days then started to boot to stock

Ok, I've been reading the forum until my eyes are popping out. I can not find my situation. So please forgive but I've been searching.
Bought a NC for my daughter for the purpose of Rooting it using the SD method. I followed the routine install last Monday:
1. Using WinImage, I burned the Size-agnostic SD Card image on the SDcard (Transcend 8GB Class 6 SDHC) using my HTC Incredible as my card reader.
2. Downloaded cm_encore_full-131.zip and moved it to the card.
3. Installed the SD card and bam! Everything was working and I was happy as hell!
4. I went through the process and got gapps-gb-20110307-signed.zip installed and I was working away downloading apps and stuff.
5. Downloaded update-CM7-dalingrin-OC-sd-063011.zip and got that loaded and our NC was flying high. And since we have the right kernel, downloaded Nook Tweaks and we can use a case with a USB keyboard with no issues playing Angrybirds and everything. LOVING IT!
I was happy as hell cause I wanted to be done in my limited time before tomorrow because my daughter is staying with my mom and this will give her something to do.
THEN today after powering it off. I powered it back on again and the following happened:
1. It appears to attempt boot from the SD card.
2. The green Cyannogen logo comes up and under it it says "loading..."
3. However, instead of the Android on the surfboard coming up like before, it will boot up to the stock Android with the N splash screen first then to the stock interface???
I tried several times powering it on and off to see if it was just a glitch but it still did it. Soooo, I redid the whole process again. But once I tried to boot from the SD card with CM7 loaded, the same thing happens. Green logo, loading..., then back to the NC stock OS.
I tried downloading the image a few times to make sure it wasn't corrupt and reburned the img on the SD card, tried booting it again and still the same results. (I did this whole process at least 5 times!)
Sorry for the long read but I am frustrated and disappointed that i will have to tell my girl that it's not working like it was earlier. Can someone give me any advice to try? Or what can I possibly doing wrong? I'm beyond my skill sets at this point. The only thing that I can find on the forum is that it maybe the Transcend SD card but it worked find for three days. Can it really suck that bad after 3 days? I only have tomorrow to work it during the day so If I have to I'll go to Costco and get a Scandisk over there as some have mentioned, I will. But if there is something someone can tell me to try, please let me know.
Thanks in advance!

You are probably on the right track with getting a new SD card. One of two things happened: the SD card failed during the initial "burn-in" period or the Nook's reader slot did. The card is thebmore likely point of failure.
If the problem persists with a new card, get your Nook back to B&N for warranty replacement. Just don't let them have your SD cards an you won't lose all your work
P.S. Yes, ANYthing electronic can "suck that bad after just 3 days". If an electronic component is going to fail, it will either be DOA (and even cursory quality control will catch it) or it will fail shortly after being placed in regular service (burn-in). If it survives the first 60 to 100 hours of use, it will PROBABLY last for years.

Thanks DiDGR8!
I hear you on the electronic part. I was also really tired when I posted. I guess I just didn't want to believe that the card was the issue or rather could be the issue specially when I can read the card from my phone and read it from the NC in the stock interface. It had to be something I did or forgot to do. But I've seen stranger things happen. LOL Things can break.
As soon as I can, I will run out and get a new (Scandisk) card and I hope that it resolves the issue. I hope it is not the NC's reader slot because I hate going through the "returning process" plus we have to leave tonight.
I'll post my results as soon as I can today.

I often not to believe the uSD card itself is the problem but I guess this time, I believe it.
I have the same card as yours (Transcend 8GB class 6), testing random read/write small block and the result were about 0.08 (meaning bad). Sure enough, running CM7 off it last few days then I got ton of FC errors. I now then boot CM7 from eMMC and use the card as an external storage, the card still gives me some problems.
Try Sandisk and keep yours fingers crossed.

Well at least I'm not alone. Thanks votinh!
I wanted to avoid running it from eMMC so that if i wanted to I can do the warranty thing.
Well, I got me a Scandisk 4Gb Class 4 this morning in addition to a card reader/writer to eliminate my phone as a card reader.
Followed the steps and still the same thing. However, I did noticed this time some I/O errors come up during the installation process.
So, I let it go to stock so i can test my phoness SD card (Scandisk 2GB) and it worked just fine. So, I'm really stumped now.
I'm going to try flashing it again a couple of more times. I can go to B&N and tell them it is not working but if i show them it does work reading my phone's SD card. unless i just push them for an exchange.

OK, tried the the latest stable and now the Driod comes up and it is in a loop. I abandoned that all together. Need to stay focused.
So, I went through the process again using #133 on my Scandisk 4GB and tried to boot with it. Same results again Green logo, loading..., then back to the NC stock OS.
However, this time I was able to take a pic of the screen so I can copy what I saw when I saw I/O errors during the installation. So at one point I got:
end_request: I/O error, dev mmcblkl, sector, <insert number>: this flashed down the screen quite a bit
also
JB2: DetectedIO errors while flushing file data on mmcblk1p2-8
Ok so I went back to the Transcend card and did #132 but using my new reader. This time it seem to install clean. When I powered it back up, this time str8 to the "Read Forever" splash screen and back to stock. Weird.
So, I redid the 4GB card again and got the I/O errors again same thing the "Read Forever" splash screen and agian back to stock. It's like it's telling me to go F*** myself.
At this point, I'm thinking its the NC reader reading off the card itself. I tried 2 brand new cards, dif brand, dif reader/writers, multiple downloads of the img and installers...I don't know what to say. I should just root it to eMMC but if i'm having trouble with the SD method and I go eMMC and that messes up I won't be able to return it on Warrenty. What am I doing wrong? Can anyone give me anything else, I'm desperate and ready to fling it out the window. LOL

LOL I love the way I'm bumping my own thread here.
So, I went to B&N and got me a new replacement NC without any hassles.
I ran through the routine from scratch with CM7 #133 (which I believe has the OC kernel in it) on my new Scandisk 4GB Class 4 without the gapps.zip just to take it one step at a time.
I powered it on and prayed to the CM7 gods. I see the same I/O errors on the install and I also saw chown: cannot access '/tmp/backuptool.sh' : No such file or directory which I've seen before as well. However, this time the droid came up refreshing itself in a continuous loop. Like when I tried the stable version earlier. I did this twice and the same results.
At this point I'm thinking it maybe the WinImage. I'm using Winimage V 8.50? So, I downloaded Win32disk imager to give it a try and using my phone as the reader again because that was the last known combo. Again, the same errors. Then the Logo, loading…, this time blank screen…crickets…
I’m out of ideas…I had a clean install once on Monday worked fine until yesterday and I can’t do a damn thing.
Different SD cards, 2 brand new NCs, different readers, multiple downloads of image, installer, etc. Two dif imagers as well…Someone please tell me you are missing a step or doing something working because this does not make any sense… Booting in recovery mode maybe?

The only idea I have is a longshot. When you were getting the looping bootanimation (the blue Andy on a skateboard), or the "crickets"; how long did you wait before aborting the boot?
I have seen it take a LOT longer in those steps than I ever remembered (or thought reasonable). I'm talking 5 or 10 minutes.
It has something to do with recreating internal partitions and the dalvik cache (IIRC). It's been so long since I booted off the SD card, I'm not really sure what is supposed to happen that way.
Sorry that I can't offer more than "just let the first boot take all the time it wants".

It's all good. I understand.
So, Truth be told I think the first time with the "stable" image I let it go for 3 rotations before I said jumped ship. As I type now, I tried going back to #128 and it's doing it again. Andy has done skated across it at least 20 times...21... I'll let it run for a bit since you say that while I research the recovering to stock in emmc in case I decide to chuck it up and go emmc. This is driving me crazy. I would guess that emmc maybe more stable than running it from an SDcard.

You have got to be s***ing me. So I staied persistant and used my 8GB Transcend card again. This time it installed clean (I was taking pictures so I can read the damn thing) and booted clean. WEIRD!!!
I'm going to see if I can get my Scandisk to do the same.

I have seen mention that using the latest winimage is not a good idea, something about it not working right.
Version 8.1 is the usual recommendation.
I have been using the dualboot image racks11479 put together, and i've burned it with winimage a handful of times without issue, but always used winimage 8.1
Not sure if that's your issue, as i've never forayed into the realm of recent nightlies, but it could be a contributing factor.

Win32Disk Imager works perfect for me, even on win7 x64 and winimage would write, but the disk wouldn't boot.

WP7 7720 and SD card trick?

I wanted to pass along something i ran into while loading Yuki/xboxmod mango build on one of my HD2's (3 in the family). All of them have the stock 16gb sd card.
only one of mine loaded cleanly.
the other 2 regardless of hard resets would lock up upon the final restart on any zune updates. I tried several different sd cards that i had working on previous builds, all without any measure of success past the base 7004 rom.
I was able to do the following successfully on both non working phones.
I installed up to and including the very first (isv?) beta of mango with no sd card in the phone. At this point to move forward it told me i didnt have enough space. I put the 16gb card back in and did a hard reset (double volume method)
at this point i ran the zune update again. They both updated without any issues at that point and the cards are functioning perfectly in the phones.
I know there is a huge thread so i thought this might get lost in the middle of it and thought this could be helpful to those with sd card issues during the update proccess. Hope this helps some people out!

Take out your sd card and turn on your phone....if it turns on go to settings,about,reset...now don't let it boot...stop it at magldr screen...now take your sd sd card and format it in your Nokia phone....and insert it back into your phone and then boot it into wp7...now it should boot normally....im sure this will work
And next time please post in the q&a section

@fahd_freak: Well he wasen't exacly asking any questions was he, so it might not be as wrong anyway.....? And I have tried Hard reset a hundred of times my SD card just will not work with encryption even though i worked with the non encrypted WP7!
[On Topic]
But I can report I had the same error my WP7 constantly gave my the SD card error upon any kind of reboot (Common reboot og because of an update) and I tried your way but i still didn't work.
I bought a new 16GB kinston Class 10 MicroSD card and now my HD2 works like a charm.
Could it be the "Nokia Trick" that renders the SD card useless/as the card can't use the encyption part any longer or something like that?

Here is the thread you should be reading!
http://forum.xda-developers.com/showthread.php?t=1239705

norphf said:
@fahd_freak: Well he wasen't exacly asking any questions was he, so it might not be as wrong anyway.....? And I have tried Hard reset a hundred of times my SD card just will not work with encryption even though i worked with the non encrypted WP7!
?
Click to expand...
Click to collapse
oops sorry didn't see that he had posted a solution for the problem
So did u try getting the old sd card to work??

Sorry double post..

[Q] LINK2SD Broke efs on my SM-G900H

A- I recently installed Link2SD on My rooted Galaxy S5 (SM-G900H) and everything seemed ok. The app asked me to reboot my phone, when I did my phone stuck on the SAMSUNG Logo screen and FACTORY RESET/Wipe data didn't work. I even tried emergency recovery with no luck (Error mounting efs). I fixed the efs issue and I re-installed the stock ROM and re-Rooted my device.
I didn't re-install Link2SD anymore because I'm afraid it may break my phone.
1- What is the maximum size of the ext2 partition?
2- Does it work on SM-G900H without issues?
B- Despite what they say about Kitkat and that you cannot move your apps to SD card, I have the option on my phone to move (movable apps) to SD card and that's good enough for me. I purchased a SANDISK Extreme plus 64 GB SD card (Which is formatted in exFAT by default). When I move apps to SD and reboot my phone, all the apps on SD disappear and my phone starts acting weird and apps crashes. Maybe it's because of exFAT but I'm sure the SD card is fine and not broken. That's why I wanted to try Link2SD and see it it solves the problem.
Have anyone faced theses issues? Anyone know a solution for these problems? I appreciate any help.

Bump... Me too!
bjaguar33 said:
A- I recently installed Link2SD on My rooted Galaxy S5 (SM-G900H) and everything seemed ok. The app asked me to reboot my phone, when I did my phone stuck on the SAMSUNG Logo screen and FACTORY RESET/Wipe data didn't work. I even tried emergency recovery with no luck (Error mounting efs). I fixed the efs issue and I re-installed the stock ROM and re-Rooted my device.
I didn't re-install Link2SD anymore because I'm afraid it may break my phone.
1- What is the maximum size of the ext2 partition?
2- Does it work on SM-G900H without issues?
B- Despite what they say about Kitkat and that you cannot move your apps to SD card, I have the option on my phone to move (movable apps) to SD card and that's good enough for me. I purchased a SANDISK Extreme plus 64 GB SD card (Which is formatted in exFAT by default). When I move apps to SD and reboot my phone, all the apps on SD disappear and my phone starts acting weird and apps crashes. Maybe it's because of exFAT but I'm sure the SD card is fine and not broken. That's why I wanted to try Link2SD and see it it solves the problem.
Have anyone faced theses issues? Anyone know a solution for these problems? I appreciate any help.
Click to expand...
Click to collapse
Yes, I am having a very similar problem and I also have the 64GB SanDisk Extreme and SM-G900H and rooted.
Did you ever find a resolution?
My extSD seems to come and go. The last time I uninstalled the last 2 apps and it was good for 24 hours. Put I just pulled it off the charger and it started acting up again.
I cleaned the contacts, chkdsk'd it on my PC (everything reads fine) and rebooted a few times but no luck.
This post had some good recommendations but cleaning contacts, etc. didn't help me.
I was going to try an OTA update but it seems that I need to un-root first. That's my next step -- starting over.

Try FAT32
alex_tytn said:
Yes, I am having a very similar problem and I also have the 64GB SanDisk Extreme and SM-G900H and rooted.
Did you ever find a resolution?
My extSD seems to come and go. The last time I uninstalled the last 2 apps and it was good for 24 hours. Put I just pulled it off the charger and it started acting up again.
I cleaned the contacts, chkdsk'd it on my PC (everything reads fine) and rebooted a few times but no luck.
This post had some good recommendations but cleaning contacts, etc. didn't help me.
I was going to try an OTA update but it seems that I need to un-root first. That's my next step -- starting over.
Click to expand...
Click to collapse
You SD card is formatted with exFAT? Try formatting it with FAT32. I didn't try it yet because I can't use my phone since my EFS partitions are gone and my IMEI code changed to 004999.... (Generic IMEI code).
Let me know if this solves your problem.:angel:

bjaguar33 said:
You SD card is formatted with exFAT? Try formatting it with FAT32. I didn't try it yet because I can't use my phone since my EFS partitions are gone and my IMEI code changed to 004999.... (Generic IMEI code).
Let me know if this solves your problem.:angel:
Click to expand...
Click to collapse
64GB will for sure need to be exFat -- FAT32 can't access all the space.
This is a good utility to reformat and fix it OR you can use the cmd level commands.
For me, I am able to use it intermittently now -- seems like it will work for hours, even days, then have a problem when I pull it off the charger. Of course, I woke up this morning and it wasn't working AGAIN.
I am on the phone now with Samsung tech support to see if there is a log somewhere that can give me more information about what is exactly failing. I did use this same card in 2 other Galaxy S5's (AT&T and T-Mobile versions) with no problem. Maybe I ruined the card when I had it in my wallet?

FAT32 - I was wrong.
alex_tytn said:
64GB will for sure need to be exFat -- FAT32 can't access all the space.
Click to expand...
Click to collapse
I was wrong. FAT32 CAN access all the space. I reformatted with FAT32 using the fat32format program and still have the same problems.
Furthermore, it happens with and without root -- I've reflashed a million times now.
At this point, I think that I just got a bad card reader in my unit because the card went off just by tilting the phone sideways last night (clean install, no root, no apps).
Good luck to the original poster.