Database Info

Moto g bricked

Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me

Joomlar said:
Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me
Click to expand...
Click to collapse
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.

smohanv said:
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.
Click to expand...
Click to collapse
Or he can ask for replacement
Sent from Samsung Chat

jaspreet997 said:
Or he can ask for replacement
Sent from Samsung Chat
Click to expand...
Click to collapse
I would not wait for two weeks for replacement when we can bring the phone to life within 30min.
I agree a risk element in it. If the phone is basically faulty, then it is not worth trying the way I suggested. Has this worked before you started mess around?
Good luck..

smohanv said:
I would not wait for two weeks for replacement when we can bring the phone to life within 30min.
I agree a risk element in it. If the phone is basically faulty, then it is not worth trying the way I suggested. Has this worked before you started mess around?
Good luck..
Click to expand...
Click to collapse
If the phone is basically faulty (a potential hardware issue) the last thing one should do is unlock the bootloader and lose the warranty.
Sent from my Nexus 5

If you have ordered from flipkart Just call them and pretend that its not turning on at all.....and they will give you a hand to hand replacement!

I can return phone but it cost more then 60 EUR via DHL and i must wait long time...
Today i will try to unlock bootloader and flash firmware. Thanks you all, have you more suggestions?
I dont know what happened. This is strange problem because telephone work fine 5 hours and after power off, i see only Motorola Logo. I hope that i will not miss guarranty when i unlock bootloader.

Unlock device is finished. Can you give me tutorial for flashing stock firmware? I am noob
U used this tutorial: http://www.theandroidsoul.com/install-moto-g-uk-generic-firmwarestock-rom/
but after flashing i have the same problem
Is there any solution? If not, how i can lock bootloader because now i lose guarranty

Joomlar said:
Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me
Click to expand...
Click to collapse
I had exactly the same issue, after I unlocked the bootloader this happened to me, don't worry is not bricked just a software issue with some providers firmwares, what did I do? The good about this is, you should be able to put it in fastboot.
Read all before try it please
* I unlocked the bootloader (seems like you already did it)
* I flashed CWM http://forum.xda-developers.com/showthread.php?t=2563599
Here the next issue was I needed to flash a ROM but I wasn't able to put any file in my device even mouting the USB in CWM or adb push, so: sideload
* I downloaded this rom http://forum.xda-developers.com/showthread.php?t=2606943 (you could use other but that worked for me)
* I Put the zip file in the fastboot directory
* I turned on my device in recovery mode (CWM, you can do it by the fastboot, select recovery, use vol up to enter, vol down to move, power button doesn't work here).
* Wipe factory, cache and dalvik (just in case I think factory wipe is enough)
* I went to the option flash from zip file, flash from sideload (or similar not sure about the name but it says sideload)
adb sideload myromfile.zip
once the adb finish, CWM will notify you and you can flash your rom regularly. It will finish, then you should reboot, It should take about 5 minutes for the first boot. Then my phone worked again.
Sorry if I said something wrong, first time I talk here and I felt identified with your issue and wanted to help you.

Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone

sounds like the phone might be faulty if it happened and you didnt do anything to cause it ,
anyway another option for you is to try a external reset,you have attempted too flash other firmwares so not 100% sure it will work but give it a try through fastboot recovery.
click the link below and halfway down the page follow the instruction for "external reset"
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth

This is my steps:
-Flash this falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB via this tutorial http://www.theandroidsoul.com/install-moto-g-uk-generic-firmwarestock-rom/
-flash CWM V3 or V2
Do i need to flash some other stock ROM before i do external reset? EDIT; external reset does not work becase i can not enter to recovery and wipe data/cache...

smohanv said:
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.
Click to expand...
Click to collapse
Except it isn't a development phone and of course you can brick it. Try erasing the bootloader and recovery and see how you get on then. Im pretty sure it'd be bricked??
To OP - you should have returned phone especially as you are a noob, no offence but a noob trying to recover a phone which has 'broken' by itself is not going to end well especially as its impossible to tell if its hardware or software issue in the first place.
I wish you luck though.

Joomlar said:
Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone
Click to expand...
Click to collapse
To get into CWM after flash it, go to fastboot mode, then in the menu, use ONLY vol down and move to the recovery option, once in the recovery option push vol up.
It also could be you phone has a fault from factory.

scott_doyland said:
Except it isn't a development phone and of course you can brick it. Try erasing the bootloader and recovery and see how you get on then. Im pretty sure it'd be bricked??
To OP - you should have returned phone especially as you are a noob, no offence but a noob trying to recover a phone which has 'broken' by itself is not going to end well especially as its impossible to tell if its hardware or software issue in the first place.
I wish you luck though.
Click to expand...
Click to collapse
You can perfeclty recover an erased or corrupt bootloader, and from there flash anything you want, including recovery. Yeah, it's an unbrickable phone.
http://forum.xda-developers.com/showthread.php?t=2623587

Joomlar said:
Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone
Click to expand...
Click to collapse
i got the same error, but i just kept flashing cwm like five times in a row then vol down then up and it loaded cwm.
try it.

Yes, it can be bricked depending on the version... Mine can't have the bootloader unlocked...
Sent from my XT1032 using xda app-developers app

I must return phone. My bootloader is unlocked, i hope that manufacturer will give me new phone.
IF you have any solution respond me please.

Maybe you could try this way http://forum.xda-developers.com/showthread.php?t=2542219 !?

Joomlar said:
I must return phone. My bootloader is unlocked, i hope that manufacturer will give me new phone.
IF you have any solution respond me please.
Click to expand...
Click to collapse
Your phone seems to be fine. the only option worth a try is to flash official firmware that should go ok with a locked bootloader forget about custom recovery and rooms
and in any case do not unlock the bootloader until you some how solve this and in the picture you posted the phone already is in flash mode just make your PC to recognize your phone by installing the necessary drivers and flash
Find everything you need in the post above mine

Bricked S7?

So I went to flash a Rom with Odin and now I can't get past the recovery screen. The phone will not show up when I plug into USB either. Is this phone officially toast?

Our crystal ball here at XDA is on the blink, unfortunately you're going to have to manually provide more information

Wlane1979 said:
So I went to flash a Rom with Odin and now I can't get past the recovery screen. The phone will not show up when I plug into USB either. Is this phone officially toast?
Click to expand...
Click to collapse
Hi mate
You said past recovery screen in recovery mode?
What firmware you flashed with odin , which files ?
If you can get into download mode there is hope still... can you? , go to recovery factory reset see if you can boot now , if not flash again firmware with odin , to avoid losing data use your home_csc file if that does not work flash again this time using CSC and checking re partition option in Odin

The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.

Wlane1979 said:
The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.
Click to expand...
Click to collapse
Model S7?
ROM you Flashed?
Download mode should still work no matter what you do with firmware tbh

It was a live demo stuck in boot loop. G930x
I'm not sure I remember the file name but it was the stock ldu rom

Wlane1979 said:
The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.
Click to expand...
Click to collapse
But what did you try to flash a custom rom or a stock firmware?
What did you format in recovery?
Sometimes during bootloops getting into download mode is tricky , keep trying
@*Detection* sorry mate i did not see your replies

MAX 404 said:
@*Detection* sorry mate i did not see your replies
Click to expand...
Click to collapse
Don't worry, two heads are better than one
---
Yea OP, as above, getting into DL mode sometimes takes a few attempts, keep Volume Down & Home & Power pressed until the phone reboots twice, after the second reboot keep them pressed and see if it boots into download mode
AFAIK with the demo units you need to flash the G930F firmware to them to unlock
But still no modem or fingerprint reader even after that iirc

But I can't used my pc to flash anymore. It does not show a device connected like if I plug in my s8.

The picture shows where I am stuck

Ok I got past that screen in dl Mode and found the right firmware or so I believe. Odin freezes when trying to add AP file. Without it my phone stays on the load screen. Help!

Wlane1979 said:
Ok I got past that screen in dl Mode and found the right firmware or so I believe. Odin freezes when trying to add AP file. Without it my phone stays on the load screen. Help!
Click to expand...
Click to collapse
Wait, ODIN takes a long time to load AP, and looks like it has frozen, just wait and it will add eventually

Can someone point me to the correct thing I need to download then? There are so many. What do I need since its a sm-g390x?

Wlane1979 said:
Can someone point me to the correct thing I need to download then? There are so many. What do I need since its a sm-g390x?
Click to expand...
Click to collapse
Maybe you can use the emergency recovery from samsung.. with serial number it will flash the correct firmware.

I'm not sure being a live demo unit

Wlane1979 said:
I'm not sure being a live demo unit
Click to expand...
Click to collapse
G930F firmware for demo units

*Detection* said:
G930F firmware for demo units
Click to expand...
Click to collapse
There are many of the 930f I have found but none of which for the United States.

Wlane1979 said:
There are many of the 930f I have found but none of which for the United States.
Click to expand...
Click to collapse
That's because it's an International firmware, use United Kingdom (BTU)

I did the firmware flash. Everything seemed to go smoothly but now I am stuck on a flashing Samsung screen

Wlane1979 said:
I did the firmware flash. Everything seemed to go smoothly but now I am stuck on a flashing Samsung screen
Click to expand...
Click to collapse
Did you use CSC rather than HOME_CSC?
Try booting into recovery and factory reset

Bricked when returning to stock (No command)

Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.

Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.

FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288

cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP

Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)

Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.

Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.

cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.

Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.

cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.

Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.

cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.

Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm

Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.

Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.

cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.

Same situation right now with my S7. Damn.

Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa

Anyone?

I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...

Still stuck in boot loop after successfull odin flash

Looking for some help please! My phone battery died the other day, I plugged it in to charge and turned it on at 3% battery life only to get stuck in a boot loop.
Did a factory reset and then successfully flashed with odin and current firmware G930TUVS9CSC1. After flashing it went to installing a system update screen only getting to about 32%, then it said erasing for a while and went back to the samsung startup screen stuck in apparently the same boot loop I started with.
Is my phone screwed or did I miss something? looking for any help, thanks.

vexcesban said:
Looking for some help please! My phone battery died the other day, I plugged it in to charge and turned it on at 3% battery life only to get stuck in a boot loop.
Did a factory reset and then successfully flashed with odin and current firmware G930TUVS9CSC1. After flashing it went to installing a system update screen only getting to about 32%, then it said erasing for a while and went back to the samsung startup screen stuck in apparently the same boot loop I started with.
Is my phone screwed or did I miss something? looking for any help, thanks.
Click to expand...
Click to collapse
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot

cooltt said:
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
Click to expand...
Click to collapse
Thanks. Appreciate the input, but it didn't work for me after trying it twice. I am positive I have the right firmware.
It boots up with no led indicating light and continues to just flash the opening samsung screen for eternity.

Got the phone to boot up normally but now it wont read my sim card. sim works in my other phone. Any ideas?

vexcesban said:
Got the phone to boot up normally but now it wont read my sim card. sim works in my other phone. Any ideas?
Click to expand...
Click to collapse
SIM reader on phone, blow into hole to dislodge any dust and make sure sim is flat in adapter. Very rarely a software problem with sim not read.

cooltt said:
SIM reader on phone, blow into hole to dislodge any dust and make sure sim is flat in adapter. Very rarely a software problem with sim not read.
Click to expand...
Click to collapse
interesting, it worked fine before this started 2 days ago. I guess maybe the sim card reader broke? theres definitely no dirt in there and it seems to make a good connection (tried a new sim card had lying around and it etched lines into the sim card nicely).
Also I should mention that I had no clue what I was doing and flashed a dozen or so different versions of firmwares probably like 20 times, so maybe I caused it.

vexcesban said:
interesting, it worked fine before this started 2 days ago. I guess maybe the sim card reader broke? theres definitely no dirt in there and it seems to make a good connection (tried a new sim card had lying around and it etched lines into the sim card nicely).
Also I should mention that I had no clue what I was doing and flashed a dozen or so different versions of firmwares probably like 20 times, so maybe I caused it.
Click to expand...
Click to collapse
Er.... Yes!
You have to flash the correct region firmware for your device or you end up with problems like you have.
Search for the SamFirm tool on here it's great for getting the correct firmware direct from Samsung servers.

cooltt said:
Er.... Yes!
You have to flash the correct region firmware for your device or you end up with problems like you have.
Search for the SamFirm tool on here it's great for getting the correct firmware direct from Samsung servers.
Click to expand...
Click to collapse
Okay well that tool's forum post says it's deprecated so I followed the alternative link to updato and got stock 8.0 from there. Flashed phone, everything works 100% but still no sim detected.
I'm wondering If I broke my phone because I even tried some custom rom with a pit file and probably did that wrong as well.

vexcesban said:
Okay well that tool's forum post says it's deprecated so I followed the alternative link to updato and got stock 8.0 from there. Flashed phone, everything works 100% but still no sim detected.
I'm wondering If I broke my phone because I even tried some custom rom with a pit file and probably did that wrong as well.
Click to expand...
Click to collapse
PIT won't do anything to SIM.
Try all of these

Hey i am having the same problem odin flash with succes but the phone still only shows the first samsung glaxy s7 screen and then reboots.
Also i cant acces recovery.

i have the same problem
Huzalio said:
Hey i am having the same problem odin flash with succes but the phone still only shows the first samsung glaxy s7 screen and then reboots.
Also i cant acces recovery.
Click to expand...
Click to collapse
hi, did you find a way to fix it?

@cooltt I made an account here in order to thank you! I was stuck in a boot loop after flashing a stock ROM and your advice saved my phone. I thought I bricked it!!

q-l-p said:
@cooltt I made an account here in order to thank you! I was stuck in a boot loop after flashing a stock ROM and your advice saved my phone. I thought I bricked it!!
Click to expand...
Click to collapse
Glad I could help

cooltt said:
It sometimes does this, make sure the firmware your using is correct for your device and flash again.
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
Click to expand...
Click to collapse
I'm having this same issue but it won't boot into recovery at all, I don't know what to do.

iroveashe said:
I'm having this same issue but it won't boot into recovery at all, I don't know what to do.
Click to expand...
Click to collapse
First MAKE SURE you are flashing correct firmware for your device.
What device do you have and what country?
If you are sure it's correct. Flash again with Odin but uncheck "auto reboot" in options.
When pass appears just disconnect phone, it doesn't matter what it shows on the screen.
In this sequence press and hold the following... Volume down+home+power.
As soon as the screen goes black move your finger to Volume up while still pressing home+power. It may take several attempts.
When recovery menu appears wipe cache partition then reboot.
Leave phone go through boot sequence, ignore what appears on the screen during this time it is normal. This boot should take around 5 minutes.

EDIT: FIXED, I did what you did, but for that to work I had to flash it without the hidden.img. Then it rebooted and got stuck on the logo again, but i was able to boot into recovery. Thank you so much.
cooltt said:
First MAKE SURE you are flashing correct firmware for your device.
What device do you have and what country?
Click to expand...
Click to collapse
Hey, thank you for responding.
I'm not 100% sure it's the right one
Device: Samsung A510M
Country: Argentina
Carrier: Personal
I downloaded a firmware from sammobile matching those specifications, but it fails at the last step with hidden.img.
This morning I downloaded another firmware through samfirm, but that one fails at modem.img instead.
I will try your instructions with either of them.
---------- Post added at 07:01 PM ---------- Previous post was at 06:06 PM ----------
cooltt said:
As soon as the screen goes black move your finger to Volume up while still pressing home+power. It may take several attempts.
Click to expand...
Click to collapse
To be clear, I only need to repeat this part of the process, not reinstall the firmware every time, correct? I've been trying to do this for a while, but it just shows:
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."

S10e Literally stuck in bootloops after 2020 Update

So i updated my phone automatically yesterday from the latest update, after it was done, i haven't been able to access my phone in anyway, it keeps on looping samsung logo and a window that says "This phone's bootloader is unlocked´and its software integrity can't be verified" and so on, ive tried to enter either Download mode and recovery mode, but none of the methods seems to have an affect on the phone at all, please help, thanks

Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.

FakerS3 said:
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
Click to expand...
Click to collapse
- The phone does not show up on the pc either

Was your phone rooted? That could explain it.

riggerman0421 said:
Was your phone rooted? That could explain it.
Click to expand...
Click to collapse
Yes

thorius95 said:
Yes
Click to expand...
Click to collapse
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?

chibuche said:
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
Click to expand...
Click to collapse
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way

Never attempt to update if you have rooted and made any changes to the system, deleted or added system apps, modified kernel, changed boot logo,etc.

thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
So, here's how I put the phone in download mode.
I left the battery to drain completely, then without pressing the power button, I pressed the volume down and Bixby button; and only then I plugged the cable. Without pressing the power button, the phone started straight into Download mode.
Now Odin sees the phone, I'm about to flash it with the stock firmware and see what happens.

thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
Maybe this thread helps: https://forum.xda-developers.com/galaxy-s10/help/galaxy-s10-bootloop-updte-to-android-10-t4023201
It's probably Samsung's vaultkeeper that caused the bootloop.

thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
I just wanted to give an update of how I rescued my phone and kept all the information on the phone memory intact (this was one of the challenges, as I had some photos on it).
I put it in download mode by draining the battery, then tried to flash the updated firmware. It didn't work, leading once again to boot loop and all I could do was boot to the stock Android recovery - not helpful.
So I got it to download mode again and flashed the stock firmware it originally came with (prior to the update). In Odin, I put HOME_CSC in the CSC field, to keep the phone memory from being erased. This solved it.
Hope this info can help someone having the same issue.