Hi,
I got my N7000 stuck in a bootloop. i did NOT flash any other rom not for the N7000. i was planning to flash the paranoidandroid rom and while shifting from ICS to GB [as it suggested] this happened.
I still have download and recovery modes. Flashing different stock roms is going through, and some custom kernels too [the yellow triangle appears after and the flash count increases]
trying to recovery from my nandroid backups gives the same result as the stock flashing
i.e. its goes through then get stuck in the boot screen before the animation [the screen which says Samsung Galaxy bla bla, the screen where the yellow triangle shows up to be clear]
What can i do now please??
thanks
edit: should i try to format /system /data /preload /emmc fom CWM recovery 5 becuase i can do that
So you flashed successfully gb? If you are on a gb and you have used a safe kernel to revert. Did you try to Wipe data and cache from recovery? Try it, it should bring you out of the boot loop.
Sent from my GT-N7000 using Tapatalk 2
Hi,
I don't know on what rom i am at the moment. it should be GB since i flashed SGN_XX_OXA_KJ1_FACTORYFS.tar
wiping data on the CWM worked before but this time it got stuck with out any progress in the blue bar for like 20min.
i was suggested to flash a wipe rom, but i dont know where to find one exactly
Like Baxos said. Try wipe all since you r at old GB. Its worked 4 for me. I've been at your stage then wipe all then root and flashed paranoidandroid. Try Get back to recovery and wipe all then reboot.
n7000 paranoid android v2
Will update to v3 when got time
wipe all = also formatting /system /data /preload /emmc fom CWM recovery 5?
because i did many of the restore to factory and clearing cache
the problem seems to be due to the fact that /data is not being wiped. the progress bar gets stuck and then reboots
any idea how i can wipe this partition?
Did you first install a safe gb kernel when you were on ics before downgrading the rom to gb? If not then you will have performed a wipe under ics kernel and it sounds like brick bug symptoms.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
jan-sgs said:
the problem seems to be due to the fact that /data is not being wiped. the progress bar gets stuck and then reboots
any idea how i can wipe this partition?
Click to expand...
Click to collapse
Maybe your /data is corrupted. You can make a new /data with adb.
hi,
sorry for the late reply. i was busy with uni work
i will try the adb method.
thanks
all partitons were wiped on a different rom version.
the boot loop seems to be irreparable and i will have to send it abroad to get it fixed. hopefully i dont have any of my data on it
Related
Guys, need help. I used this way way back (genokolar partition) http://forum.xda-developers.com/showthread.php?t=1112857 Im planning to go for ICS yesterday, i flash back the official partition, now my phone stuck at IDEOS logo. I tried wiping everything and reflash (tried MIUI,CM7,Elite SX still no luck). I use Miui before flashing the official partition. Im pretty sure i did what the step asked. Flash, no clear/wipe. Stuck at Ideos screen. Then i clear and wipe still the same. Then i go to the pink screen, restore back the original recovery and BOOT files, and flash back the official froyo, error at 2/2 update. I cant mount data in cmw. Tried factory reset in recovery but no luck, got error msg ( Mount data error ) using 4.0.0.5. I cant delete/wipe data.Keep giving me error mount data. Even in official recovery cant mount, got msg ( no such directories,Can't Mount @(or/dev/block/mmcblk0p13 ). Is this the problem ? How can i mount the data back?
heliozguard said:
Guys, need help. I used this way way back (genokolar partition) http://forum.xda-developers.com/showthread.php?t=1112857 Im planning to go for ICS yesterday, i flash back the official partition, now my phone stuck at IDEOS logo. I tried wiping everything and reflash (tried MIUI,CM7,Elite SX still no luck). I use Miui before flashing the official partition. Im pretty sure i did what the step asked. Flash, no clear/wipe. Stuck at Ideos screen. Then i clear and wipe still the same. Then i go to the pink screen, restore back the original recovery and BOOT files, and flash back the official froyo, error at 2/2 update. I cant mount data in cmw. Tried factory reset in recovery but no luck, got error msg ( Mount data error ) using 4.0.0.5. I cant delete/wipe data.Keep giving me error mount data. Even in official recovery cant mount, got msg ( no such directories,Can't Mount @(or/dev/block/mmcblk0p13 ). Is this the problem ? How can i mount the data back?
Click to expand...
Click to collapse
same problem with me
heliozguard said:
Guys, need help. I used this way way back (genokolar partition) http://forum.xda-developers.com/showthread.php?t=1112857 Im planning to go for ICS yesterday, i flash back the official partition, now my phone stuck at IDEOS logo. I tried wiping everything and reflash (tried MIUI,CM7,Elite SX still no luck). I use Miui before flashing the official partition. Im pretty sure i did what the step asked. Flash, no clear/wipe. Stuck at Ideos screen. Then i clear and wipe still the same. Then i go to the pink screen, restore back the original recovery and BOOT files, and flash back the official froyo, error at 2/2 update. I cant mount data in cmw. Tried factory reset in recovery but no luck, got error msg ( Mount data error ) using 4.0.0.5. I cant delete/wipe data.Keep giving me error mount data. Even in official recovery cant mount, got msg ( no such directories,Can't Mount @(or/dev/block/mmcblk0p13 ). Is this the problem ? How can i mount the data back?
Click to expand...
Click to collapse
Did you try official gb? You don't need froyo, it has wrong kernel for ics aurora.
cokratex said:
Did you try official gb? You don't need froyo, it has wrong kernel for ics aurora.
Click to expand...
Click to collapse
I did not, since i cant even pass the IDEOS logo on 2.2, If i flash 2.3 the bootloader is locked and if it still stuck at the same place what can i do ?
Flashed 2.3.5 official. Still the same keep reboot and phone tried to delete/wipe internal sdcard but fail. Format cache-->(failed to mount /data_pseudo )
Format data --> (make_extf4fs fail on /dev/block/mmcblk0p13). Pink screen wont show partition in computer anymore.
-Update-
I manage to make the pink screen partition shown in computer. Still same error /dev/block/mmcblk0p13. Im at the end of the rope. Rest time..
same problem in samsung galaxy fit..n also bootloop
my phone rebootng again n again..coming back from samsung logo..i think it is called bootloop..tried to install various roms again n again like creed 3.5 n razodroid..even stock..bt always saying cant mount data..n installation completed..then again stuck in bootloop..i cleared dalvic cache\data\system all..still no help
Please help.. been years... Still no luck. Cant mount sd or sd-ext now. Stuck in bootloop
heliozguard said:
Please help.. been years... Still no luck. Cant mount sd or sd-ext now. Stuck in bootloop
Click to expand...
Click to collapse
Can't mount sd? Go to recovery, take your sd out, and put it back in. If that works, you try flahing the custom partition again (not the original partition). After that, try flashing a rom.
Edit: but try to flash the original again first. Make sure you flash it, reboot recovery, flash it again, reboot recovery, and then flash your rom.
rqmok said:
Can't mount sd? Go to recovery, take your sd out, and put it back in. If that works, you try flahing the custom partition again (not the original partition). After that, try flashing a rom.
Edit: but try to flash the original again first. Make sure you flash it, reboot recovery, flash it again, reboot recovery, and then flash your rom.
Click to expand...
Click to collapse
I cant mount it in recovery. Both of the sd. And keep getting bootloops. Cant even hard reset with original image. Im trying this for now
http://forum.xda-developers.com/showthread.php?t=1971266 will update
Solved using this method thanks to OP http://forum.xda-developers.com/showthread.php?t=1971266
However still cant mount sd card both my sd card and internal sd. Internal sd show 0byte space..
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Trying install this rom:
http://forum.xda-developers.com/showthread.php?t=2494756
Went to CWM and started full wipe/reset and it got stuck on:
Formatting /cache
had to hard reboot with long press on power button then my stock room booted up, so means nothing formatted...
What to do next guys?
Thanks!
Install twrp, and in preferences check format method -r, fs. Somthing like this. Or wait longer, with standart formating it takes up to 20-30min!
Melodycd said:
Install twrp, and in preferences check format method -r, fs. Somthing like this. Or wait longer, with standart formating it takes up to 20-30min!
Click to expand...
Click to collapse
Why does the cache take forever to format on the G2?
ditto
same thing happened to me during a rom install
as i have only had the phone a week i was a bit flustered
i did what they recommended
went into twrp settings and checked <<use rm - rt>>
and then reinstalled the rom, reboot was ok this time
so far so good
yeah i have the same question about wiping cache - on my samsung note 2 using twrp it was so fast
This is a problem in twrp i think, i was using twrp on many devices before, but didn't have any problems with wipe.
first of all I'm sorry to create a new thread and it is different from other's problem.
first I'll tell what I have done.
flashed f2fs recovery by bugerXXX
formatted data, cache partitions to f2fs
flashed lineage os by harsh
rebooted to system & it was booted.
(no problem till here)
then I again rebooted to recovery
backup system& it just rebooted in the middle of the process
and that's it it never rebooting to system.
it always rebooting to splash screen infinite times when I try to power it on.
recovery works
fastboot works
download mode works
tried flashing different ROMs
reformatted data cache partitions to ext4
it always rebooting to splash screen infinite times.
even I flashed ROM (kk&lp) with QFIL and results are same.
but after flashed kk it completed boot animation and entered setup wizard, then again it started to rebooting
I think it has some problem with partitions or emmc
is there any thing that I can do to revive my phone?
senthamizhan said:
first of all I'm sorry to create a new thread and it is different from other's problem.
first I'll tell what I have done.
flashed f2fs recovery by bugerXXX
formatted data, cache partitions to f2fs
flashed lineage os by harsh
rebooted to system & it was booted.
(no problem till here)
then I again rebooted to recovery
backup system& it just rebooted in the middle of the process
and that's it it never rebooting to system.
it always rebooting to splash screen infinite times when I try to power it on.
recovery works
fastboot works
download mode works
tried flashing different ROMs
reformatted data cache partitions to ext4
it always rebooting to splash screen infinite times.
even I flashed ROM (kk&lp) with QFIL and results are same.
but after flashed kk it completed boot animation and entered setup wizard, then again it started to rebooting
I think it has some problem with partitions or emmc
is there any thing that I can do to revive my phone?
Click to expand...
Click to collapse
Revert back your partitions to ext4
Wipe them
Fix them using fix option
Flash lollipop stock ROM
And see if it boots up
And next time be sure to ask for help before doing anything so that you don't end up like this
And contact me if it does not help
Don't forget to fix partitions
still same problem
The Hard Gamer said:
Revert back your partitions to ext4
Wipe them
Fix them using fix option
Flash lollipop stock ROM
And see if it boots up
And next time be sure to ask for help before doing anything so that you don't end up like this
And contact me if it does not help
Don't forget to fix partitions
Click to expand...
Click to collapse
you mean " repair file system " in twrp??
I have formatted system, data, cache to ext4
and repaired them using "repair file system" in twrp
flashed s061 stock ROM
but the problem still present.
and I wanna know what is " validated_emmc_firehouse_8916.mbn". can I use it instead of "prog_emmc_firehouse_8916.mbn" in QFIL ??
senthamizhan said:
you mean " repair file system " in twrp??
I have formatted system, data, cache to ext4
and repaired them using "repair file system" in twrp
flashed s061 stock ROM
but the problem still present.
and I wanna know what is " validated_emmc_firehouse_8916.mbn". can I use it instead of "prog_emmc_firehouse_8916.mbn" in QFIL ??
Click to expand...
Click to collapse
The sequence of flashing files is written in scatter file so even of you change the file and it is not meant to be flashed it won't flash
I don't think there might be a hardware fault
i am also suffering from this same problem
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
skorpien said:
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
ashyx said:
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
Click to expand...
Click to collapse
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
skorpien said:
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
Click to expand...
Click to collapse
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
ashyx said:
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
Click to expand...
Click to collapse
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
skorpien said:
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
Click to expand...
Click to collapse
Did you back up the efs partition with twrp?
If so try restoring it.
ashyx said:
Did you back up the efs partition with twrp?
If so try restoring it.
Click to expand...
Click to collapse
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
skorpien said:
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
Click to expand...
Click to collapse
Don't restore everything just EFS No need to keep wiping dalvik it serves no purpose when formatting or wiping the data partition.
Also FORMAT not wipe the data partition (note this wipes internal storage)
If it still doesn't boot install the combo firmware. Let it boot, factory reset from settings then reboot to download mode and install the stock firmware again.