Flashed stock firmware from samsung updates dot com (Version ... I8160JPLK2) and 1st boot stuck at " Samsung Galaxy Ace2 GT-I8160 " screen, cant access recovery, cant access phone...can access odin mode only (download mode).....plz need help urgently its my dads phone
Flashing output
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8160JPLK2_I8160OJPLH1_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> kernel.bin.md5
<ID:0/004> NAND Write Start!!
<ID:0/004> modem.bin.md5
<ID:0/004> system.img.md5
<ID:0/004> power_management.bin.md5
<ID:0/004> cache.img.md5
<ID:0/004> hidden.img.md5
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
@All_New_BoB
Just flash 3 file firmware 2.3.6 from sammobile (russian 3 file) codename SER/ or/ SEB i dnt remember
If you want instructions type in google
( downgrade sgs ace 2 )
Cheers
Ave_Hornet said:
@All_New_BoB
Just flash 3 file firmware 2.3.6 from sammobile (russian 3 file) codename SER/ or/ SEB i dnt remember
If you want instructions type in google
( downgrade sgs ace 2 )
Cheers
Click to expand...
Click to collapse
bro, thanks!!...now what should i do to re upgrade to 4.4.4, i flashed carbon over gingerbread but didn't get signal, i don't remember doing anything special to flash carbonROM last time (like flashing stock jelly bean before flashing custom kk roms) @Ave_Hornet
All_New_BoB said:
bro, thanks!!...now what should i do to re upgrade to 4.4.4, i flashed carbon over gingerbread but didn't get signal, i don't remember doing anything special to flash carbonROM last time (like flashing stock jelly bean before flashing custom kk roms) @Ave_Hornet
Click to expand...
Click to collapse
If you are on Gingerbread, you must flash the 3 parted Jelly Bean with odin or use Samsung kies.
I have tried to just flash a JB ROM but it didn't boot... I think the 3 parted JB ROM is needed.
Can someone confirm ?
Sent from my GT-I8160 using XDA Free mobile app
Sorry for my bad English, it isn't my native language.
@Mavireck @All_New_BoB
Guys both of you if u want any custom rom u MUST have a JB (jellybean) update
now you must flash 3 firmware GB (russian) and later flash JB (your country) and later flash tempomary recovery and flash any custom rom.
@Ave_Hornet
It is nice to try to help me but I haven't got any problem I already know what has to be done in order to install a custom rom. Maybe my bad English confused you ?
I think it is needed to flash the 3 parted JB when you are on GB...
Sent from my GT-I8160 using XDA Free mobile app
Great phone for flashing
This mobile is a great phone for flashing ROM's because bootloader is unlocked, easy to flash custom recovery like clockworkmod. Pretty good i think . there is cyanogen mod instead of carbon mod amongst other kitkat ROM's.
Thanks Guys
Thank you guys for all the help, i flashed the JB stock English firmware and flashed Carbon latest update after that, I knew that this is 100% working method but i was confused because when my father first bought the phone it was stock GB (of course ) and i dont remember flashing any stock JB stock firmware before flashing Carbon and everything worked without problems. i was just trying to save some time downloading so much things but i end up doing just that (i dont have unlimited data, only 40 GB/month )...anyway, all that was because of a silly mistake by me, if anyone have a better solution please tell us, the problem is that i applied bootanimation from a CM11 theme that is made for phones with more than 2GB of RAM, the developper did mentioned that if our phone is less than that we should not apply bootanimation but i was busy and i a hurry and blabla...any solution other than factory reset?? (sry for my bad english, its not my native language )
You can reflash the ROM without wiping anything or flash another bootamimation.zip in recovery. If your phone doesn't boot, you can mount it on your PC in recovery (under "Mount and Storage") and copy the files. No need to do a factory reset
Hope this helps
Related
Hello,
Device : Samsung Galaxy Note 2 (GT-N7100)
I am a new Android user and I tried installing a Custom ROM (KitKat 4.4) on my device which worked well.
I used TWRP to boot from in order to install it. Later I tried another ROM which seems to have bricked the device.
Now when I start my device, it doesn't progress pass the Boot Logo.
Is there a way to restore the device ? Any method using Odin ?
I don't have to worry about losing data because there's nothing to back up.
I would appreciate it if someone could point me a method to install a reliable (Stock) Jelly Bean 4.3 firmware.
I do not use it for making calls - only as a WiFi device. Would it be possible to use the recently released original 4.3 firmware
available for India, Hong Kong, China ?
You can get your stock rom from sammobile and flash with odin. You can also try booting to recovery factory resetting/flashing a different custom rom. I've had my share off boot loops
Sent from my GT-N7105 using XDA Premium 4 mobile app
Not Successful with Odin
Hello,
I tried flashing a Stock firmware from SamMobile and I get errors on Odin.
<OSM> Please wait..
<OSM> N7100ZCUEMK3_N7100CHNEMK3_N7100ZCUEMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
What could I have done wrong ?
andy_central said:
Hello,
Device : Samsung Galaxy Note 2 (GT-N7100)
I am a new Android user and I tried installing a Custom ROM (KitKat 4.4) on my device which worked well.
I used TWRP to boot from in order to install it. Later I tried another ROM which seems to have bricked the device.
Now when I start my device, it doesn't progress pass the Boot Logo.
Is there a way to restore the device ? Any method using Odin ?
I don't have to worry about losing data because there's nothing to back up.
I would appreciate it if someone could point me a method to install a reliable (Stock) Jelly Bean 4.3 firmware.
I do not use it for making calls - only as a WiFi device. Would it be possible to use the recently released original 4.3 firmware
available for India, Hong Kong, China ?
Click to expand...
Click to collapse
Which rom?
Once I saw there is a FACTORY rom for N7100. Give it a try.
Here it is http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
DOWNLOAD_N7100XXDLJ2_OXA_FACTORY
These firmware is made for emergency recovery device to factory condition
Firmware consists of four parts, plus pit
Attention! All user data will be deleted during flash the firmware, including internal sdcard
After flash you will have clean device (factory condition) CSC - XEF default
Can flash with PIT - Included in the firmware (The optional - required if damaged partition PIT)
Click to expand...
Click to collapse
Thanks a lot for the above information.
I'll try it out and update results.
[email protected] said:
Which rom?
Once I saw there is a FACTORY rom for N7100. Give it a try.
Here it is http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
Click to expand...
Click to collapse
Thanks ! I've got it working now.
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
Click to expand...
Click to collapse
I believe that if it is official 4.3 you cannot downgrade.
Is it a clone?
Sent from my GT-N7105 using xda app-developers app
thedadio said:
Is it a clone?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?
New Droid said:
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?
Click to expand...
Click to collapse
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck
tonylee000 said:
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck
Click to expand...
Click to collapse
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic
New Droid said:
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic
Click to expand...
Click to collapse
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.
....
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
tonylee000 said:
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.
Click to expand...
Click to collapse
I've installed the latest version of CWM Recovery Touch v6.0.4.1 and try to flash the CyanogenMod 10.1.3 to see if it woks.
The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Right now I'm on my mobile. Can you send me the link to one post with that please. Thanks
Enviado do meu U9200 através de Tapatalk
The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Can the mk3 bootloader be downgraded? I wss under the impression that once upgraded to a mk bootloader you were stuck with it as theyre not downgradable
New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?
sora9009 said:
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?
Click to expand...
Click to collapse
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:
exceptionalkhan said:
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:
Click to expand...
Click to collapse
im pretty sure bootloader cannot be downgrade.
sora9009 said:
im pretty sure bootloader cannot be downgrade.
Click to expand...
Click to collapse
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.
exceptionalkhan said:
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.
Click to expand...
Click to collapse
this is really a great news.Thanks
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
Sorry man, for me didn't work :S It keeps giving the same error :S
Hi everyone. Finally i could flash the note 2 :victory: but i still dont get it why i cant flash through odin
This is how i do it.
1. Flash the ClockworkMod Recovery through.
2. Flash the TWRP 2.6 Recovery.zip through CWM Recovery. (Don't know i i cant flash this recovery directly on odin
3. Flash a CyanogenMod Nightly ROM
4. Install Odin Mobile.
5. Flash the lastest official rom by Samsung for Europe.
6.Yeh I have a official rom on my mobile :victory:
Now I have one problem, when i try to make a call i cant hear the people on the other side and vice versa. I know the mic and speaker are working, if o try to make a call through skype it works perfectly!
Obs.On every ROM i have this problem, on Stock ROMs by Samsung, Europe and Chinese Version and also on CyanogenMod.
When i try to flash the European ROM on Odin it fails when try to write the modem.bin.
I can flash the Chinese ROM without any problems on Odin.
I'm using the lastest ROM JB 4.3 from Samsung
What is the problem now?
The MSR firmware zip link no longer exists?
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
MadR4sta said:
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
Click to expand...
Click to collapse
Ma Bad...
Bro! the thread is closed, will update that later.
An updated link is Here:https://my.pcloud.com/#page=publink&code=XZgADZWDMzsYh1Xa8uTeOaSPsb2VAn5tb7
I had encryption on my phone due to company emails. I flashed bootloader and modem to 4.3 (I747UCUEMJB) in order to enjoy the latest custom ROMs.
However, after installing 5-6 of custom ROMs, I am always asked to "enter your PIN or password to encrypt the memory". No matter what I enter, the phone always restarts and goes back to the prompt asking me to enter PIN or password.
I did factory reset and cache/etc. wipes every time I flash. I thought encryption should be erased by those resets/wipes. BTW - I use TWRP as recovery.
What I would like to know, is there a way for me to get a stock 4.3 ROM to install using ODIN? Hopefully that will also install the stock recovery, which may be able to help me really do a clean factory reset/data wipe.
Any thoughts? Thanks.
You can find pre rooted stock rom from herehttp://forum.xda-developers.com/showthread.php?t=1739426
hope that helps
BTW, I have tried using ODIN to get back to 4.1.2: I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar file.
However, ODIN is giving "Fail (Auth)" errors. I suppose this is because I have flashed the bootloader and modem to a much higher version and there is no way to go back?
Harsh99132 said:
You can find pre rooted stock rom from herehttp://forum.xda-developers.com/showthread.php?t=1739426
hope that helps
Click to expand...
Click to collapse
Nope. these I747ATTDLK3 images won't work because once you flash these new 4.3 bootloader (I747UCUEMJB), you cannot go back to early stock ROMs. The only way is to find the 4.3 stock ROMs for ODIN, which is no where to find on the internet.
Here is the error from ODIN when I tried the I747ATTDLK3 image:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have run KK ROMs with a stock 4.1.2 bootloader with no problems at all. Updating to 4.3 isn't necessary in my opinion.
AT&T never released a stock 4.3 ROM that can be flashed via Odin. AT&T released 4.3 as an OTA update.
At this point, you may be better off flashing a custom recovery such as Philz Touch and flash a KK ROM.
audit13 said:
I have run KK ROMs with a stock 4.1.2 bootloader with no problems at all. Updating to 4.3 isn't necessary in my opinion.
AT&T never released a stock 4.3 ROM that can be flashed via Odin. AT&T released 4.3 as an OTA update.
At this point, you may be better off flashing a custom recovery such as Philz Touch and flash a KK ROM.
Click to expand...
Click to collapse
Wow. CWM recovery (Philz Touch) + CyanogenMod 10 Nightly Builds for SGH-I747 solved my problem! I can finally use my phone now!
Thank you so much!
zhangla said:
Wow. CWM recovery (Philz Touch) + CyanogenMod 10 Nightly Builds for SGH-I747 solved my problem! I can finally use my phone now!
Thank you so much!
Click to expand...
Click to collapse
That's great. Why stop at CM10? Try some 4.4.2-based ROMs like Cyanfox or Valiudus. Both are great and I love the dark theme for Validus.
I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?
FuTuRisTiC Zo3 said:
I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?
Click to expand...
Click to collapse
Ok I Installed Insecure Boot img via odin3 and my phone rebooted but now instead of it booting at the 1 second samsung screen it goes past it to the galaxy s 3 screen and just sits there. i also installed twrp, it let me mount everything but i cant u adb to push anything and it says i have no os installed. i dont know what moves to make anymore someone please help me out!!!
What version of Android did you have on your phone when it last worked, stock or custom ROM?
dawgdoc said:
What version of Android did you have on your phone when it last worked, stock or custom ROM?
Click to expand...
Click to collapse
its was a stock android rom i believe im not sure what version though.
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
yes im able to go into download and recovery mode
lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
oops didnt fully read your 1st post
lemngo02 said:
oops didnt fully read your 1st post
Click to expand...
Click to collapse
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices
If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?
FuTuRisTiC Zo3 said:
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices
Click to expand...
Click to collapse
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
ok, not to jack his thread, but what if you are on the 4.3 bootloader? i didnt do what he did, but i am stuck in a similar situation. I am on the 4.3 bootloader, but i do have a custom recovery installed. problem is i get an error when i try to wipe. Ive tried flashing stock 4.3 rom via sideload in stock recovery, and modified rom though twrp. both roms install fine, but dont boot, but they do freeze in different points so i know something is being flashed. ive also tried wiping in cwm and stock. im bout ready to flash anything to this phone. oh and a nandroid restore fails after boot img flashes.
FuTuRisTiC Zo3 said:
its was a stock android rom i believe im not sure what version though.
Click to expand...
Click to collapse
From your message, you likely were on stock 4.3. Since you are able to get into recovery and download modes, you may try a restore via custom recovery. Please see the thread below on how to install custom recovery and do a stock restore ...
<http://forum.xda-developers.com/showthread.php?t=2658486>
fastludeh22 said:
ok, not to jack his thread, but what if you are on the 4.3 bootloader? I am on the 4.3 bootloader, but i do have a custom recovery installed.
Click to expand...
Click to collapse
I would then link you to the same thread Larry2999 provided.
dawgdoc said:
I would then link you to the same thread Larry2999 provided.
Click to expand...
Click to collapse
thanks. i had found that thread right after i posted. lets hope. its halfway downloaded. if that doesnt work,ill be posting a thread about the weird way i ended up here and detailed report of what i did and what ive tried...
dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
audit13 said:
If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?
Click to expand...
Click to collapse
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do
never mind folks i got it up and running my only option was to use the sd card so i found my adapter and fixed it. im on 4.1.2 now its updating software now im guessing to 4.3. thank you guys for all the help
FuTuRisTiC Zo3 said:
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do
Click to expand...
Click to collapse
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.
dawgdoc said:
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.
Click to expand...
Click to collapse
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else
FuTuRisTiC Zo3 said:
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else
Click to expand...
Click to collapse
There is a chance that being rooted will prevent you from using the OTA official update. I've seen reports of people being able to update to the official 4.3 while rooted, but I've also seen reports of people not being able to update.
Before you make that update, bear in mind that the official 4.3 bootloader, its name ends in MJB, is the one that will prevent you from ever going back to an older bootloader. Some of the devs and the more experienced on here have no problem with that. Others do consider it an issue. An alternative is to install the leaked 4.3 bootloader, it's name ends in MJ2. That bootloader will allow you to downgrade to the 4.1.1 or 4.1.2 bootloaders, or so I have read. There is information about this in the development and the general forums for our device.
To muddy the waters more; if you intend to sim unlock your device without gettings codes from your carrier you need to do it from the 4.1.1 official ROM. A point you can not return to from the official 4.3 ROM, or so I've read.
I am having a huge booting issue with my Samsung Galaxy S3. Its a brand new one and I tried rooting it but it gave me this error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can get to download mode, but not recovery nor does it boot into the Android OS. I tried putting back the stock OS and it gave me this error:
<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
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried follow a bunch of these threads, but I can't seem to resolve my issue yet. I probably have that 4.3 bootloader which screwed everything up. Can someone help me resolve my issue? I literally got this phone today from AT&T. Thank you.
Need to warranty my Note 3 due to hardware camera problem. I unlocked my factory 4.3 bootloader, installed TWRP, and went to W03 Slim 8.5. I have never ran the official 4.4.2 update which I believe implies my bootloader is still the 4.3 version.
I launched ODIN 3.07, and flashed the N900TUVUBMI7 rom from this page: AndroidRootz
Everything appears to have ran in ODIN successfully:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone boots up with no warnings on the Samsung splash and then gets to the white T-Mobile 4G LTE splash and just hangs there. I've tried reflashing the firmware from ODIN with the same result.
What should I do? Should I flash up to the 4.4.2 version? The phone is going back regardless so I don't care about anything other than getting this to boot up so I can exchange it.
Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.
negativefx said:
Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.
Click to expand...
Click to collapse
Try wiping /data or a factory reset in recovery.
Have you tried re-downloading the 4.3 firmware. Sometimes this can happen from a bad download.
Shawn said:
Try wiping /data or a factory reset in recovery.
Click to expand...
Click to collapse
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!
happened to almost everyone, I had to odin v3.09 and run 2 times... the 1st time it said it was successful, but stuck at the Samsung screen, the 2nd time booted up just fine..
on my link I have odin and the new firmware, old firmware my stock not rooted roms... all u need for my stock not rooted is chainfire superuser app, then download busybox, your done,
look on my signature for any files needed, also uploading the Samsung driver.. no kies needed.
negativefx said:
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!
Click to expand...
Click to collapse
No problem, I used to forget to wipe when I put my phones back to stock with Odin.
I'm currently running an AOSP rom 4.4.2...what are the steps to flash the 4.3 stock rom touchwiz??
4.4.2 is out? newest firmware available atm is nk3 4.4.2
anyway
1. d/l firmware file from sammobile.com
2. boot to download mode
3. run odin and plug phone into pc(if you have a mac your on your own from here as i have a pc and not a mac)
4. load file you just d/led(in tar.md5 format) into the pda slot(i'm assuming you have odin 3.07)
5. click start and wait to profit.
you can also d/l 4.3 firmware from same site if you really want it.
good luck
I meant I have a AOSP custom rom its regular google not touchwiz
Sent from my SM-N900T
right. thats how you restore stock touchwiz though. it's pretty simple.
will I lose root?..so if I have this current baseband which is MI7..does that mean that I still have 4.3 bootloader?
Sent from my SM-N900T
yeah you will lose root. but you can reroot it afterwards. and yes if you flash the 4.3 firmware it'll keep the 4.3 bootloader or should anyway. might want to wait on someone else to chime in here on the bootloader and baseband though as i am not really sure. i just upgraded from a note 2 to my note 3. and i run nk3 on my note 3. it's fine with all the roms i have tryed so far though. no issues at all.
I'll wait a lil bit cause someone just told me that since I'm on 4.4.2 custom aosp rom I won't be able to revert back to 4.3 Touch wiz
Sent from my SM-N900T
i'd just go with the nk3 firmware. it's 4.4.2 stock touchwiz. works great. but thats me. hehe
this is my android version and that is my baseband..im soo confused
View attachment 3079890
Sent from my SM-N900T
ok. your baseband and bootloader are 4.3, but your custom rom is a 4.4.2 rom. if you install the nk3 firmware. you'll have stock touchwiz 4.4.2 with the nk3 baseband and bootloader along with the csc file. and a bunch of otherstuff. it will all be upgraded. instead of having a custom 4.4.2 rom you'll be on the newest stock touchwiz version which is nk3.
nk3 can be rooted. you can install a custom recovery and still reinstall custom roms.
if that makes sense.
that's wat I was looking for, thanks dude..this is my version of ODIN that I have..this is what I used to root the phone when I first got it last year
View attachment 3079899
Sent from my SM-N900T
1.8.5 will work. been so long since i seen that version. just add the tar.md5 file to the pda slot. click start and profit
is it better to upgrade ODIN to tge latest version or just stick with 1.85?
Sent from my SM-N900T