Hello!
Today a bought a samsung galaxy s6 for a cheap buck because the phone had entered a bootloop and the owner didn't know how to fix it. Easy fix I thought and first went through all the basic steps of charging it, wiping cache and doing full wipe but no change.
I then tried to flash a new stock firmware which seemingly worked because it started the erasing procedure but then went back to the samsung logo and the bootloop continued.. I've also tried wiping cache and full wipe after installing the new firmware.
Worth mention is maybe that the firmware version is 5.11.
Does anyone know any more steps I can take to try and fix this error? Or is it simply broken and needs to be fixed by Samsung?
Thankful for any advice!
Edit:
Device is: SM-G920f
Related
@mods
I hve a p5110 tab2 which had a problem of hanging earlier and i thought of flashing a 4.1.2 thru odin shall fix the issue! but nothing like this happened and the phone developed a new problem of rebooting constantly on samusng logo!
ive tried flashing different version roms from 2.3.6 to 4.1.2 and eveything in between, it did how a ever come to life once, but with always android error popping up on the menu, so i had to upgrade again, but it remains the same! does anybody have an idea or solution to fix this problem?
appreciate
WBR
ReyTech.
I trust you have confirmed that the ROMs were for P5110? although I have seen cases of cross-platform.
The issue you have mentioned is common among where software upgrades are done such as flashing from CM to Samsung or when there are major updates where the framework of the ROM may be different...without wipe or cache cleaning prior to flashing, preventing the device to boot properly, thus causing the hang/reboot...
Boot into recovery, wipe device and clear cache and then flash again through Odin the 4.1.2 ROM. Done.
Thanks for ur reply, ive done tht earlier, but nothing, its stil the same, anything else to try?
Sent from my GT-N8000 using Tapatalk 2
Wait you flashed a 2.3.6 Rom on a Galaxy Tab 2? Are you sure these Roms you're flashing are for the p5110? The p5110 never had Gingerbread available on it.
Try wiping everything in recovery.
Format /System
Format /Data
Format /Cache
then flashing the a Rom for your tablet.
Tks I tried even this but doesnt work
Sent from my GT-N8000 using Tapatalk 2
Wide cache
Dalvik cache
Factory reset
Flashrom for p5100
Update 03/28: Problem resolved with assistance from BadaB!ng developer of collective rom. Thank you for the help. Will post reference link.
Update 03/27: Problem not resolved. 4.04 system was some factory test image and everything I tried to flash or update caused the problem to repeat.
Problem resolved: tried the 4.04 image odin flashed
Model: GT-N8013
User Level: Idiot (Me)
I was playing with the pimp my rom app believing that it was a part of the Collective 5.1 rom, which is 100% my fault. Rebooting is a part of the completion of those tweaks and upon reboot, I could not get passed the samsung galaxy note 10.1 screen. I tried a restore and still stuck. I decided to odin flash back to stock and I am still stuck. I then went into recovery and did a factory wipe and reset. Still stuck. It did say that it could not mount /efs during the process [Invalid Argument]. I am in passed my knowledge base and am hoping another knows what to do.
Thank you for your time.
fftlambet said:
Problem resolved: tried the 4.04 image odin flashed
Model: GT-N8013
User Level: Idiot (Me)
I was playing with the pimp my rom app believing that it was a part of the Collective 5.1 rom, which is 100% my fault. Rebooting is a part of the completion of those tweaks and upon reboot, I could not get passed the samsung galaxy note 10.1 screen. I tried a restore and still stuck. I decided to odin flash back to stock and I am still stuck. I then went into recovery and did a factory wipe and reset. Still stuck. It did say that it could not mount /efs during the process [Invalid Argument]. I am in passed my knowledge base and am hoping another knows what to do.
Thank you for your time.
Click to expand...
Click to collapse
This happened from pimp my rom?
Sent from my GT-N8013 using XDA Premium HD app
seshaz said:
This happened from pimp my rom?
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
I have no way to confirm that, however, that is where I made the last change that required root and reboot occurred. From that reboot, I could only get to the Samsung Galaxy Note 10.1 screen. I need to make an update...I was mistaken when I said it was fixed. The 4.04 image that I flashed worked but was not complete...no lock screen, had some factory test program on it, and anything new I flashed or updated to resulted in getting the screen stuck on Samsung Galaxy Note 10.1 again. I am trying to find other images to odin flash or another instance of this issue.
Hello there !
I can't toggle on Bluetooth in my GT-P3110 recently.. I'm not on airplane mode.. but WiFi works though...
I even flashed a CM ROM(10.1.3 right now) to see if it works.(may be an silly deed.. I'm just new to these android things)
I have uploaded two videos which shows what really happens when trying to turn on bluetooth...
When I was using the stock rom
After flashing CM
I think that I'm having some hardware failure (i.e. dropping the unit - I never dropped myself.. idk if it happened actually as I share this tablet with my family )
I want to know whether this can be repaired ?.
Is there a seperate accessory inside for Bluetooth which can be replaced ?
Thanks in advance !
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
katsika said:
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
Click to expand...
Click to collapse
Thanks for the reply... I noticed the issue when I was on stock stock ROM. I may have to send it to Samsung.
Thanks for the support :highfive:
Is it possible you have another kernel other than stock?
Sent from my XT907 using xda app-developers app
i dont use this forum as i have a different phone and i dont particularly want to sift through every thread to find an answer so i thought id ask to find out for myself
my partner owns a stock unrooted totally unmolestered original moto g running android lollipop and earlier today it started to lag and flashed up with an error she didnt have time to read, not long after it completely froze so i tried to turn it off and on again. after trying to turn it on again it has gone in to a bootloop and will not start properly.
any help on a solution would be much appreciated if anyone can help me ASAP.
cheers
Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.
audit13 said:
Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.
Click to expand...
Click to collapse
any guides on how to wipe the cache without rooting it? im assuming id have to use fastboot or adb or whatever but the internet hasnt exactly helped me with any solutions
Just wipe by booting into stock recovery.
http://www.android.gs/enter-recovery-mode-motorola-moto-g/
Okay,
So my phone was working fine, until I tried to install Xposed on my phone. My phone restarted, but instead of working, it was stuck at the Verizon logo. I tried doing everything.
When I tried factory resetting it said it wiped the data. I pressed reboot system, and it came up as Samsung and then "custom." I don't know how to get rid of the custom thing. I can't flash the stock fireware as I don't have any money to buy it.
Someone please help me get my phone working again. I don't care if it rooted or not.
Fritz6446 said:
Okay,
So my phone was working fine, until I tried to install Xposed on my phone. My phone restarted, but instead of working, it was stuck at the Verizon logo. I tried doing everything.
When I tried factory resetting it said it wiped the data. I pressed reboot system, and it came up as Samsung and then "custom." I don't know how to get rid of the custom thing. I can't flash the stock fireware as I don't have any money to buy it.
Someone please help me get my phone working again. I don't care if it rooted or not.
Click to expand...
Click to collapse
Next time you install xposed and it won't boot, all you have to do is flash the xposed uninstaller zip for your version of xposed.
Your firmware should be available without having yo pay for it. Go to Sammobile .com or samsung-updates .com and search there using your model number.
Or do a google search for:
"Return to stock (your model number)"
Sent from my SCH-I535 using Tapatalk