[Q] Unable to root via Odin: Write protection: Enable - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Hi guys, ladies,
I try to root my i9195 but Odin fails to write. I also noticed when putting in download mode that it says: Write protection: enable. See attached screenshot.
It's a Vodafone version of the S4 Mini, I can use different carrier SIM cards, but I cannot remove the Vodafone bloatware like 'Discover'.
Any ideas how to root this version and how to disable this Write Protection?
Thanks!
Andreas

Hello write protection is not the problem, I had the same trouble with mine you need to disable all antivirus and firewall temporarily then flash.
Sent from my GT-I9195 using XDA Premium 4 mobile app

Ezylife said:
Hello write protection is not the problem, I had the same trouble with mine you need to disable all antivirus and firewall temporarily then flash.
Sent from my GT-I9195 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow, that actually worked! Thank you
For everyone that is in the same process, I used Windows8 and disabled my firewall and Windows Defender.
I followed the following guide for rooting:
http://www.techbii.com/root-galaxy-s4-mini-cwm-recovery-installation-odin/
Andreas

adewilt said:
Wow, that actually worked! Thank you
For everyone that is in the same process, I used Windows8 and disabled my firewall and Windows Defender.
I followed the following guide for rooting:
http://www.techbii.com/root-galaxy-s4-mini-cwm-recovery-installation-odin/
Andreas
Click to expand...
Click to collapse
This did not work for me. under download mode it say Write Protection: Enable
Funny thing is that I get a PASS when i flash with odin. "<OSM> All threads completed. (succeed 1 / failed 0)" But when I boot the vodafone boot animation is still there. And if I Check under About it is still the old Product Code XFV not XFA which i just flashed.
I am loading
Product Code: XFA
PDA: I9190XXUAMF7
CSC: I9190OJVAMG1
MODEM: I9190XXUAMF7
It has this on:
Product Code: XFV
PDA: I9190XXUAMF7
CSC: I9190OJVAMG1
MODEM: I9190XXUAMF7
any ideas?

Fix Boot logo
jjziets said:
This did not work for me. under download mode it say Write Protection: Enable
Funny thing is that I get a PASS when i flash with odin. "<OSM> All threads completed. (succeed 1 / failed 0)" But when I boot the vodafone boot animation is still there. And if I Check under About it is still the old Product Code XFV not XFA which i just flashed.
I am loading
Product Code: XFA
PDA: I9190XXUAMF7
CSC: I9190OJVAMG1
MODEM: I9190XXUAMF7
It has this on:
Product Code: XFV
PDA: I9190XXUAMF7
CSC: I9190OJVAMG1
MODEM: I9190XXUAMF7
any ideas?
Click to expand...
Click to collapse
You need to go to recovery mode and do factory reset and wipe cache after that reboot. to go to recovery mode (volume up + Home Button + Power button)

didn't work...
baachs said:
You need to go to recovery mode and do factory reset and wipe cache after that reboot. to go to recovery mode (volume up + Home Button + Power button)
Click to expand...
Click to collapse
I have the same problem. my phone is on XFV and I'm trying to flash XFE, but it's still on XFV, even after wiping the cache and doing another factory reset after the initial reboot...
any other advice?

S4 i9505
Same here,
I'm stuck on Get PIT for mapping..
Luckily I was able to upload a bootloader so I can still change ROMs, but for the rest the phone is fu#d up.
Impossible to restore the pit file, impossible to upload new modem
Next time stay away from Saumsung
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Click to expand...
Click to collapse

The boot animation can only be changed if you change it manually or flashing a stock ROM from sammobile.com, not by rooting.
If I where you, I flash an unbranded stock firmware with odin (go to sammobile.com, download it and follow the steps from there). That will remove vodafone's bloatware. And if you still want to root, go with it.

Problem with Odin Flash
Hi
I have a S4 mini (i9195) with StockRom 4.4.2. My Problem is when i flash a recovery with Odin (3.10) show Odin me "succes" but there is no custom recovery. Every time i boot in recovery there is only the stock recovery. I try to close BitDefender and WinFirewall and i do a FactoryReset and wipe cache i open Odin as Admin but it doesn´t work and the KnoxCounter stay always on 0x0!What can i do?

Syriass said:
What can i do?
Click to expand...
Click to collapse
Apart from disabling windows firewall, defender and antivirus... u must also terminate any kies programs running in the background. Go to taskmanager and choose processes tab. Then look for kies or any process with kies in its name. Right click on them and choose end.
Then try odin flashing again.

sasank360 said:
Apart from disabling windows firewall, defender and antivirus... u must also terminate any kies programs running in the background. Go to taskmanager and choose processes tab. Then look for kies or any process with kies in its name. Right click on them and choose end.
Then try odin flashing again.
Click to expand...
Click to collapse
Sorry i forgot it no Kies install and driver package is the last from Samsung!

The Problem was the StockRom or the Kernl! The Stock was VD2-I9195XXUCNJ6 I flash with Odin another Stock (DBT) and after this it works!

I have manged to install cwm recovery and Sammys root v2 zip for root access which I now have but still says
write protection: enable
Does this mean I'm still stuck with stock rom?
Sent from my GT-I9195

I plugged my phone in and I didnt get a response from my PC, but it works while in CyanogenMod, meaning it's not the cable. It says WRITE PROTECTION: enabled in the top corner and I uninstalled Avast! a while ago. Do I still need to disable windows firewall or what else can I try? I want to go back to stock, using Odin 3.09

Essem G said:
I plugged my phone in and I didnt get a response from my PC, but it works while in CyanogenMod, meaning it's not the cable. It says WRITE PROTECTION: enabled in the top corner and I uninstalled Avast! a while ago. Do I still need to disable windows firewall or what else can I try? I want to go back to stock, using Odin 3.09
Click to expand...
Click to collapse
Hello you can ignore write protection, but you need to temporarily disable all antivirus and firewall software and then it should work.

The way I solved this is by flashing a deknoxified bootloader. I can post my bootloader later

Did not work
Ezylife said:
Hello you can ignore write protection, but you need to temporarily disable all antivirus and firewall software and then it should work.
Click to expand...
Click to collapse
I went through control panel and disabled Windows Firewall, but when I did the same steps Odin still did not detect my phone with the "Added!!" message. Did I miss a step, are there more things to disable, or is Write Protection really a problem? Even if it's not, what does that message in BL mean because I don't remember that there before
Thanks for the help for now though, because now I hear the sound in Windows when I plug in my phone

Essem G said:
I went through control panel and disabled Windows Firewall, but when I did the same steps Odin still did not detect my phone with the "Added!!" message. Did I miss a step, are there more things to disable, or is Write Protection really a problem? Even if it's not, what does that message in BL mean because I don't remember that there before
Thanks for the help for now though, because now I hear the sound in Windows when I plug in my phone
Click to expand...
Click to collapse
What's your current ROM? I seen issues with people running cm ROMs and computer doesn't find the connect phone/tablet. If n almost any other ROM it should be fine. Just seems cm ROM don't like commuters
Sent from my GT-I9195

Weird
jimbomodder said:
What's your current ROM? I seen issues with people running cm ROMs and computer doesn't find the connect phone/tablet. If n almost any other ROM it should be fine. Just seems cm ROM don't like commuters
Sent from my GT-I9195
Click to expand...
Click to collapse
Strangely enough, I switched my USB port on my PC and it flashed normally. However, if you could help me on my other post that would be nice
http://forum.xda-developers.com/gal...problems-flashing-stock-t3129207#post61217108

I need your hel to disable write protection via odin on i9505
I have ROM: I9505XXUHOA7_OXAHOA7
Here is the message:
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ill try and download another firmware Now.

Related

Stuck at Boot Screen

Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Luke44 said:
Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Click to expand...
Click to collapse
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
shhbz said:
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
Click to expand...
Click to collapse
I flashed philz recovery. After pressing the power button just the battery symbol appeared... no reboot. So I treid to boot into the new recovery... but still the old recovery boots
Heres the log from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.11.2-n7100.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Luke44 said:
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Click to expand...
Click to collapse
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
shhbz said:
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
Click to expand...
Click to collapse
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Luke44 said:
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Click to expand...
Click to collapse
do u have kies installed when u trying odin if yes then delete it just install the samsung drivers nothing else and disable your antivirus too.
orelse u may try
thats quite strange ok now its time to try the mskip tool just delete all old samsung drivers and kies
and start fresh from here http://forum.xda-developers.com/showthread.php?t=1923956
and as far as the count in concerned its 1 as you were only able to enter recovery once thats why after that u were not able to so as many times u enter custom recovery the count increases
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Luke44 said:
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Click to expand...
Click to collapse
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
shhbz said:
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
Click to expand...
Click to collapse
Sorry but I cant find such a viedo...
Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
I tried to flsh this, but odin says:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
What exact information you can see on Download Mode Rt Upper corner.
post full details here
dr.ketan said:
What exact information you can see on Download Mode Rt Upper corner.
post full details here
Click to expand...
Click to collapse
In the right upper corner is nothing...
In the left upper corner:
ODIN MODE (written in red)
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
There is I am on phn so would be difficult for me to find but its simple u just select the pit file first in odin and flash keeping ur phn in download mode and then the firmware tar file
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried a different computer with different cable. On the computer I used this time there is not even kies installed.
Same result as before...
dr.ketan said:
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried it a few more times..it really doesnt work
Whats wrong with this !"§$%& phone:crying::crying::crying:

Guess what? I bricked my SGH-i317M :)

I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
idoit said:
I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
dicksteele said:
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
Click to expand...
Click to collapse
By reading around, I was getting the impression that I need to flash .pit file along with the stock ROM but as I don't want to get things worse I was reluctant to do it. My searches for odin package without sboot.bin takes me no where. Not that I am a super Android toddler but any help is certainly more than appreciated. Well Ok, I'm noob. admit it. :good:
Edit: I found out about N7100UBALJ2_N7100TCEALJ1_TCE ROM from http://forum.xda-developers.com/showthread.php?t=2523366 but not sure if that solves the problem or that's relevant as it's for N7100 and mine is SGH-i317m... same family but who knows maybe different ROMs! ?
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Don't use a pit file. That partitions all of your phone.
rangercaptain said:
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Click to expand...
Click to collapse
Update: I uploaded the recovery.log file from TWRP by accessing with adb in recovery mode.
Nothing happens when I connect it to PC in normal mode... I mean just connecting it as it is. (NOT in recovery mode or download mode).
Right now, I am in Windows and when I connect it in download mode, I try to adb but it says device not found. In recovery mode, I can adb but as I said in first post, I can't read or write. MicroSD is not recognized, so I can't put stock ROM there either. Is there any hope to get my phone back?
Don't use a pit file. That partitions all of your phone.
Click to expand...
Click to collapse
Well, I did try to flash a pit file from here, but it fails with same NAND Write error!
I have a good news.
So I went to /dev/block folder when ADBing and noticed mmcblk0 device. I manually mounted mmcblk0p1 and yoohoo it is mounted. It means now i can put my TWRP backup files there and run TWRP restore. Is that a good idea?! Does it make sense at all? I mean I am desperate for any way to get this thing back, a shadow of hope is huge for me too now.
Update: Ahhh damn it! I mount the MicroSD from adb to /external_sdcard (this is the folder where it used to mount my external microSD) in TWRP. Using File Manager provided by TWRP, I confirm the folder is there. But when I go to Restore section, it doesn't show any partition and it doesn't let me choose external memory. It's like this:
- Internal Memory (0MB)
- External Memory (0MB)
- USB OTG (0MB)
Any thoughts? I feel I am so close but not there yet.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
rangercaptain said:
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
Click to expand...
Click to collapse
Alright, done.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Click to expand...
Click to collapse
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Now to report back the result from Kies FER:
I follow the instructions word by word. As the screenshot shows, Kies tells me to put phone into "Recovery mode"by pressing on power button. Well, either Samsung doesn't know what recovery mode is or ... Anyways, I take battery out and etc and boot to normal phone by pressing on power button... and "Free Upgrade"button is still grayed out. I go to Recovery mode (Power + Home + Volume Up) and it is still grayed out. (first screenshot attached below)
It's only in Odin Download mode (Power + Home + Volume Down and then Volume Up) that it becomes available.
After some time, the following error appears. I have done it a couple of times now and I restarted my Windows too. but no dice.
(second screenshot attached below)
idoit said:
Alright, done.
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Click to expand...
Click to collapse
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
dicksteele said:
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
Click to expand...
Click to collapse
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
idoit said:
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
Click to expand...
Click to collapse
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
dicksteele said:
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
Click to expand...
Click to collapse
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms, 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
Awesome on the firmware site BTW !
dicksteele said:
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
Awesome on the firmware site BTW !
Click to expand...
Click to collapse
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
Hi Guy, my problem is that my phone lost baseband version and IMEI number. I download the stock rom: TLS_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3; The rom did not fix the issue. After I install it, the baseband version and IMEI number still shown Null. Could you please help me? Thousands thanks!
Click to expand...
Click to collapse
This was posted long before the 4.1.2 came around, but you have all the guts there when trying to roll back to 4.1.1 not even aware that there might be a new bootloader added on 4.1.2 I317MVLBMA3 update and returning back to 4.1.1 is quite risky
If you did not touch your device before using rooted kernels and/or custom. I suggests that you must stay on 4.1.2.
Click to expand...
Click to collapse
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
You won't lose your baseband or IEMI. What you are doing is returning your phone to 100% factory stock (except for the 4.3 bootloader). You can deal with any other issues as they arise/if they arise from a working phone easier than you can from a borked phone.
Why eight hours to download?
idoit said:
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
​
​
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
Click to expand...
Click to collapse
The losing the IMEI was because of a different issue I believe.... The /efs partition holds all the important cel info. As long as that's not hosed you're fine...
OMNIROM should not have touched that.
Backing up your /efs can be done a couple of ways.
http://www.xda-developers.com/android/backup-your-efs-partition-with-easy-to-use-app/
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
idoit said:
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
Click to expand...
Click to collapse
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
dicksteele said:
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
Click to expand...
Click to collapse
This is being downloaded quickly. Until that download is finished, I knew yesterday I downloaded I317M_BWC_I317MVLALJ2_I317MOYAALJ2_Original (Similar to the one you just said to download but for Bell). You're right, this one doesn't have sboot.bin but it does have boot.img. Anyways, I tried to flash it with Odin3 v3.04, and it fails on me!
Firmware update start...
boot.img
NAND Write Start!
Complete(Write) operation failed.​
Now, I have no idea what to do next! Wow, phones and even products from big companies like Samsung are so fragile.
[Off-topic]
Boy, these last 3 days had been hectic. First this happened to my Phone. Then today, when I was in Windows (which I rarely use, I went on Disk Management and made my C partition active). Stupid Windows, wiped all my partition table!!! And now my laptop is a piece of brick too. Oh boy, you know, when it rains it pours!

[SOLVED] Problems with rooting my Galaxy Note II (model N7100)

[SOLVED] Thanks to dabenaute for great help!
Hi guys!
I tryed to root my Galaxy Note II (model N7100) and something went wrong. I hope you guys can help me. Sorry for my bad english already.
So, I tryed to root my phone using this guide. I do everything like it said and when it was done, my phone opened same satup what was before I started. Because I am noob with this stuff, I think something went wrong. I dont know why, but I decide to make factory reset to my phone.
Then started problems. My phone try to reboot it self but it always stop in flashing Samsung logo.
Then I tryed this guide (1b) but Odin3 stop always in "Get PIT for mapping.."
<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..
Download mode in my phone says:
"ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREW: A2"
What I should try next? I am very grateful every help what I get!
Hello,
to root your phone,download "CF-Auto-Root-t03g-t03gxx-gtn7100.zip" here: http://download.chainfire.eu/264/CF-Root/CF-Auto-Root/CF-Auto-Root-t03g-t03gxx-gtn7100.zip
reboot your phone in download mode
open odin and check "AutoReboot"&"F.Reset Time"
connect your phone(you will see"added")
click on AP or PDA find cf autoroot
click on START and wait
after flash the phone will reboot
that's all,enjoy
dabenaute said:
Hello,
to root your phone,download "CF-Auto-Root-t03g-t03gxx-gtn7100.zip" here:
reboot your phone in download mode
open odin and check "AutoReboot"&"F.Reset Time"
connect your phone(you will see"added")
click on AP or PDA find cf autoroot
click on START and wait
after flash the phone will reboot
that's all,enjoy
Click to expand...
Click to collapse
Done this again and this what happens:
Odin message said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t03g-t03gxx-gtn7100.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
And after that, my phone screen is only black. When I try to open it, it has that "Samsung Galaxy Note II GT-N7100" text awhile and then screens goes black again.
Is my phone now brick?
JukkaP said:
Done this again and this what happens:
And after that, my phone screen is only black. When I try to open it, it has that "Samsung Galaxy Note II GT-N7100" text awhile and then screens goes black again.
Is my phone now brick?
Click to expand...
Click to collapse
please retry and uncheck"Re partition" : Bien:
dabenaute said:
please retry and uncheck"Re partition" : Bien:
Click to expand...
Click to collapse
It was already uncheck.
JukkaP said:
It was already uncheck.
Click to expand...
Click to collapse
sorry i have no other idea its the only way i know and use and it always works for me: (
dabenaute said:
sorry i have no other idea its the only way i know and use and it always works for me: (
Click to expand...
Click to collapse
I appreciat your help! Thanks!
I think that I broke my phone when I tryed factory reset.
JukkaP said:
I appreciat your help! Thanks!
I think that I broke my phone when I tryed factory reset.
Click to expand...
Click to collapse
Im thinking about something...
if you can go into recovery?do it
clear cache and then go into advanced and wipe dalvik cache
reboot
if that fails,go back into recovery and do a wipe factory/reset
and then try thishttp://forum.xda-developers.com/showthread.php?t=1915386
dabenaute said:
Im thinking about something...
if you can go into recovery?do it
clear cache and then go into advanced and wipe dalvik cache
reboot
if that fails,go back into recovery and do a wipe factory/reset
and then try this
Click to expand...
Click to collapse
I go in recovery and cleared cache but I don't understand what you mean by "advanced".
I got these options:
Reboot system now
Apply update from ADB
Apply update from external strorage
Wipe data/factory reset
Wipe cache partiton
Apply update from cache
JukkaP said:
I go in recovery and cleared cache but I don't understand what you mean by "advanced".
I got these options:
Reboot system now
Apply update from ADB
Apply update from external strorage
Wipe data/factory reset
Wipe cache partiton
Apply update from cache
Click to expand...
Click to collapse
hi,"advanced" is an option that you can find if you use philz recovery
dabenaute said:
hi,"advanced" is an option that you can find if you use philz recovery
Click to expand...
Click to collapse
I don't have that. I tryed instal that to my phone but now Odin doesn't even regonize it anymore.
which odin are you using to? you can find the latest philz here:http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100
odin v3.09:http://www.mediafire.com/download/b8w1on8pwd11yby/Odin+v3.09.zip
have you installed the latest drivers for your phone?
dabenaute said:
which odin are you using to? you can find the latest philz here:
odin v3.09:
have you installed the latest drivers for your phone?
Click to expand...
Click to collapse
I use Odin v3.07. I re-installed my phone drivers and boot computer, then odin regonized my phone. I installed philz_touch_6.25.0-n7100.tar.md5
This doesn't help:
dabenaute said:
if you can go into recovery?do it
clear cache and then go into advanced and wipe dalvik cache
reboot
Click to expand...
Click to collapse
Im from Finland, so is there any matter what files I use from here: http://forum.xda-developers.com/showthread.php?t=1915386
i know that thread its usefull,have you made a backup before flashing anything?
have you tried to reflash a stock rom?
---EDIT---
i found this:http://forum.xda-developers.com/showthread.php?t=2700479
dabenaute said:
i know that thread its usefull,have you made a backup before flashing anything?
have you tried to reflash a stock rom?
Click to expand...
Click to collapse
I am lost with that thread. Should I download something or read some adviced? Have to I download some rom?
When I tryed to root my phone, I try to use this guide (sry, that was missing in first post) and I don'n make any backups.
I think I know how to flash (in that thread have good help for that) but Im not sure what to download.
here is a stock rom"n7100xxuemk9"(NEE) 4.3:http://rapidgator.net/file/75b6f9c75caa96166fc0ca6582cf489b
n7100xxuelm3(THL):https://my.pcloud.com/#page=publink&code=XZhg1ZWTIv1SpmTCXVP4bKC0cP0mMWcLNX
Reinstall Complete Stock firmware using Odin & then root
Hi..
Looks like you have got boot loop for while trying to root your phone.
Don't worry.. now you need to reinstall the stock firmware on your device.
just follow the following steps:
1- Boot in recovery by pressing volume up, home button & power button simultaneously
2- go to mounts & storage & then..format system first, then format data & finally format cache
3- Now go back to the main menu of your recovery & do format data/factory reset then format cache & then go to advanced & wipe dalvik cache
4- Download your devices stock firmware from here http://www.sammobile.com/firmwares/1/ ..select your device model & country & download the file...latest firmwares are on top.
5- extract the .zip file you just downloaded & you will get a file with extension .tar.md5
6- Now Boot your device into download mode by pressing Volume down button, home button & power button simultaneously.
7- Launch Odin(v 3.07) now..u can download the attached file. (If the device is detected it will show the COM:# in the ID Com field.)
8- Select the PDA tab & browse & select the firmware file you just extracted.
9- Odin will take a while & finally it will display the message something like checking md5 finished successfully
10- click on the start button & sit back & relax...this may take upto 8 minutes..
11- Unplug the phone after flashing is complete & let the phone boot..
12- Now you will have stock recovery, if you want you will need to flash a custom recovery again.
13- Boot in download mode again & select the PDA tab & browse for the chainfire auto root file (download it from here http://download.chainfire.eu/264/CF-Root/CF-Auto-Root/CF-Auto-Root-t03g-t03gxx-gtn7100.zip )
14- extract the file & select this file from the PDA tab in ODIN & click the Start button.
15- let the flashing complete & the phone will display the recovery mode screen again & it will root the device.
16- However after booting the device you might not be able to open the superuser app.
17- To fix this go to play store & update your SuperSu app & then launch it & then it will ask you to disable Knox & select Yes.
18- Congratulations...your device is now rooted.
Hit thanks if i helped you..Let me know if you face any issues... :good:
dabenaute said:
here is a stock rom"n7100xxuemk9"(NEE) 4.3:http://rapidgator.net/file/75b6f9c75caa96166fc0ca6582cf489b
n7100xxuelm3(THL):https://my.pcloud.com/#page=publink&code=XZhg1ZWTIv1SpmTCXVP4bKC0cP0mMWcLNX
Click to expand...
Click to collapse
Thanks alot! I am very happy because you try to help me out and dont care my stupid questions
I have now downloaded those and now I try to figure out should I use both in flashin? These guides doesn't help me because files are different.
So, where I shoud but those two files in Odin? Is those files enough?
JukkaP said:
Thanks alot! I am very happy because you try to help me out and dont care my stupid questions
I have now downloaded those and now I try to figure out should I use both in flashin? These guides doesn't help me because files are different.
So, where I shoud but those two files in Odin? Is those files enough?
Click to expand...
Click to collapse
try out the steps i have mentioned above in my post..i have also attached the Odin v3.07 & clockwork recovery ver 6 files..
for clcockwork recovery you need to extract the .zip file & you will get a .tar file which you can flash using the PDA tab in odin
this wont take more than 15 minutes & as you will wipe everything you will lose all your apps & contacts..but the data on your internal sd card should remain untouched..
Hello @JukkaP,if you take mk9 you have to decompress it to have 4 files after:
open odin and put
bootloader in the 1st case,2sd ap,3t phone,4th csc
phone in download mod
connect it to the pc
you will have "added"
clic on "start" and wait
phone will reboot after flash
---EDIT----
No question is stupid

[Q] Tab pro 12.2 stuck in bootloop

Hi everyone!
My Galaxy tab pro (SM-T900) is stuck in bootloop. More precisely I can see the first Samsung galaxy tab pro screen but it restart before the samsung animation.
The tab was initially with official rom rooted with CF-Auto-Root-v2wifi-v2wifixx.
I have already tried several things without significative improvement.
At first I tried to reinstall with Kies. Kies says my version is: PDA:NB5/CSC:NB2 (XEF). But after the window asking to reboot in download mode kies stops saying my device can not be recovered. I have read it could be due to a discrepancy of CSC or things like that between Kies and the Tab.
Recovery mode says:
Odin mode
Product name: SM-T900
Current binary: Official samsung
System status: Custom
KNOX waranty void: 1
RP SWREV: A1
My Knox flag was turned to 1 and I don't know how to set System status back to official.
I have also downloaded the stock ROM XEF from Sammobile and flashed it with odin 3.09. The process goes smoothly but the tab doesn't boot.
Even after a wipe (data/factory reset and cache) in recovery mode.
In recovery mode I could not install Cyanogenmod or other Zip files. The process stop during the package verification and says:
E:footer is wrong
E:signature verification failed
I flashed a TWRP 2.8 to try with a different recovery but again the Zip are not installed.
Have you any idea or any direction to investigate?
Thank you
If ur tab is US version then u have to flash XAR(cellular south) available through sammobile through odin and then let tab update itself after reboot. U will loose root
Sent from my LG-D800 using XDA Free mobile app
lingarajug said:
If ur tab is US version then u have to flash XAR(cellular south) available through sammobile through odin and then let tab update itself after reboot. U will loose root
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Actually my tab is from France so XEF version is the most adapted.
I think flashing a different version would be rejected. Right?
Yes it can brick too
Sent from my LG-D800 using XDA Free mobile app
You can flash any ROM as long as it is for SM-T900. The builds may have different apps, keyboards, and WiFi connectivity can be an issue due to WiFi channels being slightly different for each region.
The thing is that flashing zip in recovery mode leads to the error: footer is wrong.
Is there any log file I could read to find where the boot process loops?
If dodo99x is right u can flash xar version which is for usa and flash it through odin
Sent from my LG-D800 using XDA Free mobile app
I tried to flash XAR and XAC stock roms but Odin return a Fail with the following log:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> sboot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> boot.img
<ID:0/012> recovery.img
<ID:0/012> system.img
<ID:0/012> FAIL!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
As tar.md5 files doesn't have exactly the same size, I wonder if it is necessary to check Re-partition in Odin.
Never ever touch repartition. Super dangerous if you don't have the correct .pit file to recreate them. Those sound like bad downloads. You can also try to use a different usb cable and usb port on your pc.
I have successfully downloaded and installed the last rom stock revision for France: T900XXUANI1_T900XEFANI2_XEF
But I'm still stucked in Bootloop.
Other versions (XAR and XAC) still fail.
How can I get the PIT file for SM-T900?
As I can see and copy files with TWRP, is there any log file I should check to see what is wrong?
I would try wiping cache, sytem, dalvik, data and internal storage in twrp, then reinstall the france image file in Odin. This will of course erase all data you have on the tablet, but it should take you out of your bootloop. I have yet to see any valid PIT files for the SM-T900, or SM-P900. If you mess with the partitions without one, you won't even be able to flash anything in Odin afterwards.
No problem for the personnal data. I just would like to recover my tab.
I have wiped all the internal partitions: Dalvik, cache, system, internal data.
I have reboot in download mode and launched a flash of the T900XXUANI1_T900XEFANI2_HOME.tar.md5 with Odin 3.09
I also used voodoo magic!
But still the bootloop
I think the problem comes from an other partition not flashed with this process.
What other partitions are used to start Android?
Is there any log file to check?
Very unusual... try flashing cm11 for SM-T900 via TWRP. Will that one boot?
No The Cyanogen ROM doesn't boot either.
I'm still looking deeper in the boot process to identify the problem.
While I was reading this: http://en.miui.com/thread-15659-1-1.html
I just realized that the misc partition was absent from my tab.
I create an empty one and reflashed a stock rom but it doesn't solve the boot problem.
What files are usualy inside misc? Where can I find a copy of them?
At this point I would just get Samsung to fix it. Unless you can find a PIT file for ODIN...
Even with Knox value to 1 and custom Rom/kernel/recovery?
Do you think Samsung will reset my tab in those conditions?
By the way, when I look in the Boot folder with TWRP file manager, I don't see any file. The boot partition indicates an occupied size of 8Mo.
Where are those files? How can I acces to them?
Knox warranty has nothing to do with your hardware warranty. Just reflash stock rom via ODIN and send it back. Tell them you can't get it to boot, and that's it.
Do u know if u have usb debugging enabled. Maybe try booting into rom after complete wipe of all. It will probably sit on sam logo and will not boot due to no firmware and wait for few minutes and restart into download mode and flash correct firmware from sammobile. I did this in my old galaxy s 2 long long ago and it worked.
Sent from my LG-D800 using XDA Free mobile app
Hi,
Just a short feedback.
I finally succeed to finish the restoring process of Kies but it didn't fixed my bootloop and the Download mode indicated:
Current binary: Samsung official
System status: Custom
Knox warranty void: 0x1
I decided to return the device to Samsung (France).
3 weeks after: tadaam! Everything was fixed. Samsung changed my motherboard and battery.
No charge and no warranty void due to knox or rom modification.
I am so released
... I am now looking for a way to root the device without triggering knox
Is triangle away working with SM-T900?
Moklockus said:
Even after a wipe (data/factory reset and cache) in recovery mode.
In recovery mode I could not install Cyanogenmod or other Zip files. The process stop during the package verification and says:
E:footer is wrong
E:signature verification failed
I flashed a TWRP 2.8
Click to expand...
Click to collapse
To fix this try
Advanced wipe with everything ticked except recovery then try to flash zip without reboot.
Helped me on the footer issue and if this succeeds you should be able to boot.
Hope that helps

Looking for a debrick.img for Android 5.1.1

Is anyone able to point me in the right direction or is willing to make one?
The i747 does not have a stock 5.1.1 rom; therefore, there is no debrick image for a 5.1.1 rom.
What bootloader is on the phone? Did any of the images from the debrick thread boot the phone?
Does installing 5.1 change your bootloader?
As in Cyanogenmod 12.1?
Softbricked my S3, and I'm not sure which way to attempt to recover/debrick & would appreciate any advice.
SGH I747 (ATT)
rooted 2 years ago just after 4.3 OTA updated, flashed with CM 11.
Had that on there for almost a year, got bored & installed carbonrom.
Beginning of december, flashed CM 12.1.
A week ago it got stuck on the boot logo.
Still able to get into both Recovery & download modes.
Clockwork mod 6.0.4.7
trying to flash from a new image or wipe & factory restore both give me
Code:
detected file system ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching unconditionally
E: error in /storage/sdcard1/cm-12.1-201511117-sna[status 0] installation aborted
trying to use Odin, it gives me
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
but never does anything, even hours later.
At unplug, I get
Code:
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The info on the download screen is
Code:
odin mode
product name: sgh-i747
custom binary download: yes (6 counts)
current binary: custom
system status: custom
qualcomm secureboot: enable
warranty bit: 1
bootloader ap swrev: 2
My guess from another thread is that the /system and /data partitions are not wiped properly, causing those partitions to be formatted with read-only (R/O) permissions rather than read-write (R/W)? But those files are definitely not right for my phone, so what now?
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
audit13 said:
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
Click to expand...
Click to collapse
Good to know.
Thanks.
But how do I get twrp onto the phone?
was actually trying to put twrp on with odin, but that's not working.
The downloads I've seen are for:
app-phone doesnt boot
odin- aint working
TWRP Install - Requires TWRP 2.8.4 or higher already installed
dd Install Method - oh, didn't see that one. I'll try that & let you know.:laugh:
---------- Post added at 06:54 AM ---------- Previous post was at 06:16 AM ----------
well, I'm not figuring it out....
As per the twrp page, tried: dd if=/sdcard/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
tried: dd if=/storage/sdcard1/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
did ls (hey it's like linux!)
got possible locations: external_sd, sd-ext, sdcard, also looked under mnt.
file not found error
cd'ed & ls'ed to /storage/sdcard1/ there it frickken is!
ran the command there, sans path, and still get file not found error
arrrrgh.
Try this:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy
very detailed response, thanks. I've tried most of that, as some thread I was reading said that twrp probably has the capability to fix the issue, and CWM definitely doesn't.
Odin never really does anything, though. How long should I wait?
This step is the one I haven't done "7) open Odin 3.07 and uncheck everything except f. reset time;" Just left everything alone the multiple times I tried. Hopefully that'll make a difference.
Tried 3.07, 3.09, 3.10.6. I'll try again.
By default in Odin 3.07, only auto reboot and f reset time are checked.
What do you mean when you say Odin does nothing? Does the phone appear as a com device in Odin? Are there error messages in Odin during the flash process?
never gives anything other than:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
not at a windows computer for a couple days. stuck on linux mint with no internet. has heimdall & adb, though....
have twrp img & tar, cm12.1, and gapps on the sdcard.
All I can suggest is to try and get access to a pc or try VMware with win7.
Tried again last night for about 12 hours, no response from Odin.
Decided to give jtag a shot.
Contacted the jtag guy & gave him all the above info.
He says
"Unfortunately there are many indicators that your phone has a hardware failure.... Most likely a failed emmc memory chip.
1) the phone getting stuck on boot logo for no reason.
2) Odin not flashing...
3) files not found or... Not being able to do.
These are all indicators that the emmc memory chip is toast...... The biggest clue is finding the phone stuck on boot logo... Out of nowhere for no reason.
Jtag would not be able to fix it.
Thank you"
:crying::crying::crying::crying::crying::crying:
Thanks for the help.
Might sell the remains.
16G I747 blue, normal wear & tear, small chip in one corner, the case covers it.
2 stock batteries
1 7800mah best4power battery
1 otterbox defender modified to hold extended battery without the turtleback
any offers?
i suggest trying on a Windows machine before giving up. I am not convinced the memory is damaged.
That was on a windows machine...
Odin recognizes the phone but it won't flash twrp? Have you tried different USB cables and USB ports?
I found that my s4 and s3 would fail to flash if I don't use the USB cable that came with my Samsung or LG phones.
yes to both cable & ports.
bought an LG K7, which I mostly hate, and can not root.
keeping my S3, looking for someplace cheap to replace the chip.
I bought my lg k7 today(LGMS330)metropcs i rooted it in 2 mins.with xda's KINGROOT..then removed Kingroot with WOLFDROIDS script...and now im running BUSYBOX STERICSON 1.24.1 and ChainFires SUPERSU 2.49..IT KILLS me when people cant root there devices...i did this ALL in the BURGERKING BATHROOM GOIN BOO BOO
Ok so i rooted my darn k7 ...but like a jackars i bricked it...no TWRP...NO KDZ FIRMWARE...CAN ANYONE PLEASE ...PRETTY PLEASE SEND ME A LINK TO THE METROPCS variant of the LG K7 (TRIBUTE 5) KDZ STOCK FIRMWARE..I JUST BOUGHT A $150 ELECTRONIC PAPERWEIGHT...the k7 is so new there is no support anywhere...in fact all u really find is the ads for the debut of the device in stores ...major noob mistake..im truly embarassed..PLZ HELP
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
just got a $150 paperweight...lg ms330 i do hate you now...
o4tuna said:
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
Click to expand...
Click to collapse
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
AbErCrMbPlAyA said:
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
Click to expand...
Click to collapse
I had a amazing talk with the lg develeopers yesterday....since I am in the same boat since my lg k7 is bricked....I ask them for the kdz firmware so I can reflash my phone....you wanna know what they told me?
first they ask: whats a kdz file?
their answer: We don't make those thing you need the official lg tools to update your device firmware....so we cant help you...
Me: I am extremely pissed now since they are lying to me & then I showed them a link from their server to DOWNLOAD a kdz file firmware for another device that I had....
their answer: we dont know what you are talking about...sorry we can't help you!
I even went to my nearby metropcs store & explained to him what happen...
first. he didn't understand the following:
1-bootloader
2. boot image
3. recovery mode
4. download mode
5. kdz firmware
6. bricked & softed-bricked
the f-cking guy told me I can't do anything, but "report my phone lost or stolen" so I can get a new one....
How the hell are these idiots getting jobs when they have NO IDEA what to do on how to fix a phone
My level of anger is now over 9000.....

Categories

Resources