Just to get it out if the way, yes I am a noob. I first rooted my phone with the Modded N7105 Rom and it worked. However I was looking to upgrade to the N7105XXDLL1 ROM which is 4.1.2. So after I made a backup rom, I put it into recovery mode and took all the nessacary steps to flash the rom (unzip rom, make sure nothing is checked other than Auto restart and PDA with the correct rom selected. Then I get this log from odin:
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<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> N7105XXALIJ_N7105EVRALIC_N7105BVALIG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
So I panic and hold down the power button. Now I'm stuck with the screen "Firmware Upgrade Encounted an issue. Please select recovery
mode in kies & try again". This is what I have tried so far. Made sure kies was off when running odin/unistalled and reinstalled drivers/redownloaded the rom and tried again/reboot computer/tried a different usb port/tried different computer/cleaned usb port on phone and computers/took battery out and pluged in the usb to the computer and while holding the volume down button connect into the computer.
I can't get that message off of my screen no matter what I do. This is a Tmobile galaxy note 2.If you have the ability to help me it would be greatly appriciated, I knew I ran the risks of messing up my phone when rooting so the responsibilty rest upon me. But if any of you could help, you would save my holiday. Thanks in advance for any help:good:. (Looking at email hoping for notifications)
Did you resolve this at all? I'm in the same boat and kies won't recognize my phone either.
Did you install custom recovery when you rooted? Try booting to recovery. If not try grabbing the toolkit from the note 2 section. And see if you can get it install recovery. Then just flash a custom rom. There a lot of very nice touchwiz stock based roms.
sent via note 2 in boss mode @ quad core 2 ghz
Hey yall,
Neighbor's kid handed me his Sprint galaxy s3 today and asked if I could fix it. It's not working at all right now. I'd like to think I know a thing or two about technology but I know jack about Android...I use the other brand of phones. Anyway, lots of searches led me here to ask for help.
Far as I can tell it's a Spring LPH-710 Samsung Galaxy S3. When I turn it on it has the firmware upgrade encountered an issue screen and it doesn't do anything else. I can't get VOLUP+HOME+POWER to work (recovery mode I think) but download mode works with VOLDOWN+HOME+POWER.
I went and downloaded the Kies program from samsung but it fails to load the software. here's the error message; CAN'T POST LINKS! arrrgggg. It says "Failed to upgrade firmware due to an unexpected error. Do you want to run firmware emergency recovery now?" It then says I should enter some recovery code from another PC which I don't have.
It also has some small red text on the phone screen after I saw the Kies error message. It says SW REV CHECK FAIL : Fused 2 > Binary 1. That makes no sense to me but it's red and Kies error out so I'm going to assume that's not good.
I don't have a recovery key to use and the kid tells me he never backed it up to a computer before. I've read Odin is the preferred method to use for stock recovery but I don't know what files to download and use. Apparently, people are pretty unhappy with Kies...kinda like iTunes I guess. Why can't the Kies software wipe and reload the phone? Am I doing something wrong?
The device malfunctioned or had an error when he tried doing an update / flash. And if Kies is malfunctioning you can try PC Odin.
Download Sammy drivers of device, download the stock .tar image of the sprint s3 ( L710VPUDND8 ), download Odin v3.07
- At PC. Open Odin in admin mode. Click PDA and select the .tar image file and let that load and leave everything else alone in the program.
- On device press vol dn + home + power to get into download mode, press vol up to continue.
- Plug in device and let driver installation be completed. If a box in Odin ( on PC ) doesn't show a COM:##, replug device or try different ports and cables.
- Once you have that all set up click start and leave it to flash. It takes roughly 15 minutes to flash the whole thing or lesser.
If all else fails tell him to bring it in for servicing.
Posted via XDA Mobile
Thanks for the reply Sparks. I downloaded Odin 3.07, uninstall Kies and rebooted the PC. When I loaded the .md5 file, I then plugged in the phone and saw it look for drivers. The phone shows up on COM3. Below is what I see after I press start. Doesn't look good to me! Did I get the right file?
I've read that attepting to alter the operating system will void the warranty. Would this line on the download screen indicate he tried to do that? Current Binary: Custom. He said the contract is up in March so I'd hate for him to get screwed over by this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUDND8_L710SPRDND8_L710VPUDND8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's the right file. Says md5 is valid.
Binary custom and/or warranty bit 1 means he already tried to flash something and it ticked the counters so he's out of luck getting it repaired.
Go download the Galaxy S3 Samsung drivers through the official site and install them, reboot pc and try the method again in a different USB PORT ( Preferebly 2.0 slots ) some ports and different cables can be iffy at times.
Posted via XDA Mobile Free
I have a Samsung Galaxy Tab Pro 10.1 (SM-T520 aka. picassowifi). I would like to get CyanogenMod going on it, but I simply can't get any tool to flash a recovery or root image.
I tried to flash ClockworkMod recovery via Heimdall 1.4.0, 1.4.1 and git HEAD on two Ubuntu 14.04.1 machines and a Windows 7 machine. The "sudo heimdall detect" command shows that a device is detected, but when I do "sudo heimdall flash --RECOVERY recovery.img --no-reboot" all that happens is I get "ERROR: Protocol initialisation failed!" (issue 288 filed).
I tried Odin 3.07, 3.09 and 3.10.6 on a Windows 7 machine, attempting to flash ClockworkMod, TWRP and the CF-Auto-Root image, but while it recognises the device and the verifies the image validity, it always gets stuck at "Initialzing" (typo theirs, not mine). By stuck I mean, I can leave it going for upwards of an hour and it never moves past this step; I can still close Odin (it's not frozen or anything), but when I reboot the device, it's straight back into stock. Here's the log:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
The device is never bricked or anything. After every attempt, I can still boot it into the stock firmware.
I have used each of these machines to flash other devices. I have tried multiple cables and USB ports. The device is definitely in download mode, and I restart it before every attempt. I've read [HOW TO]Root the Tab Pro 8.4 and 10.1, Problems with Odin and about a dozen other threads on here.
Can anyone give me some pointers on what to do next? I am completely out of ideas.
detly said:
I have a Samsung Galaxy Tab Pro 10.1 (SM-T520 aka. picassowifi). I would like to get CyanogenMod going on it, but I simply can't get any tool to flash a recovery or root image.
I tried to flash ClockworkMod recovery via Heimdall 1.4.0, 1.4.1 and git HEAD on two Ubuntu 14.04.1 machines and a Windows 7 machine. The "sudo heimdall detect" command shows that a device is detected, but when I do "sudo heimdall flash --RECOVERY recovery.img --no-reboot" all that happens is I get "ERROR: Protocol initialisation failed!" (issue 288 filed).
I tried Odin 3.07, 3.09 and 3.10.6 on a Windows 7 machine, attempting to flash ClockworkMod, TWRP and the CF-Auto-Root image, but while it recognises the device and the verifies the image validity, it always gets stuck at "Initialzing" (typo theirs, not mine). By stuck I mean, I can leave it going for upwards of an hour and it never moves past this step; I can still close Odin (it's not frozen or anything), but when I reboot the device, it's straight back into stock. Here's the log:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
The device is never bricked or anything. After every attempt, I can still boot it into the stock firmware.
I have used each of these machines to flash other devices. I have tried multiple cables and USB ports. The device is definitely in download mode, and I restart it before every attempt. I've read [HOW TO]Root the Tab Pro 8.4 and 10.1, Problems with Odin and about a dozen other threads on here.
Can anyone give me some pointers on what to do next? I am completely out of ideas.
Click to expand...
Click to collapse
Did you run everything as admin?
He did say sudo.
thesisman said:
Did you run everything as admin?
Click to expand...
Click to collapse
Yep. I forgot to specify that for the Windows stuff, but I did. (Also in a clean boot environment, which always seems to help.)
[Hahahaha the forum lets me post links in my original post, but not in replies. Oh well.]
I eventually managed to flash the device. The only way I could do it was by finding a machine that was about five years old (as opposed to the Mac Mini and Windows 7 laptop, which are three/one years old respectively). It was a Dell Precision, and I could run Odin on *that* to flash both the root image (just as a test) and then the TWRP image (which is what I really wanted).
I still have no idea what the problem is or was. It could be that the TM520 "doesn't like" the USB2/3 ports on the newer machines, and absolutely requires an older machine with USB2-only ports. I can't be sure about that though, and I can't imagine why it would make a difference (especially when it seems to be a problem from the device end, not the OS/Odin/Heimdall end).
I realise this won't help anyone who doesn't have access to a never-ending parade of progressively older machines they can mess around with, but my tablet happily runs CM12 now, so I'm done experimenting with it.
Hi from germany...
the S4Mini from my daughter does not work anymore since yesterday.
She uninstalled some gaes bevore - she said.
And after this it hangs a little bit and then the screen went black and the handy doesn´t work anymore.
The situation NOW is this:
1. If i push the power button, the handy vibrates one time and nothing more happend. Screen stay black.
2. if i try to enter the bootloader mode, also only one vibration and after this nothing more happening.
3. enter the download mode works.
The following is printet on the screen:
Code:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
Now.. all the evening i tryed to solve the issue by flashing a new firmware over ODIN. .
But that does not work.
With different ODIN Versions i get different errors.
I try all this on a Win10 64Bit system and i startet ODIN as admin.
If i use Odin 3.07 / Odin 3.09 and also on Odin 3.11.1 the flashing process only start and stays at the initilization thing.
After this... nothing more happend. I wait one hour the first time.
This is the output from ODIN...
Code:
ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.09)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
IF i use the ODIN Version 1.85 (very old) i get the error message: there is no pit partition.
As Firmware in all these trys i used the following file:
I9195XXUCOE4_I9195OXACOE1_I9195XXUCOE4_HOME.tar.md5
One of the many threads i read was this Tread.
But everytime i get the problems with odin.
I don´t think that this is normal with the stuck at the "Initialzation" point.
The S4Mini from my daughter was untouched before - no root, no flash.
I thing she have the last official Version from Samsung on the Device (4.4.2)
Have anyone any idear how i can bring back life to the handy?!
I would be very thankful for hints or solutions.... so my daughter will.
I hope my english is ok and everyone understand my problem.
CU
SKSAustin
Hi everyone,
so here is the issue I'm facing with my A320FL.
Last week, after I had it all reinstalled properly, phone restarted and got stuck on FRP lock menu.
So I decided to wipe it all and reinstall with proper official ROM again.
I used Odin 3.13.3 launched as Administrator and latest Samsung Drivers.
I download latest official 8.0.0 ROM from SAMmobile.
I used the procedure with BL, AP, CP and CSC files (I don't mind losing all my data, I have backup) and all goes fine up to the green PASS! (I disabled Auto Reboot in Odin's Options just to take the screenshot):
https://ibb.co/HVrnxbw
then phone restarts, then goes with "installing updates" and quickly go up to 32%, then waits a bit: https://ibb.co/t392t7Q
then restarts again, then goes "Erasing" for a like 2 minutes: https://ibb.co/FJHMT7g
then restart again, and then the problem appears when phone gets stuck on following screen:
https://ibb.co/zHby4dx
I cannot go to recovery and wipe cache or data as I've seen on other posts to resolve this issue as recovery is blocked.
If I reboot the phone with 'Volume down + HOME + Power', I get to this screen: https://ibb.co/4RhJgJG
then if I press 'Volume Up" I have this screen: https://ibb.co/Wnh5Hv0
So I have "FRP lock: ON" at the top of the screen, and I cannot install TWRP or any custom recovery (Odin ends with a fail message if I try so): https://ibb.co/0qPLFL5
And phone shows "Custom Binary Blocked By FRP Lock": https://ibb.co/hsLdKjs
So I cannot boot into the ROM, go in Developer Options and Enable OEM unlock :/
And everytime I try to reinstall the official ROM, I get stuck on the "No Command" screen.
Any idea on how to go back to proper state?
Thanks
Just wait it out a bit. If it auto goes to recovery, it goes through that, well because the phone is kinda slow. Wait out the no command thing for 5 minutes, if it doesn't proceed that's a different issue
Thanks for your answer.
When I wait on the no command screen, the phone then reboots after like 3/4 minutes, and eventually goes back to that same screen again.
Thanks
Any chance of an update or something to try on that one please?
Thanks
Hi everyone,
any chance of a suggestion on my issue?
Is the phone bricked or have I a chance to recover it?
Thanks
mhaxor said:
Hi everyone,
any chance of a suggestion on my issue?
Is the phone bricked or have I a chance to recover it?
Thanks
Click to expand...
Click to collapse
I recomend trying to press power botton cupple of times while in recovery "No Command" mode.
RootingPro-18 said:
I recomend trying to press power botton cupple of times while in recovery "No Command" mode.
Click to expand...
Click to collapse
I tried that, and nothing happens.
Again I tried a few options, in different order, and so far the phone still looks briked.
Dunno if I'll be able to recover it anytime :/
mhaxor said:
Again I tried a few options, in different order, and so far the phone still looks briked.
Dunno if I'll be able to recover it anytime :/
Click to expand...
Click to collapse
Send me PM i will try to help you.?
@mhaxor: I have the same behaviour. Is it possible that you did the latest (September) stock firmware update before ? Boot loader updates and then no combination firmware flashing is possible.
cyberbix said:
@mhaxor: I have the same behaviour. Is it possible that you did the latest (September) stock firmware update before ? Boot loader updates and then no combination firmware flashing is possible.
Click to expand...
Click to collapse
Hey, I didn't install the september update, but I tried a few different stock ROM with ODIN from sammobile, one of them being with a build date of October 2019
https://www.sammobile.com/samsung/galaxy-a3/firmware/SM-A320FL/XEF/download/A320FLXXS5CSJ1/300636/
Regards
mhaxor said:
Hey, I didn't install the september update, but I tried a few different stock ROM with ODIN from sammobile, one of them being with a build date of October 2019
Click to expand...
Click to collapse
What does your bootloader state in download mode (B:?).
I guess 4, if so you have the same softbrick then me. Did you search for a combination firmware supporting Bootloader type 4 ?
I only see this screen when booting up the phone: https://ibb.co/hsLdKjs
mhaxor said:
I only see this screen when booting up the phone: https://ibb.co/hsLdKjs
Click to expand...
Click to collapse
Yes. What I thought. Your are on bootloader 4. Take a look at several threads here about a combination firmware that works with bootloader 4. There´s none at the moment.
I´ve exactly the same behaviour, none of the stock ROMs (and I tried many of them) was able to get the phone up again.
Bad luck, but at the moment your device is less or more bricked. Let me know if you are succesful, I´ll do the same and send you a PN.
mhaxor said:
I only see this screen when booting up the phone: https://ibb.co/hsLdKjs
Click to expand...
Click to collapse
Dude try bypassing FRP, i will try to search for some tools for you!
The only way I managed to bypass FRP lock was with unlocking the OEM in the device's settings in developper mode, then installing a new recovery.
But of course I can't access this now.
is it dead?
cyberbix said:
Yes. What I thought. Your are on bootloader 4. Take a look at several threads here about a combination firmware that works with bootloader 4. There´s none at the moment.
I´ve exactly the same behaviour, none of the stock ROMs (and I tried many of them) was able to get the phone up again.
Bad luck, but at the moment your device is less or more bricked. Let me know if you are succesful, I´ll do the same and send you a PN.
Click to expand...
Click to collapse
Edit: I was using the wrong version of (3.12) odin should have used version 3.13.
anyway you can shed some light on my issue as well? this was a friends phone (legit story), here in brazil these kids don't pay attention to what they are doing. they put google accounts on phones and fail to remember them nor do they care to. the device is showing similar symptoms. all I can really say is the device will only flash combination files, if I flash a firmware it only flashes the modem. when I got the device it was on bootloader 2 (b:2 firmware A320FLXXS2BRA9). then I ended up flashing a firmware that was b:3. after I did that the device will only go to factory binary, and like I mentioned before it wont flash the firmware just the modem.
on power up the device in the upper left conner says:
nad: passed
rpwb provisioned
in bootloader:
odin mode
download speed: fast
product name: sm-a320fl
current binary: Samsung official
system status: official
frp lock: on
secure download: enabled
ccic=
warrenty void: 0 (0x0000)
rp swrev: b:3 k:1 S:1
odin after flashing a firmware:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1207)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> sboot.bin.lz4
<ID:0/008> param.bin.lz4
<ID:0/008> cm.bin.lz4
<ID:0/008> boot.img.lz4
<ID:0/008> recovery.img.lz4
<ID:0/008> system.img.lz4
<ID:0/008> userdata.img.lz4
<ID:0/008> modem_debug.bin
<ID:0/008> cache.img.lz4
<ID:0/008> hidden.img.lz4
<ID:0/008> Home Binary Download
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
@mhaxor: Are there any news on your bricked device ? Have you been successful finding a combination firmware that works with latest bootloader ?
Hello,
no further improvement, still stuck.
This is not my main phone so I can use the other one daily, but I'd still like to unbrick that A320FL.
Regards,
mhaxor said:
Hello,
no further improvement, still stuck.
This is not my main phone so I can use the other one daily, but I'd still like to unbrick that A320FL.
Regards,
Click to expand...
Click to collapse
Do You have telegram?