This morning when I turned on my NT I got the usual flash and initial screen but then nothing (no CM boot animation). Closer inspection (in the dark) revealed a slightly backlit screen so I held the power button until that went out and tried several more times with the same result.
I put in the recovery SD and restored from my most recent backup, thinking the boot image had gotten corrupted somehow. After restoring it booted up fine out of the CWM routine and worked OK. I shut it down midday and then remembered I wanted to do something else tonight. I ended up back where I started! It won't get past the slightly backlit screen.
I've tried inducing it to boot without the SD card (same result) and with the SD card from the OFF state by connecting it via cable to the USB port on my laptop (same result).
I don't know what to try next, beyond the obvious of yet another restore from backup and maybe never powering down again....
Help!
Update: so I left the NT connected via USB to my laptop for an hour or two, after letting it get to the black backlit screen (but no boot animation or any other evidence of life). When I pressed the "N" button it displayed the lock screen!!!!! Everything seems to work but this is too bizarre. Still would like suggestions.
Related
Hi
I used the factory reset function on my tab a couple days ago to delete all apps and such and upon reboot it was stuck at the slowly flashing Samsung logo and would proceed no further. I left it for a good hour and a half in that state before I tried hard resetting it but no dice. I've had it do this before when I first rooted it, but unlike that time it doesn't replay the whole boot animation, just the logo part at the end of the animation. I managed to get it in clockwork mod or bootloader whatever that function is and cleared all the caches and did a reboot recovery (i believe thats what it was called) but upon reboot it did the same exact thing. So after that I gave up and went to bed, but the next day when I went back at it again it wouldn't even turn on. After messing around with the power button and volume button trying to get into recovery mode it finally turned on but went to the battery screen with no other actions. I've tried several times to get it into recovery mode but it either wont turn on or it just goes to the battery screen. I have it plugged into my pc at the moment and apparently it is in recovery mode or something because Odin recognizes it. Says [0:COM3] and the box is yellow, but the screen never turns on though when holding the power button and volume button while it's plugged into a pc, the pc recognizes something plugged into the USB slot. My pc is only recognizing it as a modem and will do nothing else with it.
I have the Starburst rom and the overclocked kernel installed and would like to either revert it to stock rom or perhaps the AOKP rom, milestone 6. Is there any way to do this if I can't boot it into a state where I can access the SD card on my pc? All the guides I've found always require I put files on the sd card to flash in clockwork recovery mod. Thanks for any assistance
Edit: Solved it myself, feel free to delete this post. Thanks!
Hello all,
I am merely posting here if anyone has a better insight or idea, since I haven't followed with all issues regarding the Galaxy S II International version.
I have purchased mine from one of my country's carrier nearly 2 years ago. I have in the course of these 2 years, rooted it, flashed CyanogenMod, and happily updated it every so often. I always used nightlies, updating almost everyday.
In the last 2 months, it had become sometimes very sluggish, frequent slowdowns, and many lockups, freezing, and some random reboots. I was getting a little tired of it, but was getting used to it.
Yesterday, I was using it normally, when a slowdown started. The app (was 3D game) got unresponsive, but I could still pull the notification drawer, so it wasn't frozen. I pulled and pushed the drawer about 2 times, and then it also stopped responding. The screen was on, touchlights were on, and since I had seen it before, I pressed the power button for a reset.
Then the first boot screen, with the yellow triangle (where it says Samsung Galaxy S II GT-I9100) appeared, but it got stuck there and didn't get past, apparently frozen.
I tried a quick more reboots, and then tried (with very difficulty) entering CWM recovery. I got eventually there, and CWM was working as it should. I considered wiping the cache, or just reinstalling the last nightly I had saved, but decided first to just press "reboot system now".
It also got stuck on the yellow triangle initial screen. This time I couldn't get to the CWM recovery (it seems there was a very small time frame to it to enter before it actually restarted again from long pressing the power button). In a dark room, I noticed that even when the yellow triangle screen was black, the display was on, the backlight was on. The black was bright, and if I pressed the powerbutton for a reset, I could see the screen actually turning off and then on again, and going back to the yellow triangle screen.
I tried to go into Odin recovery, and eventually made it there.... So I pressed to restart the phone, and it continued frozen on the yellow triangle.
I went home with the screen frozen (I couldn't power it off, and I didn't remove the battery). I noticed that after some minutes it restarted, the screen went black and again to the frozen yellow triangle.
I managed to get to CWM recovery after several attempts with the 3 button press, but a different error had appeared: E: Can't mount /cache/recovery/command (or something like it)
So I got home, downloaded codeworkx CWM recovery, put the S2 in Odin recovery, and using Heimdall uploaded it. It completed successfully.
I managed after several tries to get to CWM recovery, it opened again, but more "Can't mount messages" appeared, system_log and such, as I have seen on some forums, and that by then I never had. Read somewhere that probably the system partition got corrupted.
Then this time I reinstalled from the internal memory another nightly I had. I was with June 19, and used the June 16 one. It flashed successfully.
Then I pressed reboot system now, but still got stuck at the yellow triangle screen. And again the message "Can't mount /cache/recovery/command".
So I got into Odin recovery mode (volume down) and using Heimdall again uploaded CWM recovery. But Heimdall got stuck at "Loading KERNEL 100%" It reached 100% but never exited. And the bluebar that was supposed to appear on the S2 screen (that appeared the first time I flashed CWM), didn't appear.
Since it got stuck there for a while, I Ctrl-C'ed my way out of Heimdall, and pressed the power putton on the S2 for another reset.
But this time, it never woke up again. No more yellow triangle screen. No more "active bright black screen". Nothing.
And it doesn't charge even when plugged to the charger.
I am reading about SGS2 that won't turn on and won't charge. It seems a general agreement that Samsung assistance tells us it's a motherboard failure, and should be replaced (and at least here in my place it's helluva expensive).
Since many cases the phone just went dead, mine wasn't quite the case, since it was somewhat alive in the yellow triangle and apparently I could have f*cked up when I Ctrl+C'ed Heimdall and turned off the phone when Odin recovery clearly states "Do not turn off target !!", even though when the flash goes ok, you have to reset it.
Two questions:
1. Is there anything else that can I do to revive it?
2. Can I recover at least the pictures and videos I had saved on the internal memory? I had a ton of pictures and videos inside DCIM/Camera, where for a long time CM10.1 camera could only save pictures to the Internal memory, and when a nightly fixed it, I kept it in internal memory.
If anyone got this far since I was exhaustingly detailed, thank you for your attention!
Unpluging was the bad move that killed your phone. Can try a jig
andrewwright said:
Unpluging was the bad move that killed your phone. Can try I jig
Click to expand...
Click to collapse
Well I had just done the same process, and it was quick. There was no waiting period after the 100%, and Heimdall exited cleanly.
The last time it got stuck in 100% for about 30 seconds, and I decided to abort with a Ctrl+C, unplugged and restart...
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
WidePants said:
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
Click to expand...
Click to collapse
I'm having the same problem. I downgraded from 1.4.3 to 1.4.0. I was able to boot it once and then shut it back down so I could root it. Now it won't start up at all and I have tried everything that I can find to boot it to no avail.
The NT can sometimes get stuck in limbo while booting up, especially with SD-based boot. To get out of it, hold down the power button for 20-30 sec to turn it off then power it on again. Also remove any "bootable" SD card from the card slot; if it boots then the card was not bootable and its non-bootability was the problem.
It's also possible that the NT battery is completely drained (battery readings on some CM builds can be quite off, sometimes as much as 20 points) in which case you'd need to use the BN wall-charger and charge it for 8-12 hours.
I'm using the Samsung Galaxy 10.1 Tab (Verizon) SCH-i905
From what I have read, the reboot loop is when the user sees the boot screen, but the tablet keeps on rebooting. My problem is severely worse.
My tablet keeps on reboots, but it doesn't show the boot screen. Instead, it just shows a blank lit up screen.
Not only that, but I cannot always turn on my tablet. I keep trying, but it typically turns on after I keep plugging and unplugging the USB from my outlet to computer, and so forth (for about 10 minutes). When it finally boots, I can go into Odin mode. I flash some sort of firmware to it, and then my device turns off. And I need to keep attempting to turn it on again for 10 minutes before it actually turns on.
Nevertheless, my device still does not work properly. I know this is infact a software problem because my device was working fine yesterday, until I decided to unmount and mount certain things in Recovery mode.
So far, I have flashed recovery.tar.md5 , PDA_SIGNED_P7105.tar, and 75XX_CWM_Recovery_v5.1.2.6.tar. None of these have fixed the problem. How can I return to factory settings?
I just saw the previous thread about this device and am currently installing PDA_HC31_EG0 ... If everything goes right, then there should be no problem. But I highly suspect that the firmware will flash successfully, and then my device will proceed to power off for another 10-15 minutes before turning on again.
If I leave my device plugged into the power source, it will start turning on and off (the blank lit screen) periodically. For example, turns on for 5 seconds, then turns off for 5 seconds (and repeat).
While this is a software problem, it seems to be on the OS level. Are there any other ROM Links besides the ROM in showthread.php?t=1342995 that I should try? Also, is there any other possible alternative?
Help! I just got CM 10.21 emmc running on my 8 GB NT and was becoming familiar with the system. I installed AdAway and after setting it up allowed it to reboot. Mistake!
This is the first time I've rebooted or turned off since the ROM flashing. I get the "N" screen, then an unnerving flash, followed by the Cyanoboot universal bootloader screen and it says "Loading (EMMC)...". Then all goes black :crying:
There is still backlighting and holding the power button will eventually extinguish it. Plugging the tablet into the charger (or the PC) has no effect (off or on).
It did the flashing according to this thread and everything went as described. The tablet has behaved flawlessly until this. I could theoretically recover to stock and start over again but if there is a way to fix this, I'd rather.
EDIT: Update. I tried booting with the CWM SD card that holds the recovery files as well as the files used to flash the CM 10.21 ROM. I get a red bar message that says "booti: bad boot image magic (in memory)". Underthat is "(SDC) LOADING BOOT...." and it's just stuck on that screen.
EDIT2: Solved itself eventually after a number of attempts. Really freaky behavior.