I successfully rooted my galaxy s3 with odin, then I tried installing the cyanogenmod. I backed up my data and apps on titanium backup before doing so. Now everytime it try to boot up my device it gets stuck on the boot screen. I tried wiping data/factory reset and rebooting system afterwards but the problem still occurs.
will letting the battery die help???
any help is awesome THANKS!!!!!
ogloc240 said:
will letting the battery die help???
any help is awesome THANKS!!!!!
Click to expand...
Click to collapse
Nop.
Get back in recovery, and re-follow their full instructions.
My guess is that you'll have to wipe system, cache and dalvik. Then reflash CM and their respective Gapps.
PS.: It can take a while to boot up.
Related
Hi,
I just got the S3 on Mobilicity in Canada. I rooted it and installed cyanogenmod 10 on it but didnt like it so I tried to install this (http://forum.xda-developers.com/showthread.php?t=1771687) stock back to my phone. Now my phone is stuck at the samsung logo. I can still get into download mode but cant get into CWM. Im really worried. Please oh please someone help me!
jd402 said:
Hi,
I just got the S3 on Mobilicity in Canada. I rooted it and installed cyanogenmod 10 on it but didnt like it so I tried to install this (http://forum.xda-developers.com/showthread.php?t=1771687) stock back to my phone. Now my phone is stuck at the samsung logo. I can still get into download mode but cant get into CWM. Im really worried. Please oh please someone help me!
Click to expand...
Click to collapse
Odin back to stock
Sent from my SGH-T999 using xda premium
funziebear said:
Odin back to stock
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried but I still get the same problem. Maybe Im doing something wrong. I put the phone in download mode, open Odin, plug it in, click PDA, choose the stock I got from the SamMobile site, and it runs completely but then gets stuck on reboot at the Samsung logo still.
go into stock recovery by powering on the phone while holding home and volume up, then choose the option to wipe cache, then reboot.
Agreed. I had a similar issue the other day. I ended up wiping cache in samsung recovery, and if that doesn't work, wipe data factory reset. I tried rebooting, but it still got stuck at the samsung logo. I then flashed CWM recovery or TWRP recovery through ODIN and then download another rom. Do a factory reset within the new recovery / wipe cache/ wipe dalvik/ wipe system/ and then flash the new rom. That will get it to boot.
Moral of the story is to not freak out too much. You're not in trouble.
bstapley said:
Agreed. I had a similar issue the other day. I ended up wiping cache in samsung recovery, and if that doesn't work, wipe data factory reset. I tried rebooting, but it still got stuck at the samsung logo. I then flashed CWM recovery or TWRP recovery through ODIN and then download another rom. Do a factory reset within the new recovery / wipe cache/ wipe dalvik/ wipe system/ and then flash the new rom. That will get it to boot.
Moral of the story is to not freak out too much. You're not in trouble.
Click to expand...
Click to collapse
Yep if u can still get into
Download mode there is plenty of hope of booting back up I had same issue and most the tars I was using held up till I found one that worked I have it saved if u need it lmk
Sent from my SGH-T999 using xda premium
bstapley said:
Agreed. I had a similar issue the other day. I ended up wiping cache in samsung recovery, and if that doesn't work, wipe data factory reset. I tried rebooting, but it still got stuck at the samsung logo. I then flashed CWM recovery or TWRP recovery through ODIN and then download another rom. Do a factory reset within the new recovery / wipe cache/ wipe dalvik/ wipe system/ and then flash the new rom. That will get it to boot.
Moral of the story is to not freak out too much. You're not in trouble.
Click to expand...
Click to collapse
+1
The wiping is key
Sent from my SGH-T999 using xda premium
ok so this may sound strange but my phone will not boot up. i have tried flashing different roms and always their boot images via fastboot right after i instal the rom. Right now my device boots up and shows the splash screen and then imediately boots into bootloader mode. i got to this problem by restoring a previous backup and then flashing its boot.img. can anyone help me or tell me whats going on?! it would be much appreciated!!! right now im out of a phone.
Erase the dalvik cache from recovery. Also something else you need to do, but I forgot what.
BenPope said:
Erase the dalvik cache from recovery. Also something else you need to do, but I forgot what.
Click to expand...
Click to collapse
thanks, im guessing the next thing is just to flash the recovery image again?
No.
i ended up just wiping data, cache, and formating the system again, followed by restoring the rom and re-downloading the boot.img again and it worked after flashing the boot image the second time. scary stuff...
So I installed CyanogenMod 7, and after the reboot everything looked great, but now I have rebooted one more time, and i'm stucked on this HTC logo, with white and green.
I don't know what to do, I can enter the recovery mode, but the Backup and Restore don't work. I tried to pick off the battery too.
Please can you help me?...
It's your first flashing, isn't it?
You have to backup from recovery before you install a rom. If you didn't, you just lost all your internal data.
Go to recovery, wipe all partitions except sd-card, flash cyanogenmod again, then reboot.
abaaaabbbb63 said:
It's your first flashing, isn't it?
You have to backup from recovery before you install a rom. If you didn't, you just lost all your internal data.
Go to recovery, wipe all partitions except sd-card, flash cyanogenmod again, then reboot.
Click to expand...
Click to collapse
Yes it's my first flashing. I did the backup. But the restore doesn't work. And I wiped too.
But I have to precise that when this happened, I have a low battery. I don't know if it's matter.
ChargementEnCours said:
Yes it's my first flashing. I did the backup. But the restore doesn't work. And I wiped too.
But I have to precise that when this happened, I have a low battery. I don't know if it's matter.
Click to expand...
Click to collapse
It doesn't. You surely did something wrong. When you restore the backup, what does it do? Bootloop? Stuck at HTC Logo?
Success !
abaaaabbbb63 said:
It doesn't. You surely did something wrong. When you restore the backup, what does it do? Bootloop? Stuck at HTC Logo?
Click to expand...
Click to collapse
So I rebooted in recovery mode again and installed again Cyanogen and it worked !! Now there are no problems anymore !!! Thank you for your help !
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
chortiman said:
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
Click to expand...
Click to collapse
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Mr.201 said:
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Click to expand...
Click to collapse
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
chortiman said:
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
Click to expand...
Click to collapse
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Mr.201 said:
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Click to expand...
Click to collapse
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
chortiman said:
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
Click to expand...
Click to collapse
Glad it worked, make sure you untick 'system' in filter in titanium backup so that you can only see your user apps .
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the cm13 rom and reinstalling the custom rom like I did the first time using twrp.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop where its stuck at now.
Any suggestions on how i could get it running again? Thanks!
Note2mk said:
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the cm13 rom and reinstalling the custom rom like I did the first time using twrp.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop where its stuck at now.
Any suggestions on how i could get it running again? Thanks!
Click to expand...
Click to collapse
Tried putting stock rom back on but still bootlooping. When i go into android system recovery it says twice
E:failed to mount /efs (Invalid argument)
Search for efs.tar file on the internet for n7100, flash it via Odin then wipe data, cache and davlik cache.
Skull97 said:
Search for efs.tar file on the internet for n7100, flash it via Odin then wipe data, cache and davlik cache.
Click to expand...
Click to collapse
Thanks. Any instructions /tutorials on how to flash an efs file?
Is it the same procedure as flashing a stock ROM using Odin?
Note2mk said:
Thanks. Any instructions /tutorials on how to flash an efs file?
Is it the same procedure as flashing a stock ROM using Odin?
Click to expand...
Click to collapse
It should use the same procedure as flash stock ROM. I'm not sure because the last time I did it was some years ago.
I have found another way, it's a bit hard, but safer
http://www.selftechgenius.com/how-t...nvalid-argument-in-all-samsung-galaxy-phones/
Skull97 said:
It should use the same procedure as flash stock ROM. I'm not sure because the last time I did it was some years ago.
I have found another way, it's a bit hard, but safer
http://www.selftechgenius.com/how-t...nvalid-argument-in-all-samsung-galaxy-phones/
Click to expand...
Click to collapse
Gave it a read. Phones not entering recovery mode anymore so not sure I can proceed. Maybe try flashing stock ROM again.