Develop Bugs

Cyanogenmod 9 has made my device useless.

After installing Cyanogenmod 9 on the One X I started to notice extremely poor signal, Mobile and Wi-Fi. Also the phone would crash and randomly reboot when doing simple tasks such as opening messages etc.
Upon trying to get into recovery to install a different rom, the phone now flashes on a black screen and restarts the phone.
To try and solve this issue, I unrooted the phone and restored to stock recovery.
I then re-rooted the phone and installed clockworkmod recovery again.
I can now access clockworkmod recovery although it seems to have no effect. Installations of any rom fail and cyanogenmod always pops straight back up again after rebooting.
Has anyone else had this issue?
Does anyone have a way to fix this? Possibly to force the phone completely back to stock?

You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)

Kamiil29 said:
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Click to expand...
Click to collapse
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?

AndyB said:
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
Click to expand...
Click to collapse
Unfortunately I can't help you with SuperWipe, but you can find the HOX stock ROMs here.
Sent from my HTC One X using Tapatalk 2

Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?

AndyB said:
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
Click to expand...
Click to collapse
Did you try holding down the Power and Volume Down buttons while in the bootloop to enter the bootloader? Hold them down until the lights start to flash, the screen goes off and then the bootloader comes up.
If you can get into recovery with that, factory reset, clear cache and dalvik cache (under advanced) then try install the ROM.
I'm not the best person to be helping, but I hope that works for you!
I had a similar problem once where the phone would just sit on the HTC One X screen, and trying to go into recovery just put the phone back to the HTC screen. I fixed it by flashing the boot.img, factory reseting, clearing out caches and installing the ROM again. No problems since.
I'm afraid if this doesn't work, I may have to abandon you and let someone else take over, as I'm no expert, but I'll see what I can do to help.
Edit: sorry, it is 2AM here and I need some rest for an early start at 6AM. I will check up on this thread when I wake.
Sent from my HTC One X using Tapatalk 2

FIXED!!!
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.

AndyB said:
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
Click to expand...
Click to collapse
Glad you got if working
Sent from my HTC One X using Tapatalk 2

[Q] Verizon / TORO JB ROM Flashing Help Needed!!!

I've tried to flash the two different ROMs out for JB and for some reason it is not getting past the Nexus Logo Boot screen. I can flash any ICS ROM but JB never gets past the boot screen. I've been flashing ROMs since the OG Droid and have never experienced this before.
Steps already taken:
1) Full wipe
2) Format of system and data
3) executed Super Wipe Script
4) Battery Pulls
5) Backed out of CWM and unmounted system and data
6) Flashed Various AOKP and AOSP ROMs and tried to JB ROM from those ICS ROMs
7) Performed a factory restore of the phone using WugFresh's ToolKit (un-rooted and locked phone) and then Rooted, unlocked, and flashed CWM again
8) Flashed Team Win Recovery and re-flashed JB ROMs
I have tried everything I can think of and yet nothing has worked. Has anyone Else experienced this or does anyone have any suggestions on what I can possibly do to get past the Nexus Boot screen? Thanks in advance.

how long are you waiting after the install?

Zepius said:
how long are you waiting after the install?
Click to expand...
Click to collapse
Average wait time is 20 minutes but I've waited up to 4 hours.

which rom are you flashing?
try this one: http://www.teambamf.net/topic/4064-romtoro-jellybamf-13/
it works for me perfectly (thanks adrynalyne)

Zepius said:
which rom are you flashing?
it works for me perfectly (thanks adrynalyne)
Click to expand...
Click to collapse
I've tried Liquid Vicious Versions 1-3 and BAMF Versions 1.0 and 1.2. Thanks for the updated BAMF...I'll try that one now.

I am having the same problem as you, I flashed multiple JB roms and it is stuck at the X screen. I can flash ics roms easily tho.

I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.

I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2

keno23 said:
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Glad to pass along the help I got earlier :highfive:

consultant.ben said:
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
Click to expand...
Click to collapse
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.

i have the same the problem with my phone , i flash the jb rom it works fine the first time booting i setup my account download my apps every thing works fine BUT when i re-start the phone the phone got stock on the google logo and don't re-start again, so guess what i have to try another rom so i try a regular ICS rom guess what on the first boot the phone got stock on the boot logo so i try another ICS rom and the same thing happing stock again on the boot logo, so i have to do flash the google factory rom to my phone got back to work

Same her.. infinite boot loop.. I'm tired of unbricking back to stock
Flash all kinds of from and kernel combo and still got boot loop.. I hope someone can help us with this..

Try mROM http://forum.xda-developers.com/showthread.php?t=1763823
Make sure wipe/factory reset and also wipe caches while you're at it. Also make sure that CWM is updated.

keno23 said:
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
Click to expand...
Click to collapse
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.

nothingshocking said:
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
Click to expand...
Click to collapse
Are you wiping dalvik and system cache along with doing data wipe?

mb9023 said:
Are you wiping dalvik and system cache along with doing data wipe?
Click to expand...
Click to collapse
wipe data/factory reset -> wipe cache partition -> wipe dalvik -> format /system -> format /data -> format/cache. I've tried super wipe. All Roms never get passed the boot animation. I get past the "Google" unlock symbol, but it just sits at the boot animation. It doesn't reboot or anything, just sits there for hours or when I get bored looking at it after about 30 minutes or so.

@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App

landrian18 said:
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Not going to happen man...I've tried EVERYTHING and have gotten feedback from various devs to no avail. All I get is Nexus boot logo FOREVER.
Solution is to flash it back to stock (plus unroot and re-lock) and then take it in to a store and get another one shipped to you since it's still under the annual warranty. As for the issue for bringing it in, just say it boot loops at random times (that's not technically a lie).
Sent from my Galaxy Nexus using Tapatalk 2

Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM

adclem said:
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
Click to expand...
Click to collapse
That doesn't work either. Thanks though.
Sent from my HTC One X using Tapatalk 2

[Q] Need Help Small Problem

So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.

Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you tried unrooting and rooting again?
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Lastly - I have heard people needing to reflash several times before it "takes" which it sounds like maybe you've tried & I realize these may be very basic things for you but you never know hopefully someone can help the more info you provide.

ldd_recoil said:
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you ever successfully loaded a custom rom on this particular phone?.... because you may have improperly rooted
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
I am on a custom rom now and everything is fine..but when I try to flash anything other than a Touchwhiz rom it seems to fail. I had paranoid running for a little while but I could not access my external sd so went back to my Jedi Mind Trick rom and everything was fine...so I decided to try a different paranoid thinking the issue was with this specific rom and it would not boot..went back to JMT and then tried aosp cm10 rom thinking and it wouldn't boot.
i have tried everything you have suggested except for the Factory Reset after the flash. Never really check the MD5 though. Might give it a try later on when I get bored with this rom again.
Thanks,
T

Sorry, reread your post now that I have the right context... Try unrooting and rerooting if you continue to have new rom flash issues.

toreone said:
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Click to expand...
Click to collapse
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:

srikanth.t989 said:
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
Click to expand...
Click to collapse
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
EDIT::: THIS WORKED...IT WAS HUNG UP ON BOOT IMAGE..FOLLOWED INSTRUCTIONS ON TOP AND BINGO!!!! I SAW THE MAGIC

toreone said:
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
Click to expand...
Click to collapse
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!

cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
I actually tried this yesterday and it went through the motions and when I restarted into recovery it was just like a blue background with the Team Win on it but never made it past that...so I had to flash back to CWM through Odin to get it to be able to flash again..

cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
After doing this try downloading quickboot to boot into twrp recovery, if that doesn't help you might need to flash back to stock/re-root and start from square one =/

[Q] ALL 4.2 ROMs hate my phone. Help thread.

So building and flashing ROMs is nothing new to me. I've been doing this since the Captivate days and have done this with all of my Android devices including my new Kindle Fire 2 (which is running 4.2) but for the life of me, I cannot get a 4.2 ROM running smoothly on my GS3.
Here's the deal. When flashing any 4.2 ROM, I get the same issues. Most times, it takes several (as in at least 8) presses of the Power button or home button to wake the screen. When it finally wakes, the animation on the "unlock" button freezes. I can sometimes still swipe it to unlock but most times, the button itself doesn't move. The phone typically runs fine once unlocked.
I know there are some camera issues still but mine make it totally unusable. I can open the camera but rotating it typically screws the orientation up on screen and no other screen presses work afterward. If I tap to open settings or flash settings, the options show up on screen but then again, screen presses are no longer working. I have to exit camera and start over which typically results in a couple Gallery FCs before it finally opens again.
What I've done to no avail. I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP as well as checking MD5 on the ROMs after they've been copied to my SDCard and am running the latest TWRP available for my phone. I have also tested this without restoring ANY data and using the packaged launchers and I get the same behavior. If I go back to a 4.1.1 ROM, everything is perfectly fine. This ONLY happens on the 4.2 ROMs available.
I'm looking for any help on getting this sorted not because it's a big deal but because it's driving me friggin' insane!

Re: [Q] ALL 4.2.2 ROMs hate my phone. Help thread.
Have you tried CWM Recovery yet? It's what I use and have literally tried every rom put there with no problems ever.
Sent from my SGH-I747 using xda premium

Jirv311 said:
I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP
Click to expand...
Click to collapse
You don't mention it, but did you use the wipe option that is at the bottom left of the TWRP wipe menu screen? The scary looking one that says it's probably not needed?
I do that one every time.
I would restore to stock 4.1.1. Then flash TWRP's latest again and try one more time by flashing something mainstream like CyanogenMod 4.2.2.
Flashing stock ROM's has fixed a couple weird issues for me lately.

I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?

Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
Have you tried a different kernel? I run ktoonsez KT747 with Task's AOKP with awesome results. Nothing against Task's underwear kernel, but maybe the 4.2 version just doesn't like your phone.

Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426

Intub8 said:
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.

Jirv311 said:
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
Click to expand...
Click to collapse
yes that is very odd. If it works fine on stock or 4.1 rom's then it definatly not a hardware issue with the button. Im sorry man , I have no idea what it could be.

Yeah I'm confused as well. I just flashed the last CM10.0 4.1.2 and it runs flawlessly. Definitely a head scratcher.

GNex stuck in boot loop since 4.3 flash

Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?

Flash the official Google image: http://forum.xda-developers.com/showthread.php?t=2376687

check dreams rom thread and see my post there
Sent from my Galaxy Nexus using Tapatalk 4 Beta

Fix it by flashing factory images! do a full wipe, you can get imprtant stuff from your Nexus by using adb pull commands!
Users was blaming me when they screwed their Nexus with the root files!
I can successfully even flash old root files and no bootloops but ofc. root wont work if using those old root files.

OP, did you factory reset between ROM flashes?

beekay201 said:
OP, did you factory reset between ROM flashes?
Click to expand...
Click to collapse
pulling files then flashing 4.2.2 stock image to start fresh

NyPlaya513 said:
Ok, I am paranoid and want to be sure about this. I am in the same boat as the OP. I have a 32gb toro on twrp 2.5. I am under the impression that flashing the stock images will flash my sdcard partition and I want to pull some files if that is the case. Is there anyway to pull the files or am I stuck and need to start fresh.
Click to expand...
Click to collapse
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.

NeoMagus said:
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
Click to expand...
Click to collapse
nvm pulling files

If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it

NeoMagus said:
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
Click to expand...
Click to collapse
nvm got the toolkit to pull files via adb for me on my parallels

agent47er said:
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Click to expand...
Click to collapse
"just wipe data" in recovery after flashing, solve bootloop issue

dexviajiboy said:
"just wipe data" in recovery after flashing, solve bootloop issue
Click to expand...
Click to collapse
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.

agent47er said:
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
Click to expand...
Click to collapse
i dont think there's any kernel for now, give it some time and you'll get one