Database Info

Galaxy Tab 7.7 P6800 Need stock Recovery

I was trying to reset the whole device because I've uninstalled some stock apps by accident using Titanium backup. So I tried to recover my device through the recovery mode and start fresh. The stock apps was still gone...
So I figure I can use Odin3 v1.87 to flash the whole device with the firmware from http://www.sammobile.com/firmware/
I thought that would most likely get me back to the factory settings with everything and start fresh. But then Odin needs PDA, PHONE, CSC to run and the firmware only gave me one P6800OZSLP7_P6800ZSLP7_HOME.tar.md5 I was like how can I use this...
Then I found a guide in XDA how to separate it out into the three sections.
http://forum.xda-developers.com/showpost.php?p=24278264&postcount=9
I was like finally i can start this fresh. Things got worse.... every time it flashes to modem.bin it got stuck. It can never go through that part of the flashing. I then want to give up and use CWM to recover it back. Now i dont have 3g anymore on my tablet. Can someone teach me how to reset the whole thing back to stock?
As you can tell from the firmware i used is an HK Galaxy Tab 7.7 in ICS.
Thank you so much!

This is the P1000 forum not P6800.
[edit] Topic moved.

You can flash your firmware with mobin odin pro( on the play store)
You can flash with odin pc with pda' s choice

micger21 said:
You can flash your firmware with mobin odin pro( on the play store)
You can flash with odin pc with pda' s choice
Click to expand...
Click to collapse
I tried it with odin but it fails to write at the end.

naihochow said:
I tried it with odin but it fails to write at the end.
Click to expand...
Click to collapse
Basically this is what I get when I try to flash it with odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800OZSLP7_P6800ZSLP7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> param.lfs
<ID:0/006> recovery.img
<ID:0/006> Sbl.bin
<ID:0/006> zImage
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

use odin to flash it with rootloader mode,maybe can work

yangdliu said:
use odin to flash it with rootloader mode,maybe can work
Click to expand...
Click to collapse
you mean like checking the bootloader checkbox in odin?
btw do any of you guys know how to just flash the whole device back to factory settings other than using odin? does kies emergency firmware recovery work? do you guys know the device code?

naihochow said:
you mean like checking the bootloader checkbox in odin?
btw do any of you guys know how to just flash the whole device back to factory settings other than using odin? does kies emergency firmware recovery work? do you guys know the device code?
Click to expand...
Click to collapse
I realized what happened i must have click repartition earlier now my device only has like 44mb hence the reason why it wouldnt finish flashing b/c it ran out of space. Do any of you know how to repartition the device back to the correct size?

naihochow said:
I realized what happened i must have click repartition earlier now my device only has like 44mb hence the reason why it wouldnt finish flashing b/c it ran out of space. Do any of you know how to repartition the device back to the correct size?
Click to expand...
Click to collapse
You should use the correct .pit file and re-flash your device. Or you can also use adb shell and repartition yourself with parted utility. But that requires some unix expertise.

Pit file for 6800
https://www.box.com/shared/320b827fc7674a3ef5b9
Sent from my GT-P6800 using xda premium

kishd said:
Pit file for 6800
https://www.box.com/shared/320b827fc7674a3ef5b9
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Thanks, I made a very noobish mistake and didnt wipe the cache and i may have flashed the wrong partition file. But everything works now. Thanks for all you guys helping me out.

HEllo, IS so nessesary to flash Tab with PIT-file. I have the same problem just boot.bin not modem. CWM flashes as well? but my native (SEK) ROM from SM - not!

[Q] Can't flash VRALEC bootchain or anything else, soft brick

I restored my phone to factory default recently, with the intent of moving on to a new Cyanogenmod version. After the factory settings were restored, it took an OTA update to 4.1.2. I then tried following the guide on androidable to root it (would post the link, but apparently newbies can't)
After trying and failing several times to flash the VRALEC bootchain to my phone (I am not sure why it failed, Odin just gave me an error message every time I tried), I decided to go back to factory default again, thinking 4.0.0 would accept the VRALEC bootchain and that 4.1.2 might be the issue, but after flashing the stock image again I get the yellow triangle of death.
I have since tried flashing the VRALEC and VRBMD3 bootchains, tried flashing clockworkmod recovery, and though the phone appears to take the stock image and VRBMD3, I can't get past the yellow triangle screen on startup. Because of this, I can't check to see if USB debugging is still enabled, and I can't access the phone memory to attempt to delete whatever software is causing the issue.
Is anybody able to help me?
UPDATE: I followed the entire guide here: http://forum.xda-developers.com/attachment.php?attachmentid=1190002&d=1341959095
I successfully flashed VRALF and Root66, but VRALEC would still not install. While the rest of the process transpired as described in the guide, the end result is still giving me the yellow triangle of death.
UPDATE 2: When trying to flash VRALEC, this is the output message I get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.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)

Could you post exactly what's on your screen when you just boot into download mode? Secondly, are you absolutely positive that you accepted OTAs up to 4.1.2? Any chance you accepted 4.3?
Sent from my SCH-I535 using Tapatalk 4

Securitom said:
I restored my phone to factory default recently, with the intent of moving on to a new Cyanogenmod version. After the factory settings were restored, it took an OTA update to 4.1.2. I then tried following the guide on androidable to root it (would post the link, but apparently newbies can't)
After trying and failing several times to flash the VRALEC bootchain to my phone (I am not sure why it failed, Odin just gave me an error message every time I tried), I decided to go back to factory default again, thinking 4.0.0 would accept the VRALEC bootchain and that 4.1.2 might be the issue, but after flashing the stock image again I get the yellow triangle of death.
I have since tried flashing the VRALEC and VRBMD3 bootchains, tried flashing clockworkmod recovery, and though the phone appears to take the stock image and VRBMD3, I can't get past the yellow triangle screen on startup. Because of this, I can't check to see if USB debugging is still enabled, and I can't access the phone memory to attempt to delete whatever software is causing the issue.
Is anybody able to help me?
UPDATE: I followed the entire guide here: http://forum.xda-developers.com/attachment.php?attachmentid=1190002&d=1341959095
I successfully flashed VRALF and Root66, but VRALEC would still not install. While the rest of the process transpired as described in the guide, the end result is still giving me the yellow triangle of death.
UPDATE 2: When trying to flash VRALEC, this is the output message I get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.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)
Click to expand...
Click to collapse
Did you use the bootloader option when you tried to flash the Boot chain VRALEC. Don't use PDA option.

buhohitr said:
Did you use the bootloader option when you tried to flash the Boot chain VRALEC. Don't use PDA option.
Click to expand...
Click to collapse
I tried it both ways, no results on either.
I confirmed that I didn't get 4.3 because I checked in the "about phone" right after I did that.
Download mode screen shows the following:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWAEV: 1

Securitom said:
I tried it both ways, no results on either.
I confirmed that I didn't get 4.3 because I checked in the "about phone" right after I did that.
Download mode screen shows the following:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWAEV: 1
Click to expand...
Click to collapse
I hate to tell it to you but that's the latest 4.3 VRUCML1 software. Download mode for 4.1.2 and older only has (notice what is missing):
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
You'll need to do this soft brick method to recover. Since you're on 4.3, you can not flash a custom recovery, custom rom/kernel, nor downgrade your software via Odin to anything except 4.3.

Securitom said:
I tried it both ways, no results on either.
I confirmed that I didn't get 4.3 because I checked in the "about phone" right after I did that.
Download mode screen shows the following:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWAEV: 1
Click to expand...
Click to collapse
What Odin version did you use? Try different Odin version see if it helps. http://forum.xda-developers.com/showthread.php?t=2189539 Also reboot your PC to start fresh. If still not working then try to reflash with Pit file and MF1 full stock rom using Odin.

SlimSnoopOS said:
I hate to tell it to you but that's the latest 4.3 VRUCML1 software. Download mode for 4.1.2 and older only has (notice what is missing):
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
You'll need to do this soft brick method to recover. Since you're on 4.3, you can not flash a custom recovery, custom rom/kernel, nor downgrade your software via Odin to anything except 4.3.
Click to expand...
Click to collapse
Thank you, thank you, THANK YOU! You brought my phone back from the dead!
So I'm stuck only using the stock firmware for the rest of the phone's life? Unfortunate, but at least it's not bricked anymore.

Securitom said:
Thank you, thank you, THANK YOU! You brought my phone back from the dead!
So I'm stuck only using the stock firmware for the rest of the phone's life? Unfortunate, but at least it's not bricked anymore.
Click to expand...
Click to collapse
My pleasure but all of the thanks is owed to @ThePagel. Make sure to drop by his soft brick thread (the one that worked!) and express your success! I feel the more people that express their success there, the less fear down the road someone else may have with the method. :highfive::good:
As of this moment, all anyone knows is that you're stuck on TW 4.3 unless a tool is ported to allow custom roms/kernels. You can only root 4.3 using Saferoot which is linked in our TW 4.3 discussion thread. You can be sure if any big developments on cracking 4.3 open will be covered there.

[Q] OTA 4.4.2 update failed, Samsung Experience no help, Please help me

I did the verizon pushed update to 4.4.2 today on my SCH I535 S3 which was totally stock with encryption. After the install finished "upgrading apps" it then did a re-boot and asked for my encrypt pin then showed the outline Andy. Then after a couple of vibrations it re-boot again and will continue this cycle until battery is removed. After sitting on the phone for several hours and conversing with Samsung and Verizon they pointed me to Samsung Experience in a Best Buy and if that doesn't work I have to send it to Samsung for re-flash. They said they couldn't get their software to recognize my phone. The guy there recommended using odin to download a stock rom.
I have downloaded odin 3.07 and have downloaded a 4.3 stock rom. I set up odin with auto reboot and F. reset time checked and nothing else. I select the .tar.md5 in the bootloader and here is my odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I535VRUCNC1_I535VZWCNC1_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECURE BOOT: ENABLE
BOOTLOADER AP SWREV: 2
SW REV CHECK FAIL : Found 2 > Binary 1
Please tell me how to recover my phone. I am new to this so give me detail please.

I believe since u pushed the 4.4.2 ne1 update u need to Odin the 4.4.2 ne1 tar file, not the 4.3 file

Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!

4theluvof2 said:
Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!
Click to expand...
Click to collapse
No problem!! Glad it worked, hit that thanks button if you don't mind!

SCH-I535
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz

hammadsalik said:
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz
Click to expand...
Click to collapse
No I didn't get the 4.3 working. I did get the 4.4.2 working though. I am not sure how exactly you'd revert back to an older version, Sorry.

[Q] Strange Downgrade Problem !!!

Hello @ all
I got a new Samsung Note Edge SM-N915FY, with 4.4.4 Stock Rom from factory.
I install CWM recovery and have root. All went fine. I did a good Backup and so I can start to play with.
I try Mickey fast and famous Rom and works also good and I tried other stuff around. Some of them are good and some of the offered stuff is not booting, but no problem, it is only for playing around.
I install with Odin Lollipop 5.0.1 and give this Beta a try.
For me is important I can use XPosed Framework with a SkyModul with HDMI out, ( I know this is still in development) so I decide to go back to 4.4.4 Rom.
And this is not working. I can try to install the factory 4.4.4 rom or other stuff which works before and right now after install the Phone starts with sign "Samsung Note Edge" and shuts down again and so on. No Booting possible.
I tried the Factory Stock Rom with Odin and after downloading the ROM the Download Mode said "Filesize is too big"
Backup from 5.0.1 lollipop works everytime.
Any Ideas??
Regards
Panic Brothers

Panic Brothers said:
Hello @ all
I got a new Samsung Note Edge SM-N915FY, with 4.4.4 Stock Rom from factory.
I install CWM recovery and have root. All went fine. I did a good Backup and so I can start to play with.
I try Mickey fast and famous Rom and works also good and I tried other stuff around. Some of them are good and some of the offered stuff is not booting, but no problem, it is only for playing around.
I install with Odin Lollipop 5.0.1 and give this Beta a try.
For me is important I can use XPosed Framework with a SkyModul with HDMI out, ( I know this is still in development) so I decide to go back to 4.4.4 Rom.
And this is not working. I can try to install the factory 4.4.4 rom or other stuff which works before and right now after install the Phone starts with sign "Samsung Note Edge" and shuts down again and so on. No Booting possible.
I tried the Factory Stock Rom with Odin and after downloading the ROM the Download Mode said "Filesize is too big"
Backup from 5.0.1 lollipop works everytime.
Any Ideas??
Regards
Panic Brothers
Click to expand...
Click to collapse
ii know with other phones the upgrade was a one-way proposition. Once the new bootloader was flashed you were essentially stuck on the newer firmware. Downgrading, even official firmware, resulted in bootlooping... Note 3, S4 had this little "feature" and it caused mass hair pulling...

After couple tests I think the Note Edge has this kind of "feature"
No chance to get back to 4.4.4
it caused mass hair pulling...
Click to expand...
Click to collapse
No Hairs here since couple of years but for sure this is a feature for massive Hair pulling

I just try all OdIn Versions and still I get this Message.
Is there no chance to get a Downgrade to 4.4.4??
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.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> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
Is it possible to get a valid PIT File for SM-SN915FY to download? I just searched around and it seems that other Note4 Owner had the same problem and it was solved with a valid PIT File.

Panic Brothers said:
I just try all OdIn Versions and still I get this Message.
Is there no chance to get a Downgrade to 4.4.4??
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.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> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
Is it possible to get a valid PIT File for SM-SN915FY to download? I just searched around and it seems that other Note4 Owner had the same problem and it was solved with a valid PIT File.
Click to expand...
Click to collapse
I had exact the same problem with the galaxy note 4. When i put another custom rom on the phone with odin, it works good. Then i go back to the original rom till so far no problem.Then i put a new rom on it from outside my country. Then the problems starting, everytime i get exact the same problem as you have. The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image. So after i can only download the official rom from my country. very strange. Till so far no problem with my Note Edge.

On NOTE 4 was possibility to downgrade STOCK ROM (from 5.x to 4x) with Mobile ODIN. Did You try this way? But I'm not sure, if Mobile ODIN is compatible with EDGE...
@phablet

Jumbo78 said:
On NOTE 4 was possibility to downgrade STOCK ROM (from 5.x to 4x) with Mobile ODIN. Did You try this way? But I'm not sure, if Mobile ODIN is compatible with EDGE...
@phablet
Click to expand...
Click to collapse
THX for this hint ... this I did not tried out but I just checked and load the mobile ODIN and the Edge is not supported in the actuall Version. Maybe later.
So it is only chance to wait for Xposed on Samsung Stock ROM :crying:

I'M back on 4.4.4 Now !!!!
This are the steps that worked on my rooted Edge SM-N915FY
- Boot to recovery mode wipe all Data/Cache
- Boot to download mode
- Start Odin 3.09 and load (AP) the original 4.4.4 from SamMobile (N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4)
- After press start all will be loaded and You get errormessage on screen Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image (Your Phone will not boot up now)
- Remove Battery and go again in the download mode
- Reset ODIN and load (AP) the custom recovery File (n915f-cwm-recovery-6.0.5.1)
After I load the recovery file the Phone starts again correct and shows 4.4.4 Version

Panic Brothers said:
I'M back on 4.4.4 Now !!!!
This are the steps that worked on my rooted Edge SM-N915FY
- Boot to recovery mode wipe all Data/Cache
- Boot to download mode
- Start Odin 3.09 and load (AP) the original 4.4.4 from SamMobile (N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4)
- After press start all will be loaded and You get errormessage on screen Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image (Your Phone will not boot up now)
- Remove Battery and go again in the download mode
- Reset ODIN and load (AP) the custom recovery File (n915f-cwm-recovery-6.0.5.1)
After I load the recovery file the Phone starts again correct and shows 4.4.4 Version
Click to expand...
Click to collapse
my N915FY is already updated with lollipop (via KIES)
i never rooted the phone...
i want to go back to 4.4.4, is there any chance to do that? can i root now the phone anf follow the same steps that worked for you?

Goofy-Goober said:
my N915FY is already updated with lollipop (via KIES)
i never rooted the phone...
i want to go back to 4.4.4, is there any chance to do that? can i root now the phone anf follow the same steps that worked for you?
Click to expand...
Click to collapse
Sorry...but this I don't know. The first thing I do for my new devices is the "root" procedure and delete google apps and crapy stuff.
But why not? I think Odin and the Download Mode are possible without a rooting a device.
"Try and error" or maybe it works.
Good luck
*Edit*
you need a custom recovery like CWM oder TWRP and you must activate USB debugging in your developer options.

this is very strange that is happening to you guys, i have the tmobile version edge, used to have kitkat when i bought it, ROM from trinidad and tobago, decided to download lollipop from tmobile, did not like it, went back to trinidad and tobago kitkat, everything flashed ok, just a bootloop that resolved after i wiped cache
my phone has never been rooted, no custom recovery, no custom rom
hope this helps you out

I have 915g and to downgrade to 4.4.4 all i had to do was turn off auto reboot in odin, flash stock kitkat, boot into stock recovery, wipe data/cache and it booted.

[Q&A] [GUIDE}★Downgrade 4.3 to 4.1.2★Unlock bootloader★Root

Q&A for [GUIDE}★Downgrade 4.3 to 4.1.2★Unlock bootloader★Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE}★Downgrade 4.3 to 4.1.2★Unlock bootloader★Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I'm running android 4.4.2 (S3 I535). I want downgrade from 4.4.2 to 4.1.2. Can i replace 4.3 update ML1 by 4.4.2 update VRUDNE1?

Sea23.vn said:
I'm running android 4.4.2 (S3 I535). I want downgrade from 4.4.2 to 4.1.2. Can i replace 4.3 update ML1 by 4.4.2 update VRUDNE1?
Click to expand...
Click to collapse
You can try as I haven't tried that
If you brick your device, you can savely go back to 4.3 or 4.4

You can try as I haven't tried that
If you brick your device, you can savely go back to 4.3 or 4.4
Click to expand...
Click to collapse
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S3ModedRom.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I got when I try to do in 4.4.2.
After this, phone just became soft-bricked phone.
What I did is instead of using 4.3 ML1 md5 file, I used 4.4.2 NE1 md5 file.
I think there are some way to downgrade 4.4.2 to 4.1.2, but I don't know what it would be...

This has proven to be successful on my phone.
Got tired of being stuck on 4.3 ML1 and having to use a limited selection of custom ROMS, was eligible for a phone upgrade so I figured meh, why not try this out. Followed the instructions (although they could be more concise) and got stuck at the Verizon 4G LTE screen with the flashing rings that appears after the Samsung logo displays. After removing the battery, booting in to recovery (volume up + home + power), performing a factory reset/clearing the cache and rebooting, everything was fine.
Thanks for this.

Nogo
Successfully downgraded 4.1.2 boots fine baseband still ml1 bootloader still ml1 tried casual root unlock program roots fine says flashing insecure bootloader successful but hard bricks on flashing recovery.upon recovering from hard brick I reflash ml1 via Odin let it boot then back to download mode flash my modded rom.tar successfully and try to repeat steps with same results I've tried flashing vralec.bootchain.tar.md5 via Odin fails cannot unlock bootloader I've repeated the steps to create my s3modedrom.tar.md5 with same results was wondering if anyone else was having issues unlocking BL or if I'm missing something any help would be greatly apreciated

PilowPants said:
Successfully downgraded 4.1.2 boots fine baseband still ml1 bootloader still ml1 tried casual root unlock program roots fine says flashing insecure bootloader successful but hard bricks on flashing recovery.upon recovering from hard brick I reflash ml1 via Odin let it boot then back to download mode flash my modded rom.tar successfully and try to repeat steps with same results I've tried flashing vralec.bootchain.tar.md5 via Odin fails cannot unlock bootloader I've repeated the steps to create my s3modedrom.tar.md5 with same results was wondering if anyone else was having issues unlocking BL or if I'm missing something any help would be greatly apreciated
Click to expand...
Click to collapse
Last I remember you could only revert back to 4.1.2 if you didn't take the update to go to NC1. If you did take the update to 4.3 NC1 trying to unlock your bootloader will not work and your stuck on it
Sent from my Nexus 5