[Q&A] [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/2 - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

[Q&A] [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/2
Q&A for [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/24
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/24. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Problem Flashing TWRP to T-Mobile Note 4 in ODIN...PLZ HELP
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.

Ttw626 said:
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.
Click to expand...
Click to collapse
Can you try verifying the md5 of the file from the place you downloaded TWRP from?

How do I verify it

re: odin flash issues
Ttw626 said:
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.
Click to expand...
Click to collapse
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!

bigbiff said:
Can you try verifying the md5 of the file from the place you downloaded TWRP from?
Click to expand...
Click to collapse
How do I verify it?
---------- Post added at 02:25 PM ---------- Previous post was at 02:13 PM ----------
Misterjunky said:
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!
Click to expand...
Click to collapse
Misterjunky i think relock is on in the phone ill disable it and try again i didnt think of that before thanks.

Misterjunky said:
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!
Click to expand...
Click to collapse
Great it took this time thanks alot sir :good:

@bigbiff...VZW Note 4 stock recovery image is here....
http://forum.xda-developers.com/showthread.php?p=56385923
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.4.13

nicee 5*

I accidentally wiped my sd card in twrp and now I'm having trouble downloading from a lot of apps. How can I fix this? Would I have to Odin back to a stock firmware to get it back to where it was? Titanium back up and other apps say I have insufficient space, but I know I have a good amount. I reflashed the ROM I've been on and started fresh, but I'm still having issues. Thanks in advanced.

re: titanium backup
paranoid android85 said:
I accidentally wiped my sd card in twrp and now I'm having trouble downloading from a lot of apps. How can I fix this? Would I have to Odin back to a stock firmware to get it back to where it was? Titanium back up and other apps say I have insufficient space, but I know I have a good amount. I reflashed the ROM I've been on and started fresh, but I'm still having issues. Thanks in advanced.
Click to expand...
Click to collapse
Uninstall titanium backup and re-download/install it from the play store then have titanium backup
detect backup location under preferences>backup location in settings then restart titanium backup.
Once you do that it will work fine.
Good luck!

TWRP 2.8.1.0 is not installing on my Tmo Galaxy Note 4
I don't know what's going on guys. I know I am doing everything the right way but for some reason whenever i get back to turning the phone off hitting Vol up/Home/ Power key it takes me to the android boot screen vs the twrp android boot screen.
I am using the img.tar file in odin under the pda option
I have odin set to auto re-boot
i turn the phone off and hit the command
nothing.
Using this twrp in odin
openrecovery-twrp-2.8.4.0-trltetmo.img.tar
if someone can please help me out greatly appreciated.

Is the phone rooted? With bootloader unlocked? Did u use CF auto root?
If so u can flash recovery with FLASHIFY [ https://play.google.com/store/apps/details?id=com.cgollner.flashify] from the play store. Just download the .IMG file for TWRP in the app and let it flash it.
Sent from my SM-N910T using XDA Free mobile app

Thanks for your help man I did end up figuring it out. For some reason the auto reboot was causing the issue. I had to turn that off and manually pull the battery out etc for it to work.
Worked great and I'm now running cm12

thanks for this

I'm guessing twrp 3.0.0 dosent work for the kindle fire (otter) right?

AlbGol said:
I gave you the correct file for what you need to do if you have the n910t, for more specifics look the post above me.
Here is the correct way of installing twrp 3.0 image file, straight from your existing recovery (twrp)
When you boot into your current Recovery 2.8.7.0 and click on Install - Bottom Right you'll see a Image Button - Click on this - The next Screen will show Boot and Recovery - You want to click on Recovery and Swipe to install.
Thats it. (All the phones that I did this were N910T, so was the image file for my device trltmo)
Here is the direct link for twrp 3.0 image file for 910t
https://www.androidfilehost.com/?fid=24407100847294047
Also if u have different model(carrier) just find it here and follow the steps:
http://forum.xda-developers.com/not...-utility-twrp-2-8-1-0-teamwin-t2915588/page44
Click to expand...
Click to collapse
Hey, HUGE problem here. I did this I may have totally bricked my phone. im freaking out.
Please help me
Stuck on recovery booting and cannot even get into download mode. Plugged into comp, I do get a chime .
Is it time to Jtag?
What are my options. Please help

Remove battery, install battery...use button combo to enter download mode and flash 2.87 with odin...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw

manbat said:
Remove battery, install battery...use button combo to enter download mode and flash 2.87 with odin...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
Click to expand...
Click to collapse
Button combo does not work, goes to recovery booting loop. This is the problem. That's the first thing i did. I haven't seen a hard brick on any of my devices in 12 years.

Related

[Q] Please help me with my Note GT-N7000 (I might have bricked it)

My Galaxy Note GT-N7000 was on CM10 last night and I followed Zedomax's rootgalaxynote.com GT-N7000 unrooting method and when I was installing the Mobile Odin Lite on my phone, it said it needs to download more add-on to be able to flash it, then all the sudden my internet connection was down, so I couldn't download it, but followed his instruction and tried wipe and factory reset, but it got stuck at formatting (no progress), then I flashed cm9 again, but it was stuck at cm9 boot logo, nothing else. Then I followed Zedomax's rootgalaxynote.com's first method using my Computer Desktop but
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKL1_N7000OLBKJ6_N7000DXKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
" it got stuck at here, no progress. The only thing I can do with my phone is that to either put on download mode or it says "Firmware upgrade encountered an isssue. Please select recovery mode in Kies & try again." Please help me with this friends. I am looking forward to your help. Thank you.
Khai.
you give not detail as needed. but nevermine, from the last part it seems you has bricked your phone.
i think you might need to refer "hg42" thread to revive your note.
Sad to be hear that.
Sent from my GT-N7000 using xda premium
immediately contact dr.ketan
khaino said:
My Galaxy Note GT-N7000 was on CM10 last night and I followed Zedomax's rootgalaxynote.com GT-N7000 unrooting method and when I was installing the Mobile Odin Lite on my phone, it said it needs to download more add-on to be able to flash it, then all the sudden my internet connection was down, so I couldn't download it, but followed his instruction and tried wipe and factory reset, but it got stuck at formatting (no progress), then I flashed cm9 again, but it was stuck at cm9 boot logo, nothing else. Then I followed Zedomax's rootgalaxynote.com's first method using my Computer Desktop but
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKL1_N7000OLBKJ6_N7000DXKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
" it got stuck at here, no progress. The only thing I can do with my phone is that to either put on download mode or it says "Firmware upgrade encountered an isssue. Please select recovery mode in Kies & try again." Please help me with this friends. I am looking forward to your help. Thank you.
Khai.
Click to expand...
Click to collapse
Contact dr.ketan for yr solution. He is the sweet n right person to guide u.
khaino said:
My Galaxy Note GT-N7000 was on CM10 last night and I followed Zedomax's rootgalaxynote.com GT-N7000 unrooting method and when I was installing the Mobile Odin Lite on my phone, it said it needs to download more add-on to be able to flash it, then all the sudden my internet connection was down, so I couldn't download it, but followed his instruction and tried wipe and factory reset, but it got stuck at formatting (no progress), then I flashed cm9 again, but it was stuck at cm9 boot logo, nothing else. Then I followed Zedomax's rootgalaxynote.com's first method using my Computer Desktop but
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKL1_N7000OLBKJ6_N7000DXKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
" it got stuck at here, no progress. The only thing I can do with my phone is that to either put on download mode or it says "Firmware upgrade encountered an isssue. Please select recovery mode in Kies & try again." Please help me with this friends. I am looking forward to your help. Thank you.
Khai.
Click to expand...
Click to collapse
the ever GOLDEN RULE: Don't ever ever attempt to WIPE data if your on a unsafe or on a stock ICS kernel. That's should be at the top of your list before you do anything on your phone. If you need to WIPE, make sure your already in a safe kernel or if you haven't still, then flash one.
Now going back on your perennial issue. The only thing you can and will do is FLASH a stock GB on download mode using PC ODIN. Yes Doc Ketan's thread/s have those old GB's ROM.. -> http://forum.xda-developers.com/showthread.php?t=1424997, follow it to a tee.
One added thing when your going to start to flash GB again... Pray, that it would not stuck back again at 'factoryfs.img'
Good luck bud!
No luck...yet.
letters_to_cleo said:
the ever GOLDEN RULE: Don't ever ever attempt to WIPE data if your on a unsafe or on a stock ICS kernel. That's should be at the top of your list before you do anything on your phone. If you need to WIPE, make sure your already in a safe kernel or if you haven't still, then flash one.
Now going back on your perennial issue. The only thing you can and will do is FLASH a stock GB on download mode using PC ODIN. Yes Doc Ketan's thread/s have those old GB's ROM.. -> http://forum.xda-developers.com/showthread.php?t=1424997, follow it to a tee.
One added thing when your going to start to flash GB again... Pray, that it would not stuck back again at 'factoryfs.img'
Good luck bud!
Click to expand...
Click to collapse
I spent two days straight working on it, but no luck. I think I am gonna contact Samsung and send it to them for the warranty and I don't know if they would know that I rooted it. But I am just gonna give a try. Please share your knowledge and thoughts. Thank you.
Reflash it with PC odin (Again? )... refer to Dr Ketan... I encounter same issues before, I just try try to reflash old GB... link at #4
khaino said:
I spent two days straight working on it, but no luck. I think I am gonna contact Samsung and send it to them for the warranty and I don't know if they would know that I rooted it. But I am just gonna give a try. Please share your knowledge and thoughts. Thank you.
Click to expand...
Click to collapse
Can you get the Note into Download mode?
If so, try using desktop Odin (latest desktop version not mobile version) and flash the Abyss 4.2 kernel. the Tar file is easily found on XDA. This is a GB kernel and should allow you to get into full Recovery. From there you can flash a new ROM as you are now on a safe kernel.
Tried that, but not sure about the latest desktop version.
Alba Donzo said:
Can you get the Note into Download mode?
If so, try using desktop Odin (latest desktop version not mobile version) and flash the Abyss 4.2 kernel. the Tar file is easily found on XDA. This is a GB kernel and should allow you to get into full Recovery. From there you can flash a new ROM as you are now on a safe kernel.
Click to expand...
Click to collapse
Hi, thank you for your message, I was on Abyskernel when I factory data reset, and tried to flash back to cm9 from cm10, but no luck. Then I used Odin3-v1.85 on desktop with Gingerbread Rom, it got stuck at factoryfs.img.. I have tried with different pc disabling firewall and anti virus. What is the latest desktop version of Odin that you know? What specific tar file do you know that is the best? Thank you again.
khaino said:
Hi, thank you for your message, I was on Abyskernel when I factory data reset, and tried to flash back to cm9 from cm10, but no luck. Then I used Odin3-v1.85 on desktop with Gingerbread Rom, it got stuck at factoryfs.img.. I have tried with different pc disabling firewall and anti virus. What is the latest desktop version of Odin that you know? What specific tar file do you know that is the best? Thank you again.
Click to expand...
Click to collapse
Latest Odin is 3.0.4
Sent from my GT-N7000 using xda app-developers app
khaino said:
Hi, thank you for your message, I was on Abyskernel when I factory data reset, and tried to flash back to cm9 from cm10, but no luck. Then I used Odin3-v1.85 on desktop with Gingerbread Rom, it got stuck at factoryfs.img.. I have tried with different pc disabling firewall and anti virus. What is the latest desktop version of Odin that you know? What specific tar file do you know that is the best? Thank you again.
Click to expand...
Click to collapse
your CM10 to CM9 downgrade sounds like a bad flash, it can happen. I would try Odin3 V3.05 with Abyss (search for "AbyssNotekernel42CWTouchOriginalLogo.tar" or go here - https://www.dropbox.com/s/yoe791qq3atbung/AbyssNotekernel42CWTouchOriginalLogo.tar).
this should allow you to install a safe kernel to flash from. if you can now access Recovery, then you can flash a ROM from there. I would use a Stock based one (I always recommend Chrack ROM or Criskelo), If you prefer, you can download a Stock tar file and use Odin but I would try downloading the latest Chrack ROM or Criskelo ROM, transferring it to your micro SD and flashing after you have installed the Abyss tar.
I hope this helps. Please hit Thanks if it did.
Question!
Alba Donzo said:
your CM10 to CM9 downgrade sounds like a bad flash, it can happen. I would try Odin3 V3.05 with Abyss (search for "AbyssNotekernel42CWTouchOriginalLogo.tar"
this should allow you to install a safe kernel to flash from. if you can now access Recovery, then you can flash a ROM from there. I would use a Stock based one (I always recommend Chrack ROM or Criskelo), If you prefer, you can download a Stock tar file and use Odin but I would try downloading the latest Chrack ROM or Criskelo ROM, transferring it to your micro SD and flashing after you have installed the Abyss tar.
I hope this helps. Please hit Thanks if it did.
Click to expand...
Click to collapse
You gave me the AbyssNotekernel, but the only thing my phone can now do when I turn on is either show a screen with "Firmware upgrade encounters an issue. Please select recovery mode in Kies and try again" or on download mode. Or is there any way I can use the Desktop Odin and try to install the AbyssNotekernel that you gave me? I really don't know bro. Thank you for the message, please let me know.
khaino said:
You gave me the AbyssNotekernel, but the only thing my phone can now do when I turn on is either show a screen with "Firmware upgrade encounters an issue. Please select recovery mode in Kies and try again" or on download mode. Or is there any way I can use the Desktop Odin and try to install the AbyssNotekernel that you gave me? I really don't know bro. Thank you for the message, please let me know.
Click to expand...
Click to collapse
Yes, the Abyss tar file is for use with Odin. install Odin on your PC, put the Note into Download and connect. Flash the tar file and wait for the Note to reboot (search for notes on how to flash with Odin if you're not 100% sure). you should now be able to use Recovery to flash a ROM from this safe kernel.
Just a quick question.
Alba Donzo said:
Yes, the Abyss tar file is for use with Odin. install Odin on your PC, put the Note into Download and connect. Flash the tar file and wait for the Note to reboot (search for notes on how to flash with Odin if you're not 100% sure). you should now be able to use Recovery to flash a ROM from this safe kernel.
Click to expand...
Click to collapse
Sorry I didn't explain in details, I am on pc Odin version 3.07 and clicked on PDA but the Abyss tar file is not appearing there even after unzipping it a couple of times on the desktop. Please let me know bro. Thank you for your response.
Khai.
khaino said:
Sorry I didn't explain in details, I am on pc Odin version 3.07 and clicked on PDA but the Abyss tar file is not appearing there even after unzipping it a couple of times on the desktop. Please let me know bro. Thank you for your response.
Khai.
Click to expand...
Click to collapse
.tar file is to be flashed with odin directly. It has an image inside and should not extract it. Should put the .tar file in one folder but not on desktop screen. Select pda box in odin and brow to the folder where you put .tar file. Should see it there.
BTW, if flash using CWM failed again, then should use hg42 scanner to check if there is partition damage.
http://forum.xda-developers.com/showthread.php?t=1823918
Update.
forest1971 said:
.tar file is to be flashed with odin directly. It has an image inside and should not extract it. Should put the .tar file in one folder but not on desktop screen. Select pda box in odin and brow to the folder where you put .tar file. Should see it there.
BTW, if flash using CWM failed again, then should use hg42 scanner to check if there is partition damage.
http://forum.xda-developers.com/showthread.php?t=1823918
Click to expand...
Click to collapse
Thanks for your patience on your instruction, I actually was able to flash the Abysskernel that you gave me with ODIN and it went straight to the recovery mode, but then I can't install anything, then I put it back to download mode and tried to flash a Gingerbread ROM, but as always it got stucked at factoryfs.img. What do you think I can do bro? Please let me know about it. Thank you.
Khai.
khaino said:
Thanks for your patience on your instruction, I actually was able to flash the Abysskernel that you gave me with ODIN and it went straight to the recovery mode, but then I can't install anything, then I put it back to download mode and tried to flash a Gingerbread ROM, but as always it got stucked at factoryfs.img. What do you think I can do bro? Please let me know about it. Thank you.
Khai.
Click to expand...
Click to collapse
It seem to show you have an emmc brick, although using the partition scanner will confirm. The options are to send to ss service for warranty or to revise using repartition. For warranty you will need to reset flash counter using a jig.
Sent from my phone
Update and question.
forest1971 said:
It seem to show you have an emmc brick, although using the partition scanner will confirm. The options are to send to ss service for warranty or to revise using repartition. For warranty you will need to reset flash counter using a jig.
Sent from my phone
Click to expand...
Click to collapse
Hi bro,
I flashed the Abysskernel again and it went to Samsung Galaxy Note GT-N7000 logo with big Triangle at the bottom and it then goes to Android system recovery <3e>, then it looks like there is no option for me to access the SD card, but its own 16GB storage it came with and that one has CM10 in it. Tried to flash that, but it says "E:failed to verify whole-file signature". If I attempt to claim for warranty will Samsung know that I rooted it after clearing the binary counts? Please let me know. Thank you for your instructions. If there is anything else you want me to try out, please let me know. Thank you.
Khai.
khaino said:
Hi bro,
I flashed the Abysskernel again and it went to Samsung Galaxy Note GT-N7000 logo with big Triangle at the bottom and it then goes to Android system recovery <3e>, then it looks like there is no option for me to access the SD card, but its own 16GB storage it came with and that one has CM10 in it. Tried to flash that, but it says "E:failed to verify whole-file signature". If I attempt to claim for warranty will Samsung know that I rooted it after clearing the binary counts? Please let me know. Thank you for your instructions. If there is anything else you want me to try out, please let me know. Thank you.
Khai.
Click to expand...
Click to collapse
Once reset flash counter the triangle will go and you can flash a stock kernel find link from dr.ketan toolbox, then it is ok to send to warranty.
Sent from my phone
Update.
forest1971 said:
Once reset flash counter the triangle will go and you can flash a stock kernel find link from dr.ketan toolbox, then it is ok to send to warranty.
Sent from my phone
Click to expand...
Click to collapse
Hi bro, it somehow managed to get on CWM and but any flashing was aborted. And tried to flash Criskelo, but got stuck at installing, no progress. What should I do? Thank you.
Just two options above, warranty or repartition.
Sent from my phone

[Q] Can´t restore recovery / adb / SD not recognize

Hi!!
First, I was trying to find some solution, here and google, but every one that could work, don´t.
I was trying to install CyanogenMod 10.1
I followed the installation guide... but when I have to choose CM zip file, I choosed another one from other sell (I was using the same card)
The CM that I use was this: cm-7.2.0-jordan.zip (from a defy phone)
instead cm-10.1-20130621-NIGHTLY-janice.zip
Everything goes bad since that.
I tried to wipe data/factory reset:
E: format_volume: fs_type "ext3" unsupported
E: Can´t mount /cache/reovery/log
E: Unknow fs_type "ext3" for /cache
I tried to update from external storage
But only shows me this: " ../ "
I tried to apply update from ADB
I followed the guide, copy the roms on self directory, put the 4 files on c:\windows , etc.
This are the common errors that shows me:
C:\Windows\Herramientas Sideload>adb sideload gapps-jb-2013
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
I tried kill the adb.exe like this, but doesn´t works
error: closed adb
I tried this but doesn´t works
I found nothing that could help more, so that´s way I making this post.
Here is some data:
GT-i9070
Windows 7 64bits
Kies updated (but could connect to the device now)
I think that drivers of the cell are updated, because windows shows me that... buy i don´t know if is the correct one.
I will be very grateful if you can help. I hope this can be fixed ..
Best regards!!
PS: sorry my english.
Can you enter in download mode with vol down+home+power when phone is switched off?
I didn´t know that.
Yes, now is in downloading mode:
Do not turn off target.
My pc can´t recognize it
Mr.BUBU said:
I didn´t know that.
Yes, now is in downloading mode:
Do not turn off target.
My pc can´t recognize it
Click to expand...
Click to collapse
Reflash stock jelly bean with Odin, then flash CoCore kernel for CWM recovery, and retry to flash CM10.1. To do that:
1-Because your pc doesn't recognize the device uninstall Kies and install only usb drivers (you can download install package here)
2-Download Odin and i9070 Stock Jelly Bean firmware from samfirmware (I recommend i9070XXLQG PDA)
3-Extract downloaded zip, you will find three files (one .dll, one .pit and one .tar.md5)
4-Launch Odin, select "Re-Partition" and leave others as they are. Press "PIT" button and select .pit file in extracted firmware's zip file, then press "PDA" and select .tar.md5 file in same directory.
5-Enter in download mode like I said you early and connect device to pc, press "Start" button on Odin and wait for the "SUCCESS" message, now your phone should power on normally.
6-Now download this zip file (for obtain root access) and put in sd card (micro sd, not internal memory!)
7-Turn off your phone, press vol up+home+power to enter recovery, select "apply update from external storage" then select root.zip, reboot device.
8-Now you have stock jelly bean rooted, update SuperSU from Google Play and install Universal Kernel Flash from frapeti (you can find it on Play Store).
9-Download CoCore Kernel here, take kernel.bin.md5 file from zip package and put it in internal storage.
10-Launch Universal Kernel Flash, select kernel.bin.md5 and flash it.
11-Power off phone and enter again in recovery with vol up+home+power, now you should have CWM-based recovery, select "backup and restore" and take a full system backup.
12-Wipe data, cache and dalvik and retry to install CM10.1-janice, in case something goes wrong or you want to remove CM without flash again with Odin you can restore your system backup from CWM.
If you have a doubt I'm here to help you
Problem:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070XXLQG_I9070OXXLQG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
8(
There wasn´t a .pít file on the i9070XXLQG
I found one from Odin3-v1.85.zip
Could be that why is wrong? I´m downloading one more... this time without the Kies sign. I bet that is the probelm.
it´s getting worst
Now when I turn on the phone, the screen looks with diagonals strips.
And only the download mode is working... no more for upload mode.
:crying:
Well... i was looking for that error... and could be the cable and the usb port.
I changed each one, and still don´t works.
Remove the SD, remove the sim, and every time get me the same error.
Anything else?
Which .pit you have? The name of the correct one is: GT-I9070_EUR_XX_8G.pit for 8GB memory. Your have 8GB or 16GB of memory?
This one, but it came with the odin... I think.
u1_02_20110310_emmc_EXT4.pit
I will look for the correct one :good:
Mr.BUBU said:
This one, but it came with the odin... I think.
u1_02_20110310_emmc_EXT4.pit
I will look for the correct one :good:
Click to expand...
Click to collapse
Always use specific pit file of a device, each Samsung device have it, for example I can't use i9000's pit file on i9070. Which model is? 8 or 16? Because the two models have different pit file
Now I know...
8gb model.
Mr.BUBU said:
Now I know...
8gb model.
Click to expand...
Click to collapse
Okay, the correct file is the one that I said you, you can find it here on xda or with Google, I have it on pc (I'm writing with phone) but here in Italy is too late and I'm going to sleep if you can't find it I can upload it for you
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
:laugh:
It´s alive !!!
And with CyanoGen working
I had to avoided some steps, because no one version let me get in the Os. Every each stop working when complete the time of the cell. Never been able to install Super Su for example.
So... I take the CM janice and the gapps cyano and at least is working. :victory:
Now to test and re test... before installing everything else.
Thanks you so much. I was affraid to had broke the cell for ever.
You really known about this... thanks for help me :good:
Mr.BUBU said:
THANKS YOU
Click to expand...
Click to collapse
next time, don't mix up the devices, files or steps. then you'll be fine.
Sent from a rice cooker
Mr.BUBU said:
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
THANKS YOU
:laugh:
Click to expand...
Click to collapse
Excellent, next time be careful when you're flashing roms
Thanks for the advice harith.unnikrishnan and Tesla-MADAL93
I have root some, but never flash roms. Always there is a first time... in my case was catastrophic
Best regards!!
Mr.BUBU said:
Thanks for the advice harith.unnikrishnan and Tesla-MADAL93
I have root some, but never flash roms. Always there is a first time... in my case was catastrophic
Best regards!!
Click to expand...
Click to collapse
Don't worry, the important is that now it works
Mr.BUBU said:
Thanks for the advice harith.unnikrishnan and Tesla-MADAL93
I have root some, but never flash roms. Always there is a first time... in my case was catastrophic
Best regards!!
Click to expand...
Click to collapse
It was not catastrophic. It would be if you flashed wrong firmware with Odin. :silly:
shut_down said:
It was not catastrophic. It would be if you flashed wrong firmware with Odin. :silly:
Click to expand...
Click to collapse
I agree with you, shut_down

Galaxy Gear Bricked, Odin always Fail

I've been trying to Flash V700XXUAMK7_V700OXAAMK7_HOME.tar.md5 (BTU) to my Galaxy gear, it got bricked and now I'm sitting in the "Firmware upgrade encountered an issue. Please select Recover mode in Kies & try again."
Well Kies isn't connecting to it and Odin results in a Fail no matter what I try. I've tried it on Odin 3.09, 3.07, 3.04. I've tried resetting but can't get to the download boot or any of that. I've tried different roms, I've tried Kies, and I can't find a way out.
Any help?
Try a different cable? Cheap cables can cause problems
Brendo said:
Try a different cable? Cheap cables can cause problems
Click to expand...
Click to collapse
I'm using the best cable I have.
Also try a different computer,,,
If it helps this is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> V700XXUAMK7_V700OXAAMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
crutzulee said:
Also try a different computer,,,
Click to expand...
Click to collapse
I tried a different computer, both cords, version 3.09 and 3.07 with the same MK7 file and it throws out the same log I posted.
EDIT: 3.09 Starts to work, then it crashes.
CarbonWyre said:
I tried a different computer, both cords, version 3.09 and 3.07 with the same MK7 file and it throws out the same log I posted.
EDIT: 3.09 Starts to work, then it crashes.
Click to expand...
Click to collapse
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
rob8178 said:
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
Click to expand...
Click to collapse
Where do you recommend downloading it from?
rob8178 said:
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
Click to expand...
Click to collapse
I redownloaded and re unzipped, same thing happened. Odin just crashed after clicking start
CarbonWyre said:
I redownloaded and re unzipped, same thing happened. Odin just crashed after clicking start
Click to expand...
Click to collapse
Has anyone gotten a solution here? I can't get Odin/Kies/Fastboot to bring this back to life. I was trying to flash Tizen and got here instead.
And minutes later Odin makes me a liar and flashes an stock android img onto the little bugger and I am back in business, thanks anyway!!
Same thing happened to me.. you will have to do one of two things. . Search for the tizen downgrade. Sorry don't have link handy. .. or flash the original tizen update not the newest nf1 then flash the nf1 after successful flash... the problem is you flashed the newest nf1 before having the tizen bootloader. .. and right now you are trying to flash android on a jacked up tizen bootloader. .. give me a min to search for you and I will post links
Sent from my SM-G900T using Tapatalk
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
Tizen downgrade. ...
http://forum.xda-developers.com/showthread.php?t=2776157
Oh yeah don't forget thanks
Sent from my SM-G900T using Tapatalk
---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------
Flash this first... then flash NF1 ... and I hope it goes with out saying flash in oden
http://forum.xda-developers.com/showthread.php?t=2767465
Sent from my SM-G900T using Tapatalk
Very Thanks !
Thanks you !
Flash this version of Tizen is only way to back to Tizen after downgrade from Tizen to Android ( i know it isn't very clever )
I try flash many tizen firmwares but, ONLY this working.
Kies Updates doesn't work, only ODIN.
Think I've Bricked My Gear
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
trisha3010 said:
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
Click to expand...
Click to collapse
No need to get back to recovery or download mode. Use odin and follow instructions by @fireishott above. I have just restored my gear from the 'Firmware Upgrade Encountered a problem' screen. It should be recognised by odin 3.09. You can try another computer, and also press the power button as if you are rebooting the gear. The screen will go off then you get the 'firmware....' screen again. Ensure you have latest samsung drivers.
Good luck.
trisha3010 said:
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
Click to expand...
Click to collapse
I used Odin3.07 and 4.2.2 stock ROM to flash first - I used PHONE option because the others didn't work (no progress in the message window). This 'faulty' flash came up with a 'UI stopped working error' when the Gear rebooted but I was able to get it into download mode now. I then used Odin 3.09 and the flashed the 4.2.2 as a PIT which worked fine!
Got there after reading through a lot of XDA threads and trying many things. But in the end, the answers were here. Thanks.
PS how I got into the mess (the firmware error message with the yellow triangle)? I was on null 23 and wanted to go back to stock rom so that I could sell the Gear. Couldn't get into download mode for Odin 3.09; I can't exactly remember what I did but I disconnected the gear midway through a seemingly failed flash and it got me to the error. Googling says use Kies but nope, it wouldn't recognise the gear even for the 'emergency firmware'. I tried a lot of things, and wasted a lot of time!
Big Thanks
chobochobo said:
I used Odin3.07 and 4.2.2 stock ROM to flash first - I used PHONE option because the others didn't work (no progress in the message window). This 'faulty' flash came up with a 'UI stopped working error' when the Gear rebooted but I was able to get it into download mode now. I then used Odin 3.09 and the flashed the 4.2.2 as a PIT which worked fine!
Got there after reading through a lot of XDA threads and trying many things. But in the end, the answers were here. Thanks.
PS how I got into the mess (the firmware error message with the yellow triangle)? I was on null 23 and wanted to go back to stock rom so that I could sell the Gear. Couldn't get into download mode for Odin 3.09; I can't exactly remember what I did but I disconnected the gear midway through a seemingly failed flash and it got me to the error. Googling says use Kies but nope, it wouldn't recognise the gear even for the 'emergency firmware'. I tried a lot of things, and wasted a lot of time!
Click to expand...
Click to collapse
Hi Everyone HUGE thanks managed to follow instructions and gear is back up and working. Just wanted to check I only flashed the tizen downgrade (ie-image 1) and this automatically rebooted the galaxy back to original settings without having to reflash the NF1 is this ok or should i flash this anyway. Many thanks again for the replies as everyone here was telling me it was beyond repair.
i was in the same situation last week kept getting same errors,decided to try different computer and went here and downloaded (http://samsung-updates.com/device/?id=SM-V700) and picked 4.2.2 btu version and went through with no error and got it back up and going
Further Problems
trisha3010 said:
Hi Everyone HUGE thanks managed to follow instructions and gear is back up and working. Just wanted to check I only flashed the tizen downgrade (ie-image 1) and this automatically rebooted the galaxy back to original settings without having to reflash the NF1 is this ok or should i flash this anyway. Many thanks again for the replies as everyone here was telling me it was beyond repair.
Click to expand...
Click to collapse
Hi everyone can't believe this but hit the reset button in the settings app and the gear has now rebooted and stuck on the Samsung screen with nothing working - odin not recognising it and even when i try to reboot in recovery mode it just keeps reverting back to same Samsung screen ... any help or suggestions would be appreciated.
solved for me
shayind4 said:
No need to get back to recovery or download mode. Use odin and follow instructions by @fireishott above. I have just restored my gear from the 'Firmware Upgrade Encountered a problem' screen. It should be recognised by odin 3.09. You can try another computer, and also press the power button as if you are rebooting the gear. The screen will go off then you get the 'firmware....' screen again. Ensure you have latest samsung drivers.
Good luck.
Click to expand...
Click to collapse
solved for me.the problem was that i didnt press the POWER button.
I had same issue after getting stuck on zimage during flashing of Tizen over Null rom. I simple flashed null rom thru odin as a phone rom and it booted back into null rom. Gear is back up and fuctioning.
Sent from my SPH-L900 using XDA Premium 4 mobile app

[Q&A] [GUIDE][HOWTO] ODIN to Stock Unrooted Firmware [NK4]

Q&A for [GUIDE][HOWTO] ODIN to Stock Unrooted Firmware [NK4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][HOWTO] ODIN to Stock Unrooted Firmware [NK4]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can I use this method to unroot if I'm on NK4 rooted?
After I've followed every step, my phone still gets stuck in the same boot loop as always. It never loads to recovery mood after flashing the stock ROM using Odin v3.09.
I used the NK4 rom. Am I doing anything incorrectly? I've tried loads of different things to get past this boot loop.
re: rooting and recovery
whatishappening said:
After I've followed every step, my phone still gets stuck in the same boot loop as always. It never loads to recovery mood after flashing the stock ROM using Odin v3.09.
I used the NK4 rom. Am I doing anything incorrectly? I've tried loads of different things to get past this boot loop.
Click to expand...
Click to collapse
Here are the steps you need to do to root and install custom recovery:
1: Download and Odin flash cf-autoroot which can be found here:
https://www.dropbox.com/s/jokv7avj6pphjkq/CF-Auto-Root-trltetmo-trltetmo-smn910t.tar?dl=0
2: Download and Odin flash twrp custom recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.1.1-trltetmo.tar
Once you have successfully odin flashed both the TAR files you should have root
and custom recovery too.
Good luck!
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.1.1-trltetmo.tar
Misterjunky said:
Here are the steps you need to do to root and install custom recovery:
1: Download and Odin flash cf-autoroot which can be found here:
link removed
2: Download and Odin flash twrp custom recovery which can be found here:
link removed
Once you have successfully odin flashed both the TAR files you should have root
and custom recovery too.
Good luck!
[/URL]
Click to expand...
Click to collapse
is it possible that my problem of being stuck in a boot loop and restarting is due to a fully drained battery?
I asked because my phone doesn't ever charge when plugged in, it instead immediately attempts to boot. Should I purchase a second battery and attempt to boot?
---------- Post added at 01:25 AM ---------- Previous post was at 01:18 AM ----------
I've attempted to flash that recovery image multiple times. It's an .img file. How am I supposed to attach it using ODIN PDA?
re: tar files
whatishappening said:
is it possible that my problem of being stuck in a boot loop and restarting is due to a fully drained battery?
I asked because my phone doesn't ever charge when plugged in, it instead immediately attempts to boot. Should I purchase a second battery and attempt to boot?
---------- Post added at 01:25 AM ---------- Previous post was at 01:18 AM ----------
I've attempted to flash that recovery image multiple times. It's an .img file. How am I supposed to attach it using ODIN PDA?
Click to expand...
Click to collapse
I don't know where you got the IMG file, but both of the links I posted
only contain TAR files which needs to be flashed in Odin's PDA slot.
My mistake was unzipping the recovery file when I should have not been doing that. I've done both of the things you suggested and now my phone auto boots with a battery icon and continuously boot loops, but instead of saying "Samsung Galaxy Note 4" for a second before boot looping, it shows the battery icon.
youtube.com/watch?v=Bj6Zssy3-ZQ&feature=youtu.be
I apologize for linking as a new member, but this is not spam and I had to modify the link to include a video demonstration of what I'm describing. Thank you.
---------- Post added at 02:02 AM ---------- Previous post was at 01:38 AM ----------
whatishappening said:
My mistake was unzipping the recovery file when I should have not been doing that. I've done both of the things you suggested and now my phone auto boots with a battery icon and continuously boot loops, but instead of saying "Samsung Galaxy Note 4" for a second before boot looping, it shows the battery icon.
youtube.com/watch?v=Bj6Zssy3-ZQ&feature=youtu.be
I apologize for linking as a new member, but this is not spam and I had to modify the link to include a video demonstration of what I'm describing. Thank you.
Click to expand...
Click to collapse
Just for fun, here is a video of what happens when I attempt to boot into recovery mode. Notice that I do not need to press the power button because my phone always attempts to auto-turn on when it is plugged in.
youtube.com/watch?v=zgbqQTuImcM&feature=youtu.be
My Note 4 is stuck in a boot loop after flashing. It gets to the T-Mobile logo, stays there for about 30 seconds and reboots. Any way around this?
Thanks in advance.
Foxhoundz said:
My Note 4 is stuck in a boot loop after flashing. It gets to the T-Mobile logo, stays there for about 30 seconds and reboots. Any way around this?
Thanks in advance.
Click to expand...
Click to collapse
Try redownloading the firmware and reflashing.
Sometimes downloads have hiccups.
Just used the exact same file and flashed today, worked fine as usual (usually flash stock about once a week).
Sent from my trltetmo using XDA Premium 4 mobile app
I was able to get it working.
For those facing the boot loops, simply go into the stock recovery mode during boot and clear your cache. That should fix any remaining issues.
Also, always make sure to factory reset before the first boot.
Perfect!
Perfect, flawless tutorial. Worked Great, ready for Lollipop OTA!
Baseband and Bootloader
For some reason I downloaded the baseband and bootloader for ANK4.
I Odin'd back to stock successfully and am wondering if I need to flash this too.
Still "custom" after unrooting
Unrooted my t-mobile note 4 using the guide, went to re-root using the same method I did before, chainfire/twrp, and get an error when hitting the start button in Odin. Every time. Even after unroot the device status still says custom. Could that be affecting re-root? Anyone else have this issue?
I've asked before in this thread:
http://forum.xda-developers.com/note-4-tmobile/help/root-unroot-kies-t3003971
Sorry for link but didn't want to copy/paste everything.
Have you tried a different version of Odin? I usually rock 3.0.4
Android_Monsters said:
Have you tried a different version of Odin? I usually rock 3.0.4
Click to expand...
Click to collapse
I've tried every version of Odin I can find... And multiple CF sources.
Razorfengraul said:
I've tried every version of Odin I can find... And multiple CF sources.
Click to expand...
Click to collapse
I've used this method multiple times to stock and re root, haven't had any problems.
Few things that may he the problem...
Are you using the factory cord that came with your device?
Are you putting your device in download mode?
Are you turning on debugging in the Developer Settings?
Do you have the correct drivers for your device?
Sent from my SM-N910T using XDA Premium 4 mobile app
devynbf said:
I've used this method multiple times to stock and re root, haven't had any problems.
Few things that may he the problem...
Are you using the factory cord that came with your device?
Are you putting your device in download mode?
Are you turning on debugging in the Developer Settings?
Do you have the correct drivers for your device?
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes to everything other than the Samsung cable... Would that really make a difference?
Alright, as stated, I've followed this guide flawlessly... Factory reset before first boot, wiped cache, everything. Device status still showed "custom" and i was unable to download OTA updates due to custom binary. (mundane, i know, but proves my point)
So i went to re-root.
This is my command line in Odin upon flashing CF Auto Root:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am i missing... Every version of Odin out there and every available CF download i can find... Happens every time.
Razorfengraul said:
Yes to everything other than the Samsung cable... Would that really make a difference?
Click to expand...
Click to collapse
Yes, ODIN sometimes only works if you have the original Factory Cable.
I've run into MANY problems (like the one you're explaining) when not using the cord that came with it.
That's your problem. Use the factory cord.
Sent from my SM-N910T using XDA Premium 4 mobile app

[Q] Not able to install cwm custom recovery in galaxy n7000

Hi,
I have rooted my galaxy n7000 running on stock 4.1.2 DDLSC using the supersu. After root tried to install the cmw custom recovery but failed then tried to flash/install the philz custom recovery and its also failed. I have tried following options.
1. downloaded the .zip version of philz and tried to flash it using stock recovery "Update from external storage". When it was updating suddenly phone was getting turned off. Tried two to three times.
2. Also tried the ODIN v1.85 and v3+. downloaded the tar.md5 file matching to n7000, and when tried to flash it using ODIN two times it got struck at "SetupConnection: and 2 to 3 times it got failed. saying
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.12.8-n7000.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help me. any kind of your help will be greatly appreciated.
I am getting mad now.
(Phone is working fine not bricked)
Exactly what PhilZ kernel do you have downloaded?
this "philz_touch_6.12.8-n7000.tar.md5" i have downloaded from the site.
Rooted using Supersu.
My n7000 details are given below.
Model number
GT-N7000
Android version
4.1.2
Baseband version
N7000DDLs6
Kernal version
3.0.31-906407
[email protected] #3
SMP PREEMPT Web Mar 6 19:53:40 KST 2013
Build number
JZO54K.N7000DDLSC
Hope this help. I am still on stock. Just rooted with supersu and trying to install customer recovery.
What is the reason for other recovery?
What rom do you want to install?
User_99 said:
What is the reason for other recovery?
What rom do you want to install?
Click to expand...
Click to collapse
wanted to install the lollipop or kitkat.
Please guide me how to install philz or cmw recovery.
What am I doing wrong, why the philz is not getting flash using ODIN or stock recovery.
I have also tried the "flashify" app. and when flashing philz recovery its saying "Partition flashed successfully" but when going to recovery mode there I find stock recovery. Nothing is working.
you need to flash a custom kernel which includes the recovery. as far as i know it is not possible to flash recovery only with keeping stock kernel. philz provided several kernels for N7000 with appropriate recovery for many different android versions.
Zoomselection said:
wanted to install the lollipop or kitkat.
Please guide me how to install philz or cmw recovery.
What am I doing wrong, why the philz is not getting flash using ODIN or stock recovery.
I have also tried the "flashify" app. and when flashing philz recovery its saying "Partition flashed successfully" but when going to recovery mode there I find stock recovery. Nothing is working.
Click to expand...
Click to collapse
Get a philz kernel that matches your ROM build number. In your case its ddlsc. If you don't find that xxlta will also do.
I understand that need to download the kernal. just to confirm is it "Signed" .zip file of philz?
Last time I was rooted with the philz signed .zip file. Root was successfull but recovery was still stock. and when I flash the recovery using CWM App. my phone bricked. it was struck at samsung logo. Some how I flashed the stock rom and my note got a life.
Now this time I am scared to do the same. But still will give a try.
Right now my phone is rooted with supersu. To flash the philz kernal with recovery, Do i have to unroot first and then flash? Or I can flash without unrooting?
Thanks for suppoting. XDA is the good place for anyking of troublesooting and memebers here are best in supporting.
Can you please provide the url from where to download the philz kernal.
You can use the zip or tar file. Zip is preferred. You don't need to unroot.
Thanks you so much. was able to successful install the philz recovery
My phone is bricked due to my friend mistake. As per your suggestion I have downloaded the philz kernel. flashed it and philz recovery was installed. I was so happy, My friend asked to see the phone and I gave him. In my phone the "ClockWorkMod app" was installed from google play. My friend asked me whether he can backup the data or not. I said ok do it. He open the "ClockWorkMode app" and went to backup and clicked on it. it asked for the name of the backup. He have given the name and clicked on the ok button. Suddently phone got turned off and was struck at "Galaxy Note GT N7000" boot screen. I tried to do the power off using power button but again it was getting turned on automatically and getting struck at boot screen. Taken the battery out.
tried to go into recovery mode but was not able to go there. Only download mode is working. I flash the "Philz recovery" using ODIN.
and when reboot the phone got struck at same boot screen with an additional yellow triangle.
Can it be re-cover or it is hard brick? Please suggest something. I have downloaded the stock DDLC tar file from sammobile site. Do I need the partition .pit file? I tried to find out the partition .pit file for 16gb version but all links are broken.
Help me please.
Zoomselection said:
Thanks you so much. was able to successful install the philz recovery
My phone is bricked due to my friend mistake. As per your suggestion I have downloaded the philz kernel. flashed it and philz recovery was installed. I was so happy, My friend asked to see the phone and I gave him. In my phone the "ClockWorkMod app" was installed from google play. My friend asked me whether he can backup the data or not. I said ok do it. He open the "ClockWorkMode app" and went to backup and clicked on it. it asked for the name of the backup. He have given the name and clicked on the ok button. Suddently phone got turned off and was struck at "Galaxy Note GT N7000" boot screen. I tried to do the power off using power button but again it was getting turned on automatically and getting struck at boot screen. Taken the battery out.
tried to go into recovery mode but was not able to go there. Only download mode is working. I flash the "Philz recovery" using ODIN.
and when reboot the phone got struck at same boot screen with an additional yellow triangle.
Can it be re-cover or it is hard brick? Please suggest something. I have downloaded the stock DDLC tar file from sammobile site. Do I need the partition .pit file? I tried to find out the partition .pit file for 16gb version but all links are broken.
Help me please.
Click to expand...
Click to collapse
Ouch, try reflashing everything according to the previous instructions again. Remember to clear cache and do a factory reset after that, the Rom Manager aka ClockWorkMode app is kinda useless..
Back to life,
After bricking my phone I was in so much stress. Was thinking all the possible way like re-partition csc etc... then suddenly thought why not flashing the stock rom which is downloaded. Puts the phone in download mode. open the ODIN 1.85 connected the phone with pc and selected the stock DDLSC tar md5 file, taken a deep breath and remembered all the gods and clicked on the start button.
flashing started within 10 min it finished and phone re-booted. back to stock rom without loosing any kind of data. To my surprise all the app which was moved to external card was automatically detected and checked the sd phone memory and all my personal file and data with contacts and messages was available. Once again many many thanks to XDA and all of you.
Again rooted the phone with Philz kernel. LOL.
Can you please help me. How to do nandroid backup and whether it can be flash by ODIN or not.
Make a nandroid backup by booting into recovery and choosing backup. Or use an app like zipinstaller.
No odin cannot flash a nandroid backup. It has to be restored using recovery only.

Categories

Resources