I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Sounds like you didn't factory reset your device. Before you factory reset, I recommend flashing TWRP recovery, mount your phone in recovery so you can back up important files to your PC if required.
After you've backed-up your files
Reboot (yes reboot, so switch your device off first) into the recovery menu (hold vol up + home + power), then select wipe data. This will wipe all data from your phone.
chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Where you cumming frop lolipop rom and flashed marshmallow or nougat rom ? If yes have you tick bootloader update in odin ? Rom will never boot without this update ! Try this if the previous good advice from Saber didn't help .
Everything is wiped. This is what happens when booting. Lines going across the screen. What originally happened was the person I got it from he had tried to do a update and the phone turned off. So I just flashed stock firmware but still get these lines.. Something is corrupted?
{
"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"
}
Sent from my SM-G900I using Tapatalk
When it boots in everything crashes in setup, get the error message unfortunately has stopped
Sent from my SM-G900I using Tapatalk
Looks like your phone needs a new main logic board because of defective memory.
chainzy said:
When it boots in everything crashes in setup, get the error message unfortunately has stopped
Click to expand...
Click to collapse
Here's my two cents if you've done what @Saber and @1981sebas suggested and still had no luck.
First, make sure the stock you've flashed is the latest MM XSA version to ensure you have the latest bootloader and modem. You can get it from sammobile or updato. It may take a couple of attempts so don't panic if it doesn't stick first time.
If it's still not right, hunt up the PIT files for your device and repartition it. Make sure you get legit files that others have used and had success with. You don't want to flash the wrong PIT. Then try flashing stock again.
Incidentally, have you tried flashing a solid custom ROM like RR or Cosmic? Maybe it's just an issue with your stock file being a bit corrupt if you haven't checked the md5 and any intact ROM will work fine.
My last option would be to try KIES because I personally find it iffy but others have had success with the recover phone option or whatever it's called. If you have KIES installed, just make sure it's disabled when you're using Odin and vice versa.
If none of this works, it may be a hardware issue. Good luck.
Sent from my Samsung SM-G900I using XDA Labs
I have tried a pit file I have but it didn't seem to do anything with that and re partition checked. I have tried several stock roms. Even tried the firmware with kies and still the same thing happens. Custom rom does the same.. The lines only come up on the screen when its booting.. They never come up in recovery or anything like that
Sent from my SM-G900I using Tapatalk
Dirty Flasher said:
hunt up the PIT files for your device and repartition it
Click to expand...
Click to collapse
That may be the case.
I'd try to download the latest "low_ship" factory firmware via Samfirm.
It contains a proper pit file in the CSC so it's necessary simply to flash it via Odin to repartition the device and clean everything on it.
Related
Hi guys
I've just bricked my tab. I flashed ICS to try it then I did a Factory reset and the tab was bricked.
I can access the Download mode, but when I put any firmware into Odin PDA the flashing process get stuck shortly after " NAND Write Start!! " at the beganing of "factoryfs.img" !
Long story short, my tab is totally bricked is there anything I can do ?? Please help me as this tab is imported and I have no warranty.
Thank you very much, really appreciate the community here.
Coolman4now said:
Hi guys
I've just bricked my tab. I flashed ICS to try it then I did a Factory reset and the tab was bricked.
I can access the Download mode, but when I put any firmware into Odin PDA the flashing process get stuck shortly after " NAND Write Start!! " at the beganing of "factoryfs.img" !
Long story short, my tab is totally bricked is there anything I can do ?? Please help me as this tab is imported and I have no warranty.
Thank you very much, really appreciate the community here.
Click to expand...
Click to collapse
As long as you can access the Download mode, you are not hard bricked, just download the rom that your device came with and install through odin, this will be the only image that your tab will accept.
The problem is, the flashing starts normally and as soon as it starts to write the NAND the progress stops then a big red fail appears after a long time.
Thank you for your reply, I'm so desperate right now.
Can you tell us what model and firmware, etc you used to flash? I think you are the first case
maybe ur firmware is corrupt?try downloading a new one...as long u can acces download mode it is softbrick
Luckily I have a screenshot of the previous firmware
{
"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"
}
I downloaded lots of firmware an none gets past the factoryFS
Did you do the factory reset while you were on ICS? Did you have CWM or root at all previously and/or after installation of ICS?
Hmmm...Curious. Any flashing program to be tried, other than Odin? If everything else fails, probably the flash ROM chip has gone bad like it did on my Xperia x10. Send it in for warranty, if possible, and tell them.you left it charging.overnight and it didn't wake in the morning...
Sent from my LG-P920 using xda app-developers app
I had root before on HC but I did a factory reset before installing ICS, then I flased the Austria ICS build. Then I did a factory reset from recovery and boom the tab can't boot nor can it be flashed ! always gets stuck at Writing NAND.
GRudolf94 said:
Hmmm...Curious. Any flashing program to be tried, other than Odin? If everything else fails, probably the flash ROM chip has gone bad like it did on my Xperia x10. Send it in for warranty, if possible, and tell them.you left it charging.overnight and it didn't wake in the morning...
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
To add insult to the injury, it's imported and I have no warranty. :good:
what you need to do is
You have super brick and not hard brick.what you need to do re partition using .pit file and then flash the room again. I had thus same issue and repartition worked for m e. How it helps
Well, you should contact service support anyway. Samsung generally doesn't care too much if the product was bought in another country...And a friend of had his Brazilian Tab 10.1 repaired in the UK, touchscreen problem, replaced by new unit free of charge... But, try another flashing solution first.
Sent from my LG-P920 using xda app-developers app
This looks like it is probably the super brick that people experienced on the note. We are luckier than the note because we have a dedicated recovery partition, so you can avoid the super brick by using a different recovery (such as the honeycomb recovery or CWM) and still use stock ICS as your rom.
As long as you don't use the stock ICS recovery for wiping/factory reset, you will be fine.
om0 said:
You have super brick and not hard brick.what you need to do re partition using .pit file and then flash the room again. I had thus same issue and repartition worked for m e. How it helps
Click to expand...
Click to collapse
How did you flash the pit file? Do you still have it?
Instructions please!
My battery actually died too - how can you charge it? D=
locerra said:
This looks like it is probably the super brick that people experienced on the note. We are luckier than the note because we have a dedicated recovery partition, so you can avoid the super brick by using a different recovery (such as the honeycomb recovery or CWM) and still use stock ICS as your rom.
As long as you don't use the stock ICS recovery for wiping/factory reset, you will be fine.
Click to expand...
Click to collapse
I guess that's not the case. Odin would overwrite all the partitions, including recovery...So device should act like factory new. However, flashing programs are often troublesome...
Sent from my LG-P920 using xda app-developers app
why not trying to let the battery run out first?
GRudolf94 said:
I guess that's not the case. Odin would overwrite all the partitions, including recovery...So device should act like factory new. However, flashing programs are often troublesome...
Click to expand...
Click to collapse
The initial post said that he did a factory reset, and then used Odin. The super brick is caused by using factory reset/wiping on recovery's built on un-safegarded kernels (the bug is actually in the firmware, but you can work around the bug by disabling a setting in the kernel). My guess is that the stock recovery with the ICS is built on an un-safegarded kernel.
I would seriously recommend that people go read up on the super brick, it affects our many (most?) of the Tab 7.7s out there. If you experience it, you better hope that Samsung support likes you.
I have tried the pit file lots of times, the flashing stops as soon as writing NAND starts.
Coolman4now said:
I have tried the pit file lots of times, the flashing stops as soon as writing NAND starts.
Click to expand...
Click to collapse
It looks like your NAND is cooked.
Have a look at ths http://forum.xda-developers.com/showthread.php?t=1682444
So Im blessed with a fried NAND Nice
Does anyone have the correct PIT file please ?
after mounting /system/apps as r/w and deleting a few bloatware apps (and trying to remove the knox and carrier iq files - i know, i know, i should have frozen them, but these were just the APK's, i hadn't uninstalled or removed the actual apps), my phone won't boot into android anymore.. is there anything i can flash to get android up and running again without tripping knox? so i can't get into adb but i can get into recovery and fastboot. is it possible to run a custom recovery through "fastboot boot <recovery img file>" or does the bootloader need to be unlocked? i don't really care what method is used as long as i can get back into android and not trip the knox counter. preferably would like to save my data, but not a big deal if i lose it. i'm on android 4.4.2 t-mobile N900T baseband NB4 rooted 0x0. thanks!
Flash stock ROM via Odin
verny94 said:
Flash stock ROM via Odin
Click to expand...
Click to collapse
thanks, that's what i figured i should do - will flashing the stock firmware work without needing to do a wipe/factory reset?
eudemonics said:
will flashing the stock firmware work without needing to do a wipe/factory reset?
Click to expand...
Click to collapse
Its better to do that
verny94 said:
Its better to do that
Click to expand...
Click to collapse
i can't get into recovery anymore since flashing the stock firmware failed instead it tells me i should choose emergency recovery mode in kies. but when i run kies 3 it tells me my device isn't supported! what can i do?
{
"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"
}
ok! i think i know what the problem is, at least i hope. (otherwise i'm out of ideas!) after searching all over the internet i found a few threads where people were having the exact same issue, and we all had one thing in common - we were all running odin in windows using vmware on a mac. i'll try flashing the stock firmware again on my windows PC in a bit and hopefully that works.
eudemonics said:
ok! i think i know what the problem is, at least i hope. (otherwise i'm out of ideas!) after searching all over the internet i found a few threads where people were having the exact same issue, and we all had one thing in common - we were all running odin in windows using vmware on a mac. i'll try flashing the stock firmware again on my windows PC in a bit and hopefully that works.
Click to expand...
Click to collapse
Yes. Vmware is broken with usb. I use parallels and it works flawlessly. Might look into that. I think parallels can even import your old vmware images.
God luck!
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Yes. Vmware is broken with usb. I use parallels and it works flawlessly. Might look into that. I think parallels can even import your old vmware images.
God luck!
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
so i plugged it into my windows PC, and strangely enough kies 3 wouldn't recognize it there either, saying it doesn't support my device. so i couldn't do the emergency recovery, but i got the phone out of the error screen and back into odin download mode, and then was able to successfully flash the firmware image and get back into android with all my data intact.
is odin the way way to flash the firmware from a computer or is there a way to do it in linux? i have heimdall for mac but i'm not too confident about using it for something like recovering from a soft brick..
eudemonics said:
so i plugged it into my windows PC, and strangely enough kies 3 wouldn't recognize it there either, saying it doesn't support my device. so i couldn't do the emergency recovery, but i got the phone out of the error screen and back into odin download mode, and then was able to successfully flash the firmware image and get back into android with all my data intact.
is odin the way way to flash the firmware from a computer or is there a way to do it in linux? i have heimdall for mac but i'm not too confident about using it for something like recovering from a soft brick..
Click to expand...
Click to collapse
Heimdall is the only way on a computer outside of odin. I have had zero luck with heimdall though.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Hadn't luck with Heimdall either. Had the same issue on my Note and i flashed the whole Firmware (with PIT etc.) to get back into Android.
Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!
F13Bubba said:
Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!
Click to expand...
Click to collapse
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
{
"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"
}
bilgerryan said:
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
Click to expand...
Click to collapse
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.
F13Bubba said:
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.
Click to expand...
Click to collapse
Uncheck Auto Reboot and F Reset (everything) when using Odin. And wait a minute after it says PASS before unplugging. Also try different ports and cables.
I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?
F13Bubba said:
I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?
Click to expand...
Click to collapse
TWRP can flash images now.
Flash this build of TWRP first. (It's a .tar for Odin)
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar
Copy this build to your device somewhere. (You might as well go ahead and copy a ROM you want to install on your device also.)
https://dl.twrp.me/jfltespr/twrp-2.8.7.0-jfltespr.img
Boot into TWRP and go to install. Select images button at the bottom right and select the build you copied to your device. You will now be running the current version of TWRP.
WOOOOOO!
After a ton of troubleshooting and grief, I finally got 5.0.1 back on, and working. I also discovered that my front usb port was not working correctly. I guess I'll try to root it now!
Aaaaaand, it seems to have worked flawlessly. Thanks for all the help guys!
so i followed the instructions here on how to flash 935U to my verizon variant and i cant get the ODIN process to work. keis and smart switch tell me my phone isnt supported because i tried to restore the phone.. help please. i followed the instructions which are simple to follow. i put my phone in download mode. started odin and loaded all the files and it failed. what can i do now.. waiting for the stock firmare to dowload now but its taking forever
oh and just incase this is why. im on a mac running windows 10 bootcamp. maybe i dont have some drivers needed ?
Head to sammobile and get the official 935v firmware again, or download through samfirm. Make sure you have ODIN 3.12 and leave the phone unplugged and in dl mode. Unzip the fw files and place them in the appropriate boxes (bl, ap, cl, csc) and once they are all in Odin plug your phone in. If the box goes blue as recognized you are hits to press start. Tart will get you back to original asks try again.
And get a pc, lol
thanks for the reply
i have a pc but i am at school for 2 months without it.. i booted windows just to get by for now.
i downloaded the firmware from sammobile and it may have been currupt becasue it didnt work as well. i am worried but i dont think its hardbricked. i just cant seem to figure out why i cant flash the 935U FW
justinsch03 said:
Head to sammobile and get the official 935v firmware again, or download through samfirm. Make sure you have ODIN 3.12 and leave the phone unplugged and in dl mode. Unzip the fw files and place them in the appropriate boxes (bl, ap, cl, csc) and once they are all in Odin plug your phone in. If the box goes blue as recognized you are hits to press start. Tart will get you back to original asks try again.
And get a pc, lol
Click to expand...
Click to collapse
I wouldnt worry about U. Get V back up and then there is whole separate U thread here with a lot of tweaks. If anything else, look at the PH1 firmware thread (may be under beta thread) and try flashing that, then update to PI3.
are there steps i am not informed on like do certain files need to be in folders together or do i need to run something that was left out in the instructions? i have rooted and flashed with odin before and it always seems to be an interesting experience to say the least. but seriously im getting soooo pissed off right now
yeah tried odin 3. 12 with stock firmware.. put the home file in and the other 3 files in the right places.. still failed.. any other advice?
putting all these files on a flash drive and taking them over to a regular pc to see if this helps.. im really at a loss. this should be EASY right now seriously easy. how am i screwing this up!
tried another computer... didnt work. tried different files and methods.. nothing works.. tried verizon repair tool...joke..... tried everything.
It sounds like Odin/PC is not seeing the phone when it's plugged in. Do you have the Samsung drivers loaded?
{
"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"
}
Don't use home CSC use csc_vzw
it was seeing it when i plugged in.. and it would say so in the log.
suprisingly the verizon repair tool brought it back to life. it restored it to factory settings and firmware.. i want to root but im worried it wont take again
mefloump said:
It sounds like Odin/PC is not seeing the phone when it's plugged in. Do you have the Samsung drivers loaded?
Click to expand...
Click to collapse
puchodog1977 said:
it was seeing it when i plugged in.. and it would say so in the log.
suprisingly the verizon repair tool brought it back to life. it restored it to factory settings and firmware.. i want to root but im worried it wont take again
Click to expand...
Click to collapse
I'm not trying to suggest anything bad by this but did you boot to download mode?
Verizon repair tool fixed it. I dont why the flashing didnt work. I spent too much time. Im not rooting this ****
I'm trying to install the factory rom of my samsumg j320m device, I'm using Odin in the current version (I already tested other previous versions) well in Odin no appears no error says that the rom was successfully installed the problem happens when the device it restarts, it goes to the screen that appears the robot of the android and begins to proceed with the installation but when it arrives in 15% or so it goes to that screen of which I can not leave again, I gave several hard reset, I searched the internet and I did not find anything that could solve this problem if someone can help me thank you very much
{
"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"
}
hollyxerecas said:
I'm trying to install the factory rom of my samsumg j320m device, I'm using Odin in the current version (I already tested other previous versions) well in Odin no appears no error says that the rom was successfully installed the problem happens when the device it restarts, it goes to the screen that appears the robot of the android and begins to proceed with the installation but when it arrives in 15% or so it goes to that screen of which I can not leave again, I gave several hard reset, I searched the internet and I did not find anything that could solve this problem if someone can help me thank you very much
Click to expand...
Click to collapse
How did you set up Odin? Send a pic of the settings tab
ffpp.2003 said:
How did you set up Odin? Send a pic of the settings tab
Click to expand...
Click to collapse
All seem to be ok. I see that it's a TAR file. Personally, I recommend you that use a .tar.md5 file, other than it takes longer, it's safer, because the file could be corrupted, and using the md5 extension, it makes a full revision of the file, looking for corruptions in the file, or information that is incorrect. I also have a j320m, and that never happened to me. Try redownloading the file, without deleting the .md5 extension. And if still getting that error, I'll give you the Odin version that i use with the j320m and other devices that are working perfectly fine.
ffpp.2003 said:
All seem to be ok. I see that it's a TAR file. Personally, I recommend you that use a .tar.md5 file, other than it takes longer, it's safer, because the file could be corrupted, and using the md5 extension, it makes a full revision of the file, looking for corruptions in the file, or information that is incorrect. I also have a j320m, and that never happened to me. Try redownloading the file, without deleting the .md5 extension. And if still getting that error, I'll give you the Odin version that i use with the j320m and other devices that are working perfectly fine.
Click to expand...
Click to collapse
I recorded a video trying to install the rom and then the error, take a look please. I downloaded the original firmware of the device directly from this site: https://www.sammobile.com/firmwares/galaxy-j3/SM-J320M/ZTO/
I downloaded almost everything from the first rom to the most current and nothing
https://www.youtube.com/watch?v=7bOHrvyJaB4
I also tried installing TWRP to install a custom rom, without success: /
hollyxerecas said:
I recorded a video trying to install the rom and then the error, take a look please. I downloaded the original firmware of the device directly from this site: https://www.sammobile.com/firmwares/galaxy-j3/SM-J320M/ZTO/
I downloaded almost everything from the first rom to the most current and nothing
I also tried installing TWRP to install a custom rom, without success: /
Click to expand...
Click to collapse
Hmmmmmm...
It's so rare...
I don't know why it's doing that. When I get home, I'll give you my Odin version, stock rom, and probably drivers, if I still having it. Other than that... I don't know what is generating that problem.
Sent from my Samsung SM-J320M using XDA Labs
ffpp.2003 said:
Hmmmmmm...
It's so rare...
I don't know why it's doing that. When I get home, I'll give you my Odin version, stock rom, and probably drivers, if I still having it. Other than that... I don't know what is generating that problem.
Click to expand...
Click to collapse
Well, I uploaded the file in OneDrive
https://1drv.ms/u/s!AvJ6DFiBtFQij12NYeyKycNa2VG7
There is a zip, wich contains:
-Drivers
-Latest stock ARO rom (Argentina, without carrier, so, it's basically the same as all other clean ROMs)
-Odin (don't remember what version)
-A tool to download the correct and latest firmware for your device (with correct codes for making your "Firmware status" original again)
The only thing it's that when you install the rom, the status of the phone probably will be modified, 'cause the location of the phone is different than the firmware.
Sent from my Samsung SM-J320M using XDA Labs
ffpp.2003 said:
Well, I uploaded the file in OneDrive
https://1drv.ms/u/s!AvJ6DFiBtFQij12NYeyKycNa2VG7
There is a zip, wich contains:
-Drivers
-Latest stock ARO rom (Argentina, without carrier, so, it's basically the same as all other clean ROMs)
-Odin (don't remember what version)
-A tool to download the correct and latest firmware for your device (with correct codes for making your "Firmware status" original again)
The only thing it's that when you install the rom, the status of the phone probably will be modified, 'cause the location of the phone is different than the firmware.
Sent from my Samsung SM-J320M using XDA Labs
Click to expand...
Click to collapse
Ok, I thank you very much :fingers-crossed:
Tell me if it worked!:laugh:
Sent from my Samsung SM-J320M using XDA Labs