It has never been flashed (that I know of) and was updated to latest stock update prior to this happening.
Got stuck on samsung logo, i flashed via Odin all went well but it still doesn't boot up. it just trys to boot to recovery
does anybody know why
Urban Designs said:
It has never been flashed (that I know of) and was updated to latest stock update prior to this happening.
Got stuck on samsung logo, i flashed via Odin all went well but it still doesn't boot up. it just trys to boot to recovery
does anybody know why
Click to expand...
Click to collapse
Wipe cache, if it worked then your phone was soft bricked
Sent from my GT-I9505 using Tapatalk
yahya wessam said:
Wipe cache, if it worked then your phone was soft bricked
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
cant boot to recovery
i suspect this is a software related issue
have been told flashing to 4.4.2 is known to fix this problem so going to try that
Urban Designs said:
cant boot to recovery
i suspect this is a software related issue
have been told flashing to 4.4.2 is known to fix this problem so going to try that
Click to expand...
Click to collapse
Just download the latest firmware for your country on Sammobile and flash that
have already tried that, it doesn't work.
tried flashing 4.4.2 and that didn't work either
does anybody have a link to the whole files? bootloader, modem etc
Related
RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.
So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?
Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Good deal
Sent from my GT-I9505 using xda premium
Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:
Hey guys,
I got jamals google edition installed on my S4 and when I forgot to charge it and I started the device I got a bootloop. I dont know why, but I also could´t get into the recovery mode, so I flashed an originial Samsung firmwar via Odin on my S4 (4.4.2)
After that, it restarted but I got a "android.process.acore has stopped" message and I couldn't use the S4 because the message kept popping up and the S4 automatically restarted and when it restarted the message appeared again, so i had a very strange loop i couldnt interrupt. So i flashed another 4.4.2 firmware and also again the same firmware, but nothing helped, I still got the message and the S4 kept restarting.
So I flashed the Omega Pre-rooted 4.4.2 firmware via odin (and the exact same thing happened). But whats strange is, that before it started it said "updating 1 of 172 apps) so that must mean, that even though I flashed 3 firmwares via Odin, my apps somehow stayed on the S4? And also the wallpaper was the same wallpaper I had before, what was very strange.
Then I installed Philz CWM Recovery because I waned to perform a factory reset. But after I installed it and tried to get into recovery mode, I couldn't and only this was displayed :
Recovery Booting...
Recovery is not Seandroid Enforcing
Set Warranty Bit: recovery
So it seems like nothing works and I'm getting really desperate, does anyone of you has an idea how to fix this? Otherwise I guess my S4 is bricked
Regards and thanks for your help
Flash latest firmware via odin with auto reboot option unchecked and before u boot into os simply open stock recovery and perform a factory reset.. hope it will help u..
Sent from my GT-I9500
coolkoushik07 said:
Flash latest firmware via odin with auto reboot option unchecked and before u boot into os simply open stock recovery and perform a factory reset.. hope it will help u..
Sent from my GT-I9500
Click to expand...
Click to collapse
Thx, I'll give it a try! Could you maybe tell me, where I get the latest firmware?
coolkoushik07 said:
Flash latest firmware via odin with auto reboot option unchecked and before u boot into os simply open stock recovery and perform a factory reset.. hope it will help u..
Sent from my GT-I9500
Click to expand...
Click to collapse
Thx man it worked :good:
thomas333 said:
Thx man it worked :good:
Click to expand...
Click to collapse
Glad to know that it worked...
Sent from my GT-I9500
I'm assuming you know about KNOX now that you've flashed an official firmware you will have KNOX and you've already tripped KNOX by installing recovery but you won't be able to use a lower version firmware just bare that in mind when flashing official stock again.
Sent from my GT-I9505G using Tapatalk
So its been a while since I tried flashing and rooting....HTC Evo while.
My Problem: Tried installing custom recovery (TWRP), when it rebooted it is stuck on Samsung logo screen.
Tried through Odin flashing the stock firmware nothing...
My S4 is older from earlier 2013, but I`ve done all the OTA updates.
Any ideas or suggestions?
Agent Droid said:
So its been a while since I tried flashing and rooting....HTC Evo while.
My Problem: Tried installing custom recovery (TWRP), when it rebooted it is stuck on Samsung logo screen.
Tried through Odin flashing the stock firmware nothing...
My S4 is older from earlier 2013, but I`ve done all the OTA updates.
Any ideas or suggestions?
Click to expand...
Click to collapse
Don't think you can revert back to older than NAE if that was your last ota. Flash stock NAE. Did you use cfautoroot? Guess knowing exactly what you did before the problem might help narrow it down
pontif said:
Don't think you can revert back to older than NAE if that was your last ota. Flash stock NAE. Did you use cfautoroot? Guess knowing exactly what you did before the problem might help narrow it down
Click to expand...
Click to collapse
I finally got it fixed and going. I did use CFAUTOROOT, which seemed to work okay, gave me the super user app. It was the recovery i keep having problems, when i tried to flash a rom it just gets stuck in bootloop.
Hi, Ive been stuck with this problem for about 3 days now. I have tried EVERYTHING possible and now I'm getting impatient. I've tried every advice on almost every forum or blog. But still cant seem to resolve the issue.
I was running echoe rom 5.1 and tried to flash cm 12 on it through philz recovery. It failed the first time but I was able to access philz. Then I tried to flash stock firmware through Odin and I dont know what happened, it failed and I got an error "Firmware upgrade failed and try recovering through kies...."
I tried kies, my device wasnt able to connect( I tried all the ports and cables I have) and even reinstalled kies just to check. No luck.
Then I killed all the kies processes and tried to flash a stock firmware, this time odin gave an error "PIT partition not found".
I have tried multiple PIT files for i9505 16gb with multiple stock roms on multiple versions of Odin (1.85, 3.07, 3.09, 3.10) some forums asked to tick 're-partition', some said to untick 'auto reboot', Ive tried all of them, still fails.
I can only access download mode on my phone right now, not philz recovery and neither stock android recovery.
my write protection is also enabled, I think this is the core issue, once the protection is disabled, PIT can re partition and flash a stock, and once a stock is flashed, I can flash any recovery and flash any custom ROM through that.
I have been flashing and rooting androids since the last 2 years and never encountered such a problem. Always found some solution online.
I would really appreciate if you guys could help with the problem. Thanks
You're device got soft bricked because you flash philz recovery and its outdated (and so does as CWM recovery) you should have flash TWRP recovery, anyways try to flash stock
Sent from my GT-I9505 using Tapatalk
yahya wessam said:
You're device got soft bricked because you flash philz recovery and its outdated (and so does as CWM recovery) you should have flash TWRP recovery, anyways try to flash stock
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I did try to flash stock firmware after that, failed at odin everytime, gives 'No PIT partition' error.... doesnt even satrt the firmware update, havent gotten past this issue.
AAF1994 said:
I did try to flash stock firmware after that, failed at odin everytime, gives 'No PIT partition' error.... doesnt even satrt the firmware update, havent gotten past this issue.
Click to expand...
Click to collapse
You're some what describing a hard brick
Only a motherboard replacement can fix it
Sent from my GT-I9505 using Tapatalk
yahya wessam said:
You're some what describing a hard brick
Only a motherboard replacement can fix it
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I can still access download mode, its a softbrick dude!
AAF1994 said:
I can still access download mode, its a softbrick dude!
Click to expand...
Click to collapse
I know, I am not fully saying that is hard bricked but it looks like it is
Sent from my GT-I9505 using Tapatalk
Hey guys, I need a little help to figure out what's going on with my dad's nexus 4.
When he tried to update to the newest version of Lollipop avaiable, the phone entered in a bootloop.
I tried flashing a factory image manually using this guide, but after it was done, the phone booted and it was still in a bootloop (stuck on the colored circles moving). I tried wiping data/factory reset afterwards and the phone remained in a bootloop state.
I also tried using the nexus root toolkit by WugFresh using the option "Flash Stock/Unroot" with the Soft brick/bootloop box checked, but it also didn't solve the problem.
There were no error messages when flashing, and I waited for 30 ~ 45 minutes after each flashing attempt to make sure that the phone was in fact in a bootloop.
I don't know what to do anymore... Can it be a hardware problem?
Did you manually flash the userdata.img file? If not, flash the file and, immediately after flashing the file in fastboot, go into stock recovery, perform a factory wipe, and reboot.
audit13 said:
Did you manually flash the userdata.img file? If not, flash the file and, immediately after flashing the file in fastboot, go into stock recovery, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
I manually flashed the files and did a factory wipe, but it didn't solve the problem.
Did you flash the userdata.img file?
audit13 said:
Did you flash the userdata.img file?
Click to expand...
Click to collapse
yes, I did exactly as you said.
Hmm, usually flashing the userdata file and wiping via stock recovery works. Have you tried different factory images?
audit13 said:
Hmm, usually flashing the userdata file and wiping via stock recovery works. Have you tried different factory images?
Click to expand...
Click to collapse
I tried to downgrade to 5.0 and 4.4.4 , but on both of them I get stucked on the boot animation.
Try 4.1.1? If it works, it is possible that the emmc chip is damaged.
audit13 said:
Try 4.1.1? If it works, it is possible that the emmc chip is damaged.
Click to expand...
Click to collapse
On google's site, the factory images avaiable start from version 4.2.2, I'll try using that.
Okay. Good luck.
audit13 said:
Okay. Good luck.
Click to expand...
Click to collapse
So, I was able to downgrade to 4.2.0 version using the toolkit that I mentioned. The phone seems to be working fine now. What does that mean? Can I try to update to lollipop without fear?
You can try updating via ota updates to kk and LP but, if it gets stuck again on kk, I think the emmc chip is a problem.
audit13 said:
You can try updating via ota updates to kk and LP but, if it gets stuck again on kk, I think the emmc chip is a problem.
Click to expand...
Click to collapse
Okay, thank you very much for the help!
You're welcome. We're all here to help each other out.
Hopefully, you'll be able to upgrade to kk or LP.
audit13 said:
You're welcome. We're all here to help each other out.
Hopefully, you'll be able to upgrade to kk or LP.
Click to expand...
Click to collapse
I couldn't upgrade to 4.3 jellybean. It got stuck on a bootloop. So it means that it is a hardware problem?
Unfortunately, it appears that the emmc chip is damaged.
audit13 said:
Unfortunately, it appears that the emmc chip is damaged.
Click to expand...
Click to collapse
So, nothing I can really do about it?
Not that I know of.