It stays on the booting screen flashing. "Samsung galaxy s6 live demo unit". I can't get it to boot hence can't set the usb debugging on to flash another firmware. What is there to do ?
EDIT: Managed to enter recovery mode and clear cache + do a factory reset. That not only did not solve anything but now i can't get into recovery or download mode at all. That "Samsung galaxy s6" thing flashes only when the phone is charging !
Alright, it has to be charging in order to get into recovery/download mode. Now, what shall i do ? What ROM should i flash since this is a SM-G920X ? Please help me, i couldn't find any useful information on google. Even if there was a suitable firmware to flash, the device is not recognized in odin. What shall i do ?
I had some problems with my account and i had to post from that other one. I downloaded samsung drivers and the phone is now recognized in odin but i cant flash the sm-g920 firmware, it fails just on start. Please help me out of this.
EDIT : FOUND THIS http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738 . I think it will be a great help.
Alright, i tried flashing that verified ready-to-flash ROM that was provided there and it failed at around 40%. Now i cant flash it again, it stay locked at
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I dont know what to do next.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Second time it fails.. I dont know why.
---------- Post added at 09:05 PM ---------- Previous post was at 08:42 PM ----------
I flashed that ready-to-go ROM successfully and now it boots further to that "welcome" screen but i encounter a big yellow triangle with an black exclamation mark in middle and a 'dead' android bot behind it. What should i do next ?
IMPORTANT NOTE : The phone won't show any kind of life unless it's CHARGING.
Can anyone really help me a little, what's up with this device ? Should i hope or try any further cause i really dont know what to do
Everything you guys need to know to get off the mess you created is here in this thread.
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Read and make sure you know what you're dealing with first, then start flashing ROMs!
I noticed the link was already found and posted by the OP in a later edit. Thanks.
One more thing i wanted to add is you can only flash a ROM that matches with your bootloaders. Since the LDU bootloader is Android 5.1.1 at the latest, you cannot flash Android 6. I suggest, if you manage to update bootloaders from 5.0.1 to 5.1.1, getting the latest 5.1.1 from sammobile, removing the *.bin files, and flash in ODIN.
Sent from my SM-G920F using XDA-Developers mobile app
Thanks god someone is willing to help me out of this ! I read the entire thread multiple times and i really really want to get out of this mess.
I took that ready-to-go ROM he provided there cause of the fact alone i have no clue what a unix machine is hence i can't remove these .bin files listed there. Also, i have no clue what bootloader this phone has or what that means in the first place, but i flashed a 5.1.1 one ( I guess) that i found on that thread successfully.
I would be extremely grateful if you could help me remove these files on my own or provided a 5.1.1 rom with these files removed.
Pure curiosity. Why does the phone 'play' dead when i'm trying to power it while not being charged ?
---------- Post added at 11:18 PM ---------- Previous post was at 10:20 PM ----------
Meh.. i seem to cant flash any ROM anymore. It would just fail mid-process saying "Removed".
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Im extremely grateful for your help, i will try to flash this one and if it won't work i'll check nand erase. I guess i can't screw it more than it already is.
EDIT : No success flashing either way.
---------- Post added at 06:05 AM ---------- Previous post was at 05:50 AM ----------
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
That's a log, 3 flash attempts in a row, different messages though.
In that g920x master thread it is said so " The only preparation required is the removal of the modem, bootloader, PIT, and related partitions.". I couldn't help but realize that while the flash was going on it still went through modem.bin, is that alright ? I have no idea myself, just trying to figure out why i can't this damned thing to work.
Ah I see the modem file in there. Sorry about that, although it seems that it flashed just fine. I would think the modem file will be there but not get used. But at any rate, I've redone the whole process from the original factory file, and i'm uploading now, no bin files this time! ETA 35 minutes ...
https://drive.google.com/open?id=0B31Omryqpl4nd2NLTG5nY3JxUk0
It still won't flash. I don't know what to do next.
Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Help me figure out the exact commands i have to type in cygwin for a filename. What do i have to do to let that terminal know where my file is located, cause i guess you have to mention the location.
Just write the exact command i have to write with the "Filename.tar" in cygwin while filename is located on desktop.
By the way, im requesting them cause i tried the commands you provided and i can't figure out how to use them.
"[email protected] ~
$ tar --delete --file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
[email protected] ~
$ tar --delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
"
I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app
Commodore 64 said:
I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app
Click to expand...
Click to collapse
I am a total noob. I cant figure it out really, it may be your way of explaining too but i cant. Just do that, write the exact command you write to remove hidden.bin from the "Filename.tar" which is located in cygwin local director.
---------- Post added at 06:05 PM ---------- Previous post was at 05:54 PM ----------
Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Wow, im unbelievably dumb. I just figured out ! You wrote the commands i have to use, one by one. Im so ashamed of myself now. I thought there are some commands i could use not at all they are meant to be used in that order, im so sorry for wasting your time.
I'm afraid i'll still have to bother you one more time
$ tar -xf AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar
tar: AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Steps i went through : 1. moved the ROM to C:\cygwin64\filename.tar (renamed it manually, not via command)
2. Wrote tar -xf filename.tar and i got that error you can see there.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
I GOT IT RIGHT, GOD. I am really sorry to waste your time. Finally, i understood, i read it all once again and i understood. I had to copy the tar file to cygwin64/home/User/. I am extremely grateful and i hope i will get my device to work.
I'm really sorry you had to dealt with such a noob though. I thank you again for your help.
Related
Hey folks,
I was trying to root my never before rooted s6 today (64 gb 920 I) using the uni-kernel method using odin for 5.1.1. I put the kernel into AP, and it failed after some seconds thus resulting in the blue screen which says "error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software."
I tried that and smart switch didn't recognise my device (maybe because USB debugging wasn't on).
Thus I downloaded a stock recovery for my device and I thought I would flash it via ODI. Things go well and the progress bar is 3/4th of the way through on my device and it suddenly says FAIL (shown below). I've tried with ODIN 3.10.6 and with 3.10.7 with the same results
<ID:0/003>Get PIT for Mapping
<ID:0/003> Firmware update Start!!
<ID:0/003> cm.bin <ID:0/003>
sboot.bin
<ID:0/003>NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) Operation failed.
<OSM> All threads completed. (succeed 0/failed 1)
What's unusual about this (to the best of my knowledge through forum search. I could be wrong and this could be common. If so I apologise) is that I've seen help threads about Odin failing at hidden.img or NAND Write Start but not during system.img. Does the fact that it's failed during system.img in particular tell us something?
Also, I can't access stock recovery, just the download section.
No clue why it's doing this. I would appreciate any help possible.
Thanks so much in advance. This means a lot.
Your current phone's firmware CSC should be same or within the region CSC of your downloaded firmware.
Hidden.img do have different partition size per Country/region. If you flash a not supported firmware, it will fail.
I.e., if your from France, just download the France firmware.so that you wont need to flash a pit file for your phone.
You can Search here at forum with keyword galaxy s6 pit file.
Or probably, your pc <> phone connection is unstable. Be sure it is connected properly, the usb cable should be in good performance etc.
I had the same happening. Don't sweat it really, no need to use that Smart Switch thing, Odin should still see the phone anyway, so just go ahead and flash a different image from Sammobile, possibly use one for your country and you'll be good.
I am so lost as to what to do next, i really need guidance.
I am offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work ASAP.
So i was attempting to root my phone [GALAXY S6 - SM-G920F]
Got the file from: https://autoroot.chainfire.eu/ which should've matched my Phone.
First attempt failed, got back into my phone everything is fine. Tried the same thing again, failed this time i get this message:
An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." The logs for the times it has failed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Tried connecting with Kies and Smart switch, none can find the device just keeps buffering and for smart switch it just say it's not supported. I am able to get into downloading mode, but that's it.
Got newest Kies, odin 3 v.10.7.exe however on my first go i noticed i had odin3 v.10.6 but now i got the latest i believe. After reading around i decided to try to fix it back to normal, so i downloaded my countries [sweden] firmware this one: http://www.sammobile.com/firmwares/confirm/57869/G920FXXU3COI9_G920FVDS3COI6_VDS/
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> 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/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004>
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And now i am here, i am truely nervous that i wont be able to get it to work.
Please Xda your my only hope. All i wanted was to free up space on my phone.. That's it.. :crying:
Ps. Worth mentioning, sometimes my usb is not recongnized and it flickers on and off (connectiong) but seems
to be fine most of the times and during the odin trials.
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
I just begain with youtubing easy way to root and i just said download odin, get the right firmware plug in an click odin.
That has failed and it's bricked, however i have tried to get my countries firmware, it didint work and produced my last log that i posted.
I am downloading another one there is two for Sweden however the other one says Sweden tre which is an operator over here and not one that i use so i doubt that will work?
i will attempt to download it but it takes 3h due to the limited speed at sammmobile.
So summarize, the sweden firmware from sammobile failed ;_;
What i do is, put phone in download mode, open odin, get the AP [Sweden from sammomobile] it finds it and press start, quickly after it says failed and i am back to square one.
I was reading the link you gave me about the pit files, it appears the error could be related to me having the wrong firmware?
I am seriously offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work.
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
blud7 said:
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
Click to expand...
Click to collapse
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
If you were on 5.1.1, then get 5.1.1
You can try the file you dl before. Just uninstall Kies before using Odin.
WaDoDem said:
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
Click to expand...
Click to collapse
You dont need to download another rom dude...the problem is your usb dont get recognized and after a while it will disconnect...it happened to me aswell...searched on youtube did an easy fix and then i flashed stock rom with odin and joined marshmallow beta...
Tldr: search on youtube a fix for usb not recognized...i dont have a link sorry you have to search it by yourself its an easy fix..
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
anthonyrv03 said:
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
Click to expand...
Click to collapse
You're fine with either.
@WaDoDem
First of all, calm down. Believe me it's harder than you think to brick S6 in a not fixable way
If Odin doesn't flash official roms or you just cant suffer a slow a** download speed from SamMobile :
1. Press and hold all of 4 buttons on your device. (Volume up + Volume Down + Home + Power) your device will reboot.
2. As soon as device reboots release volume up and hold other 3 three. (Power + Home + Volume Down). Your device should boot into downloading mode.
3. Download this :
https://dl.twrp.me/zeroflte/twrp-2.8.7.2-zeroflte.img.tar.html
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes, hold Power+Home + Volume Up. Now your device will boot into TWRP recovery.
5. Wait for drivers to be installed. Your pc should show phone's internal storage as connected device. If not, go to TWRP Mount section and enable MTP mode. (Or if it's enabled, disable and re enable it )
6. Download this rom :
http://forum.xda-developers.com/gal...rom-2013266107-arrow-rom-v1-0-0-fast-t3212318
And this kernel:
http://forum.xda-developers.com/gal...nified-development/kernel-vindicator-t3156281
Then put them on your phone.
7. Wipe system,data,cache and dalvik cache from twrp.
8. Install Arrow Rom first and then flash Vindicator Kernel.
9.Reboot, first boot can take up to 15 minutes
10.Continue celebrating new year [emoji14]
Sent from my SM-G920I using Tapatalk
sometimes if odin not working i restart my computer and put my mobile in downloadmode again and than i try again,most of the time it worked.....
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes said:
Odin cant find the tar file.
I got odin 3V3.10.7 in options auto reboot and f. reset time are all bocked in is that right?
On files to download i am able to do, ap,cp,csc,bl neither of those help to find the recovery image that i am supposed to start?
Click to expand...
Click to collapse
Damientju said:
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
Click to expand...
Click to collapse
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
WaDoDem said:
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
Click to expand...
Click to collapse
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Damientju said:
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Click to expand...
Click to collapse
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
WaDoDem said:
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
Click to expand...
Click to collapse
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
[email protected] said:
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
Click to expand...
Click to collapse
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
yes
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
WaDoDem said:
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Click to expand...
Click to collapse
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
sd_N said:
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
Click to expand...
Click to collapse
I just downloaded and tried the pit that above user posted.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
It's a Galaxy s6 32GB.
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Parteeajp said:
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Click to expand...
Click to collapse
Hi mate
Just flash a stock rom with odin on top of it
http://www.sammobile.com/firmwares/database/SM-G930V/
back up everything important before you do it ..just in case
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Hi
Yes you need to flash it with Odin
did you downloaded from sammobile?
if not try i from there , follow their instructions :
Extract (unzip) the firmware file
Download Odin v3.11.1
Extract Odin ZIP file
Open Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Usually sammobile has only one tar file ( unzip it just once) , back up you photos and files before just in case
Check this thread is not for your phone but the basics apply to all samsung phones
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Can you post a pic of the back of the phone showing the model number as SM-G930V and FCC ID. Then take a pic of the bootloader screen and show what what model number it has, if flash successfully it should be showing as SM-G930T. If proven true then it may seem that as the S7 is a Universal Hardware phone (QCOMM that is).
Please Help
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Benaiah1287 said:
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Click to expand...
Click to collapse
nitropowrd said:
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Click to expand...
Click to collapse
You need to use the prince comsey's modified odin that bypasses SHA verification.
Saga's End
aromerblz said:
You need to use the prince comsey's modified odin that bypasses SHA verification.
Click to expand...
Click to collapse
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
nitropowrd said:
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
Click to expand...
Click to collapse
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
nitropowrd said:
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
Click to expand...
Click to collapse
thanks a lot. I had 2 S7s. One I was able to flash with G930UUEU2APEH, but the other one couldn't...but I could with the one you posted ( SM-G930U_1_20160921124641_vvcrzx3ej5_fac)
Help please <ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img.ext4
<ID:0/006> Home Binary Download
<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> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
I am having the same problem. How do I know the version before trying and failing until I get one that works?
Couldn't the boot loader 'version' be changed/hacked within the (down graded) boot loader so the version check would pass?
Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!
isssaputra said:
Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!
Click to expand...
Click to collapse
If you trip Knox you won't be able to use Secure folder, Samsung Pay or Samsung Health and that's it.
You won't get any other problems.
Hi!
Yesterday I rooted my S7 (SM-G930F) with CF-Auto Root (from desktop.firmware.mobi)
Unfortunately, I didn't notice that the Kernel was 7.0, while my S7 was already on 8.0.
Now I have a lot of apps (including camera, youtube, lightning launcher, opera, ...) that either crash directly after starting or freeze shortly after they are opened.
Do you know if/how it is possible to get a working system again?
Thank you in advance (and forgive my bad english),
Andi
If you download 8.0 firmware files (either use samfirmtool, or go to sammobile.com or updato.com) and flash using Odin, use AP, BL, CP and HOME_CSC instead of normal CSC (HOME_CSC keeps data, normal CSC wipes data), it should set your kernel and everything back to 8.0 without causing any data loss.
Flash guide here https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
However I'm pretty sure doing this will reset your root, your best bet is to flash TWRP and root using Magisk as its the more modern and updated root method.
Hi @Beanvee7,
thanks for your info!
In the meantime, I have installed TWRP, and downloaded the firmware from sammobile, but failed with magisk (since it is one of the apps that keep on crashing right after startup).
So, I'll have to install it the old fashioned way with odin tomorrow.
But I have one more question left: Is there an advantage of using CSC vs. HOME_CSC? Since I have backups of all my data, and rooting wiped data anyways (the system was encrypted), a wipe does not inflict any (addiditional) damage.
Thanks,
Andi
CSC is probably preferred because it means a clean wipe, so you won't be carrying across any potentially broken apps/system files.
If you have backups then I'd recommend CSC.
Hi!
I am still stuck: No matter what type of installation I choose, it fails:
Odin reports success, but doesn't install the new firmware (neither 7.0 nor 8.0, from updato or sammobile).
<ID:0/006> modem_debug.bin
<ID:0/006> cache.img.lz4
<ID:0/006> hidden.img.lz4
<ID:0/006> Home Binary Download
<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> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
The "Now Writing.. Please wait about 2 minutes"-part only takes one second or so.
Installing via TWRP reports "Invalid zip file format".
ROM Toolbox Pro also reports "Invalid ZIP file"
Magisk still crashes upon startup.
Do you have any ideas left?
Hello! Yesterday I went to install TWRP on my Galaxy S8 to install a custom rom. In the tutorial, he said he should do Wipe on some things. I have and since then my phone is dead! I tried installing three different roms and none works.
When I flash the rom I have the following message:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> modem_debug.bin
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4042 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm using Odin v3.13. The most recent I found.
I've already looked all over the internet and saw a video where you should click Start on the odin and then click on the three buttons to restart the device etc. That did not solve!
Please, can anyone help me? I am getting crazy!
Solution
1-. First at all run ODIN as an administrator.
2-.Boot on download mode.
3-.Dont flash (BL) for the moment select only AP and HOME_CSC to make a fast flash.
4-.When you boot successfully on your system go to developer options and then select "Oem Unlock".
5-. Download a zip called (no-verity-opt-encrypt.zip) for the S950F . Move the zip to your phone you will need that later to make work the TWRP.
6-.Boot on download mode again.
7-.Flash the Custom recovery.
8-.Boot on Custom recovery wipe all data.
9-.Reboot on recovery again
10-.Now flash no-verity-opt-encrypt.zip and restart normally
11-.Done!
MrMeeeMdick said:
1-. First at all run ODIN as an administrator.
2-.Boot on download mode.
3-.Dont flash (BL) for the moment select only AP and HOME_CSC to make a fast flash.
4-.When you boot successfully on your system go to developer options and then select "Oem Unlock".
5-. Download a zip called (no-verity-opt-encrypt.zip) for the S950F . Move the zip to your phone you will need that later to make work the TWRP.
6-.Boot on download mode again.
7-.Flash the Custom recovery.
8-.Boot on Custom recovery wipe all data.
9-.Reboot on recovery again
10-.Now flash no-verity-opt-encrypt.zip and restart normally
11-.Done!
Click to expand...
Click to collapse
Thanks for the answer! I selected the AP and the SCS, but when I click to start the same thing happens!
Check the print
prntscr.com/kd0c3j
I got to TWRP. Is there anything I can do?:crying:
Rubson Goldner said:
Thanks for the answer! I selected the AP and the SCS, but when I click to start the same thing happens!
Check the print
prntscr.com/kd0c3j
I got to TWRP. Is there anything I can do?:crying:
Click to expand...
Click to collapse
...
Rubson Goldner said:
...
Click to expand...
Click to collapse
1.-Boot on TWRP If you can. Select the option (Advanced Wipe Cache and Data)
2.-Select only (AP) MAKE SURE IS CORRECT FIRMWARE, you have the correct samsung drivers and you are running odin as an ADMINISTRATOR
3.-If that doest work flash only the bootloader (BL). if you successfully flash the (BL), then flash (AP).
MrMeeeMdick said:
1.-Boot on TWRP If you can. Select the option (Advanced Wipe Cache and Data)
2.-Select only (AP) MAKE SURE IS CORRECT FIRMWARE, you have the correct samsung drivers and you are running odin as an ADMINISTRATOR
3.-If that doest work flash only the bootloader (BL). if you successfully flash the (BL), then flash (AP).
Click to expand...
Click to collapse
Hi!. I was able to install an alternative ROM, not original by TWRP, but I happen to be without a signal, then I would go back to the original rom, but I get the same error every time!
Rubson Goldner said:
Hi!. I was able to install an alternative ROM, not original by TWRP, but I happen to be without a signal, then I would go back to the original rom, but I get the same error every time!
Click to expand...
Click to collapse
Downgrade the Bootloader (BL). But you can install Z3 and repair the signal
***You can also flash the original modem.bin and you are go to go with the signal***