Related
For those who are stuck in the "Brickloop" after restoring a backup in TWRP. See "Edit 2"...
____________________________
Edit : This seems to be the fix.. Worked for me and others who have tried .. :thumbup:
1. Install Stock firmware via Odin, then re-run auto-root (to regain root of course)
2. Install TWRP 2.6.3.2 via odin, reboot to recovery.
3. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...
Gotta love the XDA community !!!:highfive:
Edit 2
You can also try just running Commands via TWRP before using Odin to revert to stock, re-rooting etc..Worked for me while I was doing some restore testing with Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run.
Clear the box, type the following command
mkdir /efs
Hit Go - The command will run.
Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the directions.
Also, if you plan on flashing custom ROM's after getting out of the loop, use TWRP ver 2.6.3.1.
Updated : Please see updated TWRP thread for latest information regarding release Version. 2.3.6.8
Steve Lazarus said:
Just trying to provide a thread for those of us "Early Adopters" that have encountered the boot loop issue trying to restore in TWRP 2.6.3.1
If anyone has any crazy ideas they would like me to try to resolve this issue, please let me know. I encountered the Boot Loop this morning trying to restore a backup, nothing will fix it, Odin, Re-Flash etc... NOTHING to this point will resolve the issue. I have been in contact and walked through various attempts by some great folks (Dev's here) with no luck as yet...
Early adopters please be advised to download the newest release 2.6.3.2, I can not vouch for that release as my phone is currently in a soft brick state
Let's get this figured out !!! My guess is we need a stock PIT file, anyone have one laying around ??
Click to expand...
Click to collapse
you try this to help you http://www.youtube.com/watch?v=0U3x9f_0qLM&list=FLzlWiSvUo6qQhHdETAHc7vQ&index=1
how did yours get soft bricked again sorry?
chrisa887 said:
you try this to help you http://www.youtube.com/watch?v=0U3x9f_0qLM&list=FLzlWiSvUo6qQhHdETAHc7vQ&index=1
how did yours get soft bricked again sorry?
Click to expand...
Click to collapse
Trying to "Restore" a backup this morning....
Got another one coming, so I have this one to experiment on for fixes for a couple day's. Hopefully we can get it figured out... Seems to be a partition issue (my guess anyway), need to get a stock PIT file to flash in Odin, at least we can see if that's it..? Rule it out, or determine it's the culprit.
That's such a bummer. Keeping an eye on this thread and will report anything i find. 4th one I've seen..
Have there been any reports of this on ATT or other versions?
Sent from my SM-N900T using Tapatalk 4
Steve Lazarus said:
Trying to "Restore" a backup this morning....
Got another one coming, so I have this one to experiment on for fixes for a couple day's. Hopefully we can get it figured out... Seems to be a partition issue (my guess anyway), need to get a stock PIT file to flash in Odin, at least we can see if that's it..? Rule it out, or determine it's the culprit.
Click to expand...
Click to collapse
can you get it into download mode
Steve Lazarus said:
Just trying to provide a thread for those of us "Early Adopters" that have encountered the boot loop issue trying to restore in TWRP 2.6.3.1 as to avoid cluttering up that thread with our issue.
If anyone has any crazy ideas they would like me to try to resolve this issue, please let me know. I encountered the Boot Loop this morning trying to restore a backup, nothing will fix it, Odin, Re-Flash etc... NOTHING to this point will resolve the issue. I have been in contact and walked through various attempts by some great folks (Dev's here) with no luck as yet...
Early adopters please be advised to download the newest release 2.6.3.2, I can not vouch for that release as my phone is currently in a soft brick state
Let's get this figured out !!! My guess is we need a stock PIT file, anyone have one laying around ??
Click to expand...
Click to collapse
When in TWRP did you go into settings and check Use rm -rf instead of formatting like AssassinsLament said to.......................................... >
chrisa887 said:
can you get it into download mode
Click to expand...
Click to collapse
Oh yeah, when I say we tried everything, WE TRIED EVERYTHING !!! Flashing stock via Odin, Relfashing TWRP through Odin and trying to install custom ROM, various portions of all of the above etc.... Think the partition needs fixed, only way to do that is with a PIT file to flash via Odin.. Does anyone know how to extract or create the stock PIT from the Note 3 ?
deeznutz1977 said:
When in TWRP did you go into settings and check Use rm -rf instead of formatting like AssassinsLament said to
Click to expand...
Click to collapse
Negative, I'll give that a try....
Steve Lazarus said:
Oh yeah, when I say we tried everything, WE TRIED EVERYTHING !!! Flashing stock via Odin, Relfashing TWRP through Odin and trying to install custom ROM, various portions of all of the above etc.... Think the partition needs fixed, only way to do that is with a PIT file to flash via Odin.. Does anyone know how to extract or create the stock PIT from the Note 3 ?
Click to expand...
Click to collapse
There are some pit file tools out there.
I believe this is what you are looking for
Heimdall Suite
http://forum.xda-developers.com/showthread.php?t=1916936
les_garten said:
There are some pit file tools out there.
Click to expand...
Click to collapse
Yep, problem is I don't know what the stock PIT looks like, phone is currently locked into handicapped mode lol
deeznutz1977 said:
When in TWRP did you go into settings and check Use rm -rf instead of formatting like AssassinsLament said to.......................................... >
Click to expand...
Click to collapse
Made it worse, didn't even get to the T-Mob splash screen, got stuck on the initial Note 3 screen... Previous attempts made it to the T-Mob splash screen, on occasion it would actually just get into the launcher when I'd get "System Process Failed" with the option to wait or cancel. Regardless of selection, or just letting it sit there for a minute, would throw it back into a boot loop...
So for this attempt
Installed TWRP via Odin
Checked rm - rf
Wiped, Factory Reset
Tried installing Darthstalker / Deodexed Stock
No Luck..
Steve Lazarus said:
Yep, problem is I don't know what the stock PIT looks like, phone is currently locked into handicapped mode lol
Click to expand...
Click to collapse
I think you would need to get someone with a TMO N3 to make one for you.
les_garten said:
I think you would need to get someone with a TMO N3 to make one for you.
Click to expand...
Click to collapse
Exactly....:good:
Just hoping someone with the know how chimes in!!!! Would be sweet !!
Steve Lazarus said:
Exactly....:good:
Just hoping someone with the know how chimes in!!!! Would be sweet !!
Click to expand...
Click to collapse
I'd be interested in doing this but won't have mine till who knows when with Negri!
So I just tried another Odin reflash, out of curiosity, while I was watching the messages in Odin, it say's "Get PIT for mapping" does it always say that, or is it telling me that's the problem. Just that I've never reviewed everything that comes up in that window before...
Steve Lazarus said:
So I just tried another Odin reflash, out of curiosity, while I was watching the messages in Odin, it say's "Get PIT for mapping" does it always say that, or is it telling me that's the problem. Just that I've never reviewed everything that comes up in that window before...
Click to expand...
Click to collapse
Did it work
Sent from my SM-N900T using Tapatalk now Free
Hello,
Same problem here on N9005 after restore
Hayaa said:
Hello,
Same problem here on N9005 after restore
Click to expand...
Click to collapse
Hey and welcome to the family !!!
But seriously, bummer and hopefully we'll get it sorted eventually. I truly am sorry!!!
chrisa887 said:
Did it work
Sent from my SM-N900T using Tapatalk now Free
Click to expand...
Click to collapse
Nope, same sheet...
http://forum.xda-developers.com/showthread.php?t=2026569
I followed all of the instructions on the above link and after using odin my phone won't boot in clock work mod recovery. it only boots in the android system recovery and I didn't realize it at first and ended up clicking apply update from external storage and then chose the "CWM-SuperSU-v0.97.zip and when my phone rebooted it was wiped.
Odin passes so why is clock work mod recovery not working? please help
I also followed these instructions:
http://video.search.yahoo.com/video...c=2&sigr=11a718jq9&sigt=116j41687&age=0&&tt=b
rebecca928 said:
http://forum.xda-developers.com/showthread.php?t=2026569
I followed all of the instructions on the above link and after using odin my phone won't boot in clock work mod recovery. it only boots in the android system recovery and I didn't realize it at first and ended up clicking apply update from external storage and then chose the "CWM-SuperSU-v0.97.zip and when my phone rebooted it was wiped.
Odin passes so why is clock work mod recovery not working? please help
I also followed these instructions:
http://video.search.yahoo.com/video/play;_ylt=A2KLqIRlQI5SphoAIkX7w8QF;_ylu=X3oDMTByN2RnbHFoBHNlYwNzcgRzbGsDdmlkBHZ0aWQDBGdwb3MDMw--?p=how+to+root+galaxy+note+2+att&vid=2388eab99f70408a6b22d9a0083af7d6&l=8%3A24&turl=http%3A%2F%2Fts2.mm.bing.net%2Fth%3Fid%3DV.5053124652827001%26pid%3D15.1&rurl=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dw7zGq_-gFlE&tit=How+to+Root+the+AT%26amp%3BT+Galaxy+Note+2&c=2&sigr=11a718jq9&sigt=116j41687&age=0&&tt=b
Click to expand...
Click to collapse
If you don't have root do this first,
http://forum.xda-developers.com/showthread.php?t=1980644
Then do this to install CWM
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
jibust said:
If you don't have root do this first,
http://forum.xda-developers.com/showthread.php?t=1980644
Then do this to install CWM
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
Click to expand...
Click to collapse
I followed all of the instructions here
http://forum.xda-developers.com/showthread.php?t=1980644
and then installed root checker and it still says I am not rooted :-/
rebecca928 said:
I followed all of the instructions here
http://forum.xda-developers.com/showthread.php?t=1980644
and then installed root checker and it still says I am not rooted :-/
Click to expand...
Click to collapse
I followed them to the letter and was rooted in 1 minute.
See if there is something you are skipping,make sure you have the latest PC drivers
Your not rooted. Reroot using odin 3.0.9 you might need to reinstall stock rom. If you read skynote thread your answer is there as well as download links... your welcome
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I re-ran odin and I am now rooted, my phone wasn't in debug mode... and the instructions didn't say that but I tried it and it worked.
Now my problem is when I try to start my phone in recovery mode the galaxy note logo flickers up and down the screen and the phone completely goes dead and i have to take out the battery to get it to start again. I have followed both sets of instructions to a T for clock work mod recovery and it hasn't worked.
And on the clock work mod recovery instructions, now when I click to download it it says failed download error...
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
I re-installed clock work mod recov 4 times and still when I try to start in recovery mode the screen flickers n theres lines across the screen n then the phone goes dead and I have to pull the battery to restart.
rebecca928 said:
I re-installed clock work mod recov 4 times and still when I try to start in recovery mode the screen flickers n theres lines across the screen n then the phone goes dead and I have to pull the battery to restart.
Click to expand...
Click to collapse
Try it with TWRP
http://tinyw.in/16LP
I installed that but it is an image file and odin will not open an image file?
Is it the same instructions to run this as it is to run cwm?
It says it needs to converted to a .tar file. How do I do that?
rebecca928 said:
I installed that but it is an image file and odin will not open an image file?
Is it the same instructions to run this as it is to run cwm?
Click to expand...
Click to collapse
The link I provided is for the tar file. If you downloaded it do not extract it.
Look here, end of the page
http://teamw.in/project/twrp2/124
Maybe this doesn't apply to you, or maybe it's too late, but some flavors of Samsung Android 4.x have a file to restore stock recovery at boot.
With the phone rooted and a root capable file explorer like Root Explorer or ES File Explorer look in the /etc directory. If there is a file in there called install-recovery.sh rename it and then try re installing cwm or twrp.
oldnoob said:
Maybe this doesn't apply to you, or maybe it's too late, but some flavors of Samsung Android 4.x have a file to restore stock recovery at boot.
With the phone rooted and a root capable file explorer like Root Explorer or ES File Explorer look in the /etc directory. If there is a file in there called install-recovery.sh rename it and then try re installing cwm or twrp.
Click to expand...
Click to collapse
I tried this and I still have the same problem. When I try to start in recovery mode the samsung galaxy logo flickers and the phone shuts off n then I have to pull the battery to reboot.
:-/
jibust said:
The link I provided is for the tar file. If you downloaded it do not extract it.
Look here, end of the page
http://teamw.in/project/twrp2/124
Click to expand...
Click to collapse
I clicked on the link and then went to end of the page to download for Odin, but when you click on that link there are a million different files, I just want to make sure I am clicking on the right one. Dont want to brick my phone. Is there a difference between all of the different files?
openrecovery-twrp-2.6.3.1-t0lteatt.img.tar.EjYLF6
is that the correct file?
Ok so I got TWRP installed.
Next question, I have been out of the loop for a few years so how do I get the latest firmware? Right now I have Android Version 4.1.2 and baseband version I317UCAMH3.
Is that the latest for the galaxy note 2? I have att and its the SGH I317
I didnt even plan to f with my phone but the other day my phone glitched and erased 300 pictures and videos from my newborn daughter that I just had and I was so upset and trying to find a way to recover them, someone told me to root my phone and try disk digger... so far I have had no luck at all with recovering anything... totally sucks and I am soooo upset!
rebecca928 said:
Ok so I got TWRP installed.
Next question, I have been out of the loop for a few years so how do I get the latest firmware? Right now I have Android Version 4.1.2 and baseband version I317UCAMH3.
Is that the latest for the galaxy note 2? I have att and its the SGH I317
I didnt even plan to f with my phone but the other day my phone glitched and erased 300 pictures and videos from my newborn daughter that I just had and I was so upset and trying to find a way to recover them, someone told me to root my phone and try disk digger... so far I have had no luck at all with recovering anything... totally sucks and I am soooo upset!
Click to expand...
Click to collapse
4.1.2 is the latest OFFICIAL AT&T build. There is an unofficial leak in the Android Development section, but I honestly don't know how it performs as I only run AOSP roms.
thanks
This method has been proven by me to work on Mac OS X, Windows 7, 8, and 8.1, plus Linux (whatever heimdall works on).
If you are reading this, you should already be frustrated as all HELL like I was the other night. No need to fear. When Odin doesn't work, Heimdall is here to rescue you. Heimdall and I stayed awake until 3 am the other night so I could throw these quick TUTs your way. Sometimes the gods don't answer, but their watchers will guide you...
There really shouldn't be a need to say this, but....
I take absolutely no responsibility for what happens to your phone. At this point you were probably already messing around with it, then Odin decided to be a prick and error all day long. If you so happen to feel that you messed up your phone more than you already had it, sorry, but still, not my fault.
Thanks:
Benjamin Dobell for Heimdall - http://forum.xda-developers.com/showthread.php?t=755265
DeezNutz1977 - Original 4.3 Build
allenjthomsen - KK Build files
Phil5739 - Philz CWM Advanced Recovery
bigbiff - twrp always in progress
dragonstalker - for his ROMS and contributions.
ghibli3 - for this guide which allowed me to pull and edit the KK pit file successfully.
There were a ton of threads I read through, I cant remember them all, but thanks pretty much goes out to all who contribute here. The XDA community is great!
Bootloop Recovery Heimdall Guide
The above guide will help you to recover your phone using heimdall. This is not a heimdall tutorial. For those instructions please see the heimdall website and read their instructions. I am posting this to help those that may be stuck in a similar situation as I was. Plus the presentation counts towards my "communications" class. The text guide is below...
Download 4.3 JB Recovery Zip Here
Upload for 4.4.2 in progress
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on flash tab after successfully detected.
5. In the pit section, choose the pit file I provided.
6. Click add in the partitions box to the right > Select BOOT
7. Select the boot.img file provided
8. Click add in the partitions box again to the right > Select CACHE
9. Select the cache.img.ext4 file provided.
10. Click the add in the partitions box again > Select RECOVERY
11. Select the recovery provided (you can probably use any recovery, but provided is twrp 2.6.3.7) <-- this will trip knox if you haven't already done so.
12. Make sure no reboot is checked
13. The phone may flash all the way to the end and error out. If this is the case, proceed with steps 14 and 15. If not, proceed to step 16.
14. **Pull battery
15. **Replace
16. Boot to recovery, and re-install your backup (or another ROM, whatever).
If anyone has a mirror, feel free to share as necessary.
Stock Restore Heimdall Guide
The above guide will help those restore to stock MI7 via Heimdall. If you were in the same situation I was in, this will help tremendously as odin would not help me out in the least.
Download Stock JB MI7 here.
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on Load Package tab after successfully detected.
5. Click browse and choose the file (tar.gz) you downloaded.
6. After the package loads, click the "load/customize" button on the bottom right corner.
7. Click on the flash tab afterwards.
8. Ensure repartition, no reboot, and resume checkboxes are not checked.
9. Click on the "start" button in the lower right hand corner... Profit?
** Continue here only if phone does not take the first time.
10. If you receive a libusb error, consult Heimdall instructions for fix... try, try again.
Again, mirrors and sharing are encouraged.
noobtoob said:
This method has been proven by me to work on Mac OS X, Windows 7, 8, and 8.1, plus Linux (whatever heimdall works on).
If you are reading this, you should already be frustrated as all HELL like I was the other night. No need to fear. When Odin doesn't work, Heimdall is here to rescue you. Heimdall and I stayed awake until 3 am the other night so I could throw these quick TUTs your way. Sometimes the gods don't answer, but their watchers will guide you...
There really shouldn't be a need to say this, but....
I take absolutely no responsibility for what happens to your phone. At this point you were probably already messing around with it, then Odin decided to be a prick and error all day long. If you so happen to feel that you messed up your phone more than you already had it, sorry, but still, not my fault.
Bootloop Recovery Heimdall Guide
http://youtu.be/-huMP5ZaMiw
The above guide will help you to recover your phone using heimdall. This is not a heimdall tutorial. For those instructions please see the heimdall website and read their instructions. I am posting this to help those that may be stuck in a similar situation as I was. Plus the presentation counts towards my "communications" class. The text guide is below...
Download this First: https://www.dropbox.com/s/oc534gzr5usbivi/BootLoop Recovery.zip
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on flash tab after successfully detected.
5. In the pit section, choose the pit file I provided.
6. Click add in the partitions box to the right > Select BOOT
7. Select the boot.img file provided
8. Click add in the partitions box again to the right > Select CACHE
9. Select the cache.img.ext4 file provided.
10. Click the add in the partitions box again > Select RECOVERY
11. Select the recovery provided (you can probably use any recovery, but provided is twrp 2.6.3.7)
12. Make sure no reboot is checked
13. The phone may flash all the way to the end and error out. If this is the case, proceed with steps 14 and 15. If not, proceed to step 16.
14. **Pull battery
15. **Replace
16. Boot to recovery, and re-install your backup (or another ROM, whatever).
If anyone has a mirror, feel free to share as necessary.
Stock Restore Heimdall Guide
http://youtu.be/hXtZDUD7MYQ
The above guide will help those restore to stock MI7 via Heimdall. If you were in the same situation I was in, this will help tremendously as odin would not help me out in the least.
Download this First: https://www.dropbox.com/s/m9dpb7ya0umvrzl/Stock_SM-N900T_MI7.tar.gz
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on Load Package tab after successfully detected.
5. Click browse and choose the file (tar.gz) you downloaded.
6. After the package loads, click the "load/customize" button on the bottom right corner.
7. Click on the flash tab afterwards.
8. Ensure repartition, no reboot, and resume checkboxes are not checked.
9. Click on the "start" button in the lower right hand corner... Profit?
** Continue here only if phone does not take the first time.
10. If you receive a libusb error, consult Heimdall instructions for fix... try, try again.
Again, mirrors and sharing are encouraged.
Click to expand...
Click to collapse
Won't download right now...too much traffic. It looks like almost everyone wants to download this lol...
kuroy301 said:
Won't download right now...too much traffic. It looks like almost everyone wants to download this lol...
Click to expand...
Click to collapse
Seriously? I just put this up. Any mirror suggestions? I don't really post/share much since I started school a year ago.
Edit: Only 3 views, must be from the youtube videos...LOL. I will search for a mirror.
Dropbox sharing has been denied due to bandwidth usage. Uploading to mediafire now. Should be up in about 2 hours. Sorry everyone.
EDIT: OP Updated, new links added. Hope you all get the help needed.
Heimdall install
Hello
I use windows8.1 and I amunable to instal lHeimdall. I installed the C++ and yet still giving msvcp110.dll Anyoneexperiencing this?I really need this solution. My GN3 is loopboot many days. My knox this 0x1 and I cannot flash a rom that in no loopboot.
help
Fates_Warning said:
Hello
I use windows8.1 and I amunable to instal lHeimdall. I installed the C++ and yet still giving msvcp110.dll Anyoneexperiencing this?I really need this solution. My GN3 is loopboot many days. My knox this 0x1 and I cannot flash a rom that in no loopboot.
help
Click to expand...
Click to collapse
Have you tried installing both the 32 bit and 64 bit visual c++ applications? I installed both because i want sure which one heimdall would use.
Sent from my SM-N900T using Tapatalk
Thank you. was missing install the 32-bit. :good:
The problem is now being with the cache file. It hangs at 52% and not flash. Any ideas, my friends?
What are you flashing? The entire stock ROM, or are you doing the recovery?
Sent from my SM-N900T using Tapatalk
i tried using this and got this "ERROR: Failed to access device. libusb error: -12, can you pls send me a link where i can find out what to do next? i'm not very computer literate
jboy619 said:
i tried using this and got this "ERROR: Failed to access device. libusb error: -12, can you pls send me a link where i can find out what to do next? i'm not very computer literate
Click to expand...
Click to collapse
In the files you downloaded when you got heimdall, there is an .exe that allows you to replace the USB driver for you device. You have to follow the directions in the read me file they gave you.
You have 3 driver choices to replace the one to flash for yours. There is a windows driver, a libusb driver, and a libusb (k) driver. One of these will allow the phone to flash.
noobtoob said:
What are you flashing? The entire stock ROM, or are you doing the recovery?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
My problem is when I try to flash the file cache.ext4 in the early stages by heimdall .
Fates_Warning said:
My problem is when I try to flash the file cache.ext4 in the early stages by heimdall .
Click to expand...
Click to collapse
Need a few questions answered.
1. Are you flashing with a libusb driver from the drivers package provided by heimdall?
2. can you get into recovery as of right now? What version is it?
1a. If you are flashing without using the drivers that were provided, experiment a bit. My particular phone likes the libusbk one that is provided. See the heimdall readme file for details.
2a. If you can get into recovery right now, try to wipe cache, data, and dalviche. The try to reflash.
I don't know what kind of boot loop you are stuck in. This method may not work for you depending on what I was just asking. You may need to explore a different method to get your device up and running.
Sent from my SM-N900T using Tapatalk
noobtoob said:
Need a few questions answered.
1. Are you flashing with a libusb driver from the drivers package provided by heimdall?
2. can you get into recovery as of right now? What version is it?
1a. If you are flashing without using the drivers that were provided, experiment a bit. My particular phone likes the libusbk one that is provided. See the heimdall readme file for details.
2a. If you can get into recovery right now, try to wipe cache, data, and dalviche. The try to reflash.
I don't know what kind of boot loop you are stuck in. This method may not work for you depending on what I was just asking. You may need to explore a different method to get your device up and running.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Many thanks for the help.
The heimdall can communicate with my GN3. I can flash the boot file and the recovery usually, but not of cache.ext4. I have attached a photo of the error and heimdall. After flashing my recovery is TRWP sign that is heimdall flash and other files that not only the cache.
About My bootloop error:
My phone stock by odin installs normally. And then starts the android is giving the error "process system is not responding" and loops .. I already gave wipe with all available recovery. Have several flash stock (uk, zto, international, etc. ..) and the problem persists with any rom. Any idea?
Do not proceed from here! I just noticed you are trying to flash a sm-n900t to a sm-n9005. That is why it is not working. The recovery you are trying to flash is not meant for your phone model.
Sent from my SM-N900T using Tapatalk
Fates_Warning said:
Many thanks for the help.
The heimdall can communicate with my GN3. I can flash the boot file and the recovery usually, but not of cache.ext4. I have attached a photo of the error and heimdall. After flashing my recovery is TRWP sign that is heimdall flash and other files that not only the cache.
About My bootloop error:
My phone stock by odin installs normally. And then starts the android is giving the error "process system is not responding" and loops .. I already gave wipe with all available recovery. Have several flash stock (uk, zto, international, etc. ..) and the problem persists with any rom. Any idea?
Click to expand...
Click to collapse
See above post.
Sent from my SM-N900T using Tapatalk
Hi!
Thanks for your work!
Does it trigger KNOX please ?
noobtoob said:
See above post.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
true .. the problem is that my shows the same bootloop problem are you trying to solve?
"Local and device PIT files don't match and repartition wasn't specified!"
What's wrong ? Should I click on "repartition" ? I have also an MI7 version of the ROM. n9005 too... ????? :/
WHat about KNOX ??
Thank you
EDIT : Just saw that the open post doesn't even say it is for N900 !!!!! Please, fix this!!
thank you found the file but now i got a new challenge "ERROR: Failed to initialise protocol!"
---------- Post added at 12:54 AM ---------- Previous post was at 12:41 AM ----------
thanks found it but now i got a new challenge "ERROR: Failed to initialise protocol!" ?
Nemorensis32 said:
"Local and device PIT files don't match and repartition wasn't specified!"
What's wrong ? Should I click on "repartition" ? I have also an MI7 version of the ROM. n9005 too... ????? :/
WHat about KNOX ??
Thank you
EDIT : Just saw that the open post doesn't even say it is for N900 !!!!! Please, fix this!!
Click to expand...
Click to collapse
Do not click on repartition. Do not proceed from here if you do not have the sm-n900t. This forum is posted under the "T-Mobile Samsung Galaxy Note 3" which is the sm-n900t. It is possible for you to have this device on a different network, but you should already know what model you are trying to fix.
The .pit file in my recovery zip will not work for you because the phone is not the same. Please go to your respective forum, and look for the files there.
Knox will trip if you flash the recovery I provided.
Sent from my SM-N900T using Tapatalk
jboy619 said:
thank you found the file but now i got a new challenge "ERROR: Failed to initialise protocol!"
---------- Post added at 12:54 AM ---------- Previous post was at 12:41 AM ----------
thanks found it but now i got a new challenge "ERROR: Failed to initialise protocol!" ?
Click to expand...
Click to collapse
Try using libUSB, and libUSBk drivers. Mine specifically likes the libusbk. But every phone is different. I believe I had the same error when trying to use the win32 and the libusb drivers.
Other than that, it may be a heimdall issue that I am unfamiliar with.
EDIT: Also I should mention, when mine did all of this, I had to use the recovery zip first, then move onto the stock restore portion. I can't necessarily say why I had to, but I did. If you already have knox tripped, I recommend doing that. While in recovery, I performed an advanced wipe. Wiped system, cache, dalvik and internal storage. The internal storage part may not be necessary, but I wanted to start fresh.
Sent from my SM-N900T using Tapatalk
ok so i recently updated to cm 10.2rc2(or1 i dont remember) and ever sinc then ive been having trouble then when i was the new update i decided to update to that using cyanogenmod installer but about half way through an error occurred causing my phone to go into a boot loop i cannot boot into recovery because when i try it all it says is the tiny blue text in the corner and then it stays stuck on the cyanogenmod mascot when i try to connect it to my computer it makes the noise but it does not recognize it anymore until i go into download mode and i was wondering if i could reflash cyanogenmod again using odin? another thing is that somehow the cm installer let me use it again but this time it wanted me to re-tick the usb debugging box and i cant because like a said its stuck in a boot loopif you can please send me a link to the files i must download to fix my phone and thank you so much for reading this !!
You could go here [ROM][ODIN][TAR]SPH-L710 MD4 (MD4 Modem/Kernel/ROM - Stock): http://www.sxtpdevelopers.com/showthread.php?t=233 to get the one click odin file, download the EXE (might want to start with the rooted MD4 to save a few steps) then you can try to reflash CM afterwards
how?
jdelano said:
You could go here [ROM][ODIN][TAR]SPH-L710 MD4 (MD4 Modem/Kernel/ROM - Stock) to get the one click odin file, download the EXE (might want to start with the rooted MD4 to save a few steps) then you can try to reflash CM afterwards
Click to expand...
Click to collapse
i want to thank you for atleast replying to this since just one guy at the cyanogenmod forums replied but with the wrong information and i wanted to ask how do i do this can you detail this for me since im sort of a noob at this and i usually dont read up in things before i do it (witch i should start doing) so can you send me the link to the rooted md4 file??? please reply quick my phone is used for many things in my daily life especially school and my calender
krozz00 said:
i want to thank you for atleast replying to this since just one guy at the cyanogenmod forums replied but with the wrong information and i wanted to ask how do i do this can you detail this for me since im sort of a noob at this and i usually dont read up in things before i do it (witch i should start doing) so can you send me the link to the rooted md4 file??? please reply quick my phone is used for many things in my daily life especially school and my calender
Click to expand...
Click to collapse
That link there has all the instructions and files you need.
Basically you'll download the 2nd file (the exe version) under the heading "nodata" versions.
then follow the step by step instructions on that page.
you should be good to go.
just to sum it up
jdelano said:
You could go here [ROM][ODIN][TAR]SPH-L710 MD4 (MD4 Modem/Kernel/ROM - Stock): to get the one click odin file, download the EXE (might want to start with the rooted MD4 to save a few steps) then you can try to reflash CM afterwards
Click to expand...
Click to collapse
so when you say try that means theres a chance it might not work?
can you help me if it doesnt work ? have you had problems like this before? whats MOAR rom like ? and what do you suggest for later updates and android maintenance? thanks for the help just answerr those and ill press the thanks button for you !! ps what does nodata version mean?
editing again because i read it and it said that on user version kept my data what data? and do i just skip the other steps and go directly to download mode because i cant do the other steps cause of the boot loop and do i download the modem/kernel or no??
harmful
krozz00 said:
so when you say try that means theres a chance it might not work?
can you help me if it doesnt work ? have you had problems like this before? whats MOAR rom like ? and what do you suggest for later updates and android maintenance? thanks for the help just answerr those and ill press the thanks button for you !! ps what does nodata version mean?
editing again because i read it and it said that on user version kept my data what data? and do i just skip the other steps and go directly to download mode because i cant do the other steps cause of the boot loop and do i download the modem/kernel or no??
Click to expand...
Click to collapse
i downloaded it and my computer said windows protected my pc
I ran into the boot loop early today when I tried to install CM10.2 via the windows installer.
All I could do was to get the phone to boot into "download mode". However, ODIN wasn't recognizing that my phone was plugged in.
I ended up uninstalling and re-installing the Samsung USB drivers.
When I plugged in my phone it completed the install of the drivers,\.
ODIN then recognized my phone was connected and the "COM" lit up.
I was able to reflash TWRP recovery and get my phone to reboot in recovery and reflash the backup rom.
kev
how?
kkocken said:
I ran into the boot loop early today when I tried to install CM10.2 via the windows installer.
All I could do was to get the phone to boot into "download mode". However, ODIN wasn't recognizing that my phone was plugged in.
I ended up uninstalling and re-installing the Samsung USB drivers.
When I plugged in my phone it completed the install of the drivers,\.
ODIN then recognized my phone was connected and the "COM" lit up.
I was able to reflash TWRP recovery and get my phone to reboot in recovery and reflash the backup rom.
kev
Click to expand...
Click to collapse
where did you download the recovery and how did you do it?
krozz00 said:
where did you download the recovery and how did you do it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2011491 <- I followed this thread from skunkape
The ROMS are listed here....
http://forum.xda-developers.com/galaxy-s3-sprint#romList <- you can get the rom from here (remember to wipe the davlik-cache because I think that is what was causing mine to reboot)
You can alternatively get the CM10.2 (http://download.cyanogenmod.org/?device=d2spr) from here and copy it to your SDcard and install.
kev
thanks
kkocken said:
[ <- I followed this thread from skunkape
The ROMS are listed here....
<- you can get the rom from here (remember to wipe the davlik-cache because I think that is what was causing mine to reboot)
You can alternatively get the CM10.2 from here and copy it to your SDcard and install.
kev
Click to expand...
Click to collapse
THANKS!!! i got it working again and i thanked you and the other guy!!
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
re: md5 error
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse
Before doing anything else you need to re-download the TAR.MD5 firmware.
If you get MD5 errors it simply means that for some reason the download
had an error in it (checksum error).
You need to have a error free download of the TAR.MD5 firmware in order
to solve the issues you are having. Your phone is NOT bricked at all and all
it needs is a error free TAR.MD5 file to flash with odin and your phone will
work perfectly. You should never flash a TAR.MD5 file which has errors.
Your problem has nothing to do with the versions of the firmwares like 4.4.2
and or 4.3 you are trying to flash, it all has to do with errors during the actual
download process of the TAR.MD5 file.
Good luck!
Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.
Call me to un brick your phone
HEY CALL ME TO UNBRICK YOUR PHONE AM A REPAIR SHOP IF YOU MAIL ME THE PHONE I COULD FIX IT FOR A SMALL FEE [email protected] HAVE A GOOS DAY :fingers-crossed:
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
Click to expand...
Click to collapse
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.
blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.
Click to expand...
Click to collapse
I always ODIN flash the newest firmware, let the phone boot up, then I just ODIN flash TWRP... and then in recovery I flash my personnel rom and flash SU from chainfire...
then I just install busybox which I have a copy of all the on my sdcard, a folder I call apk files.... then I install titanium backup and restore my apps.. all done in less then 10 minutes...
when ever u think u have a problem, flash the firmware your on, or the newest, that should always fix any issues.. I have all of the versions on my site, and stock odex roms...
Silvist said:
Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.
Click to expand...
Click to collapse
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin
xxjahasotoxx said:
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin
Click to expand...
Click to collapse
I just kept trying to flash to the stock image that's in the link in my post. It kept giving me md5 errors, so I re downloaded the file until it passed. I also ran odin as administrator, which helps. I used an older version of odin, 3.5 I believe.
Everything else I tried failed, like hemdall. I did attempt it, but it failed when I tried to flash through it. I'm not really familiar with it, just followed the guide on these forums. It can supposedly do more than even odin can do, that's if you can get it to work lol.