I went through and followed the instruction to a T.
Got CW3 installed, everything appeared normal, converted to EXT4 no problem. Wiped 3 times, no errors, installed midnight 3.3 and rebooted.
I was greeted with the setup screen but I have absolutely no signal. Just the circle with a slash through it. I can't even connect through wifi.
Since I can't sign into my google account, I just skip it for now.
So now I'm at my home screen and I press and hold the power button to shut down. Now I see the airplane mode flickering on and off rapidly.
Right now my phone is pretty much useless. Any help would be appreciated.
sounds like something went wrong. Flash back to DK28 with Odin and try again.
I'm actually coming from DI18.
I just used odin to do a restore back to DI18, I'll try it again.
I don't see how something could have gone wrong, I installed it exactly how it's written.
No good.
Just flashed again, following the documented instructions again. Same problem.
Have to flash either all of dk28 or at least the modem to run any of the dk28 roms. Just odin to dk28 and start from there.
That did it.
I used odin to flash to DK28 and booted, everything was working.
Reflashed to Midnight 3.3 and I have a signal now.
Related
So, I flashed Caulks new EK02 Rom, and, when I went to restart, phone is stuck on boot screen; Wiped everything as normal before flashing, but stuck on the yellow triangle screen.
I tried all the normal stuff to get into recovery, but phone won't go past the initial boot screen.
I have a mac computer, and thats all there are in the house, so I can't use Odin..
Can someone help me get the phone back to a state where it starts up?
Thanks so much for your help!
Use heimdall.
Sent from the future.
did that, flashed to stock, and we are back in business!
I did think about the hammer though...
MOD, please close!
Hello, this is kind of a long story but.......I was in clockworkmod recovery looking to restore back to a backed up rom. I saw a backup titled, 2000-01-01.00.00.16/. I didn't remember a backup that had that named and it said it was from the year 2000. Out of curiosity I decided to backup to it. Then It got stuck or what appeared to be stuck on "checking md5 sum". After ten minutes I pulled the battery thinking it hadn't even started restoring. When I put the battery back in I got the charging battery icon with a cloud and a thermometer, assuming this meant that the phone was to hot I felt the back and it wasn't hot at all. I tried to power the phone off but each time I turned it back on I got the same icon. Finally I tried plugging it in. Then the icon went away and the booted into clockworkmod. So then I restored to the Unnamed rom and the led notification light wouldn't go off. Then every time I turn the phone off I get the thermometer icon and have to plug it in. On top of that my computer won't recognize the phone. I want to use Odin to go back to stock but since the computer won't recognize it I'm stuck with a phone full of problems. Any suggestion?
First backups can't contains signs /&%*+# etc...
Second.. can you get to recovery?
Sent from my SPH-D710 using XDA Premium App
omg .. i THINK YOU BRICKED YOUR PHONE!!
But not to worry, most likely it's an easy fix. Reboot phone a couple times, MAKE SURE DRIVERS & EVERYTHING are INSTALLED FIRST, open ODIN with proper .TAR file, .PIT NOT needed. Only Auto Reboot box should be checked, then plug in to pc. Wait for phone to connect and hit start. BE PATIENT. If it doesn't work try booting into CMW, holding POWER and VOL UP buttons. Hope this helps!
Thanks everyone for the help. I ended up downloading mobile odin from the market, and then flashing the stock unrooted EK02.tar file. I still had the same problems and figured it was a hardware problem. So I took it into my local sprint store and they took one look and it and ordered me knew for free, no questions asked!
Tonight I flashed for the first time (yay, go me) and everything worked great, followed this thread: http://forum.xda-developers.com/showthread.php?t=1739426. I chose to flash JB 4.1.1 stock rooted (also in that thread).
When I use my phone, all is great, EXCEPT, if I don't touch it, the screen times out and goes black in ~5 seconds. I went into settings->display and set it to 10m...same issue. Rebooted, same issue. Power off, start up, same issue.
Ideas?
wow never-mind, im an idiot.
Well what did you do wrong? :silly:
[Samsung Galaxy Note II N7100]
((EDIT: Suddenly, after leaving it turned off for about 15 minutes, it works. It just powered up IN THE PACMAN ROM! Still no clue what happened though, Would like to find out for the future))
Hello there,
My device was working fine yesterday, however today I re-rooted after an update. This went well and all was working fine, until I decided to try my first ROM, the PACMan ROM. I flashed with CWM6 (Following a tutorial, using Odin) which seemed to work fine until I actually tried to use it. I went to reboot my phone, and when it started up, it was (graphically) glitching, with the Samsung Galaxy Note II logo twitching around the screen, and a strange set of brown, thick-ish bars moving around the bottom half. Following a few seconds of this, the device shut off.
Following this I discovered that I could get it to stay on and boot-up successfully if I held down the home button (Not sure if relevant), however I still wanted to get down to the bottom of the issue. Following some research, I decided to try and flash a different download of CWM 6 for my phone again. This time it worked, and I went straight to factory reset then install the 'Gapps' and ROM file. There were no unexpected errors in this installation, however when the phone restarted, the same glitch occurred, only without a way past it.
I have since tried patching with the other CWM file that didn't work to see if perhaps I could use my phone again, but this didn't work. Similarly, I've used the working CWM to do a factory reset without installing any ROMs, and the booting still didn't work.
Please help I don't wan't to risk doing further damage, and would be perfectly happy going back to regular jellybean.
Thanks in advance!
Regards,
Thomas
TL;DR My Galaxy Note I N7100's boot is after flashing
Hello,
Ive had this device for now 3 months and never once had a problem. I did however stay on stock for quite awhile just rooted. Recently Ive been testing out different roms and ran through quite a few until I heard about the all mighty CM gem by Sultan. So I figured I would give it a shot. Went ahead and downloaded that along with gapps like any other rom. Booted into TWRP and wiped both the system and cache/dalvik. Then went ahead and attempted to install the rom. Unfortunately midway through it froze and my screen artifacted. I figured I would give it a few seconds and the screen turned black with the notification light turned on. I then tried to reset it with a volume+power combo and nothing happened. After about 5 mins of letting it rest it turned back on.
I went ahead and tried this process again thinking it was just a fluke but nope happened again. So I figured it was a corrupt zip file and I would just go back to the stock image I flashed before which was working perfectly fine. Again froze and gave me artifacts. Hoping to find an answer I downloaded the latest TWRP image and flashed the roms again. Same outcome. I even went out of my way to flash the stock recovery, fully reset all my data through there and then reflash TWRP and sideload Sultan's CM. Which I for once actually got into the ROM however now whenever I get into the ROM my phone overheats instantly and I get the nasty artifacts back along with a reset of the phone. Well kind of the screen goes black and I have to wait until it cools off to turn it back on or else it wont turn on.
Anyone have this issue? Anyone know how to solve this? This is my only phone and I go off to college next monday. Thanks in advanced.
UPDATE: I now cannot get the phone to turn on. No haptic feedback, no LED notification light, no recognition in windows. Literally a paperweight at this point.
The same here, flashed CM and Gapps...
Phone hangs on boot, rebooted the phone and now it won't go on..