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:
Related
Howdy.
I've been using custom firmware since I got my phone over a year ago, but I'm now having big issues.
I tried to install a 4.2.2 ROM and couldn't boot, even after trying bunch of times, clearing cache, all that jazz..
So.. usually I would just put on another ROM or just restore from a backup, but I'm stuck in a weird situation.
I have a bunch of ROM backups (Clockwork Mod Recovery) going back to April last year, the 1st one is standard AT&T, then various custom ROMS (last one I used was Cynogen 10).
But I can only restore the first AT&T ROM, nothing else will restore. I also cannot even install any ROM the only way I can get a working phone is to go back to the horrible original AT&T ROM..
Clockwork mod recovery also crashes when I try to wipe cache, so think that maybe a clue....
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks
eckythump said:
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks
Click to expand...
Click to collapse
What version of CWM are you on?
You can always restore to your AT&T backup, transfer all of your other backups to your external SD or computer, ODIN to stock, do a complete wipe of the phone, flash the most recent CWM from Sk8 and try again. I'd say that's your best case scenario.
mrfeuss said:
What version of CWM are you on?
I'm on 6.0.1.4 which I believe is latest. I can't even get the original ROM to restore now either. Ughhhh hope I'm not bricked.
Click to expand...
Click to collapse
Try Odin back to stock before u do brick it that should fix any problems
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.
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989
thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.
No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.
Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989
Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app
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