Related
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
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).
Hi -- I can't find anything else here at all about this.
Over the course of about 3 hours today I've been trying to get my Nexus 7 (2013) to run multiple roms using this tool:
http://forum.xda-developers.com/showthread.php?t=2457063
I'm going to try to give you as much information as I can.
This is a Nexus 7 2013, Wifi, 16GB
pics: http://imgur.com/a/mSonj
Just incase you missed any of that,
Nexus 7 2013 FLO
Cyanogen Mod 10.2 9/21/13 Nightly Build
TWRP v2.6.3.0
Anyway, here's my problem.
I'm trying to get this tablet to run Cyanogen Mod 10.2 and Ubuntu Desktop 13.04 Raring.
I started off by flashing the custom TWRP recovery, which worked perfectly.
I wiped the cache and dalvik just to be safe.
Rebooted into my Cyanogen Mod which still worked.
I then used the custom TWRP recovery to flash the multirom.zip in that thread.
I wiped the cache and dalvik once again, rebooted, and it worked.
Cyanogen was then my internal with absolutely no problems.
I used TWRP recovery to add the Ubuntu Rom which still posed no problems, the internal booted well but obviously I needed a Kexec patch Kernal to actually boot the Ubuntu image.
Once I flashed the custom Kernal though, the internal would not boot, getting stuck on a black screen.
The Ubuntu rom would attempt to start but get stuck on the Google logo.
Please excuse my complete noobiness, this is literally my first post here and I've only had this tablet for approximately a month or so.
Is anyone having a similar or the same problem, and is there any solution? Thank you so much.
If you've actually read to this point I love you lol
It's related to the patched kernel (I guess), it won't boot my CM10.2 rom, too. It's also mentioned in the CM10.2 thread that ROMs from 09/25 won't boot with the included kernel. You can use the 1.6 beta ElementalX kernel which has the needed patches included, (didn't tested it), wait for an updated (patched) CM kernel, or use a stock based rom as primary rom, the patched stock kernel boots fine. You only have to flash back your working kernel, make backup in TWRP, install any stock based rom, (Full-Wipe), flash patched stock kernel, add rom (Backup), choose your backup. As far as I know, any other system as Android isn't available(working?) ATM, that's the reason you can't boot Ubuntu.
Edit:
ElementalX 1.6 Beta working fine
Gesendet von meinem Nexus 4 mit Tapatalk 4
I'm really sorry I can't be of help, but where did you get the Ubuntu download?
Regardless of your kernel's problems :
Ubuntu will not work on your tablet. It does not have yet the requiered drivers, and I didn't see any team working on it.
Ubuntu touch has some experiments for the Flo version, but nothing that works, and nothing that can be released now, I think.
For a GNU/linux distro ROM, you'll have to wait or buy another device.
iPWNtehNOOB said:
I'm really sorry I can't be of help, but where did you get the Ubuntu download?
Click to expand...
Click to collapse
It's just the raring preinstall image, google it.
For everyone else, thank you all for giving me simple answers.
I'm going to try that kernal later.
I would thank you if I had any idea how
I guess you won`t see the thanks button before you will reach at leat 10 posts.
xPoseid0n said:
It's just the raring preinstall image, google it.
For everyone else, thank you all for giving me simple answers.
I'm going to try that kernal later.
I would thank you if I had any idea how
Click to expand...
Click to collapse
Isn't that only for the old Nexus?
I wiped the dust off my old S2 in hopes to get it running again. The last ROM I had on it was Jedi Mind Trick JB 4. I flashed sultanxda's CM11 ROM and it booted up fine(logged into google, installed some apps). I did a soft reboot and the phone never wanted to boot back up. It flashed the Samsung logo and then just sat at a black screen. I flashed CM11 again just to make sure it didn't get corrupted the first time, but it still did not want to come up after a reboot. Then I thought maybe it's the ROM/ZIP so I flashed ParanoidAndroid 4.6-beta5. Same issue, it boots up fine after the flash, but will not start up after a reboot.
I'm on CWM Recovery 6.0.2.7, and I wipe/format the usual before the flash. Also on radio UVMC6. Any ideas?
I'm having the same problem, did you find a fix ?
Rushaan™ said:
I'm having the same problem, did you find a fix ?
Click to expand...
Click to collapse
same issue, different roms .
You. Guys are using an out of date recovery. Get the newest version of twrp and you should. Be fine.
CWM: http://www.teamchopsticks.org/p/cm110-release-notes.html
TWRP: http://forum.xda-developers.com/showthread.php?t=1768742
Hello everyone, recently I have started digging into the world of modding so I tried rooting, custom ROMs and custom kernels. Everything was working fine until yesterday, when I decided to move from lineage to pure nexus with elementalX kernel. I had some trouble with the installation and I had to re flash the same ROM several times because it soft bricked( At the end the problem was the radio and bootloader version ).But when I configured the ROM I saw that the autorotation on YouTube wasn't working, so I started searching for solutions on Google but with no luck. I swear I've tried ALL the possibile solutions (installing an app to see if the proximity sensor works, reflashing pure nexus and Resurrection Remix and lineage and stock Nougat and stock Marshmallow ROM, wiping data cache system ART/DALVIK internal storage, factory resetting from stock, editing the proximity firmware manually, disassembling the phone to check hardware error and so on ) but I can't get this sensor working, I can't even find the cause of this faulty sensor . I would really appreciate ANY kind of suggestions, thanks in advance
RichardCasales said:
Hello everyone, recently I have started digging into the world of modding so I tried rooting, custom ROMs and custom kernels. Everything was working fine until yesterday, when I decided to move from lineage to pure nexus with elementalX kernel. I had some trouble with the installation and I had to re flash the same ROM several times because it soft bricked( At the end the problem was the radio and bootloader version ).But when I configured the ROM I saw that the autorotation on YouTube wasn't working, so I started searching for solutions on Google but with no luck. I swear I've tried ALL the possibile solutions (installing an app to see if the proximity sensor works, reflashing pure nexus and Resurrection Remix and lineage and stock Nougat and stock Marshmallow ROM, wiping data cache system ART/DALVIK internal storage, factory resetting from stock, editing the proximity firmware manually, disassembling the phone to check hardware error and so on ) but I can't get this sensor working, I can't even find the cause of this faulty sensor . I would really appreciate ANY kind of suggestions, thanks in advance
Click to expand...
Click to collapse
Flash the vendor.img in TWRP or fastboot that matches the build name of the rom you are installing. This gets updated monthly so custom rom users need to flash this each month.
Sent from my Nexus 5X using Tapatalk
I think am already updated with the latest vendor for my current ROM (pure nexus with N2G47F vendor.img)
RichardCasales said:
I think am already updated with the latest vendor for my current ROM (pure nexus with N2G47F vendor.img)
Click to expand...
Click to collapse
Well, it looks like you'll have to wipe the entire device and reinstall the latest factory image.
Edit: Does autorotation work anywhere else?
Sent from my Nexus 5X using Tapatalk
Sadly auto rotation doesn't work anywhere, I've wiped all the phone ( system, internal storage, dalvik and cache) and installed the latest factory image but the problem doesn't seem to solve..
RichardCasales said:
Sadly auto rotation doesn't work anywhere, I've wiped all the phone ( system, internal storage, dalvik and cache) and installed the latest factory image but the problem doesn't seem to solve..
Click to expand...
Click to collapse
Interesting, no working autorotation anywhere. Which factory image are you using (include entire file name)? Could you screenshot the computer after you run the entire command for installing factory image?
Sent from my Nexus 5X using Tapatalk
The zip file name of the image was (image-bullhead-n2g47)
I installed the factory.img manually because I had trouble with the flash-all.bat file.
I don't think I can take a screenshot of the computer anymore because the PC wasn't mine and I can't have access anymore.
I take it you have tried sensor apps to see if it gives any values,
I have the same problem, warranty states it is due to water damage.
Does anyone know where the sensor is on the board?
Bmi160 gyroscope