[Q] bricked during jelly bean installation - Nexus S Q&A, Help & Troubleshooting

Tried to upgrade Andriod ice sandwich to jelly bean using auto update, couldnt bring the phone up after installation. Stuck with Google logo. Fast recovery options (factory rest) doesnt work. Tried to update from sdcard but packages are not listed, .adriod_secure and /Andriod/data doesnt contain necessary software to boot.
Worst part, PC doesnt detect the phone.. so cant root using Nexus Root Toolkit.
Is there anyway to get this phone up
Details,
Product - HERRING
HW version - REV 11
Bootloader version -I9020XXLC2
carrier info - eur
lock state - locked

vjag said:
Tried to upgrade Andriod ice sandwich to jelly bean using auto update, couldnt bring the phone up after installation. Stuck with Google logo. Fast recovery options (factory rest) doesnt work. Tried to update from sdcard but packages are not listed, .adriod_secure and /Andriod/data doesnt contain necessary software to boot.
Worst part, PC doesnt detect the phone.. so cant root using Nexus Root Toolkit.
Is there anyway to get this phone up
Details,
Product - HERRING
HW version - REV 11
Bootloader version -I9020XXLC2
carrier info - eur
lock state - locked
Click to expand...
Click to collapse
I think the only 100% way to get fixed is to call Samsung customer service. Especially if this happened from an ota
Sent from my awesome Nexus S

vjag said:
Tried to upgrade Andriod ice sandwich to jelly bean using auto update, couldnt bring the phone up after installation. Stuck with Google logo. Fast recovery options (factory rest) doesnt work. Tried to update from sdcard but packages are not listed, .adriod_secure and /Andriod/data doesnt contain necessary software to boot.
Worst part, PC doesnt detect the phone.. so cant root using Nexus Root Toolkit.
Is there anyway to get this phone up
Details,
Product - HERRING
HW version - REV 11
Bootloader version -I9020XXLC2
carrier info - eur
lock state - locked
Click to expand...
Click to collapse
If you haven't rooted it or touched the phone at all and left it be then take it for repairs. Samsung would be able to fix it no problem.

If you have nexus root toolkit 1.5.5, click "Full Driver Installation Guide - Automatic + Manual"
Read and follow the instructions. That tool will download the drivers for you as well. Choose PdaNet drivers on step 2.

No offense, Returning it to Samsung is definetly an option, but that defeats the purpose.. bought Nexus instead of glossy ones just to try out Andriod
Now that it is messed up I want to fix it.
@ ej8989 have installed the drivers manually and tried them separately. (uninstalling the failed ones right from Samsung to PdaNet)
System fails to detect the device.
Cheers

Related

[Q]

Hello if someone could help me with my sch-i535 I would appreciate it soooo much. I bricked my phone by trying to flash cyanogenmod after taking the 4.3 update... Obviously I am new. I tried everything , lots of tries with Odin , I made an image on my sd card with win32 disc imager , I tried a bootloader unlock code with Odin...nothing worked. Then I went onto a Verizon forum , and the very thing that hurt me , the Verizon update assistant , un-bricked my sch-i535. The update assistant has an option "Repair Assistant" I ran this as the instructions said ...connected my phone to my laptop , and unbelievably an hour or so later it finished , and my phone just booted up. I had almost given up...I was ready to do a JTAG. Also my phone was updated to 4.4.2 Kit Kat.
So , my question is: Is there any way to flash cyanogenmod , on the sch-i535 after the 4.3 update ? I read somewhere in the forums that the Firmware can be changed , so that the bootloader is not locked.....or am I doomed to use the Verizon , bloated , battery stealing software ?
williamacker said:
Hello if someone could help me with my sch-i535 I would appreciate it soooo much. I bricked my phone by trying to flash cyanogenmod after taking the 4.3 update... Obviously I am new. I tried everything , lots of tries with Odin , I made an image on my sd card with win32 disc imager , I tried a bootloader unlock code with Odin...nothing worked. Then I went onto a Verizon forum , and the very thing that hurt me , the Verizon update assistant , un-bricked my sch-i535. The update assistant has an option "Repair Assistant" I ran this as the instructions said ...connected my phone to my laptop , and unbelievably an hour or so later it finished , and my phone just booted up. I had almost given up...I was ready to do a JTAG. Also my phone was updated to 4.4.2 Kit Kat.
So , my question is: Is there any way to flash cyanogenmod , on the sch-i535 after the 4.3 update ? I read somewhere in the forums that the Firmware can be changed , so that the bootloader is not locked.....or am I doomed to use the Verizon , bloated , battery stealing software ?
Click to expand...
Click to collapse
Nope. Once you've taken the OTA to 4.3 ML1 your stuck on a locked bootloader permanently
There is no way to downgrade or flash custom roms. Your limited to TW(Touchwiz) based only and anything other than those is out of the question
Sent from my Nexus 5
Hard to understand
ShapesBlue said:
Nope. Once you've taken the OTA to 4.3 ML1 your stuck on a locked bootloader permanently
There is no way to downgrade or flash custom roms. Your limited to TW(Touchwiz) based only and anything other than those is out of the question
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for replying ... That is hard for me to understand , my phone was bricked ... and obviously Verizon has a line or two of code , that unlocked my bootloader , inside their "Repair assistant". The repair assistant then installed Kit Kat on my phone. If the bootloader can be unlocked by code ... and Kit Kat installed , then it stands to reason that other ROM's could be downloaded , if someone could figure out the code that Verizon uses to unlock the sch-i535. I know that this would help more than one or two people , from reading the forums.
williamacker said:
Hello if someone could help me with my sch-i535 I would appreciate it soooo much. I bricked my phone by trying to flash cyanogenmod after taking the 4.3 update... Obviously I am new. I tried everything , lots of tries with Odin , I made an image on my sd card with win32 disc imager , I tried a bootloader unlock code with Odin...nothing worked. Then I went onto a Verizon forum , and the very thing that hurt me , the Verizon update assistant , un-bricked my sch-i535. The update assistant has an option "Repair Assistant" I ran this as the instructions said ...connected my phone to my laptop , and unbelievably an hour or so later it finished , and my phone just booted up. I had almost given up...I was ready to do a JTAG. Also my phone was updated to 4.4.2 Kit Kat.
So , my question is: Is there any way to flash cyanogenmod , on the sch-i535 after the 4.3 update ? I read somewhere in the forums that the Firmware can be changed , so that the bootloader is not locked.....or am I doomed to use the Verizon , bloated , battery stealing software ?
Click to expand...
Click to collapse
williamacker said:
Thanks for replying ... That is hard for me to understand , my phone was bricked ... and obviously Verizon has a line or two of code , that unlocked my bootloader , inside their "Repair assistant". The repair assistant then installed Kit Kat on my phone. If the bootloader can be unlocked by code ... and Kit Kat installed , then it stands to reason that other ROM's could be downloaded , if someone could figure out the code that Verizon uses to unlock the sch-i535. I know that this would help more than one or two people , from reading the forums.
Click to expand...
Click to collapse
The bootloader used to be able to be unlocked on this phone prior to the 4.3 ML1 update. Just because the firmware can be changed by Verizon does not mean the bootloader is unlocked. If it were as simple as figuring out the code Verizon used, then the bootloaders on all the locked phones on Verizon would have been unlocked by now. The problem is there is a security key and signature verification that is found in several partitions on the phone. The signatures must match or the phone will not boot up. The repair assistant was using official Verizon firmware which contained all the proper signature verifications. That is why it was able to install Kit Kat on your phone. A lot of smart people have been trying for several years now to find or crack the signature verification checks on quite a few phones without success. On Verizon, once you have a phone with a locked bootloader, you are stuck with that and their bloated software.

SM-915A Aug. Update 5.0.1 Firmware Search...

I've been looking everywhere for the latest updated firmware for the SM-915A. Apparently my phone updated without my knowledge, (Thanks again AT&T) and I went to roll back to KitKat without looking at my FW version....now soft bricked. Does anyone know where i can find the latest version? Thanks.
Use kies. Under tools there is an option to initialize or something. There you put in your serial number an it will flash your phone with the latest os from your carrier. Think your phone must be in either download mode or the "firmware update had an issue, please connect to kies" mode.
Sent fra min SM-N915FY via Tapatalk
elfysrfr said:
I've been looking everywhere for the latest updated firmware for the SM-915A. Apparently my phone updated without my knowledge, (Thanks again AT&T) and I went to roll back to KitKat without looking at my FW version....now soft bricked. Does anyone know where i can find the latest version? Thanks.
Click to expand...
Click to collapse
Go to best buy they will refresh your phone. Kies are not working on At&t phones.
Sent from my SAMSUNG-SM-N915A using XDA Premium HD app
Thanks for the info
I had boot loop. Fixed it on my T Mobile Note Edge by booting into recovery and doing a factory reset. I am now on 4.4.4 native.
This is the AT&T variant...note edge SM-915A. We don't have an unlocked bootloader, hence no custom recovery to boot into and reflash
I didn't use a custom recovery. I would have mentioned that. I used Samsung's stock recovery mode and did a hard reset
Gotcha...yeah mine killed stock recovery too. We'll after being without a phone for a week, I tried best buy Samsung experience and they couldn't fix it. I ended up going to the Samsung service center storefront and they finally got it going again for free. Well looks like I'm stuck on LP though but at least I've got a phone again

Custom binary blocked by FRP lock

Hi there,
I have a Samsung Galaxy Tab A6 (SMT-580) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
dottech .org/200476/how-to-install-twrp-recovery-on-samsung-galaxy-tab-a-sm-t580/
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Hi. Have you got it fixed yet? You need to download and flash stock firmware for your model and flash it in odin. Once it's done you have to enable oem unlock before you flash twrp. Let it be enabled as long as you you have twrp, root or anything custom.
Skickat från min SM-A310F via Tapatalk
ok, I read this is the place for noobs, so, I too got myself into a FRP LOCK on my Galaxy Tab A6 sm-T280. I use the tablet strictly for flying my drone for surveillance around the rural location where I live. It was having some connectivity problems, so I rooted it to hopefully get enough horsepower to run the DJI Go app. That didn't work so I did a wipe/factory reset, had a problem with the password, and here I am.
I am researching, and gathering the required tools to fix it.
I finally found some guides that are basic enough for me to understand.
I found numerous sites to download the stock rom, but not sure which ones are safe. Suggestions? Also, I am not sure about the country code for the firmware. I am in the USA, and I don't see it listed anywhere. Does it matter? This android stuff is all new and confusing to this old man. I am determined to get this tablet fixed, and would appreciate any and all advice. Thanks, Gary
edit: Will this rom work? : T280XXUOAPL1 using XAA for theCSC? Is xaa the default/generic for U.S.A. ?

[Guide] How to downgrade from Android Oreo 8.0 to 7.0 (Non-rooted)

How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further! ​(I believe it works on your S7 too, but make sure you have downloaded the correct firmware)​
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example: https://i.imgur.com/DIB2d1S.png
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this: https://i.imgur.com/FYosmx2.png
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Thanks
I'm guessing Knox counter wouldn't have incremented?
ZionMainframe said:
Thanks
I'm guessing Knox counter wouldn't have incremented?
Click to expand...
Click to collapse
No, not at all, if you are using the official firmware! Just follow the guide closely
Please help me downgrade from G935FXXS3ERHD to G935FXXU2DRAG.
I tried nand TWRP BL restore, BL and stock firmware flash in Odin. Nothing works.
Edit:
I found a solution, see: Original post
but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2
can you upload the bootloader?
How to know each android 7.0 bootloader is V2?
Now with the lattest update the binary changed to 3 then i cant downgrade to Nougat
(Im spanish)
Oreo to nougat
I have a s7 edge with the Data firmware Version 2018/09/18 8.0.0
PDA: G935FXXS3ERHD
CSC: G935FITV3ERG2
is it possible to downgrade from oreo to nougat? I have the battery that you always download
I tried but doesn't work
Hello dear!
I have a S7 edge SM-G935T and I tried to flash the last version of Nougat 7, but doesn't work. Odin don't let me finish the process. Maybe you wrote this thread before my cellphone received the last update of Oreo.
Do you have any solution in this case. I really appreciate it.
King regards, _/\_
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
i have stupid question but, i have R16NW.SM-G930FXXS3ERKE (oreo) but i think im not supposed download this(G930FXXS3ERKE) if i want downgrade to nougat but rather (G930FXXS2DRC3) because the first firmware i mentioned get me oreo again.... am I right??? i don t wont screw things up....
TheLoller221 said:
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
Click to expand...
Click to collapse
YES, the Guide is NOT working ANYMORE...
Does this work still
Help with G930A
Hello um I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1). I've tried to root it but after some research I've come to find out I have to downgrade it to nougat to root it. But the problem is everytime I load a firmware it fails and I did more research I think it said something about the bootloader blocking it and the only way to downgrade the bootloader is downgrading the firmware which I can't do because of that cycle. Can someone please help me all I want to do is root install a custom recovery and a custom rom I love playing around with android tweaks but I can't get it because of this. I hope someone can help me please and thank you.
freshair4552 said:
I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1)...
Can someone please help me all I want to do is root install a custom recovery and a custom rom...
Click to expand...
Click to collapse
Your bootloader cannot be unlocked due to it being Snapdragon, so unfortunately there is nothing you can do. Only Exynos variants can be modified.
Hello guys,I have a problem with my galaxy s7 sm-g935f(Exynos version).Few months ago I flashed my phone from android Nougat SEE CSC(South East Europe) to UK's Oreo BTU CSC.I'm curious is there any other way to downgrade it from oreo to nougat,otherwise than Odin.I tried flashing it a few times with the latest Odin version (3.13.3) and nougat SEE CSC(South East Europe) because that's my original CSC.Odin recognizes the device normally,but when i click start,it comes to setup connection and then FAIL.The reason I'm trying to downgrade is very poor battery life and heating,and the phone is very laggy.I even tried through Samsung Smart Switch Emergency software recovery but it seems that Samsung has restricted that option...please help if anyone has/had similar problem.Thank you!
Mine is Sprint g935pvpsbcta1
Am I screwed also?
Hi, I have
SM-G935F​and I can't find any nougat firmware with baseband of: G935FXXS8ETCA.. Can I flash any country / baseband 7.0 firmware? And will it improve the SOT? I'm currently getting upto 5 hours SOT.
lovetv said:
How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further!
(I believe it works on your S7 too, but make sure you have downloaded the correct firmware)​
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example:
https://imgur.com/DIB2d1S
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this:
https://imgur.com/FYosmx2
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Click to expand...
Click to collapse
I just wonder this solution will be work as well? my phone is s6 edge plus G928C.
And i want to downgrade to 5.1.1 or 6.0 because 7.0 was really terrible.

Help downgrading encrypted bootloader samsung phone.

Hi all !
Hope everyone have a great day, i have got a samsung galaxy A6 US variant TMB, (SM-A600T) with android version 9, I was trying to root the phone but didn't have the knowledge that this phone can't be rooted because of locked bootloader which can't be unlock with any procedure. So i gave up and just updated my phone to the latest version available of PIE . (Android 9), To tell you more, before it was also on the same version of android 9 but earlier date. I have not updated a whole version of android but just to a latest date of android 9, Android 10 is also available for this phone but i haven't done that yet. The main problem with my phone is that before this update i just needed to charge my phone once in 24 hours, and now after update i need the same phone with same demands to charge it 3 times in 24 hours, Did every optimization for battery, unused apps, extra apps uninstalled, just one google account left, synchronization is off, NFC and near scanning is off, Bluetooth / Wifi is off, GPS is off. Auto update for apps and system software is off. Battery saving mode is enabled, clear cash has been done, factory reset is already done with flashing this version of android with odin tool, and etc every other thing has been tried with no luck, please don't advise for these things as the main problem for me is just the android version itself which i have newly flashed. Because of locked bootloader i can't flash back my older version of android 9 with odin tool, phone gives error of bootloader :
sw rev check fail device 2 binary 5​something like above after many tries the same result. tried my old firmware with the new bootloader but still no luck. (Same error). Any help or suggestions will be greatly appreciated. I am thinking what if i extract the AP of the new flashed firmware and replace the system.img.lz4 with my old firmware's system.img.lz4 to trick the phone and reflash with the new firmware but old system image file, Can this be done ? or i may brick my phone for ever ? what if i take my phone to the outside market and request a z3x flash for the old firmware version ? will that work ?
Please give any accurate solution i really want my old phone back, this locked bootloader has become a really annoying thing for me. I will never buy a phone like this which bootloader's can't be open again. Or if i wasn't able to flash this to my old version i will never use android again in my life, Better option will be to buy an iphone after 17 years of android use.
Thanks in advance.

Categories

Resources