Database Info

[Q] Help, stuck in bootloop with CM 10 ROM

So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Note: I accidentally posted this in the Android Q&A section, so I apologize for the double post. I just think this is probably the best place to get my answer.

Did you flash the boot.img?

I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.

jon8105 said:
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
Click to expand...
Click to collapse
if they are backups from sense, that *MAY* cause problems, but don't quote me on that. I don't use sense, can't say for sure

OK, maybe that is why. Not a big deal since I haven't had the One X too long. Thanks for the help guys.

Good to know

[HUGE BUG] Partitions disappeared!

Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!

Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock

I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.

CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!

blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center

I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse

Experiences with rooted and encrypted S7

Since almost one week i am trying to a S7 rooted, debloated and encrypted.
Starting encryption with a decrypted phone from CFW:
After installing a CFW on an decrypted, i were not able with two different CFWs to get it encrypted. If you select the encryption by AndroidMeni the process starts and after a few minutes, it does a usual reboot without any changes. I tried this method, and this as well. Some xda users told me, that i have to use stock. I had no chance to get it encrypted afterwards with selection through Android/Security menu.
Start with encrypted stock rom:
So i gave up and descided to start with stock (oct release) and encrypted.
Flashing Stock with Odin, let it reboot and let it encrypt on first start, go through the assistent, reboot to download mode and root with odin and cf-auto-root.
Dont have to install TWRP, hence doesnt make any sense. You dont get acces to /data nor to /sdcard (internal storage).
After that i tried several debloating scripts, some worked, some not. So i decided to debloat manually with SSHdroid & putty.
Then i recognized, that the apps were not removed, although the files were been deleted?!
I did a factory reset, now the phone was clean. But the encryption was gone
btw: my experiences with FlashFire were also negative. Somehow it doenst let FlashFire mount any partitions on restart. It just doenst work.
Do anyone have an idea, how can I use this damn S7 rooted, debloated and encrypted? I can live with stock too.
I lost my interest - just tired, wasted so many days. Just want to make my data on my phone safe against a thieve.
Thanks

Stuck in a bootloop + CWM question

Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.

oneplus6 seems damaged following a failed twrp restore

So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.

Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)

I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.

Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.

So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.

I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.

I already stated thats already been done.
I eventually got msm working. and that luckily worked.

@chrcol ..., but you've issues

chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.