Hello,
I'm new to custom ROM flashing and I fear something might've gone wrong. I basically rooted my Nexus S (i9020A) and tried to installed CyberGR mod v5 through clockwork recovery (after installing from market) I wiped dalvik cache but deemed it unnecessary to clear data because I had just rooted the phone , everything seems to have gone well, flashed the ROM, phone automatically rebooted, and now I am presented with a colourful boot screen (presumable the mod's one). Thing is, it has been like that for more than 20 mn :s, and I'm not sure what to do now, is this normal?
Hi,
it shouldn't take longer than 10 minutes.
Even though you just rooted your phone, follow the instructions in the OP and everything should be fine.
Go back to CWM, wipe everything and flash it again.
Have fun!
Thank you Kramonte, works perfectly now.
SOLVED
Related
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
quanium said:
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
Click to expand...
Click to collapse
Hi Buddy,
What you should have done when your phone froze after crashing the system server is to have taken your battery out and then just re-booted your phone, all would have been good.
If you are still at the same stage now from when you posted just flash the fxp kernel in the flashtool provided by J, your phone will now boot with FXP030b.
You was never close to bricking your phone so do not worry.
I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
atlcr said:
I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
Click to expand...
Click to collapse
Nevermind...apparently pressing vol. down when the LED flashes blue gets me to a boot menu. Pheww!
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Please ask all questions in Q&A. Thread moved there.
atlcr said:
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Click to expand...
Click to collapse
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
3ze said:
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
Click to expand...
Click to collapse
I don't think he has to flash the sbf, just flash gapps n wipe data n cache. also try dalvik cache
Sent from my MB526 using xda premium
You could simply install a new .zip from recovery. You could use the same CM10 11/28 or any other rom. This shoud work out for you.
I experienced the same with my Defy today and I installed a new CM 10 09/05 by Epsylon and it worked like a charm.
Thank you for the replies!
I had to flash it a hundred times to get it to work (I kept getting write access errors for cache folder). What ended up working was to wipe everything and install the 9/24 build. From there, I rebooted and installed (without wiping) the latest build along with the correct gapps. It works fantastically now! My phone is soo much more responsive and I'm loving CM10.
3ze had it right. I was using the latest gapps (12/2) instead of the "minimal" version in the quarx dir.
I haven't noticed a battery drain as has been widely reported here. In fact, it seems to be less of a drain now though that is likely due to the fact that I wiped everything and only installed apps I needed this time around. Tons of unnecessary apps could explain why my battery life was less before.
I have noticed a slight difference in reception now though. Places that used to be fine for connecting to the network (Tmobile) have now become less strong and frequently dropping out. I wonder if the signal strength could have been messed with?
So ive had my n7 for a while and had over 10 different roms that i went through before landing on cookies and cream for 4.1.2 and cyanogenmod for 4.2.1
Well heres the problem. i was getting pissed off at all of the bugs and random reboots and incompatabilities so i fully wiped the device, minus bootloader, and flashed stock 4.1.2, it booted great
heres where it went wrong... i tried flashing cyanogenmod 10 via twrp, letting it use its stock kernel and even trying a different cm compatible kernel after booting failed.
when that didnt work i went back to stock, downloaded cookies and cream, wiped the rom, cache and dalvik cache. still bootloops
so i was like F**k it, and installed stock 4.2.1, booted fine.
tried again with the 2 latest cyanogenmod nightlies, which i know worked fine from before
still just bootloops with no idea how to fix it.
just to be clear, stock works, custom WILL NOT
bump guys, im kinda up **** creek without a paddle, emphasis on the kinda part
I have a similar problem(http://forum.xda-developers.com/showthread.php?t=2073977). Pretty much the only way I can get a ROM to stick is if I wipe /data as well. Not sure what's causing this, but I'm working on it. I think it could have something to do with the way that android stores some of it's /system data in /data at times
What's worked for me to flash a ROM other than stock, is to wipe the entire thing, and then use adb sideload to load the ROM.
Hey bro, i saw your thread before, by data, do you mean internal storage or just the system rom itself, because i wiped everything but the bootloader and started from scratch
I'm just talking about /data. An hour ago I noticed that as long as I use the Factory Reset option in TWRP, it will wipe it, and not touch the stuff on the sdcard(it could be just me though, my Nexus seems to be kinda weird). Then I wipe system, and flash whatever I need to.
Alright, one problem though, doing a factory reset deletes everything on the sdcard then when i try to use fastboot to flash cyanogenmod in a zip format it says stuff like android-product-info.txt is missing and whatnot, what do you do?
edit, dont read the part about wiping storage, i had a idiot moment there, ill give it a shot
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
ricomana said:
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
Click to expand...
Click to collapse
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
malybru said:
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
Click to expand...
Click to collapse
Thanks for replying
I followed the instructions and succesfully installed the official stock rom for my device and region.
But it's still stuck at the samsung boot screen.
And now i can't boot into TWRP anymore either, is that correct?
After that I flashed with the .pit file. But still stuck on bootscreen.
Is there any other way to solve this problem?
idgaf about custom roms or CM10.2 anymore, i just want my phone to work.
Wether it's with custom or with stock firmware.
Really hope I didn't break my phone. :crying:
EDIT:
I wiped cache after flashing, but no data wipe/factory reset. That did the trick.
God i can't be happier my phone finally works again. Now i'm scared to flash a custom rom again. I think i need to install TWRP or CWM again too I'll just wait for now.
Hello,
Firstly I want to apologies for creating new thread for a thing on which there already number of threads here. However when I was in this big trouble (at least it was for me) on Saturday evening I searched everything and couldn't find a working solution.
And I would like to request moderator or someone who has better knowledge of what did happen and how it got fixed can make it guide with his thoughts if there is a need to .
Let's start with my story. I unlocked bootloader first time and flashed CWM. While restarting I tried to wiped data as told in one of the tutorial and then I restarted. As long as I remember it said you would not be able to boot in CWM again and I said Yes. That's the time when it got stuck to X logo. I flashed CWM again and then tried to restart still nothing happened. I got further and flashed CM 10.1.2.
Then it got stuck to CM logo. I wiped cache, data, dalvik cache before and after; nothing helped. Then I managed to Power off phone and planned to go for sleep. I thought I have ruined my phone
This is how I fixed it:
At the last moment I thought to give it a last try before sleeping. I could not have went to sleep with that I thought Then I rebooted my Nexus 4 in CWM and went to 'Mount and Storage'. Mounted everything which were in unmount state. Formatted data. Went back a step then wiped data. And restarted. And there it got rebooted in CM 10.1.2 :highfive: