Hello! I was trying to figure out if there was a way to remove the bloatware from this phone, without a root. I might not be able to since my build number is G930VVRSBCTC1, which is the B bootloader. If there is, or you need more info, please notify me. Thank you
TheVideoEffect said:
Hello! I was trying to figure out if there was a way to remove the bloatware from this phone, without a root. I might not be able to since my build number is G930VVRSBCTC1, which is the B bootloader. If there is, or you need more info, please notify me. Thank you
Click to expand...
Click to collapse
The issue with the B bootloader has to do with rooting, not with flashing unbranded firmware through Odin. You just need the correct U firmware and Odin.
You might also need the patched Odin, I can't recall which models require it but some do for flashing from carrier to non-carrier software. Try normal Odin first and if it gives a mismatch error then use patched Odin.
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Drunkpilot said:
The issue with the B bootloader has to do with rooting, not with flashing unbranded firmware through Odin. You just need the correct U firmware and Odin.
Click to expand...
Click to collapse
Well, how would I know which version of the U firmware I would need? Does it need to match my bootloader version?
I'm trying to do the opposite. I have a Verizon S7 that I long ago flashed to the 930U firmware. Now it's being sold, and it will need the 930V firmware. But all of my attempts to flash back to Verizon has failed miserably on every version of Odin I've tried. Not sure where to go next.
To add, I keep getting FAIL! (Auth) errors no matter what I do. I've tried different PCs. Different firmware. Different cables. Nothing.
Some of the firmwares are at different bootloader levels, so if the G930V firmware you're trying to flash is an older bootloader it'll fail. Try flashing everything but BL.
If that doesn't work also try patched Odin as it can bypass some fail messages https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Beanvee7 said:
Some of the firmwares are at different bootloader levels, so if the G930V firmware you're trying to flash is an older bootloader it'll fail. Try flashing everything but BL.
If that doesn't work also try patched Odin as it can bypass some fail messages https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
Im finally getting around to flashing this, as my dumb phone went into the Verizon software error so why not
TheVideoEffect said:
Im finally getting around to flashing this, as my dumb phone went into the Verizon software error so why not
Click to expand...
Click to collapse
Alright here we go again. My phone gets stopped when it trys to flash the recovery.img in the AP file...
Related
Was on NCG with root, unlocked the Developer mode http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..
ProSeriesRacing said:
Was on NCG with root, unlocked the Developer bootloader http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..
Click to expand...
Click to collapse
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.
smokerbond said:
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.
Click to expand...
Click to collapse
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.
smokerbond, Thank you . Back up & running again
ProSeriesRacing said:
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.
Click to expand...
Click to collapse
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?
al50 said:
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?
Click to expand...
Click to collapse
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.
ProSeriesRacing said:
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.
Click to expand...
Click to collapse
Ok. Glad to hear that you've gotten your device up and running.
I am having issues trying to root my Galaxy Note Edge with the following build number:
N915GXXS1DPK2
It has Marshmallow 6.0.1 installed. I try to flash CF root via Odin and it gets to what I think is the last step and fails. I have read a few people saying on other sites that the bootloader needs to be unlocked for it to work and others make no mention of it. I have attempted it several times and have tried using various USB ports but to no avail. Would it be easier trying to flash another ROM in order for it to work and if so, what would I use?
All help would be greatly appreciated.
Sorry if this has been mentioned elsewhere
By the look of it, you got a stock rom, wich provider do you have? I have Telstra for a while now and newer had a locked boot loader,
I'm not sure about the other providers but I believe there BL are not locked either...
to get root on your phone, the best way is, install a custom recovery (preferable TWRP) with Odin, and then flash the latest super su
hingerl said:
By the look of it, you got a stock rom, wich provider do you have? I have Telstra for a while now and newer had a locked boot loader,
I'm not sure about the other providers but I believe there BL are not locked either...
to get root on your phone, the best way is, install a custom recovery (preferable TWRP) with Odin, and then flash the latest super su
Click to expand...
Click to collapse
Yeh I have looked into that but cant seem to locate the right TWRP Flash file. Odin wont recognise ones I have found. Am on Optus
bradles73au said:
Yeh I have looked into that but cant seem to locate the right TWRP Flash file. Odin wont recognise ones I have found. Am on Optus
Click to expand...
Click to collapse
this one worked for me: https://forum.xda-developers.com/note-edge/development/twrp-915fy-915tmo-moment-t3129459
look for your variant, G, get the tar file, not the zip file, if you have problems with the latest version, try V3.0
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.
Hi
I tried to change my firmware by flashing a stock firmware from the STOCK FIRMWARE thread.
I got an error msg saying Custom Binary Blocked by FRP and I am not able to boot up now.
Before you ask me
The phone's model is G955-F (it is network locked to 3IE)
I have tried to restore using smasung smart switch it gives me the same error
I have tried used odin to restore the stock firmware which was in device before.
Can someone please help me?
rishab_s said:
Hi
I tried to change my firmware by flashing a stock firmware from the STOCK FIRMWARE thread.
I got an error msg saying Custom Binary Blocked by FRP and I am not able to boot up now.
Before you ask me
The phone's model is G955-F (it is network locked to 3IE)
I have tried to restore using smasung smart switch it gives me the same error
I have tried used odin to restore the stock firmware which was in device before.
Can someone please help me?
Click to expand...
Click to collapse
That's probably because you hadn't unlocked your bootloader. The Odin restore method will work, I have done it myself, make sure you select all of the files required in Odin. Sammobile have the 3IE firmware, get version G955FXXU1AQDD
daveuk87 said:
That's probably because you hadn't unlocked your bootloader. The Odin restore method will work, I have done it myself, make sure you select all of the files required in Odin. Sammobile have the 3IE firmware, get version G955FXXU1AQDD
Click to expand...
Click to collapse
I have already tried that.
rishab_s said:
I have already tried that.
Click to expand...
Click to collapse
This could sound like a really dumb suggestion but remove your google account and retry. Could it be the factory reset protection?
Sent from my SM-T810 using Tapatalk
I returned it, will be getting a refund and will buy another one
I have the exact same problem with my SM-G955F
It has FRP lock on it
It originally could boot up, but then the google screen would ask for a password
I then went to try and flash TWRP on it which did not work
I then tryed to install the samsung stock firmware for android 8.0.0 which brings up "Custom Binary(RECOVERY) Blocked by FRP Lock"
I dont know the password, so could not enter one
I only have access to the Download screen on the phone
Flashed AP "AP_G955FXXU1CRB7_CL12993656_QB17006520_REV00_user_low_ship_meta.tar.md5"
ON PHONE SCREEN IN DOWNLOAD MODE: KERNEL REV. CHECK FAIL. DEVICE:11, BINARY:1
What can i do to remedy this ?
Hello,
I am trying to install Lineage OS 14.1 on my SM-G930R4 herolte device. I have tried multiple odin versions, ranging from 3.09 to 3.12.3. I am trying to flash to newest TWRP, but I did try twrp-3.1.1-0 aswell. Nothing has worked. The error I am getting in ODIN when using 3.10.6 and 3.12.3 is "Complete(Write) operation failed." and in 3.09 I am getting "NAND Write Start!!" where it gets stuck.
I have ticked OEM unlock and USB debugging. I have also spent awhile googling this issue. But I am not finding anything and am not skilled enough to figure this error out myself. Any help is greatly appreciated!
I'm having similar issues. Any luck?
Robby98756 said:
I'm having similar issues. Any luck?
Click to expand...
Click to collapse
I can fix it for you by teamviewer and in process i need your whatsapp number for convenience.
Everything I can find suggests the G930R4 is USA snapdragon. You can't flash TWRP on USA snapdragon models, bootloader is locked permanently and the unlock option in settings doesn't actually do anything for them.
Beanvee7 said:
Everything I can find suggests the G930R4 is USA snapdragon. You can't flash TWRP on USA snapdragon models, bootloader is locked permanently and the unlock option in settings doesn't actually do anything for them.
Click to expand...
Click to collapse
Please Make an engineering boot for V9 binary in latest csc G930UUES9CSC2.
NONE CAN ROOT OR EVEN INSTALL TWRP FOR THE LACK OF V9 OR S9 BINARY ENGINEERING BOOT FILE