Develop Bugs

Galaxy Y Animation bootloop help

I followed all the instructions in the stock rooting post of Doky37 (done it 3 x) and my problem is I keep getting a bootloop . I tried wiping the cache, wiping/restoring the factory setting, etc. but I still get the boot loop everytime I turn on the phone.
I took a picture of the screen just before the loop and noticed that it says it cannot mount the data (??) . ANy idea on what I should do?

Do this
spiderworld said:
I followed all the instructions in the stock rooting post of Doky37 (done it 3 x) and my problem is I keep getting a bootloop . I tried wiping the cache, wiping/restoring the factory setting, etc. but I still get the boot loop everytime I turn on the phone.
I took a picture of the screen just before the loop and noticed that it says it cannot mount the data (??) . ANy idea on what I should do?
Click to expand...
Click to collapse
Follow this video carefully..check out the description for the proper steps and download link...u r in stock rom right???
http://www.youtube.com/watch?v=R_0l9zscf0o&context=C3442e2bADOEgsToPDskKPIKjoeGf8tXrCn-BjSOtZ
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
spiderworld said:
I followed all the instructions in the stock rooting post of Doky37 (done it 3 x) and my problem is I keep getting a bootloop . I tried wiping the cache, wiping/restoring the factory setting, etc. but I still get the boot loop everytime I turn on the phone.
I took a picture of the screen just before the loop and noticed that it says it cannot mount the data (??) . ANy idea on what I should do?
Click to expand...
Click to collapse
make sure u have kies installed before flashing

I followed the instruction and it still bootloops.
Yes I am in stock ROM.

Do you mean I should have KIes running in the background when I Flash using Odin? or just installed but not running?

spiderworld said:
Do you mean I should have KIes running in the background when I Flash using Odin? or just installed but not running?
Click to expand...
Click to collapse
u must have installed kies before
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
spiderworld said:
I followed the instruction and it still bootloops.
Yes I am in stock ROM.
Click to expand...
Click to collapse
while it is in boot now,take the battery off..put it on again..recovery mode..wipe data.reboot..

Yes Kies is installed. Odin is working and I can flash the phone but after flashing I get the boot loop.
I am thinking there might be wrong with the internal memory

spiderworld said:
Yes Kies is installed. Odin is working and I can flash the phone but after flashing I get the boot loop.
I am thinking there might be wrong with the internal memory
Click to expand...
Click to collapse
while the phone is stuck in the samsung screen take out battery,put it in again,recovery mode and data wipe,,this has worked for many

aadaars said:
while the phone is stuck in the samsung screen take out battery,put it in again,recovery mode and data wipe,,this has worked for many
Click to expand...
Click to collapse
yes I have tried removing the battery, wait a few minutes, replace battery, power up in recovery mode, wipe data, re boot, then it goes back to boot loop.

spiderworld said:
I followed the instruction and it still bootloops.
Yes I am in stock ROM.
Click to expand...
Click to collapse
Do you remember, what version you had before?

flash it in odin to fix...it happens to my phone too...and the recovery menu bootloop too...

Found some corruption in S5360_DDLA3_ODDLA2_DDLA2_by_Doky.zip's CSC part. I've removed the full pack, uploading a CSC update, and a repaired full package as well.

Doky73 said:
Found some corruption in S5360_DDLA3_ODDLA2_DDLA2_by_Doky.zip's CSC part. I've removed the full pack, uploading a CSC update, and a repaired full package as well.
Click to expand...
Click to collapse
Okay sir,when u uploading...M using that nw and found it to be quite good...
There were slight problems with the touch while the battery was charging thats it

I went to the Samsung repair center and brought the phone
they re flashed with a PIT, bootloader, CSC, PDA tar files. it booted up after that but the ginger bread version is now back to 2.3.5 (it used to be 2.3.6}
I an planning to update it back to 2.3.6 and flash with stock ROM LA2.

i'm having the same problem.
I read this thread and wanted to try something. I just added a line at-last ro.com.android.dateformat=dd-MM-yyyy and rebooted.
Then happens the boot loop.
I tried wipe/factory reset. no use
I tried flash with Odin, and it says
Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/003> Added!!
What am i supposed to do..?
I recently updated my firmware using Kies

Neva mind..
I just flashed with XXLA2 and got back into galaxy...

follow this for "can't mount data. format failed on :/dev/stl11" or something like that.
http://androidadvices.com/samsung-g...cial-global-gingerbread-ddla1-236-firmware/2/

My note2 is SuperBrick.Help me

My note 2 --> superbrick (loop in logo, can enter download mode, can't enter recovery mode). I try repartition with N7100.pit by odin 3.07 but no pass (show messeage Get Pit Map and stop). please help me :crying:

Use a USB Jig?
How can you try something with Odin if you have no download mode?

Raphy511 said:
Use a USB Jig?
How can you try something with Odin if you have no download mode?
Click to expand...
Click to collapse
thank.i have download mode but no recovery mode.

kittipo said:
My note 2 --> superbrick (loop in logo, can enter download mode, can't enter recovery mode). I try repartition with N7100.pit by odin 3.07 but no pass (show messeage Get Pit Map and stop). please help me :crying:
Click to expand...
Click to collapse
First you have to give more detail what did you do before you got stuck at boot loop. So someone will know more about your situation .
Now try hold home button for awhile to see note can boot back to normal.

Have you tried flashing any stock roms with Odin?
Sent from my GT-N7100 using xda premium

I try install any rom but not work. After install rom It reboot and show robot logo and install bar then mobil autoreboot --> show samsung logo then show robot logo and autoboot show robot again and again

Hmm.. Did you tried flashing a kernel with CWM in Odin, and from CWM Wipe Data, Wipe Cache, Wipe Dalvik Cache, then download mode and reflash stock image?

kittipo said:
My note 2 --> superbrick (loop in logo, can enter download mode, can't enter recovery mode). I try repartition with N7100.pit by odin 3.07 but no pass (show messeage Get Pit Map and stop). please help me :crying:
Click to expand...
Click to collapse
This may help .
http://forum.xda-developers.com/showthread.php?t=1932327

ionutzm05 said:
Hmm.. Did you tried flashing a kernel with CWM in Odin, and from CWM Wipe Data, Wipe Cache, Wipe Dalvik Cache, then download mode and reflash stock image?
Click to expand...
Click to collapse
Yes. I am try flash cwm in odin.After flash cmw it autoreboot show samsung logo and show Slash cwm logo not enter menu and autoreboot come to samsung logo again and show cwm agian and loop samsung logo agian and again

If you want ANY chance of someone being able to help you, you need to post EXACTLY what you did to your device, including telling us EXACTLY what ROMs you flashed with links to the ROM threads.
No one here can help you unless they know what you did in the first place.

FloatingFatMan said:
If you want ANY chance of someone being able to help you, you need to post EXACTLY what you did to your device, including telling us EXACTLY what ROMs you flashed with links to the ROM threads.
No one here can help you unless they know what you did in the first place.
Click to expand...
Click to collapse
I sorry but I don't know to expian. I think it cause I try recovery system staus is show custom by try flash stock rom I download from sammobile. Switch between stock rom and not wipe data and not reset factory reset.???

Good grief...
kittipo said:
I sorry but I don't know to expian. I think it cause I try recovery system staus is show custom by try flash stock rom I download from sammobile. Switch between stock rom and not wipe data and not reset factory reset.???
Click to expand...
Click to collapse
OK, so what did you do after getting your new device? What ROM version did you start off with. Did you install any OTA updates? What rooting method did you use? What recovery were you using? What version of TriangleAway did you use? What ROM did you flash? What ROM did you download from Sammobile? Did you use ODIN? If yes, what version did you use?
Geez dude... If you don't know what you did, how can you expect people to help you? No one here is psychic you know.

kittipo said:
I sorry but I don't know to expian. I think it cause I try recovery system staus is show custom by try flash stock rom I download from sammobile. Switch between stock rom and not wipe data and not reset factory reset.???
Click to expand...
Click to collapse
I am not complain about anything ,but have you read this post kittipo ?
http://forum.xda-developers.com/showthread.php?t=1932327
It seem to be your solution.

goddamnit said:
I am not complain about anything ,but have you read this post kittipo ?
http://forum.xda-developers.com/showthread.php?t=1932327
It seem to be your solution.
Click to expand...
Click to collapse
Yes. I am try 2 time. but not work.after boot in show robot logo and autoboot loop. switch between samsung and robot.
Sorry for answer your late because i just come home (I drive my car faster for come back home and answer you)
My rom data in my computer. long story for my note2. (sorry for my english. i am thai people)
I remember first I try install triangle away again and again for reset system status custom or modify but not work it still custom (some people in xda tell me try install and reset will work for reset system status) In the end I give up for system status.
But yesterday I enter menu setting again and i found my system status show normal. I try enter boot menu and show system status official. when i come back restart normal mode my system status show modify and custom. I so confuse. Why ? I want to answer.(Because I try many time but not work)
that I try install stock rom again and again. I found --> I use triangle away and reset by menu setting or reset by enter recovery mode and After first normal boot if I use connect samsung account , google account (and setup uncheck autoupdate befor restore data done -- now system status still custom) for restore my data when finish I delete some wiget. Slash samsung will occur and system status will change custom to normal and Bootloader status show official. But if you not connect restore from samsung and google accout --> system status will still custom ( That answer me why not success before because I not restore my data in first boot).
I think I close to answer for How I can change system status and come back update OTA.
In last I remember I flash stock rom N7100XXALIE_N7100OLBALI9_N7100DXALI9_HOME.tar.md5. After flash rom I change system status to normal and try update OTA by normal process that work I can update OTA Rom update to 1 step but not current Rom (From Old rom --> Current Rom must update 2-3 time ) After update it reboot everything fine by system come back modify again and can't update OTA.
I search in web xda for answer. Someone tell because program can detect SuperSu and Su program.I try change system status again to official. and After that I reboot enter bootloader mode (system status now official) and reflash by N7100XXALJ3_N7100OLBALJ3_N7100DXALJ1_HOME.tar after that my note2 autoreboot ( I think that begin i am not sure) .That all my remember.

kittipo said:
Yes. I am try 2 time. but not work.after boot in show robot logo and autoboot loop. switch between samsung and robot.
N7100XXALJ3_N7100OLBALJ3_N7100DXALJ1_HOME.tar after that my note2 autoreboot ( I think that begin i am not sure) .That all my remember.
Click to expand...
Click to collapse
From your post ,I think you want to keep root ,and OTA at the same time ?
Okay ,leave your phone unroot ,and everything stock ,then enjoy OTA
Since the first day you root your Note 2 .
forget OTA ,OTA is **** .Odin is god .
Do everything with odin is fine .
Unless you want to return your phone to samsung .
There is no method to keep root ,and OTA right now

I search Super brick. it must use repartition by pit file for repair. I load Pit file from xda by this column http://forum.xda-developers.com/showthread.php?t=1896696 N7100.pit
I try use pit file with Odin 3.04 or Odin 3.07. But odin show
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
and stop.
I have question -->pit file can repair my problem?

goddamnit said:
From your post ,I think you want to keep root ,and OTA at the same time ?
Okay ,leave your phone unroot ,and everything stock ,then enjoy OTA
Since the first day you root your Note 2 .
forget OTA ,OTA is **** .Odin is god .
Do everything with odin is fine .
Unless you want to return your phone to samsung .
There is no method to keep root ,and OTA right now
Click to expand...
Click to collapse
Thank you very mush. Ok Now I never mind root or unroot or OTA.But I want to my note come back to normal use. Do you have anyway? please tell me.

kittipo said:
I search Super brick. it must use repartition by pit file for repair. I load Pit file from xda by this column http://forum.xda-developers.com/showthread.php?t=1896696 N7100.pit
I try use pit file with Odin 3.04 or Odin 3.07. But odin show
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
and stop.
I have question -->pit file can repair my problem?
Click to expand...
Click to collapse
Pit file is NOT for you.
Say ,if you flash 16G pit to 32G phone ,you will get 16G leave .
Nothing related .
(I try to use English like Thai .. I'm hongkong ppl XD)
---------- Post added at 11:59 PM ---------- Previous post was at 11:53 PM ----------
kittipo said:
Thank you very mush. Ok Now I never mind root or unroot or OTA.But I want to my note come back to normal use. Do you have anyway? please tell me.
Click to expand...
Click to collapse
1 : Your phone is not super brick
2 : Re-Partition is not for you ,too .We will tell user "DO NOT" tick it ..
You may check this two therad first .
Dr.ketan
http://forum.xda-developers.com/showthread.php?t=1896696
Chainfie
http://forum.xda-developers.com/showthread.php?t=1933542

I try flash stock rom from http://forum.xda-developers.com/showthread.php?t=1896696
I download N7100XXALIE_N7100OLBALI9_N7100DXALI9_HOME.tar --> not work stay loop between samsung and robot logo
try N7100XXALJ3_N7100OLBALJ3_N7100DXALJ1_HOME .tar --> same
try N7100ZSALIA_N7100OZSALIA_N7100XXALIE_ROOT_DEODEX from column http://forum.xda-developers.com/showthread.php?t=1915386
--> much error problem show. I correct and come back N7100XXALJ3_N7100OLBALJ3_N7100DXALJ1_HOME .tar but have old problem (still loop)

kittipo said:
--> much error problem show. I correct and come back N7100XXALJ3_N7100OLBALJ3_N7100DXALJ1_HOME .tar but have old problem (still loop)
Click to expand...
Click to collapse
check this
http://forum.xda-developers.com/showpost.php?p=33405902&postcount=64

[Q] At&t S3 Sudden Bootloop / Can't flash

Alright folks, here's what I've got:
An S3, which is rooted, using TWRP for recovery and on a CM11 nightly. This had been running happily with no problems since February.
About a week ago, it began randomly shutting down / restarting for no apparent reason. It would do this maybe once a day.
Two days ago, it did this again while I was surfing the internet, but then proceeded into a boot loop and now will not start up at all. It shows the Samsung screen, then the Galaxy S3 screen, then stops and loops on the CM animated screen. As far as I know I didn't do anything to trigger this - no new app downloads, no new ROM flashing, etc - it just did it suddenly in use.
I can successfully get into both download mode and recovery and the phone will stay there (so I don't think this is the power button issue), but I can't do anything useful from either mode. In TWRP I get error messages regarding failure to mount cache regardless of what I do. I can't do a factory reset or wipe it, and can't flash anything.
It will connect to Odin in Download mode, but anything I have tried there comes up "Fail", or "Complete - Write Operation Failed". Can't flash back to stock, can't flash CM again. I've tried a couple different cables and different USB ports, and reinstalling the drivers. The computer in question, which has worked with Odin before, is running Win 8.
I'm at the end of what I know to do to this thing, and am beginning to suspect it has a hardware problem. Any thoughts or things to try?

I'm in a similar boat as you :
I flashed a ROM, it was working w/o issue for 3 days then all of a sudden when I launched an app on my phone (don't recall which one, but one I used regularly), the phone rebooted and was stuck at the loading screen.
TWRP couldn't mount ANY partition either..
Here is my story...
http://forum.xda-developers.com/showthread.php?t=2725985
It's either a coincidental hardware failure or something weird is going on with the custom ROMS.

the.teejster said:
I'm in a similar boat as you :
I flashed a ROM, it was working w/o issue for 3 days then all of a sudden when I launched an app on my phone (don't recall which one, but one I used regularly), the phone rebooted and was stuck at the loading screen.
TWRP couldn't mount ANY partition either..
Here is my story...
http://forum.xda-developers.com/showthread.php?t=2725985
It's either a coincidental hardware failure or something weird is going on with the custom ROMS.
Click to expand...
Click to collapse
This does sound like a similar issue. However, since I had been running the same ROM for almost 2 months with no problems, I thought I was safe from ROM-related issues.....
I've now tried a couple different versions of Odin and they all fail, though 1.85 gives me more info (much like you saw).

Have you tried removing sim card and sd card from the phone before going into download mode and plugging to computer? I did this when I almost bricked my phone and I was able to flash factory firmware with Odin 3.07. From now on, I'm staying away from any Nightly build...

Nico3d3 said:
Have you tried removing sim card and sd card from the phone before going into download mode and plugging to computer? I did this when I almost bricked my phone and I was able to flash factory firmware with Odin 3.07. From now on, I'm staying away from any Nightly build...
Click to expand...
Click to collapse
Yep, I tried pulling the SIM and SD card. No change in behavior either with or without.

If you are not running a stock 4.3 bootloader, could try using Odin to flash a stock ROM from sammobile.com. If you have the 4.3 bootloader, this could be causing the failed flash. What is the screen info when your phone is on download mode?
Have you tried using Philz Touch to flash?

audit13 said:
If you are not running a stock 4.3 bootloader, could try using Odin to flash a stock ROM from sammobile.com. If you have the 4.3 bootloader, this could be causing the failed flash. What is the screen info when your phone is on download mode?
Have you tried using Philz Touch to flash?
Click to expand...
Click to collapse
Download screen is currently showing:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 2
I've tried to get Philz on the phone and that fails, as did trying to flash stock from sammobile. I'm getting a write failure in Odin.

Also just tried to install Philz from within TWRP.
This goes through and says "Successful", but then ends with:
Updating partition details
E: Unable to mount '/cache'
Selecting Wipe Cache/Dalvik results in:
Failed
Formatting Cache using make_ext4fs function.
E:Unable to mount 'cache'
Updating partition details
E: Unable to mount 'cache'

Use Odin to install Philz rather than twrp.

audit13 said:
Use Odin to install Philz rather than twrp.
Click to expand...
Click to collapse
Attempting in Odin gets me:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection
<ID:0/005> Initialization..
<ID:/005> Gt PIT for mapping..
<ID:/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1).
Grr....

Try flashing Philz for the d2att instead and see what happens. I have used the d2att and d2lte version on my Canadian Bell i747m.

I've never encountered this before and I really need help... Device will not wipe!

I am not new to rooting and flashing roms but this has really stumped me. I'm on a rooted sprint note 4. I'm running the Bonsai stock rom with TWRP recovery. I absolutely cannot factory reset or wipe or even format from recovery anymore. No matter what I do. It appears to wipe but the current rom loads back anyway. I am totally perplexed. Only thing I can think of is maybe a virus. Has gotten a hold. Any help would be most appreciated.

I'm not fully clear on what you're saying. Sound like you can get into recovery, but no of the wipe functions of TWRP are working.
Was TWRP working before? If so, than maybe something you flashed corrputed the custom recovery. I two suggestions. 1) reflash TRWP via Odin. That may fix the custom recovery, without wiping the phone. If that doesn't work, 2) Odin the stock tar file so that phone is just like when you got it, excpet knox counter tripped; this is already tripped so it's not causing anything new. Then just reflash via Odian CF-autoroot and TWRP. Something you just have to start to from step one. Hopefully, you either have a nandroid or backed up your apps via Titanium Backup.

Thanks you lovekeiiy for replying. Just to be clear I CAN get into TWRP. It appears to be working but it's not really doing anything. It runs through the scripts but it's not actually changing anything. Also when I'm am fully booted I can deleteprograms and cchange things around... Then reboot and everything comes right back like I never changed anything.

I agree. Flash recovery again, try wiping, let us know if that works.

I think I'm screwed. I downloaded the Original Stock Tar from Samsung. I first tried to reinitialize with Kies but that failed. So then I tried to ODIN the stock tar and that fails (see below). I can still use the phone...I can normal boot right back into the current rom as if nothing changed. But I cannot wipe this damn thing. Nor can I format or load a different rom! I have no idea what to do next.
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

Also I can't re-flash the recovery cuz that fails too.

Might have to Odin to stock and start over. ?

No you don't understand. I can't Odin anything. When I try to flash the stock rom through Odin it fails. It's like this thing is write protected somehow. I am really at a loss here. I'm thinking of returning it to Sprint and take my chances gettig a rooted phone replaced or repaired unless someone can suggest something.

Just a thought, can you try Odin with the SD card and the Sim card removed?
Try a different PC, and good USB data cable! Can you un-root with super su? Then cf auto root Odin? Sometimes it is just the order of processes that can make it work or fail.

SS_DL.dll -->desktop
Romun yanındaki SS_DL.dll dosyasını desktop a atın

I tried to uproot with SU. It just doesn't matter what I do the rom loads right back up. It's as if nothing can be written to the system. Also I noticed when I enter recovery I am getting "recovery not seandroid enforcing".
Do you think if I take this to Sprint and ask them to factory reset they would do it? It's bizarre because something has got to be able to format this thing. Like a low level format or something.

Try going to this page, download the stock kernel zip and flash in twrp. Maybe then you can wipe is stock recovery. If that works, see if you can then flash twrp again.
http://shabbypenguin.com/?developer=Sprint_Note_4-trltespr&folder=Stock-NIE
---------- Post added at 03:04 PM ---------- Previous post was at 02:56 PM ----------
You can also go here, download twrp img file and flash with flashy in your rom. http://www.techerrata.com/browse/twrp2/trltespr

Thank you for the suggestion but Odin fails everytime. Here is the error I get on the phone: MMC: mmc_write fail It seems that the partition is write protected somehow. There must be a way to change this! I am really out of options here. Has anyone have any experience with write failures?

I didn't say to use odin in either of my suggestions. Within twrp you can flash the stock recovery and reboot recovery should bring you back to stock recovery so you can wipe and factory reset. If that doesn't work use flashy from the play store to flash twrp img within the rim.

dschachm said:
I didn't say to use odin in either of my suggestions. Within twrp you can flash the stock recovery and reboot recovery should bring you back to stock recovery so you can wipe and factory reset. If that doesn't work use flashy from the play store to flash twrp img within the rim.
Click to expand...
Click to collapse
I am sorry for misunderstanding you. It won't work from the recovery either. The reason is, that I cannot write to whatever partition needs to be written to, to delete or modify. I cannot wipe this device no matter what I have tried. When I flash an .img with Flashify or TWRP or ROM TOOLBOX or even ODIN it appears to flash but sends me right back to TWRP recovery with a message saying: recovery not seandroid enforcing. The area that I need to write to needs to be formatted or repaired but I don't know how or even what program to do this with. I cannot believe that there isn't a way to totally re-format and re-partition like a low level format. The weird thing is that I can still totally use the phone. It's just that if I re-boot it, it returns to the state it was in when the problem started. This means if I add a program or delete a program or change anything, it will all revert back to how it is now after a re-boot.
Does anybody know of a way to completely reformat?? I hope this brand new Note 4 is not toast

If you have xposed installed, go to wanam, security hacks and select disable SEandroid. After reboot try flashy to flash twrp and the see if wiping works.

dschachm said:
If you have xposed installed, go to wanam, security hacks and select disable SEandroid. After reboot try flashy to flash twrp and the see if wiping works.
Click to expand...
Click to collapse
Thanks but that doesn't work. All it does is reboot me back to my current state (without the Winam hacks). I need something to re-partition or format from outside of the OS. That's why I thought ODIN would be the answer but it too can't write. I get eMMC_write fail. How do I fix that?

You need the pit file to flash with the stock tar so it reparations the phone. Not sure there is one yet. Pm shabby and see if he can get you it.

dschachm said:
You need the pit file to flash with the stock tar so it reparations the phone. Not sure there is one yet. Pm shabby and see if he can get you it.
Click to expand...
Click to collapse
Yes. The PIT file. I bet that will re-partition it. I will try to PM him. I know there isn't PIT yet.

Um How do I find Shabby?? Is "Shabby" his username?

Help, caught it boot loop

While attempting to root my galaxy note 4 I somehow managed to get caught it a boot loop when trying to revert to a rooted stock room please help

Double check the ROM you're trying to flash, if it is the correct one for your device.
Sent from my GT-I9505 using XDA Free mobile app

yilun said:
Double check the ROM you're trying to flash, if it is the correct one for your device.
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Before the boot loop odin failed on me while trying to flash N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5

LeoPRide said:
Before the boot loop odin failed on me while trying to flash N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5
Click to expand...
Click to collapse
Most likely can't flash that unlocked bootloader from a reactivation locked bootloader. What is your current bootloader? Most likely not OB7 because it's blocked to Odin.
Try to restore the last TWRP backup that ran after last update. No current backup, you need to Odin a tar. Maybe Noterized ROM will flash.
If you want to figure out which tar you can flash in Odin, Odin TWRP with no auto reboot and battery/USB pull for 30 seconds when done. Copy your TWRP log to sdcard and read it. Near the bottom it will tell your current bootloader. Flash that tar if you're stuck on boot loop.
I hope you didn't enable the reactivation lock in Settings/Security. That should be disabled prior to Odin flash. There's also an OEM unlock in Odin 3.10 series. You should use that but I'm not saying it bypasses the failure to disable reactivation lock. May have to call Sprint if that happened. It's anybody's guess if they can override that.
Sent from my SM-N910P using Tapatalk

Ive learned in the last 30 hours I have been fighting with rooting my friends 910p. I also have the note 4 910p and failed to realize he had updated to og5 (5.1.1 if I understand correctly.) Well I tried flashing the same way I did my phone using CF auto root and flashing Noterized Stable 3. Didn't even get through auto root and been looking for this boot loop fix since then. Tried flashing stock og5 and it didn't help. Also tried beastmode kernal with twrp. TWRP works fine and once out of about 35 flashes let me make it to android setup. Halfway though, it rebooted into boot loop. I've only tried Hybrid-X rom and a stock og5 .tar and it hasn't work. I'm about to try and figure out which boot loader I am working with (see previous posters statement saying "Most likely can't flash that unlocked boot loader from a reactivation locked boot loader. What is your current boot loader? Most likely not OB7 because it's blocked to Odin.") and try and match a stock file. After that ill be trying Sacs rom and what a previous poster in this page had said. Sounds like we are dealing with the same demon so I will update you if I make any progress with those ideas. Sorry for mispellings and if I dont make sense. I promised him Id have it figured out and im exhausted from up all night and then working. (side note I broke the laptop screen halfway diagnal across, because I somehow got the phone battery between the screen and keyboard hauling it home from work. If you fix your boot loop issue please post how :highfive: :fingers-crossed:
Also I left my friend the backing up process (he came to me wanting this because of mine.) and he only backed up photos, google, and contacts. I've been surfing this forum off and on for years (since my first smart phone Samsung Moment) for the knowledge you guys have that goes with my love of android. Hope to become a helpful active member.
Edit: I just seen a main difference where you failed odin and mine passes. Not sure if that matters.

store2426gm said:
Ive learned in the last 30 hours I have been fighting with rooting my friends 910p. I also have the note 4 910p and failed to realize he had updated to og5 (5.1.1 if I understand correctly.) Well I tried flashing the same way I did my phone using CF auto root and flashing Noterized Stable 3. Didn't even get through auto root and been looking for this boot loop fix since then. Tried flashing stock og5 and it didn't help. Also tried beastmode kernal with twrp. TWRP works fine and once out of about 35 flashes let me make it to android setup. Halfway though, it rebooted into boot loop. I've only tried Hybrid-X rom and a stock og5 .tar and it hasn't work. I'm about to try and figure out which boot loader I am working with (see previous posters statement saying "Most likely can't flash that unlocked boot loader from a reactivation locked boot loader. What is your current boot loader? Most likely not OB7 because it's blocked to Odin.") and try and match a stock file. After that ill be trying Sacs rom and what a previous poster in this page had said. Sounds like we are dealing with the same demon so I will update you if I make any progress with those ideas. Sorry for mispellings and if I dont make sense. I promised him Id have it figured out and im exhausted from up all night and then working. (side note I broke the laptop screen halfway diagnal across, because I somehow got the phone battery between the screen and keyboard hauling it home from work. If you fix your boot loop issue please post how :highfive: :fingers-crossed:
Also I left my friend the backing up process (he came to me wanting this because of mine.) and he only backed up photos, google, and contacts. I've been surfing this forum off and on for years (since my first smart phone Samsung Moment) for the knowledge you guys have that goes with my love of android. Hope to become a helpful active member.
Edit: I just seen a main difference where you failed odin and mine passes. Not sure if that matters.
Click to expand...
Click to collapse
First flash with CFAutoRoot will boot loop due to not using the kernel exploit and SuperSU zip (rooting stock? Just Odin of TWRP and pre-rooted Hybrid X would have been for OG5 stock).
2nd attempt with TWRP and Beastmode should have included the SuperSU zip prior to boot. But I don't think that should cause a boot loop.
If Odin isn't failing but you're getting boot loops, try installing CWM. It seems that if TWRP gets crashed on the reactivation bootloader, it no longer works to recover with a successful flash.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
I suspect that is the case with both phones in this thread.
Sent from my SM-N910P using Tapatalk

So flash a stock og5 file then reboot and wipe dalv and then use oden to flash cwm. After that flash a custom rom that's og5? This correct? Is there an easier way with having a non loading rom and TWRP on there now? Main thing I feel hurt this root was it was 5.1.1 and I didn't realize that.
Thank you for the fast replies!

store2426gm said:
So flash a stock og5 file then reboot and wipe dalv and then use oden to flash cwm. After that flash a custom rom that's og5? This correct? Is there an easier way with having a non loading rom and TWRP on there now? Main thing I feel hurt this root was it was 5.1.1 and I didn't realize that.
Thank you for the fast replies!
Click to expand...
Click to collapse
You can try just Odin CWM and flash the pre-rooted OG5 ROM. The ROM likely does most of the wiping for you if it's Hybrid X.
That should be enough. If not, format data partition and Odin OG5 tar and CWM then the pre-rooted ROM.
Sent from my SM-N910P using Tapatalk

It went all the way through the installer for the Hybrid 3.0 rom. After reboot it black screens with blue LED fading in and out. CWM worked amazingly!! Should I try and figure out the steps to find what boot loader its stuck on? Maybe it tried to take the 5.0.1 version and it stuck???
Progress baby, progress

store2426gm said:
It went all the way through the installer for the Hybrid 3.0 rom. After reboot it black screens with blue LED fading in and out. CWM worked amazingly!! Should I try and figure out the steps to find what boot loader its stuck on? Maybe it tried to take the 5.0.1 version and it stuck???
Progress baby, progress
Click to expand...
Click to collapse
I'm not familiar with Hybrid X 3.0 The Sprint yellow splash with blinking blue LED was common for many TW OB7 ROMs. IDK, that may been an indication it's installing the deodex ROM prior to optimizing and starting apps which would pop-up a notification screen.
Maybe let it sit 10 minutes or more and see if it updates the status? As long as the blue LED is blinking and phone doesn't vibrate and go off or loop, that may be acceptable if it actually completes the install.
Sent from my SM-N910P using Tapatalk

So while waiting on the black screen and blue led I fell asleep. still didnt work. Re downloading a good og5 tar to try and flash again. Also I am still struggling to figure out how to find which bootloader its on. Would it hurt to try flashing a 5.0.1 rom? Ill be giving him my sphone to use until I get this fixed. Hate to do that because I need my phone but it isnt his fault.
Also I have changed to odin 3.10.7 and it failed last try. It may have been my settings on odin though.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> carrier.img.ext4
<ID:0/004> RTN for Sprint
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
OP, is any of this helping? I dont mean to hijack your thread but figured we could work through it together. Otherwise if you like I can get my own thread going because this is a pain in the butt...... lol

store2426gm said:
So while waiting on the black screen and blue led I fell asleep. still didnt work. Re downloading a good og5 tar to try and flash again. Also I am still struggling to figure out how to find which bootloader its on. Would it hurt to try flashing a 5.0.1 rom? Ill be giving him my sphone to use until I get this fixed. Hate to do that because I need my phone but it isnt his fault.
Also I have changed to odin 3.10.7 and it failed last try. It may have been my settings on odin though.
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Erase...
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
persist.img.ext4
modem.bin
cache.img.ext4
carrier.img.ext4
RTN for Sprint
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
OP, is any of this helping? I dont mean to hijack your thread but figured we could work through it together. Otherwise if you like I can get my own thread going because this is a pain in the butt...... lol
Click to expand...
Click to collapse
Did you have the OEM unlock checked in Odin options? Was this OG5 tar?
Try to Odin the stock kernel first. Then try to recover with KIES. Odin or KIES might work after flashing the kernel, modem and recovery separately. It's risky doing it with OB7 individual Odin flashes but I believe it was done successfully on an OE1 update that crashed the reactivation locked bootloader. The gap may have been plugged on OG5.
IDK if CWM has a log like TWRP does. I can see the partitions by version in TWRP log written to sdcard.
You may also try just flashing an OG5 ROM or Noterized.
Edit: I no longer see OEM unlock in Odin 3.10.7; not sure which version had that or just bad recall; sorry for the bad info.
Sent from my SM-N910P using Tapatalk

So this is the stock file I been flashing.
ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar
Is that correct? I am not sure what modem or anything from before. I know it was the 5.1.1 and he updated earlier Aug. Is there a way to find out? Also I am still able to access and install twrp or cwm, use odin to flash tar files so I am not completely screwed yet. I am not used to using kies but wonder if I should get used to it quickly.
In 3.10.7 that failed (see post earlier), I had Nand erase, ??? for sprint, and f. reset time checked. The time it failed was the first time I seen a message on the phone saying to "use kies or recovery to fix a firmware issue."

Wasnt there some roms that requires it be pushed through odin?
I just tried the noterized stable 3 build (older version thats on my phone) and flashed stock tar and cwm, then tried stock tar and twrp. Never worked. Just starts spark screen then goes black with blue led slowly flashing. Also when trying to flash a rom through recovery it would start install then juat power off. Did this on 2 diff roms.
Ughhh so far away from getting this done i feel.
Somwtimes i see a message saying "skipping md5 check. No md5 file" or something along those lines.
Sent from my SM-N910P using XDA Free mobile app

store2426gm said:
Wasnt there some roms that requires it be pushed through odin?
I just tried the noterized stable 3 build (older version thats on my phone) and flashed stock tar and cwm, then tried stock tar and twrp. Never worked. Just starts spark screen then goes black with blue led slowly flashing. Also when trying to flash a rom through recovery it would start install then juat power off. Did this on 2 diff roms.
Ughhh so far away from getting this done i feel.
Somwtimes i see a message saying "skipping md5 check. No md5 file" or something along those lines.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
If developer doesn't include md5, the setting should be do not check md5 or something similar. Most do not include md5 from my experience on Note 4.
I thought you had established some success with CWM recovery. It usually works where TWRP fails.
I don't think it's necessary to flash a ROM prior to Odin of stock tar. I think I'd be wiping everything but sdcard plus data partition format or factory reset and powering down prior to Odin if it was boot looping. Did you try the stock recovery factory reset?
Sent from my SM-N910P using Tapatalk

I have done all that except the stock recovery factory reset. Trying that now. I have tried over and over variationd of using odin for stock tar then either superbeast, then a cwm or twrp, then try just that or then try to put a rom on. Twrp logs havnt helped other than seeing some "unable mount /data " just figured it was the rom due to trying to get root. Idk...
What could have possibly happened using auto root on a 5.1.1? It will sit ob spark screen for 5 min then just shut off. Other trys have gotten me to a boot loop 10 sec into booting...
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------
Also i have wiped everything including sd. Ive done this several ways too.
Its like it tries then half way during whatever its doing it just locks up then shuts off. Kinda like a random reboot but leads to boot loop..
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
Im re flashing stock tar now then when it goes dark during spark screen ill give it a few and batt drip. Then recovery and factory reset and let you know.
Sent from my SM-N910P using XDA Free mobile app

Anyone know how i flash these? I just need to get this phone working. Stock, rooted, doesnt matter..
Sent from my SM-N910P using XDA Free mobile app

So the latest is flashed stock tar, factory reset with recovery, then flashed stock tar again. Got all the way to optimizing apps 3 of xxx and shut off. Just powered off. Not sure why. Going to wipe dalv and reboot. May just load cwm and a rom to see what happens.
Sent from my SM-N910P using XDA Free mobile app

Here are a few pics to show what i am seeing. It made it to optimizing app 2 of 25 then just shuts off.
Sent from my SM-N910P using XDA Free mobile app

Got it! Had to format sd card twice. Then flash tar (no reboot), flash cwm and factory resets, then flash tar with reboot on this time. It is now a stock note 4 again and working. He wont let me try the 5.1.1 root method now that i know the new steps. Lol
Thanks for all the help! Hope to return the favor and pass along the info someday!
Sent from my SM-N910P using XDA Free mobile app