Good morning,
I purchased this phone a couple years ago specifically for being able to root and customize my phone, I wanted to go with Lineage OS, but wasn't available at the time so I went with Renovate. Last night I tried to move to Lineage but failed, in fact I couldn't install any custom firmware's even returning back to Renovate. In troubleshooting I reflashed a stock image back to the phone and now i'm back to stock and working, but when I try to flash TWRP I am unable to I am getting only stock firmwares are allowed, i'm thinking perhaps I flashed a locked stock firmware. Looking at the developer options OEM unlock is enabled. Any thoughts, or help pointing me to a stock firmware that I would be able to flash to TWRP with?
jleiss said:
Good morning,
I purchased this phone a couple years ago specifically for being able to root and customize my phone, I wanted to go with Lineage OS, but wasn't available at the time so I went with Renovate. Last night I tried to move to Lineage but failed, in fact I couldn't install any custom firmware's even returning back to Renovate. In troubleshooting I reflashed a stock image back to the phone and now i'm back to stock and working, but when I try to flash TWRP I am unable to I am getting only stock firmwares are allowed, i'm thinking perhaps I flashed a locked stock firmware. Looking at the developer options OEM unlock is enabled. Any thoughts, or help pointing me to a stock firmware that I would be able to flash to TWRP with?
Click to expand...
Click to collapse
The firmware has nothing to do with twrp so it's strange indeed. Can you get an Odin log from when you try to flash twrp? With this it's easier to identify why twrp won't flash.
callumbr1 said:
The firmware has nothing to do with twrp so it's strange indeed. Can you get an Odin log from when you try to flash twrp? With this it's easier to identify why twrp won't flash.
Click to expand...
Click to collapse
I'm hoping this is what you looking for, if not let me know how I can enable more logging
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 38 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.imghttps://mail.google.com/mail/u/0?ui=2&ik=059f10abc2&attid=0.1&permmsgid=msg-f:1637431265232865158&th=16b9530f6c52c786&view=att&disp=safe
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also included screen shot of developers options, and then what pops up on the screen after the flash.
https://hmp.me/cmul
https://hmp.me/cmuk
jleiss said:
I'm hoping this is what you looking for, if not let me know how I can enable more logging
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 38 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.imghttps://mail.google.com/mail/u/0?ui...865158&th=16b9530f6c52c786&view=att&disp=safe
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also included screen shot of developers options, and then what pops up on the screen after the flash.
https://hmp.me/cmul
https://hmp.me/cmuk
Click to expand...
Click to collapse
Hmm the first screenshot, I've never seen before. Custom binary blocked due to remaining installment balance?! But from what I can see it maybe due to a network lock or OEM. Which stock firmware fo you have currently and what CSC?
callumbr1 said:
Hmm the first screenshot, I've never seen before. Custom binary blocked due to remaining installment balance?! But from what I can see it maybe due to a network lock or OEM. Which stock firmware fo you have currently and what CSC?
Click to expand...
Click to collapse
I'm back up and working thanks to @ZeroXO
I have the same problem, I cant root my Galaxy with TWRP, I have OEM botton ON but say when I try to flash TWRP custom bynary etc...
RMM STATE: NORMAL
KGSTATE : Checking
FRP LOCK: OFF
OEM LOCK: OFF
my CSC code is PCT Galaxy S8 SM-G950F Android Pie Security Patch 1 April 2019.
I want to root it with current Android Pie version, I try to Downgrade and i did it, but cant install TWRP.
Thanks in advance.
Related
Hi
My phone is N910U and it's CSC code is BRI (Thailand)
I was waiting for lollipop update, but it seems that only some countries have received the update.
So I decided to chage CSC to whatever the New Zealand CSC is to get the official update.
My phone isn't rooted and it runs stock rom.
While I was trying to flash recovery.tar via odin, it shows an error:
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used correct recovery file, and this happens when I want to flash autoroot too.
USB debugging on, download mode, stock USB cable, reinstalled driver
Does anyone know how to resolve this issue?
Also, can I just download New Zealand firmware and flash it via odin?
Will my phone not brick and be able to use it in the UK?
Any help would be very appreciated
EDIT: FIXED - Disable reactivation lock
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
absinthesummer said:
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
Click to expand...
Click to collapse
Thanks for your reply
the reactivation lock was enabled, so I disabled it. But it is still not working.
It shows slightly different error
<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..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I really have no idea what went wrong.
Do you have any clue?
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
absinthesummer said:
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried to root it first, and it gave me the same error(new one) as above.
I never had an issue when I was playing around with my SGS3 couple of years ago. Rooting, recovery, custom rom all flashed well via odin.
Any idea?
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
cosmostronomer said:
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
Click to expand...
Click to collapse
Very glad to hear it! That reactivation lock is the number one issue when odin fails (on this device anyway)
Hey everyone,
So I've finally had my first soft brick :crying: Hopefully I am missing some easy solution. So here's the background. This morning I was running MF3 with root. Using this guide http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642 I was able to upgrade to NB1 using Odin. Then I upgraded to NJ4 using stock recovery added root using towelroot v3. Then the trouble began.
I noticed my WiFi wouldn't switch on so I performed a stock recovery wipe data then factory reset. This didn't fix the problem. I then tried to use Odin to go back to NB1 because my WiFi was working back then. It failed halfway through (message on Odin) so I left it sitting for about 30 min. The phone never changed anything so I removed the battery and tried Odin again. It failed again. I decided to try to boot into stock recovery and was unable to do so. I have the screen with a phone (dot)(dot) yellow triangle (dot)(dot) computer saying Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Tried Odin again and I actually got about 75% through the process but it failed again. Now it makes the same amount of progress every time and continues to fail.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
My overall goal is to upgrade to OC3 with root access but right now it seems like I just need to unbrick my phone. Any ideas?
Update: Even though there are a bunch of warnings against it I went ahead and used Odin to redo my PIT file. Now I can boot into recovery. About to wipe data/factory reset.
Update 2: After the factory reset I tried to flash NB1 again using Odin. Still failing near the beginning, but with all my resetting I was finally able to get into the phone itself (WiFi still won't turn on). Also when starting up I no longer have the Samsung Custom with the lock (I'm assuming this means my root is gone for now). Now to figure out a way to fix the WiFi....
Update 3: My baseband version is NJ4 and the build version is NB1. I'm pretty sure this is why the WiFi is not working. I am now following this guide http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 to get to OC3. Hopefully this will fix the WiFi issue...
ava12ice said:
Hey everyone,
So I've finally had my first soft brick :crying: Hopefully I am missing some easy solution. So here's the background. This morning I was running MK3 with root. Using this guide http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642 I was able to upgrade to NB1 using Odin. Then I upgraded to NJ4 using stock recovery added root using towelroot v3. Then the trouble began.
I noticed my WiFi wouldn't switch on so I performed a stock recovery wipe data then factory reset. This didn't fix the problem. I then tried to use Odin to go back to NB1 because my WiFi was working back then. It failed halfway through (message on Odin) so I left it sitting for about 30 min. The phone never changed anything so I removed the battery and tried Odin again. It failed again. I decided to try to boot into stock recovery and was unable to do so. I have the screen with a phone (dot)(dot) yellow triangle (dot)(dot) computer saying Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Tried Odin again and I actually got about 75% through the process but it failed again. Now it makes the same amount of progress every time and continues to fail.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
My overall goal is to upgrade to OC3 with root access but right now it seems like I just need to unbrick my phone. Any ideas?
Click to expand...
Click to collapse
Mk3 is a sprint s3 modem, make sure you're in the right forum. As far as what else to try, I'm not sure.
Sorry not MK3, I meant MF3 (original post edited as well)
i have a 32 gb n900 phone that with official lolipop that i was put it from sammobile.com and flash it by odin, then i tried 2 do a root with odin but it is not succes so i do it by kingo root
now, i need to flash a xda's developer Rom 2 my mobile by odin but there are a problem in odin to flash recovery !!!
i tried 2 use a varity of recoveries but it is not useful
it (odin) present that the recovery is failed with red and give
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
plz help because every things i did 2 make a recovry is unsuccedes
Then turn off reactivation lock
Sent from my GT-N7000
Rosli59564 said:
Then turn off reactivation lock
Sent from my GT-N7000
Click to expand...
Click to collapse
then after what ???
and how can I do this ??
As far as I remember reactivation locked is only available in KK. Not sure with Lollipop. I'm not with stock Lollipop for long. Some more my phone has just broke so I couldn't tell more about it.
Sent from my GT-N7000
Did you Troy different USB cables and USB ports?
I have reactivation lock on note 3 n900w8 so maybe some versions of note 3 have the lock in lollipop.
Tried rooting this device (SM-G950F, 3 UK carrier logo), USB Debugging On, OEM Unlock On, odin successfully installed TWRP 3.3.1-1. Device restarted and since then does not go beyond Samsung logo. Can't go into recovery, can't shutdown the phone. Only goes into download mode. Googled and found a way to flash AQF7 BL, did flash it successfully with odin but still the same stuck at boot screen.
Here is what I tried so far;
Tried flashing TWRP older version 3.1.1-2
Tried flashing AQF7 Bootloader (BL_G950FXXU1AQF7_CL11544126_QB13847492_REV00_user_low_ship.tar)
Odin says successful install for both but can't get past boot screen.
Should I try flashing AQF7 firmware now? (downloading anyway). I would've tried it without asking but seen people doing it and still stuck at the same situation.
ODIN Log for TWRP flashing:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<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)
ODIN Log for BL Flash
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> up_param.bin
<ID:0/006> cm.bin
<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)
What if you try latest BTU firmware (CP/BL/AP/CSC) and then flash TWRP, untick autoreboot and try again? Is what comes to my mind atm
Well finally managed to flash a firmware... all is good. Phone is rooted now. All I wanted to do is to change the imei of this device. Installed Xposed firmware and the module (IMEI Changer). Imei changed as well, but when I put a sim it say not registered to network. Xposed IMEI changer says that its a software exploit and in Pakistan, the telecom authority has blocked all the imported phones (asking ridiculous amount as customs duty). Now I am not sure if the phone is carrier locked or locked by PTA (Pakistan Telecommunication Authority).
I apologize for the thread itself. It was more like a panic thread. Mods, would you please delete the thread, or if it doesn't bother anyone then someone please help me resolve this issue. PTA blocks the unregistered imei. This device is blocked and I have no idea how they do it. Youtube videos claims that imei changer works and changes the imei that PTA reads and unblocks the phone, but still not sure as I've successfully changed the imei.
Thanks.
I've been gone for awhile. I've always been rooted until I got a phone that couldn't be so that made me less active on here. Then that phone broke and I got an Iphone given to me. I won't be getting another Iphone. That wasn't fun for me. Now I'm back at it with a phone that can be rooted and is already rooted but I can't get to the next step for some reason. The problem I'm having is that I can't get odin to flash TWRP for nothing. Here is my log if that helps. Just give me advise and I'll see what I can do here.
I'm doing all I can to get xposed on this phone so I can get those handy dandy addons.
In recovery mode it says I have the ''heroqltevzw''. I tried using google I even looked on here but I can not find any information about ''heroqltevzw''. It's either heroqltechn or herolte.
Using Odin3 v3.12.7. Used A Few Others But It All Gives Me The Same Problem.
Some info about my phone.
Model Number: SM-G930V (VERIZON)
ANDROID vERISON: 8.0.0 (OREO)
Build Number: R16NW.G930VVRU4CRE5
Debugging Is Enabled And So Is OEM Unlock.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
In recovery mode it says ''heroqltevzw''
TylerMarshall256 said:
I've been gone for awhile. I've always been rooted until I got a phone that couldn't be so that made me less active on here. Then that phone broke and I got an Iphone given to me. I won't be getting another Iphone. That wasn't fun for me. Now I'm back at it with a phone that can be rooted and is already rooted but I can't get to the next step for some reason. The problem I'm having is that I can't get odin to flash TWRP for nothing. Here is my log if that helps. Just give me advise and I'll see what I can do here.
I'm doing all I can to get xposed on this phone so I can get those handy dandy addons.
In recovery mode it says I have the ''heroqltevzw''. I tried using google I even looked on here but I can not find any information about ''heroqltevzw''. It's either heroqltechn or herolte.
Using Odin3 v3.12.7. Used A Few Others But It All Gives Me The Same Problem.
Some info about my phone.
Model Number: SM-G930V (VERIZON)
ANDROID vERISON: 8.0.0 (OREO)
Build Number: R16NW.G930VVRU4CRE5
Debugging Is Enabled And So Is OEM Unlock.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
In recovery mode it says ''heroqltevzw''
Click to expand...
Click to collapse
Bootloader is locked down tight. You can't flash TWRP on this phone.
landshark68 said:
Bootloader is locked down tight. You can't flash TWRP on this phone.
Click to expand...
Click to collapse