Database Users

Discussion - Stuck at Sammy Logo Issue on Official Jellybean ROMs - Discussion

Mates, the problem is there, we should admit that, had it on Galactus rom twice ( reflashed the rom again after full wipes to make sure ), and had it also on the stock LSZ with its stock kernel, and also on Cassie's rom.
Nothing solves the problem apart from wiping data.
Is it the preload ? the kernel ? defective JB from Samsung ? I really don't know.
The only thing I would really like to mention is that on Cassie's rom, had the issue surprisingly occuring on odd restarts not the even ones ! the first restart gets stuck, the other goes on !
Tried all the tricks in the book (restart to recovery, reinstalling bootloader, overinstalling the same rom, wiping everything keeping data, nothing worked.
Unless data gets wiped, the problem persists.
BTW, I had the same problem on all the previous leaked versions before the official ones.
Back to ICS while discussing here.....

i have no bootloop on the LSZ. been on it for couple of days and many reboots later....no issue.
i flashed the .md5 file from samfirmware link via odin ...let it boot and settle....then flashed philz LM5 4.35 kernel for root...
then i changed my build.prop for lcd density and installed the xposed installer and xposed app settings etc...
no lag and no bootloop.
also uninstalled a couple of the german apps that came with the firmware.
looks good!!

I (luckily) resolved it by
pressing POWER BUTTON for about 5 seconds while on samsung splash screen bootloop...
or
reboot to recovery>>advance>>reboot to recovery(again)>>>reboot system now..
or
making nandroid backup and restoring it
Recognized Distributor™

I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis

I think bootlops are caused by the use of /preload partition for some .apk since JB rom like xxls7 that didn't use preload like RRv3 aren't affected by them.

Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2

zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Exactly, especially the 7 sec power button restart, almost 100% bootloop state.
Sent from my GT-N7000 using Tapatalk 2

pbirdas said:
I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis
Click to expand...
Click to collapse
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2

jaguaralani said:
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ohh...I see.. This is what is keeping me away of flashing the official ROM.. i will just wait for the issue to be found before i flash it.. Thanks for the info!!

Official JB is quite stable.. on XLSC (ultimate rom) my phone face sudden bootloop while it on my pocket, longest use on XLSC is 2 or 3 days before it bootloop by it self...only can be solve by restoring nandroid backup, something happen when I make force reboot or force shutdown...
But on XLSZ I only got bootloop on 1st reboot (after force reboot & force shutdown)....on 2nd reboot my phone will reboot normally..and never face suddent bootloop.. But yes bootloop bug is still there..
My XLSZ now is on:
+stock kernel
+rooted
+odexed/stock official
+some system apps is on preload partition
+no system/data restored by TB..
Sent from my GT-N7000 using Tapatalk 2

Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium

zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ok....so I tried both your methods of getting a boot loop.
1. After holding down power button till it came to the Sammy screen, it stuck there. I held power button down until screen went blank and let go....within a second phone came back on and rebooted normal.
2. Same as what happened in 1.
But this happened before where it would sometime get stuck at Sammy logo..in other versions of android and even inn my i9000 before....but it boot up fine after so no problems here.
Sent from my GT-N7000 using Tapatalk 2

ssss69 said:
Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for the info mate, this clearly shows that it is a Samsung problem.
Sent from my GT-N7000 using Tapatalk 2

Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Sent from my GT-N7000 using Tapatalk 2

jaguaralani said:
Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Click to expand...
Click to collapse
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.

I've never had bootlop with LS7 and LSA and LSZ only few bootlops with lsc but i do wipeing cash and dalvik and works again
Verstuurd van mijn GT-N7000 met Tapatalk

kopitalk said:
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.
Click to expand...
Click to collapse
Thanks for the info mate...

today I'm updating my friend phone from stock ICS DXLR5 to XLSZ (free of chrge) using PC ODIN..while on stock XLSZ kernel I make a force reboot on my friend phone and its stuck on N7000 logo and boot find after second reboot (without any wipe or restore) , same things happen to my phone to...after that flash new Philz XLSZ kernel on my phone & my phone too from stock recovery...and what is surprise me is my friend phone survive when I make a force reboot but my phone not...maybe its time to reflash, will report again..

I have faced this problem many times before and the only cure sometimes was to make a nandroid backup and restore it
but if the backup failed at the data partition that means the data is corrupted and you must wipe your data ...
but one solution for sure worked for me with all roms I've tried ... do not use the preload partition ....
I do not use it at all ... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.

Super Prince said:
... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.
Click to expand...
Click to collapse
Care to share how to do this?

Bootloader Loop problem

Hi, my phone acted weird today, been running custom room for over couple months without any problem, but then when i resart my phone today it got to the bootload screen and stuck there ever seen. I can able to go into custom recover and did a full wipe but nothing change, could anyone help me out? I have loki also. Using S4 ATT version.

Try wiping cache in your recovery

i did that, always do that after install a new rom, don't know why my phone is soft bricked now...

akahimaro said:
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
Click to expand...
Click to collapse
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.

xBeerdroiDx said:
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
Click to expand...
Click to collapse
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...

Before ODIN'ing back to MDL/MDB...
akahimaro said:
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Click to expand...
Click to collapse
What recovery image are you running? You are not the only one that had this problem. I am trying to piece this together.

Twrp backup

I have 2 backups that I have tried to restore while using twrp 3.0. No h seem like they restore but when the phone gets to the screen where it would eventually say Android after the animation never goes away and the phone doesn't boot all the way up. Has anyone else had this problem or know a solution. When I did my back ups I backed up everything available including vendor and vendor.img. I just continue to get a bootloop and phone doesn't boot. Thank u to anyone who may help

This happened to me as well even before trwp 3.0. It worked for me once I restored only boot, system, and data.

janedoesmith said:
This happened to me as well even before trwp 3.0. It worked for me once I restored only boot, system, and data.
Click to expand...
Click to collapse
Thanks. I think I tried this how you've said but I'll try again later as I need to make sure my phone is working for now.

Since day 1 I've always backed up boot, system and data. Not sure why anyone would ever back up anything else. Takes up too much space and is unnecessary. I've never had one issue. On all past devices (all Nexus) I've always backed up boot, data and system. New twrp is great! Now we can flash vendor images!! ?
Sent from my Nexus 6P using Tapatalk

Issues restoring backup

Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.

KLit75 said:
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
Click to expand...
Click to collapse
What partitions did you backup/restore?

Heisenberg said:
What partitions did you backup/restore?
Click to expand...
Click to collapse
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks

KLit75 said:
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
Click to expand...
Click to collapse
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.

Heisenberg said:
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Click to expand...
Click to collapse
So simple. Thanks a lot!

KLit75 said:
So simple. Thanks a lot!
Click to expand...
Click to collapse
Let me know if you get it booting.

Heisenberg said:
Let me know if you get it booting.
Click to expand...
Click to collapse
Well yes. Thanks again. However, I've got something funky going on. Pin pointing is hard but yea the backup restored. Then I tweaked elemental kernel (nothing crazy, used stable profiles) maybe it was that and an xposed mod (thinking ifont because its one I only just started using lt recently). Anyway when I rebooted to install drivers for viper I got stuck in bootloop. This time I couldn't restore my backup. So I factory reset and reflashed pure nexus. Due to the time I couldn't try and restore the backup again but will try tonight. If I wasn't so hasty I could've deleted the modules list in twrp then maybe booted up but I'm not 100% it has anything to do with xposed. One other factor, it was using dark stock theme.
EVERYTHING I mentioned I've done/run on this ROM without issues but there's a combination of things that's causing the bootloop I think.

Nandroid backup bootloop

Hi guys, little issue here with nandroid backups. I've been using the 6p since it's release and have tried about 5 different Roms. I like switching between them monthly or weekly, but every time I attempt a nandroid restore, I get a boot loop. Every time. I'm using twrp recovery, and when I go into backup, I just leave the default ones chosen, but I've even tried choosing all of them. The boot loop goes on for over 10 minutes before I power it down. I've tried wiping the phone, minus storage, I've tried restoring without wiping and both fail.
Can anyone here tell me what I might be doing wrong? I've looked around for guides but they all seem to work without issue for everyone.
Edit: maybe if someone can write me a simple guide on how to do a nandroid or link me to one in case I missed a step, although it seems pretty straight forward, I'd appreciate it

Robertdudeman said:
Hi guys, little issue here with nandroid backups. I've been using the 6p since it's release and have tried about 5 different Roms. I like switching between them monthly or weekly, but every time I attempt a nandroid restore, I get a boot loop. Every time. I'm using twrp recovery, and when I go into backup, I just leave the default ones chosen, but I've even tried choosing all of them. The boot loop goes on for over 10 minutes before I power it down. I've tried wiping the phone, minus storage, I've tried restoring without wiping and both fail.
Can anyone here tell me what I might be doing wrong? I've looked around for guides but they all seem to work without issue for everyone.
Edit: maybe if someone can write me a simple guide on how to do a nandroid or link me to one in case I missed a step, although it seems pretty straight forward, I'd appreciate it
Click to expand...
Click to collapse
All you need for a backup is system, data, and boot if that's what you're doing it might be you need to flash the vendor

I'm having this issue as well. Maybe we can work together to narrow it down. This happens every time and the only reason can currently think of is that I may need to remove the fingerprint and pin security before the backup. My question to you is, have you tried disabling lockscreen security before backing up?

Robertdudeman said:
Hi guys, little issue here with nandroid backups. I've been using the 6p since it's release and have tried about 5 different Roms. I like switching between them monthly or weekly, but every time I attempt a nandroid restore, I get a boot loop. Every time. I'm using twrp recovery, and when I go into backup, I just leave the default ones chosen, but I've even tried choosing all of them. The boot loop goes on for over 10 minutes before I power it down. I've tried wiping the phone, minus storage, I've tried restoring without wiping and both fail.
Can anyone here tell me what I might be doing wrong? I've looked around for guides but they all seem to work without issue for everyone.
Edit: maybe if someone can write me a simple guide on how to do a nandroid or link me to one in case I missed a step, although it seems pretty straight forward, I'd appreciate it
Click to expand...
Click to collapse
stryver said:
I'm having this issue as well. Maybe we can work together to narrow it down. This happens every time and the only reason can currently think of is that I may need to remove the fingerprint and pin security before the backup. My question to you is, have you tried disabling lockscreen security before backing up?
Click to expand...
Click to collapse
You're most likely selecting the wrong options when creating the backup. There's a section dedicated to nandroid backups in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

This helped a lot, thank you.