Related
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
My coworker gave me his Verizon S3 on 4.3 I was going to try to unlock it for TMobile by following this thread and not realizing that I wouldn't be able to flash the custom JB image because I was on 4.3. Needless to say, it didn't work. Odin failed repeatedly. Well one time it hung but I thought it was just orphaned so I unplugged my phone. Bam, soft brick.
I got the stock Verizon image here and tried to ODIN it back to stock. I fail at aboot. I tried the stock PIT along with the stock image. Failed.
I tried SUA and its stuck at 83% and has been for over an hour.
I tried Kies and it does not even recognize the device but does know when I unplug it.
I just want to get it to stock so I can root. Any help is appreciated.
I should add I am on a Macbook Pro using VM Fusion. I don't have another Win 7 machine. I do have an Ubuntu box and my wife's Win 8 laptop.
HotShotAzn said:
My coworker gave me his Verizon S3 on 4.3 I was going to try to unlock it for TMobile by following this thread and not realizing that I wouldn't be able to flash the custom JB image because I was on 4.3. Needless to say, it didn't work. Odin failed repeatedly. Well one time it hung but I thought it was just orphaned so I unplugged my phone. Bam, soft brick.
I got the stock Verizon image here and tried to ODIN it back to stock. I fail at aboot. I tried the stock PIT along with the stock image. Failed.
I tried SUA and its stuck at 83% and has been for over an hour.
I tried Kies and it does not even recognize the device but does know when I unplug it.
I just want to get it to stock so I can root. Any help is appreciated.
I should add I am on a Macbook Pro using VM Fusion. I don't have another Win 7 machine. I do have an Ubuntu box and my wife's Win 8 laptop.
Click to expand...
Click to collapse
Use this guide, and specifically use jodin and follow the directions:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Use this guide, and specifically use jodin and follow the directions:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the tip. I tried JODIN but it sits in a "RUNNING" status for a long time. Like I left it for over an hour and it still just said "running".
HotShotAzn said:
Thanks for the tip. I tried JODIN but it sits in a "RUNNING" status for a long time. Like I left it for over an hour and it still just said "running".
Click to expand...
Click to collapse
Somethings wrong then, did you use the pit file?
I say unplug it and give it a shot again. Try a better cable if you have one.
Somebody else reported the same thing and I couldn't figure it out.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Somethings wrong then, did you use the pit file?
I say unplug it and give it a shot again. Try a better cable if you have one.
Somebody else reported the same thing and I couldn't figure it out.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Correct, I used the PIT file for the 16GB S3.
I switched to the Windows version and let it run. It finished and said no changes were made. Rerunning it now.
I have a couple more cables at home (stock factory) so we'll give that a whirl.
Well its off and running. Task manager has it using about half a gig of memory and CPU bounces so it looks like its doing something. I guess I'll just keep my fingers crossed.
Well nada. It ran for over two hours and nothing. Not sure where the disconnect is.
I'm at home now and am going to try with a different cord.
Is there even a good indicator of JODIN running besides watching CPU/Memory?
A handful of people seem to get stuck at 83%. I'll try to look into the problem when I get the time. In odin how far did it get before it failed? Just so I know I'm explaining properly what part is odin flashing.
ThePagel said:
A handful of people seem to get stuck at 83%. I'll try to look into the problem when I get the time. In odin how far did it get before it failed? Just so I know I'm explaining properly what part is odin flashing.
Click to expand...
Click to collapse
Thanks! I appreciate the offer for help!
This is the furthest that Odin has gone. I had just removed all Samsung drivers and rebooted.
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HotShotAzn said:
Thanks! I appreciate the offer for help!
This is the furthest that Odin has gone. I had just removed all Samsung drivers and rebooted.
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
A few things to try before I start looking into more drastic options. I did a quick google search and it seems the gs4 people have a similar problem but at 66%. One person said that by using the usb on the actual motherboard not the front or pci/pcie slot it worked. I would add a recommendation of uninstalling the drivers restart the pc then reinstall the drivers without the phone plugged in restart again and make sure you use a built in usb 2.0 (make sure its not 3.0 or 1.1). also if you have the samsung usb cable use that if you don't and fail try a different one. if you tried everything and you do have a usb 3.0 it couldn't hurt to try it (the first time I used the verizon utility was on 3.0 and it worked fine for me). I will hopefully have time tomorrow to explore this a little but my schedule is packed. I can look at the forums on my phone every hour or so but no access to a computer because I am running around.
Ideas that came right before I hit submit but I don't feel like changing my post:
Make sure your pc is updated 100% (especially drivers, you may need to go to the manufacturers website to get motherboard drivers. widows update is ok but not 100% recent)
Make sure you install the phone drivers with kies (check the install unified drivers option at the end of install. or if its already installed click trouble shoot connection in kies)
Make sure kies is completely closed before you open odin or verizon utility (Reboot should take care of that)
Before you open odin or verizon utility make sure no unneeded programs are running (once again that last restart should take care of that unless you have programs auto launch on start up)
Open odin or Verizon utility as administrator
Lastly if you go to try a different usb cable or port you should click that trouble shoot connection button then make sure you completely close kies before you plug the phone in. I know that sounds like a pain but its the only way to make sure every base has been covered. sometimes the biggest problems are from the smallest detail. Also it looks like it is running fine until you get to the big file which is the system file. I am wondering if perhaps you are on a usb 1.1 and that is why the over one gigabyte file fails to transfer.
ThePagel said:
A few things to try before I start looking into more drastic options. I did a quick google search and it seems the gs4 people have a similar problem but at 66%. One person said that by using the usb on the actual motherboard not the front or pci/pcie slot it worked. I would add a recommendation of uninstalling the drivers restart the pc then reinstall the drivers without the phone plugged in restart again and make sure you use a built in usb 2.0 (make sure its not 3.0 or 1.1). also if you have the samsung usb cable use that if you don't and fail try a different one. if you tried everything and you do have a usb 3.0 it couldn't hurt to try it (the first time I used the verizon utility was on 3.0 and it worked fine for me). I will hopefully have time tomorrow to explore this a little but my schedule is packed. I can look at the forums on my phone every hour or so but no access to a computer because I am running around.
Ideas that came right before I hit submit but I don't feel like changing my post:
Make sure your pc is updated 100% (especially drivers, you may need to go to the manufacturers website to get motherboard drivers. widows update is ok but not 100% recent)
Make sure you install the phone drivers with kies (check the install unified drivers option at the end of install. or if its already installed click trouble shoot connection in kies)
Make sure kies is completely closed before you open odin or verizon utility (Reboot should take care of that)
Before you open odin or verizon utility make sure no unneeded programs are running (once again that last restart should take care of that unless you have programs auto launch on start up)
Open odin or Verizon utility as administrator
Lastly if you go to try a different usb cable or port you should click that trouble shoot connection button then make sure you completely close kies before you plug the phone in. I know that sounds like a pain but its the only way to make sure every base has been covered. sometimes the biggest problems are from the smallest detail. Also it looks like it is running fine until you get to the big file which is the system file. I am wondering if perhaps you are on a usb 1.1 and that is why the over one gigabyte file fails to transfer.
Click to expand...
Click to collapse
I'm on a Macbook Pro that is a late 2011. According to Google, I should have USB 2.0.
I am updating the Windows VM as we speak. After that, here's my plan:
1) Install updates
2) Reboot
3) Verify no Samsung drivers are installed
4) Install KIES with Unified Drivers
5) Reboot
6) Open ODIN as Admin
7) Attempt flash
My biggest concern is the fact that I am using the VM. I believe the way VMware sees the USB ports is as a hub, not native USB ports. (I hate Macs ) My only other machines are my wife's Win8 and my Ubuntu box....although I could probably go steal my folk's Win7 machine. I tried JODIN for the Mac but it really doesn't seem to be doing a whole lot.
HotShotAzn said:
I'm on a Macbook Pro that is a late 2011. According to Google, I should have USB 2.0.
I am updating the Windows VM as we speak. After that, here's my plan:
1) Install updates
2) Reboot
3) Verify no Samsung drivers are installed
4) Install KIES with Unified Drivers
5) Reboot
6) Open ODIN as Admin
7) Attempt flash
My biggest concern is the fact that I am using the VM. I believe the way VMware sees the USB ports is as a hub, not native USB ports. (I hate Macs ) My only other machines are my wife's Win8 and my Ubuntu box....although I could probably go steal my folk's Win7 machine. I tried JODIN for the Mac but it really doesn't seem to be doing a whole lot.
Click to expand...
Click to collapse
When you ran the PIT file for your phone in Odin, did you flash that PIT file by itself? Reason I ask is because I remember "Odin getting stuck at 83%" being an issue in one of the 4.3 debrick method threads. I did a few searches and found post #86 where the user fixed it by flashing both the PIT AND VRUMCL1 tar. @ThePagel will probably remember reading this as well since its kinda obscure.
Edit: I'm gonna also suggest to try either Windows laptop as well if the Windows VM isn't working for you.
SlimSnoopOS said:
When you ran the PIT file for your phone in Odin, did you flash that PIT file by itself? Reason I ask is because I remember "Odin getting stuck at 83%" being an issue in one of the 4.3 debrick method threads. I did a few searches and found post #86 where the user fixed it by flashing both the PIT AND VRUMCL1 tar. @ThePagel will probably remember reading this as well since its kinda obscure.
Edit: I'm gonna also suggest to try either Windows laptop as well if the Windows VM isn't working for you.
Click to expand...
Click to collapse
PIT and tar file both.
So with KIES unified drivers, I fail at aboot.mbn. With "native" drivers that are installed without any additional installs, I get to the recovery.img.
I'm going to try the wife's Win 8 laptop.
Any ideas why even JODIN isn't working?
HotShotAzn said:
PIT and tar file both.
So with KIES unified drivers, I fail at aboot.mbn. With "native" drivers that are installed without any additional installs, I get to the recovery.img.
I'm going to try the wife's Win 8 laptop.
Any ideas why even JODIN isn't working?
Click to expand...
Click to collapse
I haven't a clue, I'm unfamiliar with JODIN. Haven't seen it mentioned too often so I haven't attempted to learn what its about. I might change that this weekend after work though.
Well @ThePagell, @SlimSnoopOS, @BadUsername looks like this is resolved.
Macs do not play well with Androids...at least in my case and with the S3. I had no problem using ADB with my S2. My wife's Win 8 laptop installed native drivers and is flashing using Odin 3.09 as we speak. No updating this or installing that. "It just works" (haha, ok, i'm done now).
Thanks for your time and your suggestions. I personally disliked my MBP but its what my work gave me and I'm too cheap to go buy a laptop although this experience has reiterated the need for a dedicated Win 7 machine at my house.
HotShotAzn said:
Well @ThePagell, @SlimSnoopOS, @BadUsername looks like this is resolved.
Macs do not play well with Androids...at least in my case and with the S3. I had no problem using ADB with my S2. My wife's Win 8 laptop installed native drivers and is flashing using Odin 3.09 as we speak. No updating this or installing that. "It just works" (haha, ok, i'm done now).
Thanks for your time and your suggestions. I personally disliked my MBP but its what my work gave me and I'm too cheap to go buy a laptop although this experience has reiterated the need for a dedicated Win 7 machine at my house.
Click to expand...
Click to collapse
I'll take that progress! haha great job on getting this resolved!
If using the MBP I would suggest setting up a Bootcamp partition instead of a VM. Odin in VMs used to work, but not anymore. Bootcamp works well though because its native.
I had similar issues but unfortunately the only fix for me was buying a jtag service off eBay and sending them the phone. Works great afterwards.
Sent from my Amazon Kindle Fire using Tapatalk
Accidentally bricked my phone. Changed file called secsettings.apk to secsettings.apk.bak and completely ****ed it up. I can't mount it using my recovery, and when I can somehow manage to get it to connect to my PC, it cant install drivers for some reason. Only way I can really get files onto my phone is via Odin3 and Download Mode. I've tried Converting the rom i was running on into a .tar file and had no luck. Also tried .gz, no luck. I have no idea what to do. I'm kinda screwed for now. Whenever I try sending the rom file across on Odin, I get
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Should I test my luck and take it back to Best Buy? I doubt its under warranty after I rooted and everything.
Also, It has something to do with MTP being corrupted I think. I have tried my phone across multiple computers, running linux, windows, etc. and all have had issues with MTP connection. Not sure if that does anything.
ToeJullar said:
Accidentally bricked my phone. Changed file called secsettings.apk to secsettings.apk.bak and completely ****ed it up. I can't mount it using my recovery, and when I can somehow manage to get it to connect to my PC, it cant install drivers for some reason. Only way I can really get files onto my phone is via Odin3 and Download Mode. I've tried Converting the rom i was running on into a .tar file and had no luck. Also tried .gz, no luck. I have no idea what to do. I'm kinda screwed for now. Whenever I try sending the rom file across on Odin, I get
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Should I test my luck and take it back to Best Buy? I doubt its under warranty after I rooted and everything.
Also, It has something to do with MTP being corrupted I think. I have tried my phone across multiple computers, running linux, windows, etc. and all have had issues with MTP connection. Not sure if that does anything.
Click to expand...
Click to collapse
Did you try using this to Odin http://forum.xda-developers.com/showthread.php?t=2737112 ?
miked63017 said:
Did you try using this to Odin http://forum.xda-developers.com/showthread.php?t=2737112 ?
Click to expand...
Click to collapse
I'll download this now, let you know if I get a successful flash.
miked63017 said:
Did you try using this to Odin http://forum.xda-developers.com/showthread.php?t=2737112 ?
Click to expand...
Click to collapse
THANK YOU SO MUCH! This worked perfectly!
To anyone else who bricks their phone, put your phone into download mode, flash this file using Odin. Works like a charm.
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