Why is that when i flash a kernel on a compatible rom it boots to the samsung note 2 logo for a few seconds then it just sits there black?, no progress is ever made, only sitting there black. when i decide to restore to the fresh nandroid backup i made before the kernel flash it always corrupts it somehow and i cant restore to it, always gives me an error at the restoring data part . Its for the tmobile note 2; please and thanks for the help
oCazper said:
Why is that when i flash a kernel on a compatible rom it boots to the samsung note 2 logo for a few seconds then it just sits there black?, no progress is ever made, only sitting there black. when i decide to restore to the fresh nandroid backup i made before the kernel flash it always corrupts it somehow and i cant restore to it, always gives me an error at the restoring data part . Its for the tmobile note 2; please and thanks for the help
Click to expand...
Click to collapse
we need more details. rom, recovery info?
I currently am running slimkat rom 4.4.2 on my note 2(tmo), when I flashed Perseus kernel on my phone I was using a regular debloated 4.3 rom but still went black. I have CWM, when I flashed everything was good(booting up never past the black screen) when I went to recover back to my fresh backup it starts off good but when I gets to recovering data it sits there for a few minutes and then it gives me an error "error recovering from backup". I wish I had more to say but I'm writing this from my phone
Sent from my SGH-T889 using XDA Premium 4 mobile app
oCazper said:
I currently am running slimkat rom 4.4.2 on my note 2(tmo), when I flashed Perseus kernel on my phone I was using a regular debloated 4.3 rom but still went black. I have CWM, when I flashed everything was good(booting up never past the black screen) when I went to recover back to my fresh backup it starts off good but when I gets to recovering data it sits there for a few minutes and then it gives me an error "error recovering from backup". I wish I had more to say but I'm writing this from my phone
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
make sure you are on the latest version of CWM. I don't know if perseus is still supported. I would give agni or devil kernel a try. also flash your rom then boot it up. Then reboot back to recovery and flash the kernel
Thank you, I'll give it a try in a few
Edit: sorry it took a while to respond after flashing one of your suggested kernels; I flashed devils kernel and it worked great no black screens, absolutely no problem at all
Sent from my SGH-T889 using XDA Premium 4 mobile app
Related
I tried to install CarbonRom JB 4.2.1 found here http://forum.xda-developers.com/showthread.php?t=2136995 but after install and reboot the screen flickered at the first boot screen and wouldnt go on. I had been running omega v11 before just fine, I tried to go back to omega and new it is stuck at the boot screen and can not go past. I can get into download mode and recovery just fine, but nothing after that.
What should I do? I do not want to press on and cause further damage before I can find a fix! Thanks in advance for a timely response.
p.s. meant boot screen not boost screen in title
Do you have a complete version of Omega on your sd card? Have you tried wiping, installing, and THEN restoring Omega. You may have a problematic version of CWM, which has had issues with both Aroma and CM10.1 variously.
I have the same version worked the first time (922mb). I tried a rom wipe then install but do not have a backup of omega just my stock rom. I am also running teamwin recovery not cwm. Would going back to a stock rom correct this?
reverting back to a stock rom seems to of fixed it. Thanks Ben for your help!
You should have done a data wipe.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
You should have done a data wipe.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I did, unfortunately I guess my phone just rejected the rom switched over to slimbean with no errors. :victory:
Glad you're back on track, dude. It's always a little bit scary when you don't have a functioning ROM installed.
Hi, this morning I encountered something which I haven't seen before in my 3 years or so of flashing roms on Android phones. The scenario was the standard process: Root with Odin > Install CWM with Odin > Copy Rom / gapps package to sdcard > Wipe & Install rom with CWM.
I rooted my Note II using CF Auto Root, all went fine, I flashed the latest Phil's touch CWM recovery using Odin which was also successful.
I had root access and was able to do a titanium backup of apps and messages/call logs. I successfully did a Nandroid backup of the stock rom.
After wiping data through CWM as per normal, I flashed the latest Utacka ParanoidAndroid and gapps. The flash was successful, but after rebooting, the 'Samsung Note II' splash screen only appeared briefly, then the image sheared and distorted and the screen went black, in less than three seconds.
I restored my nandroid backup and repeated the process, this time also formatting system, and installing CM10.1 nightly instead of PA. Again, I got a distorted splash screen then a black screen when trying to boot.
Can anyone think of a reason why my phone does not seem to be able to boot a custom rom?
Many thanks
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
koalauk said:
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Really? I've tried searching xda, google and the CM forums and havent found anything relevant.
I had this problem recently and after some nice guys helping me out we conclude that the solution is to flash RedPill kernel as the culprit for this glitch is the stock kernel you previously had.
I had such issue with my Note2 too. I was advised to flash Thor kernel 0.15 too after flashing cm10.1 and gapps. And problem was solved. Now cm10.1 boots normal on my Note2.
Sent from my GT-N7100 using xda premium
Did you do a factor reset.
Sent from my GT-N7100 using xda app-developers app
Alright, im not completely new to rooting but I have encountered a new problem.
I rooted my phone through odin (galaxy s3 T999), had some hiccups with that so I ended up downloading the stock rom tar and reflashed using that, problem solved good to go still rooted. awesome.
So, I attempted to flash the cyanogen rom using clockwork mod. it wouldn't come past the load screen, went into clockwork mod to recover my backup but for some reason it wouldn't let me access the SD card to get it. next thought was to go back to odin and flash the same file I used previously to get back to where I was, for some reason this is not working, I can get to download, use odin to flash it, says success and all that, then upoon rebooting it stays at the Samsung loading screen.
So from there I went and downloaded the GS3 toolkit and tried all of their recovery files, all having the same issue. about 18 flashes later I tried reformatting from the phone itself, same issue with the samsung logo being stuck. And now, I am currently baffled, anyone wanna help me out? I have a feeling it has something to do with the .pit option on odin, but I am not that advanced and its just a hunch. so...thanks in advance guys!
So I understand not to touch pit, roger, reading other posts makes that clear, but still cant find a fix, the top right of my download says
ODIN MODE
Product Name SGH-T999
Custom Binary yes: 19 counts
Current Binary Samsung Offical
System Status Custom
Qualcomm secureboot Enable
Okay, what is the current state of the device?
Whst do you see when you boot into recovery ( take battery out of phone the put it back in and do the following: hold volume up, home button and power button, let go of all buttons when you feel the phone vibrate and blue text flashes in the upper left corner of the screen)?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I just tried to send a rom over that had CWM 6.0.2.3 and it installed that, but still stuck on logo. going into recovery I am in CWM 6.0.2.3
have the standard options wipe/factory, install from zip etc.
You flashed a rom that had cwm 6.0.2.3 or did you flash a rom while on 6.0.2.3?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Flashed a rom that had 6.0.2.3. I do not have any roms on my ZIP, been doing everything through ODIN. Very confused as to why it suddenly stopped working.
DocHoliday77 said:
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what do you mean by full wipe, factory reset? or something else?
connorjiy said:
what do you mean by full wipe, factory reset? or something else?
Click to expand...
Click to collapse
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looked it up, that is what I do by default, didn't know thats what was considered a full wipe, just tried it with similar results, didn't know about the dalvik cache though. im on a work computer so I cannot currently DL a new rom from the site, I hope thats what the issue is, but I still cannot see why my other ones would suddenly not work.
connorjiy said:
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
Click to expand...
Click to collapse
I'm just not sure what you mean by it installing CWM attached to a Rom? Recoveries shouldn't be included with a Rom.
Odin flash the root66 firmware, then reboot to STOCK recovery and factory reset. This will wipe all user data, including your internal sd card. Then try rebooting again.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Have you tried PhilzTouch yet?
Alex9090 said:
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
lalec said:
Have you tried PhilzTouch yet?
Click to expand...
Click to collapse
Never used philz and never thought of just reflashing the kernel. I may try that though. Now to find the kernel. I should mention that I end up using Odin to reflash stock. Then I root and then custom recovery. That boots fine and for the most part all I'm ever doing is trying to restore a 4.4 rom I backed up.
Flashing a kernel worked. lol my phone doesn't think it's the stock kernel but it booted at least.
I do find this interesting. I would think when you restore a nandroid backup that it would restore the kernel that was with the rom you are restoring. I guess this isn't the case?
Using the latest clockwork has always worked for me.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had Rom Manager Premium since my Defy days. I'm a firm believer in it. I was just surprised I would have to reflash a kernel after restoring a rom.
Corwinder said:
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
Click to expand...
Click to collapse
I use OUDHs Touch recovery v1.0.3.3 in conjunction with Rom Manager and I have NEVER had that problem. Also, when I use Rom Manager to "Back Up Current Rom" I can NAME the backup file, and it goes into the recovery and uses the filename I have already typed in and it's a seamless operation. Even using restore via Rom Manager works seamlessly and it has NEVER balked on me.
The only time I had a problem was once using My Backup Pro and trying to do an on-line system backup. MMS, SMS, Call Log has always been absolutely perfect! No out of sequence messages, and all the pictures are restored correctly too!
Aloha and Good Luck!
BTW, I am on a Stock 4.2.2 with the latest M919UVUFNB4 (modem.bin) Flashed for the radio and it's reception qualities are better than it's ever been before!
Hi guys,
I recently rooted my phone and switched over to CM 10.1 for a little bit. I wanted to switch back to my rooted TouchWiz, but when I tried to restore it from my CWM restore something appears to have gone wrong. The phone will start up and I can get past the Samsung splash screen, but then it just sits on the AT&T globe screen indefinitely. Anyone have any ideas on what has happened or how to fix it? Thanks in advance!
Try flashing a touch wiz rom.
Sent from my SGH-I317 using XDA Free mobile app
I ended up using a rooted TouchWiz rom and reloaded it using Odin. It was still booting and getting stuck on the AT&T splash screen so I booted into recovery mode and chose to factory reset/wipe data. After that it booted just fine.
bigbrown1135 said:
I ended up using a rooted TouchWiz rom and reloaded it using Odin. It was still booting and getting stuck on the AT&T splash screen so I booted into recovery mode and chose to factory reset/wipe data. After that it booted just fine.
Click to expand...
Click to collapse
Good you figured it out on your own. Cuz that's what I was going to tell you to do.
Or just re flash the Rom again if it get stuck at the Samsung logo. In your case factory reset usually fixes most minor issues flashing Roms...
Sent from my SAMSUNG-SGH-I317 using Tapatalk