SCH-I545 VRUGOF1 [Guide][Rooted][Bricked] De-brick,ROM list, Kernel MOD

SCH-I545 VRUGOF1 [Guide][Rooted][Bricked] De-brick,ROM list, Kernel MOD - Verizon Samsung Galaxy S 4

YOUR BOOTLOADER IS LOCKED, NO CUSTOM RECOVERY, NO MARSHMALLOW,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NO CM, NO AOSP, NO TWRP, NO CWM, NO PHILZ, NO WHINING!
What does that mean?
Who Locks Them?
Want more info: eFuse
For those that are still curious: If we are serious about unlocking the bootloader
Don't need to de-brick? Scroll down and see "The Good News"
The Five Stages of OF1 Grief:
Denial: “Oh, no problem, I’m rooted!”
Anger: "Darn that Verizon."
Bargaining: “I’ll downgrade to Kit-Kat, if it will unlock my bootloader.”
Depression: “No CM-13? I can’t go on!”
Acceptance: “Next time I’ll do more research before buying a new phone.”
A list of common mistakes that cause boot loops or worse on stock ROM
Flashing TWRP, CWM, or Philz
Flashing a Custom ROM*
Flashing a Custom Kernel*
Flashing X-posed*
Flashing just about anything*
Uninstall System App
Uninstall System Priv-App
Convert System App to User App
Convert User App to System App
Uninstall System App That Was a User App But Got Converted To System App By User
Install a Font
Install a Bootanimation
TOUCHING ANYTHING THAT SAYS (ODEX)
Tweaking the Kernel*
Un-tweaking the Kernel*
This list could go on for a while, but I think you get the point:
*Without proper knowledge, see below.
Don't worry, there are options. Keep scrolling.
Mistakes that can cause a Hard brick:
1. Trying to downgrade your bootloader so you can unlock it and flash TWRP and install CM13
______________________________________________________________
Please try this first, before posting a HHEEELLLPP! thread.
If you are soft-bricked(boot loop):
Instructions:
Download firmware here: Firmware/Odin
Extract (unzip) the firmware file
Open Odin3 v3.10.7 (Other versions included JIC)
Boot device into Download Mode:
With the device powered down, press and hold Power & Volume Down buttons.
When warning appears, release and press Volume up to Enter Download (Odin) Mode.
Connect device and wait until you get a blue tab in Odin, upper left below ID:COM
Click the AP button and navigate to the extracted firmware and select it. Odin will verify the md5. This may take a little while.
Once verified click the start button. Sit back and wait. When finished you will see "PASS" and phone will reboot:
JOY
If you are Hard-bricked (unresponsive, not recognized by Odin):
NO JOY
See your local VZW dealer.
Or you could try this:
J-Tag
________________________________________________________________
The Good News
If you are rooted, have Kinguser SuperSu and Busybox installed, and are good at following directions look here:
or
or
or here:
and here:
Also Available:
Unsigned Kernel Module For OF1!
By @[SIZE="4"]klabit87[/SIZE]
Flashfire Install!
Extreme Battery Saving Method
By @[SIZE="4"]ATGkompressor[/SIZE]
So tell me. Who needs CM now?
Thanks to @stang5litre, @klabit87, @Albe95, @mohammad.afaneh, @Surge1223 and @ATGkompressor
for providing a means to improve our phones.
Myself and the others listed are NOT responsible
for the damage that YOU do to your phone!
See next post for additional notes.
Don't forget to

If you are having trouble with Odin, first try a different USB cable. Then try a different version of Odin. See link below.
I have attached a .pit file also. This is unverified, See link below.
Always follow the OF1 instructions in ROM link's.
Hint: FF = Flashfire = OF1
Take one: View attachment Statement.pdf
Older Odin Versions
Pit File

Don't forget J-tag [emoji106] [emoji2]
Sent from my SM-G935V using Tapatalk

stang5litre said:
Don't forget J-tag [emoji106] [emoji2]
Click to expand...
Click to collapse
Added It's actually a great video. I got a little misty :crying:

im always corrupt file when im download at sammobile, anyone have direct link pls

AnggaKun said:
im always corrupt file when im download at sammobile, anyone have direct link pls
Click to expand...
Click to collapse
Hey. In what way do you mean corrupt? Is Odin giving you an error?

bg260 said:
Hey. In what way do you mean corrupt? Is Odin giving you an error?
Click to expand...
Click to collapse
not at odin but when im try to extract it(firmware.zip) with using winrar.. it show text archive is corrupt :crying: can u help me pls
im got bootloop on of1 firmware when im instaling kernel A3 in stang5litre, im wanna flash it but when im download firmware at sammobile it always corrupt
#ask can if im flash using oc1 firmware? thank u :good:

AnggaKun said:
not at odin but when im try to extract it(firmware.zip) with using winrar.. it show text archive is corrupt :crying: can u help me pls
im got bootloop on of1 firmware when im instaling kernel A3 in stang5litre, im wanna flash it but when im download firmware at sammobile it always corrupt
#ask can if im flash using oc1 firmware? thank u :good:
Click to expand...
Click to collapse
First of all try the NOBL.tar.md5 alternative from above. Are you trying to extract from the zip? you don't need Winrar for that.

AnggaKun said:
not at odin but when im try to extract it(firmware.zip) with using winrar.. it show text archive is corrupt :crying: can u help me pls
im got bootloop on of1 firmware when im instaling kernel A3 in stang5litre, im wanna flash it but when im download firmware at sammobile it always corrupt
#ask can if im flash using oc1 firmware? thank u :good:
Click to expand...
Click to collapse
Since I'm in a good mood:
Firmware
I can't leave it there forever, though. Just please stop posting questions all over the forum. You made a mistake. A really big one. A little humility goes a long way.

bg260 said:
Hey. In what way do you mean corrupt? Is Odin giving you an error?
Click to expand...
Click to collapse
bg260 said:
First of all try the NOBL.tar.md5 alternative from above. Are you trying to extract from the zip? you don't need Winrar for that.
Click to expand...
Click to collapse
can u give me the link ? :crying: im sorry if im bother u sir xD
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
bg260 said:
Since I'm in a good mood:
Firmware
I can't leave it there forever, though. Just please stop posting questions all over the forum. You made a mistake. A really big one. A little humility goes a long way.
Click to expand...
Click to collapse
okay im wanna to delete it sir :fingers-crossed::good: im sorry if im bother u
and thanks for all

this file is for ekstract? im try to extract it it say !
D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: Unknown method in I545VRUGOF1_I545VZWGOF1_I545VRUGOF1_HOME.tar.md5
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: No files to extract
help xD
---------- Post added at 07:04 AM ---------- Previous post was at 06:34 AM ----------
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
stuck in there

Hey AnggaKun,
I'm not sure if this is your issue but I had a firmware extraction / zip issue..and could not figure it out. I tried on multiple machines until I narrowed down the problem. I had *BAD MEMORY* chip! I had to replace the memory and *VOILA* problem went away... Not sure if that is your issue.
-TimJ
AnggaKun;67808617]this file is for ekstract? im try to extract it it say !
......
help xD
Click to expand...
Click to collapse

AnggaKun said:
this file is for ekstract? im try to extract it it say !
D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: Unknown method in I545VRUGOF1_I545VZWGOF1_I545VRUGOF1_HOME.tar.md5
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: No files to extract
help xD
---------- Post added at 07:04 AM ---------- Previous post was at 06:34 AM ----------
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
stuck in there
Click to expand...
Click to collapse
Try a different version of Odin. It definitely sounds like a computer problem. See next post.

View attachment Odin_v1.85.zip
View attachment Odin_v3.09.zip
View attachment Odin3_v3.10.5.zip
View attachment Odin3_v3.10.6.zip
View attachment Odin3_v3.12.3.zip

Good..

Anyone have link to download s4 verizon repair assistan? Im search for the link but i dont find the link.. someone say can fix the anggakun problem with using Samsung S4 verizon repair asistan.. :good:

@Rahmatkhairullah
Found this in a thread here somewhere. I have never been able to make it work. Have at it.
View attachment Verizon_Upgrade_Assistant.zip
I think I searched for Upgrade Assistant instead of Software Repair Assistant.

Anything else?

bg260 said:
Anything else?
Click to expand...
Click to collapse
The software upgrade assistant might be too outdated, I can't get it to run on my pc
can u reupload sir ? im sorry sir help me pls

View attachment 3817908
I think I searched for Upgrade Assistant instead of Software Repair Assistant.
AnggaKun said:
The software upgrade assistant might be too outdated, I can't get it to run on my pc
can u reupload sir ? im sorry sir help me pls
Click to expand...
Click to collapse
^^^^^^

Related

[rom] uk-JRO03H.I8190 XXALJL_btu-rooted [ONLINE]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This rom is primarily for UK unlocked devices (BTU) but it will work in any other country code.
ROM version-JRO03H.***** XXALJL
Baseband- XXALJL
Csc-BTU I8190OXXALJ8
This is a full Uk firmware rooted.
Download the rom an odin from the provided link and unzip it .
Put your phone into “Download mode” by Shutting down your device ,the press and hold Home button+Volume-down+Power Button, once you get to the screen with a yellow triangle press “volume Up”.
Connect your device to the pc…
Open odin and select “ Pda” and browse to the location of the “rooted.tar” now press start in odin.
Flashing will take about 10 minutes.
Rom will not void your warranty nor will wipe your data, will not increase your download binary count er either.
Firmware has been tested in 2 devices, but I will not be responsible for any damage cause by it or from it. As always flash it at your own risk.
Rom Languanges*
en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;
el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;
pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU; sk_SK; sl_SI; uk_UA;
uz_UZ;az_AZ;hy_AM; ka_GE;es_US; pt_BR;
Keyboard support
en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;
sr;sk;sl;sv;tr;uk;ko;hy;bg
What are the advantages of flashing a rom designed for your country code/service provider?
Well for one you’re rom VERSION and CSC CODE will match therefore when there are official updates from Kies you should be able to just update.
Flashing a rom that was not made for your specific country code will work ,but you may find that your battery will drain faster, wireless performance is degraded etc ,this is because every rom made for a country id/provider also has a matching modem/baseband included, mess with that and you may find that your device will not perform as intended.
Some people may say: “I will flash any rom then just flash my country id/provider modem and that’s the problem fixed”
NO. Specific radios work specific matched (SYS)roms ( rill files) etc.
The rule is, your Baseband version should match the Build number, like so:
Baseband version-*****XXALJL
Build number- ******.*****XXALJL
Thanks to Avicohh, for all his advice and KEN for providing the devices!
Disclaimer:
If you don’t know what I’m talking about above I suggest you leave your device alone and do some research before attempting to flash it.
Firmware has been tested in 2 devices, but I will not be responsible for any damage cause by it or from it. As always flash it at your own risk.
DOWNLOAD HERE......

Thanks for your work.
I was wondering what are the optimizations this ROM brings to the official one except rooting?

Well im not from UK, im from Macedonia but my baseband and build number are xxajlj, so i can flash without problems?
Пратено со Tapatalk 2 од мојот SGSIII mini

vonuzu said:
Well im not from UK, im from Macedonia but my baseband and build number are xxajlj, so i can flash without problems?
Пратено со Tapatalk 2 од мојот SGSIII mini
Click to expand...
Click to collapse
Yes as you have the same baseband. The rom will work with all basebands its just optimized to the uk .

goodmamba said:
Thanks for your work.
I was wondering what are the optimizations this ROM brings to the official one except rooting?
Click to expand...
Click to collapse
The rom is stock as it was a test on rebuilding roms, but im currently writing a tutorial in how to build a custom rom.

I just flashed my sgs3mini with no problems, it was about 9min and it didnt wipe anything. Thanks faria
Пратено со Tapatalk 2 од мојот SGSIII mini

Perfect. I have a rooted s3 mini 1 day after i bought it Thanks alot from Sweden!

Hi, worked for my german Mini also. Just installed rSAP successful, the thing that was really missing! I will test function later today.

I get this:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Cannot flash.
Any ideas?

imbehind said:
I get this:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Cannot flash.
Any ideas?
Click to expand...
Click to collapse
Does ODIN recognize your phone? It should show something like 0:[COMxx] at the top left box (green colored).
If not you need to install drivers (KIES from samsung)

imbehind said:
I get this:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Cannot flash.
Any ideas?
Click to expand...
Click to collapse
Are drivers installed :thumbup:

Guide on flashing this rooted ROM with Heimdall: http://forum.xda-developers.com/showthread.php?p=35903752#post35903752

quendil said:
Does ODIN recognize your phone? It should show something like 0:[COMxx] at the top left box (green colored).
If not you need to install drivers (KIES from samsung)
Click to expand...
Click to collapse
Yes, ODIN recognizes the phone (COM8) in second row first box from the left.
Kies/Drivers are installed.

Try another USB port with another cable if u have one, and exit kies because Odin & kies don't get along if running together. Try that see if that helps.
Sent from my GT-I8190 using xda premium

Worked perfectly with Romanian SGS3 Mini with the same baseband as in picture and the same info :good: Thank you :laugh:

Thanks for the ROM, it is the same as mine in Czech Republic
PDA - I8190XXALJL
PHONE- I8190XXALJL
CSC- I8190OXXALJ8
Well I hope it is the one, because you named the file that way (you have no CSC in the original post).
I also downloaded the original (unrooted rom) from the sammobile site.
The strange thig is that after flashigng with Odin both of these ROMs report
CSC: Unknown
Everything works, so I am not complaining but I am just curios as to why.
Thanks again for the rooted rom!

Thank you! I'm gonna try this right after I get the courage to flash my 3 day old phone

I'm using your V2 rom, had no problems so far only that software update won't allow it says that phone has been modified, will this ROM cure this problem?
Sorry for the noob question
Sent from my GT-I8190 using Xparent Blue Tapatalk 2

Build custom rom
faria said:
The rom is stock as it was a test on rebuilding roms, but im currently writing a tutorial in how to build a custom rom.
Click to expand...
Click to collapse
I would love to get your tutorial.. I want to start building custom roms too.

[Q] Samsung S3 i9300 Stuck In Bootloop

Hi guys
First some details about the S3:
Model: GT-i9300 (International)
ROM: Custom (Omega v34)
Kernel: SiyaKernel v1.6
FW ver: 4.1.2
The boot loop happened freakishly :silly:. I'm saying it because, yesterday the S3 was working fine. I went to sleep and upon waking up found the S3 in a boot loop with the "Samsung i9300" and the black screen background.
I've been using the custom rom since 1 month without any issue. All I did yesterday (out of the ordinary), was to install a few updates of a few apps like AllShare/Facebook etc.
I'm able to boot into Recovery as well as Download mode. The Download mode shows:
Product Name: GT-I9300
Custom Binary Download: Yes (2 Counts) - I'm guessing this is the binary counter
Current Binary: Custom
System Binary: Custom
Had created a Nandroid backup, so tried restoring from it. Tried advanced restoring with boot first, but the phone restarted midway and then had the boot loop again. After that I tried a normal restore, same thing happened.
I've gone through a few similar posts here, but couldn't find an exact match for mine. Hence, I created this thread. For one, the details in the Download mode are different from others (in some the product or the other was missing, but all are showing in mine). So, I'm guessing my boot partition is still intact (I'm a noob, so, I might be wrong).
What are my options here:
Can I flash a newer ver of custom rom on it?
Will wiping data/factory reset help?
How about Cache Partition/Devlik cache?
Or should I flash a stock rom?
Also, if any other option available and in what order?
Any help will be really appreciated with a big THNX :good::angel:

Just go to download mode, flash a stock rom.. root it again and flash a custom rom (if you like)
Factory resetting wont help, nor wiping caches and dalvik cache
Sent from this girl who's an Android Nerd

saywhatt said:
Just go to download mode, flash a stock rom.. root it again and flash a custom rom (if you like)
Factory resetting wont help, nor wiping caches and dalvik cache
Sent from this girl who's an Android Nerd
Click to expand...
Click to collapse
Thnx for the info :good: . Will give it a try and revert back with the result
Fingers :fingers-crossed:

yup. flashing stock rom with odin and start all over again is ur best chance

I tried installing Stock Rom from the Download mode using ODIN.
Followed this thread http://tutorialfor-android.blogspot.in/2012/08/how-to-flash-firmware-to-galaxy-s3-via.html
Did everything, but ODIN returns as FAIL. What am I doing wrong? Am using ODIN v3.07..
Downloaded the stock rom from SamMobile..
The snapshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HELP!!!!!!

Use XDA instructions .
http://forum.xda-developers.com/showthread.php?t=1671969
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
jje

JJEgan said:
Use XDA instructions .
http://forum.xda-developers.com/showthread.php?t=1671969
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Click to expand...
Click to collapse
Thnx a lot buddy:good:. Will check and let you know how it went. Maybe post in that same thread for more help

Hey buddy "JJEgan". Tried what you had mentioned. Went to the respective threads and did exactly what was advised in them. But the end result was the same.
This time around I used an older ver of ODIN 3.04. This time the update process moved ahead a bit more. But after a while I got an error msg:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLK1_I9300ODDDLI7_I9300DDDLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not sure what to make out about the issue. At wits end. Could you help me find a solution?

Sudden death, your NAND is dead, replace the motherboard under warranty

anirmj said:
Hey buddy "JJEgan". Tried what you had mentioned. Went to the respective threads and did exactly what was advised in them. But the end result was the same.
This time around I used an older ver of ODIN 3.04. This time the update process moved ahead a bit more. But after a while I got an error msg:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLK1_I9300ODDDLI7_I9300DDDLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not sure what to make out about the issue. At wits end. Could you help me find a solution?
Click to expand...
Click to collapse
Try this ,
1. go to http://checkrom.com download the latest resurrection rom , make sure you have usb drivers installed
2.go into download mode in your phone and flash this rom through odin 3.04 ( administrator mode)
3.once everything is done it should boot into cwm recovery after that wipe data/factory rest and wipe cache partition and then reboot system
4. if everything goes well it should boot into the resurrection rom
Good Luck!

why would resurrection work if the stock rom didn't?

Glebun said:
why would resurrection work if the stock rom didn't?
Click to expand...
Click to collapse
when i had a bootloop .. the stock rom didnt work but when i flashed the resurrection rom it did .. so maybe it may work for him too .

Just wanted to ask. Are there any other options that I might have before taking the mobile to the customer care?
I have read somewhere that a PIT file could resolve issues. Can that work in this scenario? If so, which file to use and what are the perils of using such a file?
Also, buddy "galaxy3lover", when you talk about resurrection rom, can you guide me to the exact FW that you are talking about? The link that you have provided contains a lot of links. Which one should I download from?

http://checkrom.com/download/ scroll down gt - 19300 if you are using the international model ... and then checkrom v6.zip

galaxys3lover: Tried ur resurrection rom, but its a no go.
Other than that also tried the PIT file/re-partitioning method but that too failed.
Searched a lot but couldn't find any other methods for my soft brick. So, is it really game over, even though mine is not a hard brick? Isn't there any other way to fix the issue?

Well if the nand and bootloaders are fine, Odin should be able to just flash it.
Try Kies firmware initialization

xSpeced said:
Well if the nand and bootloaders are fine, Odin should be able to just flash it.
Try Kies firmware initialization
Click to expand...
Click to collapse
Yeah, no harm in trying that as well. Its interesting to note that where ODIN failed can KIES come to the rescue?
Stay tuned for the answer

No even KIES turned out to be a dead end. It begun and stopped with an error. Tried emergency recovery but failed again.
Guess the only option left for me now is take it to the Service Center...

anirmj said:
No even KIES turned out to be a dead end. It begun and stopped with an error. Tried emergency recovery but failed again.
Guess the only option left for me now is take it to the Service Center...
Click to expand...
Click to collapse
You have void warranty so be prepared .
jje

JJEgan said:
You have void warranty so be prepared .
jje
Click to expand...
Click to collapse
Yeah, I always knew about that final outcome

Odin FAIL: Xmit Write fail and XmitData Fail

Hi everyone. I have a big problem on my hands. I tried to install Jelly Bean 4.1.2 stock firmware (on Samsung S II) from SamFirmware via Odin. During the install process a "FAIL!" message appeared.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
)
Here is the message list below:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSS_I9100OJCLS4_I9100XXMS2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013> factoryfs.img
<ID:0/013> __Xmit Write fail
<ID:0/013> XmitData Fail..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I followed the installation instructions carefully:
Boot phone into download mode.
Load Odin.
Connect phone to computer via USB.
Click PDA and browse for file (mine is I9100XWLSS_I9100OJCLS4_I9100XXMS2_HOME.tar.md5).
Make sure default settings unchanged and Re-Partition is disabled.
Then I clicked "Start"
I have used Odin before and have successfully rooted and installed firmware on my phone in the past.
I just dont understand why this is happening.
At the moment I havent touched anything (my phone is still connected to my computer and Odin has been left as it is and not closed). As I am quite scared to brick it. The download bar hasnt moved.
Please help. My friend asked me to install this firmware on his phone so I am in seriously need urgently. Thanks

Hopper8's "Odin troubleshooting' thread. Find it, try as much of the stuff in the thread as you need to in order to get a successful flash.

MistahBungle said:
Hopper8's "Odin troubleshooting' thread. Find it, try as much of the stuff in the thread as you need to in order to get a successful flash.
Click to expand...
Click to collapse
Thanks. I read the guide (http://forum.xda-developers.com/showthread.php?t=2345831) but what I saw there was about flashing failing when the connection to Odin isnt working.
With me my connection works (Ive updated firmware before via Odin) but the thing is it failed in middle of process
Are there any options I can choose in Odin to reboot safely? It is still in Fail state and phone still connected to computer (I havent touched anything)

It can fail in the middle of a flash for all kinds of reasons (bad download, temporary break in the connection between phone/PC but not long enough to register on the PC side).
You don't really have any other choice than pull the plug & hope you can switch the phone off & get into download mode again/hope that you haven't hard bricked it.
One way or another you need to get a successful Odin flash away in order to fix it. Despite your protestations to the contrary, the stuff in that thread does apply to the situation you find yourself in. If you can still get into download mode once you've unplugged it/pulled the battery, I very much recommend you try everything in that thread (including trying different PC's if necessary; how many previously successful flashes you've had is irrelevant if you can't fix this phone). Unless you'd rather take it to a Samsung service centre & pay them an exorbitant amount of money to fix it ?

MistahBungle said:
It can fail in the middle of a flash for all kinds of reasons (bad download, temporary break in the connection between phone/PC but not long enough to register on the PC side).
You don't really have any other choice than pull the plug & hope you can switch the phone off & get into download mode again/hope that you haven't hard bricked it.
One way or another you need to get a successful Odin flash away in order to fix it. Despite your protestations to the contrary, the stuff in that thread does apply to the situation you find yourself in. If you can still get into download mode once you've unplugged it/pulled the battery, I very much recommend you try everything in that thread (including trying different PC's if necessary; how many previously successful flashes you've had is irrelevant if you can't fix this phone). Unless you'd rather take it to a Samsung service centre & pay them an exorbitant amount of money to fix it ?
Click to expand...
Click to collapse
I managed to get it working. I disconnected the phone and it fortunately was able to go into download mode and I installed a different stock firmware. Thanks for help

protein.synthesis said:
I managed to get it working. I disconnected the phone and it fortunately was able to go into download mode and I installed a different stock firmware. Thanks for help
Click to expand...
Click to collapse
I can get into download mode, Odin will just NOT complete the install of the galaxy S3 firmware it stays stuck at "system ext4" for hours...any thoughts - see attachment...ty

And you're posting in an I9100 thread why exactly ?

it was my usb cable
try a genuine Samsung usb cable (the white one). I tried the one that came with my galaxy tab 3 swapped out my cheapo usb cable and got past this error and got the orginal firmware back on my sgh-t999 S3

Pretty sure nobody here cares given you have a different device (this is obvious advice anyway - of course you try different USB cables, in particular genuine Samsung ones).

idiot
MistahBungle said:
Pretty sure nobody here cares given you have a different device (this is obvious advice anyway - of course you try different USB cables, in particular genuine Samsung ones).
Click to expand...
Click to collapse
why didnt you help out protein.synthesis with this info then? the error is the same fix across all the S3 variants.

Bigger idiot
I did help that individual, but that person lied about going through Hopper's thread in a methodical way, which will always recover a phone that's actually recoverable in this situation. And why did that person lie ? Because 95% of people who post here a ****ing lazy & want 'easy'. There is no ****ing easy in this situation.
Hopper's thread mentions the USB cable thing & 238 other troubleshooting steps dip****, which is why we refer anyone who has this issue with an I9100 to it. We're sick & tired of posting this **** over & over for people who are too ****ing lazy to search.
You should be posting in forums for your specific device, not wherever the **** you feel like it.
And you need to get your ****ing facts straight/get some reading/comprehension skills before you gob off in future you ****ing moron.
Also, FYI, the fixes are pretty much the same across all Galaxy series phones, but that is absolutely beside the point.

Basically same for me.
I've been trying to root my Samsung Galaxy S2 GT-i9100 XWLSW and every time I try to install a custom Kernel ODIN says:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> __XmitData_Read ..
<ID:0/005> XmitData Fail..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I need help

^^^
You need:-
1) To say please. We're not your servants :-/
2) To read my first post on the first page (after the OP). It refers to the 'tools' you need to fix this.

*Update*
Reviving this thread since it is still prevalent on google. Do you have Kies installed at the time of Attempting to flash with Odin? This is a common problem when trying to flash with Odin. Hope this helps for all those tearing their hair out over this!

once i got rid of my custom recovery things seemed to get better. I flashed cf auto root with odin 3.07 then flashed stock FW and i was back in business. Hopefully this will work for others.

jeepersmr said:
try a genuine Samsung usb cable (the white one). I tried the one that came with my galaxy tab 3 swapped out my cheapo usb cable and got past this error and got the orginal firmware back on my sgh-t999 S3
Click to expand...
Click to collapse
thanks a lot dude it fixed the error

AndroidInitiate said:
Reviving this thread since it is still prevalent on google. Do you have Kies installed at the time of Attempting to flash with Odin? This is a common problem when trying to flash with Odin. Hope this helps for all those tearing their hair out over this!
Click to expand...
Click to collapse
I had Kies installed and got this error:
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
when trying to flash my Note 5 with ODIN. I was using a Samsung USB cable but it was from an S5. I switched to the Note 5 USB cable and uninstalled Kies and I was able to overcome the error.
Thanks!

hay que cambiar el cable y listo

Charging your device can also help in case it resets because of it

(SOLVED) PIT/Bricked/Dead problem on GT-I9300 international

Hi XDA.
There are several thread about PIT/Partition/ brick/ mounting problem etc.
i spent over 2 days to fix my international GT-I9300 16GB white.
i think there is not much left about PIT on not only XDA but on other websites. Which I didn't read.
some of them are scary like. don't check partition box in odin or motherboard will be dead or that's it your phone is junk/ send it to service center. blah blah blah........
but all you need to do is downgrade you boot loader..........yes.***********THAT'S IT*********
tried millions of method (yes almost million) but nothing work. and i don't want to anyone else spend that much time on it
(back on topic)
here is how i did it.
download all files at last of this post
1. Put your phone on download mod (volume down+home button+power and than volume up)
2.open odin and select option *auto reboot*re-partition*f.reset time *Nand erase all(don.t worry just do it*unless you have other option*)
3.select **GT-I9300.PIT** as pit file(DO NOT SELECT ANY OTHER ONE)
4. click start(after finishing task phone will reboot )
5.now download CF-Root for SGS3 v6.4 from here-------> http://forum.xda-developers.com/showthread.php?t=1695238
6. again put phone in download mode and root your phone with CF-Root (file you downloaded)
7.now put ***Restore_Bootloader_XXBLFB** ZIP file on your sd card and flash it using phone recovery (cwm)
8.now download any 3 part official firmware for your phone and flash with odin ..
that's it
method above worked for me on my SAMSUNG GALAXY S3 GT-I9300 WHITE 16 GB but i still take no responsibility
for any damage to your phone or to your Dog/cat during process.
Thank you
Hope it'll work for you
sorry for my bad english.

In your post you link to the Old rooting method from Chainfire he hasn't supported that thread for around a year now, he moved to a new version of rooting, link is in my signature that is the better rooting method to use unless with your process it requires that you use the old rooting method.

Yes my process required this old root TAR file as it comes with cwm recovery. The new one does not. And as I mentioned up you need recovery to flash bootloader. So in this way you saving time to flash recovery after rooting.
Anyway after recovering your phone you can use new root file from chainfire to re root 3 part firmware which you flashed in recovering process.
Enjoy android

ManojKBanga said:
Yes my process required this old root TAR file as it comes with cwm recovery. The new one does not. And as I mentioned up you need recovery to flash bootloader. So in this way you saving time to flash recovery after rooting.
Anyway after recovering your phone you can use new root file from chainfire to re root 3 part firmware which you flashed in recovering process.
Enjoy android
Click to expand...
Click to collapse
Partition Info flashing[PIT] works but bootloader is a problem! ANy other option to may the system works as earlier???
This zipped can not be flashed from Stock Recovery. It says its signature can not be verified! I do not know what to do now. Can not get my bluetooth bhai!

You need CWM recovery to flash this file. Read carefully bhaisaab
and iam not sure what you mean bluetooth not working. Explain more.

ManojKBanga said:
You need CWM recovery to flash this file. Read carefully bhaisaab
and iam not sure what you mean bluetooth not working. Explain more.
Click to expand...
Click to collapse
Sorry for not seeing CWM. I am using stock recovery! Bluetooth icon has gone into gray color, I can not make it green[try to turn ON, it will go to OFF position]. Above all, my csc folder is missing. May be it's the culprit!
found csc folder by making my IMEI into that 049... by flashing ITV rom explains in other thread. I didn't worry much I know I will get back IMEI as I didn't break my efs. flash back thereafter 4.3 swc then to indian xxemh4 4.1.2. my network, wifi, gprs work fine, I got my CSC folder back.
but I still have my Bluetooth non functional and mobile is as laggy as that of 4.3.
another problem is both UART & USB change automatically to modem everytime phone booted!

Hi! I'd like to try your method, but this is what happens in the first step:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can not flash anything. My phone, as I've read is not bricked, just semibricked.
Thanks in advance!

THX
thx a lot, i solved the problem on my s3

SOLVED

SignalX said:
my phone is International GT-i9300 16gig White too
i have access to download mod only, there's no recovery menu
after doing 1 - 4 steps according to the first post, when i want to do step 5 & 6 [flashing CF-Root] i'll get this error in Odin:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and this is what my phone show:
anyone knows what should i do now?
Click to expand...
Click to collapse
You say your phone is international GT-19300 but in your photo of download mode it say's product name SGH-T999

Plz delete........

Mementii said:
Hi! I'd like to try your method, but this is what happens in the first step:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can not flash anything. My phone, as I've read is not bricked, just semibricked.
Thanks in advance!
Click to expand...
Click to collapse
Same problem here, any help?
Thnx in advance

ManojKBanga said:
Hi XDA.
There are several thread about PIT/Partition/ brick/ mounting problem etc.
i spent over 2 days to fix my international GT-I9300 16GB white.
i think there is not much left about PIT on not only XDA but on other websites. Which I didn't read.
some of them are scary like. don't check partition box in odin or motherboard will be dead or that's it your phone is junk/ send it to service center. blah blah blah........
but all you need to do is downgrade you boot loader..........yes.***********THAT'S IT*********
tried millions of method (yes almost million) but nothing work. and i don't want to anyone else spend that much time on it
(back on topic)
here is how i did it.
download all files at last of this post
1. Put your phone on download mod (volume down+home button+power and than volume up)
2.open odin and select option *auto reboot*re-partition*f.reset time *Nand erase all(don.t worry just do it*unless you have other option*)
3.select **GT-I9300.PIT** as pit file(DO NOT SELECT ANY OTHER ONE)
4. click start(after finishing task phone will reboot )
5.now download CF-Root for SGS3 v6.4 from here-------> http://forum.xda-developers.com/showthread.php?t=1695238
6. again put phone in download mode and root your phone with CF-Root (file you downloaded)
7.now put ***Restore_Bootloader_XXBLFB** ZIP file on your sd card and flash it using phone recovery (cwm)
8.now download any 3 part official firmware for your phone and flash with odin ..
that's it
method above worked for me on my SAMSUNG GALAXY S3 GT-I9300 WHITE 16 GB but i still take no responsibility
for any damage to your phone or to your Dog/cat during process.
Thank you
Hope it'll work for you
sorry for my bad english.
Click to expand...
Click to collapse
I tried all that but it gets stuck at <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> Erase...

did anyone succeed ?
having same issue (write operation fails) any help

_Choy said:
Same problem here, any help?
Thnx in advance
Click to expand...
Click to collapse
I'm also having this trouble with my GT-i9300 16GB

Same trouble!!!
This happenned to me too..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any Solution????

help
Mementii said:
Hi! I'd like to try your method, but this is what happens in the first step:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can not flash anything. My phone, as I've read is not bricked, just semibricked.
Thanks in advance!
Click to expand...
Click to collapse
hi I get the same prablem how did u fix this prablem please

nassiry said:
hi I get the same prablem how did u fix this prablem please
Click to expand...
Click to collapse
this problem can only be fixed with box us z3x or riff box

Same unsolving problem here
I can't get rid of "Complete(Write) operation failed" too (samsung galaxy i9300).
Can't do nothing on Odin 3 , with PIT file or CF-root
Odin FAIL !
HELP ! SOS !
On CWM Clock Work Mod Recovery, the message trying to reset / wipe factory data is "E:Can't mount /cache/recovery/"

romuloff said:
I can't get rid of "Complete(Write) operation failed" too (samsung galaxy i9300).
Can't do nothing on Odin 3 , with PIT file or CF-root
Odin FAIL !
HELP ! SOS !
On CWM Clock Work Mod Recovery, the message trying to reset / wipe factory data is "E:Can't mount /cache/recovery/"
Click to expand...
Click to collapse
as i know, you have a problem with motherboard or emmc chip, need replacement.
i have one with the very same problem you have described

[Q] Bricked note 10.1 (GT-N8000) need help

first things first ... sorry for not intrduce my self
my name's mohaned and i am very nice to meet you guys
sec being reading and searching a lot of theards around XDA about fixing dead devices
the nearest solution i've found is this
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
but i don't have access to boxs
so i wanted to ask you about my problem
lets come to facts
my device can power on and i have access to both download mode (odin mode)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and recovey mode (in my case custom recovey mode [TWRP] )
iam were on official 4.4.2 rom then updated the gnabo rom v5
it's a custom rom based on the official kitkat 4.4.2 with amazing featurs
the device was working fine for 2 months
then when i trie to start the device normally it stuck on samsung logo and keep restarting
so first thing come to my mind is to wipe the device and restore factory setting
and this is what i get
so i try reflash the rom
but nothing happend
and this what i got when i tried to flash the official 4.4.2 using odin
<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> SingleDownload.
<ID:0/018> sboot.bin
<ID:0/018> NAND Write Start!!
<ID:0/018> FAIL!
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
a friend of mine told me this could be curreption in the internel memory and a reformat may fix it
any ideas
could you please help me

any help here ?

no one even care about my problem ?

meedo64 said:
no one even care about my problem ?
Click to expand...
Click to collapse
Have you flashed a Custom Rom?
Always make a back-up before updating, flashing zips, or writing in system folders. just a tip
---------- Post added at 04:10 PM ---------- Previous post was at 04:03 PM ----------
meedo64 said:
no one even care about my problem ?
Click to expand...
Click to collapse
Re download the Rom and sideload via adb. It won't mount due to there isn't anything to mount or format. Had this issue with my infuse 4g
Always make a back-up before updating, flashing zips, or writing in system folders. just a tip

Can you guide me to how sideload viaadb ... although my device doesn't have fastboot ... it's only have download mode
Which uses odin which I used and it didn't work

meedo64 said:
Can you guide me to how sideload viaadb ... although my device doesn't have fastboot ... it's only have download mode
Which uses odin which I used and it didn't work
Click to expand...
Click to collapse
Can you enter recovery mode?
Always make a back-up before updating, flashing zips, or writing in system folders. just a tip

Yes

meedo64 said:
Yes
Click to expand...
Click to collapse
Download this and there are instructions inside -> https://www.dropbox.com/s/8xbkusu5i1yv9bz/UNZIP IN YOUR DOWNLOAD FOLDER.zip?dl=0
THE NOOBS TIP:
Always make a back-up before updating, flashing zips, or writing in system folders.
---------- Post added at 06:27 AM ---------- Previous post was at 06:26 AM ----------
meedo64 said:
Yes
Click to expand...
Click to collapse
Please quote me for my device can notify me
Always make a back-up before updating, flashing zips, or writing in system folders. just a tip

Tony the noob :D said:
Download this and there are instructions inside -> https://www.dropbox.com/s/8xbkusu5i1yv9bz/UNZIP IN YOUR DOWNLOAD FOLDER.zip?dl=0
THE NOOBS TIP:
Always make a back-up before updating, flashing zips, or writing in system folders.
---------- Post added at 06:27 AM ---------- Previous post was at 06:26 AM ----------
Please quote me for my device can notify me
Always make a back-up before updating, flashing zips, or writing in system folders. just a tip
Click to expand...
Click to collapse
i tried your method but this is what i get

meedo64 said:
i tried your method but this is what i get
Click to expand...
Click to collapse
Flash this recovery and re-elected sideload. TWRP and CWM have given me trouble like that
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later
---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------
meedo64 said:
i tried your method but this is what i get
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2202714
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later

Tony the noob :D said:
Flash this recovery and re-elected sideload. TWRP and CWM have given me trouble like that
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later
---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2202714
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later
Click to expand...
Click to collapse
can you reupload the file for me
all links became offline
Hello,
Unfortunately, as of this time, the main portions of goo.im have been disabled. Due to a finance issue, our CDN account has been suspended, and all files stored on it are effectively non-accessible. Due to some RL issues on my(Alexander)'s part, once goo started actively losing money 6 months ago, I had changed jobs a bit to help support goo. Unfortunately, this wasn't enough combined with some other issues that crept up on me. Due to this, I'm formally shutting down Goo. There is an offer in to take over the files and hosting from a generous sponsor, however, until the financial issues are sorted out, they are unable to adsorb Goo. It's been my pleasure to serve files for you all for the past couple of years, and I wish everyone good luck into the future.
-- Snipa/Alexander Blair
If you have picked up a sponor account within the last two months, please reach out to us if you'd like a refund. It may take some time, but we'll do our best to get these processed and sent out. -- Thanks for everyone who's supported us over the years.
Click to expand...
Click to collapse

Tony the noob :D said:
Flash this recovery and re-elected sideload. TWRP and CWM have given me trouble like that
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later
---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2202714
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later
Click to expand...
Click to collapse
i can't flash a new recovery
with odin
<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-n8000.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> SingleDownload.
<ID:0/018> recovery.img
<ID:0/018> NAND Write Start!!
<ID:0/018> FAIL!
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/018> Removed!!
<ID:0/017> Added!!
<ID:0/017> Removed!!
Click to expand...
Click to collapse
install from external sd card
even tried to sideload it
with no luck

meedo64 said:
i can't flash a new recovery
with odin
install from external sd card
even tried to sideload it
with no luck
Click to expand...
Click to collapse
Well all I can say is restore a back up from TWRP. Let my find some one who can send me on for your device
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later

Tony the noob :D said:
Well all I can say is restore a back up from TWRP. Let my find some one who can send me on for your device
:-: A TIP FROM THE NOOB :-:
All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later
Click to expand...
Click to collapse
ok .. thanks
waiting for you

meedo64 said:
ok .. thanks
waiting for you
Click to expand...
Click to collapse
If you haven't fixed the issue yet, try a different version of Odin bud
:-: A TIP FROM THE NOOB :-: All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later

Tony the noob :D said:
If you haven't fixed the issue yet, try a different version of Odin bud
:-: A TIP FROM THE NOOB :-: All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. be on the safe side. do it now or regret it later
Click to expand...
Click to collapse
need help here

meedo64 said:
need help here
Click to expand...
Click to collapse
I'm here. Talk to me
:-: A TIP FROM THE NOOB :-: All ways backup your current rom before adding root apps, modifying system/system files, flashing zip files, or installing new rom. just to be on the safe side. do it now or regret it later

Better Mobile App

welcome