Develop Bugs

Bootloop after reboot PLEASE HELP!

Hey guys after installing wicked v3 with twrp when ever i reboot it wont pass the "samsung galaxy s4" image, i have to fully wipe and again and reinstall but when i reboot again does the same thing. Has someone encountered this before? im trying to odin back to stock but konanes .tar file is offline could someone please share it, Thanks in advance

deleted

raphyv23 said:
Have you wiped the Dalvik, Cache and Data?
Click to expand...
Click to collapse
every single time

deleted

raphyv23 said:
USE ADB Sideload on TWRP. Sideload a ROM to your phone
Click to expand...
Click to collapse
not sure how to do that but i just rather go back to stock thru odin, do you have the .tar file?

deleted

raphyv23 said:
SGH-i9505 Stock: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=GT-I9505
SGH-i9500 Stock: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=GT-I9500
They are from samsung's website I haven't tested them trough
Click to expand...
Click to collapse
wouldnt i need the one for the m919?

deleted

re: boot loops
unciviilized said:
Hey guys after installing wicked v3 with twrp when ever i reboot it wont pass the "samsung galaxy s4" image, i have to fully wipe and again and reinstall but when i reboot again does the same thing. Has someone encountered this before? im trying to odin back to stock but konanes .tar file is offline could someone please share it, Thanks in advance
Click to expand...
Click to collapse
Your bootloop is an easy fix if you have not started odin flashing yet.
Just reboot into recovery and select "Factory Reset" then reboot the phone
and most of the time this fixes the problem, I should say at least 8 out 10
booloops can be fixed with a "Factory Reset" then reboot.
Good luck!

Misterjunky said:
Your bootloop is an easy fix if you have not started odin flashing yet.
Just reboot into recovery and select "Factory Reset" then reboot the phone
and most of the time this fixes the problem, I should say at least 8 out 10
booloops can be fixed with a "Factory Reset" then reboot.
Good luck!
Click to expand...
Click to collapse
i do that everytime, so now i have flashed cwm to see if that fixed my problem so now after fully wiping it doesnt even pass the galaxy s4 screen
im downloading the uvuamdl.zip to odin but download time says 1 hr 33 mins

ok so last night i left the UVUAMDL.zip to download over night but it seems i got a bad download and today im at work and cant download big files because of security reasons, can I flash twrp thru odin to see if i can get my phone to boot? before i installed cwm i could get it to boot with twrp but when ever i rebooted it just bootlooped and i had to fully wipe again and flash the rom again to get it running, or could someone please upload the mdl tar file so i can return to stock? Please someone help me as im desperate and need a running phone for work :crying:, thank you

unciviilized said:
ok so last night i left the UVUAMDL.zip to download over night but it seems i got a bad download and today im at work and cant download big files because of security reasons, can I flash twrp thru odin to see if i can get my phone to boot? before i installed cwm i could get it to boot with twrp but when ever i rebooted it just bootlooped and i had to fully wipe again and flash the rom again to get it running, or could someone please upload the mdl tar file so i can return to stock? Please someone help me as im desperate and need a running phone for work :crying:, thank you
Click to expand...
Click to collapse
You can download the MDL tar from the Odin thread. Yes, you can flash TWRP through Odin. You can get the tar file here.

Atmazzz said:
You can download the MDL tar from the Odin thread. Yes, you can flash TWRP through Odin. You can get the tar file here.
Click to expand...
Click to collapse
im at work now so unable to download the .tar but I will try and flash twrp thru odin and see if i can at least get the phone to boot before i odin back, thanks for your response. Will report back

So i installed twrp thru odin and that got me to boot. But i odined back to stock just to avoid any more issues, thanks to all who tried to help!
Sent from my SGH-M919 using Tapatalk 4 Beta

Something weird

Hi guys i had the Note 5120 running 4.1.2 and all the while rooted with Framaroot 1.60 and had install multi window manager. I did not install custom recovery so i did not have any backups made as im just a simple user and will make use of the root for some enhancements. Today i installed font installer https://play.google.com/store/apps/details?id=com.jrummy.font.installer. After i chose my desire font, it request for a reboot and i did.
That is where the problem arised. My device is now stuck at the welcome screen with the word Samsung glowing and thats about it. I had done a hard reset but still the same. And i didnt manage to get any further info of my built and anything else *sigh*.
Anyone here be able to help me on this as that is all the rooting i have done on this phone. Never tried Odin or anything else. Hopefully some can help revive my 8 days old Note

Your device is in a bootloop. Reflash your stock ROM.

Lim Wee Huat said:
Your device is in a bootloop. Reflash your stock ROM.
Click to expand...
Click to collapse
Just as i found out about it. I am currently downloading the stock rom from sammobile. Just to be sure that i can place the stock rom in my ext sd card and use stock recovery to flash it after i rename it as update.zip?

you can just do a factory reset in stock recovery and your tablet will go back to factory fresh status..dont bother downloading or flashing anything, just factory reset and you are back to square one

In most cases, you need to extract the tar.md5 file from zip and flash using odin.
Sent from my GT-N5120 using xda app-developers app

wase4711 said:
you can just do a factory reset in stock recovery and your tablet will go back to factory fresh status..dont bother downloading or flashing anything, just factory reset and you are back to square one
Click to expand...
Click to collapse
it doesnt work for me. it will end up with the same again with the word SAMSUNG.

mayday2 said:
In most cases, you need to extract the tar.md5 file from zip and flash using odin.
Sent from my GT-N5120 using xda app-developers app
Click to expand...
Click to collapse
So i need to use odin to flash the stock rom that i have located for my device. Flashing from stock recovery wont work yah.
Edited: My device is now up and running. Flashed the right firmware via Odin. Thanks to you guys!

Sprint Galaxy S3 not goimg into new recovery

Hi guys newbie here
I just another Galaxy s3 for the fiance and installed the clockwork in it but it just wont go it just keep going back to the stock recovery. I installed it using Odin 3 3.07 and it says PASS but nothing... Any ideas or help?

s13maniacs said:
Hi guys newbie here
I just another Galaxy s3 for the fiance and installed the clockwork in it but it just wont go it just keep going back to the stock recovery. I installed it using Odin 3 3.07 and it says PASS but nothing... Any ideas or help?
Click to expand...
Click to collapse
Because you can not let the phone boot after the flash. You have to pull the battery once it completes. Then put it back in and boot into recovery. Then you have to flash teamepic.zip to root. If not once you boot up it will overwrite the recovery with stock.
Whatever method your doing will tell you to not let the phone boot up. Your missing that step. Make sure reboot is not checked on odin.
Sent from the future via Tapatalk 4

edfunkycold said:
Because you can not let the phone boot after the flash. You have to pull the battery once it completes. Then put it back in and boot into recovery. Then you have to flash teamepic.zip to root. If not once you boot up it will overwrite the recovery with stock.
Whatever method your doing will tell you to not let the phone boot up. Your missing that step. Make sure reboot is not checked on odin.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
will try this right now.. Thanks in advance

You are awesome Thanks a lot

s13maniacs said:
You are awesome Thanks a lot
Click to expand...
Click to collapse
I think, even after that you might end up in the stock recovery after one or two reboots. Check this link that talks about removing a couple of files that cause this issue "What to do if Phone Boots into Stock Recovery (Android Recovery) instead of CWM".
Only follow the steps under the section "What to do if Phone Boots into Stock Recovery (Android Recovery) instead of CWM". Rest of the guide is not applicable to SPH L710 Galaxy S3 Sprint. (@edfunkycold suggested to remove the link, but this link was really useful when I first installed the CWM on my phone and kept getting the stock recovery back).

@gndlgisdbna
That's talking about i9300 that's the international S3 anything that has to do with that device will brick a US variant S3 please edit and remove that link before a noob follows that link and messes up their phone.
Sent from the future via Tapatalk 4

s13maniacs said:
Hi guys newbie here
I just another Galaxy s3 for the fiance and installed the clockwork in it but it just wont go it just keep going back to the stock recovery. I installed it using Odin 3 3.07 and it says PASS but nothing... Any ideas or help?
Click to expand...
Click to collapse
edfunkycold said:
Because you can not let the phone boot after the flash. You have to pull the battery once it completes. Then put it back in and boot into recovery. Then you have to flash teamepic.zip to root. If not once you boot up it will overwrite the recovery with stock.
Whatever method your doing will tell you to not let the phone boot up. Your missing that step. Make sure reboot is not checked on odin.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
When I had a bad download of a unofficial 10.2 rom a couple weeks ago, i odin'ed stock and just used cf auto root, then flashed twrp from goo

Thank you but his problem was already solved 2 1/2 days ago. :thumbup:
Sent from the future via Tapatalk 4

Help me! Flash failed

hello, on my notes I have a 2 rom DN3.0 today I wanted to go to 3.1, but after starting the procedure flash aroma and all of the phone is locked. I removed the battery and I rebooted into recovery, full wipe, flash retried this time it went a bit further but it was locked again. Removed the battery and restarted the phone, the recoverynon me access to the external SD, after several attempts I managed to get the menu of the backup-restore, see the file, begins recovery and crashes, I remove the battery and restart again, but not now goes into recovery.
What could have happened? and how can I fix it? give me a help?
Thank you and .... sorry for the bad English, but the fault is Google translator!

Same problem
Serjo61 said:
hello, on my notes I have a 2 rom DN3.0 today I wanted to go to 3.1, but after starting the procedure flash aroma and all of the phone is locked. I removed the battery and I rebooted into recovery, full wipe, flash retried this time it went a bit further but it was locked again. Removed the battery and restarted the phone, the recoverynon me access to the external SD, after several attempts I managed to get the menu of the backup-restore, see the file, begins recovery and crashes, I remove the battery and restart again, but not now goes into recovery.
What could have happened? and how can I fix it? give me a help?
Thank you and .... sorry for the bad English, but the fault is Google translator!
Click to expand...
Click to collapse
+1 I have the same problem. Anyone?? :crying:

NO ADVICE?

Serjo61 said:
NO ADVICE?
Click to expand...
Click to collapse
If the phone freezes after Aroma installer starts it is probably a bug with recovery. Try flashing older version of Philz (v5.x).

dalanik said:
If the phone freezes after Aroma installer starts it is probably a bug with recovery. Try flashing older version of Philz (v5.x).
Click to expand...
Click to collapse
unfortunately when I turn on my phone it remains stuck on the SAMSUNG NOTE II screen and does not move from there
how can I do?

I317 or 7105??
Sent from my SGH-I317 using Tapatalk

note 2 7100

Try using the latest twrp
Sent from my SGH-I317 using Tapatalk

I can not seem to go into recovery, then I tried to flash with odin an old version of phliz, now came into recovery, I'm trying to restore the old ROM but locks control md5 sums
possible that there is a file restore damaged?

I solved it with the flash from odin of Philz, full wipe then install new rom, I flashed the DN3.1 and all ok!
Thank you all for the help!
And season's greetings!

Serjo61 said:
I solved it with the flash from odin of Philz, full wipe then install new rom, I flashed the DN3.1 and all ok!
Thank you all for the help!
And season's greetings!
Click to expand...
Click to collapse
Your still on a old version flash 3.1.1 then download ota 3.2 but flash that through recovery. I use twrp and it boots everytime
Sent from my SGH-I317 using Tapatalk

the problem was that I could not get into recovery, but I solved it with odin and now I installed the DN3.1.1

[Q] Note 4 sprint

Hello crew, I've recently gotten a Note 4 through sprint. I've been rooting devices since the HTC Magic and have had no bricks. I rooted my Note 4 via Odin 1.85. I flashed the latest twrp and It worked great. This morning my phone was frozen and when I pulled the battery, it boot looped. Figured it was a stock kernel issue with xposed installer. I went back into twrp and it refused to mount the system partition. I can't flash a rom, I can't recover from any of the images I created. I went through the unroot process and flashed the stock recovery back with odin. Now it boots but hangs up at the samsung splash screen for a while then loops. Any ideas? Thank you in advance.

Flash twrp again.

Note 4
w7excursion said:
Flash twrp again.
Click to expand...
Click to collapse
Thank you for the fast response. I did. I tried an older version too just in case it was a bug. No luck. When I used Odin to flash the stock recovery and rom back it starts to boot past the black and white Note 4 screen then gets to the samsung splash screen and it just hangs there. I cleared the cache and did a factory reset in the stock recovery.

If its got oel inside your stuck bro

pbedard said:
If its got oel inside your stuck bro
Click to expand...
Click to collapse
OEL? I don't understand why It won't mount the system partition in twrp. I had no initial issues at all. I even flashed a Cyanogenmod nightly. It's still early and wasn't very stable so I went back to a backup I made. worked fine. I was back to rooted stock. Then the next day it froze and here I am.

pbedard said:
If its got oel inside your stuck bro
Click to expand...
Click to collapse
Yep... OE1... Samsung's latest bit of terrorist activity.
Read through the general and help threads... You'll see.
Try notarized rom (search) and then wait for the next official release (5.1.1?) .

jhill110 said:
Yep... OE1... Samsung's latest bit of terrorist activity.
Read through the general and help threads... You'll see.
Try notarized rom (search) and then wait for the next official release (5.1.1?) .
Click to expand...
Click to collapse
Yea bro I'm on of5 now

And any backups to share hmmmm

Ill see what i csn do

tjgr17 said:
OEL? I don't understand why It won't mount the system partition in twrp. I had no initial issues at all. I even flashed a Cyanogenmod nightly. It's still early and wasn't very stable so I went back to a backup I made. worked fine. I was back to rooted stock. Then the next day it froze and here I am.
Click to expand...
Click to collapse
Flash CF Auto Root through Odin and it will put you back on your last rom that booted.

xxSTARBUCKSxx said:
Flash CF Auto Root through Odin and it will put you back on your last rom that booted.
Click to expand...
Click to collapse
Yes, also noticed OP's Odin 1.85 is old.
To OP: CF Auto Root comes bundled with the recommended Odin. I think we're using 3.07 or 3.09 but 3.07 is recommended to uncheck the auto-boot so user can pull USB and battery after flashing custom recovery over OE1 so it sticks.
I also recommend flashing root tar and rebooting as chain fire recommends. "If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home)."
Once booted, see what build you have.
Sent from my SM-N910P using Tapatalk