Database Info

[Q] CWM sticking, stock recovery isn't coming back

for some reason my cwm recovery is sticking and its causing my play store to stay on 3.4.7
Any ideas on why the recovery is sticking I didn't even touch the install-recovery.sh
Infact all I did was get the stock 4.0.4 image from google flash that:
Format System, data, cache, sd card, dalvik cache
Reboot into bootloader
flash bootloader, radio, update image
then flash cwm recovery and install superuser
after that my stock recovery just won't come back, any ideas?
I left the recovery on stock and the play store updated immediately, i also tried manually flashing the recovery from the stock image package from google that didn't help either.

The stock recovery has nothing at all to do with the market updating

You just need to run
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
using the recovery image in the update .zip. There's a guide here about halfway down. As albundy said though, it shouldn't have any effect on the Market updating.
Edit: Flashing a new recovery will delete all data and so on (afaik) so backup and what not first.

albundy2010 said:
The stock recovery has nothing at all to do with the market updating
Click to expand...
Click to collapse
i remember when i first started rooting and all that if you don't have the stock recovery you don't receive things like OTA updates also, thats why I wanted the stock recovery.
Also if i leave the recovery as stock the market updates immediately thats whats bothering me but when I root (flash CWM) it won't update even after hours of waiting it stays on 3.4.7
x ZackehSoul x said:
You just need to run using the recovery image in the update .zip. There's a guide here about halfway down. As albundy said though, it shouldn't have any effect on the Market updating.
Edit: Flashing a new recovery will delete all data and so on (afaik) so backup and what not first.
Click to expand...
Click to collapse
i flashed the stock recovery it didn't help, for some reason. Thats why I posted this question, thanks for the suggestion though

[Q] I can't get any 4.3 roms to work.

Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.

ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.

bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1

ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)

ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.

bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.

bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.

ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.

bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?

ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.

bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot

ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!

ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.

I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app

I am having the same problem. I have followed the steps but still no joy . Any thoughts?

sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.

the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.

[Q] Accidentally wiped system, how to revert back to stock without losing root?

So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?

xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps

xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images

Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?

xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.

xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?

Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk

xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.

gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?

xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.

gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk

xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).

gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk

Samsung Galaxy S2 Telus T989D stuck on Koodo logo after rooting

Hi There,
So, I have a Samsung Galax S2 Telus SGH-T989D phone and I decided to root it using the 4.4 KitKat and it went well and everything was great.
However, afterwards to resolve some other issues I was having I decided to make the mistake of loading the gapps which was for another
package into my phone and that messed everything up!
So, I have been struggling with the phone and first it wouldn't let me install another ROM from recovery and kept on giving me error 7 and 6
But, I fixed that and now I can install any ROM from the recovery or Odin (download mode) without any errors.
However:
The phone vibrates , brings up the galaxy logo and then the Koodo logo appears and a bar fills up quickly under it but it never goes away!!!
Phone freezes there and that's that!! Even after taking out the battery I noticed the logo was still stuck on the screen where as normally
it goes blank!!
So, at this point I am not sure what else to do! This is annoying and I'm tired of experimenting. I went through some XDA foroums here and
tried the Super Vipe (taking out the battery has been tried, factory reset and wiping the cache all have been tried)
So, please please please help me out here. I used to have a MyTouch4G which I rooted with CyanogenMod back in the day and it's the most
stable thing ever and all I wanted to do was to perform the same thing on my Galaxy S2 and boom not this time!!!
Awaiting your response and thanks in advance

King-2012 said:
Hi There,
So, I have a Samsung Galax S2 Telus SGH-T989D phone and I decided to root it using the 4.4 KitKat and it went well and everything was great.
However, afterwards to resolve some other issues I was having I decided to make the mistake of loading the gapps which was for another
package into my phone and that messed everything up!
So, I have been struggling with the phone and first it wouldn't let me install another ROM from recovery and kept on giving me error 7 and 6
But, I fixed that and now I can install any ROM from the recovery or Odin (download mode) without any errors.
However:
The phone vibrates , brings up the galaxy logo and then the Koodo logo appears and a bar fills up quickly under it but it never goes away!!!
Phone freezes there and that's that!! Even after taking out the battery I noticed the logo was still stuck on the screen where as normally
it goes blank!!
So, at this point I am not sure what else to do! This is annoying and I'm tired of experimenting. I went through some XDA foroums here and
tried the Super Vipe (taking out the battery has been tried, factory reset and wiping the cache all have been tried)
So, please please please help me out here. I used to have a MyTouch4G which I rooted with CyanogenMod back in the day and it's the most
stable thing ever and all I wanted to do was to perform the same thing on my Galaxy S2 and boom not this time!!!
Awaiting your response and thanks in advance
Click to expand...
Click to collapse
Clean solution: Flash stock firmware via Odin or install custom rom via recovery

LS.xD said:
Clean solution: Flash stock firmware via Odin or install custom rom via recovery
Click to expand...
Click to collapse
Thank you for your reply. However, as I've mentioned before, I've already tried those (from ODIN and through RECOVERY) with multiple different
ROMS and it's not doing anything which is why I am posting this here.

King-2012 said:
Thank you for your reply. However, as I've mentioned before, I've already tried those (from ODIN and through RECOVERY) with multiple different
ROMS and it's not doing anything which is why I am posting this here.
Click to expand...
Click to collapse
Did you perform a FULL wipe? Custom recovery -> format ALL partitions except EFS?

I have tried the Super Vipe off the SD card through the recovery mode and also from recovery I've tried the wipe cache,
factory reset and wipe cache partitions.
I am not sure about "format ALL partitions except EFS" nor am I aware of the procedure.
How would I perform that?

Have you installed a working custom recovery?
Sent from my beloved HTC One S using (most time buggy) Tapatalk

LS.xD said:
Have you installed a working custom recovery?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Yes I'm able to successfully install recovery-clockwork-5.0.2.7-hercules or CWM_Root_Superuser_3.1.3_Busybox_1.20.2
from the recovery without any errors (same if rooted through Odin)
If there's a specific ROM you are thinking about please let me know and I will be more than glad to give it a shot.

You really should use a newer recovery version. But for now go to mounts and storage and format all partitions except EFS. Then try flashing stock firmware via Odin
Here you can get the latest recovery for your device --> TWRP for hercules

LS.xD said:
You really should use a newer recovery version. But for now go to mounts and storage and format all partitions except EFS. Then try flashing stock firmware via Odin
Here you can get the latest recovery for your device --> TWRP for hercules
Click to expand...
Click to collapse
Under mounts and storage and format all partitions except EFS > Don't even see ESF there to begin with..
Do you have a working link for downloading the stock firmware? I have downloaded few and none of them even let me install them (status 0 error)
Any ideas?
Odin is already being used v3.0.7

Format System Data Cache dalvik. Realy... Then flash stock firmware using ODIN!
Sent from my beloved HTC One S using (most time buggy) Tapatalk

LS.xD said:
Format System Data Cache dalvik. Realy... Then flash stock firmware using ODIN!
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
I was able to finally bring it up!!
Basically I looked for a stock firmware for T-Mobile and after formatting the phones multiple times I tried this ROM
using ODIN and it got rid of the Koodo logo and replaced it with a T-Mobile logo and then it BOOM loaded to start screen finally!! :laugh:
I was about to hammer the phone. So, trust me I was very happy to see it work.
Thank you for your quick and helpful response :good:
Cheers :victory:

[Q] First boot taking forever .

Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:

TheHelplessGuy said:
Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:
Click to expand...
Click to collapse
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989

The same
jrc2 said:
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?

TheHelplessGuy said:
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?
Click to expand...
Click to collapse
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989

jrc2 said:
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989
Click to expand...
Click to collapse
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?

TheHelplessGuy said:
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?
Click to expand...
Click to collapse
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989

jrc2 said:
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989
Click to expand...
Click to collapse
The one with Android 4.1 my guess is Nature UX

TheHelplessGuy said:
The one with Android 4.1 my guess is Nature UX
Click to expand...
Click to collapse
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989

jrc2 said:
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you suggest ?

TheHelplessGuy said:
What do you suggest ?
Click to expand...
Click to collapse
I don't know, sadly. Maybe someone else will know and we'll both learn something.
Sent from my SGH-T989

Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck

150208 said:
Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck
Click to expand...
Click to collapse
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?

TheHelplessGuy said:
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?
Click to expand...
Click to collapse
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:

150208 said:
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:
Click to expand...
Click to collapse
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix

TheHelplessGuy said:
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
Click to expand...
Click to collapse
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.

150208 said:
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.
Click to expand...
Click to collapse
re-rooted as you said still the same loading screen , you can give me a link to the part of the forum where I can speak with developers as you said few comments ago