I have had a wierd issue with booting. My phone was fine until a couple days ago when i booted and the screen went black after the boot animation. I've odined to stock and now im stuck on the samsung image. It seems like somethign is corrupt right on boot. Does anyone have access to the pit file for a repartition or do you have any suggestioins?
If you can find the user Garwynn or rwilco, I think either of them might. Or one of their pals. (check the RDF thread in general)
Sent from my calculator watch.
I'm on the same boat. Just bought another Note II and it's stuck in the Samsung logo. I've tried a couple of different stock ODIN tar files, and it fails after a few seconds. I've read in the AT&T Note II forum other users experiencing the same issue: http://forum.xda-developers.com/showthread.php?t=1927150
What did you do prior to it failing to boot?
And theres a full restore with PIT floating around in the [WIP] missing IMEI thread by t3project in dev that will wipe and repartition the entire device before restoring lj1 or ljc forget which build it includes
I like to break stuff!
Former owner said he was trying to root it.
AlpineMan said:
Former owner said he was trying to root it.
Click to expand...
Click to collapse
Try flashing this with odin http://www.androidfilehost.com/?fid=9390169635556426493 its a full restore that *should* get you booting as long as the former owner didnt bork the bootloader or install firmware from another variant
I like to break stuff!
Thanks for all the suggestions, I did however get it to boot. I believe that something in my data that gets loaded early on just after the core boot got corruppted. This is because when I flashed the rooted odin tar which does not affect data the screen remained black directly after boot. However the full restore which wipes data, unfortunately including the internal sd card, it did successfully load. I then experimented by rerooting and restoring my data from the backup I made following the issue. This reaulted in the same issue and so I had to re odin. The wierdest thing though, is I did nothing to cause this issue, other than maybe a battery pull. My phone was on in class and I could not access the power button discretely enough, so I pulled yhe battery. Roughly 2hours later I reinserted the battery and powered the phone on. This is when the problem startrded.
Sent from my SPH-L900 using xda app-developers app
-EViL-KoNCEPTz- said:
Try flashing this with odin http://www.androidfilehost.com/?fid=9390169635556426493 its a full restore that *should* get you booting as long as the former owner didnt bork the bootloader or install firmware from another variant
I like to break stuff!
Click to expand...
Click to collapse
I've tried many ODIN stock ROMs including that one you linked w/o using a PIT partition file. ODIN tells me "There is no PIT partition" and ODIN stops.
I tried this ODIN stock ROM w/ the PIT file: http://forum.xda-developers.com/showpost.php?p=35961891&postcount=179
ODIN tells me "Re-partition operation failed"
If it's a bootloader issue, can it still be fixed? How about if a ROM for a different Note II variant was used....can that still be fixed?
*** UPDATE ***
One other thing I noticed is that when I plug in the phone either to its charger or on the PC while the phone is off, I see the battery logo show up, but it doesn't update the battery status according to its current charge (it shows an empty battery even though I know it's full). In addition, when I remove the USB cable from the phone, the battery logo stays there. Only way to clear it out is to remove the battery and put the battery back in.
Thanks!
AlpineMan said:
I've tried many ODIN stock ROMs including that one you linked w/o using a PIT partition file. ODIN tells me "There is no PIT partition" and ODIN stops.
I tried this ODIN stock ROM w/ the PIT file: http://forum.xda-developers.com/showpost.php?p=35961891&postcount=179
ODIN tells me "Re-partition operation failed"
If it's a bootloader issue, can it still be fixed? How about if a ROM for a different Note II variant was used....can that still be fixed?
*** UPDATE ***
One other thing I noticed is that when I plug in the phone either to its charger or on the PC while the phone is off, I see the battery logo show up, but it doesn't update the battery status according to its current charge (it shows an empty battery even though I know it's full). In addition, when I remove the USB cable from the phone, the battery logo stays there. Only way to clear it out is to remove the battery and put the battery back in.
Thanks!
Click to expand...
Click to collapse
You may have to either have it Jtag'd to get it repaired or file an ins claim to get it replaced. Jtag would be cheaper but you'd be without thw device about a week, although since its not booting now I doubt that would be too much hassle to have it working when you get it back
I like to break stuff!
I wonder if I can do a warranty claim. Looking at that AT&T thread I linked above, looks like other folks experienced the same problem when they simply downloaded a regular app from Play Store. Phone shut down and it's stuck in the same place where I'm stuck. ODIN didn't work for them either.
Sent from my SPH-L900 using Xparent SkyBlue Tapatalk 2
AlpineMan said:
I wonder if I can do a warranty claim. Looking at that AT&T thread I linked above, looks like other folks experienced the same problem when they simply downloaded a regular app from Play Store. Phone shut down and it's stuck in the same place where I'm stuck. ODIN didn't work for them either.
Sent from my SPH-L900 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
If the custom binary count shows anything other than "no" or "0" your warranty will be denied and your account flagged that the warranty on that device is now void.
I like to break stuff!
When I go to Download mode, it shows me the following:
Product Name: (blank)
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Sent from my SPH-L900 using Xparent SkyBlue Tapatalk 2
AlpineMan said:
When I go to Download mode, it shows me the following:
Product Name: (blank)
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Sent from my SPH-L900 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
That system status *may* cause problems although you could always try playing dumb since the binary count says no. Product name shouldn't be blank though so it appears the previous owner did in fact flash either something for the wrong device or a corrupted file that borked something.
I like to break stuff!
In the AT&T thread, those who've tried to flash the stock N7100 bootloader via ODIN got the phone working again. I tried looking for the SPH-L900 bootloader, but I can't find it so far. Perhaps that's my last hope before trying to send it in for warranty repair.
Bootloader should be in a full restore. You will probably need to try an lj1 restore. I know for a fact ma5 includes bootloader but its not official so if it doesn't work you're stuck again. It may be worth a try anyways tho cuz if you can get it booting with ma5 you can then do the hoop jumps to downgrade the bootloader and firmware if you want, although most people seem to like ma5 alot and it fixes the exynos root exploit and is 4.1.2 and apparently google wallet works without much hassle
I like to break stuff!
I looked at the SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 file. I see a boot.img. Do I simply delete all other files in the tar file and flash the SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 and put it in the "bootloader" section in ODIN to flash it?
AlpineMan said:
I looked at the SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 file. I see a boot.img. Do I simply delete all other files in the tar file and flash the SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 and put it in the "bootloader" section in ODIN to flash it?
Click to expand...
Click to collapse
Boot.img is the kernel not bootloader. Lemme see if I can scrounge up just a bootloader tar from somewhere. I know on a full restore like ma5 you'd just put the whole tar in pda and it will flash everything where it needs to go. I haven't tried flashing a bootloader onlh thru odin and I know putting things in the wrong slot = big trouble. You would really need to flash an AiO with bootloader, rom etc since we dont even know what if any rom is on there
I like to break stuff!
---------- Post added at 04:55 PM ---------- Previous post was at 04:52 PM ----------
AlpineMan said:
I've tried many ODIN stock ROMs including that one you linked w/o using a PIT partition file. ODIN tells me "There is no PIT partition" and ODIN stops.
I tried this ODIN stock ROM w/ the PIT file: http://forum.xda-developers.com/showpost.php?p=35961891&postcount=179
ODIN tells me "Re-partition operation failed"
If it's a bootloader issue, can it still be fixed? How about if a ROM for a different Note II variant was used....can that still be fixed?
*** UPDATE ***
One other thing I noticed is that when I plug in the phone either to its charger or on the PC while the phone is off, I see the battery logo show up, but it doesn't update the battery status according to its current charge (it shows an empty battery even though I know it's full). In addition, when I remove the USB cable from the phone, the battery logo stays there. Only way to clear it out is to remove the battery and put the battery back in.
Thanks!
Click to expand...
Click to collapse
On the restore you linked here did you make sure to download the attached PIT file at the bottom of the post as well? If not that maybe why that restore failed and you could try including the PIT and reflashing
I like to break stuff!
I was able to extract the param.bin and sboot.bin from SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5. Looks like these 2 files are the bootloader files. In any case, I attempted to flash it via ODIN and it still didn't work.
And yes, I used the PIT file attached with the ODIN recovery I linked. That didn't work either. So right now it's looking like the only options I have:
1) Warranty claim
2) JTAG
AlpineMan said:
I was able to extract the param.bin and sboot.bin from SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5. Looks like these 2 files are the bootloader files. In any case, I attempted to flash it via ODIN and it still didn't work.
And yes, I used the PIT file attached with the ODIN recovery I linked. That didn't work either. So right now it's looking like the only options I have:
1) Warranty claim
2) JTAG
Click to expand...
Click to collapse
Yea sounds like someone flashed incorrect firmware and borked the partitions up. I know the international variant I believe has its misc partition in the same place the sprint versions boot partition is and if you flash that its forked up good. (I might be thinking of s3 here, I'm maintaining so many devices its getting hard to keep them all straight) either way flashing firmware from another variant is never a good thing at the very minimum the modems are for entirely different hardware/frequencies, and at the worst the partitions are all different and screw up the emmc with no way to gain access to correct the failed partitions.
I like to break stuff!
I PM'd Dr.Ketan (recognized developer in the N7100 section). He thinks my Note 2 is a victim of SDS (sudden death syndrome) http://forum.xda-developers.com/showthread.php?t=2093599 there may be hope yet for a warranty claim.
Sent from my SPH-L900 using Xparent SkyBlue Tapatalk 2
Related
I was just flashing my phone back to the Stock Telus ROM from the Index thread using Odin. I went into download mode and then I added the PIT file from the Odin folder by clicking the PIT button, then pressed the PDA button and added the Stock ROM TAR file. I connected the device and it was detected, so i pressed start and it was going to do the NAND flash and it said Error. So i tried again, same thing.
Now my phone will not boot up at all, meaning:
-Absolutely nothing on the screen
-Buttons don't do anything
-I got the USB to pick up something called a QUSB-DUMP but then the driver installation failed and I haven't got it to do it again.
-So the phone does absolutely nothing
I remembered that there was no instructions that said anything about the PIT file, so maybe that was it? Please help in anyway you can! Thanks!
Went to store and exchanged it, can anyone confirm what may have caused the brick?
Went back to store again and got a sgs s ii! mwahahahahaha !
Sent from my GT-I9100M using XDA
koodiifin said:
Went to store and exchanged it, can anyone confirm what may have caused the brick?
Click to expand...
Click to collapse
I would definitely say the PIT mode, we only use ODIN for PDA as far as I know.
word. not following instructions = bricked phone
Sent from my SGH-T989
not sure why he's laughing so hard about getting a sgs2 when he already has a sgs2?
base on his sig, looks like he's in the wrong forum... this is 989 not 9100
Issue
1. Phone won’t boot beyond the Samsung Logo.
2. It won’t boot into recovery (download mode works).
3. Can flash rom using Odin but phone still won't boot.
Type of Phone
Type: AT&T Samsung Galaxy Note 2
Model: i317
Ownership: Bought in Nov 2012 brand new. Warranty is up but it is insured through AT&T.
History: Rooted and then un-rooted and returned to stock in January 2014.
Actions leading up to Issue
Updated to Samsung’s newest firmware Android 4.3 but didn’t like it. I rooted my phone and tried a custom rom but wasn’t happy. Un-rooted by flashing original stock rom via Odin 3.07. Worked great and I was back in business. But then the phone went through an update and never booted back up.
Detail
I’ve rooted all my other phones but never felt the need to root this one until I updated to Samsung’s new Android 4.3. I wasn’t happy with the decreased battery life and poor performance. So I used the method at http://forum.xda-developers.com/showthread.php?t=2004650 to root my phone using “root66_ATT_I317UCALJ2.tar.md5” with Odin 3.07 and it worked. I then tried a custom Cyanogen Mod rom but it still left something to be desired.
After more research I flashed the original stock rom “KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5” via Odin 3.07 and my phone worked beautifully, at least for a day. Then I started getting the AT&T update window for Android 4.3 and the only way to get rid of it was to pull my battery. It was happening so much that I couldn’t even make a phone call. Out of pure frustration I decided to accept the update.
After the update installed it rebooted and never made it past the Samsung logo. So I figured I would just go into recovery and perform a factory reset as well as wipe the cache. The problem here is that it won’t boot into recovery. Only download mode works. I’m also seeing a red LED which I’ve read is a sign of SDS.
I’ve tried re-flashing the original stock rom again. Every time I do I get the green “Pass” display but my phone still won’t boot. The binary count is now at 21 since I’ve tried flashing so many times. I’ve been working on this and researching for 3 weeks. I’ve never had an issue that I couldn’t resolve when it comes to any of my past phones but this is beyond my skill or understanding. I also tried Samsung keys but it says my device is not supported.
Short of digging a hole in my back yard and burying it, is there anything I can do to fix this?
(Note) My wife has the same phone and also didn’t like the update so I flashed the same original stock rom to her phone via Odin and it has been working just fine. Only difference is I never rooted hers. I should have gone that route with mine.
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?
josh3josh3 said:
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?
Click to expand...
Click to collapse
Here's the link to TWRP (you want the Odin link toward the bottom):
http://teamw.in/project/twrp2/124
Here's the direct link to the latest philz cwm (you want the md5 file):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
I prefer philz, but you will likely need TWRP to follow the dicksteele guide. You should also track down a CWM flashable recovery package for MH3 recovery to flash back should you need to return the phone for repairs. You can get this by following the i317 link in my sig.
If flashing this in Odin doesn't work that would tend to support the emmc fail scenario. (i.e. you flash it, Odin behaves as if it flashed ok, you power off, attempt to boot recovery with home-VolUp-power and it still doesn't boot). If it does boot recovery, you can try the guide as I mentioned before. Good luck!
Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.
josh3josh3 said:
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.
Click to expand...
Click to collapse
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ
So, there appear to be many people who see this update as a bad joke. Like me.
I had a thread a couple days ago about how to kill the notification from att
Without root. Nothing can be done as far as ive heard/seen. Im a bit confused
About needing a battery pull to remove pp note, I have been just reboot and it
Goes away until next data use/net access. When my 8 hrs is up I turn data on
(Data off as 8hrs expires) and immediately get note and then I hit home- get
another 8 hrs. Im sorry to hear they wore you down with the note- im going to
fight and resist for the duration. And keep stock. Its a game now!
R, john
qkster said:
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ
Click to expand...
Click to collapse
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.
Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
josh3josh3 said:
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.
Click to expand...
Click to collapse
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....
dicksteele said:
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....
Click to expand...
Click to collapse
Have tried that many times with no luck. Wish it were that simple.
josh3josh3 said:
Have tried that many times with no luck. Wish it were that simple.
Click to expand...
Click to collapse
Have you tried this yet ?
http://forum.xda-developers.com/showpost.php?p=49826416&postcount=9
Zen Arcade said:
Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.
josh3josh3 said:
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.
Click to expand...
Click to collapse
That would be the Thanks button by the Quote...
OUTSTANDING !!!
Glad you're back among the living.
This will get you back to 4.1.2
http://forum.xda-developers.com/showpost.php?p=49616718&postcount=2
EDIT:
I just did this and it worked perfectly .....
I'm actually doing that step right now also. I flashed back to stock testing the ATT update server.
EDIT #2:
At this step when the phone reboots the script will run. When it completes you want to boot to system. The next prompt will be do you want to install ROOT. If you do the swipe it will install ROOT, there is a DO NOT INSTALL button on the middle of the screen. Just a heads up, don't know if you are turning your phone back in or not now.
- Second step is:
You will need to download TWRP 2.6.3.1 and flash it in ODIN.
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
This is necessary for an openrecovery script to run that is stored in the /cache directory from the update.
- Put your Note 2 in Download Mode.
- Open ODIN, put openrecovery-twrp-2.6.3.1-t0lteatt.img.tar in PDA slot. Click Start and let the phone reset.
- Your phone will reboot in TWRP. If not, pull battery and enter recovery mode boot into TWRP recovery (HOLD VOL UP+HOME+POWER). The script will run by itself.
sgh-i317 EFS seems like its gone
could anybody help me out with my note 2. ive tried just about everything i can think of. im getting pretty desperate. i can get everything to work fine (recovery,download mode,) but something is keeping it from booting up to the main screen, it will just hand at the boot animation, or the att logo. in twrp it tells me failed to mount efs. ive looked around in the file folders and its like it got wiped out? im not sure how though. could that be why its not booting up?
any ideas??
Thanks for taking the time first!
I recently updated to CM10.2 but had issues that I overlooked. Those issues lead to my phone hard bricking... Completely black and no power.
After doing research, I found out about a Jig but while I was waiting for it come in the mail I found out about the SD Unbrick. I tried the SD Unbrick and the phone came back on! However, I got the following:
______________________________________________
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
BOOT RECOVERY
WRITE 159488 sectors
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
and after trying to flash via ODIN - Odin says "there is no pit partition"
and the phone I get:
"ODIN: flash read failure" at the bottom
______________________________________________
I got the Jig in the mail today and tried it without the SD and the phone wouldn't boot up.
However, and this weird part, if I have the SD Debricker in the phone and then use the Jig it boots up without me even having to touch the power button. Not sure what to do at this point?
From what I've read so far, the Warranty Bit: 0 might be my problem but I'm not sure? I can't get anything to install on the phone. I have yet to get the phone into a download mode that has the android mascot either.
Thanks for any all help!
You probably need the pit file. Thread in General section.
DocHoliday77 said:
You probably need the pit file. Thread in General section.
Click to expand...
Click to collapse
Flashing a PIT file does you no good if the phone can't read from or write to the internal storage.
I'm in the same boat, and this sounds like an eMMC failure.
I have not heard about anyone who has had success fixing this kind of brick, JTAG or otherwise.
I wish I had a RIFF box to test that theory, but I can't spend much more money to fix this.
[OT]I wish there was a way to disable Qualcomm Secure Boot (bootloader signature checking),
because that would allow us to use 4.1 debrick images with a 4.3 bootloader, cross-device bootloaders,
and possibly boot Android directly from the SD card, bypassing this useless brick "download" mode.
If Android booted, we might have low-level access to the eMMC, assuming the hardware still works. But no, Catch-22...[/OT]
Considering he can get it to boot with the SD card, and Odin says there is no PIT file, its at least worth a shot before writing it off.
I've tried every combination I can think of: different PIT files, different debrick images, different versions of ODIN, repartition/no repartition, and I don't think any amount of fiddling with this useless "download mode" (I'm not convinced it's actually in download mode BTW) will make it flashable. I'd like to try JTAG or a low-level format, but both require eMMC hardware that isn't dead. Not being able to boot into Android like the debrick image is supposed to let you do is frustrating, because if it got as far as recovery mode I could at least poke at the eMMC.
OP, if JTAG is an option for you, don't expect it to work, but if you do try, let us know how it goes.
If this flash write failure is fixable with JTAG, I'd love to know - I'm just not prepared to pay shipping costs to send it in for JTAG repair when it's near certain that they won't be able to fix it without replacing the eMMC chip (expensive and risky) or the motherboard.
---------- Post added at 02:08 PM ---------- Previous post was at 01:56 PM ----------
PhillyKing said:
However, and this weird part, if I have the SD Debricker in the phone and then use the Jig it boots up without me even having to touch the power button.
Click to expand...
Click to collapse
Can you clarify "boot"? Is it the same screen that says "BOOT RECOVERY MODE" at the top?
If you can boot into recovery or Android from the SD card, you may be able to poke at the eMMC and reset it.
If I'm not mistaken, a jig is supposed to automatically boot into download mode, and that's all. If you can boot with the sd debrick image, then inserting the jig should work normally.
When I got the sd debrick method working, I was able to fully boot system, recovery and download mode. Of course if you don't have a working system after attempting to flash over your last rom it won't boot that part, but you should be able to get to recovery.
Have you tried flashing just twrp or cwm via odin? Does it give the same message as you posted above?
If you can boot to a custom recovery, have you tried flashing another rom?
Can you clarify "boot"? Is it the same screen that says "BOOT RECOVERY MODE" at the top?
If you can boot into recovery or Android from the SD card, you may be able to poke at the eMMC and reset it.
Click to expand...
Click to collapse
Yes, when it "boots" up it says "BOOT RECOVERY MODE" -- I don't have nor get the Android mascot either.
PhillyKing said:
Yes, when it "boots" up it says "BOOT RECOVERY MODE" -- I don't have nor get the Android mascot either.
Click to expand...
Click to collapse
Have you tried any of the things I've suggested?
DocHoliday77 said:
Have you tried any of the things I've suggested?
Click to expand...
Click to collapse
I'm having a hard time finding the Pit files....
Just search general section for "pit" and this is the second result.
http://forum.xda-developers.com/showthread.php?t=1848267
Sent from my SGH-T999 using Tapatalk
I found the PIT file but when I try to flash it using ODIN I get:
SECURE CHECK FAIL : PIT
Oh man....I remember in the note3 forums people mentioned they needed a properly signed pit.....I hope that this isnt the case for us on 4.3! Search for a program called pit magic. I dont know if it can help or not, but its worth a try.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Oh man....I remember in the note3 forums people mentioned they needed a properly signed pit.....I hope that this isnt the case for us on 4.3! Search for a program called pit magic. I dont know if it can help or not, but its worth a try.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got the app but not sure what I need to do with it.
Youll have to read up on the thread. I dont know much about it, just that it may have the potential to help.
Ive never needed to use it myself, but ive directed others there and it helped some and didnt help others...
Sent from my SGH-T999 using Tapatalk
brick
test
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've not done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Majin Kaioh said:
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Click to expand...
Click to collapse
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I have had my share of boot looping experiences, never from not doing any type of experiments with my devices. nonetheless myself and I'm sure many other people just do what was mentioned in the quote to alleviate that problem.
i know you (OP) mentioned you don't plan on doing any flashing, but i would do that before using insurance personally, even if there was no deductible
Majin Kaioh said:
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
Click to expand...
Click to collapse
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
jack man said:
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
It won't fix what sounds like a missing or corrupted boot file, had to deal with it on a LG g3.. restoring a full back up or a plain reset had no effect.. it was either doing a full flash or flashing the boot files
for that phone it would randomly happen when the OTA tried to upgrade the device while it was rooted, took me 3 times of dealing with it before I realized OTA was still live
Small update. My local AT&T store has a replacement being sent to me. I'm unhappy, however, since its apparently a refurbished device. I pay for insurance that covers a new device if something, anything, happens. They're refusing to send me a new one for some reason that they won't explicitly state to me.
My loyalty with AT&T has wavered, and I will probably be on another network in coming months. I'm thinking Sprint so that I can least have an unlocked Note 4.
Regardless, since this device is being sent back, I decided to try and Odin flash it anyways. It did not work. Still boot loops at the Note 4/Android screen. Doesn't even load the AT&T logo. I'm fairly certain something is fundamentally broken with the device. Probably a factory error. It's never been dropped, and has been inside a hard case since day one.
Being that it is a manufacturing error, I'm not to angry about that. These things do happen. AT&T's treatment of me, however, is just unacceptable. I've been a customer for about eight years, and have been on Android since the Motorola Backflip. I upgraded to a Samsung Captivate and never looked at another manufacturor.
Are you able boot to the recovery menu?
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
i have the bootloop issue before to put *#9090#
the loop is every aprox 3 mins
some sugestion?¡
sudoBacon said:
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Click to expand...
Click to collapse
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
thepinkpanter said:
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
Click to expand...
Click to collapse
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
sudoBacon said:
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
Click to expand...
Click to collapse
I already did it but by using Odin 3.09 pls. see http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391/page5
maybe I did something wrong
or from where can I get / download a different N910AUCU1COC4 ?
thanks again for your kind help
Was running latest renegade rom and SkyHigh kernel. I woke up sunday morning after my phone having been on the charger, and it only showed 14% charge and powered off. Not needing my phone right away, I had assumed maybe the charger wasn't making the best connection and replugged and let it charge fully. Later, when it was fully charged, I took it off the charger and powered it up to an endless bootloop. Smart Switch and Kies says my device isn't supported.
I have tried reflashing in TWRP to no avail. I tried to ODIN a stock rom to the same results. It gets so far into the restore/install and the phone just reboots to recovery. It seems to me I have a partition gone bad maybe?? I have no idea what else to try here. Please help!!
sparytrainor said:
Was running latest renegade rom and SkyHigh kernel. I woke up sunday morning after my phone having been on the charger, and it only showed 14% charge and powered off. Not needing my phone right away, I had assumed maybe the charger wasn't making the best connection and replugged and let it charge fully. Later, when it was fully charged, I took it off the charger and powered it up to an endless bootloop. Smart Switch and Kies says my device isn't supported.
I have tried reflashing in TWRP to no avail. I tried to ODIN a stock rom to the same results. It gets so far into the restore/install and the phone just reboots to recovery. It seems to me I have a partition gone bad maybe?? I have no idea what else to try here. Please help!!
Click to expand...
Click to collapse
Check IMEI/MEID in Download Mode, it gives you the option there to see serial/imei/meid, if its all 0's, likely your EFS was damaged or deleted and i would say this is likely the cause of the bootlooping. Had this happen to my personal device, Sprint some how fixed it, but flashing stock firmware via odin etc, didnt fix it for me. Good luck!
I don't see any options in download mode. Just says downloading..
U need to flash a stock kernal using odin then flash stock firmware with odin again ... It will 100% work hit thanks it helps
Sent from my LG-H815 using XDA-Developers mobile app
jinderation said:
U need to flash a stock kernal using odin then flash stock firmware with odin again ... It will 100% work hit thanks it helps
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
You wouldn'y by chance have a link handy would you?? I can't find just the kernel anywhere on here or google.. lol.. or ANYONE for that matter???
sparytrainor said:
You wouldn'y by chance have a link handy would you?? I can't find just the kernel anywhere on here or google.. lol.. or ANYONE for that matter???
Click to expand...
Click to collapse
If you have a bad partition, flashing the PIT file would mark bad blocks in the bootloader. So it won't try to write to them. All links are in the General section in a nice very organized thread.
elesbb said:
If you have a bad partition, flashing the PIT file would mark bad blocks in the bootloader. So it won't try to write to them. All links are in the General section in a nice very organized thread.
Click to expand...
Click to collapse
Yeah, I've tried flashing the pit a little while ago and it does the same thing.. Odin shows successful, but when it installs on the device, it only gets so far, then says deleting (or erasing) and reboots.. I believe Anderd hit the nail on the head, as download mode shows zeros in for imei.. guess I'll be making a call tomorrow and playing around with CDMA workshop.. Not sure what else to do since it's a boost phone and you can't even get a simple card at a boost shop.. Don't really want to send it in..
sparytrainor said:
Yeah, I've tried flashing the pit a little while ago and it does the same thing.. Odin shows successful, but when it installs on the device, it only gets so far, then says deleting (or erasing) and reboots.. I believe Anderd hit the nail on the head, as download mode shows zeros in for imei.. guess I'll be making a call tomorrow and playing around with CDMA workshop.. Not sure what else to do since it's a boost phone and you can't even get a simple card at a boost shop.. Don't really want to send it in..
Click to expand...
Click to collapse
It seems like a hardware fault then. If it can't flash the PIT file, which doesn't even flash anything, just re-arranges blocks, then there's something hardware related. Especially if you get 0 for IMEI. That's usually a tell tale sign of time for a new device. Lol. They aren't too expensive anymore on Swappa.com. Got mine from there.
You can try flashing this kernel first via odin then flash stock rom
copy paste this in web address
http://wikisend.com/download/257572/SM-G920P--kernel--[17-05-16].zip
---------- Post added at 10:30 AM ---------- Previous post was at 10:14 AM ----------
if this still doesnt work u can downgrade to 5.11 but flash the stock kernel first via odin
click n download
http://wikisend.com/download/497232/UniKernel_v8-0001-BOH1-920P-091215.tar
and then downgrade firmware, download from below
https://www.androidfilehost.com/?fid=24052804347838030
if still stuck in boot loop let the phone drain to 0% in odin mode it would be turned off plug in charger charge it 10% without turning on the device and after the charge 10% reached turn on ur phone let the bootloader load i really dont think u should have any issue now...