Hi all.
My friend has a note 5 dous and it was automatically updated to marshmallow. She had a lot of problems with its wi-fi connection stability, So I flashed her phone to a newer marshmallow build and made a factory reset afterwards but she still has all previous problems with wifi.
My question is that is it safe now to downgrade her phone to stock lollipop?
roostaamir said:
Hi all.
My friend has a note 5 dous and it was automatically updated to marshmallow. She had a lot of problems with its wi-fi connection stability, So I flashed her phone to a newer marshmallow build and made a factory reset afterwards but she still has all previous problems with wifi.
My question is that is it safe now to downgrade her phone to stock lollipop?
Click to expand...
Click to collapse
Yes so long as you use the correct firmware version for the phone and don't allow odin to reboot the phone.. After odin finishes press and hold the volume down button and power button until the screen turns off then when it turns on select factory reset and then let it finish and reboot itself and it will be fine.
Just follow this but use your own firmware not the one in here
http://forum.xda-developers.com/ver.../downgrade-to-lollipop-5-1-1-verizon-t3368250
Related
i just updated my galaxy note and when i rebooted its not getting passed the note N 7000 screen can any one help me with that? i had previously updated it to XXLA3 and it was working fine!
noteN7000 said:
i just updated my galaxy note and when i rebooted its not getting passed the note N 7000 screen can any one help me with that? i had previously updated it to XXLA3 and it was working fine!
Click to expand...
Click to collapse
Was it an OTA or KIES update u did?
U rooted and on stock or any custom rom ?
If not rooted....then u can still try hitting volume up + home + power buttons all at the same time and holding them pressed till the time the same N7000 logo shows up and leave the buttons then. The phone should boot into stock recovery. Now try clearing the cache there if the option is available. If nothing works then either wipe/format your note (warning all data will be lost except the internal/external sd card) or reflash the firmware through PC odin using Dr Ketan's guide from the stickies post in the development section of note forum here on xda.
How did you update you phone? Via kies?
i am new to all these things! i haven't rooted my phone as well! jst went on to "about phone" and update. after which it didn't started. tried the vol. up home key and power didn't worked...
So it was an OTA update. Did you tried pressing volume down + home + power button for booting into download mode?
ya tried that as well but it said custom OS can cause critical problems so canceled it...
noteN7000 said:
ya tried that as well but it said custom OS can cause critical problems so canceled it...
Click to expand...
Click to collapse
vol up+home+power should work. Try that again and keep pressing them till the time the n7000 logo shows up and leave them immediately after it.
if u are not able to get into recovery then the only way for you is to flash via odin.
Refer the guide and roms here-
http://forum.xda-developers.com/showthread.php?t=1424997
does that mean my phone will be rooted?
noteN7000 said:
does that mean my phone will be rooted?
Click to expand...
Click to collapse
No. You just flash the latest firmware you want from the PC odin. The phone will be stock rom and wont be rooted unless you run the rooting tool.
Remember to read the full post !
Hi everyone. I have a rooted Galaxy Note 1. I accidentally tried to update something (the phone said there was an Android update or something) and now my phone in stuck in a bootloop showing the Android logo. When I try to reset it (volume+home+power buttons) it goes to an Odin "Downloading..." screen and gets stuck on that.
I've seen some stuff about unbricking the phone using Odin to return to the original stock rom. But from what I can tell, there are different stock roms available depending on your Country Sales Code (CSC). So apparently I need to look in Kies for my CSC to know which rom to download, but Kies doesn't recognise the phone, I guess because it's bricked. I know the phone is from the UK, but I don't know what network it came from (I bought it second hand). All I know is that it is unlocked now.
I have CWM.zip, CWM-SuperSU-v0.87.zip, and franco.Kernel-r5.zip on the micro SD card from when I was rooting it ages ago. Do these have anything to do with fixing it?
Any ideas on where I go from here? Thanks for your help.
Which volume button did you press ? You need volume up + home + power to get into recovery.
You can flash any rom from any region using odin.
Same problem
Hey,
Thanks for helping me in advance...
I used the Custom ROM (( http://forum.xda-developers.com/showthread.php?t=1970626 )) Ultimate N7000 for a long time. However this build became more and more unstable the longer I used my phone.
So I decided to go back to STOCK.
So I followed this guide: http://forum.xda-developers.com/showthread.php?t=1424997
And everything went well (Odin didnt give any errors)
However after reboot... the problem began... I cant turn my phone on anymore.... It seems to be stuck in a bootloop....
How can I fix this?? please help me
Which rom did you flash? If you flashed JB, boot into recovery and wipe data. Then reboot.
I have just purchased this Samsung GTi 9305 LTE from a mate. I found out then that it was rooted, but not correctly. I used Rootchecker to tell me. The Security manager kept telling me also that it was blocking Supersu.
Oops. Just done a factory reset on this S3 Gti9305 (LTE) and all I am getting now is the blue notification light on and the Samsung logo just going light and dark blue.
I tried to then do a recovery, with all the buttons held down, it starts with a green warning;
A custom OS can cause critical problems in phone and installed applications. ( Yeah, just found out)
If you want to download a custom OS, press vol up key, if not, vol down and restart. ( which it doesn't).
I remember disabling Supersu, and unticking the security manager warning box. I put in the correct sim card, factory reset, and since then it will not start.
Phone was on Uk EE, but was unlocked for previous owner. The replacement sim is GiffGaff- running on UK O2 lines.
When hooked up to pc and Kies 3, the phone was not recognized and I was notified that the usb device is not working. When usb lead is in phone, it shows that it is charging, so lead looks to be ok.
Is this what you call a brick? Or just in a bootloop mode ??
I rooted my S3 GTi9300 ok and put on Omnirom v5.
Any help would be appreciated, so I can throw the phone back at mate.
Thank you.
Gregg1100 said:
I have just purchased this Samsung GTi 9305 LTE from a mate. I found out then that it was rooted, but not correctly. I used Rootchecker to tell me. The Security manager kept telling me also that it was blocking Supersu.
Oops. Just done a factory reset on this S3 Gti9305 (LTE) and all I am getting now is the blue notification light on and the Samsung logo just going light and dark blue.
I tried to then do a recovery, with all the buttons held down, it starts with a green warning;
A custom OS can cause critical problems in phone and installed applications. ( Yeah, just found out)
If you want to download a custom OS, press vol up key, if not, vol down and restart. ( which it doesn't).
I remember disabling Supersu, and unticking the security manager warning box. I put in the correct sim card, factory reset, and since then it will not start.
Phone was on Uk EE, but was unlocked for previous owner. The replacement sim is GiffGaff- running on UK O2 lines.
When hooked up to pc and Kies 3, the phone was not recognized and I was notified that the usb device is not working. When usb lead is in phone, it shows that it is charging, so lead looks to be ok.
Is this what you call a brick? Or just in a bootloop mode ??
I rooted my S3 GTi9300 ok and put on Omnirom v5.
Any help would be appreciated, so I can throw the phone back at mate.
Thank you.
Click to expand...
Click to collapse
Hi,
You should use ODIN v3.09 and flash a i9305 official firmware (4.1.2, 4.3 or 4.4.4). You can search on samsung-updates.com or sammobile.com.
IMPORTANT : If you don't want KNOX BL because of warranty purpose, don't flash official 4.3 or 4.4.4 via ODIN.
Don't forget to install Samsung usb drivers on your computer.
For instance, you can follow that guide from MaHo_66 : http://forum.xda-developers.com/gala...sions-t2694249
Gregg1100 said:
I have just purchased this Samsung GTi 9305 LTE from a mate. I found out then that it was rooted, but not correctly. I used Rootchecker to tell me. The Security manager kept telling me also that it was blocking Supersu.
Oops. Just done a factory reset on this S3 Gti9305 (LTE) and all I am getting now is the blue notification light on and the Samsung logo just going light and dark blue.
I tried to then do a recovery, with all the buttons held down, it starts with a green warning;
A custom OS can cause critical problems in phone and installed applications. ( Yeah, just found out)
If you want to download a custom OS, press vol up key, if not, vol down and restart. ( which it doesn't).
I remember disabling Supersu, and unticking the security manager warning box. I put in the correct sim card, factory reset, and since then it will not start.
Phone was on Uk EE, but was unlocked for previous owner. The replacement sim is GiffGaff- running on UK O2 lines.
When hooked up to pc and Kies 3, the phone was not recognized and I was notified that the usb device is not working. When usb lead is in phone, it shows that it is charging, so lead looks to be ok.
Is this what you call a brick? Or just in a bootloop mode ??
I rooted my S3 GTi9300 ok and put on Omnirom v5.
Any help would be appreciated, so I can throw the phone back at mate.
Thank you.
Click to expand...
Click to collapse
just flash a stock firmware via odin..
I had the exact same problem after some unsuccessful attemts to root my s3 lte!
Sent from my GT-I9305 using XDA Free mobile app
Non start up after factory reset. Bricked ??
Thanks for help. All sorted.
If your phone stuck on boot after flash stock via odin, go to recovery and make a full vipe and factory reset. Some devices unable to boot first after reflash stock.
you can watch here how to install rom via odin.
https://youtu.be/32TQ6DG0JZ8
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?
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...