This is my first thread as a user, I have been a lurker for very long time. I have decent understanding of flashing roms on HTC one X and HP touchpad, everything learned from XDA. But I have been facing this weird issue on Unlocked Rogers Galaxy note 2.
My galaxy note 2 was all stock and few days ago when I picked it up while it was charging, phone was hanging on main screen. I simply turned off and since then its stuck in bootloop. I am only getting samsung logo screen. So far everything I have tried, it hasnt resolved the issue.
I have flashed rogers stock 4.1.2 rom from samsung-updates using ODIN, but still its stuck in bootloop. I have tried multiple recoveries Stock, Clockwork and TWRP, phone mostly reboots when I try to do a factory reset. even when I am able to complete factory reset, nothing changes. All recoveries give me errors in line of unable to mount /cache and unable to mount /data.
Right now I have flashed TWRP and it shows unable to mount /cache, and it reboots when I try to do a factory reset.
These are the exact errors
E: unable to mount "cache"
E: can't mount '/cache/recovery/command'
E: can't open '/cache/recovery/command'
E: can't mount '/cache/recovery/log'
E: can't open '/cache/recovery/log'
E: can't mount '/cache/recovery/last_log'
E: can't open '/cache/recovery/last_log'
E: can't mount '/cache/recover/last_install'
E: can't open '/cache/recover/last_install'
Please help.
If nothing else works, can anyone show me a way to hard brick? So I can send in for warranty, coz download mode shows the binary counter?
Thanks
Hi, sounds like you either have a corrupted partition on your phone or a hardware issue. I have had lots of bootloops in the past and was always been able to fix it with flashing stock software with odin. You probily going to send it in for warranrt repair.
Sent from my SGH-I317M using XDA Premium HD app
pterry30 said:
Hi, sounds like you either have a corrupted partition on your phone or a hardware issue. I have had lots of bootloops in the past and was always been able to fix it with flashing stock software with odin. You probily going to send it in for warranrt repair.
Sent from my SGH-I317M using XDA Premium HD app
Click to expand...
Click to collapse
Is there any fix for corrupted partition on note 2? I have seen threads regarding s3 but not note2.
Also if I flash Mr robinsons rom from here
http://forum.xda-developers.com/showthread.php?t=2004650
it should reset the flash counter to 0, So I can send it in for repair.
I believe to fix a bad partition you need the pit file. I think it is in the stock firmware. I have never had a issue where I could not do a factory wipe/reset. You need triangle away app from the play to reset counter. You need to be on stock software, stock recovery, stock kernel but be rooted to use triangle away
Sent from my SGH-I747 using XDA Premium HD app
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
Your issue is most likely hardware related because you were on stock software when you started having problems and you had not flashed any others software and you flashed stock software through odin and did not fix your problems
Sent from my SGH-I747 using XDA Premium HD app
I'd say try flashing a new kernel, and doing a factory reset
Edit...I re read op, and I think pit file also...
Sent from my SGH-I317M using xda premium
If that doesn't work I would definitely try flashing the pit file with the stock firmware in Odin.
Sent from my GT-N7105 using Tapatalk 2
cdshepherd said:
If that doesn't work I would definitely try flashing the pit file with the stock firmware in Odin.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
sorry for the late reply, had to leave country for few weeks. So I tried to flash stock rom (redownloaded 4.1.1 from samfirmware) again through ODIN, and its still stuck in bootloop. when I boot into stock recovery after flashing stock rom, I get "E:failed to verify whole file signature, E:signature verification failed."
Format sd card then install latest stock rom with pit file ..it wil help u
nabilsweet007 said:
Format sd card then install latest stock rom with pit file ..it wil help u
Click to expand...
Click to collapse
I havent been able to find the pit file for note 2 i317m at all. If you have links, please share.
Anyone?
prince_f_swords said:
I havent been able to find the pit file for note 2 i317m at all. If you have links, please share.
Click to expand...
Click to collapse
Bump, anyone with pit file or a way to repartition?
Pm for pit
Thanks for the pit file, but Odin gets stuck at "Get pit file for mapping". Any ideas?
Are you putting it in the pit slot in odin?
twanskys204 said:
Are you putting it in the pit slot in odin?
Click to expand...
Click to collapse
yes, here's a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know you are having bootloop issues and im not an expert by any means. However, should repartition be checked? I know typically under odin you never want that box checked but maybe in this instance you do.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
cloudraker said:
I know you are having bootloop issues and im not an expert by any means. However, should repartition be checked? I know typically under odin you never want that box checked but maybe in this instance you do.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Click to expand...
Click to collapse
well I am trying to repartition it by using pit file, as I think the errors in CWM are indicating that partition is messed up.
Ok so you have boot loops check it out,
here is list of what to grab odin version here
http://forum.xda-developers.com/showpost.php?p=33854395&postcount=2
follow those direction just insert your stock instead of cf auto root tar md5
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done
go to next post and grab cf auto root for i317m, IF your going to attempt to reboot
grab zip fro stock build http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
and un zip with 7zip
place in odin pda slot as the directions from chainfire's post, remove sd if installed and continue.
when finished let reboot and it will hang on boot ani. pull battery, go into stock recovery and format cache and factory reset, then reboot.
you should be good to go at that point. if not pm me.
riassan said:
Ok so you have boot loops check it out,
here is list of what to grab odin version here
http://forum.xda-developers.com/showpost.php?p=33854395&postcount=2
follow those direction just insert your stock instead of cf auto root tar md5
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done
go to next post and grab cf auto root for i317m, IF your going to attempt to reboot
grab zip fro stock build http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
and un zip with 7zip
place in odin pda slot as the directions from chainfire's post, remove sd if installed and continue.
when finished let reboot and it will hang on boot ani. pull battery, go into stock recovery and format cache and factory reset, then reboot.
you should be good to go at that point. if not pm me.
Click to expand...
Click to collapse
Here's what I did, downloaded stock rom I317MVLALJ2_I317MOYAALJ2_RWC
downloaded ODIN 1.85 from chainfire's post
put stock rom into PDA tab, reset time and auto reboot checked
- start flash, it Passed.
then downloaded CF auto root for I317M
- put the phone in download mode again
- put CF auto root to PDA tab, reset time and auto reboot checked
- it passed too
now I cannot get to recovery
- battery out Volume UP+power +Home
- "samsung galxy note II" logo keeps coming back
one thing I remember from before when device was on complete stock, it use to show "Samsung" logo in Bold not "Samsung Galaxy Note II"
any ideas?
prince_f_swords said:
Here's what I did, downloaded stock rom I317MVLALJ2_I317MOYAALJ2_RWC
downloaded ODIN 1.85 from chainfire's post
put stock rom into PDA tab, reset time and auto reboot checked
- start flash, it Passed.
then downloaded CF auto root for I317M
- put the phone in download mode again
- put CF auto root to PDA tab, reset time and auto reboot checked
- it passed too
now I cannot get to recovery
- battery out Volume UP+power +Home
- "samsung galxy note II" logo keeps coming back
one thing I remember from before when device was on complete stock, it use to show "Samsung" logo in Bold not "Samsung Galaxy Note II"
any ideas?
Click to expand...
Click to collapse
Anyone............
Make sure its volume up home then power
Related
Hello everyone!
This is a guide dedicated to those who are a bit noobish or new to XDA, so if you're not one, I would advise to stop reading now! (although feedback would be great! )
After my success over at the GSII's boards with over 300,000 thread views all over my threads from all sections, I believe that this board should also get some taste of my how to. I'm going to be explaining step by step what to do and how to do it, while explaining each thing.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, if you poorly flash a ROM and it results in a NAND rw corruption (NAND's read and write function corrupted) it means that it is an issue deeper than a soft brick, but still no reason to be alarmed!
When you can flash a kernel, but you can't flash a ROM due to ODIN errors, that happens because it can't properly read the NAND, but it still can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple" (just pulling and pushing folders without touching partitions), so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
__________________________________________________
IF YOU ONLY HAVE A BOOTLOOP
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
Let's start with the basic files, downloads and requirements
1) You have to know the basics of ODIN and flashing for starters!
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN v3.07, the tool that we'll use to flash all the things into our loved Galaxy Note 2 N7100!
4) Download the necessary files : the Recovery Package/ROM and the bootloader will be included in the very package. Android 4.1.2, unbranded, XXDLJ2. When you recover the phone, just update it if you want a newer version!
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip if you'd like.
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GNII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.
Which means that you CANNOT have a damaged USB, corrupted drivers and such.
When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with
But where are the files going, you say?
.PIT -> PIT
BOOTLOADER -> BOOTLOADER (or PDA if flashed alone)
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
***If you have a 1 file .tar package, then flash it in PDA***
There is only 1 way to recover a soft bricked phone. How to recover from a NAND corruption? We'll get on that later on
__________________________________________________
Recovering a soft bricked phone
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC (and the .PIT). Put each one in its place (EXCEPT the .PIT, refer to the warning below).
2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.
3) Plug in your phone. It will show you, in a blue box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
Now here, take a breath
First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5-10 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!
You deserve some cake afterwards, and some rest
Now, if your problem is the NAND rw coruption, and wasn't fixed by the above fix, then follow these steps :
WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
4) Open the zip you downloaded and find the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partition
5) Flash the recovery package, like in steps 1-4 (WITH the re-partition ticked and the .PIT file in place) and that will fix any of your issues
6) After you have recovered your phone, I advise you to have your phone completely up to date by browsing and downloading the firmware for your version through SamMobile!
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to as i9000, for his amazing collection of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.
I was wondering where I can download the recovery package? I can not seem to find a link pointing in any directions. All the help would be great. I know my way round odin an stuff but, this new problem is an new playing field for me
Buckers1313 said:
I was wondering where I can download the recovery package? I can not seem to find a link pointing in any directions. All the help would be great. I know my way round odin an stuff but, this new problem is an new playing field for me
Click to expand...
Click to collapse
Oh man, I derp'd on there! Apparently I didn't include the DL link
Will fix in a moment!
EDIT : Hmmm, the link was there all along, in the code at least... Now that was weird
Good.
This should go into general imao
this is XXXDDDAAA
Phistachio said:
Oh man, I derp'd on there! Apparently I didn't include the DL link
Will fix in a moment!
EDIT : Hmmm, the link was there all along, in the code at least... Now that was weird
Click to expand...
Click to collapse
Thanks for that. Everytime I extract the files, I don't get anything for odin just a heap of img and bin files. Am i extracting them wrong?
Buckers1313 said:
Thanks for that. Everytime I extract the files, I don't get anything for odin just a heap of img and bin files. Am i extracting them wrong?
Click to expand...
Click to collapse
You shouldn't extract them. You must put the .tar file in each box, CODE -> PDA, etc
The file which you extracted must be put in pda tab. The. Tar.md5 file. You must not extract that.
this is XXXDDDAAA
Phistachio said:
You shouldn't extract them. You must put the .tar file in each box, CODE -> PDA, etc
Click to expand...
Click to collapse
Thanks for your help. my device isnt flashing anything
just hangs at setupconnect and then fails for different reasons. might try my chances with a warranty :S
Buckers1313 said:
Thanks for your help. my device isnt flashing anything
just hangs at setupconnect and then fails for different reasons. might try my chances with a warranty :S
Click to expand...
Click to collapse
Tell me exactly what you're doing, step by step.
Phistachio said:
Tell me exactly what you're doing, step by step.
Click to expand...
Click to collapse
downloaded the zip
unzipped (all correct tar files where there and the pit)
Opened odin and placed each tar and pit file in the correct place.
Phone placed in download mode (the phone is showing in odin as connected)
Pressed start (tried with pit and no pit)
Put simply the phone isn't receiving anything. Usually when I flash with odin the phone and software do there thing. Download mode isn't even showing any signs of being connected. Setupconnection hangs there for a while and then it fails and sometimes it says pit file mapping (or something) and then fails after 10 mins of hanging there.
I have even tried flashing the bootloader by itself and that doesn't work either.
Cheers for all your help to.
Buckers1313 said:
downloaded the zip
unzipped (all correct tar files where there and the pit)
Opened odin and placed each tar and pit file in the correct place.
Phone placed in download mode (the phone is showing in odin as connected)
Pressed start (tried with pit and no pit)
Put simply the phone isn't receiving anything. Usually when I flash with odin the phone and software do there thing. Download mode isn't even showing any signs of being connected. Setupconnection hangs there for a while and then it fails and sometimes it says pit file mapping (or something) and then fails after 10 mins of hanging there.
I have even tried flashing the bootloader by itself and that doesn't work either.
Cheers for all your help to.
Click to expand...
Click to collapse
Try a different USB cable or a different USB port
Phistachio said:
Try a different USB cable or a different USB port
Click to expand...
Click to collapse
Cheers. I have tried different cables, USBs and even computers. I have tried with or without drivers and all the steps you have suggested.
I find it weird that it boots into download mode but just doesn't download. I'm wondering if something else may have stuffed itself?
Buckers1313 said:
Cheers. I have tried different cables, USBs and even computers. I have tried with or without drivers and all the steps you have suggested.
I find it weird that it boots into download mode but just doesn't download. I'm wondering if something else may have stuffed itself?
Click to expand...
Click to collapse
Usually when it's stuck at setupconnection it means that it can't connect to the NAND, more specifically, to r/w to the bootloader. Have you tried flashing JUST the bootloader?
Phistachio said:
Usually when it's stuck at setupconnection it means that it can't connect to the NAND, more specifically, to r/w to the bootloader. Have you tried flashing JUST the bootloader?
Click to expand...
Click to collapse
Yeah same thing happens. First time around it asks for the pit file though. I have tried flashing it as a bootloader and PDA file, but it still just hangs there.
Buckers1313 said:
Yeah same thing happens. First time around it asks for the pit file though. I have tried flashing it as a bootloader and PDA file, but it still just hangs there.
Click to expand...
Click to collapse
Hmm, that's odd You're using ODIN v3 correct?
It's SDS nothing to do, send back to Samsung service; it means motherboard replacing
almaalma74 said:
It's SDS nothing to do, send back to Samsung service; it means motherboard replacing
Click to expand...
Click to collapse
If it was SDS, would the phone be able to boot into download mode?
Phistachio said:
If it was SDS, would the phone be able to boot into download mode?
Click to expand...
Click to collapse
Yeah, it's called as "half" SDS, it is sad but true... My phone had same issues
almaalma74 said:
Yeah, it's called as "half" SDS, it is sad but true... My phone had same issues
Click to expand...
Click to collapse
Will Samsung know that I have put customer roms on it?
Fail to show as connected
I'm trying to flash out of CWM into TWRP but nether the Toolkit nor Odin shows my device as being connected in debug mode or download mode. What's the way ahead on this? I'm just trying to get another boot loader because I've been having issues with CWM failing on ROM installs from zip files. The only ROM I've been able to install is PAC.
Hi there,
This may seem like a daft question but i have just rooted my Note 2 using Odin and i went ahead and installed CWM from the play store.
However, i don't seem to have the option of making a backup of my current ROM.
All it gives me is (in blue)
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache.
This worked on my HTC One X, am i doing something wrong? My Note 2 was purchased as SIM free from phones4u.
I'm on android version 4.1.2, baseband version N7100XXDLK7, BUILD NO. JZO54K.N7100XXDMB2., MODEL NO. GT-N7100.
Could my bootloader still be locked? Is this causing the issue?
Any help would be much appreciated!
Just flash CWM/TWRP recovery.
Here is one of it
http://forum.xda-developers.com/showthread.php?t=2028103
Loading default android recovery even though TWRP successfully installed
Hi,
I am not sure if I should've started a separate thread for this, please move this if this has to be a separate thread but I've mentioned below why I am posting here.
My phone Galaxy note 2 International version GSM is rooted and I installed TWRP through Goomanager and I got a message stating that "Recovery was successfully installed". After this I shut down the phone and pressed Volume up + Home + Power to go into recovery mode and it still goes into the Android default recovery mode. I tried installing it again and still faced the same issue.
Since I was having a problem, I thought I will install TWRP through Odim 3.7. So, I connect PC to my phone and downloaded the openrecovery-twrp-2.3.1.1-n7100.img.tar.md5 and opened Odim in administrator mode and clicked on PDA >> Start. Within a second I got an error stating "odin downloader has stopped working". I went to task manager and shut down Samsung KIES and tried again but still got the same error.
Next, I tried using the Samsung Note 2 Toolkit. Before I installed TWRP through option 5 in the toolkit, I wanted to Rename Recovery Restore files (if present) as suggested by the toolkit. When I chose this option, I get an error stating adbd cannot run as root in production builds. When I googled this error, it went to a post which said that the bootloader needs to be unlocked.
But then the previous post says that I need TWRP for unlocking the bootloader and I'm doing all this to first of all install TWRP.
Apart from this, as additional Info, when I open ROM Manager - Under Recovery Setup - Current Recovery is Team Win Recovery Project. When I choose to reboot in Recovery mode from the application, it goes to the Android System Recovery. No matter what I do, TWRP recovery just does not seem to open up.
I'm pretty clueless now as to what other options I have or if I have messed up somewhere
Any suggestions would be appreciated.
Thank you
its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733
yahyoh said:
its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733
Click to expand...
Click to collapse
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.
gr8one said:
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.
Click to expand...
Click to collapse
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( and make sure kies is fully closed )
Tried that
yahyoh said:
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
( and make sure kies is fully closed )
Click to expand...
Click to collapse
Yahyoh,
Thank you for your response but if you see my original post, I have mentioned that I had already tried Odin 3.7 and put my phone in download mode and got the blue color showing ID: COM but when I pressed start, Odin gave an error stating odin downloader has stopped working and the only dialog box was to close. So, once I press START, I get a error message in a second and have to shut down. I did make sure that I have the correct tar version as I downloaded from TWRP's website directly for N7100. I did make sure that Kies was also closed.
After this I tried using Toolkit and that didn't help as well. Kinda going crazy why such a simple thing is getting to become a irritating problem, been sitting on this for the past 4 hours.
try to run odin as administrator
ran odin as administrator
yahyoh said:
try to run odin as administrator
Click to expand...
Click to collapse
Yes. I did run odin as administrator all the time.
try on another PC ? try to download odin again ? try another cable ?
yahyoh said:
try on another PC ? try to download odin again ? try another cable ?
Click to expand...
Click to collapse
I have tried downloading odin 4 or 5 times. The cable I have is brand new samsung cable. Right now, I dont have another pc but might have to go to a friends and try if that helps. I do have a mac but not sure if there is mac version of odin. I'm attaching a picture of what I see when I press volume up + home+power.
abhijitdroid said:
Hi,
1. Check that USB drivers are properly installed.
2. Your USB cable is proper and allows you to charge your phone as well as copy data from your PC.
3. Change USB port and try again. (This has worked in my case)
Click to expand...
Click to collapse
Usb drivers are installed properly. PC reads the phone as soon as itd connected. Tried three different usb ports that is available in my laptop. The phone does get charged when it's connected and I'm able to transfer data. Only thing left to try is a different pc.
Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;
Nazar78 said:
Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;
Click to expand...
Click to collapse
Hi Nazar78,
Mobile odin app is not free, it needs to be purchased. I already have the twrp image in the internal storage and was looking around if there was a free version of mobile odin app somewhere but couldn't find it.
I do not know how to use terminal apps and not familiar with the commands etc. So didn't wanna try that and mess it up. As a temporary solution I have installed CWM latest version using Rom manager but TWRP would be much better as it seems to be more user friendly.
If you could tell me how to enter this terminal apps page, I will probably follow the codes you have given and see if that helps.
Thanks
just install Android Terminal : https://play.google.com/store/apps/...251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
then type via keyboard what @Nazar78 wrote in the terminal
Just download any free terminal emulator app from play store and enter those commands per line each.
Btw u mentioned previously about adbd can't run on prod builds, its because the adbd binary in ur rom is stock, u need a patched one. Look for app called adbd insecure by CF. Or any custom builds should do the trick...
To flash recovery, tou need not to have paid version of mobile odin
Wait updating this post with link
Edit : here is mobile odin lite
http://forum.xda-developers.com/showthread.php?t=1347899
Download attached mobile odin lite from post 1
Then download flasher kernel from post 7
(download 5.0 versiin) and install
Then open mobile odin Select recovery tab, point to recovery file (tar/img) and flash
Sent from my GT-N7100 using xda premium
Thank you
Thanks Nazar78, Yahoyoh and Ketan, It's about 1:30am now, so I'm gonna shut down now and try these tomorrow. WIll get back with updates. Appreciate.
Also if you have installed EMET, a Microsoft software to stop security exploits, disable it.
It's cause me issues in the past.
I've also seen reports of people not having odin running properly when the kies process runs in the background. This was always the case when flashing with the Galaxy s, and might be a rare occurance with the note 2 too.
Sent from my GT-N7100 using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
By flashing this recovery you take full responsibility to whatever happens on your device. The developer will NOT be held responsible to whatever happens on your device. Ofcourse, the recovery has been tested but whatever happens on your device will not be held against the developer.
What Is CWM Recovery ?
CWM recovery is a way that enables you to falsh a custom rom , customize your rom and can save you from bad situations. To Be fully in controll of your android device you need a recovery and this is one of them.How To Install CWM Recovery ?
There are 2 methods for installing CWM
1.Method (dd method)
You need root before you continue.
now copy recovery.img from second post to your sd card and :
1.On PC :
Make shure that device is on usb debugging mode.
Plug device and open Terminal/command prompt.
Copy Pasta the Following Commands :
PHP:
adb shell
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.4.4
2.On Phone :
First Download Terminal Emulator From Play Store.
Plug device and open Terminal apk
Right the Following Commands :
PHP:
su (you need root acess for it )
Then
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !(guys with fat fingers stay away !)
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.3.3
Second Method Is Via ODIN.
First Download ODIN
Now Download the N8000/N8013-CWM-6.0.4.4.tar From Second Post and put it in same directory as odin.
Go To Download Mod (Volume Down +Home+Power) and plug device.
Now in Odin You Will see {added} and a light blue figure on top that means that device has been recognized if you dont get them uninstall devices drivers and retry.
Now click PDA and select N8000/N8013-CWM-6.0.4.4.tar And Then Click Start .
After Device reboots Your Done and CWM Is Flashed.Thanks To :
CM Team For CWM recovery .
@Dees_Troy @bigbiff @anders3408 @cybojenix @invisiblek {These Guys Are The Best And I Thank Them for helping me every step in the way and not thinking that i am a nut job }
Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.
Downloads And Q&A
Downloads :
1.IMAGES
N8000-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
N8013-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
2.TAR FILES
N8000-CWM-6.0.4.4.tar Build #1 {For Odin}
N8013-CWM-6.0.4.4.tar Build #1 {For Odin}
Change Log :
Build #1 Fully Working.Whats To Do In Future Build ?
Enable Touch .
Add OTG Support.FAQ:{Please Read Before Posting}
Q: OMG ! Recovey Not Booting What To Do ?
Alease Dont try entering recovery first time from advanced power menu just do it the hard way
Q:My Device is not getting read by windows ?
A:Uninstall all drivers that you installed for the device .Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.
For Later Use
it can't mount the external sd
iRoNX said:
it can't mount the external sd
Click to expand...
Click to collapse
seriously i did not notice such error, i will see what i can do tomrrow Thanks
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
Well thats odd :/ are you sure you have n8000 build not n8013 as i am recovery fine
Yes, i'm pretty sure. I've tried to do this few times via both terminal and odin. Now will try one more time...
UPD: I've repacked the img file with the tar archiver+ put md5 checksum (tar.md5) and flashed it with odin successfully.
And like iRoNX said it can't mount extSD: "error mounting /storage/sdcard1"
UPD2: The recovery from similar thread have another issue: cannot format "/data" and cannot explore internal flash )))
Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
+1.
The Odin tar file is not OK. Although I did not get a bootloop, the indicator on phone in download mode goes to the end and then stays there at "NAND write". I has to disconnect the phone and reboot manually, and my old version of CWM was still there (phew!). The .img files and dd worked fine.
Thanks anyways for this update !!!! It worked to get me on JB 4.4 !
Update: When phone is powered off and charger connected, upon starting there is a garbled green image that comes on for several seconds - most likely the battery charging icon - and then the phone will start up. It was not there before flashing 6.0.4.4. Anyways my phone does start up........
Tar file not working.. gets stuck at "Nandwrite"
Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip
zedomax said:
Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip
Click to expand...
Click to collapse
Way to go, champion !!
Flashed but the external SD card doesn't work
Sent from my GT_N8000
ODIN Image file attached.
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
SD cards problem
Hello again,
Within this version of CWM, the SD card problem seems to be only for the 64g cards as tested on my N8013. However, after you flash the Rom you'll using, there is no problem with 64g cards outside of CWM recovery mode.
Smaller sized cards 32g and less will mount fine while you are in CWM recovery mode.
Cheers,
L
lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Not working for me... says img. file is invalid. then ends.
Love it. Thanks.
lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Anyone confirm this as working?
Edit: Not working. Odin says invalid.
missing file
I seem to have lost my \efs folder, and in searching for a solution one of the steps I'm told to take is to flash "N8000-CWM-6.0.4.4.tar". However, it doesn't seem to exist anywhere (now that goo is gone), other than in this thread and the version here seems to be broken. Does anyone have the N8000 version of the .tar file?
Boot-loop, can't wipe device.
Hey everyone. I'm not exactly sure what happened, but it seems that my GT-N8000 is on the fritz again. The device was screen-off this morning (I left home) and when I came home it was in a reboot loop.
I jumped into recovery (CWM v6.0.4.4) to try to wipe both cache and dalvik (both successful) and rebooted. Same bootloop.
So then I decided to wipe the storage and reinstall the ROM (Gnabo v8 is what I had been running). When I attempt to "wipe data/factory reset", it says "formatting data . . ." and then reboots into the bootloop again.
Then I thought that maybe it was wiped, so I attempted to flash Gnabo. It installs successfully (Installing update, blue bar goes across, "Enjoy!" and "Install from sdcard complete."), however, when the installation starts, I get the first box and then it sits for almost 2 minutes before the blue bar appears, fills in just a few quick seconds, and then displays the completed message. It seems to me that the installation and the blue bar should be taking longer, but what do I know. Anyway, I rebooted (No, don't fix ROM flasing stock recovery on reboot), then back into the bootloop. So I'm still losing.
I don't know if it's related, but some months ago I had something similar happen in that the device was in a bootloop and it turned out that it had somehow lost the /efs folder. I had restored that (thanks XDA forums!) and it had been working fine since about June 2015.
I'm starting to think that my memory has gone bad, and that I basically have a 10.1 inch paperweight. Suggestions? Thanks for any help you can provide.
As a general FYI, if you think you need to repartition your phone it is also possible that your phone has experienced:
a) A hardware issue, possibly partial or total emmc failure.
b) A mismatch between bootloader (sboot.bin) and trustzone (tz.img) versions. See this post or my MK6 stock thread for some possible options to fix this.
As a step of last resort to recreate the partition table on your phone, a pit file may be what you need. This can be done in either Odin or Heimdall.
Warning - repartitioning your phone may erase all data and might cause other unintended consequences. You assume all risk.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
To use a pit file in Odin, this is typically done as part of a flashing a stock rom package, like the LJ2 or MA4 package for the i317 (or similar package for the i317m). You specify the pit file in the PIT section, make sure the repartition box is checked, and then add the rom package in the PDA section like usual.
If you are running an official 4.3 or later bootloader you will not be able to successfully flash a stock firmware package that contains earlier bootloaders - Odin will hang and you will need to find a different stock package to flash that does not contain a bootloader. (i.e. If you took the the i317 4.3 OTA and are running the MK6 bootloader or a later bootloader, you'll want to avoid UCAMA4)
The attached zip includes pit files for both the i317 and the i317m. The partition mapping is the same for both (see the included analysis files), but the pit files have unique security signatures which are accepted only by the bootloader of the specific model phone for which they are intended. I've tested the file for the i317 and can confirm that it works as intended. The file for the i317m was pulled the same way by an XDA member (thanks @plemen !) with an i317m and I've confirmed it is formatted correctly. It has now been confirmed as working.
If you want to learn a bit more about pit files, check out this thread by Adam Outler:
http://forum.xda-developers.com/showthread.php?t=2540480
Very interested in this, as I need the pit file for my I317. Question about the bootloader, though.... I've never taken an OTA, just flashing CM and OmniROM nightlies (was on 4.4.2 when my phone committed suicide). Should I be safe to use this pit file? And what factory firmware would you recommend to go with it?
pit files should be back in a day or two (I'll be testing over the weekend).
Depending on what happened to your phone it's still highly probable that your pit (partition) data is fine. There's a way to confirm this using Heimdall - when time permits I'll add instructions to post #2. That's a safer first step than attempting a repartition.
As for bootloader and firmware - if you've never taken an OTA, and you're not on a 4.3 bootloader your best bet for stock firmware is UCAMA4. It's a more complete and somewhat newer package than the other option (UCALJ2). You can get this from sammobile, or a mirror copy I have linked in post #2 here:
http://forum.xda-developers.com/showthread.php?t=2589891
that post also has information on a couple apps you can load that will allow you to check which bootloader you have loaded once your phone is operational.
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
anine said:
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
Click to expand...
Click to collapse
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Zen Arcade said:
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Click to expand...
Click to collapse
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Help
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
The symptoms you describe are similar to those I've seen on the Q&A forum recently. I don't want to be the bearer of bad tidings, but I suspect you have a partial emmc (hardware) failure.
My time during the week is limited so I expect to have testing done this weekend.
terpencar said:
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
Click to expand...
Click to collapse
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
http://www.androidfilehost.com/?fid=23060877490003986
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
rob_z11 said:
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
Click to expand...
Click to collapse
Thanks.. It just hangs at system.img in odin
Nice job Zen
Sent from my SGH-I317 using XDA Premium 4 mobile app
Pit files are back up and attached to the OP. The i317 pit file is tested and confirmed working.
The i317m file is identical, except for the security signature. I'm currently looking for someone with a healthy i317m willing to test flash the i317m pit file to confirm it works. (I would do this myself, but I don't have an i317m).
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
My phone was not booting and stopped at Samsung logo. After the pit file and stock rom, my phone is live again. I am still having issue with storage but at least I have good starting point.
thanks
Works fine on i317m
anine said:
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626593
qkster said:
http://forum.xda-developers.com/showthread.php?t=2626593
Click to expand...
Click to collapse
See posts #9 and #13 on the thread above for the specific potential solution to try.
Corrupt pit file it says. for note 2 att help
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
kumar_420 said:
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
Click to expand...
Click to collapse
Err mj9 is verizon haha
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
Hello,
I'm Hesham from Egypt I bought my GT-N7100 2 years ago. As usual I pluged it to the charger and got sleep. I waked up next day and find this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The mobile stuck on logo screen
Sent from my GT-I9300 using XDA Free mobile app
Hello,
I'm Hesham from Egypt I bought my GT-N7100 2 years ago. As usual I pluged it to the charger and got sleep. I waked up next day and find this
View attachment 3188775
The mobile stuck on logo screen. I tried to flash from recovery but this is the result when I push (volume up+home+power)
View attachment 3188777
By the way l have never setup or flash any rooms
View attachment 3188778
I tried all the possible ways to flash stock room or non stock room or even re-partition the E: with no luck
I don't know any information about the phone even if its model is Note II.
So I don't know if this is the international phone or not.
The back details are as shown below
Sent from my GT-I9300 using XDA Free mobile app
Mr Hesham
Your phone is an International model Note 2. The model number GT-N7100 tells you that.
Can you repost your attachments/screenshots please so we can can see what's going on
Shukran
Sent from my GT-I9300 using XDA Free mobile app
the photos
grwalker said:
Mr Hesham
Your phone is an International model Note 2. The model number GT-N7100 tells you that.
Can you repost your attachments/screenshots please so we can can see what's going on
Shukran
Click to expand...
Click to collapse
sorry I posted the pic separated as per forum's Privacy
Mr Hesham
Thanks for the pictures. What was the process you were going through when the error messages appeared on the screen?
I tried flashing the room such the attached picture.
And the failure messages is
Re-partition faild
Sent from my GT-I9300 using XDA Free mobile app
Hi
That seems like a strange way to flash a ROM. Have you looked at using ODIN? It's the best and most reliable way to flash a ROM.
Have a look at these links
http://www.jayceooi.com/how-to-install-firmware-on-samsung-galaxy-note-2-with-odin-video/
https://www.youtube.com/watch?v=nyNmR_tsD90
Let me know how you go
Thanks
I have already used ODIN V 3.04 and the attched Picture shaws the files which I used. But unlikely each time I try to flash it told me " operation failed "and the failure message is " re-partition faild "
I wish I could explain the issue.
Another way to explanation:
1- I tried to flash from recovery with no luck.
2- I have been downloaded the files which appeared on the last PIC
3- I used Odin 3.04 to make a new flash.
4- go to the Download mode and connect my phone to my PC then clicked on Start button on odin after selecting the pit and PDA ....ext files.
5- it seems working well but after 2 minutes I got the failure message "re-partition failed"
Several tries one with check re-partition box another without. Trying flash with Pit file and remove the other files . Trying flash with PDA file and remove the other files. Each time I get the failure message "re-partition failed".
Sent from my GT-I9300 using XDA Free mobile app
Mr Hesham
it looks like you have the same problem as I did with my Note 2. Getting stuck with a re-partition error looks very much like it is a failure of the eMMC chip.
First, pull the battery for a couple of minutes.
Reinsert the battery and go to recovery mode (VOL UP, HOME, POWER) and perform a factory wipe/reset.
Then go to download mode (VOL DOWN< HOME< POWER) and connect to PC
Open Odin. Make sure phone is connected to Odin
Download the file http://www.sammobile.com/firmwares/download/26440/N7100XXUENA1_N7100OJVENA1_EGY/
Flash the file. Select it via PDA. Do not extract the file.
DO NOT flash the PIT file and leave re-partiton unckecked.
Send a screenshot off the PC of what happens
when used odin controlled the box "re-partition" was not checked? because it is one of the most important steps to verify when a rom is installed, the option is NOT checked.
Did you try the step i suggested?
dear Grwalker,
attached the result of the first step of your suggestion.
I'm downloading the file you mentioned on the 3rd step and I'll send you the result once finishing the steps.
Dear Grwalker,
as the attached Pic ODIN can't find the file because it's extention is " ZIP " and the PDA Browser told that the file must be " tar, md5 or smd ".
also you asked me to don't EXTRACT the file.
what shall I do?!
look inside the zip file, if there are tar files just extract and open in odin.
odin needs tar files.
look at the bootom of the page with download link - quick instruction what to do with the zip file
grwalker said:
Mr Hesham
it looks like you have the same problem as I did with my Note 2. Getting stuck with a re-partition error looks very much like it is a failure of the eMMC chip.
First, pull the battery for a couple of minutes.
Reinsert the battery and go to recovery mode (VOL UP, HOME, POWER) and perform a factory wipe/reset.
Then go to download mode (VOL DOWN< HOME< POWER) and connect to PC
Open Odin. Make sure phone is connected to Odin
Download the file http://www.sammobile.com/firmwares/download/26440/N7100XXUENA1_N7100OJVENA1_EGY/
Flash the file. Select it via PDA. Do not extract the file.
DO NOT flash the PIT file and leave re-partiton unckecked.
Send a screenshot off the PC of what happens
Click to expand...
Click to collapse
"Flash the file. Select it via PDA. Do not extract the file"
Mr Grwalker said that
I read the instructions but may be there is another way or another steps I should do . Cauz I'm already tried to extract the Zip file and flash with th .tar file but the odin stuck on NAND WRITE START!
Sent from my GT-I9300 using XDA Free mobile app
Mr Hesham
Sorry i should have been more clear. Extract the zip you downloaded from Sammobile but don't extract what comes from the zip.
Select the extracted file in PDA
once ODIN says it is ready click start
Send a screenshot of what Odin does
Thanks
the first try with ODIN V 3.04
NAND Write Start!
<>Complete (Write) operation failed.
the second try with Odin V3.09
please help.