Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
AW: Strange IMEI behavior
Rekoil said:
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
Click to expand...
Click to collapse
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
jjpro45 said:
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Beats me mate, myself along with a couple others are having the same exact problem. We have no idea what is going on. Discuss possible solutions in the thread I linked.
AW: Strange IMEI behavior
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yes, join the club.
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Cundis said:
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Not at all. I have been using it from the start. Will choose it every day over stock kernel
nateboi81 said:
Not at all. I have been using it from the start. Will choose it every day over stock kernel
Click to expand...
Click to collapse
Just out of curiosity, what happens if you install a non-Perseus kernel?
Related
Galaxy note is stuck at boot screen after flashing the wrong rom. before its was Stock ICS germany
tried to flash again using pc odin .... but same
Tied to flash stock ICS but same
tried to flash gingeerbread but same
Installed Abbys kernal.
strange thing noted unable to perform full wipe from CWM.
full wipe word after ABys kernal installation.
please advise.
help needed.....
Tried to flash PIT and bootloader also but the results are same.
flashing the wrong rom? what rom did you flash ? more info woudl be nice
its was on Stock ICS , flashed note at&t custom rom hybrid
unable to flash wipe rom.... odin stuck at data.img
Well, what happened?
I am stuck on the boot screen as well.
Did you performed Full Wipe on ICS Stock Rom ? If so then its unfortunate to say your note might be bricked.
I advise u stop flashing stuff when you clearly don't know what your doing.
Sent from My Omega powered beast, using Xparent ICS
qamarabbas277 said:
unable to flash wipe rom.... odin stuck at data.img
Click to expand...
Click to collapse
It is not a good sign. Looks like a case of superbrick to me due to emmc bug. Probably will need repartition with custom pit or adb.
Sent from my phone
forest1971 said:
It is not a good sign. Looks like a case of superbrick to me due to emmc bug. Probably will need repartition with custom pit or adb.
Sent from my phone
Click to expand...
Click to collapse
+1, you're bricked. Either repartition or claim replacement motherboard.
Sent from my GT-N7000 using xda premium
I wonder why people come here after damaging the device instead of before...
I don't even buy a device before reading a lot about it here in xda..
Sent from my GT-N7000 using Tapatalk 2
Hi guys,
I normally try and work this stuff out for myself (as you can tell by my join date and my post count) but this has me stumped..
I was attempting to change ICS rome and somewhere in the process something went wrong...
After many unsuccessful attempts of flashing, stock ICS & GB, Abyss.. I checked the partions for errors and found the actual size of p-10 was different than the reported size by 1kb.
So, tried the e2fsck fix- it reported that it had corrected some errors.. I tried flashing again and agin- no success.
I then deleted the partitions, recreated them and reformatted in CWM. ADB reports no errors on any partition. When I try to load an ICS rom, it installs then hangs when it gets to the screen where you select the language.
I can successfully install a GB rom, but after a couple of minutes I start getting errors- then the affected app closes.
Any ideas?
Thanks
bump... Anyone?
shawnthecableguy said:
bump... Anyone?
Click to expand...
Click to collapse
Which ics rom were you on originally before you tried flashing to which ics rom? Did you perform any wipes while on ics? Does sound like you have a good understanding of emmc bug and partitioning so forgive me if this all seems mundane.
Sent from my GT-N7000 using xda premium
shawnthecableguy said:
Hi guys,
I normally try and work this stuff out for myself (as you can tell by my join date and my post count) but this has me stumped..
I was attempting to change ICS rome and somewhere in the process something went wrong...
After many unsuccessful attempts of flashing, stock ICS & GB, Abyss.. I checked the partions for errors and found the actual size of p-10 was different than the reported size by 1kb.
So, tried the e2fsck fix- it reported that it had corrected some errors.. I tried flashing again and agin- no success.
I then deleted the partitions, recreated them and reformatted in CWM. ADB reports no errors on any partition. When I try to load an ICS rom, it installs then hangs when it gets to the screen where you select the language.
I can successfully install a GB rom, but after a couple of minutes I start getting errors- then the affected app closes.
Any ideas?
Thanks
Click to expand...
Click to collapse
Download emmc app from market and perform a memory test... Get a rooted gb rom as it needs root access.. And skip all kinds of setup at startup once you flash the gb(rooted) rom
Sent from my GT-N7000 using xda premium
msedek said:
Download emmc app from market and perform a memory test... Get a rooted gb rom as it needs root access.. And skip all kinds of setup at startup once you flash the gb(rooted) rom
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
+1 for this approach, it sounds like there's lingering issues on the chip.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Which ics rom were you on originally before you tried flashing to which ics rom? Did you perform any wipes while on ics? Does sound like you have a good understanding of emmc bug and partitioning so forgive me if this all seems mundane.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I was on N7000XXLRB, Kernel Version 3.0.15-N7000XXLRG, and Build number IMM76D.XXLRG. Tried to go to AlBa rom, flashed Abyss, wiped cache/data in the CWM recovery and flashed the rom in CWM recovery...
I can successfully flash a stock GB rom with PC Odin, but it hangs on the boot screen( so I can't install dmmc test).
I have tried everything I can think of, just waiting on a jig to come in the mail so I can reset my counter for warranty
If you find a solution please post it.
I think i have the same problem. I posted it in general ( can anybody move it over here? I think this was wrong. Sorry i panicked. )
It's called permantly rebooting after flashing cm9.
I pledge for a solution.
Sent from my HTC Desire using xda premium
shawnthecableguy said:
I was on N7000XXLRB, Kernel Version 3.0.15-N7000XXLRG, and Build number IMM76D.XXLRG. Tried to go to AlBa rom, flashed Abyss, wiped cache/data in the CWM recovery and flashed the rom in CWM recovery...
I can successfully flash a stock GB rom with PC Odin, but it hangs on the boot screen( so I can't install dmmc test).
I have tried everything I can think of, just waiting on a jig to come in the mail so I can reset my counter for warranty
Click to expand...
Click to collapse
If you are on stock gb go recovery (volume up+home+pwer) wipe data and reboot
Sent from my GT-N7000 using xda premium
msedek said:
If you are on stock gb go recovery (volume up+home+pwer) wipe data and reboot
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yeah, tried that....
I have tried everything I can think of. The Odin flash does'nt spit out an error... I can flash anything successfully but nothing actually boots?
I keep having to flash my backup because every time I flash a script or have to force reboot my phone, when the phone boots everything force closes and the phone is totally unusable. Any help on how to solve this would be very much appreciated :thumbup::thumbup::banghead:
Sent from my GT-S5570 using xda premium
delete your backups
and do fresh install
droidface said:
delete your backups
and do fresh install
Click to expand...
Click to collapse
I've tried that mate. I've deleted all backups and done fresh installs of a few different roms, but to no avail. It's got to the point that I have to keep updating my backups because the phone becomes unusable so often
Sent from my GT-S5570 using xda premium
If nothing helps then you can try this as the last option. You can reflash your firmware via Odin then custom recovery after rooting your phone and finally the custom rom you are using.
Sent from my GT-S5570 using XDA
hsay said:
If nothing helps then you can try this as the last option. You can reflash your firmware via Odin then custom recovery after rooting your phone and finally the custom rom you are using.
Sent from my GT-S5570 using
Thanks for the reply. I think I'm gonna have take your advice and try this as a last resort. It's got to the point that I'm afraid to reboot in case it happens again.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
How exactly you perform clean install? And what scripts you flash?
Try going back to a stock ROM release, then flash CWM via ODIN and from there, a rom of your choice
yackovsky said:
How exactly you perform clean install? And what scripts you flash?
Click to expand...
Click to collapse
I flashed SlaidyBoostV2.3, it made my phone completely unusable. I flashed the Beats script too, and that had the same effect.
I perform a clean install by wiping data and cache/dalvik. Then I flash the rom and repeat the wiping process. Am I doing something wrong?
Sent from my GT-S5570 using xda premium
LeSommy said:
Try going back to a stock ROM release, then flash CWM via ODIN and from there, a rom of your choice
Click to expand...
Click to collapse
I'm having trouble getting the stock firmware for my phone. It says the firmware is for SIM unlocked phones, and my phone is locked to one network. Looks like I'm gonna have to get my phone unlocked. I'll do this as a last resort if I can't find a solution.
Sent from my GT-S5570 using xda premium
Hello! My friend's phone basically bricked while flashing. I did root first with stock recovery method, then i installed 6.0.1.4 touch cwm, which installed fine, but bootlooped to recovery(normal). I downloaded 6.0.2.6(which appeared as 6.0.2.7 in recovery), transferred it to ext sdcard, then installed it. No more bootloop(after datawipe), but now it said that too little memory, cannot perform this action. I checked it from settings, no memory was mounted? Weird. Well, i did as i promised to my friend, installed remics jb v2, and gapps. Starts fine, incredibly fast compared to stock! Now i take the phone to my friend, and then he puts his sim card in, askes pin code, entered. Now, there is still nothing in signal bars. I check phone info, no imei(000000...00) imei sv 00. I tried to install stock again, nothing. Would using only phone to install recovery and others affect this? Because i have done several flashings with this model and always has worked. But then i had computer in use. Help please, i told him that it has it's own risks, i do not take responsibility. I have no efs backup, that's the problem. It usually takes backup automatically. Thanks!
P.s. Sorry for possible typos, i'm writing this on my tablet.
Sent from my GT-P5100 using XDA Premium HD app
Try to install broodrom rc5 rev2 via odin. I think it can resolve your problem.
Sent from my GT-i9001 using xda premium
kRYySTy said:
Try to install broodrom rc5 rev2 via odin. I think it can resolve your problem.
Sent from my GT-i9001 using xda premium
Click to expand...
Click to collapse
Broodrom helped me when i tried to flash cm10 with a bad recovery and also here's a hint dont use 6.0.2.6.
Try a non-touch one.
Hi
Ancient history - I rooted my Galaxy Note a few weeks ago with a Philz kernel. I didn't really know what I was doing, but it seemed to work fine. This morning, my phone was shut down, and wouldn't start up, sticking on the Samsung screen. I read other threads here, and it seems like to fix this, I need to flash the same Philz kernel using Odin when in download mode, then start up in recovery mode, mount as USB and extract my files, then restart and reinstall files, and I should be back to more or less where I was last night. /Ancient history
I've installed Odin, started the device in download mode, found the correct .tar, connected the phone, and started the process in Odin.
When it got to restart, the phone is again flicking the logo screen on and off, now with a yellow triangle and an exclamation. Does this essentially mean I need a different kernel? I was hoping that reflashing it with the same Philz kernel would solve the problem, but it appears not .
I solved this bit
I also solved this bit. Please see the edited original post for the current problems.
SamWise72 said:
I also solved this bit. Please see the edited original post for the current problems.
Click to expand...
Click to collapse
if you already have flashed philz kernel, try to boot into recovery mode with volume up+power+home button. Yellow exclamation is nothing to worry about, it can be removed once you have phone booted up.
treacherous_hawk said:
if you already have flashed philz kernel, try to boot into recovery mode with volume up+power+home button. Yellow exclamation is nothing to worry about, it can be removed once you have phone booted up.
Click to expand...
Click to collapse
Yeah, I found that I can get into recovery mode, I mounted and backed up my USB, and then I did a factory reset. The phone now runs, and I'm finding myself tempted to put in a KitKat rom, because I'm a glutton for punishment.
SamWise72 said:
Yeah, I found that I can get into recovery mode, I mounted and backed up my USB, and then I did a factory reset. The phone now runs, and I'm finding myself tempted to put in a KitKat rom, because I'm a glutton for punishment.
Click to expand...
Click to collapse
The Step to install kilkat are:
Install The correct philz kernel version.
Install the raw kernel and reboot the recovery.
Full wipe.
Install the 4.4 Rom
Install the gapps.
Wipe cache and dalvik
Roboot.
Sent from my GT-N7000 using Tapatalk
Need help mates. Can't seem to get my stock ROM nandroid backup restored and working. Keeps hanging immediately after boot up and reboots and hangs.
What should I do? Thanks in advance.
Sent from my GT-N7000 using xda app-developers app
Chibuoj said:
Need help mates. Can't seem to get my stock ROM nandroid backup restored and working. Keeps hanging immediately after boot up and reboots and hangs.
What should I do? Thanks in advance.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
You should start a new thread and describe your rom what you did, root or not, what kernel...in more details so that people can help. The issue in this thread is different from yours.
Sent from my GT-N7000 using Tapatalk 2
Chibuoj said:
Need help mates. Can't seem to get my stock ROM nandroid backup restored and working. Keeps hanging immediately after boot up and reboots and hangs.
What should I do? Thanks in advance.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
if you made nandroid backup from philz kernel then flash philz kernel, reboot recovery and try to restore. If you didnt include preload in the backup then that could be a problem. You can do a clean flash for the stock rom and then advanced restore and restore data.
treacherous_hawk said:
if you made nandroid backup from philz kernel then flash philz kernel, reboot recovery and try to restore. If you didnt include preload in the backup then that could be a problem. You can do a clean flash for the stock rom and then advanced restore and restore data.
Click to expand...
Click to collapse
Thanks. But didn't work.
Guess I'll have to try flash via Odin PC. Any helpful thoughts, or directions?
Chibuoj said:
Thanks. But didn't work.
Guess I'll have to try flash via Odin PC. Any helpful thoughts, or directions?
Click to expand...
Click to collapse
If you tried what i mentioned and that didn't work then you can clean install stock rom and you can extract the backup on pc by using 7zip or compression tool and the reatore tbat using titanium backup pro. I haven't tried this ever but this ia what i was suggested by @nokiamodeln91
Sent from my GT-N7000 using Tapatalk
Hey guys. Been around for a while and have never encounted this problem. I went to restore back to stock firmware after running a custom rom.. both 4.3... I added the firmware to odin. It failed before it started and rebooted th phone. Figured out that the firmware I downloaded must of been corrupt/incompletly downloaded.. stuck on samsung boot logo.. tried to restore a fresh complete rom but still stuck on boot logo.. is there something I can do to fix it other than sen it in.
Sent from my GT-S5830 using xda app-developers app
You don't mention recovery .
Usual would be to format sdcard system data cache boot to download mode and flash stock rom .
Yeah i have done all that
Sent from my GT-S5830 using xda app-developers app
After install, try pulling the battery during boot then boot into stock recovery and do a factory reset/data wipe.
Has worked for some
fridgie said:
After install, try pulling the battery during boot then boot into stock recovery and do a factory reset/data wipe.
Has worked for some
Click to expand...
Click to collapse
Tried. Didnt work.. seems like the I have corrupted something in the phone.. tried everything in this forum. But wont come out of boot loop..
Sent from my GT-I9305 using xda app-developers app
winxuser said:
Tried. Didnt work.. seems like the I have corrupted something in the phone.. tried everything in this forum. But wont come out of boot loop..
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Have you tried to change the sdcard?
viktorak said:
Have you tried to change the sdcard?
Click to expand...
Click to collapse
the sdcard is not the problem,, i have corrupted the partitions i think,, altho flashing firmware with odin works fine, it just doesnt boot
really wish I could afford to get this phone fixed I miss this phone and have gone back to an old crappy galaxy ace