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
Related
The problem I encountered must be the worst problem ever! For some reason my nexus reboot randomly and its not just a regular reboot but it reboot as a DEEP FREEZE. So basically once it rebooted, it goes back to a same specific point of time. I can't even delete stuff from the phone, for example if I deleted 1GB of music off my phone, after few second the phone will reboot automatically OR if i reboot the phone myself the 1GB of music would be back in my phone. Like WTH? I am completely lost. I have no idea how it happened, but I know it happened after I installed Paranoid Android AOSP 2.99 beta5. I was fine when flashing Paranoid Android 1,3,4. ALSO I cannot do a factory reset or install a factory rom. It just go back to 4.2.1 AOSP 2.99 beta5...
please guys, if anyone can help me that would be great. If you guys need more explaining please email or PM me. I will be glad to write a whole essay on what you guys need to know to help me out. Thank you
Go back to stock and start fresh.
Sent from my i9250
bk201doesntexist said:
Go back to stock and start fresh.
Sent from my i9250
Click to expand...
Click to collapse
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Yellowfriedrice said:
Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
ahmadallica said:
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
Click to expand...
Click to collapse
You cant brick a nexus! Try making a jig with this link http://www.youtube.com/watch?v=jKRrTZayRxU Then get download odin and an img file of whatever rom you want and flash it through odin. Problem should be solved.
Yellowfriedrice said:
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
khuzema9 said:
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
Click to expand...
Click to collapse
Based on the language used in the OP I think he used a toolkit to root/unlock his Nexus and that's why he knows nothing about his device and how to fix it.
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
altimax98 said:
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
Click to expand...
Click to collapse
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
still didn't work
ahmadallica said:
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
Click to expand...
Click to collapse
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Yellowfriedrice said:
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Click to expand...
Click to collapse
I really have not done anything to my GNex via Windows becuse I am using Ubuntu Linux so I have not experienced installing these drivers on Windows. I also have neither returned my phone to stock before nor used the Nexus toolkit. I am doing everything manually.
I think you are referring to the drivers in this page. If you are using Windows 8 then there are some steps mentioned on how to get pass the driver signature enforcement.
If you are on Windows 7, then look here.
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
ahmadallica said:
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
Click to expand...
Click to collapse
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Yellowfriedrice said:
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Click to expand...
Click to collapse
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
ahmadallica said:
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
Click to expand...
Click to collapse
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Yellowfriedrice said:
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Click to expand...
Click to collapse
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
ahmadallica said:
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
ahmadallica said:
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
Thank Goodness im not the only one who has this issue... Bugs the crap outta me lol..
To the OP:
Try this, 1: make sure your an admin on your PC. From the sounds of it you may not be if it said 'access denied'. 2: Plug your nexus in while in the 'device manager' section of windows. 3: Find the new device and delete it. Delete anything that says Android ADB or Android anything or galaxy Nexus or Galaxy phone. Just delete them. Windows will warn you but do it anyways... 4: reboot the pc. 5: Plug your nexus back in, it should either install the device or fail. At that point find and download the newest samsung naked drivers and use the option on windows to install driver from disk and navigate to your unzipped folder.
That is the sure fire way to get it working again. Sorry to say if you still have driver issues then your doing something wrong. Do alot of reading and the answer will show itself.
1. Can you boot your phone into fastboot mode?
2. If so, once in fastboot mode, what happens when you connect the phone to the computer?
It is very very difficult to brick a nexus, so don't worry... .
Yellowfriedrice said:
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
Click to expand...
Click to collapse
Sorry for not being able to help you better. I'm sure that others who are familiar with Windows can help you overcome your earlier issues with drivers and so on thus be able to return to stock and start fresh
Good Luck
It is very very difficult to brick a nexus said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse
OKAY i tried everything.. nothing seem to work.. selling my nexus!
Yellowfriedrice said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse
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...
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!!
Before I get linked to a thread full of geeky complicated replies, please; I already checked 4 threads & came to the conclusion I just wont understand it.
I basically rooted my phone using odin; just used the simple instructions on Max lee's website. Did the Vol up + Power Button + Home, plugged it into my laptop; clicked pda & chosen the .tar file of the note 2 (cwm6-root-note2.tar) Everything went well & my device started without any issues.
My phone works fine, but at first SuperSu would give me this message ' unfortunately supersuhas stopped' So I updated it in the playstore and now get this message 'There is no SU binary installed, this is a problem!'
Its a note II N1705 running Andriod 4.4; any help would be appreciated; I think I have to flash SuperSu or something along these lines, but hope someone can explain me how to do so.
I also read that my phone is 'technically' rooted, so I made sure to try out titanium backup which didn't work because I don't have root access.
Thanks in advance,
5parc said:
Before I get linked to a thread full of geeky complicated replies, please; I already checked 4 threads & came to the conclusion I just wont understand it.
I basically rooted my phone using odin; just used the simple instructions on Max lee's website. Did the Vol up + Power Button + Home, plugged it into my laptop; clicked pda & chosen the .tar file of the note 2 (cwm6-root-note2.tar) Everything went well & my device started without any issues.
My phone works fine, but at first SuperSu would give me this message ' unfortunately supersuhas stopped' So I updated it in the playstore and now get this message 'There is no SU binary installed, this is a problem!'
Its a note II N1705 running Andriod 4.4; any help would be appreciated; I think I have to flash SuperSu or something along these lines, but hope someone can explain me how to do so.
I also read that my phone is 'technically' rooted, so I made sure to try out titanium backup which didn't work because I don't have root access.
Thanks in advance,
Click to expand...
Click to collapse
Here is the Link to cwm recovery that you need to flash with odin 3.09.
http://galaxynote2root.com/cwm-recovery/
I think your phone is 7105 (lte), so download 1 for that. It should be a tar file.
Once it is installed, reboot to recovery and flash supersu zip using option "install zip"
Make sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.
U will find it on chainfire's Web.
Press thumps up if you found this suggestion helpful.
ceomaverick said:
Here is the Link to cwm recovery that you need to flash with odin 3.09.
I think your phone is 7105 (lte), so download 1 for that. It should be a tar file.
Once it is installed, reboot to recovery and flash supersu zip using option "install zip"
Make sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.
U will find it on chainfire's Web.
Press thumps up if you found this suggestion helpful.
Click to expand...
Click to collapse
I downloaded the .tar file? Am I going to use Odin ? Or am I going to do this by only using my phone?
'Flash supersu zip using option install zip?' What do you mean flash
'Makee sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.' You first say I need a tar file then start talking about a zip file? Am completely confused.
Explain this as if you are explaining it to a noob, I don't get it.
EDIT:
I managed to fix my problem after tons of research to translate your post to something more understandable; regardless of that! You got my upvote
5parc said:
I downloaded the .tar file? Am I going to use Odin ? Or am I going to do this by only using my phone?
'Flash supersu zip using option install zip?' What do you mean flash
'Makee sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.' You first say I need a tar file then start talking about a zip file? Am completely confused.
Explain this as if you are explaining it to a noob, I don't get it.
EDIT:
I managed to fix my problem after tons of research to translate your post to something more understandable; regardless of that! You got my upvote
Click to expand...
Click to collapse
Tons of research, really?
You are the first guy who found it difficult to understand my instructions.
Anyway, I am happy you found your way and in the process gained more knowledge.
hlp
i m also having the same trouble,n i also.dun knw wat u saying,but u nid ur hlp,i nid u to show me the step clearly pls,can?
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.