I installed Ubuntu Touch and as it says on their wiki page, there are known issues like device fails to boot after rebooting, and I'm stuck at this point.
When I boot i get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when trying to turn it off by holding on the power button for 5-10seconds it turns black for a few seconds and comes right back to the samsung boot screen.
They do say how to fix this in the wiki, but I got no idea how I can get access to those files and modify them
I would have posted on their development thread, but as I don't have 10 posts, I can't do that.
jeggy said:
I installed Ubuntu Touch and as it says on their wiki page, there are known issues like device fails to boot after rebooting, and I'm stuck at this point.
When I boot i get this:
and when trying to turn it off by holding on the power button for 5-10seconds it turns black for a few seconds and comes right back to the samsung boot screen.
They do say how to fix this in the wiki, but I got no idea how I can get access to those files and modify them
I would have posted on their development thread, but as I don't have 10 posts, I can't do that.
Click to expand...
Click to collapse
although i haven't tried ubuntu touch still you can try going into download mode by holding power button and volume down button both together and flash stock rom or
try going into recovery mode and restore cwm or twrp backup which you must have made
HIT THANKS IF IT HELPED
Jaspreet.master7 said:
although i haven't tried ubuntu touch still you can try going into download mode by holding power button and volume down button both together and flash stock rom or
try going into recovery mode and restore cwm or twrp backup which you must have made
HIT THANKS IF IT HELPED
Click to expand...
Click to collapse
yeah, i was thinking that, but I don't know how to? The only thing I have access to is "Download Mode", so I have been trying to find a way to install a new ROM from odin, but with no luck. I'm still a beginner to these stuff, so if you could show me a way to use twrp or cwm to install a new rom that would be great I used twrp to install Ubuntu Touch, but I needed access to Android to install twrp.
I didn't do a real backup before, but I saved all the important data online. I just want to make fresh install of Android, don't care if it's the original from Samsung or some custom rom
jeggy said:
yeah, i was thinking that, but I don't know how to? The only thing I have access to is "Download Mode", so I have been trying to find a way to install a new ROM from odin, but with no luck. I'm still a beginner to these stuff, so if you could show me a way to use twrp or cwm to install a new rom that would be great I used twrp to install Ubuntu Touch, but I needed access to Android to install twrp.
I didn't do a real backup before, but I saved all the important data online. I just want to make fresh install of Android, don't care if it's the original from Samsung or some custom rom
Click to expand...
Click to collapse
if you have access to DOWNLOAD MODE then
download stock rom from sammobile
unzip the file and then u will obtain md5 file
now use odin3 dont check anything in it
select pda and open the md5 fie
wait till it checks the file
go to download mode and plug via usb and flash
if you get a bootloop keep holding ppower and volume up button for recovery mode
wipe data and cache rebbot
Jaspreet.master7 said:
if you have access to DOWNLOAD MODE then
download stock rom from sammobile
unzip the file and then u will obtain md5 file
now use odin3 dont check anything in it
select pda and open the md5 fie
wait till it checks the file
go to download mode and plug via usb and flash
if you get a bootloop keep holding ppower and volume up button for recovery mode
wipe data and cache rebbot
Click to expand...
Click to collapse
It's stuck at
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XWALI4_N8010O2UALI1_HOME.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> system.img
<ID:0/004> NAND Write Start!!
Jaspreet.master7 said:
if you have access to DOWNLOAD MODE then
download stock rom from sammobile
unzip the file and then u will obtain md5 file
now use odin3 dont check anything in it
select pda and open the md5 fie
wait till it checks the file
go to download mode and plug via usb and flash
if you get a bootloop keep holding ppower and volume up button for recovery mode
wipe data and cache rebbot
Click to expand...
Click to collapse
Hi, I have same problem My Samsung Galaxy Note 10.1 stuck at opening logo as well, further i can't able to detect my Note in ODIN(or my Laptop is not detecting any USB, even after connecting Note) , then how can i install and perform these steps. Thanks in Advance
jeggy said:
It's stuck at
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XWALI4_N8010O2UALI1_HOME.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> system.img
<ID:0/004> NAND Write Start!!
Click to expand...
Click to collapse
OK
CAN U PLZ TELL ME WHAT VERSION OF ANDROID DID YOUR TABLET HAVE BEFORE INSTALLING UBUNTU
WAS IT JB OR ICS
IF IT WAS ICS THEN U CAN TRY AND USE THE ODIN PROVIDED IN THE ATTACHMENTS
IF THAT DOES NOT HELP
YOU ARE INSTALLING UNITED KINGDOM ROM , REGION CODE O2U [ CORRECT ME ]
Try downloading the united kingdom rom REGION CODE: BTU
The latest is JB
And flash again and report
AND ALSO WHEN IN THE PREVIOUS POST I MENTIONED DON'T CHECK ANYTHING
I MEANT JUST OPEN ODIN SELECT PDA AND FLASH
Jaspreet.master7 said:
OK
CAN U PLZ TELL ME WHAT VERSION OF ANDROID DID YOUR TABLET HAVE BEFORE INSTALLING UBUNTU
WAS IT JB OR ICS
IF IT WAS ICS THEN U CAN TRY AND USE THE ODIN PROVIDED IN THE ATTACHMENTS
IF THAT DOES NOT HELP
YOU ARE INSTALLING UNITED KINGDOM ROM , REGION CODE O2U [ CORRECT ME ]
Try downloading the united kingdom rom REGION CODE: BTU
The latest is JB
And flash again and report
AND ALSO WHEN IN THE PREVIOUS POST I MENTIONED DON'T CHECK ANYTHING
I MEANT JUST OPEN ODIN SELECT PDA AND FLASH
Click to expand...
Click to collapse
I had Android 4.1.2 Jelly Bean, and the only reason I installed UK was becuase I'm from Faroe Islands, and it's not listed there, it could be the danish one, but that wasn't listed either, so I have no idea which one to choose. And this file doesn't exist anymore :/ http://www.sammobile.com/firmwares/3/?download=20586 so what should i try?
jeggy said:
I had Android 4.1.2 Jelly Bean, and the only reason I installed UK was becuase I'm from Faroe Islands, and it's not listed there, it could be the danish one, but that wasn't listed either, so I have no idea which one to choose. And this file doesn't exist anymore :/ http://www.sammobile.com/firmwares/3/?download=20586 so what should i try?
Click to expand...
Click to collapse
ok so u had Jb BEFORE
use this link http://samsung-updates.com/details/21145/Galaxy_Note_10.1_WiFi/GT-N8010/BTU/N8010XXUCMG1.html
its the same file u r trying to download only diff website
hope this will solve ur problem
Jaspreet.master7 said:
ok so u had Jb BEFORE
use this link http://samsung-updates.com/details/21145/Galaxy_Note_10.1_WiFi/GT-N8010/BTU/N8010XXUCMG1.html
its the same file u r trying to download only diff website
hope this will solve ur problem
Click to expand...
Click to collapse
It's stuck at NAND Write Start!! again, could it be the version of Odin that im running? I see there are thousands of thousands of versions of Odin out there
jeggy said:
It's stuck at NAND Write Start!! again, could it be the version of Odin that im running? I see there are thousands of thousands of versions of Odin out there
Click to expand...
Click to collapse
try to use the odin i provided
Hi! Try this video:
http://www.youtube.com/watch?feature=player_detailpage&v=_PSt8b5D2dM#t=322
Also, have you installed the samsung USB drivers?
Jaspreet.master7 said:
try to use the odin i provided
Click to expand...
Click to collapse
Hi,
Did you try to use ADB to find out whether your tablet can communicate with Odin??
Try this command:
adb devices
And reply with the output.
About the Jelly bean firmware, may be you can use other countries ( e.g. Dutch or German ) which is available for your device??
By the way, which recovery do you have and can you get into it??
rtunru said:
Hi,
Did you try to use ADB to find out whether your tablet can communicate with Odin??
Try this command:
adb devices
And reply with the output.
About the Jelly bean firmware, may be you can use other countries ( e.g. Dutch or German ) which is available for your device??
By the way, which recovery do you have and can you get into it??
Click to expand...
Click to collapse
I ran that, and i got an empty list, I tried while it's in download mode and while it's turned off:
Code:
C:\Users\Jeggy\cminstaller\bundle\win32>adb.exe devices
List of devices attached
And yes I have Samsung USB Drivers installed. But I don't think my device is working anymore, I'm not getting the samsung boot screen anymore, the absolutely only thing I have access to now is download mode. I uploaded a video to youtube showing how it looks now:
http://www.youtube.com/watch?v=ZgtZPHjoudw
Or do you guys still have hope for me, as I still have access to download mode?
jeggy said:
I ran that, and i got an empty list, I tried while it's in download mode and while it's turned off:
Code:
C:\Users\Jeggy\cminstaller\bundle\win32>adb.exe devices
List of devices attached
And yes I have Samsung USB Drivers installed. But I don't think my device is working anymore, I'm not getting the samsung boot screen anymore, the absolutely only thing I have access to now is download mode. I uploaded a video to youtube showing how it looks now:
http://www.youtube.com/watch?v=ZgtZPHjoudw
Or do you guys still have hope for me, as I still have access to download mode?
Click to expand...
Click to collapse
First of all, do not panic.
You still have the download mode
Second, the problem is clear, your adb driver is not installed properly. Solve this and then use ODIN to flash a stock firmware for your device.
By the way what is your device?? N8010??
rtunru said:
First of all, do not panic.
You still have the download mode
Second, the problem is clear, your adb driver is not installed properly. Solve this and then use ODIN to flash a stock firmware for your device.
By the way what is your device?? N8010??
Click to expand...
Click to collapse
yes I have N8010. Could you list all the things I should have installed, so maybe I can try on another computer?
jeggy said:
yes I have N8010. Could you list all the things I should have installed, so maybe I can try on another computer?
Click to expand...
Click to collapse
OK, I also have N8010
I think you did not do the steps at the right moments.
First of all we need to fix the ADB issue.
Therefore you need to do the following:
1. Put your your N8010 in download mode and start your ODIN
2.Connect the USB cable to your PC then to your tablet.
3.If the adb driver is not installed correctly, it will now.
4.Check your device manager for this.
5.If OK then
6. DO adb devices..Now you should get an output.
7.Check whether your ODIN also detects your tablet ( ID:com shows in color ).
8.Go back to Odin.
9.Flash your firmware with it.
10.If succeeded, your N8010 will come back to live
Good luck
rtunru said:
OK, I also have N8010
I think you did not do the steps at the right moments.
First of all we need to fix the ADB issue.
Therefore you need to do the following:
1. Put your your N8010 in download mode and start your ODIN
2.Connect the USB cable to your PC then to your tablet.
3.If the adb driver is not installed correctly, it will now.
4.Check your device manager for this.
5.If OK then
6. DO adb devices..Now you should get an output.
7.Check whether your ODIN also detects your tablet ( ID:com shows in color ).
8.Go back to Odin.
9.Flash your firmware with it.
10.If succeeded, your N8010 will come back to live
Good luck
Click to expand...
Click to collapse
That one which is selected gets there when connecting to the pc, and when removing the usb it gets removed, and the other that is unknown I got no idea what it is, probably just some random driver I'm missing, I installed Windows 8 myself.
Even with the "Samsung Mobile USB" driver in the device manager I get an empty list when running adb devices
I just tested running adb devices with my phone and it worked right away:
Code:
C:\Users\Jeggy>adb devices
List of devices attached
47901ea687d530a8 device
And this is while having my tablet connected
EDIT
and when it said "NAND Write Start!!" it did change something on the tablet itself, I got a blue loading bar(The same one as when rooting but this time not moving) under "Do not turn off target!!" but it started at 100% and never changed
jeggy said:
I just tested running adb devices with my phone and it worked right away:
Code:
C:\Users\Jeggy>adb devices
List of devices attached
47901ea687d530a8 device
And this is while having my tablet connected
Click to expand...
Click to collapse
This means that your PC and tablet are connected and the ADB driver is installed correctly.
At this point you must see the comm:id field ofOIDIN changes color.
At this point you can choose your firmware and then click on start.
EDIT
and when it said "NAND Write Start!!" it did change something on the tablet itself, I got a blue loading bar(The same one as when rooting but this time not moving) under "Do not turn off target!!" but it started at 100% and never changed
Click to expand...
Click to collapse
Are you sure you are using a total package firmware and NOT the one with 3 packages??
In the latter case you need to fill PDA, modem and CSC in ODIN
rtunru said:
This means that your PC and tablet are connected and the ADB driver is installed correctly.
At this point you must see the comm:id field ofOIDIN changes color.
At this point you can choose your firmware and then click on start.
Are you sure you are using a total package firmware and NOT the one with 3 packages??
In the latter case you need to fill PDA, modem and CSC in ODIN
Click to expand...
Click to collapse
It does change color and get "0:[COM4]", and I don't know which 3 packages you are talking about, I am trying the one I got from samMobile which is a .tar.md5 file and is a 1.5GB file. I never tried CSC and don't know what it is and how to get one
http://khp.randompoop.net/uploads/AndroidHelp123.png
Related
Hey, complete noob but will try to give a concise post of what I've done and where I'm at now. I received an I727R second hand and I am trying to put seanzscreams Sky ICS rom on it but am constantly running in to problems. Here are some important details:
Phone: SGH-I727R
Android Version: 2.3.5 GB (stock rogers firmware)
Baseband: I727RUXKJ7
Kernel: 2.6.35.11
Unrooted
O/S: Windows 7 Ultimate x64
Phone was in USB debugging mode before I bricked it
Did *#7284# and switched from Modem to PDA
Plugged in phone first time ever to PC, drivers installed OK. Installed Kies from Canadian Samsung website, did not recognize phone. Uninstalled/Reinstalled Kies after using registry cleaner; no difference, still connection error (wouldn't troubleshoot too). Uninstalled Kies. Uninstalled samsung drivers, installed standalone samsung drivers (Samsung_USB_Driver_for_Mobile_Phones_v1_3_2200_0.exe). Reinstalled Kies still no difference. Uninstalled Kies and standalone drivers, used registry cleaner, plugged in phone and let drivers install from Windows update.
Next I figured I wanted to root my phone so I could install CWM, and custom ROMs.
Installed android sdk for windows; made sure I had adb drivers for my phone. Tried to use adb for zergRush exploit; exploit worked but when running the command "adb remount" adb wouldn't recognize device (does the phone need to be in download mode when doing this whole process? Never was it mentioned that it needed to be). Then tried to use Skyrocket Easy Root method from this thread (http://forum.xda-developers.com/showthread.php?t=1340710), plenty of errors but it resulted in my phone apparently being rooted. Tried installing ROM manager from market to then install CWM, said I had no permissions (phone isn't rooted).
Then after getting frustrated...
Tried grabbing Odin 1.8.5 and this recovery file for CWM (http://www.mediafire.com/?5xc7gjkrbwihajp) and tried to flash to phone. First attempt it got stuck at <ID:0/004> recovery.img, let it stay for about +15min, nothing. Phone bricked (Firmware upgrade encountered etc.; not able to get in to download mode). Next tried to reinstall stock rogers 2.3.5. Still nothing, hangs at <ID:0/004> SetupConnection... Tried multiple times to reboot phone and then load firmwares again, nothing. Latest error is this after trying the recovery image again <OSM> All threads completed. (succeed 0 / failed 1). Moving the phone to different USB ports on my laptop makes Odin not recognize the phone at all
I beg someone to help me unbrick this phone and to help me get the custom ICS debloated version running on it. I'm short of pulling all of my hair out from frustration
Thanks for taking the time to read this
Look at the Odin tar thread. Its a sticky in the development section. Flash the tar file to completely restore your device. And read read read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
cdshepherd said:
Look at the Odin tar thread. Its a sticky in the development section. Flash the tar file to completely restore your device. And read read read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
+1
how did you ever find that old thread, read the last part of my sig and go to the second link in my sig
EDIT: Nvm, I just saw vincom's post which directs me to the thread you were talking about. I've read that thread, and still can't flash to stock firmware.
Here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727RUXKJ7_I727RRWCKJ7_I727RUXKJ7_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
flum said:
If by Odin tar thread you mean this, http://forum.xda-developers.com/showthread.php?t=1566613, it's not a stickied thread. I tried flashing it anyways and it fails everytime I try. Thanks for the input though.
Click to expand...
Click to collapse
you must be blind, look at my sig
flum said:
If by Odin tar thread you mean this, http://forum.xda-developers.com/showthread.php?t=1566613, it's not a stickied thread. I tried flashing it anyways and it fails everytime I try. Thanks for the input though.
Click to expand...
Click to collapse
My goodness lol. Look in vincoms sig. Its obvious you jumped into this without doing your homework. Now your paying for it. Not trying to be rude but your not paying attention. Good luck and we are here if you still can't figure it out...luckily:thumbup:
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
vincom said:
you must be blind, look at my sig
Click to expand...
Click to collapse
Nah, read his post before I refreshed and saw yours directing me to the thread
Well?
stoopendis said:
Well?
Click to expand...
Click to collapse
He's not good at reading, it seems. Oh well that's what happens when you just start flashing away without research.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
stoopendis said:
Well?
Click to expand...
Click to collapse
I've followed vincom's directions exactly for reflashing the phone with a stock firmware and this is what I get:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727RUXKJ7_I727RRWCKJ7_I727RUXKJ7_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I tried his directions for reflashing the phone with a CWM recovery file to no avail:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> recovery.img
Odin is still running so I'm not sure what to do now
Sorry guys, I've just been frustrated with hitting so many problems right from the beginning after reading through numerous guides. I guess I did rush too fast in trying to upgrade it/fix it but now I face the result of it. Hopefully I can unbrick it and learn why it wouldn't flash. As for now though I feel like I'm at a dead end because Odin is still running and it seems that it won't write for whatever reason.
flum said:
Sorry guys, I've just been frustrated with hitting so many problems right from the beginning after reading through numerous guides. I guess I did rush too fast in trying to upgrade it/fix it but now I face the result of it. Hopefully I can unbrick it and learn why it wouldn't flash. As for now though I feel like I'm at a dead end because Odin is still running and it seems that it won't write for whatever reason.
Click to expand...
Click to collapse
did you read the whole sticky, theres a troubleshooting section for odin, basically
you have a problem with
1. drivers
2. usb cable
3. usb port
go through the troubleshooting section for odin, thats why i wrote it, but if newbs arent going to read it then why the frack did i write it.
Throwing this out there.
Set time out to 10 minutes
Enable usb debugging in settings
Enable download from unknown sources
Sent from my SAMSUNG-SGH-I727 using xda premium
When I've have Odin trouble sometimes this helped.
1. Uninstall kies if you have it installed, it will leave the drivers.
2. Try a different version of Odin and /or a different USB port
3. Try a different PC
If all else fails pm me
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
stoopendis said:
Throwing this out there.
Set time out to 10 minutes
Enable usb debugging in settings
Enable download from unknown sources
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I made sure all of that was checked before I bricked the phone. Phone is completely bricked, I cannot get in to download mode or even recovery mode. It goes straight to the screen with an image of the phone yellow warning triangle and computer with the text reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
cdshepherd said:
When I've have Odin trouble sometimes this helped.
1. Uninstall kies if you have it installed, it will leave the drivers.
2. Try a different version of Odin and /or a different USB port
3. Try a different PC
If all else fails pm me
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've already had Kies uninstalled before I started to actually try flashing things to the phone. I've downloaded Odin 1.8.3 and it won't recognize the phone at all. I've tried different USB ports but I get an error from Windows saying that the USB device has malfunctioned and both Windows and Odin cannot see the phone; the only way I can get my system to see the phone again is if I reboot the phone and plug it in before the error screen shows. I'm going to be doing a little more troubleshooting before I try it out with another computer which will likely be tomorrow. Thanks for all the replies so far guys I'm gonna try tinkering with the drivers but I'm worried about my system not being able to see the phone if I do. I have no access to another cable and the cable I am using is not the OEM cable that came with the phone so the problem might be that right there.
flum said:
I made sure all of that was checked before I bricked the phone. Phone is completely bricked, I cannot get in to download mode or even recovery mode. It goes straight to the screen with an image of the phone yellow warning triangle and computer with the text reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've already had Kies uninstalled before I started to actually try flashing things to the phone. I've downloaded Odin 1.8.3 and it won't recognize the phone at all. I've tried different USB ports but I get an error from Windows saying that the USB device has malfunctioned and both Windows and Odin cannot see the phone; the only way I can get my system to see the phone again is if I reboot the phone and plug it in before the error screen shows. I'm going to be doing a little more troubleshooting before I try it out with another computer which will likely be tomorrow. Thanks for all the replies so far guys I'm gonna try tinkering with the drivers but I'm worried about my system not being able to see the phone if I do. I have no access to another cable and the cable I am using is not the OEM cable that came with the phone so the problem might be that right there.
Click to expand...
Click to collapse
That screen with the triangle means it's still in download mode, man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
That screen with the triangle means it's still in download mode, man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
:thumbup:
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
your not bricked if u see the dl screen, your on the right track for troubleshooting, just take it slow as your phone is not dead, but go through my odin troubleshooting section in the 2nd link in my sig.
kies and adb should not be running in the background, and yes get a samsung usb cable to rule out cable issues
I think your whole problem was when you did this
"Did *#7284# and switched from Modem to pda"
Ive never had to do that with mine. Just put phone in download mode. Use odin and flash. Runnin windows 7 x64 found drivers by it self.
Sent from my SGH-I727R using xda app-developers app
enegizer07 said:
I think your whole problem was when you did this
"Did *#7284# and switched from Modem to pda"
Ive never had to do that with mine. Just put phone in download mode. Use odin and flash. Runnin windows 7 x64 found drivers by it self.
Sent from my SGH-I727R using xda app-developers app
Click to expand...
Click to collapse
he did get into dl mode, the problem is the computer wont see the phone
I have a Galaxy Tab 2 10.1 w/ JB 4.1.1 through AT&T that got screw up while rooting
I was following the guide here:
androidrooting.com/how-to-root-galaxy-tab-2-10-1-p5100/
I deviated from the guide in 1 way. When it says to select the '.zip' file, I assumed they meant the .md5, as .zip is not an option
When I hit start on Odin, Odin crashed. I loaded it up and tried it again. This time it 'failed'. My tablet rebooted to the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." So, I installed Kies on my computer and tried to do what it says. When the device is plugged in Kies tries to connect but comes back with the error "Device not responding. To fix the issue, reboot the device". I also tried using Odin again to continue where I left off, but it simply fails.
Any advice would be great. Please help, thanks!
tholt2121 said:
I have a Galaxy Tab 2 10.1 w/ JB 4.1.1 through AT&T that got screw up while rooting
I was following the guide here:
androidrooting.com/how-to-root-galaxy-tab-2-10-1-p5100/
I deviated from the guide in 1 way. When it says to select the '.zip' file, I assumed they meant the .md5, as .zip is not an option
When I hit start on Odin, Odin crashed. I loaded it up and tried it again. This time it 'failed'. My tablet rebooted to the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." So, I installed Kies on my computer and tried to do what it says. When the device is plugged in Kies tries to connect but comes back with the error "Device not responding. To fix the issue, reboot the device". I also tried using Odin again to continue where I left off, but it simply fails.
Any advice would be great. Please help, thanks!
Click to expand...
Click to collapse
I should also note that the upper right corner of the tablet says:
"ODIN MODE
PRODUCT NAME: ESPRESSO10
CUSTOM BINARY DOWNLOAD: YES (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Unsupport devtype"
tholt2121 said:
I have a Galaxy Tab 2 10.1 w/ JB 4.1.1 through AT&T that got screw up while rooting
I was following the guide here:
androidrooting.com/how-to-root-galaxy-tab-2-10-1-p5100/
I deviated from the guide in 1 way. When it says to select the '.zip' file, I assumed they meant the .md5, as .zip is not an option
When I hit start on Odin, Odin crashed. I loaded it up and tried it again. This time it 'failed'. My tablet rebooted to the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." So, I installed Kies on my computer and tried to do what it says. When the device is plugged in Kies tries to connect but comes back with the error "Device not responding. To fix the issue, reboot the device". I also tried using Odin again to continue where I left off, but it simply fails.
Any advice would be great. Please help, thanks!
Click to expand...
Click to collapse
Strange, because it should work. You didn't need to select the .zip file indeed, choosing the .md5 file was the right choice. Have you tried running Odin as an administrator?
Endiej said:
Strange, because it should work. You didn't need to select the .zip file indeed, choosing the .md5 file was the right choice. Have you tried running Odin as an administrator?
Click to expand...
Click to collapse
I have not - how would I go about doing that?
tholt2121 said:
I have not - how would I go about doing that?
Click to expand...
Click to collapse
Just right click on the Odin setup file (the .exe file) and select 'Run as an administrator'. Always run as an administrator when doing something in Odin.
Try running as admin for sure. Even though my windows account is admin, odin will not flash properly. I have to run as admin for it to flash.
Sent from a rooted candy bar
Zagnutty said:
Try running as admin for sure. Even though my windows account is admin, odin will not flash properly. I have to run as admin for it to flash.
Sent from a rooted candy bar
Click to expand...
Click to collapse
I tried it running as administrator. It still didn't work. Here is the log from Odin:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sooo.. any other thoughts on this?
I also tried using the .md5 file from this guide:
http://forum.xda-developers.com/showthread.php?t=2158914
Does the fact this is the AT&T version of the tablet make any difference
Yes the reason it isn't working may be that it was not written for the ATT Tab 2. Never try to install anything like this not written for your tablet or phone. Close does not count.
Try this proven method instead:
http://forum.xda-developers.com/showthread.php?t=2342501
Agoattamer said:
Yes the reason it isn't working may be that it was not written for the ATT Tab 2. Never try to install anything like this not written for your tablet or phone. Close does not count.
Try this proven method instead:
http://forum.xda-developers.com/showthread.php?t=2342501
Click to expand...
Click to collapse
Yes!! Thank you so much! That fixed my tablet [and rooted it]. You are amazing. It didn't strike me that my tablet had any different version.. thanks!! Now to figure out what to do with this root access...
Pay close attention. There are no ROMs on XDA for the ATT I497 Tab2. Do not attempt to install a ROM for another version of our Tab.
I'm trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=1705260
But the instructions don't work for me. The only way I can make Odin detect my phone is if I start the phone normally (no usb debug, no download mode), connect the usb cable, and when prompted on my phone, select 'firmware update (kies)'.
Then the box on Odin goes yellow as OP says, and it's writen 0:[COM3]
Is that correct? Can I go ahead with rooting like this? I'm going to be installing Beansprout.
Edit:
I tried it anyway, and it failed (0 success 1 fail)
How can I get it to be detected in download mode then?
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
Y.June said:
I'm trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=1705260
But the instructions don't work for me. The only way I can make Odin detect my phone is if I start the phone normally (no usb debug, no download mode), connect the usb cable, and when prompted on my phone, select 'firmware update (kies)'.
Then the box on Odin goes yellow as OP says, and it's writen 0:[COM3]
Is that correct? Can I go ahead with rooting like this? I'm going to be installing Beansprout.
Edit:
I tried it anyway, and it failed (0 success 1 fail)
How can I get it to be detected in download mode then?
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Hey there,
I am assuming you have no trouble getting into download mode, and Kies is not running at the time?
Kies didn't work for me when it came to appropriate drivers. I ended up using generic Android drivers for stuff like ADB and download mode. The drivers in this package may work for you:
http://forum.xda-developers.com/showthread.php?t=2588979
Hope this helps.
joel.maxuel said:
Hey there,
I am assuming you have no trouble getting into download mode, and Kies is not running at the time?
Kies didn't work for me when it came to appropriate drivers. I ended up using generic Android drivers for stuff like ADB and download mode. The drivers in this package may work for you:
http://forum.xda-developers.com/showthread.php?t=2588979
Hope this helps.
Click to expand...
Click to collapse
Unfortunately the new drivers didn't help, it's still not detected while in download mode, only when the phone is booted.
Yes, I can enter download mode (robot with a shovel).
When I first tried, Kies was running (didn't know it wasn't supposed to). I uninstalled to be sure it wouldn't run. When that didn't work I installed it again but made sure to close it before trying Odin.
Does it matter if usb debug is on or off? The OP doesn't say either way.
The phone is only detected in Kries firmware update mode (shows up as COM3) or Usb debug mode (shows up as COM4)
State of debug mode shouldn't matter, only matters for ADB (I think). But I would leave it on just in case.
I don't think the availability of COM ports makes any difference either.
Sorry, I am out of ideas for now.
Sent from my MyTouch 4G Slide using XDA Free mobile app
Code:
Beanstalk install instructions:
http://forum.xda-developers.com/showthread.php?t=2091900
Coming from Froyo(2.2) Gingerbread(2.3) or ICS(4.0)
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
So the idea is to get gingerbread on my phone (with Odin) and then use SGS kernel flasher to install CWM.
If I understood that right, I wonder if I can just use SuperOneClick to install gingerbread, then use the kernel flasher to install CWM.
I do have the kernel flasher on my froyo, but I guess it needs to be gingerbread.
Edit: well, scratch that, 2.3.3 superoneclick download not available :/
Edit: firmware 2.2 is froyo, right? I mean, it says that, and build number froyo, but my kernel version is 2.6.32.9
Alas, another edit! I could try installing jellybean (guide page 1, page 2) but again, that needs superoneclick for which there is no download available unless I'm mistaken.
Y.June said:
Code:
Beanstalk install instructions:
http://forum.xda-developers.com/showthread.php?t=2091900
Coming from Froyo(2.2) Gingerbread(2.3) or ICS(4.0)
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
So the idea is to get gingerbread on my phone (with Odin) and then use SGS kernel flasher to install CWM.
If I understood that right, I wonder if I can just use SuperOneClick to install gingerbread, then use the kernel flasher to install CWM.
I do have the kernel flasher on my froyo, but I guess it needs to be gingerbread.
Edit: well, scratch that, 2.3.3 superoneclick download not available :/
Edit: firmware 2.2 is froyo, right? I mean, it says that, and build number froyo, but my kernel version is 2.6.32.9
Alas, another edit! I could try installing jellybean (guide page 1, page 2) but again, that needs superoneclick for which there is no download available unless I'm mistaken.
Click to expand...
Click to collapse
2.2 is Froyo. Kernel Version 2.6.x has to do with the Linux counterpart, not much to be concerned about at this point.
My concern with SuperOneClick is that if something goes wrong, you will be unable to flash back to Froyo. Best to get Odin working in Download Mode first.
A quick search ("no odin in download mode") found this thread (on a different Samsung device):
http://forum.xda-developers.com/showthread.php?t=2561137
So your fix may involve a different version of Odin, a different USB cable (and as a note from some place else) you may want to make sure you are not using a USB 3.0 port (2.0 preferred), and connected straight from the motherboard (no hubs). This may not be a requirement for Odin, but I've seen the recommendation (and it's a requirement for certain HTC tasks).
Edit: ... argh... I did the install recommended to fix the rainbow screen and now the phone is bricked. No signs of life.
I guess it was too good to be true.
Don't do the bootloader he tells you to install to fix rainbow screen.
No download mode, no recovery mode. If I go into recovery mode it just gives me some red letters about RST_stat, IRQ, and some hexcodes (those 0x000 numbers)
Click to expand...
Click to collapse
Edit again! I fixed it! I was all ready to get a usb jig. When I tried to go to download mode nothing happened at all. But instead of plugging in the cable to the phone and then to the computer, I plugged it to the computer first and then the phone. It gave me download mode! I thought this was bricked for sure!
So I can't do emergency recovery mode from kries mini, it only gives the option from the 'firmware update' option you get when connecting the phone while it's booted in.
That means I need to do Odin again... I hope it works! This time I won't do the rainbox fix. I'll just deal with it. Rainbows are pretty anyway.
Click to expand...
Click to collapse
I got Odin to work and install! After uninstalling drivers and rebooting over and over, and installing the samsung driver that was in that link you posted.
Thanks!
This is what I was typing before I got it to work so I'll post it anyway. It might be helpful for someone:
I found a samsung.com link for installing gingerbread. I can't link on forums yet so just google this:
AT&T Cell Phones: How Do I Update My Infuse 4G (SGH-i997) Mobile Device to Android 2.3 (Gingerbread) Operating System?
Click to expand...
Click to collapse
I did try it,it was detected fine, and started installing after Kris Mini put the phone in download mode. But a bit after installing it failed. However, the website does have some more troubleshooting info that could help someone. The website does say kries 3 is not compatible with this model, you have to download kries mini.
Here's the troubleshooting info:
Basic Troubleshooting
General
If you are unable to download an install the Kies mini application you may need to disable all Firewall & Anti-Virus Programs.
Kies Mini Does Not Detect The Phone
Remove previously installed Samsung software and drivers. PC Studio, New PC Studio, or Kies can cause driver conflicts. Uninstall these applications/drivers and reinstall Kies mini.
Enable USB debugging mode before connect your device to the PC.
Close the Kies mini application.
On you device press Menu Menu >Settings > Applications > Development > USB debugging to place a checkmark.
Reopen the Kies mini application.
Reconnect your device to the PC.
You may have changed your default USB settings. To check your USB settings follow the instructions below.
Close the Kies mini application.
On you device press Menu Menu > Settings > Applications > USB settings.
Touch Kies (Firmware update).
Reopen the Kies mini application.
Reconnect your device to the PC.
Download or update Windows Media Player to the latest version. Click here for the Windows Media player update website.
Remove previously installed service provider applications (ACM, VMM, etc…). These applications may cause driver conflicts. Uninstall these applications and reinstall Kies mini.
Depending on the amount of data stored in the phone memory, this could impair Kies Mini's ability to detect the device. It may be necessary to remove the microSD card (Requirements). Should problems persist, the internal memory may need to be purged. Backup all desired data (using instructions provided above) and then go to Menu > Settings > Privacy > Factory Data Reset. Follow the onscreen instructions and after reboot, attempt to connect to Kies Mini.
The Media Scan process could produce a loop if connected while in progress. If this occurs, disconnect and power cycle the device. Wait until the device fully boots and the process is finished before connecting again.
When the handset goes into download mode instructed by Kies Mini, additional drivers need to be installed. A timeout may occur from the time the drivers install until Kies Mini can detect. Should this occur, close Kies Mini and remove the cable. Next, remove the battery cover and battery. Afterwards, insert the battery, place the cover back on, and power on the device. When the device reboots, connect the data cable and open Kies Mini.
Click to expand...
Click to collapse
Y.June said:
I got Odin to work and install! After uninstalling drivers and rebooting over and over, and installing the samsung driver that was in that link you posted.
Thanks!
Click to expand...
Click to collapse
Glad I could be of help. If the ADB/Driver package post was helpful, feel free to thank it.
Y.June said:
That means I need to do Odin again... I hope it works! This time I won't do the rainbox fix. I'll just deal with it. Rainbows are pretty anyway.
Click to expand...
Click to collapse
With regard to the rainbow bug, if I recall correctly the ROM's don't have that issue, so you may want to explore Cyanogenmod or Beanstalk (et cetera). I found CM 10.1 useful* (albeit with a few minor bugs), although it seems everyone has moved on to KitKat.
Just a thought. Gingerbread is a bit long in the tooth these days, but you may be set on sticking with stock for a while. (For the record, there is nothing wrong with the OS itself, it's that the app selection is starting to narrow.)
Good luck!
* I tried CM 10.2. I'm not sure if it was my phone (Rogers), or a bad download, but I could not finish the install and CWM was so borked I had to Odin back to stock and start over. I thus gave up on trying anything newer.
go up too CarbonRom latest nightly 4.4.2 KitKat https://carbonrom.org/downloads/?device=infuse4g&type=nightly its almost perfect
My phone appears to be in a bootloop as it is stuck on the Samsung Galaxy Note GT-N7000 Screen. I cannot access recovery mode, I can only access Downloading Mode. It started when I used Rom Manager to flash CWM to my device and do a backup. I have tried flashing a stock ROM to my device but ODIN (v3.9) gives me the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ORALT3_HOME.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And shows a FAIL at the top in red.
Does anyone have any suggestions? Any help would be much appreciated.
Thank you.
Update:
After searching around it appears I may need to use PIT file, is this the case and does anyone know where I would get one for my device?
ivel97 said:
My phone appears to be in a bootloop as it is stuck on the Samsung Galaxy Note GT-N7000 Screen. I cannot access recovery mode, I can only access Downloading Mode. It started when I used Rom Manager to flash CWM to my device and do a backup. I have tried flashing a stock ROM to my device but ODIN (v3.9) gives me the following error:
And shows a FAIL at the top in red.
Does anyone have any suggestions? Any help would be much appreciated.
Thank you.
Update:
After searching around it appears I may need to use PIT file, is this the case and does anyone know where I would get one for my device?
Click to expand...
Click to collapse
Sure HERE you can download ODIN 1.85 + PIT file. Make sure to choose the correct PIT size 16/32GB
ivel97 said:
My phone appears to be in a bootloop as it is stuck on the Samsung Galaxy Note GT-N7000 Screen. I cannot access recovery mode, I can only access Downloading Mode. It started when I used Rom Manager to flash CWM to my device and do a backup. I have tried flashing a stock ROM to my device but ODIN (v3.9) gives me the following error:
And shows a FAIL at the top in red.
Does anyone have any suggestions? Any help would be much appreciated.
Thank you.
Update:
After searching around it appears I may need to use PIT file, is this the case and does anyone know where I would get one for my device?
Click to expand...
Click to collapse
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
root-expert said:
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
Click to expand...
Click to collapse
Suggested ODIN version for GT-N7000 is 1.85 (as I linked it). Could also be related to a wrong version of ODIN.
Thanks for the suggestions. I have tried different versions of ODIN. I'll have a go with different USB cables.
root-expert said:
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
Click to expand...
Click to collapse
I don't have the original Samsung charging cable that came with my device. I looked online for some and found one that claims to work for all Note models, does that sound right?
root-expert said:
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
Click to expand...
Click to collapse
I bought a new cable for the Note, still getting the same error. Any suggestions?
ivel97 said:
I bought a new cable for the Note, still getting the same error. Any suggestions?
Click to expand...
Click to collapse
Kill all kies proccess and try again. Also enable usb debugging.
root-expert said:
Kill all kies proccess and try again. Also enable usb debugging.
Click to expand...
Click to collapse
I uninstalled keis (not the USB driver) and I can't enable USB debugging because the phone is in a boot loop.
Then make sure that you have installed the correct drivers. Also try to download odin from other sites.
root-expert said:
Then make sure that you have installed the correct drivers. Also try to download odin from other sites.
Click to expand...
Click to collapse
Tried both. Sorry.
I think I'll just give up and take it to a phone repair shop, see what they can do. :crying:
ivel97 said:
Tried both. Sorry.
I think I'll just give up and take it to a phone repair shop, see what they can do. :crying:
Click to expand...
Click to collapse
Remove your bettery and leave it for 5 minutes. Then go again to download mode and flash with odin. Also you can try defferent usb ports and ensure that you don't use a usb hub! Finally nesure that you are running odin as admin.
root-expert said:
Remove your bettery and leave it for 5 minutes. Then go again to download mode and flash with odin. Also you can try defferent usb ports and ensure that you don't use a usb hub! Finally nesure that you are running odin as admin.
Click to expand...
Click to collapse
ODIN got a little further this time. Still stuck on cache.img, though.
<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> SingleDownload.
<ID:0/006> cache.img
Click to expand...
Click to collapse
ivel97 said:
ODIN got a little further this time. Still stuck on cache.img, though.
Click to expand...
Click to collapse
Now you have to check that the file you have downloaded is correct. Maybe you can check the md5 checksum or something. Or simply redownload it. Which step fixed your issue?
root-expert said:
Now you have to check that the file you have downloaded is correct. Maybe you can check the md5 checksum or something. Or simply redownload it. Which step fixed your issue?
Click to expand...
Click to collapse
Changing USB port I think, maybe in conjunction with new cable because I've tried changing ports before. Also made sure I started in admin. Odin checks the md5 checksum automatically but I'm downloading it again. Got the stock firmware off sammobile.com . Using the UK Orange version - XXLT9. I think that is the right one from memory. Can't check build setting because I'm stuck in bootloop. Pain.
EDIT:
Damn. Just tried again with ODIN 1.85 and it gets stuck on setup connection again. Same with v3.09.
ivel97 said:
Changing USB port I think, maybe in conjunction with new cable because I've tried changing ports before. Also made sure I started in admin. Odin checks the md5 checksum automatically but I'm downloading it again. Got the stock firmware off sammobile.com . Using the UK Orange version - XXLT9. I think that is the right one from memory. Can't check build setting because I'm stuck in bootloop. Pain.
EDIT:
Damn. Just tried again with ODIN 1.85 and it gets stuck on setup connection again. Same with v3.09.
Click to expand...
Click to collapse
Do the same with the battery
root-expert said:
Do the same with the battery
Click to expand...
Click to collapse
Taking out the battery fixed the setup connection error. Thanks!!! Still failing on cache.img, though. Waiting for the stock Rom from sammobile.com to finish downloading and I'll try again.
root-expert said:
Do the same with the battery
Click to expand...
Click to collapse
Redownloaded the stock firmware from sammobile and tried again. Failing after cache.img.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ORALT3_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> cache.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ivel97 said:
Redownloaded the stock firmware from sammobile and tried again. Failing after cache.img.
Click to expand...
Click to collapse
Have you already try to flash .pit file. I recomend you don't because if odin fail to flash it your phone will f*** up. So this is your last resort. You can try different roms. You can try to use heimdall for windows to flash your firmware. Heimdall is more reliable
root-expert said:
Have you already try to flash .pit file. I recomend you don't because if odin fail to flash it your phone will f*** up. So this is your last resort. You can try different roms. You can try to use heimdall for windows to flash your firmware. Heimdall is more reliable
Click to expand...
Click to collapse
Not tried to flash .pit file. I'll try heimdall, thanks.
Hi
I downloaded the UK (live in Denmark) H3G version (same firmware number as my old one), added it in Odin (newest version) and flashed.
Just before finishing up, it failed. Waited 10-20 minutes and nothing happened (cause it told me to not turn off the device or unplug).
But well nothing happened, so I unplugged and restarted phone.
Now it's at a blue screen saying: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I then tried that, but it says my device is unsupported.
Do anyone have any idea what to do?
Thanks in advance
EDIT THE ERROR:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCV_G920FH3G1AOC1_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Faspaiso said:
Hi
I downloaded the UK (live in Denmark) H3G version (same firmware number as my old one), added it in Odin (newest version) and flashed.
Just before finishing up, it failed. Waited 10-20 minutes and nothing happened (cause it told me to not turn off the device or unplug).
But well nothing happened, so I unplugged and restarted phone.
Now it's at a blue screen saying: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I then tried that, but it says my device is unsupported.
Do anyone have any idea what to do?
Thanks in advance
EDIT THE ERROR:
Click to expand...
Click to collapse
Can you boot into download mode? press power on, volume down and home button. Then you download Samsung Kies 3 and go to "firmware upgrade and initialization", type model name "SM-G920F", then write your serial number which you can find on a sticker on back of your phone. If you can't boot into download mode its impossible to recover your phone.
Aircondition said:
Can you boot into download mode? press power on, volume down and home button. Then you download Samsung Kies 3 and go to "firmware upgrade and initialization", type model name "SM-G920F", then write your serial number which you can find on a sticker on back of your phone. If you can't boot into download mode its impossible to recover your phone.
Click to expand...
Click to collapse
Tried with Kies. It said my device is not supported and I should use Smart Switch. But was still able to continue with Kies. An error occured and Kies closed.
I then continued with Smart Switch and tried to do the same and this occured. Image not working when putting it in, so here the link is. http://prntscr.com/6vy161
I'm able to enter download mode, yes.
Faspaiso said:
Tried with Kies. It said my device is not supported and I should use Smart Switch. But was still able to continue with Kies. An error occured and Kies closed.
I then continued with Smart Switch and tried to do the same and this occured. Image not working when putting it in, so here the link is. http://prntscr.com/6vy161
I'm able to enter download mode, yes.
Click to expand...
Click to collapse
So you got to this screen and then when you plugged USB cable in it says "device is not supported"?
Also make sure you have Kies 3.0 and not earlier versions. My phone also got softbricked but you may have messed it up way more than me. Then your only option left is to flash stock rom with Odin 3.10.6, you will have to find right CSC version for your country from sammobile.com (15 kb/s download speed) or download faster with Kies client (it will save it to C:\Users\AppData\Local\Temp)
Aircondition said:
So you got to this screen and then when you plugged USB cable in it says "device is not supported"?
Also make sure you have Kies 3.0 and not earlier versions. My phone also got softbricked but you may have messed it up way more than me. Then your only option left is to flash stock rom with Odin 3.10.6, you will have to find right CSC version for your country from sammobile.com (15 kb/s download speed) or download faster with Kies client (it will save it to C:\Users\AppData\Local\Temp)
Click to expand...
Click to collapse
Thank you. It worked now.
I already got Kies 3.0 and I already tried to flash with Odin before. But well, I restarted my PC and suddenly, it worked just fine.
So thank you mate.
hello excuse English but I find myself in your same conditions and with no win 8.1 Riec it to start it in emergencies with kies it with smart switches, nor with odin pui tell me step how to solve I would be grateful
pippo74 said:
hello excuse English but I find myself in your same conditions and with no win 8.1 Riec it to start it in emergencies with kies it with smart switches, nor with odin pui tell me step how to solve I would be grateful
Click to expand...
Click to collapse
Just do what is wrote in the thread.
It worked just fine for me, after the restart on my PC, but I think it was because my network connection was going on and off, so it couldn't download the file.
I used Kies, but I think Smart Switch works just fine too.
Remember to use Kies 3.0 and put your phone into download mode.
a quick way to fix this is to flash twrp with odin...
enij said:
a quick way to fix this is to flash twrp with odin...
Click to expand...
Click to collapse
THANK YOU!!!
I know it's an old post but it saved me from going even more insane.
Flash this via odin.
http://www.sammobile.com/firmwares/download/49782/G920FXXU2BOFJ_G920FH3G2BOF1_H3G/
roydok said:
Flash this via odin.
http://www.sammobile.com/firmwares/download/49782/G920FXXU2BOFJ_G920FH3G2BOF1_H3G/
Click to expand...
Click to collapse
3 months too late, but you still get my thanks just for trying.
Help i cannot get smart switch or kies 3.0 to reconize device SM-g920f
My girlfriend S6 suffered a softbriked after a OTA update. I was about to return the phone and I was going to be a lot of problems. Thank you for saving me!!!!
Aircondition said:
So you got to this screen and then when you plugged USB cable in it says "device is not supported"?
Also make sure you have Kies 3.0 and not earlier versions. My phone also got softbricked but you may have messed it up way more than me. Then your only option left is to flash stock rom with Odin 3.10.6, you will have to find right CSC version for your country from sammobile.com (15 kb/s download speed) or download faster with Kies client (it will save it to C:\Users\AppData\Local\Temp)
Click to expand...
Click to collapse
Hi sorry to bother you but I have the same problem only mine happened when i tried to root my phone and failed, so I am now on the same blue screen as the other guy. I went onto Kies and did everything and it was working fine until it told me to put my phone into recovery mode, which I assume is download mode, and then it says start upgrade, but the box where it says this is gray and I cannot click on it. Any idea on what I can do?
ALL,
i have the same issue., i had a stock firmware and wanted another sotck firmware on the phone
the original firmware from sammobile failed via odin
i went through the smart switch pc software and it also failed near the end.
what can i do to fix the issue please.? need urgent help.
Somoeone earlier mentioned to install TWRP via odin to fix the issue, is this correct? will this trip knox when installed TWRP?
PLEASE ADVISE.
Yes it will... download the newest firmware in sammobile of your model (doesnt metter the country) and flash. Or post here the logs of odin of failing flash
lummujaj said:
Yes it will... download the newest firmware in sammobile of your model (doesnt metter the country) and flash. Or post here the logs of odin of failing flash
Click to expand...
Click to collapse
Im trying to download this version of the firmware G920FXXU1AOCV_G920FTEF1AO.zip but the download fails before it can download onto my computer for use in odin, how do i make the download work?
i have a solution my friend . just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
have a lot of fun with your phone !
Faspaiso said:
Hi
I downloaded the UK (live in Denmark) H3G version (same firmware number as my old one), added it in Odin (newest version) and flashed.
Just before finishing up, it failed. Waited 10-20 minutes and nothing happened (cause it told me to not turn off the device or unplug).
But well nothing happened, so I unplugged and restarted phone.
Now it's at a blue screen saying: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I then tried that, but it says my device is unsupported.
Do anyone have any idea what to do?
Thanks in advance
EDIT THE ERROR:
Click to expand...
Click to collapse
I know that you already fixed your issue, but this is just for those who may run into your same issue again in the future.
I just had this issue, and spent hours trying to figure out what to do. I was reading the app (Smart Switch), and one of the steps it gives you is that you can download Smart Switch to another computer, write down the recovery code that it gives you when you get that error, plug that recovery code in the app on the other computer, and then try the download again. Worked like a charm for me. Even though, I didn't read the app at first, and it took me 3 hours to finally figure it out (duh). So far, my phone is up and running like normal. Maybe that will help someone for next time.
Device ID - IMEI - S/N -MAC; in Google Playstore.
Aircondition said:
Can you boot into download mode? press power on, volume down and home button. Then you download Samsung Kies 3 and go to "firmware upgrade and initialization", type model name "SM-G920F", then write your serial number which you can find on a sticker on back of your phone. If you can't boot into download mode its impossible to recover your phone.
Click to expand...
Click to collapse
The freeware ap in the heading of this post works well.
Device ID - IMEI - S/N -MAC