[Q] Softbrick, bootloop, TWRP Password - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

My girlfriends S3 (Bell, I747M, d2can) is currently boot looping. It had a custom ROM on it, but I'll be damned if I could tell you which one. It was working, then it wasn't. No updates, no flash/wipe/etc.
Now I turn on her phone, and it gets to the ROM's boot screen, and just as it's about to complete, it restarts again. I can enter TWRP (2.6.3.1) but it requires a password (which is a bug, afaik). I can press "cancel" and try to reset/wipe, but it won't mount or reset the cache partition, so it fails.
I used Odin (3.07, 3.09) to try and flash TWRP 2.6.3.0 and 2.7.0.0, and both failed. The result was Odin would reboot the phone, then it would enter the same bootloop, and the recovery would still be TWRP 2.6.3.1.
I tried downloading a stock S3 firmware and flashing it with Odin. Same problem.
I've tried new drivers. New cable. New USB port. I've tried using a different computer. Always the same result.
So a summary of what I can/can't do:
Can't use TWRP to reset/wipe
Can't use ADB Sideload
Can't modify device via ADB
CAN see the device via ADB
CAN enter download mode
Any help?
I pulled DMESG at some point during all this. Maybe it can help shed some light: http://pastebin.com/4c2uL3Qq

Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.

theramsey3 said:
Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.
Click to expand...
Click to collapse
Appreciate all the help! I've tried pretty much every combination.
I've turned off auto-reboot, flashed, but Odin stops at:
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
Click to expand...
Click to collapse
I assume that's where it's supposed to be. Then I enter recovery and it's still the same TWRP 2.6.3.1. Very strange.
I don't think her phone is using 4.3 bootloaders, as I don't remember them being available when I flashed this phone. I'm a Nexus guy, so maybe I'm doing something wrong this time.
EDIT: I also seem to recall on my phones that when I flashed something in Download/Fastboot mode, there was a progress bar of sorts on the phone itself indicating it was receiving something. On this phone it doesn't display anything to imply something's happening.

Boot into download and let us know what it says on the download screen. If you have the 4.3 bootloader, try flashing a pre-rooted 4.3 Bell ROM using Odin 3.07. If you have a lower version bootloader, try flashing a pre-rooted 4.1.1 or 4.1.2 ROM.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=139036464
In Odin, don't check auto reboot. When you see reset in the status windows, disconnect the USB cable and pull the battery. Boot into recovery and wipe cache, data, and reboot.

Thanks for the reply! I'm 99% sure it's a pre-4.3 bootloader. Here's what it shows in DL mode:
ODIN MODE
PRODUCT NAME: SHG-I747M
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
DUALCOMM SECUREBOOT: ENABLE
If I recall correctly, a 4.3 bootloader would show two more lines at the bottom.

Tried installing a 4.1.1 ROM (root66_BMC_I747MVLDLK4)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDLK4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
4.1.2 (root66_BMC_I747MVLDMF1.7z)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDMF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

I feel it's worth mentioning again: At no point, while using Odin, does the phone display a transfer bar of any sort.

Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.

audit13 said:
Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.
Click to expand...
Click to collapse
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.

X04D said:
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.
Click to expand...
Click to collapse
Try this: when you flash with Odin, uncheck auto reboot, start the flash process. When you see the word reset in the status window, remove the USB cable, pull the battery, and boot into recovery.

Related

Another Soft Brick...

Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
bbrou33 said:
Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
Click to expand...
Click to collapse
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
audit13 said:
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
Click to expand...
Click to collapse
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
britt21 said:
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
Click to expand...
Click to collapse
The only ATT DKL3 firmware that I can find is in this thread. WinRar was failing to unpack the .7z file every time I tried. But I'll try again later when I get home
bbrou33 said:
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
Click to expand...
Click to collapse
You can try different stock firmware from sammobile if you are sure you do not have the 4.3 bootloader.

[Q] Unable to flash to stock with odin / having two 0 directories

So newb questions and might have been answered but I have been unable to find the answer I'm looking for.
Background:
SGH T999
Original I was on 4.1 stock. I used towelroot and was able to root and all that jazz. I uploaded an old version of CWM to my phone and was unable to flash and ROMs, they would all hang on the Samsung Galaxy SIII screen.
I updated CWM to put on a Cyanogen Mode ROM and all was good. I tried out a couple other ROMs then decided I wanted to go back to stock and see how stock 3.3 or 3.4 was. I tried using Odin to bring back to stock and no luck. I then installed PhilZ recovery and booted to Wicked ROM for 4.1. After this I got current TWRP and tried to update other roms. I went into ROM manager switched over to CWM 6.0.4.5 then updated my kernel. At some point along the way I noticed that on the internal sd card I have a 0 directory inside my 0 directory.
Now when I reboot my phone into Recovery mode I see a Samsung Galaxy SIII screen with the Cyanogen guy on it, then it loads to CWM but nothing is on the screen but the hat, then after a couple of seconds it loads to a Samsung screen quickly, then to the Samsung Galaxy SIII and hangs indefinitely. I'm still able to get the phone to go into download mode fine. Now I'm trying to just bring back to stock but not having any luck. Here's my repro:
1. Put hardware into download mode (HOME + Vol Down + Lock).
2. Open Odin 3.09 as Admin (I'm using Win 7).
3. Connect hardware to computer (Odin recognizes 0:Com5).
4. Place "T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5" in AP field.
5. With only "Auto Reboot" and "F.Reset Time" selected press Start button.
RESULT:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Then on my hardware I get
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Offical
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
SW REV CHECK FAIL : Fused 1 > Binary 0
Click to expand...
Click to collapse
Any idea's how I can bring this back?
tiger_johnson said:
*snip*
Any idea's how I can bring this back?
Click to expand...
Click to collapse
Hmm, if the device is recognized in your PC by ODIN there's still hope. I personally recommend TWRP (LINK for latest ODIN flashable version) for everything as CWM has caused havoc with my phone before. Stay away from it. IF you can still access recovery, do format everything, including the internal SDcard. Also please use the PIT file when trying to use ODIN for the MD5 firmware you're choosing. LINK for the PIT file (choose your model's PIT and put it on the PIT part of ODIN then proceed on flashing the MD5 firmware - credit goes to DocHoliday for the PIT files). That little file can sometimes fix stuff when trying to ODIN the device back to stock firmware. Just giving ideas, don't give up and best of lucks!
You can't flash MD5. It looks like you are currently running MJC base firmware which means you can ONLY flash MJC or NC2 with Odin. Do not try to downgrade via any method or it will hard brick your device.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
"SW REV CHECK: Fused 1" means you currently have MJC. It will change to Fused 2 if you update to NC2. (If I'm remembering all those nemesis right).
Just FYI in case anyone was wondering.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Samsng Tab 3 7.0 probably hard bricked

My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
untamed1 said:
My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
Click to expand...
Click to collapse
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
bierma32 said:
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
Click to expand...
Click to collapse
Thank you for your response.
First if with search function you mean by using google, I have done a lot of of that, but so far with no luck.
I am pretty good with this stuff but not good enough. I would like to find someone who has either a lot of knowledge or has resolved a situation like mine and is willing to help.
The link you suggested is probably good, but does not totally relate to my situation. They had a working device they were simply trying to root. I instead don't have a working device and not even access to recovery mode. I don't even know right now what files and folders are on my device.
Thank you for the pit file though; now I have to find out whether repartitioning with it would be good, or whether it would push me down deeper in the hole.
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
bierma32 said:
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
Click to expand...
Click to collapse
Bierma32,
first of all thank you for spending the time to assist me it is very much appreciated. I followed your procedure and unfortunately it went nowhere fast. This is the report from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210RUEU0COB1_T210RXAR0COB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what happened earlier with the only difference being the "Set PIT file" command.
Any idea?
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Rom's for Samsung Tab 3 7.0 SM-T210R
Doom1337 said:
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Click to expand...
Click to collapse
For non stock ROM's:
http://forum.xda-developers.com/galaxy-tab-3/development-7
For Stock ROM's:
http://www.sammobile.com/firmwares/
For stock there are faster download sources also, do some google searching. By the way my issue has nothing to do with rooting.
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
I had found another PIT file as well, that looked very promising but did not work. I will try these two. Thanks.
:fingers-crossed:
Continuation
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
untamed1 said:
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
Click to expand...
Click to collapse
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
No battery picture
vinay said:
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
untamed1 said:
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
Click to expand...
Click to collapse
you just hard bricked your device.
but download mode is working so still a hope.(untill power end)
which version of odin are you using.?
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
untamed1 said:
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
Click to expand...
Click to collapse
When this happen.
What was you doing.
Like
Your tab was running you turned off and it won't turn on. Or you flashed a rom/kernel and it won't turn on.
Sent from my D2212 using XDA Free mobile app
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
untamed1 said:
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
Click to expand...
Click to collapse
First of all update your odin to 3.09 or higher if there is. And try flashing again.
(btw is that rom was made for your variant)
Sent from my Xperia E3 using XDA Free mobile app
same issue
i also have an unresponsive sm-t210r that has the OP's issues of a broken looking download screen, no boot and no recovery
pit file problems in odin and timeouts and now not postitive if my device made it to the 4.4.2 locked bootloader. looking to get it back to stock.
will help with files, time etc.
-ty
SOLVED
got my tab(SM-T210R) back up and running,,
been at it a few hours a day all this week,
kies firmware upgrade and initializaton somewhat didnt work. it installed it but always booted a black screen and backlight no sound. no vibiration,
so i am back to help the OP' and all others with this specific issue of dirty flashing directly to 4.4.2 from a rooted custom recovery tab3 that now have a messed up black screen problem but can still sneek into download mode thats looking all messed up> with the fallowing message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
and then get PIT file errors and setup connection hangs.
please be shure you dont still have your custom recovery. you just have to hold home and vol+ ten seconds longer then usual after releasing the power button when the backlight appears. i thot i didnt have mine. until after i did this. now im just not shur if i held the buttons long enough then.
(if you need to get your current binary to offical please use odin's firmware and initialization process.. it will go thru and your binary will be changed to official but you will still have the black screen boot even though kies installed everything. proceed to next)
to get your brick back to being a useful loaf
this is what you need.
factory usb cable
odin 3.07
LT02.pit file from a 4.4.2 firmware (not 100%on that) ask me for the one i extracted if all eles fails
and T210.TWRP.2.8.0.0.tar.md5
start with opening odin
set your pit file and load the twrp recovery_
you want repartition checked for this (loading pit file should automatically fill the check box)
also autoreboot and f.reset time , checkboxes are checked
get your bricked device into download mode and connect
confirm odin sees the device and flash
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.2.8.0.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
at this point within 15 seconds after the reboot i got a splash screen and it booted up into 4.4.2 checked the status, device status of custom.
restarts and power offs are safe at this point. just take 5 seconds longer than normal.
so now we have an operating tablet with recovery and a messed up but working download mode.
checked download mode screen STILL CORRUPTED with the same weird message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
i checked for twrp to operate it did. just took longer to boot it
PLEASE DO NOT AT THIS POINT wipe everything. it only got me back to the black screen with no booting.
and not being able to odin the .md5 package stock firmwares
it put me back an hour to get back to where these instructions end.
if this happends to you run keis firmware and intialize, to get the stock package back in and return to the corrupted download mode to see binary samsung offical.. then continue my odin instructions.
FALLOW UP:
had some time to experiment. i got back to %100 official system/binary and normal download mode with the green android guy being back.
i had updated to the latest TWRP and rooted.
i then unrooted with the super su app
then with the new kies program called SMARTSWITCH i again did the firmware and initialize and it went through and booted. without a hitch.
try it then go ahead and check for stock recovery and android man in download mode
-your welcome
b.t.w it seems in all the mess im still HW-rev 0x5 and it never installed the knox warraty bit..., blessing in disguise?
if this works for people somebody wanna make a sticky and add it to a 4.4.2 unbricking guide?
be aware that this is what worked for me. if you feel a different recovery or pit file may work go ahead. this is my results and wont be held accountable for what happens to you.
> DISCLAIMER> TRY AT YOUR OWN RISK< I AM NOT RESPONSIBLE
kal swift said:
got my tab(SM-T210R) back up and running,,
been at it a few hours a day all this week,
kies firmware upgrade and initializaton somewhat didnt work. it installed it but always booted a black screen and backlight no sound. no vibiration,
so i am back to help the OP' and all others with this specific issue of dirty flashing directly to 4.4.2 from a rooted custom recovery tab3 that now have a messed up black screen problem but can still sneek into download mode thats looking all messed up> with the fallowing message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
and then get PIT file errors and setup connection hangs.
please be shure you dont still have your custom recovery. you just have to hold home and vol+ ten seconds longer then usual after releasing the power button when the backlight appears. i thot i didnt have mine. until after i did this. now im just not shur if i held the buttons long enough then.
(if you need to get your current binary to offical please use odin's firmware and initialization process.. it will go thru and your binary will be changed to official but you will still have the black screen boot even though kies installed everything. proceed to next)
to get your brick back to being a useful loaf
this is what you need.
factory usb cable
odin 3.07
LT02.pit file from a 4.4.2 firmware (not 100%on that) ask me for the one i extracted if all eles fails
and T210.TWRP.2.8.0.0.tar.md5
start with opening odin
set your pit file and load the twrp recovery_
you want repartition checked for this (loading pit file should automatically fill the check box)
also autoreboot and f.reset time , checkboxes are checked
get your bricked device into download mode and connect
confirm odin sees the device and flash
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.2.8.0.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
at this point within 15 seconds after the reboot i got a splash screen and it booted up into 4.4.2 checked the status, device status of custom.
restarts and power offs are safe at this point. just take 5 seconds longer than normal.
so now we have an operating tablet with recovery and a messed up but working download mode.
checked download mode screen STILL CORRUPTED with the same weird message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
i checked for twrp to operate it did. just took longer to boot it
PLEASE DO NOT AT THIS POINT wipe everything. it only got me back to the black screen with no booting.
and not being able to odin the .md5 package stock firmwares
it put me back an hour to get back to where these instructions end.
if this happends to you run keis firmware and intialize, to get the stock package back in and return to the corrupted download mode to see binary samsung offical.. then continue my odin instructions.
FALLOW UP:
had some time to experiment. i got back to %100 official system/binary and normal download mode with the green android guy being back.
i had updated to the latest TWRP and rooted.
i then unrooted with the super su app
then with the new kies program called SMARTSWITCH i again did the firmware and initialize and it went through and booted. without a hitch.
try it then go ahead and check for stock recovery and android man in download mode
-your welcome
b.t.w it seems in all the mess im still HW-rev 0x5 and it never installed the knox warraty bit..., blessing in disguise?
if this works for people somebody wanna make a sticky and add it to a 4.4.2 unbricking guide?
be aware that this is what worked for me. if you feel a different recovery or pit file may work go ahead. this is my results and wont be held accountable for what happens to you.
> DISCLAIMER> TRY AT YOUR OWN RISK< I AM NOT RESPONSIBLE
Click to expand...
Click to collapse
I still cant get it working, i keep getting stuck with it saying it doesnt have a pit file even when i try to load it

Screen says There is no PIT partition after Firmware Install Failure

So I've been at this for a total of 9 hours now...here's the story:
Yesterday I have my trusty Note 4 on the charger, it charges fully and I unplug from the cord.
I hit the home button and the screen stays black like it was frozen.
I hit the power button, nothing happens.
I pull the battery, put it back in, nothing.
It finally goes back on and I get the Cant do normal boot:"MMC_Failed" and I'm stuck on the Odin screen.
Try to just re-flash the stock rooted ROM I was using at the time of this disaster and I kept getting the same message so I bring the phone to a Sprint service center where, when I walk in the front door and tap the power button, the phone lights right up and works. Now I look like a clown.
I leave the store and it freezes again so I try a factory reset, which sets this whole process in motion again once I set it up...freezes, "can't do normal boot" etc.
Then after someone suggested to flash the latest TWRP (3.0.0.0) and a stock firmware, I get a "system write fail" in Odin (both 3.09 & 3.10) so I try to flash the stock ROM again now I get a "No PIT File" error.
I flash the PIT file specific for my phone I got from SamMobile along with the same ROM and the phone wouldn't start.
I noticed the "system" was unchecked in TWRP so I checked it before doing anything but still no luck as of last night/this morning at 3:00am.
I wake up this morning and it goes right on with no issue just like a fresh/factory reset device.
Is there something i can do to make sure everything is ok so I don't have to go through this again?
I need this Note 4 to work.
I have been running stock OJ6 rooted ROM and that's it. No mods or anything, just root so for this to start acting up the way it did or why it happened is beyond me.
Someone recommended to install ClockworkMod so that would fix the "system" error but I'd rather see if anyone else had the same problem and how they fixed it before I attempt anything else.
Usually, any time I ever had a problem I clear the dalvik/cache, factory reset or flash firmware in Odin and everything is straight.
Thanks ahead of time for any help.
What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk
samep said:
What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night
broad_st_bully said:
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night
Click to expand...
Click to collapse
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk
samep said:
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...
Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
broad_st_bully said:
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...
Click to expand...
Click to collapse
If it dus not boot try to flash repair firmware
broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
Removed!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
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
cache.img.ext4
modem.bin
RQT_CLOSE !!
RES OK !!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
If you've wiped everything but extSdCard and flashed the stock tar in Odin, there shouldn't be any trace of root. You're not rooted.
Did you try factory reset in stock recovery? Can't recall, but is there also a format data option in stock recovery? If so, try that too.
Sent from my SM-N920P using Tapatalk
broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped
waheem said:
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped
Click to expand...
Click to collapse
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:
broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...
broad_st_bully said:
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:
Click to expand...
Click to collapse
Just press thanks buttons if help
broad_st_bully said:
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...
Click to expand...
Click to collapse
@broad_st_bully any luck on this issue since last post? or had you given up? I am experiencing the same issue but with the tmobile version running cmremix rooted.... at least it was...

Boot loop problem! Help me

Hello! I've a problem with my Note 4 Sprint. The phone is in a boot loop state, it reebots every time when the logo "Samsung Galaxy Note 4" is showed. I've tried everithing! When I flashed stock roms it reboots again. When I try to install custom rom it says error 7 set_perm failed. I want to say that in each custom recovery I've installed, the touch screen is misaligned and to press a button I've to touch it 1 or 2 cm up!
Sometimes after flashing a stock rom, it pass the Note 4 logo, but when on the screen there is the "SAMSUNG" logo it reboots again and again and again.... when it reach SAMSUNG logo a strange thing happen... the pixels on the screen are showed badly such as rainbow.
In the download mode the Binary status is Samsung official and the system status is custom (also with stock rom).
I don't know to do. Can you help me? I've tried JIG also.
Thank you!
Your touch is off because you've flashed wrong custom recovery. Check that and reinstall correct one. As long as you have flashed a recent stock tar, when you can get a successful boot, open dialer and dial *#2663# and select the top left option to reinstall TSP FW update (General). If that doesn't work, reinstall the stock tar and auto boot and promptly fix that with dialer code.
The recovery flash error you're getting could be caused wiping system or flashing with mounted system partition. If you do either of those, unmount system and reboot recovery before trying to flash.
The boot loop could be caused by loss of root but custom kernel is currently installed or incompatible our corrupt data. Did you install custom kernel and wipe data or previously install CM or Xposed framework before the bootloops started?
You may need to factory reset and wipe internal memory to get it to boot. Try that with custom ROM again. You typically don't have to wipe system or mount it unless you have a problem. Many custom ROMs I've seen in our forum wipe system in updater-script(s) before installing ROM.
Here's the TWRP recovery for Sprint Note 4 for Odin flashing.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Sent from my SM-N910P using Tapatalk
Thank you
Thank you for your reply. First to fix the touch, I've to boot the phone. Why flashing his stock ROM (Full, with boot, kernel ecc... ) it doesn't boot?
When I flash 5.1.1 in his stock recovery it says dm-verify verification failed, when I flash a 6.0.1 stock ROM it says dm-verify verification failed and also to install first DRK!! I've not success to downgrade the phone to 5.0.1 or 4.4.4 because Odin stop me.
kaddhuzzu93 said:
Thank you for your reply. First to fix the touch, I've to boot the phone. Why flashing his stock ROM (Full, with boot, kernel ecc... ) it doesn't boot?
When I flash 5.1.1 in his stock recovery it says dm-verify verification failed, when I flash a 6.0.1 stock ROM it says dm-verify verification failed and also to install first DRK!! I've not success to downgrade the phone to 5.0.1 or 4.4.4 because Odin stop me.
Click to expand...
Click to collapse
If you can recall the update you had on your phone before you first attempted to flash the older stock tars that wouldn't flash, I'd recommend you get that specific stock tar, verify md5 against zip if you get it from our general forum with uploads to AFH.
After verifying md5, extract the tar.md5 for Odin flash. Factory reset in stock recovery if still on it. Odin TWRP and wipe internal memory and then power down. Pull battery for at least 30 seconds while draining power circuit by gently pressing and holding power button down.
Install battery and boot to download mode. Verify your phone's display indicates that reactivation lock is off. Ensure when connecting USB in download mode that Odin indicates COM as added. Once you have md5 verified and COM added displayed in Odin log, start the flash with Odin default options.
It should boot and stock recovery shouldn't indicate dm-verity failure.
Above, I suggested the update you had before the older tar wouldn't flash because you've most likely triggered a factory reset protection condition. I wouldn't advise flashing stock tars below OG5 because the bootloader in Android 5.1 and up block downgrade to 4.4 and 5.0 lower security bootloaders. This started with OE1 do that one and OF5 may still work but differ from OG5 and up. There is a way to run KitKat but Odin won't do that and your bootloader should remain on the higher security ones to avoid issues like yours. The OG5 to OK1 custom kernel should work with the KitKat ROMs, allowing it to boot.
If the recommended steps above doesn't reset the dm-verity, Chainfire may help; flashing systemless SuperSU zip and using the SuperSU app once booted to fully un-root may clear the dm-verity failure if wiping and flashing doesn't. Warning: unless you have stock kernel, fully un-root may leave you in a bootloop state until flashing SuperSU zip again. But if it doesn't boot after stock tar, you may have to try Chainfire Auto Root for Note 4 to root (make sure you have the latest by downloading again- Chainfire Auto Root for KitKat shouldn't be used. Hopefully it boots if you've had boot issues up to this point. Otherwise, Chainfire may not help. If still not booting, factory reset and try the stock tar again. Sometimes, flashing the stock tar a second time helps.
Wiping everything but extSdCard in TWRP before flashing stock tar is another option you may consider. I think I read one poster had thought that accidentally restoring an old EFS backup had started his dm-verity issue. Take notes and share what works if you resolve it. Best wishes for success.
Sent from my SM-N910P using Tapatalk
samep said:
If you can recall the update you had on your phone before you first attempted to flash the older stock tars that wouldn't flash, I'd recommend you get that specific stock tar, verify md5 against zip if you get it from our general forum with uploads to AFH.
After verifying md5, extract the tar.md5 for Odin flash. Factory reset in stock recovery if still on it. Odin TWRP and wipe internal memory and then power down. Pull battery for at least 30 seconds while draining power circuit by gently pressing and holding power button down.
Install battery and boot to download mode. Verify your phone's display indicates that reactivation lock is off. Ensure when connecting USB in download mode that Odin indicates COM as added. Once you have md5 verified and COM added displayed in Odin log, start the flash with Odin default options.
It should boot and stock recovery shouldn't indicate dm-verity failure.
Above, I suggested the update you had before the older tar wouldn't flash because you've most likely triggered a factory reset protection condition. I wouldn't advise flashing stock tars below OG5 because the bootloader in Android 5.1 and up block downgrade to 4.4 and 5.0 lower security bootloaders. This started with OE1 do that one and OF5 may still work but differ from OG5 and up. There is a way to run KitKat but Odin won't do that and your bootloader should remain on the higher security ones to avoid issues like yours. The OG5 to OK1 custom kernel should work with the KitKat ROMs, allowing it to boot.
If the recommended steps above doesn't reset the dm-verity, Chainfire may help; flashing systemless SuperSU zip and using the SuperSU app once booted to fully un-root may clear the dm-verity failure if wiping and flashing doesn't. Warning: unless you have stock kernel, fully un-root may leave you in a bootloop state until flashing SuperSU zip again. But if it doesn't boot after stock tar, you may have to try Chainfire Auto Root for Note 4 to root (make sure you have the latest by downloading again- Chainfire Auto Root for KitKat shouldn't be used. Hopefully it boots if you've had boot issues up to this point. Otherwise, Chainfire may not help. If still not booting, factory reset and try the stock tar again. Sometimes, flashing the stock tar a second time helps.
Wiping everything but extSdCard in TWRP before flashing stock tar is another option you may consider. I think I read one poster had thought that accidentally restoring an old EFS backup had started his dm-verity issue. Take notes and share what works if you resolve it. Best wishes for success.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you again, I've tried to do what you say me. The phone is still in boot loop, when I flashed the first time CF Auto Root it stops in half of the process. And on the display of download mode it's appeared "Set Warranty Bit: cache" (yellow), while Odin shows Cache instead of Pass and the log report RQT_CLOSE !!. Can I try anything else?
kaddhuzzu93 said:
Thank you again, I've tried to do what you say me. The phone is still in boot loop, when I flashed the first time CF Auto Root it stops in half of the process. And on the display of download mode it's appeared "Set Warranty Bit: cache" (yellow), while Odin shows Cache instead of Pass and the log report RQT_CLOSE !!. Can I try anything else?
Click to expand...
Click to collapse
Which stock tar are you flashing?
Can you copy paste the Odin log? What does phone display?
The Chainfire Auto Root should only be flashed over stock recovery. Recommended after stock tar flash.
Sent from my SM-N910P using Tapatalk
samep said:
Which stock tar are you flashing?
Can you copy paste the Odin log? What does phone display?
The Chainfire Auto Root should only be flashed over stock recovery. Recommended after stock tar flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
With OG5 (5.1.1) stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display a black screen with a little robot and a progress bar. When the progress bar reaches the half, the phone reboots and on the "Samsung Galaxy Note 4" logo it continue to reboot again and it goes in bootloop...
With PC1 or other 6.0.1 stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_N910PVPU4DPC1_N910PSPT4DPC1_CL7381751_QB8794358_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> carrier.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display "Installing system update" and when the progress bar is about 30% the sentence chage to "Erasing...". Then a red sentence appear: "Device does not have DRK, please install DRK first. Press any button?". When I press a button after a minute it goes on recovery screen with these logs:
Supported API: 3
Installing package
finding update package
opening update package
verifying update package
Installing update...
Successfully installed package.
Wiping data..
Formatting /data
Formatting /cache
Set Factory reset done
Copying media files
preload checkin
Data wipe complete
(Success)
Appling Multi -CSC
Applied the CSC-code: XAS
Successfully applied multi-CSC
Set Factory Reset done
Copying media files
preload checkin
Device does not have DRK (Device Root Key), contact to SW PL
Please flash ENG binary then install DRK
When i reboot the phone it continue to boot loop...
kaddhuzzu93 said:
With OG5 (5.1.1) stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display a black screen with a little robot and a progress bar. When the progress bar reaches the half, the phone reboots and on the "Samsung Galaxy Note 4" logo it continue to reboot again and it goes in bootloop...
With PC1 or other 6.0.1 stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_N910PVPU4DPC1_N910PSPT4DPC1_CL7381751_QB8794358_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> carrier.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display "Installing system update" and when the progress bar is about 30% the sentence chage to "Erasing...". Then a red sentence appear: "Device does not have DRK, please install DRK first. Press any button?". When I press a button after a minute it goes on recovery screen with these logs:
Supported API: 3
Installing package
finding update package
opening update package
verifying update package
Installing update...
Successfully installed package.
Wiping data..
Formatting /data
Formatting /cache
Set Factory reset done
Copying media files
preload checkin
Data wipe complete
(Success)
Appling Multi -CSC
Applied the CSC-code: XAS
Successfully applied multi-CSC
Set Factory Reset done
Copying media files
preload checkin
Device does not have DRK (Device Root Key), contact to SW PL
Please flash ENG binary then install DRK
When i reboot the phone it continue to boot loop...
Click to expand...
Click to collapse
The OG5 Odin flash looks normal to me and didn't have the drk issue. That may be the one you need but did you factory reset and try to boot when it didn't boot? Did you try anything else after that before trying PC1?
What wipes have you done so far? Flashing OG5 after PC1 means you should factory reset before flashing OG5 at the very least. I usually wipe internal memory too.
Think of it this way... If you have factory reset protection blocking the Odin flash, you should get it bypassed using TWRP to wipe everything but extSdCard and powering down, pull battery and flash same stock tar that last successfully flashed. Was it OG5? The update in question could have been Odin flash or OTA and would have most likely been the last update that ran normally. Flashes since may not have taken. PC1 Odin flash doesn't seem normal because of the drk issue.
There is a factory reset protection bypass method using UTG and a downloaded file but that method is only required if you had reactivation lock enabled or and wiped system and data and tried to flash a different update and couldn't recall your Google account or original password. IIRC, flashing the same update and using the same Google account and password wouldn't require the bypass. That also requires an ability to boot to bypass anyway.
It's a theory this same factory reset protection gets activated by trying to downgrade the bootloader. The difference being an inability to flash in Odin and auto boot. I think the steps were to wipe everything but extSdCard, power down, pull battery and flash same update in Odin and use same Google account and password. Effectively, you're breaking Odin flash capability and not really flashing until you get the steps right. Once you satisfy that, Odin and OTA updates should work again.
There may be a way to get it going but I haven't seen these requirements lately: flashing parts of the stock tar and then flashing whole tar or using KIES emergency recovery to flash stock tar.
I'd suggest trying the wipes with the right stock tar first. Seems it should boot with a factory reset or factory reset and wipe internal memory. Like I said before, sometimes just flashing the stock tar again after factory reset works (flash tar, boot fails, factory reset on stock recovery, if boot fails again, flash same stuck tar again).
Sent from my SM-N910P using Tapatalk
samep said:
The OG5 Odin flash looks normal to me and didn't have the drk issue. That may be the one you need but did you factory reset and try to boot when it didn't boot? Did you try anything else after that before trying PC1?
What wipes have you done so far? Flashing OG5 after PC1 means you should factory reset before flashing OG5 at the very least. I usually wipe internal memory too.
Think of it this way... If you have factory reset protection blocking the Odin flash, you should get it bypassed using TWRP to wipe everything but extSdCard and powering down, pull battery and flash same stock tar that last successfully flashed. Was it OG5? The update in question could have been Odin flash or OTA and would have most likely been the last update that ran normally. Flashes since may not have taken. PC1 Odin flash doesn't seem normal because of the drk issue.
There is a factory reset protection bypass method using UTG and a downloaded file but that method is only required if you had reactivation lock enabled or and wiped system and data and tried to flash a different update and couldn't recall your Google account or original password. IIRC, flashing the same update and using the same Google account and password wouldn't require the bypass. That also requires an ability to boot to bypass anyway.
It's a theory this same factory reset protection gets activated by trying to downgrade the bootloader. The difference being an inability to flash in Odin and auto boot. I think the steps were to wipe everything but extSdCard, power down, pull battery and flash same update in Odin and use same Google account and password. Effectively, you're breaking Odin flash capability and not really flashing until you get the steps right. Once you satisfy that, Odin and OTA updates should work again.
There may be a way to get it going but I haven't seen these requirements lately: flashing parts of the stock tar and then flashing whole tar or using KIES emergency recovery to flash stock tar.
I'd suggest trying the wipes with the right stock tar first. Seems it should boot with a factory reset or factory reset and wipe internal memory. Like I said before, sometimes just flashing the stock tar again after factory reset works (flash tar, boot fails, factory reset on stock recovery, if boot fails again, flash same stuck tar again).
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I can try again...
I tried every firmware in this page (https://www.sammobile.com/firmwares/database/SM-N910P/SPR/) from 5.1.1 to up with the same result as logged to you ( also wiping everything but extSD ).
I let you to know about my next tries...
With OK1 firmware (the latest of 5.1.1) it remains on Samsung Galaxy Note 4... but it doesn't proceed to boot... I'm going to leave in this situation and wait to boot...
My Note 4 started shutting down at 40% battery and then boot looping. I replaced the battery, and it worked fine after that.
Examine your battery to see if it's swelling up at all. Look at the side of the phone to see if anything is bulging. Even if it isn't swelling, it could still be your battery, but that's one thing to check.
I know it sounds weird that it would be the battery, but I'm not the only one who has experienced this, and fixed it with a new battery.

Categories

Resources