Getting Canadian firmware when rooting has soft bricked your phone. - Samsung Galaxy S7 Edge Questions and Answers

I just wanted to post this as I had a hell of a time trying to get my phone back to its original state after I installed TWRP and it completely locked up my phone and would not let me get into the custom recovery. I was able to get into download mode but trying to flash stock firmware i found on some help sites would not let me flash in odin, it kept failing and i was scared i had to shell out 80 bucks for someone to fix the software. I installed kies 3 and it was asking for the serial number which I could not access as i took the sticker off the back of the phone and it is not printed on the box anywhere. I actually contacted samsung's live chat and asked them if i gave them my imei would they be able to give me the serial. They did no problem and now my phone is back to its original state. Just wanted to post this as I could not find an answer anywhere and this worked for me and i know how scary it is. Hopefully this can work for someone who is in the same boat as i was.

This happened to me. I have a Rogers S7 Edge. What I did was press volume down then hold power to get out of download mode. Then I held down power home and volume up and was able to get into recovery. I screwed it when I botched xposed install. Luckily I backed up in recovery.

Related

MY LG G2 for verizon is bricked HELLLPPPPP PLEASE

sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Im in the same boat
xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
BAYOUREBEL said:
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
Click to expand...
Click to collapse
DId you not try and go back to stock?...
http://forum.xda-developers.com/showthread.php?t=2432476
xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
If you can't boot into stock recovery (vol down + power key) and can't get into download mode (this is where they detect root once FW update shows up and the bottom left corner says Bootloader: ROOTED) then you can rest assure as long as you are under warranty, send it in to LG directly.
Do not send it to Verizon as you may incur charges for replacement. There's insurance from Verizon, but the real "replace with no charge" warranty is sending it to LG directly. Make an account on their website, register your G2, and make a Repair request by online chat or phone.
I just got my T-mobile G2 back after 2 weeks with the same issues and while it took a while to get repaired, I didn't pay a penny and it works without T-Mobile ever knowing its different hardware (all they replace is the flash memory that is corrupted in the phone).
Only downside is that it came back with KitKat and unrooted which means I have to wait for a working root procedure for it unlike with JB (I'm not afraid to root it again since I know what messed it up before was custom recovery TWRP version 2.6.3.2 that doesn't support KitKat lol).
hyelton said:
DId you not try and go back to stock?...
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
He can't get into download mode which means no KDZ flashing.
MDA400 said:
If you can't boot into stock recovery (vol down + power key) and can't get into download mode (this is where they detect root once FW update shows up and the bottom left corner says Bootloader: ROOTED) then you can rest assure as long as you are under warranty, send it in to LG directly.
Do not send it to Verizon as you may incur charges for replacement. There's insurance from Verizon, but the real "replace with no charge" warranty is sending it to LG directly. Make an account on their website, register your G2, and make a Repair request by online chat or phone.
I just got my T-mobile G2 back after 2 weeks with the same issues and while it took a while to get repaired, I didn't pay a penny and it works without T-Mobile ever knowing its different hardware (all they replace is the flash memory that is corrupted in the phone).
Only downside is that it came back with KitKat and unrooted which means I have to wait for a working root procedure for it unlike with JB (I'm not afraid to root it again since I know what messed it up before was custom recovery TWRP version 2.6.3.2 that doesn't support KitKat lol).
He can't get into download mode which means no KDZ flashing.
Click to expand...
Click to collapse
Not getting into download mode is odd especially for just accepting a OTA update. Remember since they accepted the OTA its gonna take a special way of getting into download mode as the phone will be constantly on in boot loop. not all of the time but most of the time when people say they cant get into bootloader they have to keep trying due to the phone has to be "Turned off" OR rebooted at the same time of holding down the key combo.
hyelton said:
Not getting into download mode is odd especially for just accepting a OTA update. Remember since they accepted the OTA its gonna take a special way of getting into download mode as the phone will be constantly on in boot loop. not all of the time but most of the time when people say they cant get into bootloader they have to keep trying due to the phone has to be "Turned off" OR rebooted at the same time of holding down the key combo.
Click to expand...
Click to collapse
To get the phone to turn off, one has to reboot the phone (power key for 10 seconds) while holding volume up WITHOUT having the USB cable plugged in.
Recovery mode is a bit trickier by having to hold the power key for 10 seconds, then just as the phone reboots, hold PWR + VOL DWN and while holding VOL DWN, release PWR and press it again (gets to that factory reset screen where you press PWR 3 times).
Not trying to teach you this if you already know how, just stating it if the OP looks at this then he can try again with the above.
Also, Download mode is essentially the "bootloader" and it is locked meaning unless you have certified software (KDZ FW updater), you can't adb anything just in download mode unlike some LG phones that have emergency mode which is unlocked bootloader.
MDA400 said:
To get the phone to turn off, one has to reboot the phone (power key for 10 seconds) while holding volume up WITHOUT having the USB cable plugged in.
Recovery mode is a bit trickier by having to hold the power key for 10 seconds, then just as the phone reboots, hold PWR + VOL DWN and while holding VOL DWN, release PWR and press it again (gets to that factory reset screen where you press PWR 3 times).
Not trying to teach you this if you already know how, just stating it if the OP looks at this then he can try again with the above.
Also, Download mode is essentially the "bootloader" and it is locked meaning unless you have certified software (KDZ FW updater), you can't adb anything just in download mode unlike some LG phones that have emergency mode which is unlocked bootloader.
Click to expand...
Click to collapse
Yea I know the commands, The guide for going back to stock was created by me for the G2 haha, Hopefully the OP will see your post and try that
ive tried
ive tried factory reset "vol down & power"...its just goes black and stays the same
I'm having about the exact same problem. I rooted my phone a while back, I left it stock and just used some modules (xposed). When I noticed the update I of course was stupid enough to hit the update... My phone is doing the same as his. I can get to the factory reset screen but even if I go through there I get the same black screen (though backlit). I can't boot into download. I'm downloading the .tot needed for stock, but I'm not sure if that'll be a lot of good without download mode. I have everything on my phone backed up from when I rooted it (I'm missing a few pictures but nothing major.) Any and all help would be appreciated. I've got a bunch of precalc homework and Prom in a couple days so I'm willing to sacrifice sleep tonight. Thanks! (Made this account just for this, though I've used the site a bit before.)
xdavelope said:
ive tried factory reset "vol down & power"...its just goes black and stays the same
Click to expand...
Click to collapse
It's cuz you're not doing it correctly.
Yes, you're supposed to depress "vol down & power" but once you see LG logo, let go of both buttons and then immediately hold down only the "power" button.
After a few secs, a white factory reset screen will appear. Ignore the warning and press power button. I know, its kinda scary at first, but then phone will load into recovery.
I can get to the factory data reset screen but when i choose yes it just gives me the secure boot error. I am able to put my phone into download mode by pressing up volume and power when plugging to pc, but cant get pc to recognize it. I am sure I am missing something.
i am also bricked. i cant get into download mode or recovery. i have twrp installed, cant get to that either. i have tried every button combination and all i get is a black screen and vibrations, no lg logo. need help.
Dont
BAYOUREBEL said:
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
Click to expand...
Click to collapse
Call LG verizon will void your warranty
Has anyone made any progress or did all just send back to LG?
I am in similar shape, can get to the white factory reset screen - which does nothing once I accept.
I can also get into download mode, but the phone isn't recognized.
Wanted to confirm before I try to send it back that I can't fix myself.
Thanks!
Also, did anyone who was able to get back to the hard reset screen have luck sending to LG? Or did it have to be completely bricked?
Im also bricked. And there is no recovery mode. download mode is usable. but when i in twrp before brick i deleted efs because i have a back up after that recovery had corrupted and driver in the rom memory to talk to pc had also deleted with efs(i think). I have an idea to fix but im not sure
If I can change rom from mainboard and replace it other rom from other lg g2? Will it solve my and our problem??????
thanks to reply.

SM-N900V "RECOVERY BOOTING" loop

I have a Verizon Galaxy Note 3 (SM-N900V) that is stuck in a boot loop. I get "RECOVERY BOOTING" in blue at the top left corner of the screen. No combination of power, volume up, volume down, or home buttons have any effect. I've tried all combinations. I have to pull the battery to get it out of the boot loop. Any advice?
Toaplan said:
I have a Verizon Galaxy Note 3 (SM-N900V) that is stuck in a boot loop. I get "RECOVERY BOOTING" in blue at the top left corner of the screen. No combination of power, volume up, volume down, or home buttons have any effect. I've tried all combinations. I have to pull the battery to get it out of the boot loop. Any advice?
Click to expand...
Click to collapse
Were you running Safestrap and a custom ROM... or were you totally stock before the phone started bootlooping and did you try to flash anything through Odin or Safestrap before it started? What build version is your phone on (4.4.2, 4.4.4, etc...)? Can you still get into Odin mode?
If you could provide some information, it should help others to give you some suggestions.
If you were rooted and had Safestrap installed, then this thread might provide some useful information to help you get the phone out of the bootloop. If your situation is similar to the others in the linked thread and you think that flashing the NC2 Kernel might get you out of the bootloop... then you should be able to grab the NC2 kernel from Beanstown106’s thread here.
You should also check out Droidstyle's restore guide here, which should help you restore the phone back to factory stock if necessary.
mattnmag said:
Were you running Safestrap and a custom ROM... or were you totally stock before the phone started bootlooping and did you try to flash anything through Odin or Safestrap before it started? What build version is your phone on (4.4.2, 4.4.4, etc...)? Can you still get into Odin mode?
If you could provide some information, it should help others to give you some suggestions.
If you were rooted and had Safestrap installed, then this thread might provide some useful information to help you get the phone out of the bootloop. If your situation is similar to the others in the linked thread and you think that flashing the NC2 Kernel might get you out of the bootloop... then you should be able to grab the NC2 kernel from Beanstown106’s thread here.
You should also check out Droidstyle's restore guide here, which should help you restore the phone back to factory stock if necessary.
Click to expand...
Click to collapse
Hey thanks for the help. I was running Safestrap and the leaked KitKat 4.4.2. There's not much more to say other than in my first post. It just kind of randomly starting happening. All recovery options are failing because I can't get any combination of button presses to register when it's first booting up. This means I can't get into odin mode, bootloader, recovery... anything.
Toaplan said:
Hey thanks for the help. I was running Safestrap and the leaked KitKat 4.4.2. There's not much more to say other than in my first post. It just kind of randomly starting happening. All recovery options are failing because I can't get any combination of button presses to register when it's first booting up. This means I can't get into odin mode, bootloader, recovery... anything.
Click to expand...
Click to collapse
If holding the volume down + home + power buttons all together doesn't work any more to boot the phone into download mode, then it might be worth trying a usb jig to see if it would force the phone into download mode. Here's a listing for a usb jig on eBay that is less than $5 and the seller seems to have good feedback. The listing says it should work on a Note 3. If you'd rather make your own usb jig, there are several guides on YouTube and xda on how to make one.
Before trying the jig... here's an idea to get the phone into download mode...(it probably won't work, but shouldn't hurt anything to try)-- Take the battery out of the phone, then with the micro usb cable plugged into the phone, hold the volume down button on the phone and plug the other end of usb cable into the computer. Hopefully that will turn the phone screen on and prompt you to hit the volume up button to enter download mode.
If you can't get into download mode, then you might see if the Verizon Repair Assistant or Kies Emergency Firmware Recovery would work to restore the phone while in bootloop. I read someone else's post where they said that when using the Repair Assistant, they accidentally updated their phone to 4.4.4, so you'll probably want to research that more before using it so you don't lose ability to root.
If none of these things work, then I can't think of any other ideas other than sending it to someone for jtag repair. Maybe someone else can chime in with some other suggestions.
@Toaplan,
If you haven't been able to fix your phone yet, I was thinking you may also want to check this unbrick thread: ( http://forum.xda-developers.com/showthread.php?p=54534374 ). Per info in the thread... it sounds like jtag isn't an option for our version of the note 3, so please disregard my above comment about jtag.
mattnmag said:
If holding the volume down + home + power buttons all together doesn't work any more to boot the phone into download mode, then it might be worth trying a usb jig to see if it would force the phone into download mode. Here's a listing for a usb jig on eBay that is less than $5 and the seller seems to have good feedback. The listing says it should work on a Note 3. If you'd rather make your own usb jig, there are several guides on YouTube and xda on how to make one.
Before trying the jig... here's an idea to get the phone into download mode...(it probably won't work, but shouldn't hurt anything to try)-- Take the battery out of the phone, then with the micro usb cable plugged into the phone, hold the volume down button on the phone and plug the other end of usb cable into the computer. Hopefully that will turn the phone screen on and prompt you to hit the volume up button to enter download mode.
If you can't get into download mode, then you might see if the Verizon Repair Assistant or Kies Emergency Firmware Recovery would work to restore the phone while in bootloop. I read someone else's post where they said that when using the Repair Assistant, they accidentally updated their phone to 4.4.4, so you'll probably want to research that more before using it so you don't lose ability to root.
If none of these things work, then I can't think of any other ideas other than sending it to someone for jtag repair. Maybe someone else can chime in with some other suggestions.
Click to expand...
Click to collapse
mattnmag said:
@Toaplan,
If you haven't been able to fix your phone yet, I was thinking you may also want to check this unbrick thread: ( http://forum.xda-developers.com/showthread.php?p=54534374 ). Per info in the thread... it sounds like jtag isn't an option for our version of the note 3, so please disregard my above comment about jtag.
Click to expand...
Click to collapse
Hey mattnmag,
Thanks for all the suggestions! This phone isn't my daily driver and I haven't been able to try any of this yet. I'll let you know how I make out when I get a chance to try some of this out. Thanks!

Bootloop fix help. - No recovery.

So, my friend came down to visit in FL from GA.. Her phone ended up snapping in half, but she found an older one in her car. We have since been trying to fix said phone, but nothing has worked. I've used Odin to try and install an OG firmware (which is nearly impossible to find, might I add) and that didn't work. It only made the bootloop issue worse. I also tried to use Odin to put TWRP on it, which showed signs of hope, but gave no real progress to the issue. The recovery menu doesn't exist. The power + vol up + home button doesn't boot to recovery which is why I figured I'd try a custom one. ADB doesn't work because USB debugging wasn't turned on before the phone got destroyed. Idk what happened to the phone before to cause this, neither does she. We simply found it in her car this way. She's going back tomorrow, but has no GPS to find her way, so I'm in desperate need of help. I've tried almost everything I can think of and this stupid phone still won't boot to recovery. I know if I can get it to recovery, I can fix it. Google hasn't been much help either. Everyone always suggests recovery mode, but I can't get to recovery.
Thanks for any help, guys.
Edit: Model # - SM-S920L

Assistance With Bricked Device

Hi all,
Apologies if this has been posted before elsewhere in the forum, I've done some searching but I'm having a real hard time in getting this fixed.
My friend recently bought a Huawei P10 Plus off Facebook, second hand. He went to the guy's house, bought it and then didn't realise until he got home that it was a demo unit and on the back it says "NOT FOR SALE"
He went back to the house and the guy was nowhere to be seen and now they deny all knowledge of selling it.
So, unable to use it without a 15 second timeout going to a demo video - he gave it to me. I've got some experience of unlocking bootloaders, rooting etc. and I thought that I'd give this a bash.
The Vendor Country Info was locked to Country: Demo - so no firmware upgrades would work.
I got the bootloader unlocked (thanks Huawei Israel - no telephone verification) and then installed TWRP. I then proceeded to modify the oeminfo to set the correct country. This restarted the phone and now it's effectively bricked.
When I power it on, I get two options: eRecovery mode (which is useless) or hold down Vol Up, Vol Down + Power to get the EMUI manual updater.
No firmware files are working with the manual updater and the eRecovery doesn't find any packages to install.
Fastboot doesn't work - hold Vol Down + plug in USB cable just goes to the charging icon on screen. Tried with Power + Vol Down - straight to eRecovery.
Vol Up + Power goes to eRecovery, no standard recovery or TWRP recovery option.
I'm at a complete loss now, I'd be happy to get the demo firmware back on so that I can at least give it back and say "I tried", but I can't seem to get ANY firmware to install.
For information, I'm in the UK - so I'd need VKY-L09C440 firmware.
Any help is appreciated and once again, sorry if I'm reposting stuff - but it's a very particular case.
Anyone have any ideas on this?
Looking to get this resolved ASAP, but just at a real dead end with it all.
Hi there, does anyone have any ideas for this? Tried looking around the site, but can't seem to find any ideas anywhere

set warranty bit: kernel error and imei theft

hello, i had a samsung j5 (sm-j500f) its imei has been stolen. i contacted with samsung and they said we can restore your imei if you have it. unfortunately, its box is missing and sticker under the battery erased, so we couldnt figure it out that way. we throw that phone away for a while. a couple days ago i found it and i wanted to give it another chance, but it doesnt open now, no reaction for any button conbination (recovery or download mode) and says set warranty bit: kernel. i realized, this error mostly occurs due to custom rom flashes etc. but in my case, there is no such thing. i was using it with official software. i wonder are these two things (error and imei theft) might be related or is there totally another situation here? are there any chances for getting this phone back to life?
haytalper said:
hello, i had a samsung j5 (sm-j500f) its imei has been stolen. i contacted with samsung and they said we can restore your imei if you have it. unfortunately, its box is missing and sticker under the battery erased, so we couldnt figure it out that way. we throw that phone away for a while. a couple days ago i found it and i wanted to give it another chance, but it doesnt open now, no reaction for any button conbination (recovery or download mode) and says set warranty bit: kernel. i realized, this error mostly occurs due to custom rom flashes etc. but in my case, there is no such thing. i was using it with official software. i wonder are these two things (error and imei theft) might be related or is there totally another situation here? are there any chances for getting this phone back to life?
Click to expand...
Click to collapse
Its normal, you cant fix it. Its not an error, its just the system showing a mini debug interface. Where did you get the phone from? Someone else used it? Bcs they tried to install a custom ROM on it, failed and just left it as that. If you shut down the phone, hold down Powerup button, down volume and home button you will enter download mode where you can install stock ROM and fix this soft brick. Follow this
NecromancerViper said:
Its normal, you cant fix it. Its not an error, its just the system showing a mini debug interface. Where did you get the phone from? Someone else used it? Bcs they tried to install a custom ROM on it, failed and just left it as that. If you shut down the phone, hold down Powerup button, down volume and home button you will enter download mode where you can install stock ROM and fix this soft brick. Follow this
Click to expand...
Click to collapse
thanks for the answer mate, but i guess i needed to give a little bit detail for the problem. i was the first user of the phone, i bought from store not from someone else. so it had original software from the beginning. i am aware these kind of issues mostly caused by flashing custom roms etc. but this is different. i contacted with samsung customer support when this happened and they said they can fix and give its imei number if i give the imei but unfortunately i had nothing. i couldnt find phone box and the sticker under the battery was faded out. i put the phone away for a while and a couple days ago, i found it and wanted to try my luck one more time. one the other hand, you mentioned download mode but i tried all button combinations and no response. if i can enter download mode, i probably would have been flashed original software, but still there is imei problem. i guess i will let this phone go. i cant find any other solution.

Categories

Resources