After working for a week, rooted, my G935A is stuck at AT&T logo. I've tried wiping cache and it will not boot into safe mode at all. I can get to Odin & Recovery properly.
Yamaha169 suggested... set selinux permissive.
Adb devices (should display device)
Adb root
Adb shell
Setenforce 0
Click to expand...
Click to collapse
... I did this but it still hangs at AT&T logo
I found posts that say using Odin to flash HOME_CSC has worked without having to wipe and all user data survives
... WHERE can I get HOME_CSC? I downloaded the stock ROM but dont see it in there.
LivinOne said:
After working for a week, rooted, my G935A is stuck at AT&T logo. I've tried wiping cache and it will not boot into safe mode at all. I can get to Odin & Recovery properly.
Yamaha169 suggested... set selinux permissive.
... I did this but it still hangs at AT&T logo
I found posts that say using Odin to flash HOME_CSC has worked without having to wipe and all user data survives
... WHERE can I get HOME_CSC? I downloaded the stock ROM but dont see it in there.
Click to expand...
Click to collapse
That will depend on which firmware you're running. To my knowledge, they aren't interchangeable. Are you on PI2? PK1?
I'm having the same problem with my S7. Wiped Cache and it still gets stuck on AT&T logo, solid blue light and vibrates every 5 seconds then 12 seconds.
Anyone know where to find this for PK1 ?
Related
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.
silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.
Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.
sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!
sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:
is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.
I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app
im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?
I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk
Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk
I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079
My SM-G900M is stuck in a boot loop.
When this happened, I Tried to do a factory reset plus cleaning cache in recovery. However this didnot fix my problem so I decided to reflash using odin, so i download the official rom and installed it but again same issue happened. After so much research and headache I installed CWM and did a kalvic, factory reset + format system a few times then I reflashed it afterwards. This seemed to have made the boot loop even worse since I doesn't pass through samsung galaxy s5 powered by android logo. That where the boot loop happens.
So overall I have tried
Reflashing ROM about 5 or 6 times using odin
Flashing a custom recovery multiple times
Factory reset
Clean cache + kalvic
FORMAT system and boot
Pulling the battery out for about a trillion times
Current result:
An Expensive Paper Holder
Thanks
PD: it only works when is pluged in
PhyraxYT said:
My SM-G900M is stuck in a boot loop.
When this happened, I Tried to do a factory reset plus cleaning cache in recovery. However this didnot fix my problem so I decided to reflash using odin, so i download the official rom and installed it but again same issue happened. After so much research and headache I installed CWM and did a kalvic, factory reset + format system a few times then I reflashed it afterwards. This seemed to have made the boot loop even worse since I doesn't pass through samsung galaxy s5 powered by android logo. That where the boot loop happens.
So overall I have tried
Reflashing ROM about 5 or 6 times using odin
Flashing a custom recovery multiple times
Factory reset
Clean cache + kalvic
FORMAT system and boot
Pulling the battery out for about a trillion times
Current result:
An Expensive Paper Holder
Thanks
Click to expand...
Click to collapse
You must flash pit file in odin but must find pit file for ur device : http://www.theandroidsoul.com/download-samsung-galaxy-s5-pit-files-and-information-84379/ You have problems with partition map
it doesn't works, i think my phone is completely useless now
PhyraxYT said:
it doesn't works, i think my phone is completely useless now
Click to expand...
Click to collapse
Download the latest firmware , bootloader end pit file for repartion, put all together in odin end flash.
If you have Samsung logo ur device is not death
Petreion said:
Download the latest firmware , bootloader end pit file for reparation, put all together in odin end flash.
If you have Samsung logo ur device is not death
Click to expand...
Click to collapse
Just asking:
Can i use the verizon file to unlock the bootloader for my s5?
i guess the answer is no but ... can i?
PD: i'm not with verizon
PhyraxYT said:
Just asking:
Can i use the verizon file to unlock the bootloader for my s5?
i guess the answer is no but ... can i?
PD: i'm not with verizon
Click to expand...
Click to collapse
Forget that, i found another bootloader file and it just didn't work
Firmware: http://www.sammobile .com/firmwares/download/68245/G900MUBU1BPB2_G900MUWM1BPB3_COL/
BootLoader: http://forum.xda-developers .com/showpost.php?p=52210611
Pit: http://www.theandroidsoul .com/download-samsung-galaxy-s5-pit-files-and-information-84379/
PhyraxYT said:
Just asking:
Can i use the verizon file to unlock the bootloader for my s5?
i guess the answer is no but ... can i?
PD: i'm not with verizon
Click to expand...
Click to collapse
Verizon file FROM THE SAME MODEL YOU MEAN SM-G900M OR OTHER DEVICE MODEL??
Petreion said:
Verizon file FROM THE SAME MODEL YOU MEAN SM-G900M OR OTHER DEVICE MODEL??
Click to expand...
Click to collapse
Same model
PhyraxYT said:
Same model
Click to expand...
Click to collapse
You can flash files from same model device without problems but if ur fone was looked by imei end you want to unlock the device by changing the firmware your device will not be unlocked the only way is octopus box
What you try to do recover the device or unlock device??
Petreion said:
You can flash files from same model device without problems but if ur fone was looked by imei end you want to unlock the device by changing the firmware your device will not be unlocked the only way is octopus box
What you try to do recover the device or unlock device??
Click to expand...
Click to collapse
Recover It, it's just that i found that dile and i wasn't sure if it would work and it didn't worked, i flashed the pit file, the lastest firmware (5.0 not 6.0) and the bootloader and it keeps having the bootloop
Dear xda users,
I have a big problem with my Samsung S7 Edge G935F!
Yesterday my phone restarts continuously so I used Odin to flash Firmware Stock. First, I used this Firmware: http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065 .
Odin doesn't show any errors and my phone restarts; but after Samsung S7 Edge Boot Splash Screen, the phone shows a screen with yellow triangle and Android dead and then, phone restarts in Stock Recovery Mode.
In the Recovery mode when I press Reboot System Now or PowerOff, appears "Verifying DMVerity Hash Tree..." and then "Failed" and my phone restarts again in Recovery.
I tried Wipe data and cache but Nothing!
Then I tried to repair firmware with Kies 3: No errors but my phone won't boot!!
And then I tried another firmware file with Odin but nothing!
The phone is Completely Stock! Recovery Mode and Download Mode work and the phone is recognised by PC.
Please help me!
Thanks in advance
Sorry for my english
re: firmware issues
adc.droid said:
Dear xda users,
I have a big problem with my Samsung S7 Edge G935F!
Yesterday my phone restarts continuously so I used Odin to flash Firmware Stock. First, I used this Firmware: http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065 .
Odin doesn't show any errors and my phone restarts; but after Samsung S7 Edge Boot Splash Screen, the phone shows a screen with yellow triangle and Android dead and then, phone restarts in Stock Recovery Mode.
In the Recovery mode when I press Reboot System Now or PowerOff, appears "Verifying DMVerity Hash Tree..." and then "Failed" and my phone restarts again in Recovery.
I tried Wipe data and cache but Nothing!
Then I tried to repair firmware with Kies 3: No errors but my phone won't boot!!
And then I tried another firmware file with Odin but nothing!
The phone is Completely Stock! Recovery Mode and Download Mode work and the phone is recognised by PC.
Please help me!
Thanks in advance
Sorry for my english
Click to expand...
Click to collapse
Have you tried doing a "Factory Data Reset" in stock recovery yet?
If not, do that before doing anything else.
The Factory Data Reset in stock recovery will WIPE your internal
sdcard but it will not wipe your external SD if you have one.
Also it would be very helpful to know the exact filename(s) of the
stock firmware(s) which you have tried to odin flash and what the
model of your phone is. (G938F) or other variant?)
Good luck and have a great day!
Misterjunky said:
Have you tried doing a "Factory Data Reset" in stock recovery yet?
If not, do that before doing anything else.
The Factory Data Reset in stock recovery will WIPE your internal
sdcard but it will not wipe your external SD if you have one.
Also it would be very helpful to know the exact filename(s) of the
stock firmware(s) which you have tried to odin flash and what the
model of your phone is. (G938F) or other variant?)
Good luck and have a great day!
Click to expand...
Click to collapse
Thanks for your reply!
Yes I tried Wiped data/Factory Reset and Wipe cache partition in Stock Recovery..
Device: Samsung Galaxy S7 Edge
Model: SM-G935F
Firmwares tha I tried to flash with Odin:
Netherlands (Android 6.0.1) G935FXXU1APF2_G935FPHN1APE2_G935FXXU1APEQ_PHN
Italy (Android 6.0.1) G935FXXU1APF2_G935FITV1APE2_ITV
If flashing succeeds, and you still have the same problem:
go back with your device where you bought it
You can't solve it yourself, and probably something is wrong/defect with the main-board
When you 1st discovered the continuous reboot:
1. why did you not go to the store where you bought your phone?
2. why trying to flash "other firmware" on your phone instead of your "original firmware"?
What's your original CSC? Flash your phone with your original phone's CSC and bring your phone back for repair and/or replacement!
re: Odin flashing
adc.droid said:
Thanks for your reply!
Yes I tried Wiped data/Factory Reset and Wipe cache partition in Stock Recovery..
Device: Samsung Galaxy S7 Edge
Model: SM-G935F
Firmwares tha I tried to flash with Odin:
Netherlands (Android 6.0.1) G935FXXU1APF2_G935FPHN1APE2_G935FXXU1APEQ_PHN
Italy (Android 6.0.1) G935FXXU1APF2_G935FITV1APE2_ITV
Click to expand...
Click to collapse
Are you using the latest version of Odin3?
The latest version is "3.11.1" if not here
is the download link for it, give it a try:
https://www.androidfilehost.com/?fid=24572369242686812
Good luck,
Have a great day!
henklbr said:
If flashing succeeds, and you still have the same problem:
go back with your device where you bought it
You can't solve it yourself, and probably something is wrong/defect with the main-board
When you 1st discovered the continuous reboot:
1. why did you not go to the store where you bought your phone?
2. why trying to flash "other firmware" on your phone instead of your "original firmware"?
What's your original CSC? Flash your phone with your original phone's CSC and bring your phone back for repair and/or replacement!
Click to expand...
Click to collapse
In attacchments there are images of Recovery Mode.
I don't know CSC because phone won't boot to see the code.. Kies says that CSC code is PE2
I can not do anything.. right?
Misterjunky said:
Are you using the latest version of Odin3?
The latest version is "3.11.1" if not here
is the download link for it, give it a try:
https://www.androidfilehost.com/?fid=24572369242686812
Good luck,
Have a great day!
Click to expand...
Click to collapse
Yes, I did. I tried Odin v3.10.7 and v3.11.1
adc.droid said:
Yes, I did. I tried Odin v3.10.7 and v3.11.1
Click to expand...
Click to collapse
you could try samsung smartswitch for pc.If it works cool but if that does not work i suggest taking it back.
jdoggawesomex900 said:
you could try samsung smartswitch for pc.If it works cool but if that does not work i suggest taking it back.
Click to expand...
Click to collapse
I tried with Kies3 but the problem remains.. I think with Smartswitch is the same thing because the file and the installation procedure is identical.. I don't know
adc.droid said:
I tried with Kies3 but the problem remains.. I think with Smartswitch is the same thing because the file and the installation procedure is identical.. I don't know
Click to expand...
Click to collapse
But smartswitch is newer and supports most samsung devices 5.0 and up.Kies is not meant for anything higher than kitkat.
jdoggawesomex900 said:
But smartswitch is newer and supports most samsung devices 5.0 and up.Kies is not meant for anything higher than kitkat.
Click to expand...
Click to collapse
So I'll try with SmartSwitch..
Hello everyone. One of the ladies I look up to as a mother gave me her broken s4 this morning. It was in a boot loop, and needed to have the full software flashed again. I downloaded OK3 from sammobile and successfully flashed it using Odin 3.11. I then rebooted and flashed CF Autoroot in Odin, rebooted and tried to enter recovery mode. I would get 3 lines of info that left the screen really fast, then the screen was blank for 10 seconds, then it vibrates and reboots into the normal rom. So I went back to Odin and flashed TWRP 3.0.2-0-jftespr.img.tar (unchecking the options for auto reboot, re-partition, f. reset time) and the log says suceed 1/failed 0, I get a green pass and when I try to reboot into recovery I get the seandroid message. So the phone knows I have a non-standard recovery...still after that message I get the same blank screen, 10 second delay, and then vibrate and reboot to the rom. I tried reflashing the stock OK3 and the seandroid message goes away, but recovery mode still does not work for me Other than this recovery issue, the phone appears to work fine and it even downloaded an OTA (which I have not installed.) Any suggestions?
I would try flashing TWRP with a different version of Odin. I recently needed to reflash recently. I had a similar problem. Tried Odion 10.7. Worked fine. You could also install the Flashify app and install your recovery with that.
spaldingsmails said:
I would try flashing TWRP with a different version of Odin. I recently needed to reflash recently. I had a similar problem. Tried Odion 10.7. Worked fine. You could also install the Flashify app and install your recovery with that.
Click to expand...
Click to collapse
Thanks for your suggestions, I will try and let you know the outcome. Of course now, I have the problem with the wifi not turning on...which is only harder to fix without a recovery to boot into. Any thoughts on this new wrinkle?
spaldingsmails said:
I would try flashing TWRP with a different version of Odin. I recently needed to reflash recently. I had a similar problem. Tried Odion 10.7. Worked fine. You could also install the Flashify app and install your recovery with that.
Click to expand...
Click to collapse
Thanks for your suggestion! I tried flashing using odin 3.09 and the white samsung usb cable, and I finally have a recovery! Do you happen to know how to fix the wifi?
No idea on the wifi. That is way over my head.
angel4b said:
Hello everyone. One of the ladies I look up to as a mother gave me her broken s4 this morning. It was in a boot loop, and needed to have the full software flashed again. I downloaded OK3 from sammobile and successfully flashed it using Odin 3.11. I then rebooted and flashed CF Autoroot in Odin, rebooted and tried to enter recovery mode. I would get 3 lines of info that left the screen really fast, then the screen was blank for 10 seconds, then it vibrates and reboots into the normal rom. So I went back to Odin and flashed TWRP 3.0.2-0-jftespr.img.tar (unchecking the options for auto reboot, re-partition, f. reset time) and the log says suceed 1/failed 0, I get a green pass and when I try to reboot into recovery I get the seandroid message. So the phone knows I have a non-standard recovery...still after that message I get the same blank screen, 10 second delay, and then vibrate and reboot to the rom. I tried reflashing the stock OK3 and the seandroid message goes away, but recovery mode still does not work for me Other than this recovery issue, the phone appears to work fine and it even downloaded an OTA (which I have not installed.) Any suggestions?
Click to expand...
Click to collapse
I would suggest you flash TWRP in a different version.
Hey guys, in a bit of a pickle.
I'm helping a buddy fix his Verizon S8. We were flashing stock firmware back onto it (never been rooted//unlocked) and afterwards when it boots into recovery, it says "Erasing" and then powers off. We've got it into the boot recovery thing and tried to reset it from there as well as recovery and it does the same thing. I've had him just flash CSC with Odin and to no prevail.
Suggestions would be appreciated. Repartition and nand erase look interesting, thoughts?
Craz Basics said:
Hey guys, in a bit of a pickle.
I'm helping a buddy fix his Verizon S8. We were flashing stock firmware back onto it (never been rooted//unlocked) and afterwards when it boots into recovery, it says "Erasing" and then powers off. We've got it into the boot recovery thing and tried to reset it from there as well as recovery and it does the same thing. I've had him just flash CSC with Odin and to no prevail.
Suggestions would be appreciated. Repartition and nand erase look interesting, thoughts?
Click to expand...
Click to collapse
Should try to reset from settings insside android to avoid frp. See if that helps. If not flash whole firmware in odin with home csc that always resets em
TheMadScientist said:
Should try to reset from settings insside android to avoid frp. See if that helps. If not flash whole firmware in odin with home csc that always resets em
Click to expand...
Click to collapse
It wont boot into Android. We've flashed the latest pie build with Odin and nothing.
It sounds like a bootloader problem to me, as sometimes recovery wont even pop up.