I was asked to make this one-click to help simplify the process of restoring a stock factory build for our Note 8.0 users. At this time neither myself or @garwynn are planning on releasing a rooted One-Click.
This Odin One-Click.exe contains the Stock GT-N5110 XXDNE1 Bootloader, Kernel, Modem and ROM for the Samsung Galaxy Note 8 16GB Wi-Fi edition (GT-N5110). Yes, that means this comes with the full Knox Bootloader.
There has been no change to the ROM from the initial build released by Samsung.
This will NOT trigger the Yellow Triangle NOR will it increment the Odin flash count.
This one-click resets your whole device to the stock XXDNE1 experience, similar to a factory restore and it may wipe all data. It also contains the full bootloader and Knox.
Instructions:
1: Backup anything important and Disable any PINs.
During this process your device's software will be returned to the Stock setup. All system data will be lost. To be safe, it is best to archive your backup off your device, ie on your PC or Dropbox.
2: Install Samsung USB/Android drivers (if necessary).
Samsung Drivers Download Link
3: Download the XXDNE1 Stock ROM One-Click.
GT-N5110 XXDNE1 Full Restore Unrooted (Compressed Archive).exe (Resets user data)
4: Unzip One-Click ROM using 7zip (this package is a self-extracting exe you should just be able to double-click on it after download and it will do the rest).
5: Start the Odin One-Click.
Navigate to the location where the "GT-N5110 XXDNE1 Full Restore Unrooted.exe" was saved upon extract from the 7Zip archive.
Double-click on "GT-N5110 XXDNE1 Full Restore Unrooted.exe". *On Vista or newer, you may need to right-click on the file and Run as Administrator.
6: Place device in Download Mode.
- Power device completely off.
- Press and hold Volume Down, Home and Power buttons, all at the same time.
- Release the buttons only when the ‘Warning!!’ message appears.
- Press [Volume Up] to enter Download mode.
7: Connect USB cable to PC and device.
Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click.
8: Start Odin flash process.
Press [Start].
9: Complete - PASS!
Status should change to green PASS! At this point your device should automatically reboot.
The boot process will take slightly longer than usual during which time you'll see the Samsung logo screen.
Congratulations! You've flashed the Factory Restore XXDNE1 build!
XDA:DevDB Information
[ROM][ODIN] GT-N5110 XXDNE1 (Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Samsung Galaxy Note 8.0
Contributors
rwilco12
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2015-02-09
Last Updated 2015-02-09
Download Link: rwilco12.com/forum/showthread.php?tid=762
n5100
Having trouble loading 4.4.2 bootlader through odin onto my n5100 would it be ok to flash this, then root it and then install the custom n5100 rom of my choice or would I be on tne wrong bootlader and mess my tab up TIA
johnnyk75 said:
Having trouble loading 4.4.2 bootlader through odin onto my n5100 would it be ok to flash this, then root it and then install the custom n5100 rom of my choice or would I be on tne wrong bootlader and mess my tab up TIA
Click to expand...
Click to collapse
I believe it would mess up your bootloader but I don't have a way to verify as I don't have the n5100. Sorry!
Sent from my SPH-L900 using Tapatalk
triangle away
Will this reset the flash counter and allow ota updates? Or do you need to reset flash counter before you do this?
capitoldach said:
Will this reset the flash counter and allow ota updates? Or do you need to reset flash counter before you do this?
Click to expand...
Click to collapse
This won't reset the counter but it won't increment it either. This is a 100% stock unrooted ROM so you'll be able to take OTA's again after flashing.
Can I side load this with ADB? I am currently bricked and looking to start over if I can get my N5110 to install another ROM.
Sent from my SGH-I317 using XDA Premium 4 mobile app
addison892 said:
Can I side load this with ADB? I am currently bricked and looking to start over if I can get my N5110 to install another ROM.
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're bricked, how do you intend to use ADB?
styles420 said:
If you're bricked, how do you intend to use ADB?
Click to expand...
Click to collapse
I have full access to recovery and download modes.
I am unable to Odin and flash because of partition errors. I plan on using TWRP and the ADB option with Android SDk. Do you think this will work?
I have not been able to Odin . Pit files successfully and re-partition. I am hoping ADB will allow me to put the rom inside the current partitions and use TWRP to flash.
Just a thought. I really don't know what I am doing or how to fix it. But if I have download mode and recovery, I should be able to find a way.
I am currently in a bootloop to recovery.
Thanks for your response and any suggestions you may have.
Sent from my SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
I have followed the instructions posted here to the letter, but keep getting a FAIL! at the sboot.bin point shortly after starting one-click.
Sent from my SGH-I317 using XDA Premium 4 mobile app
addison892 said:
I have full access to recovery and download modes.
I am unable to Odin and flash because of partition errors. I plan on using TWRP and the ADB option with Android SDk. Do you think this will work?
I have not been able to Odin . Pit files successfully and re-partition. I am hoping ADB will allow me to put the rom inside the current partitions and use TWRP to flash.
Just a thought. I really don't know what I am doing or how to fix it. But if I have download mode and recovery, I should be able to find a way.
I am currently in a bootloop to recovery.
Thanks for your response and any suggestions you may have.
Sent from my SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
I have followed the instructions posted here to the letter, but keep getting a FAIL! at the sboot.bin point shortly after starting one-click.
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately I don't know that this will work for you at this time. Essentially the one-click is a repackaged TAR. The TAR itself contains image files that correspond to specific partitions on your device. If the partitions on the device don't match up Odin is supposed to throw up a flag and stop the flash in order to prevent bricking the device.
I can't be 100% certain but given the fact it is stopping on sboot.bin, my guess is that the issues you are experiencing probably come from flashing a ZIP bootloader or ROM for another device. If that's the case we might be able to backtrack and undo what you've done so far but this won't work unless you have the right partition structures already in place.
I have spent hours trying to re-partition. The furthest I have gotten is where I am now... Stuck on Get PIT for mapping..
.. In ODIN. I am using the only PIT file for N5110 available on the entire World Wide Web!
☺
Sent from my SGH-I317 using XDA Premium 4 mobile app
hello, could someone please point me in the right direction. I've been trying to use this tool, I have access to stock recovery, when I factory reset it says it can't mount the /system. I tried this tool to reinstall every thing, but it fails at sboot.bin. all the research I've done leads me to believe this has something to do with the bootloader being locked, but I can't find anything about it, I keep getting lead back to this post. If anyone could point me where I need to be to figure this out I would really appreciate it.
Edit: I'm not sure what my problem was, but I eventually downloaded the stock 4.4.2 firmware and was able to flash through Odin and get up and running.
bookofjoshua said:
hello, could someone please point me in the right direction. I've been trying to use this tool, I have access to stock recovery, when I factory reset it says it can't mount the /system. I tried this tool to reinstall every thing, but it fails at sboot.bin. all the research I've done leads me to believe this has something to do with the bootloader being locked, but I can't find anything about it, I keep getting lead back to this post. If anyone could point me where I need to be to figure this out I would really appreciate it.
Edit: I'm not sure what my problem was, but I eventually downloaded the stock 4.4.2 firmware and was able to flash through Odin and get up and running.
Click to expand...
Click to collapse
can you point me in the direction of where you found stock 4.4.2 firmware, looked everywhere for odin flash file
redman2770 said:
can you point me in the direction of where you found stock 4.4.2 firmware, looked everywhere for odin flash file
Click to expand...
Click to collapse
For some reason they post the US version under Cellular South. You'll need to create a free account to download. It took about am hour for me to download with the free account.
http://www.sammobile.com/firmwares/download/30487/N5110UEU2CNE2_N5110XAR2CNE2_XAR.zip/
Does this clean up all the crap left over from many flashes & nandroid backups & restores? I find I have a lot of bits like old directories from previous meddling (mine) & would like to a real clean up back to pristine stock (so I can start meddling again, sort of from scratch so to speak.
Going to run it anyway (meddling again) to see what comes out the other end but was curious 'is all.
Error
This fails for me - on the tablet it says: sw rev. check fail. device:2, binary:1
Trying to flash back to stock after CM12
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<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>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
kjarlin said:
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<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>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
thewinelover said:
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
Click to expand...
Click to collapse
Still no solution?
dopeismarcus said:
Still no solution?
Click to expand...
Click to collapse
+1
Same error.
Regards
kjarlin said:
This fails for me - on the tablet it says: sw rev. check fail. device:2, binary:1
Trying to flash back to stock after CM12
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<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>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
thewinelover said:
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
Click to expand...
Click to collapse
dopeismarcus said:
Still no solution?
Click to expand...
Click to collapse
mcpterra said:
+1
Same error.
Regards
Click to expand...
Click to collapse
Not able to verify as I no longer have the Note 8 but if I remember correctly the error you are getting is due to your device having a newer bootloader than the one-click. Most of the time a new bootloader locks out flashing of older bootloaders.
Sent from my Nexus 5X using Tapatalk
Related
Was stuck on dl01 with voodoo, bloatware frozen, rooted, and using launcherpro.
I followed the first link in that sticky: http://forum.xda-developers.com/showthread.php?t=908451
and now my phone wont boot up. when I turn it on I see the samsung logo and then it goes through this:
--Wiping data--
Formatting FOTA...
Formatting DATA...
Data Wipe failed.
Formatting Cache
Formatting DBDATA
Wipe_Data Failed.
Click to expand...
Click to collapse
then it will go back to the samsung logo and go around in circles again.
everything went fine with odin. This is what the little message window said:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Enter CS for MD5..
<ID:0/005> Check MD5.. Do not unplug the cable..
<ID:0/005> Please wait..
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Checking MD5 finished Sucessfully..
<ID:0/005> Leave CS..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> recovery.bin
<ID:0/005> zImage
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I have no idea what went wrong but now i have no phone and this sux big time.
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Rockstar52 said:
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Click to expand...
Click to collapse
will take a look at that in a minute thanx.
but what the hell went wrong? was it something to do with voodoo?? none of the steps said to disable it or anything....
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Rockstar52 said:
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Click to expand...
Click to collapse
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
If you can get odin to work again use atlas_v2.2.pit to format back to rfs file-system. Use the PIT button in odin.
fupamobile said:
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
Click to expand...
Click to collapse
Definitely try to Odin the Pit 2.2 that DMT suggested.
Here's a link to a giude that should help get you back to stock as it isn't as intimidating for some as the un-bricking one: http://forum.xda-developers.com/showthread.php?t=1124391
And if that fails might I suggest trying it on a more up to date PC, maybe your issues have come from that if your pc never recognized the phone properly.
Nnneeeedd heellp nowwww!!!!!!!!!!
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
xwhofarted said:
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
Click to expand...
Click to collapse
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Voodoo used to be a p.i.t.a but it really isn't that hard now with the newer cwm supporting both voodoo and non voodoo, the steps myself and the person who posted above me are describing direction for odin..not heimdall.I don't know much about heimdall or how to use it but you can get your phone back and working using odin
Use the link in junkboy0's reply..follow the directions in the first post.
fupamobile said:
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
efan450 said:
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
fupamobile said:
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
Click to expand...
Click to collapse
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
I concur...soft bricked, boot looped, many many times and never used heimdall either
Sent from my SCH-I500 using XDA App
fupamobile said:
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
Click to expand...
Click to collapse
Correct voodoo will be gone but you can just flash another voodoo kernel later and you can flash voodoo over voodoo just not voodoo to non voodoo with out removing it
Sent from my SCH-I500 using XDA App
efan450 said:
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
fupamobile said:
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
Click to expand...
Click to collapse
Recovery..clock work mod...or cwm is the recovery program you will use to install custom rom, kernels, or zip files...I will send you a p.m.later with files, info, and instructions and you can read over it and decide if you want to do it now or wait till you're a lil more familiar with the process..but for now odin the pit atlas 2.2 file and eb01 and you will be stock and be able to use launcher pro.
Sent from my SCH-I500 using XDA App
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
I found that sometimes its all in the technique of how you plug things in and the usb used. Try different usb cords. Try different usb ports. and then for some reason what worked for me is have odin open plug usb into computer, and then put the phone into download mode and finally connect the microUSB into the phone. Hope it works, hit back if it does or doesnt
[email protected] said:
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
Click to expand...
Click to collapse
How long did you let it go for on the factoryfs.img?
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
creepyncrawly said:
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
Click to expand...
Click to collapse
I have tried it on all usb ports that I have on my laptop.
OK here's exactly what I did to my phone:
I downloaded the ICS version for i777 from sammobile and flashed it using ODIN. Then, I installed Siyah kernel using mobile odin. I then installed triangle away to get rid of the flash counter. I used my phone like this for a couple of days. Then today, I installed the AOKP rom. To do this, I first back up using CWM, then i booted in CWM recovery mode, did a complete wipe, deteled cache and dalvik, and then I proceeded to install the rom. Installation worked fine and everything, however the data wasn't working on my phone. So I then tried to enter the T-Mobile APN settings (it's an unlocked phone), however I couldn't save the APN settings. Tried to enter them multiple times and selected save from the menu, but it just wouldn't show up on the APN list. So, I tried to restore to my back up in CWM restore, however that failed. Admittedly, I should have asked for help at this point. However I was frustrated, so I decided to just use Odin again to flash the ICS stock firmware that I got from sammobile. However, it failed and had some error along the lines of completed writing but operation failed? I tried switching to different USB ports and restarted Odin with run as administrator, but kept getting the same error. On one of these numerous tries, I also tried to check the re-partition option just to see if that would change anything (probably not a very smart idea). Anyways, at some point during these numerous attempts, it got to the point where the phone wouldn't boot up and asked me to connect to samsung kies to restore. I tried that but my phone won't connect with kies. I then found your one-click odin stock firmware thing on these boards and used that. Tried multiple times at different ports, but it keeps getting stuck at factoryfs.img. I have left it in there for a good 30 minutes in this current try (4th). Also, this may or may not be relevant, the flash counter keeps going up.
PS: This is my first android phone so I'm pretty new at this, but I did try to read up a lot before trying anything (well, except for when I randomly checked re-partition that one time).
Edit: Sorry I should have made this clear - even though the phone will not boot, I can still get into download mode.
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
creepyncrawly said:
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
Click to expand...
Click to collapse
'
Thank you for the swift response. No, I am unable to get into recovery mode. It goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
While I didnt have your issues. I also recently bought an i777, my install went very smooth, everything worked more or less on the first try tried diff cords, ports and then finally it was the plug sequence that did it for me. Upon flashing AOKP, I immediately unlocked the phone via that galaxy S unlocker, I followed the steps to the T and my IMEI is still the same. I am also on tmobile, with working edge. I still have the pesky triangle, but I havent read too many good things about the triangle remover.
Perhaps you have a bad rom download? It might sound silly but flashing AOKP for a friend when I redownloaded the rom, everything worked fine. What the guy above me said, try recovery mode instead and then go from there. Good news is that your phone doesnt sound borked
creepyncrawly said:
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
Click to expand...
Click to collapse
Ok I tried this, and it completed successfully in Odin, however, the phone now gets stuck on the "Samsung Galaxy SII GT-I9100" screen.
But will it boot into recovery now?
creepyncrawly said:
But will it boot into recovery now?
Click to expand...
Click to collapse
No, it still does not boot into recovery.
OT: How long will I have the 5 min restriction on posting?
Also, I don't know if this is relevant, but when I try to turn off the phone, it turns off but then it'll automatically start back up within a few seconds and then get stuck on the samsung galaxy sII screen
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
creepyncrawly said:
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
Click to expand...
Click to collapse
No, I didn't put a pith file. Also just to make sure I'm flashing the right file, is it the one called "I777 UCKH7 stock param.lfs"?
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
creepyncrawly said:
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
Click to expand...
Click to collapse
It was the UCLE5 file. I'll try this one.
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
[email protected] said:
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
Click to expand...
Click to collapse
OK I tried it on all the USB ports that I have on my laptop. No luck. Still getting stuck at Sbl.bin. Any more ideas?
Yes. If it were my phone, I would start by flashing the param.lfs by itself and see if that allows it to boot, or makes progress.
If not, then I would flash the sbl.bin by itself and see if that allows it to boot, or makes progress.
If still not, then I would try the full UCKH7 package with the PIT file, and repartition checked.
You can get all the files from the Download Repository. Please bear in mind that there is risk in everything you are doing, (and have been doing.)
I had mk2 installed with root, stock ROM. I tried to update with OTA with no luck, so I unrooted, still no luck
Any ideas how to get the 4.4.2 stock ota upgrade? I got rid of root, but the bootloader still says custom.
Thanks so much
I have same issue.. But I was running saferoot as well
Sent from my SCH-I545 using XDA Premium 4 mobile app
mikedombo said:
I had mk2 installed with root, stock ROM. I tried to update with OTA with no luck, so I unrooted, still no luck
Any ideas how to get the 4.4.2 stock ota upgrade? I got rid of root, but the bootloader still says custom.
Thanks so much
Click to expand...
Click to collapse
Sounds like you still have something modified on your system from root. You should Odin the no-wipe mk2 odin from here and then try taking to OTA.
Why dint r you just Odin the nb1 and not worry about the update
Sent from my Nexus 5
I had the same custom issue after unrooting. Go back and find the saferoot file you downloaded. ( if you no has go finds again)
Depending where your at you'll need to either re-root and install superuser(let it update) or if you haven't removed SU yet don't do it.
The point is you need to use the uninstall.bat from saferoot to remove the root and then remove root via superuser. reboot (it'l still say custom) and wait 10 mins and then reboot again, should now come up clean.
But from there I still wasn't able to update OTA.
Make sure you didn't have ANY apps frozen via titanium backup or any stock apps deleted. Verizon pulls some crazy sorcery
It will be best to just Odin the no-wope mk2 full tar like I said a few posts up
Sent from my SCH-I545 using Tapatalk
odin flashing failing
so I'm trying odin flashing using both 1.85 and 3.09, and neither work.
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUEMK2_I545VZWEMK2_I545VRUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Nevermind - looks like I just had a bad cable
Is nb1 the new 4.4.2 OTA? Where can we get it? Or is that the leak?
One I update to 4.4.2, I lose root. Am I correct?
Sent from my SCH-I545 using xda premium 4 app
Phone: Verizon Galaxy S4
Tablet: Samsung Galaxy Tab2 10.1
swrght13 said:
One I update to 4.4.2, I lose root. Am I correct?
Sent from my SCH-I545 using xda premium 4 app
Phone: Verizon Galaxy S4
Tablet: Samsung Galaxy Tab2 10.1
Click to expand...
Click to collapse
that is correct
Finally got OTA with odin
BruteSource said:
Is nb1 the new 4.4.2 OTA? Where can we get it? Or is that the leak?
Click to expand...
Click to collapse
NC5 is the OTA version, I just got it to work once I used odin.
I got the OTA to succesfully install after using odin as well. Flashed back to a fully stock rom(mk2) and did a factory reset to remove the "samsung custom" bootscreen. Once that finished, I installed the new OTA
joshuabg said:
Sounds like you still have something modified on your system from root. You should Odin the no-wipe mk2 odin from here and then try taking to OTA.
Click to expand...
Click to collapse
I have a question; under build number on my phone it says JSS15J.I545VRUEMK2
Under Step 1 in the link you provided I don't see my build number listed anywhere, so how do I know which factory image to download and flash?
Thanks for any help. I'm an extreme novice at rooting. I rooted my phone for the first time back in December using saferoot/SuperSU and am a real newbie when it comes to stuff like this, so I'd really appreciate any help.
WildKap said:
I have a question; under build number on my phone it says JSS15J.I545VRUEMK2
Under Step 1 in the link you provided I don't see my build number listed anywhere, so how do I know which factory image to download and flash?
Thanks for any help. I'm an extreme novice at rooting. I rooted my phone for the first time back in December using saferoot/SuperSU and am a real newbie when it comes to stuff like this, so I'd really appreciate any help.
Click to expand...
Click to collapse
Flash the one for mk2. What do you want to do? Odin mk2 will put your phone back to a like new condition. If you flash the no wipe version everything on your internal will need preserved.
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Flash the one for mk2. What do you want to do? Odin mk2 will put your phone back to a like new condition. If you flash the no wipe version everything on your internal will need preserved.
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I'd prefer the no-wipe version, but it doesn't really matter at this point since I have all my stuff backed up and already did a factory reset anyway. I'm just trying to get my phone back to stock so I can do the OTA update.
Again, I know this is probably a real newbie question but when you say "flash the one for mk2", which build file am I supposed to download out of these that are listed in that post you linked me to: VRUAMDK, VRUAME7 or VRUDMI1?
WildKap said:
I'd prefer the no-wipe version, but it doesn't really matter at this point since I have all my stuff backed up and already did a factory reset anyway. I'm just trying to get my phone back to stock so I can do the OTA update.
Again, I know this is probably a real newbie question but when you say "flash the one for mk2", which build file am I supposed to download out of these that are listed in that post you linked me to: VRUAMDK, VRUAME7 or VRUDMI1?
Click to expand...
Click to collapse
If you are already backed up and want to be on mk2 I'd flash the all in one file from here. http://forum.xda-developers.com/showthread.php?p=49687770. Just extract the.tar file from the .rar file using 7-zip
Sent from my SAMSUNG-SGH-I727
WildKap said:
I'd prefer the no-wipe version, but it doesn't really matter at this point since I have all my stuff backed up and already did a factory reset anyway. I'm just trying to get my phone back to stock so I can do the OTA update.
Again, I know this is probably a real newbie question but when you say "flash the one for mk2", which build file am I supposed to download out of these that are listed in that post you linked me to: VRUAMDK, VRUAME7 or VRUDMI1?
Click to expand...
Click to collapse
The MK2 ODIN images can be found here. Don't try flashing anything earlier than MK2 if you're planning to go to NC5 via OTA.
Kiss root good bye for the foreseeable future once you upgrade to KK.
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
swrght13 said:
I got the OTA to succesfully install after using odin as well. Flashed back to a fully stock rom(mk2) and did a factory reset to remove the "samsung custom" bootscreen. Once that finished, I installed the new OTA
Click to expand...
Click to collapse
You do not have to factory reset to remove the "Custom" screen.
Restore a factory stock image. Boot your phone. Wait an hour or so. Now, reboot. It won't show "Custom" any longer.
You just need to leave the phone running long enough for the scanner to figure out that it's now back to stock.
jd1639 said:
If you are already backed up and want to be on mk2 I'd flash the all in one file from here. http://forum.xda-developers.com/showthread.php?p=49687770. Just extract the.tar file from the .rar file using 7-zip
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Ok, cool. And basically, I'm just booting the phone in ODIN mode and then I'm selecting the .tar file under "PDA" on the app on my computer, pressing start and then that's it?
WildKap said:
Ok, cool. And basically, I'm just booting the phone in ODIN mode and then I'm selecting the .tar file under "PDA" on the app on my computer, pressing start and then that's it?
Click to expand...
Click to collapse
That's correct. Just use the default settings that Odin has
Sent from my SAMSUNG-SGH-I727
jd1639 said:
That's correct. Just use the default settings that Odin has
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Awesome. Thanks so much for your help, dude, I really appreciate it!!:good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:03 AM ----------
jd1639 said:
That's correct. Just use the default settings that Odin has
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
OK, I did everything and am getting a fail message in Odin...any idea why?
It says
<ID:04/004> NAND Write Start!!
<ID:04/004> FAIL! (Auth)
<OSM> All threads completed. (succeeded 0 / failed 1)
EDIT: Some users have experienced issues with my initial Full-wipe .tar. I am adding @Surge1223 's files as additional options:
Full-Wipe NG6
No-Wipe NG6
I545VRUFNG6_Full_Wipe.rar
This is an "All-in-One" file, extract the .tar and flash in PDA Slot in Odin(AP in Odin v3.09+).
**Tip** The most common cause of an Odin flash failure is a bad USB port or cable.
man you like came out of nowhere. first with the updated, fixed safestrap and then with this. thank you for everything, man
skepticmisfit said:
man you like came out of nowhere. first with the updated, fixed safestrap and then with this. thank you for everything, man
Click to expand...
Click to collapse
lol, been hanging out in a remote corner of the I337 forum stalking and learning from all of the greats like @jeboo, @Surge1223, @Hashcode, and others. Thank you!
muniz_ri said:
lol, been hanging out in a remote corner of the I337 forum stalking and learning from all of the greats like @jeboo, @Surge1223, @Hashcode, and others. Thank you!
Click to expand...
Click to collapse
ah, everything I know I learned from my tablet and my old phone. this is the first and hopefully last phone I will deal with that has a locked bootloader.
Thanks for posting. Should we also be flashing a .pit file along with the full wipe rar?
DTCsk8er said:
Thanks for posting. Should we also be flashing a .pit file along with the full wipe rar?
Click to expand...
Click to collapse
no the .pit file is already in the .tar
Keep Root?
muniz_ri said:
I545VRUFNG6_Full_Wipe.rar
This is an "All-in-One" file, extract the .tar and flash in PDA Slot in Odin(AP in Odin v3.09+).
Click to expand...
Click to collapse
If I use this file to update my rooted NC5 will I keep Root? If not, what is the best procedure to use to Root after install? Does this fix the SD-Card write concern with Kit Kat?
Thank you,
Rodger
Root
rbird2 said:
If I use this file to update my rooted NC5 will I keep Root? If not, what is the best procedure to use to Root after install? Does this fix the SD-Card write concern with Kit Kat?
Thank you,
Rodger
Click to expand...
Click to collapse
Here you go buddy
http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-root-i545vrufng6-t2905848
My wife's GS4 hasn't been able to update with the NG6 update (hers is stock). Can I use this to update her GS4 to NG6 via Odin?
She's been having some issues with her phone and I was hoping the update would fix them.
Not working
I can't get this to work. It keeps failing. I don't know what to do. I followed the link to download ODIN that was provided, and i loaded the file using the AP button for PDA files. This is the log that keeps repeating:
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> system.img.ext4
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Would you mind providing an MD5? I have ran this twice and it hasn't wiped the phone at all.
otakudeter said:
I can't get this to work. It keeps failing. I don't know what to do. I followed the link to download ODIN that was provided, and i loaded the file using the AP button for PDA files. This is the log that keeps repeating:
...
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
What's being displayed on your phone when the write fails? That often has info that's useful for diagnosis.
---------- Post added at 09:35 AM ---------- Previous post was at 09:33 AM ----------
Metroba said:
Would you mind providing an MD5? I have ran this twice and it hasn't wiped the phone at all.
Click to expand...
Click to collapse
The download already has the ZIP integrity check (which isn't the greatest) and a MD5 sum on the .tar file, so your download is OK.
To fully wipe, you need to use the PIT file for your phone (if you flash using the 16gb PIT on a 32gb phone, you'll lose 16gb!)
I got this flashed on my wife's GS4. I noticed a few things.
1. It didn't do a full wipe as all her apps and data are still on the phone.
2. Now when rebooting, at the Samsung screen it shows the unlocked lock and says "Custom" like my MDK Loki'd GS4. What is that and what does it mean on her's?
3. After updating via this method, I still get a Verizon Updater update available.
Help is appreciated.
The file has been downloaded 385 times. Strange that issues are just now appearing. I would be interested in hearing a few others chime in before considering taking it down.
muniz_ri said:
The file has been downloaded 385 times. Strange that issues are just now appearing. I would be interested in hearing a few others chime in before considering taking it down.
Click to expand...
Click to collapse
It worked fine for me. I just had the few questions I posted above.
Do you happen to have the NC5 file so I can Odin back to it to get SS installed?
I did the full wipe with the PIT and use the AP section to flash this.
Upon reboot I get a "Unfortunately, the process com.android.phone has stopped".
Any help would be great.
Edited. Hangouts SMS issue was in using Hangouts as the SMS gateway. Reset the contact properly and could send via cell radios. Never mind. NC5 working great.
muniz_ri said:
The file has been downloaded 385 times. Strange that issues are just now appearing. I would be interested in hearing a few others chime in before considering taking it down.
Click to expand...
Click to collapse
Im sure your zip is valid, but here's mine just for comparison, md5's should be the same.
Full-Wipe NG6
No-Wipe NG6
Trouble with No-Wipe.tar
The initial state of my phone was a failed Hyperdrive rls 20 kk install (forgot the kernel modules for Safestrap) on top of rooted stock vrufng6.
I downloaded No-Wipe.tar with Free Download Manager and flashed in Odin 3.10 with a PASS.
Then the phone rebooted into recovery briefly, then exited recovery mode and booted normally...until I got a persistent message:
"Unfortunately, the process android.process.media has stopped"
It would not go away, blocking the screen, and seemed to interfere with the phone activation which would not finish.
Also, I could not hard reset the phone; pressing up volume and power and home put it in a temporary recovery mode that would hang with a black screen until I let go of the buttons-and then the phone went back to normal boot and the dreaded message.
I tried flashing the file a second time and the same thing happened.
Going to try the Full-Wipe and hope it works .
---------- Post added at 01:28 AM ---------- Previous post was at 01:08 AM ----------
Original state of phone was PASS attempt to flash No-Wipe.tar followed by issue below.
Full-Wipe.tar has the exact same issue (downloaded with just Chrome browser this time). Flashes in Odin with PASS, com.android.phone has stopped and the message blocks out the screen (I can spam "ok" and get to the poweroff/airplane mode/restart menu for like 1 second at a time). But I still can't access recovery mode. Is anyone else getting these issues, or should I try to flash some other version of the stock verizon rom on my phone?
N00bFighting! said:
The initial state of my phone was a failed Hyperdrive rls 20 kk install (forgot the kernel modules for Safestrap) on top of rooted stock vrufng6.
I downloaded No-Wipe.tar with Free Download Manager and flashed in Odin 3.10 with a PASS.
Then the phone rebooted into recovery briefly, then exited recovery mode and booted normally...until I got a persistent message:
"Unfortunately, the process android.process.media has stopped"
It would not go away, blocking the screen, and seemed to interfere with the phone activation which would not finish.
Also, I could not hard reset the phone; pressing up volume and power and home put it in a temporary recovery mode that would hang with a black screen until I let go of the buttons-and then the phone went back to normal boot and the dreaded message.
I tried flashing the file a second time and the same thing happened.
Going to try the Full-Wipe and hope it works .
Click to expand...
Click to collapse
---------- Post added at 02:17 AM ---------- Previous post was at 01:28 AM ----------
fireattack7 said:
I did the full wipe with the PIT and use the AP section to flash this.
Upon reboot I get a "Unfortunately, the process com.android.phone has stopped".
Any help would be great.
Click to expand...
Click to collapse
I had that problem with both .tar files after multiple flashes and finally hard reset the phone (after flashing to stock unrooted NC5 which STILL HAD THE MESSAGE) since I was desperate (by spamming ok to the message and getting to the hardware power menu eventually between its reappearing, holding down volume up & home & power, then letting go of power until the dead android appeared and then letting all buttons go). Then I reflashed to No-Wipe.tar NG6 in this forum. Somehow the error message is gone (no idea why). From there you could go through the setup menu (the one you get when you buy the phone for the first time), check OTA so that towelroot v3 works properly, flash NC5 kernel, root, flash modified NG6 kernel, install busybox, install safestrap, rom w Safestrap, etc. Just don't do what I did and forget to add kernel modules to rom when you use Safestrap. That results in a rom with no wifi, no safestrap, that has to be completely reflashed with NG6 (or NC5, factory reset, then NG6, then OTA, etc. if you get that error message) all over again T_T.
This is the stock firmware, right? (sorry if this is obvious, I just want to double check)
Thanks
Hey everyone,
I'm brand new at this, so please forgive me. Yesterday I followed directions to root after a security update at http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-root-i545vrufng6-t2905848 and, with only a few bumps, managed to get my device rooted and back up to speed on vrufng6. After having some trouble getting my build to go into permissive mode, I managed to get a safestrap partition installed and a backup put in place - things seemed to be running fine and dandy.
This morning I tried to install an unsupported version of cyanogenmod (I blame their site, they said that the verizon build had been included in an all-in-one version) and found that it was non-functional. No troubles though, I had a backup! Right? Wrong. As far as I can tell I accidentally saved the backup to the externalSD card and managed to do something to make it inaccessible -- safestrap says it can't load and finds no system information. Odin (which I used heavily in the initial downgrade-upgrade shuffle to reinstate root access) won't load the full recovery image provided in the original thread or any of the stock roms out on the internet.
So I've been trying to use the push update feature found in recovery mode (using adb, running windows 8.1 command prompt) and once it uploads I get an error message on the phone, and am back where I started from. I should mention that it doesn't seem like we S IV users have a fastboot option.
Is there a way to fix this? I can **sometimes** get into safestrap, but most times my options are download mode and recovery mode (letting it try to boot normally just hangs the device at Galaxy S 4 screen for awhile before a reboot.) When I do get through safestrap I can find my recovery image, but it won't mount, and the restart option warns me that I have no OS installed.
Again, I'm sorry if I'm not offering enough information. If anyone knows how to get this thing back to stock I would really appreciate a point in the right direction.
Can't you just use Kies to flash the stock firmware? That's what I did when I wound up with a non working os. I coudn't even load the os. Try Kies first.
backsidesmack said:
Can't you just use Kies to flash the stock firmware? That's what I did when I wound up with a non working os. I coudn't even load the os. Try Kies first.
Click to expand...
Click to collapse
backsidesmack -- Thanks for the response. I did try Kies, but might not have given it a fair shake. It won't find my device by its own volition, and when I enter the (correct) model and serial numbers for an emergency recovery it won't accept the input. I've tried each of the options under the tool menu, but it can't find my phone. Is there some secret to getting it to cooperate?
If you can get into download mode then flash the full wipe of this. http://forum.xda-developers.com/showthread.php?t=2735172 Don't forget this will WIPE all your data.
michaely123 said:
If you can get into download mode then flash the full wipe of this. http://forum.xda-developers.com/showthread.php?t=2735172 Don't forget this will WIPE all your data.
Click to expand...
Click to collapse
Hey this is DylanDeValera: in 3 hours I managed to lose my login credentials.
Just tried it with odin 3.09 -- here's the failure log:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Any pointers? Also didn't take it through adb sideload..
michaely123 said:
If you can get into download mode then flash the full wipe of this. http://forum.xda-developers.com/showthread.php?t=2735172 Don't forget this will WIPE all your data.
Click to expand...
Click to collapse
Just tried it with odin 3.09 -- here's the failure log:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Any pointers? I couldn't get it to work through sideload either; same error as before.
It's also probably time to confess that I'm running a windows 8.1 vm on a mac, to do all of this, but I managed to flash to a downgraded kernel and back up with the same setup.
going back to Kies, emergency firmware recovery won't show any options. How do you generate a recovery code?
Quick question. Which version of SafeStrap did you download and install?
ErisDev said:
Quick question. Which version of SafeStrap did you download and install?
Click to expand...
Click to collapse
3.75, which I believe added a button that would attempt to set enforcing mode to passive (instead of using terminal emulator for the same purpose).
I don't think it was any fault of its own - the latest verizon update removed the exploit that towelroot uses and also seemed to do something to disable setenforce 0, so I had to downgrade the firmware using the method posted above to get it to work. The safestrap boot also seemed to work fine, and claimed to successfully restore the backup I had made when I tested it.
DylanDevalera said:
3.75, which I believe added a button that would attempt to set enforcing mode to passive (instead of using terminal emulator for the same purpose).
I don't think it was any fault of its own - the latest verizon update removed the exploit that towelroot uses and also seemed to do something to disable setenforce 0, so I had to downgrade the firmware using the method posted above to get it to work. The safestrap boot also seemed to work fine, and claimed to successfully restore the backup I had made when I tested it.
Click to expand...
Click to collapse
You can only flash Cynanogenmod or any pure AOSP rom if you are on MDK, which you are not. Being on NG6, your only options for rom's are going to be Touchwiz based as we can't flash any kind of kernal. Having said that, you're only option now is going to be the NC5 full wipe Odin tar that is in the thread found here http://forum.xda-developers.com/showthread.php?t=2735172. It seems as if you've had problems flashing in Odin, I just returned my phone to NC5 stock this past weekend using the full wipe files found in the link so your issue, assuming you got good downloads, is either hardware (USB cable, port on p.c., port on phone) or you should try a different version of Odin. I used 3.10 and always have and it has always worked like a charm.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
DylanDevalera said:
As far as I can tell I accidentally saved the backup to the externalSD card
Click to expand...
Click to collapse
Why would you not save the backup to your external SD card?
ETA: Were you using Kies for Windows or Mac?
Seems to be some extra work needs to be done to use a VM:
Samsung Rooting with Odin / VirtualBox / OSX Lion
Using Odin in Mac OSX with Windows as VirtualBox's Guest OS
Hope you don't have a brick.
Tromatic said:
Why would you not save the backup to your external SD card?
ETA: Were you using Kies for Windows or Mac?
Seems to be some extra work needs to be done to use a VM:
Samsung Rooting with Odin / VirtualBox / OSX Lion
Using Odin in Mac OSX with Windows as VirtualBox's Guest OS
Hope you don't have a brick.
Click to expand...
Click to collapse
Yeah, the external backup comment was dumb on my part, I was misinterpreting safestrap's recovery methods. I think the trouble came from using an older version that ng6 was outsmarting.
Thanks for all the info on extra VM work. It did end up working without any extra help: turned out it was just an outdated version of odin, so the VM was functioning fine. It's always the most trivial things. I'm using parallels desktop FWIW. Kies was by way of mac.
liljoe727 said:
assuming you got good downloads, is either hardware (USB cable, port on p.c., port on phone) or you should try a different version of Odin. I used 3.10 and always have and it has always worked like a charm.
Click to expand...
Click to collapse
HOLY CRAP THANK YOU!! I was running 3.09, odin 3.10 fixed it on the first try. You.. If I could buy you a beer or something.. Thanks, really. to a layman it's always the most trivial little details.
Thanks again, you saved my phone.