Galaxy A5 having issues booting after firmware flash - Galaxy A3, A5, A7, A8, A9 Android Development

Hello, people of XDA,
I had decided to restore my Galaxy A5 2015 (A500FU) back to TouchWiz. I had used Odin to flash the firmware back, and I had done the usual, flash into AP and left Auto-Restart on. I then realised, when the device was supposed to boot up, the screen when black and the phone turned off. I tried booting into download mode and into the recovery mode but nothing doesn't seem to work. I have even tried charging it but after 30 minutes, nothing seems to happen, even if I try to start up to download or recovery mode.
Help would be very much appreciated.
Thank You,
Josh
DEVICE DETAILS:
SAMSUNG GALAXY A5 2015
THREE NETWORK (H3G)
A3500FU MODEL
FIRMWARE FLASHED: ANDROID 4.4.4 A3500FUBTU

Why did you flash a firmware with and android version of 4.4.4 a.k.a kitkat? The latest is Marshmallow 6.1.0. What version of android did u have before u flashed kitkat? I think you flashed an old firmware over a more recent bootloader, which means u will be stuck and bootloop. Also, can you describe a bit more about what the problem of your device - like what actually happens when you hold the power button etc. Does you display turn on? You said u left it for charging for 30 Mins and the device still did not turn on... might be hardware related. When you try to boot into download mode or recovery, what happens on device? Please answer my questions and we might get closer to solving your problem.

InfernoWolf19 said:
Why did you flash a firmware with and android version of 4.4.4 a.k.a kitkat? The latest is Marshmallow 6.1.0. What version of android did u have before u flashed kitkat? I think you flashed an old firmware over a more recent bootloader, which means u will be stuck and bootloop. Also, can you describe a bit more about what the problem of your device - like what actually happens when you hold the power button etc. Does you display turn on? You said u left it for charging for 30 Mins and the device still did not turn on... might be hardware related. When you try to boot into download mode or recovery, what happens on device? Please answer my questions and we might get closer to solving your problem.
Click to expand...
Click to collapse
Hey, i have galaxy a500f and flashed android 5.0 firmware on it . I want to flash custom recovery on it but unable to find oem unlock option in developer mode. I also flash android 6 firmware but same problem oem option not showing. Why this happen to my device?

karan68 said:
Hey, i have galaxy a500f and flashed android 5.0 firmware on it . I want to flash custom recovery on it but unable to find oem unlock option in developer mode. I also flash android 6 firmware but same problem oem option not showing. Why this happen to my device?
Click to expand...
Click to collapse
I had the same problem but I still somehow rooted and installed twrp on my device without ever using oem unlock . I am pretty unsure on how I did it but I think I just used CF-Auto Root and then installed twrp later. The CF root file just rooted my phone somehow without me even finding the oem unlock. Just to say, if you are going to use CF, do at your own risk - Just search up how to root SM-a500F

InfernoWolf19 said:
I had the same problem but I still somehow rooted and installed twrp on my device without ever using oem unlock . I am pretty unsure on how I did it but I think I just used CF-Auto Root and then installed twrp later. The CF root file just rooted my phone somehow without me even finding the oem unlock. Just to say, if you are going to use CF, do at your own risk - Just search up how to root SM-a500F
Click to expand...
Click to collapse
I just rooted phone with cf auto root but can't install twrp . Phone gets booted to stock recovery istead of twrp , however phone is rooted but no twrp

karan68 said:
I just rooted phone with cf auto root but can't install twrp . Phone gets booted to stock recovery istead of twrp , however phone is rooted but no twrp
Click to expand...
Click to collapse
You tried flashing the twrp from device or odin?

InfernoWolf19 said:
You tried flashing the twrp from device or odin?
Click to expand...
Click to collapse
I flashed with odin method and also with flashy.
when i root phone with cf auto root method it gets rooted with su app installed then i install flashy app to flash recovery , then flashy app said recovery installed successfully but when phone reboot it again open stock recovery.

InfernoWolf19 said:
Why did you flash a firmware with and android version of 4.4.4 a.k.a kitkat? The latest is Marshmallow 6.1.0. What version of android did u have before u flashed kitkat? I think you flashed an old firmware over a more recent bootloader, which means u will be stuck and bootloop. Also, can you describe a bit more about what the problem of your device - like what actually happens when you hold the power button etc. Does you display turn on? You said u left it for charging for 30 Mins and the device still did not turn on... might be hardware related. When you try to boot into download mode or recovery, what happens on device? Please answer my questions and we might get closer to solving your problem.
Click to expand...
Click to collapse
i'm so sorry for not replying quickly, the device is completely unresponsive, wont even vibrate or charge. thats all i can say, its unusable. i will probably check the device for hardware issues soon.

Hi,
First check your device model is a500fu,
And check you flashed wich version twrp a3500fu
And flash file.i think file you flashed mismatch.
Conect charger and long press volume down button and power button .check booting or not.if not boot
Confirm wrong flash file you flashed...

Related

Bricked or Boot loop - help needed

Hi people!
I got bricked my galaxy mini gt-s5570, but not totaly (that means I can still use the download mode, and RAMDUMP ARM9 mode) but I can't power up the phone. That happened after I used ODIN for gt-s5570 and changed the Kernel (I forgot to make backup before), and device was working well with the new kernel, but after it I use the same step in ODIN to get back to the old one. So the result is, when I'm pushing the power key the screen starts to blinks and nothing more! But as I say download mode, and ARM9 mode are still working. Any solution for this?
just download the new firmware from samfirmware.com n flash it thru odin as u can go to download mode..n ur phone will be back to life again..
i accidently pressed thanks on ur first post
I can't, I don't have access to recovery mode, it doesn't work!
Explainations
ybregeon said:
I can't, I don't have access to recovery mode, it doesn't work!
Click to expand...
Click to collapse
I mean even when I flash an official rom with Odin, I still have the same problem, I am trying this since three days now and noway...
i think you tried to upgrade firmware not boot whenever you upgrade firmware it cant be downgrade it can just be more upgraded when you downgrade your firmware it will not boot up it will just show a black screen so just reinstall the firmware again and do not try to downgrade it

[SOLVED] HELP PLZ! xperia TL in eternal bootloop

Can s/o please point me in the right direction? I have a brand new Xperia TL. I followed the directions on the All-In-One Readme thread to root the phone, which came with locked bootloaders. Then I tried flashing the rom- [AOKP][JB] Xperia T - KangXperiaProject - [milestone 1].
Then the phone turned off, and when I turned it on all that happened was the Sony boot logo came up, then a fuzzy/staticky screen with random colors, then the phone shuts off, and then turns on again, and then the same thing. The battery isn't removable so I can't do a battery pull.
I managed to get the phone into Flash mode for Flashtool, tried flashing a kernel, but nothing happened. I tried all the different key combos to get into recovery, but no dice. I was actually lucky that once it remained stable long enough to flash a kernel, but usually when it's connected to the comp it won't stay on long enough to do much of anything. I also tried accessing the phone with an ADB shell, but that won't read the phone.
I also searched and searched and searched for possible solutions, but can't seem to find any posts (on XDA or otherwise) that deal with this specific set of issues.
Any help would be tremendously appreciated!!
You cannot flash custom rooms that are not stock based with a locked bootloader.
That is because you cannot flash custom kennels with a locked bootloader.
Flash a stock ftf with flashtool to fix your phone.
To do a virtual battery pull then press and hold the power button and volume up button until the phone vibrates
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
Thanks for the info. I tried flashing a stock ftf (I think the LT30_7.0.A.3.195_kernel.ftf you provide in the readme thread), but then it just want back to bootlooping.
Is there a different one I should flash? Or is there something else I could do? Meanwhile, I'll try flashing again when I get home today.
aryeh00 said:
Thanks for the info. I tried flashing a stock ftf (I think the LT30_7.0.A.3.195_kernel.ftf you provide in the readme thread), but then it just want back to bootlooping.
Is there a different one I should flash? Or is there something else I could do? Meanwhile, I'll try flashing again when I get home today.
Click to expand...
Click to collapse
Try flashing a ftf for a TL model.
Where can I find one....?
gregbradley said:
You cannot flash custom rooms that are not stock based with a locked bootloader.
That is because you cannot flash custom kennels with a locked bootloader.
Flash a stock ftf with flashtool to fix your phone.
To do a virtual battery pull then press and hold the power button and volume up button until the phone vibrates
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
Click to expand...
Click to collapse
I flashed the ftf again- the phone still bootloops, but sometimes it show an image of a phone and the triangle with the ! in the middle- which I know is Download Mode on my old phone (Samsung Captivate). Is this what's supposed to happen? If yes, what's the next step? If not, what else can I do?
Thanks so much gregbradley!
aryeh00 said:
I flashed the ftf again- the phone still bootloops, but sometimes it show an image of a phone and the triangle with the ! in the middle- which I know is Download Mode on my old phone (Samsung Captivate). Is this what's supposed to happen? If yes, what's the next step? If not, what else can I do?
Thanks so much gregbradley!
Click to expand...
Click to collapse
TL version
http://forum.xda-developers.com/showpost.php?p=33744425&postcount=56
Thank you gregbradley and hkjr.
I was having trouble flashing an ftf b/c the phone kept shutting off in the middle of a flash. What I did was flash (the T version) piece-meal; I checked "Exclude" for all the components except the 1st, flashed, then checked "Exclude" for all except the 2nd, flashed, etc., and IT WORKED!!
Then I flashed the TL version ftf, rooted it, and all was good. Now it was time to flash a custom rom. I flashed recoba23's Xperia Curiosity V1.2 Rom (for locked bootloaders). That worked. Then I wanted to take a look at TiMiN8R's XperimenT rom. The phone told me that the file finished downloading. I thought it was a little smaller than indicated on the download page, but the phone said the download was complete. Flashed it. Then BRICK. Dunno if it's because the full file didn't download, but now ALL I get is the Sony splash screen (no bootloop, just stays like that). I can't get into recovery and I can't get the phone into flash mode, although the computer does recognize it when I plug it in and I can access the files on the phone.
Any ideas what's going on??
same problem please help =(
I too have the same problem, stuck at "SONY" screen can't go to recovery mode, can't connect to pc, i did the power+up volume button, turns off but if i turn it on same result stuck at sony... I followed this method http://forum.xda-developers.com/showthread.php?t=2020796 for locked bootloader, i have the att xperia TL.
I flashed the generic 7.0.A.1.303 ftf
Rooted using Bin4ry's method
Install CMW for locked bootloaders
Enter recovery, factory reset and flash the ROM(STOCK ROOTED 7.0.A.3.195)
and when im going to flash the flashable CMW, i cant find it in my ext sd.. i put it with stock rooted 7.0.A.3.195.zip and superuser.zip, it says "file not found" on recovery after i flashed the stock 7.0.A.3.195.zip so i decided to reboot.. and this happened. Is there a fix to this please help us :crying:
OK, I got my phone back up and running! For me, it just seemed to be a matter of playing around with the buttons and the plugging/unplugging the phone from the computer and/or charging it, and eventually it went into flash mode. I was able to flash stock kernel, root and apply CWM, then made sure that I downloaded the whole file for whichever ROM I wanted, flashed it, and all was good!
fatedcircle9, just try playing around with it. If you can't flash the new CWM from recovery right after you install the ROM, just reboot the phone, attach it to the computer, and install CWM like you did before. At least that's what worked for me....

[Q] Issue on GT-N7000

Hi Team XDA,
I am facing issues with my GT-N7000
1. I was running on Slim saber 4.4.4 with TWRP
2. I flashed CWM 6.0.4.5 in TWRP and after restart my phone went in to Bootloop.
3. Then I restarted my phone on Download mode and flashed Stock Rom 4.1.2 from Sam Mobile on my GT-N7000 using Odin
4. It Stuck on Samsung logo again
5. I was trying to boot recovery mode but it was not booting (to wipe Data/Cache/Dalvik Cache)
6. I am able to start phone in Download Mode only and not Recovery mode. (using Hardware Keys)
Can anyone help me out coming out of this. I still believe if i can wipe my data/Dalvik/System Cache using ODIN my phone will start.
NikhilDj26 said:
Hi Team XDA,
I am facing issues with my GT-N7000
Can anyone help me out coming out of this. I still believe if i can wipe my data/Dalvik/System Cache using ODIN my phone will start.
Click to expand...
Click to collapse
kinda strange issue,
usually if you've already flashed the original Samsung firmware, it will come together with "built-in" recovery which "possible" to be access in any circumstances,
hmmm, try to do odin again, with different frimware version from different country (I also didn't use my own country firmware) :silly:
by default, try to disable "auto-reboot" option on the odin,
once you've complete flashed the firmware, try to remove the battery for moment, and boot into recovery,
should be working
give it a try, I used to do it in my S Plus, :silly:
kazuna69 said:
kinda strange issue,
usually if you've already flashed the original Samsung firmware, it will come together with "built-in" recovery which "possible" to be access in any circumstances,
hmmm, try to do odin again, with different frimware version from different country (I also didn't use my own country firmware) :silly:
by default, try to disable "auto-reboot" option on the odin,
once you've complete flashed the firmware, try to remove the battery for moment, and boot into recovery,
should be working
give it a try, I used to do it in my S Plus, :silly:
Click to expand...
Click to collapse
Nope. Its not booting in Recovery mode. I tried installing firmware from different countries.. but same case.
Even with CWM it is not booting in recovery.
NikhilDj26 said:
Nope. Its not booting in Recovery mode. I tried installing firmware from different countries.. but same case.
Even with CWM it is not booting in recovery.
Click to expand...
Click to collapse
hmm, strange, however I did do some research for this kind of issues,
and most of my finding stated it might to do with hardware issues (case where unable to boot normally, only download mode),
however, I do believe you can try with older version of firmware (probably last year?)
and try disable "auto-reboot" on the odin,
upon odin stated "reset" quickly pull out the battery (providing the screen is completely closed/off)
and try to reboot into recovery mode by it combinational keys, "volume up + home + power" (hold it a bit longer till samsung logo disappear) :silly:
I've even try to soft-bricked my S Plus, and try this one, seems I can boot both normally and recovery (to do wipe)

Note 4 stuck in TWRP boot loop after factory reset of CM 12

About a month ago I flashed CM 12 onto my Note 4 with no problem and the phone worked great. However, I have now purchased a new phone to replace my old device and wanted to give my Note 4 to my mom and so I factory reset the device in CM 12. Now the phone is stuck in a TWRP bootloop and I have tried numerous times to access the recovery mode (power + vol. up + home button) but to no avail I cannot access recovery mode on the device.
I have tried flashing the stock ROM using Odin, but it did not work because when attempting to flash the stock all I get is an error (imgur .com/ THOYjjI) [remove the spaces, sorry the photo was taken using my phone as I was using my mom's Windows laptop for Odin and pasted the text into notepad] I am able to access the download mode (power + vol. down + home button)
I have even tried ADB and Fastboot, but I was unable to figure out to properly work the command prompt as well as configure the phone at the same time
I hate to sound desperate, but I have been trying to remedy this problem for about 2 days now and I am getting extremely frustrated at this point as I feel as though I have scoured the internet for any possible answer. Anyone please help I appreciate any input.
BunniiButt said:
About a month ago I flashed CM 12 onto my Note 4 with no problem and the phone worked great. However, I have now purchased a new phone to replace my old device and wanted to give my Note 4 to my mom and so I factory reset the device in CM 12. Now the phone is stuck in a TWRP bootloop and I have tried numerous times to access the recovery mode (power + vol. up + home button) but to no avail I cannot access recovery mode on the device.
I have tried flashing the stock ROM using Odin, but it did not work because when attempting to flash the stock all I get is an error (imgur .com/ THOYjjI) [remove the spaces, sorry the photo was taken using my phone as I was using my mom's Windows laptop for Odin and pasted the text into notepad] I am able to access the download mode (power + vol. down + home button)
I have even tried ADB and Fastboot, but I was unable to figure out to properly work the command prompt as well as configure the phone at the same time
I hate to sound desperate, but I have been trying to remedy this problem for about 2 days now and I am getting extremely frustrated at this point as I feel as though I have scoured the internet for any possible answer. Anyone please help I appreciate any input.
Click to expand...
Click to collapse
I see you are pushing COD6, were you on DOK2 prior to installing CM? If so, you cannot odin cod6, only DOK2 and above.
Alternatively, if twrp is jacked up, can you repush twrp from odin for a fresh recovery?
One more edit....you reset from within cm, correct? Have you tried reseting from twrp? You didn't reset in twrp and wipe the system did you?
I apologize, but could you please "dumb" down what you said...
When I factory reset my Note 4 the device was running Cyanogenmod 12 nightly and I did not think to go to the TWRP recovery before hand and had simply factory reset the phone through Cyanogenmod. The phone is currently stuck in the "teamwin" boot loop and if possible I would like to flash the stock ROM or just at least boot into Cyanogenmod. I believe the phone is bricked at this point and if possible I would like to save it.
If someone could kindly explain in layman's terms and detail how to use ADB and Fastboot to possibly fix the device. I would appreciate it. Thank you.
BunniiButt said:
I apologize, but could you please "dumb" down what you said...
When I factory reset my Note 4 the device was running Cyanogenmod 12 nightly and I did not think to go to the TWRP recovery before hand and had simply factory reset the phone through Cyanogenmod. The phone is currently stuck in the "teamwin" boot loop and if possible I would like to flash the stock ROM or just at least boot into Cyanogenmod. I believe the phone is bricked at this point and if possible I would like to save it.
Click to expand...
Click to collapse
Do you know what touch wiz base it was on prior to loading CM? If it was the latest 5.1.1 (firmware ending in DOK2), then the firmware 5.0.1 (COD6) that you are trying to Odin will be blocked (security related). If you don't know, I would try DOK2 or EPE3 (6.0.1). Honestly Marshmallow has been great on my device and I left CM to go back to stock touch wiz with Systemless root.
Edit: if you load DOK2 or EPE3, you will be blocked from downgrading.
---------- Post added at 03:55 PM ---------- Previous post was at 03:52 PM ----------
BunniiButt said:
If someone could kindly explain in layman's terms and detail how to use ADB and Fastboot to possibly fix the device. I would appreciate it. Thank you.
Click to expand...
Click to collapse
I can't help here with Samsung devices. I only use ADB with my nexus devices and only Odin with Sammy.
nine5raptor said:
Edit: if you load DOK2 or EPE3, you will be blocked from downgrading.
Click to expand...
Click to collapse
When flashing CM 12 I believe I had the latest version of Marshmallow, but since you are saying that I will blocked that means I cannot flash my phone to stock ROM?
Dok2=lollipop pe3=marshmallow you can't downgrade the bootloader from dok2 to cod6 for security... but you can flash stock dok2 instead... OR the new pe3 mm update throught odin. (you can get these from sammobile) Have you tried pulling your battery reinsert in it and booting into recovery? If that's not working. Into download mode and reflashing twrp with odin?

Note5 Softbrick Issue

Hi,
My Note5 N920C is currently softbricked. It occurred during the rooting process, where Odin crashed as i was flashing a kernel and rendered my phone virtually useless. When the phone turns on, it goes immediately to a blue screen with a message telling me to use the "Emergency Recovery feature on Smart Switch." Smart Switch when ran on my PC would not recognise the phone, so that option is out of the question.
The phone from this screen can be put into the TWRP recovery mode too, but as the Note5 has no MicroSD slot, this is not that useful. It can also enter download mode, which is where i think the solution could lie. Would i be able to flash onto the phone using Odin and the download mode, or would that not work/make things worse?
Any ideas welcome,
Cheers,
James
Jameswebb97 said:
Hi,
My Note5 N920C is currently softbricked. It occurred during the rooting process, where Odin crashed as i was flashing a kernel and rendered my phone virtually useless. When the phone turns on, it goes immediately to a blue screen with a message telling me to use the "Emergency Recovery feature on Smart Switch." Smart Switch when ran on my PC would not recognise the phone, so that option is out of the question.
The phone from this screen can be put into the TWRP recovery mode too, but as the Note5 has no MicroSD slot, this is not that useful. It can also enter download mode, which is where i think the solution could lie. Would i be able to flash onto the phone using Odin and the download mode, or would that not work/make things worse?
Any ideas welcome,
Cheers,
James
Click to expand...
Click to collapse
Enter Download mode and flash your official variant firmware. Since this is result of an Odin crash it MUST be a full official firmware so you can be sure all your partitions are correctly flashed, bl,sbl,cp, etc...
Sent from my SM-N930F using Tapatalk
Rx8Driver said:
Enter Download mode and flash your official variant firmware. Since this is result of an Odin crash it MUST be a full official firmware so you can be sure all your partitions are correctly flashed, bl,sbl,cp, etc...
Click to expand...
Click to collapse
Thanks a lot, this worked out all fine. Reflashed the stock Rom and booted up all fine.
Jameswebb97 said:
Thanks a lot, this worked out all fine. Reflashed the stock Rom and booted up all fine.
Click to expand...
Click to collapse
That's great news! If you want to root again i recommend flashing supersu in odin (to allow boot of Twrp) then Twrp in Odin, Reboot Twrp then BACKUP, then do your wipes and flash Rom of choice (please already have downloaded it to internal storage! Lol) according to the rom devs Instructions...
Sent from my SM-N930F using Tapatalk

Categories

Resources