Hello, im completely new to android world.
I want to root the phone and i tried using that version with odin 3.04.
Inside it it has several files in this order list view: ipl.bin, normal2.bin, normal.bin, recovery.img, ssgtest.img, STE_boot.bin
When i clicked start it added the 1st file (ipl.bin) and stopped (FAIL).
I know that this CMW isn't for my phone (NFC), so i ask these questions see if anyone can help me:
1 - How can i replace that "ipl.bin" with the original on my phone? Can i extract the ipl.bin to see its contents ?
2 - Do i need to enable USB DEBUG MODE on my phone settings ? (some people say yes others don't say anyting, very confusing...)
3 - Where can i get CMW for I8190N (with NFC) ?
GraphicAdventure said:
Hello, im completely new to android world.
I want to root the phone and i tried using that version with odin 3.04.
Inside it it has several files in this order list view: ipl.bin, normal2.bin, normal.bin, recovery.img, ssgtest.img, STE_boot.bin
When i clicked start it added the 1st file (ipl.bin) and stopped (FAIL).
I know that this CMW isn't for my phone (NFC), so i ask these questions see if anyone can help me:
1 - How can i replace that "ipl.bin" with the original on my phone? Can i extract the ipl.bin to see its contents ?
2 - Do i need to enable USB DEBUG MODE on my phone settings ? (some people say yes others don't say anyting, very confusing...)
3 - Where can i get CMW for I8190N (with NFC) ?
Click to expand...
Click to collapse
1. Why you want to mess with ipl.bin?
2. USB debug is not needed in download mode. If it's bricked it would be pretty impossible to turn it on anyway.
3. CWM is the same for all i8190's. take a look at my sig for all recoveries.
tys0n said:
1. Why you want to mess with ipl.bin?
2. USB debug is not needed in download mode. If it's bricked it would be pretty impossible to turn it on anyway.
3. CWM is the same for all i8190's. take a look at my sig for all recoveries.
Click to expand...
Click to collapse
Thanks for replying.
I don't want to mess with it. odin copied that file to my phone, and i would like to undo that.
What is ipl.bin ? part of recovery mode ? does original recovery mode have ipl.bin ?
I think that for my model it only needs recovery.img, is that right ? so the others files have no purpose.
If CWM works for all models, why did it fail ?
I saw several post already saying that I8190N is different and will not work. Could you confirm ?
GraphicAdventure said:
Thanks for replying.
I don't want to mess with it. odin copied that file to my phone, and i would like to undo that.
What is ipl.bin ? part of recovery mode ? does original recovery mode have ipl.bin ?
I think that for my model it only needs recovery.img, is that right ? so the others files have no purpose.
If CWM works for all models, why did it fail ?
I saw several post already saying that I8190N is different and will not work. Could you confirm ?
Click to expand...
Click to collapse
Ok, so this was something you flashed to gain root. What firmware is that?
Yeah, your right, if you want root you only need to flash cwm or twrp recovery, than the supersu.zip, or a rom.zip of your choice.
I tried to flash the ClockWorkMod 6.0.2.7 with the 3 buttons hack included. It started the process, copied the ipl.bin and i supposed that when it tried to copy the next file (normal2.bin) it failed. So what does ipl.bin do ? phone is working fine, so i suppose that file is only for recovery menu or something.
My phone has 4.1.2 JB with JZO54K.I8190NXXAMB1 and Kernel 3.0.31-900027
So what recovery.img should i use for NFC version ?
GraphicAdventure said:
I tried to flash the ClockWorkMod 6.0.2.7 with the 3 buttons hack included. It started the process, copied the ipl.bin and i supposed that when it tried to copy the next file (normal2.bin) it failed. So what does ipl.bin do ? phone is working fine, so i suppose that file is only for recovery menu or something.
My phone has 4.1.2 JB with JZO54K.I8190NXXAMB1 and Kernel 3.0.31-900027
So what recovery.img should i use for NFC version ?
Click to expand...
Click to collapse
Which ever one you prefer, CWM or TWRP
i personally prefer TWRP since its easier to use on this phone
Related
Hi
I'm looking for root & cwm for this device. specially cwm recovery or another kernal/recovery that can install zip files.
there is something like that?
thanks a lot.
avicohh said:
Hi
I'm looking for root & cwm for this device. specially cwm recovery or another kernal/recovery that can install zip files.
there is something like that?
thanks a lot.
Click to expand...
Click to collapse
someone managed to do the root?
nixonik said:
someone managed to do the root?
Click to expand...
Click to collapse
managed some soft bricks in how not to root. Odin up & waiting if a dev comes up with it
I am also waiting for the root!
not sure if it would work, but im working on a rom right now that is pre-rooted, but like i said i dont think that it will work,, i hope someone makes a cwm recovery soon
I'm currently trying to create a prerooted rom the way I did it for my tablet.
Extracting the system image from the Update package was easy, currently I'm trying to mount the syste,.img to set the rights and add the SU binaries.
If this works out, how can I flash this ROM?
With KIES? Or Update.zip on SD?
Is there an Update mode, and how can I get there?
edit: Okay... I was able to mount the System.img, but this is not that straight forward as in the img of my tablet.
I found a lot of folders, but no .apk, known folder or something I could work with.
softbricked
gummygum said:
managed some soft bricks in how not to root. Odin up & waiting if a dev comes up with it
Click to expand...
Click to collapse
Have you tried adb shell?. I am not allowed to post outside links, but if you type "londatiga net/it/how-to-use-android-adb-command-line-tool/" in Google, you will get the appropiate link
Could you explain with some derail how did you unbricked the phone?
Thanks a lot
teddybt said:
I'm currently trying to create a prerooted rom the way I did it for my tablet.
Extracting the system image from the Update package was easy, currently I'm trying to mount the syste,.img to set the rights and add the SU binaries.
If this works out, how can I flash this ROM?
With KIES? Or Update.zip on SD?
Is there an Update mode, and how can I get there?
edit: Okay... I was able to mount the System.img, but this is not that straight forward as in the img of my tablet.
I found a lot of folders, but no .apk, known folder or something I could work with.
Click to expand...
Click to collapse
ou should of just setup android kitchen and put the boot.img and system.img in there and it extracts them, plus you can pre-root it aswell
I have posted here for help!
Hi guys, I'm pretty new here.
I was wondering if there is any official 4.1.1 Jellybean for SIII Mini, 'cause my phone is pretty dead at this moment. I tried to download from official servers some packages , and use them with Odin ...but the phone is still at the main screen " Samsung Galaxy S III Mini GT-I8190 ". Any ideas how to manage with this ?
Or can I use another firmware, as 2.3.4 Gingerbread?To downgrade the device just to work?
zeek12 said:
Hi guys, I'm pretty new here.
I was wondering if there is any official 4.1.1 Jellybean for SIII Mini, 'cause my phone is pretty dead at this moment. I tried to download from official servers some packages , and use them with Odin ...but the phone is still at the main screen " Samsung Galaxy S III Mini GT-I8190 ". Any ideas how to manage with this ?
Or can I use another firmware, as 2.3.4 Gingerbread?To downgrade the device just to work?
Click to expand...
Click to collapse
Do you tried to get some of this firmwares:
samsung-updates.com/device/?id=GT-I8190
and installing with:
trickytweaks.com/i8190xxaljl-4-1-1-jelly-bean-update-gt-i8190-s3-mini-how-to.htm
Yes, I have tried with my provider's firmware , but nothing happened. Still at logo screen. I have also tried with other firmwares, but still at a dead end. Right at this moment I'm flashing my phone again, hoping that something will change.
Had it stuck by flashing custom boot.img. Solved it by flashing 1 file image from samfirmwares as pda in Odin 1.85 default settings
Sent from my GT-I8190 using xda app-developers app
I have succesfully extracted the PIT file from my S3 mini with the Heimdall software, but I don't wanna use it to flash with Odin because I think it's pretty messed up. Can anyone provide me with their Galaxy S3 Mini PIT file, hoping to rescue my dead phone ?
no boot into recovery mode and wipe data/cache that should get the phone booting again, esppecially after flashing firmwares with odin
winxuser said:
no boot into recovery mode and wipe data/cache that should get the phone booting again, esppecially after flashing firmwares with odin
Click to expand...
Click to collapse
Well, if the recovery mode can be accessed with Volume Up + Home + Power, then I can say that my S III Mini won't get into it.If I press these buttons the phone just gets on, and remains at Samsung Logo. So that is why I'm asking for a PIT file, 'cause I can't get into recovery mode to erase all data, so I can flash my phone again using Odin.
I have tried all official firmwares and still nothing. I guess my SIII Mini partitions are a little (or a little more) messed up, and I need to use Re-Partition from Odin so I can revive my phone.And to do this I need a PIT file from a working phone.
Or there is another way to get into recovery mode, excepting Volump Up + Home + Power?
Thanks for the answers.
elco27 said:
There is a solution for hte problem you have with that phone.
Check this thread for more info: h t t p://forum.gsmhosting.com/vbb/f286/i8190-galaxy-s3-mini-hang-startup-solution-1574562/#post8970902
Click to expand...
Click to collapse
Well, the NsPro tool requiers a box, that costs 170$. The program is useless without that box. I have downloaded it and doesn't work without that box.Another solution is by using a JTAG box, which does the pretty same thing, but again, it is expensive.
I was thinking that if I'll repartion my phone it will resolve the boot.img file, because it's in the "softbrick" at this moment.
helpline
Have you tried emailing or phone SAMSUNG`s helpline, they might help.
Write this image file whit odin 1.85 and voala you phone revive.
Pls use tanks buton
That param.tar file I saw it is for S II . Does it work for a S III mini too? Aren't 2 different devices?
Hello Guys
I Have a Galaxy tab GT-P1000 WI-FI+GSM
It's Stuck In a BOOTLOOP:crying::crying:
AND THE 4 TOUCH BUTTONS IN THE BOTTOM OF THE TABLET DOESN'T WANT TO LIGHT:crying::crying::crying:
BECAUSE WHEN THEY LIGHT THE TABLET WORKS FINE
I Have TO PUT IT IN THE CHARGER FOR ABOUT 8-9 HOURS TO WORK
AFTER I COMPLETLY FORMATED THE DEVICE AND INSTALED THE STOCK 2.3.3 ROM THE PHONE STUCK IN A BOOT LOOP
I PUT IT IN THE CHARGER FOR ABOUT 8-9 HOURS BUT THIS TIME IT DIDN'T WORK:crying::crying::crying:
PLEASE,HELP.
What did you do? What files did you flash? We need details
Here Are The Files
Jarmezrocks said:
What did you do? What files did you flash? We need details
Click to expand...
Click to collapse
P1000JPJPD_P1000OJPJPE_P1000JXJP4_HOME.tar.md5
gt-p1000_mr.pit
dbdata.tar
these files worked fine until i formated every thing on the device using overcome kernel 4.0.0 and reinstalled those files
i tried every way that made it run in the past but....nothing,the 4 touch buttons in the bottom of the device doesn't work any more
the tablet will work if they light up
Preacher_M4 said:
P1000JPJPD_P1000OJPJPE_P1000JXJP4_HOME.tar.md5
gt-p1000_mr.pit
dbdata.tar
these files worked fine until i formated every thing on the device using overcome kernel 4.0.0 and reinstalled those files
i tried every way that made it run in the past but....nothing,the 4 touch buttons in the bottom of the device doesn't work any more
the tablet will work if they light up
Click to expand...
Click to collapse
Yes your device should be recoverable. If it is working all bar the touch buttons then something just must have gone wrong in the flash?
I have had issues with similar files. I would suggest that you go to the thread where you downloaded the Overcome kernel and you will see the download for GB_Stock_Safe_v5.zip. Try >>> Here thread by @sos_sifou
Ensure that you have copied all of the data you require off your internal SDcard (Try mounting the card in recovery if you are unable to boot your device - Overcome kernel should allow this very easily)
Put the device into download mode, Use Odin 1.7 (only use this version)
select the same pit gt-p1000_mr.pit as PIT (naturally) and then choose GB_Stock_Safe_v5.tar as PDA, and then choose JP4 modem (or similar - what ever is best for your region)
Flash your device.
If you have troubles or brick your device (it happens - I must have done it at least 30 times last week ) then download Heimdall Oneclick Unbrick by Adam Outler >>> here. You will probably need this so you should download it anyway.
Any questions. Post back here.
BTW I am no expert, I have just failed lots of times fairly recently so I am in good order to pass on this valuable info.
I'm download the files now
Jarmezrocks said:
Yes your device should be recoverable. If it is working all bar the touch buttons then something just must have gone wrong in the flash?
I have had issues with similar files. I would suggest that you go to the thread where you downloaded the Overcome kernel and you will see the download for GB_Stock_Safe_v5.zip. Try >>> Here thread by @sos_sifou
Ensure that you have copied all of the data you require off your internal SDcard (Try mounting the card in recovery if you are unable to boot your device - Overcome kernel should allow this very easily)
Put the device into download mode, Use Odin 1.7 (only use this version)
select the same pit gt-p1000_mr.pit as PIT (naturally) and then choose GB_Stock_Safe_v5.tar as PDA, and then choose JP4 modem (or similar - what ever is best for your region)
Flash your device.
If you have troubles or brick your device (it happens - I must have done it at least 30 times last week ) then download Heimdall Oneclick Unbrick by Adam Outler >>> here. You will probably need this so you should download it anyway.
Any questions. Post back here.
BTW I am no expert, I have just failed lots of times fairly recently so I am in good order to pass on this valuable info.
Click to expand...
Click to collapse
i will try that,thanx:good:
i flashed the files
Jarmezrocks said:
Yes your device should be recoverable. If it is working all bar the touch buttons then something just must have gone wrong in the flash?
I have had issues with similar files. I would suggest that you go to the thread where you downloaded the Overcome kernel and you will see the download for GB_Stock_Safe_v5.zip. Try >>> Here thread by @sos_sifou
Ensure that you have copied all of the data you require off your internal SDcard (Try mounting the card in recovery if you are unable to boot your device - Overcome kernel should allow this very easily)
Put the device into download mode, Use Odin 1.7 (only use this version)
select the same pit gt-p1000_mr.pit as PIT (naturally) and then choose GB_Stock_Safe_v5.tar as PDA, and then choose JP4 modem (or similar - what ever is best for your region)
Flash your device.
If you have troubles or brick your device (it happens - I must have done it at least 30 times last week ) then download Heimdall Oneclick Unbrick by Adam Outler >>> here. You will probably need this so you should download it anyway.
Any questions. Post back here.
BTW I am no expert, I have just failed lots of times fairly recently so I am in good order to pass on this valuable info.
Click to expand...
Click to collapse
i flashed all the files,they worked fine but i am stuck in the boot loop
i opend the recovery and these words were written by yellow color
-- verfing internal mmc block...
checksum confirmation -> check(0)
not need checksum confirmation
already executed!!...
#MANUAL MODE#
-- Updating application...
successfully updated application.
--Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/EGY/system/'.
successfully applied multi-CSC
I Think that's the problem
i need help,thanx:laugh:
I tried upgrading my international N7000 to CM10.3 following the instructions in
http://wiki.cyanogenmod.org/w/Install_CM_for_n7000
but now the phone won't even boot into the recovery, all it shows is
Samsung
GALAXY Note
GT-N7000
/ \
/ | \
/--*-\
When i tried flashin from my Mac iusing Heimdall,
the download finished on the mac, but on the N7000
it still showed the blue line etc. I waited a lng time and tried
rebooting, but got the above.
Re-flashing in Heimdall had no effect.
I then tried flashing
hardcore-speedmod-ics-recovery-n7000.tar
using Odin 3.185 from my VMwars Fusion XP install,
and that seemed to finish ok, but no luck either.
I looked for the latest CWM 6.0.4.3 recovery, but I cannot find any
odin-flashable format for it, and of course I cannot use the sdcard
as I cannot even boot into any recovery as is.
Can anyone suggest next steps?
sejtam said:
I tried upgrading my international N7000 to CM10.3 following the instructions in
http://wiki.cyanogenmod.org/w/Install_CM_for_n7000
but now the phone won't even boot into the recovery, all it shows is
Samsung
GALAXY Note
GT-N7000
/ \
/ | \
/--*-\
When i tried flashin from my Mac iusing Heimdall,
the download finished on the mac, but on the N7000
it still showed the blue line etc. I waited a lng time and tried
rebooting, but got the above.
Re-flashing in Heimdall had no effect.
I then tried flashing
hardcore-speedmod-ics-recovery-n7000.tar
using Odin 3.185 from my VMwars Fusion XP install,
and that seemed to finish ok, but no luck either.
I looked for the latest CWM 6.0.4.3 recovery, but I cannot find any
odin-flashable format for it, and of course I cannot use the sdcard
as I cannot even boot into any recovery as is.
Can anyone suggest next steps?
Click to expand...
Click to collapse
1st things 1st. Why would u use heimdall or odin? And what is your current ROM before trying to flash CM 10.3, was it stock? You should have looked for CWM recovery or Philz safe kernels as base when doing ROM flashing ESPECIALLY custom roms. From what you said, then can you still boot into download mode? I have no knowledge of heimdall so just download Stock Firmware, flash it with odin and see if you can boot your N7000 first.
The worst case scenarios is you are experiencing emmc bug-brick. go to the thread and read carefully to deduce your type of 'brick' and find solutions there. Good Luck.
I was on a stock 4.0.4 (but rooted). I originally tried flashing the cwm from the sd card, but after starting to load it it also just hung,
so I looked for an alternative..
I found a post on stockroms (http://forum.xda-developers.com/showthread.php?t=1424997) but the links all point to hotfile.com. which my browser says it cannot find. is hotfile dead? Is there an alternative?
sejtam said:
I was on a stock 4.0.4 (but rooted). I originally tried flashing the cwm from the sd card, but after starting to load it it also just hung,
so I looked for an alternative..
I found a post on stockroms (http://forum.xda-developers.com/showthread.php?t=1424997) but the links all point to hotfile.com. which my browser says it cannot find. is hotfile dead? Is there an alternative?
Click to expand...
Click to collapse
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app
same problem
Jackwu696 said:
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
i have the same problem , only mine loads into the recovery menu , ive tried finding a working odin to nstall it back to factory.
when i had this problem last night , i wasnt sure what i done but i managed to install a custom rom and that worked but now i seem to be getting status 7 error ,
my computer wont recognise my phone so i cant do anything that way . any ideas or links to solutions will be appreciated
i have the same problem
conanbrapp said:
i have the same problem , only mine loads into the recovery menu , ive tried finding a working odin to nstall it back to factory.
when i had this problem last night , i wasnt sure what i done but i managed to install a custom rom and that worked but now i seem to be getting status 7 error ,
my computer wont recognise my phone so i cant do anything that way . any ideas or links to solutions will be appreciated
Click to expand...
Click to collapse
I'm sorry so did u succeed or did you not succeed in installing the custom rom? If your custom rom boots fine then all u need is to search for solving status 7 error thread. My advice to all noobs is to always try n avoid installimg anything except stock rom in odin. Always read and re read before flashing anything that's beyond your knowledge. Basic knowledge of flashing cusroms is :
1. ALWAYS make sure you're on SAFE and COMPATIBLE KERNEL. Most rom threads ALWAYS Include threads/links to a specific recovery/kernel to use. Read n RE READ that.
2. Wipe everything IN RECOVERY mode before flashing a rom.
Sent from my GT-N7000 using XDA Free mobile app
fixed miine
Jackwu696 said:
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
Jackwu696 said:
I'm sorry so did u succeed or did you not succeed in installing the custom rom? If your custom rom boots fine then all u need is to search for solving status 7 error thread. My advice to all noobs is to always try n avoid installimg anything except stock rom in odin. Always read and re read before flashing anything that's beyond your knowledge. Basic knowledge of flashing cusroms is :
1. ALWAYS make sure you're on SAFE and COMPATIBLE KERNEL. Most rom threads ALWAYS Include threads/links to a specific recovery/kernel to use. Read n RE READ that.
2. Wipe everything IN RECOVERY mode before flashing a rom.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
im not Sure what i did , i unbricked (soft) and successfully installed kitkat not sure exactly how but it worked.... still have root too ... had and error about needing to wipe data for suib i think but thats the only fallback i fell into
conanbrapp said:
im not Sure what i did , i unbricked (soft) and successfully installed kitkat not sure exactly how but it worked.... still have root too ... had and error about needing to wipe data for suib i think but thats the only fallback i fell into
Click to expand...
Click to collapse
If you're able to boot up properly n prompted to wipe, then do it. But do it in recovery not on device.
Ok, I downloaded one of the stock kernels for my internatinal N7000, but flashing that with Odin 3.185 hangs about 3/4 through (has now been
sitting there for >60 mins).
Looks like I am screwed?
The file I found is KIES_HOME_N7000XXLT4_N7000OXALT4_1103517_REV02_user_low_ship.tar.md5
I f I wanted to try flashing this with Heimdall, I'd need to know partition numbers I think
Where can I get those?
Or should I get another file?
sejtam said:
Ok, I downloaded one of the stock kernels for my internatinal N7000, but flashing that with Odin 3.185 hangs about 3/4 through (has now been
sitting there for >60 mins).
Looks like I am screwed?
The file I found is KIES_HOME_N7000XXLT4_N7000OXALT4_1103517_REV02_user_low_ship.tar.md5
I f I wanted to try flashing this with Heimdall, I'd need to know partition numbers I think
Where can I get those?
Or should I get another file?
Click to expand...
Click to collapse
Before that, do u have KIES installed? KIES is NOT compatible with odin and will cause potential trouble. So is some firewall and antivirus apps. You need to disable all of them before using odin. Please search the thread http://www.sammobile.com/firmwares/ for stock rom site.
Sent from my GT-N7000 using XDA Free mobile app
Ok. I downloaded two stock roms from sammobile:
[email protected] 1 mathias staff 808649674 May 9 10:53 N7000XXLT5_N7000MBCLT1_MBC.zip
[email protected] 1 mathias staff 750466356 May 9 10:50 N7000XXLRL_N7000OXELR5_MBC.zip
but both fail with some (unreadable, apparently character set issue) error under ODIN.
I found this:
http://droidangel.blogspot.sg/2012/01/samsung-galaxy-note-gt-n7000-all.html
which shows how to do a full flash , including PIT file, but the links again go to hotfile which seems to be down.
http://hotfile.com/dl/140099962/b9e0d63/Q1-20110914_16GB.pit.rar.html
Where can I get a) separate
CODE_N7000xxxxx_CLxxxxxxx_REVxx_user_low_ship.tar.md5
MODEM_N7000xxxxxx_REV_00_CLxxxxxx.tar.md5
GT-N7000-CSC-MULTI-xxxxxx.tar.md5
and the PIT file?
sejtam said:
Ok. I downloaded two stock roms from sammobile:
[email protected] 1 mathias staff 808649674 May 9 10:53 N7000XXLT5_N7000MBCLT1_MBC.zip
[email protected] 1 mathias staff 750466356 May 9 10:50 N7000XXLRL_N7000OXELR5_MBC.zip
but both fail with some (unreadable, apparently character set issue) error under ODIN.
I found this:
http://droidangel.blogspot.sg/2012/01/samsung-galaxy-note-gt-n7000-all.html
which shows how to do a full flash , including PIT file, but the links again go to hotfile which seems to be down.
http://hotfile.com/dl/140099962/b9e0d63/Q1-20110914_16GB.pit.rar.html
Where can I get a) separate
CODE_N7000xxxxx_CLxxxxxxx_REVxx_user_low_ship.tar.md5
MODEM_N7000xxxxxx_REV_00_CLxxxxxx.tar.md5
GT-N7000-CSC-MULTI-xxxxxx.tar.md5
and the PIT file?
Click to expand...
Click to collapse
Of course you fail... When using ODIN, U should have downloaded the .tar. if you downloaded a zip. then unzip it first to get the tar file, then you flash it with odin. All requests are included in the stock.tar And PLEASE DO NOT Play with PIT files if you don't know what you are doing.
So now what you need to do is. :
1. DISABLE KIES (Uninstall it better), Your firewall, antivirus.
2. Install CORRECT Samsung USB driver. (Search keyword "download samsung N7000 usb drivers")
3. Unzip your zip file and extract the tar.file.
4. Run ODIN as Administrator (Right click/run as)
5. Go to download mode. connect your device to Pc/laptop.
6. Wait until Odin detects your device, click AP/PDA and choose the tar file you extracted.
7. DO NOT tick partition.
8. Let it run
Of course I unzipped the zip to get a SINGLE .tar.md5, but flashing that fails on factoryfs about 3/4 through. consistently.
sejtam said:
Of course I unzipped the zip to get a SINGLE .tar.md5, but flashing that fails on factoryfs about 3/4 through. consistently.
Click to expand...
Click to collapse
Try updating your odin. Use the newest vers. And try and read this https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNGd2e3iG5hkDeo0KyAjGuCSfQSLUw . If All fails then it's a confirmed SUPER-BRICK and there's nothing except samsung service centre can help you now... Sorry for not being able to help more..
Thanks. That led me to
http://forum.xda-developers.com/showthread.php?t=1656635
where I found the PIT file, but for ROMs pointed to http://forum.xda-developers.com/showthread.php?t=1530501
which again points to hotfile and fileserve.com , which (besides being under maintenance) says
FileServe can only be used to download and retrieve files that you have uploaded personally.
which makes it useless for finding ROMs...
sejtam said:
Thanks. That led me to
http://forum.xda-developers.com/showthread.php?t=1656635
where I found the PIT file, but for ROMs pointed to http://forum.xda-developers.com/showthread.php?t=1530501
which again points to hotfile and fileserve.com , which (besides being under maintenance) says
FileServe can only be used to download and retrieve files that you have uploaded personally.
which makes it useless for finding ROMs...
Click to expand...
Click to collapse
His link to ROMS were basically the same ones you can download at sammobile.
Hi, after a failed rooting my s3 blocked, i tryed to put on the I9300XXALE8_I9300ITVALE7_ITV (i'm from italy), but now is blocked on the Samsung logo. Also when i go in download mode it says
Odin mode
Product name : GT-I8190
Custom binary donwload : YES (17 counts) (ye i tryed 17 times to fix it)
Current binary : custom
System status : Official
So i have some questions : Can i send it to assistance and they can repair it (with warranty)? , should i try to re download the I9300XXALE8_I9300ITVALE7_ITV file? ( i tryed with 3 versions of odin, with 2 of them it says : failed, with the newest it says : pass but it blocks on Samsung logo)
Or there is something other that i can do?
(sry bad english)
Are you flashing a i9300 firmware to a i8190?
No wonder why it doesn't work.
tys0n said:
Are you flashing a i9300 firmware to a i8190?
No wonder why it doesn't work.
Click to expand...
Click to collapse
+1 Just find the ROM you want to install here http://live.samsung-updates.com/index.php?device=GT-I8190 then download and flash this http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip and finally go and install this https://play.google.com/store/apps/details?id=eu.chainfire.supersu (or update if you have it installed after you flash the file above). I can root any phone with this simple method
NOTE : It doesn't matter which country you're from, you can flash any firmware you like, so why not be it the latest one available for your device (ANF3 at the moment)? You can still change language to Italian after flashing so there's really no difference between regions
WildDorian27 said:
Hi, after a failed rooting my s3 blocked, i tryed to put on the I9300XXALE8_I9300ITVALE7_ITV (i'm from italy), but now is blocked on the Samsung logo. Also when i go in download mode it says
Odin mode
Product name : GT-I8190
Custom binary donwload : YES (17 counts) (ye i tryed 17 times to fix it)
Current binary : custom
System status : Official
So i have some questions : Can i send it to assistance and they can repair it (with warranty)? , should i try to re download the I9300XXALE8_I9300ITVALE7_ITV file? ( i tryed with 3 versions of odin, with 2 of them it says : failed, with the newest it says : pass but it blocks on Samsung logo)
Or there is something other that i can do?
(sry bad english)
Click to expand...
Click to collapse
you tried i9300 firmware that is wrong, you should i8190 format
koragg97 said:
+1 Just find the ROM you want to install then download and flash this UPDATE-SuperSU-v1.99r5.zip and finally go and install this eu.chainfire.supersu (or update if you have it installed after you flash the file above). I can root any phone with this simple method
NOTE : It doesn't matter which country you're from, you can flash any firmware you like, so why not be it the latest one available for your device (ANF3 at the moment)? You can still change language to Italian after flashing so there's really no difference between regions
Click to expand...
Click to collapse
I've never rooted a phone so I was just wondering how to do it like this? I've read some guides but it's really unclear still, one that I tried simply didn't work (the one where you flash CWR with Odin as the first step). Can you/someone tell me how to do this exactly, please? This is what I'm thinking atm:
1) If I already have the latest version I'm happy with, do I still need to download that version again or can I just go ahead with the SuperSU flashing part?
2) How do I in practice flash the SuperSU zip file? I currently have Odin v.3.0.7 and Minimal ADB and Fastboot installed on my PC. Thanks for any help!
Nanhia said:
I've never rooted a phone so I was just wondering how to do it like this? I've read some guides but it's really unclear still, one that I tried simply didn't work (the one where you flash CWR with Odin as the first step). Can you/someone tell me how to do this exactly, please? This is what I'm thinking atm:
1) If I already have the latest version I'm happy with, do I still need to download that version again or can I just go ahead with the SuperSU flashing part?
2) How do I in practice flash the SuperSU zip file? I currently have Odin v.3.0.7 and Minimal ADB and Fastboot installed on my PC. Thanks for any help!
Click to expand...
Click to collapse
If you don't have the latest firmware on your phone, download it from the link I gave (it's a .md5 file). Now go to Developer Options in your phone's settings and tick USB Debugging. Power off your phone. After that enter download mode on your phone by pressing power+volume down+home button while turning it on. You'll see a big message on your screen saying "Downloading, don't unplug target". Now plug your s3 mini into the pc and start Odin. Select PDA and find the .md5 file from before. Make sure that f.reset time and re-partition are unchecked and then press start. Once it's done odin will say "pass" and your phone will reboot. Congrats, you now have the latest firmware on your s3 mini
Now in order to root it, you need a custom recovery so let's go
On Google search "TWRP 2.7.1.1 Android-Andi xda" and download it from the attachments of his post (it's a .md5 file again). Again turn off the phone and enter Download Mode like before. Now do the same steps with Odin as the first time (with the firmware), but this time select the TWRP.md5 file instead of the firmware one in PDA section of Odin. Make sure all the options on the left are ticked/unticked exactly like the first time and hit Start. The "Pass" message should be displayed and the phone should reboot.
Congrats, you now have the latest TWRP Recovery on your s3 mini
And the last step - rooting it
Download the SuperSU.zip from the link in my post and copy it to your device's memory (internal or external). Now in order to enter Recovery Mode you need to turn off your phone and turn it back on by holding the power+volume up+home buttons until you see a "TeamWin" message on your screen. This recovery is touch based so just select install, choose the SuperSU.zip file and flash it. Reboot the phone.
Now you're rooted and on the latest firmware arty:
For future updates do the same. Just change the firmware .md5 file with the latest one available. The rest is the same xD
Man, I got tired ...
Sent from my " Black Beauty " using XDA Premium 4 mobile app
koragg97 said:
For future updates do the same. Just change the firmware .md5 file with the latest one available. The rest is the same xD
Man, I got tired ...
Click to expand...
Click to collapse
Thankd! Bookmarking for sure for future reference!
Nanhia said:
Thankd! Bookmarking for sure for future reference!
Click to expand...
Click to collapse
:thumbup:
Sent from my " Black Beauty " using XDA Premium 4 mobile app
I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
I used a tool to fix baseband the tool reboot my phone into download mode and flash something
i try to boot my phone it get bootloop i try flash stock rom still bootloop
i flashed combination file still bootloop
i think the tool did something to efs partition
Did you complete a backup with TWRP?
willhemmens said:
did you complete a backup with twrp?
Click to expand...
Click to collapse
no i didint flash twrp my device not rooted
devil499 said:
no i didint flash twrp my device not rooted
Click to expand...
Click to collapse
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk
Good luck dude when the mention above most really suck having a bricked note 9
jaylence said:
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
i have done that but didnt worked
plz help me
i didint find pit file for my device
n960f
HtcOnekid said:
Good luck dude when the mention above most really suck having a bricked note 9
Click to expand...
Click to collapse
i found this post https://forum.xda-developers.com/ga...ide-fix-n950f-efs-failed-to-mount-dm-t3831184
i beg you can you plz help understand it
Extract Stock firmware AP file (rename .md5 to .tar)
this i cant understand wich should i rename or what i do
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wuc...f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
What? I'm using desktop. Is there a different view on mobile?
Bricked Note 9 due to efs
devil499 said:
I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]
Click to expand...
Click to collapse
I have the same problem with my note 9. Im looking if anyone can provide me with efs file of N960F Binary 3 so i can get it unbricked again.
I found this website but it has efs files for binary 1 and 2 not 3. Will it still work if i use binary 2 efs?
//frpdone.com/efs-mdm-samsung/
Did u find a solution?