So back in july i decided to get a custom rom and went with cm 10.1. When i was flashing the rom my phone got stuck in a boot loop but it evemtually fixed itself. A few days ago i decided to update to another version ofcyanogenmod, and during the update my phone was again soft bricked. It evemtually got back to normal after i did a factory reset in clockworkmod recovery and when it got back to the homescreen i noticed none of the stock apps were there. I thought it was just the version of cm that was glitchy so i tried getting another version but when the phone reboots in recovery it shows an error has occured. It also wont let me flash other roms and it's really annoying how i only have a page of apps like messaging, phone, calculator, clock etc..... PLEASE HELP ME!!!!
crhis27 said:
So back in july i decided to get a custom rom and went with cm 10.1. When i was flashing the rom my phone got stuck in a boot loop but it evemtually fixed itself. A few days ago i decided to update to another version ofcyanogenmod, and during the update my phone was again soft bricked. It evemtually got back to normal after i did a factory reset in clockworkmod recovery and when it got back to the homescreen i noticed none of the stock apps were there. I thought it was just the version of cm that was glitchy so i tried getting another version but when the phone reboots in recovery it shows an error has occured. It also wont let me flash other roms and it's really annoying how i only have a page of apps like messaging, phone, calculator, clock etc..... PLEASE HELP ME!!!!
Click to expand...
Click to collapse
You need gapps. 10.1 requires the 4.2.2 ones. In my signature.
Related
I have a serious problem. I have a Samsung Galaxy s II Tmobile for about a year now I have had it rooted since day one with not one problem with it. I mostly have had installed custom roms is all. I Just recently updated to CM10.1 nightlys with no trouble. I thought I would update the custom recovery since its been a while I went from 5.0.2.7 and updated to 6.0.2.8 and this is where everything went wrong. my phone went into a bootloop at first wouldn't load at all I went into recovery restored to a cm 10 which was working before which now is doing a boot loop. and i restored back to 2.3.5 rooted and that worked. but with some serious problems. I can't download anything like from the web or play store at all I keep getting this error code 492. I was thinking ok well I'll just put a fresh copy of cm10.1 back on the phone flashing it through recovery and nothing it froze. I played around with this new recovery and found out that I can't install anything through recovery can't fix permissions won't format won't wipe cache or factory reset and it won't even reboot the phone the only thing i got it to do was restore to 2.3.5. well I thought ok well I'll just start over again by unrooting the phone and start at square one again. no problem as the phone isn't bricked but when I hooked it to the computer now its not recognizing it. it comes up as unknown device which worked yesterday and never had a problem before i tried uninstalling drivers off my computer reinstalling them to no success. however I thought If I somehow get rom manager back on the phone i can reinstall 5.0.2.7 back on which i did come up with the idea to use kies air for that which did work. but I couldn't get back to 5.0.2.7 by doing that does anybody have any suggestions that can help me out my phone is working i can do everything that it is suppose to do make call connect to the mobile web, wifi but i want back on my custom rom can anybody help thanks
hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Darkmanx said:
hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Click to expand...
Click to collapse
Which recovery are you running?
joeyhdownsouth said:
Which recovery are you running?
Click to expand...
Click to collapse
I got it, I finally got stock a rom to load via Odin but it was getting stuck on the Samsung screen so I rooted it before it even let me in. Then i did a wipe and it started up and now all is well stock 4.3 rooted. This reminded me why i always choose stock rooted roms
I recently installed CyanogenMod 11 on my S3 about a month ago. Yesterday, I got a notification on my phone stating that an update was available for CyanogenMod. I let it install and when the phone rebooted, it was stuck on the bootloader for at least an hour or two. I figured that I must've bricked the phone. I can still get into recovery mode and download mode.
So, I tried to reinstall the stock AT&T GS3 ROM as I had never particularly liked CyanogenMod. I thought this would be a great time to reinstall the stock ROM. I factory reset the phone and flashed the stock ROM (which I downloaded from another thread) using Odin. It automatically rebooted, the Samsung logo flashed for a second and the CyanogenMod bootloader showed up and it has not gone away since. So, what have I done wrong here and is there a way to save my phone? Any help would be greatly appreciated.
Where did you get the ROM you flashed? Did your phone have the 4.3 bootloader? What about Knox?
If your phone has the 4.3 bootloader, you cannot flash the 4.3 ROM via Odin as it was never released as a complete ROM, only as an update. THis might help: http://forum.xda-developers.com/showthread.php?t=2658486
Hey,
I had AOSP installed on my ascend p6, everything working no problems at all.
Suddenly when I was a week on vacation when my battery died it wouldn't get passed the rom loading screen.
I have TWRP 2.7 and have wiped everything and everything over and over but nothing is working. I am now trying to install The lastest aosp sincde OMNI and CM11 didn't work.
Any help how to fix this? it keeps happening at every rom I install.
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
UPDATE: Okay somehow after rebooting it around 20 times with fastboot, recovery and other combinations it is now booting I think. Praise the lords. It is now optimizing the apps
I have no idea what I did but I will post an update when it is done optimising
UPDATE UPDATE: Okay the weirdest thing just happened and I don't get this at all... I have wiped my whole phone like 5 times. with itsto and exsto. but somehow I now boots with all my apps, settings and launcher intact and inplace... I even installed multiple roms trying to make it work. WHAT IS THIS MAGIC?!
I know I shouldnt do this but I am going to re-install twrp 2.6.*.* and then pushing it to 2.7. Wish me luck! (following the excact instructions to make it work haha)
UPDATE UPDATE UPDATE: Okay, After seeing the wi-fi not turning on I tried rebooting my phone now it is stuck at the huawei ascend screen.
TomTheTiger said:
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
Click to expand...
Click to collapse
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
warea said:
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
Click to expand...
Click to collapse
Will try! I thought I was passed this haha. When It starts i'll try to figure out a way to install it probs trough adb fastboot. since I can't get to the recovery screen with buttons
Update: Okay I managed to boot recovery up trough adb, It automatically started installing the update.app package.
I am now hoping for the best, one good thing... My phone was luckily already in unlock state
UPdate: Succesfully flashed my phone the stock with unlocked bootloader!
UPDate: And now on omni rom Everything is working fine!
so much like a handful of other people around here today, I soft bricked my phone yesterday morning with an ATT OTA update.
I have managed to get CWM 6.0.4.7 working, and I have tried multiple ROMS, but I can not get anything to boot past the splash screen.
please, I know I must be missing some simple thing, but I can not find out what I am doing wrong despite digging through threads all day here.
I have reset caches, data, etc, dalvik, all the recommended steps...
nothing seems to be able to boot, but I feel like I am soooo close.
thanks in advance
solution - revert, reset, reinstall
this softbrick with no potential for rollback was solved with a combination of techniques.
firstly, I used zadig and heimdall to flash a cm11 recovery into the phone.....
then, I used that recovery to install roms....
they were all locking up on boot.
I reverted back to a stock recovery for the phone 4.3 ish
then did the zadig / heimdall recovery again, installed the latest nightly of CM, and it booted!
flashed carbon kitkat, with the proper gapps, and back in action...only took a whole day!