Related
i flash my phone alot. im not sure why im having this issue. i couldnt get cm9 to install with touch recovery so i flashed a nontouch 5.x like it said to do. i got cm9 installed with it, but when i boot back into recovery the aroma installer gives me the choices, but in one second it says its done. i reboot and it still say rc2. tried just wiping cache and dalvik, then tried full wipe. same thing. anyone know what im doing wrong? i really love this rom and want it to run. :crying:
jasonsamms666 said:
i flash my phone alot. im not sure why im having this issue. i couldnt get cm9 to install with touch recovery so i flashed a nontouch 5.x like it said to do. i got cm9 installed with it, but when i boot back into recovery the aroma installer gives me the choices, but in one second it says its done. i reboot and it still say rc2. tried just wiping cache and dalvik, then tried full wipe. same thing. anyone know what im doing wrong? i really love this rom and want it to run. :crying:
Click to expand...
Click to collapse
Umm, read the thread? Armygunner posted that the updater script had a flaw, he is uploading a new build.
I got it thankyou
Sent from my SAMSUNG-SGH-I727 using xda premium
I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?
Boot into recovery and wipe your cache and dalvik cache again
mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use
I still want to keep my phone rooted. This wont kill the root right?
No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner
Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):
I'm going to install cm10 right now them go back to stock rooted and see what's up with this
There's no issues going back and forth. You probably flashed a bad ROM
yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.
DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10
redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.
about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks
and to clarify , it was gapps 4.2.2
Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.
If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app
i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .
You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.
actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.
i figured out twrp. never gave it achance. ill see if that does the trick
tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks
Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?
Just got my n5 and decided to unlock and root it, everything went well until I wanted to flash a rom, no matter what rom I flashed I got all kinds of issues from all apps force closing to bootloops, soft keys not working ect. I've tried flashing stock img, factory reseting ect, nothing seems to work. I'm not sure what's going on here, any help?
I am probably already asking you questions you have already done but... Have you reformated the system, data, and cache partitions prior to flashing? Also are you checking the MD5 of the ROMs you are trying?
Yeah tried all of that, md5's are correct, thanks though
what recovery and version are you on?
what wipes exactly are you performing?
you've checked the md5?
Ok. just trying to narrow things down. When you flash the stock image from https://developers.google.com/android/nexus/images#hammerheadkrt16m are you running the flash-all script? And after that before even adding any apps or changing anything does it give you issues?
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Xolith said:
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Click to expand...
Click to collapse
are you flashing a gapps add-on package with your custom roms? the right gapps?
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
simms22 said:
are you flashing a gapps add-on package with your custom roms? the right gapps?
Click to expand...
Click to collapse
Yeah, tried a few including banks, PA 0-day, psx gapps
neomorphix said:
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
Click to expand...
Click to collapse
They appear right after I flash the rom, tried with both the included and with a custom one
Tried a few days later and it worked, weird haha. Thanks though
So I'm trying to install custom ROM on my friend Nexus 5, should be a 2 minute job turns into 2 hours..
CWM is giving me a list of can't mount anything basically.
I tried fe-flashing the entire phone back to stock via fastboot, that went fine, flashed recovery again to CWM.. and can't mount anything again..
I need to be able to mount in order to install zip...
anybody can help??
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
THE_KINGDOM said:
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Click to expand...
Click to collapse
yup, you will need to wipe and reflash.
still can't mount sdcard in recovery..
so i can't do anything.. I had to sideload the ROM..
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
THE_KINGDOM said:
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
Click to expand...
Click to collapse
try twrp recovery
but i've been using CWM forever on every nexus device without problems..
I though process is simple.
1. Unlock bootloader
2. Fastboot flash recovery recovery.img (cwm)
3. wipe & install custom ROM (Purity)
4. gapps
5. start phone..
what am I missing???
so I tried installing the previous version of CWM 6.0.4.4 and CWM problems seems to be resolved.. clearly they must have issued with the latest version.
Now im able to read /sdcard and hopfully install purity ROM, gapps etc.
but I'm still getting the system UID's inconsistent issue...
what a colossal waste of time...
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
anybody?????
THE_KINGDOM said:
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
Click to expand...
Click to collapse
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
THE_KINGDOM said:
anybody?????
Click to expand...
Click to collapse
No bumping within 24 hours is the forum rule. I also believe they should set a punctuation limit. Chill out
Sent from my Nexus 5 using Tapatalk
Lethargy said:
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
Click to expand...
Click to collapse
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
THE_KINGDOM said:
what am I missing??????
Click to expand...
Click to collapse
cwm recovery SUCKS. but if you are unwilling to try other recoveries, oh well..
THE_KINGDOM said:
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
Click to expand...
Click to collapse
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Lethargy said:
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Click to expand...
Click to collapse
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
BirchBarlow said:
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Click to expand...
Click to collapse
CWM is built from CM11 4.4.3 source code.. But yeah it has issues., lacks functionality and also is antiquated
Sent from my Nexus 5 using Tapatalk
THE_KINGDOM said:
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
Click to expand...
Click to collapse
Don't know what to tell you, just try TWRP. I've had issues with CWM on every single device I've put a custom ROM onto (Xperia Arc S, HTC One M7, Galaxy S4, HTC One M8, Galaxy Note 3, Xperia Z, Nexus 5), and never had a single issue with TWRP on any.
gonna try Philz Touch CWM and if that doesn't work then TWRP