Boot loader Exception - Samsung Galaxy S7 Edge Questions and Answers

Hi All,
I have S7 Edge Without changing anything i woke up this morning and found this msg on my phone :-
Bootloader Exception
[RST_START = 0x100000000 ]
[...]
Exception: do_handler_serror: SERROR(esr: 0xbf00000000)
[...]
I checked the following thread but no luck :-
http://forum.xda-developers.com/s7-edge/help/s7-edge-bug-t3331878
what should i do ? is there any solution i can use without sending the phone to warranty ( i am sure they will take a lot of time in my country )
I use all the key combination with no luck , the msg keeps running the phone what kind of msg is this ? how to solve it ? why it's happened in the first place ?
Thanks

Reading this thread appears to work.
Not the same exact error, but very similar.
I would say let the battery die completely and then charge it up. Once it's charged for a good bit, turn it on an hopefully it works.
http://forum.xda-developers.com/galaxy-s7/help/s7-dead-red-text-t3335846

Related

Got a bricked X2, please help.

Ok, so i got fed up with my phone freezing so i thought i would get SEUS to
re install the rom, (mr1, mr2 is not available to me yet).
The indicator got to about an inch along when a message popped up saying
update failed.
Now i cannot enter bootloader to try again, the phone will not turn on, SE refuse
to help saying it is not released in the UK so i am not entitled to support.
I have not yet had a reply from where i got it from.
Is there any way to get this piece of junk going again?
Thanks.
Try to charge your battery on another phone / external charger.
I encountered a similar problem when trying to flash the X2. I received the UPDATED FAILED error, pulled out the battery, Volume Down + Power and gave it another try.
SEUS shouldn't brick your phone, maybe it's a problem with your battery.
The battery is at about 80%, i have tried it in my X1 as it is the same battery.
I tried the X1's battery in the X2 as well.
When i press the volume down and power buttons it vibrates for a fraction of a
second and then just stays on a black screen.
Let's try then a forced bootmode connection.
1. Insert the data cable into the phone without the battery plugged in.
2. Open SEUS and go to the connection screen.
3. While the software is searching for the phone, keep VOL DOWN + POWER and insert the battery.
After the phone vibrates, the software should recognize the X2.
This procedure generally applies to dead phones and sometimes works.
Post the result.
Still nothing, i kept the buttons pressed for about 30 seconds, then vista popped up a message 'usb device not recognised' the phone stayed as it did before and SEUS did nothing.
Sadly the support excuse they are using is what a lot of manufacturers do if you are in an area where they don't support it. This is the downside of buying a device on eBay etc. before it is "officially" released in your area. Contact the point of sale and hopefully they can send it in for you. You might have to pay shipping costs.
Leave your battery out and unplugged for an hour and then try again after that to revive it.
I did not even realise it had not been released in the UK, i got it from a UK website.
I am still waiting for them to get back to me, as it is Sunday they won't be getting back to me till Mon Tue i would think.
SE were fast though, less than an hour to reply, about the only credit they get though.
I have had the battery out for more than an hour a few times so that does not work.
Thanks for the suggestions though, keep em coming if there are any more.
WINE GLASS said:
Ok, so i got fed up with my phone freezing so i thought i would get SEUS to
re install the rom, (mr1, mr2 is not available to me yet).
The indicator got to about an inch along when a message popped up saying
update failed.
Now i cannot enter bootloader to try again, the phone will not turn on...
Click to expand...
Click to collapse
The exact same thing happened to me today, but I did not even get the update failed message (but I got the inch )
The phone is now bricked. No bootloader no nothing.
I guess you guys have the Singapore English versions? A lot of those retailers in the UK were getting them through Malaysia and so on. Then selling in the UK but not informing buyers that SE wont support it in the UK yet. It's really sad
It's a French X2, and I got it in France. I think I will have no issue with getting my X2 unbricked (or replaced), SE support is pretty good over here.
But if in the mean time someone has an idea or a trick on how to unbrick a X2 (other than the tips already listed in this thread), I would be happy to test it
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
-kOS- said:
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
Click to expand...
Click to collapse
Wrong phone, wrong forum, wrong idea.
-kOS- said:
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
Click to expand...
Click to collapse
Learn to "Read" and use the "Search" function newb.
Hi!
This has happened to me also. The solution was to connect the original charger (I usually charge from the USB port on my PC).
Try this:
1. Disconnect all cables from phone.
2. Remove battery.
3. Insert battery.
4. Connect original SE charger and charge for 5 minutes.
5. With the charger still connected, press volume down and then power on simultaneously - hold until SE logo appears.
If not working, repeat from step 1 several times (i tried 3 times before it finally worked).
6. Connect PC USB and run SEUS update.
Seems to me like the phone does not always charg from USB, and that when it enters the "black-screen-after-short-vibration-after-power-on"-mode it does not charge while in this mode.
Mod edit: not rom dev related, moved to general
well... when it say update fail but if save the new rom to ur phone then its fine, take the battery out and restart ur phone.. it should load the new OS.. my one says fail everytime.. so no problem for me

[Q] Overheating & Baterry Draining & Hang After about 1 minute

Sorry but i'm just a newbie here. Plz help me ... I'm having someproblem with my SS4 I9500 GSM only model. Just bought it a few days ago and yesterday after I root it with Kingroot everything still ok until I download the TWRP recovery on CHPlay. It show some kind of warning that could affect my SD but I ignore and have it done something to install the TWRP on my phone. After one time reboot my phone started to run real slow , super hot until hang itself and extremely battery draining ( about 25 - 30 % for one time boot till it hang and reboot ). I've tried to reinstall an Original Firmware but couldn't because I can't connect my phone with the PC everytime I tried to connect the cable my PC show the Code Err 23. Device not recognized. . I tried the factory reset but it still operated like that and there's no TWRP but the original recovery of android. Changed the cable , changed the PC , still nothing happened. Someone plz help !!!

Samsung S4 Fullbrick

Hello, first, sorry for my bad english too :\ i'm french
I'm posting this for a friend, unfortunately it is not good at phone and do not understand English. I therefore support myself (by teamviewer).
His phone was purchased in France, he received yesterday, phone clearly worked well, apart if I understand an error message: "Process.android.acore stopped." He tried to update it to Android 5.0.1 (by about => Update, and in my opinion, that's where the problems have begun, its connection is really not stable at all, she interrupted constantly and is also very very very slow, sometimes I wonder if it exceeds 50k / s ... He told me that during the update, he went to see his friends, ( + - 3h download ...) he put his phone on charge a few hours later, he returned home and the problems started and His phone was put out .. It no longer able to restart it.. told me there have no signs of life, here is what has been've already made.
-> Press VOL +, HOME and Power at the same time to get in recovery: No results
-> Press VOL -, HOME and Power at the same time to set download: No results
-> Remove the battery, sim and sd, and press 30sec Power: No results
-> He tested his battery on his brother's phone (also S4) it works, he tested his battery (his brother) in his phone: No results
Nothing appears on the phone, black screen and no LED ... I told him that his phone was probably a DOA (Dead On Arrival), however, I still tried to help because it m ' You said the phone will require three months to repair ..
After more research, I saw that his computer recognized the phone as Qualcomm HS-USB QDLoader 9008. The phone is completely bricked, can you provide me with the necessary files and tell me how I should proceed?
Thank you
If's a SAMSUNG GALAXY S4 I9505
I had the exact same problem with the pc only recognizing qualcomm...
I'm afraid to tell you that the partitions are probably corrupted i gave it to my provider back then which took them 2 weeks to repair i think they switched the so called emmc even though i had knox 0x1 and root so better send it back/ let the seller give it to repair because the waiting time was really killing me xD.
I saw tutorial like this http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 and other to rebuild partition, i'm sure it's possible, but i need help ^^
This is about as bricked as it gets, and software likely isn't going to fix it. This same issue has happened on the Galaxy SII and they haven't found a solution after nearly four years of trying. The phone needs to be serviced.

LG G4c half bricked. Can't connect with pc or start recovery mode. How to fix it?

Hey guys. I tried rooting my LG G4c but after rebootingen it seems that my phone is stuck in a loop, and i can't fix it.
What happens when i turn the phone on:
1. LG logo turn up
2. The following message appears:
[670] --------------------------------------
[670]
[670] Boot verification fail!!
[670] - cause : MISMATCH_SIG_LEN
[670]
[670] --------------------------------------
3. Phone reboots
Using the power button + volume down does NOT work anymore to start recovery mode (although starting the IMEI display still works).
I tried using LG UP to install the original firmware via USB but the device does not show up in the list (probably because the phone keeps rebooting itself). Some website also said to connect the phone with the pc, turn LG UP on, then put out the battery and put it back in to make it work, but that also didn't work.
Anyone know what i can try next? What method can i use to reinstall the firmware? And if it's not possible, does it cost much to repair and who should i ask?
Edit: It seems i can start "Factory data reset" but when this proces starts the phone restarts and continues the loop with the error message.
I also tried connecting the device with LG UP while the phone is stalled on the IMEI screen and the Factory data reset screen. This way the phone does note restart itself and it might appear in the device list of LG UP. But too bad it still didn't work.
I don't know if i'm reaching anyone who can help me, but even a answer from anyone saying that the problem is hard to deal with would already be very relieving I really can't find anything related to this problem on the internet and i'm noobish myself. I'm probably gonna visit a some phone shop down town in the next days because i really don't know what to do.
vanderplate said:
I don't know if i'm reaching anyone who can help me, but even a answer from anyone saying that the problem is hard to deal with would already be very relieving I really can't find anything related to this problem on the internet and i'm noobish myself. I'm probably gonna visit a some phone shop down town in the next days because i really don't know what to do.
Click to expand...
Click to collapse
I had this problem too. I send it to LG and said the phone was unplugged during update process. They flashed it and I gave it to my mom. I have an S4 yet. Much better performance and rom support.
download mode
vanderplate said:
I don't know if i'm reaching anyone who can help me, but even a answer from anyone saying that the problem is hard to deal with would already be very relieving I really can't find anything related to this problem on the internet and i'm noobish myself. I'm probably gonna visit a some phone shop down town in the next days because i really don't know what to do.
Click to expand...
Click to collapse
Can you get it into download mode?

Yotaphone 2 YD206 in Bootloop after update

Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
easyxx said:
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
Click to expand...
Click to collapse
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
kophyo07 said:
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
Click to expand...
Click to collapse
If your phone displays Downloading... and fastboot keeps saying waiting for device then there is something wrong with the installed ADB driver. Check some of the posts in this forum like this one on how to fix this. http://forum.xda-developers.com/yotaphone-one/help/yotaphone-2-yd-206-china-flash-firmware-t3306797/post69311402#post69311402
Strange that you had an OTA (Over The Air update). You didn't do anything between the SIM/Google registration and OTA ?
Normally there are no OTAs allowed on yd206 phones bought from China/HK , where did you buy it ? Chinese retailers have their own firmware that they put on phones , for me , maybe you had bad firmware installed.
The warranty of your phone is voided if you flash yotaphones bought from China and HK .
When you use yotaflasher do you get error message or "waiting for device" ?
To flash the Yotaphone , it should be in developer mode , but you couldn't put it in this mode because it first did the OTA that started your bootloop. Android apps are updated like that ("installing x of 127") when it gets updated to lollipop. Normally the OTA should have worked OK. Did you allow enough time at the Yotaphone logo after the first reboot ? It stays on this logo for 5 minutes before starting. I made this mistake.
The OTA started just after you set up Google etc ?
If so, normal yotaflashing will never work, but at least you havent broken the warranty . The thing we need to know is what exactly happened when you tried to flash , what errors messages appeared ?
If you did not put the phone in developer mode, then you cannot easily flash the phone, so your best possibility is to return the phone. Normally you can contact the seller by chat or email . Some are very good in exchanging.
It IS possible to flash your phone using fastboot, but I would not personally attempt it and you would lose your warranty . You need rootkits, SDK toolkits, universal drivers and images. Google "bootloop without USB debugging".
When I flashed my yd206 , (after many attempts) I flashed my yd206 to yd201 Russian KitKat ROM first and then did an OTA to lollipop.

Categories

Resources