Database Info

Cromi 5.1.2 - stuck on logo team

Hello all,
I've installed cromi-x 5.1.2 one month ago, without any problems. But today, after a night in charge (tablet off), I can't boot on cromi-x, I'm blocked on cromi-x logo with waiting cursor which turns, turns, turns
I can access to twrp only but I never do a backup. Numerous reboots done without effects.
Any help will be heplfull :good:
Thx for your help

tanis73 said:
Hello all,
I've installed cromi-x 5.1.2 one month ago, without any problems. But today, after a night in charge (tablet off), I can't boot on cromi-x, I'm blocked on cromi-x logo with waiting cursor which turns, turns, turns
I can access to twrp only but I never do a backup. Numerous reboots done without effects.
Any help will be heplfull :good:
Thx for your help
Click to expand...
Click to collapse
I believe that you have a bootloop... Can you tell us what is your bootloader version or firmware version? What is your TWRP version also? You may need to wipe your system to get it up and running again...

Thx LetMeKnow,
I'm using twrp 2.6.1.0. Bootloader number is 10.6.1.14.10-20130601.
When you tell about a wipe, full wipe with full install of the rom again? I will have to do a backup, data only is enough for apps installed?
thx

tanis73 said:
Thx LetMeKnow,
I'm using twrp 2.6.1.0. Bootloader number is 10.6.1.14.10-20130601.
When you tell about a wipe, full wipe with full install of the rom again? I will have to do a backup, data only is enough for apps installed?
thx
Click to expand...
Click to collapse
Your TWRP and firmware are good... I think that your data partition is corrupted and these are my suggestions..
1. In your TWRP, go to Advance and file manager, copy all your personal stuff to your external SD so you will not loose them when you format your data partition.
2. In your TWRP, do a nandroid backup of system, data, and boot
3. Try this first, Wipe everything except your system and your external SD and reboot...:fingers-crossed: If your device is up and running then it is telling you that you have a data partition corruption.. So your data backup from TWRP is useless..
4. If step 3 did not work, then your system is corrupted..You may want to do these.
--Format your data partition
--Wipe everything except your external SD
--Reinstall Cromi x and reboot so you a totally clean installion...
--Now you can restore your data backup and hope that it is not corrupted
--Good luck ....:fingers-crossed:

LetMeKnow said:
Your TWRP and firmware are good... I think that your data partition is corrupted and these are my suggestions..
1. In your TWRP, go to Advance and file manager, copy all your personal stuff to your external SD so you will not loose them when you format your data partition.
2. In your TWRP, do a nandroid backup of system, data, and boot
3. Try this first, Wipe everything except your system and your external SD and reboot...:fingers-crossed: If your device is up and running then it is telling you that you have a data partition corruption.. So your data backup from TWRP is useless..
4. If step 3 did not work, then your system is corrupted..You may want to do these.
--Format your data partition
--Wipe everything except your external SD
--Reinstall Cromi x and reboot so you a totally clean installion...
--Now you can restore your data backup and hope that it is not corrupted
--Good luck ....:fingers-crossed:
Click to expand...
Click to collapse
It's not a bootloop if he's stuck on the boot animation. If it keeps booting back - then yes, but getting stuck on the boot animation has happened to me numerous times (and always when I was on a Hund's kernel - sorry LMK, but Hund's just doesn't work on my tab), which a simple Factory Reset (the default option in the TWRP "Wipe" menu) took care of.
If that doesn't work, then yes - you will have to format data.

berndblb said:
It's not a bootloop if he's stuck on the boot animation. If it keeps booting back - then yes, but getting stuck on the boot animation has happened to me numerous times (and always when I was on a Hund's kernel - sorry LMK, but Hund's just doesn't work on my tab), which a simple Factory Reset (the default option in the TWRP "Wipe" menu) took care of.
If that doesn't work, then yes - you will have to format data.
Click to expand...
Click to collapse
The only way to diagnose the cause of "stuck at boot animation" (i.e. to gain insight instead of trying random things involving data loss) is to read the logcat.

Hello guys
Thx for all these infos. Finallly, it was the data...
Just before your answers, I've tried a wipe of cache and dalwik cache. Android's apps updated, and stuck again on logo animation.
So I've tried to update to 5.2a, with no format of data, the same arrived.
I've reinstalled the 5.2a with full wipe, and now it's ok (I will have to do it again, some options unselected are finally necessary. I will go back on 5.1.2 one if no update of 5.2a in the week.)
How can the data be corrupted? I remember, I've had installed an apk from googleplay, this apk can be faulty?
Thx

I seem to be having the same issue with the same version of CROMI and TWRP 2.4.4.0 so I wiped the tablet and put the ROM on a microsd to reflash. For some reason, I'm not seeing the zip file in the file manager or the install option. Please help.

tkdftw said:
I seem to be having the same issue with the same version of CROMI and TWRP 2.4.4.0 so I wiped the tablet and put the ROM on a microsd to reflash. For some reason, I'm not seeing the zip file in the file manager or the install option. Please help.
Click to expand...
Click to collapse
Try with a microsd formated in fat32, this should help.

TF700 with Chrimi-x 5.2a
Hi Guys,
First post. I installed Chromi x 5.2a to my TF700 and it was working great.
I was looking at the options and it said I was using the 4.1 JB theme but I could switch to 4.2 Theme of JB. I did, and when my tablet restarted, I get a black screen and a bunch of errors once in a while.
Is there a way I can change it back to 4.1? I can't access the OS only TWRP.
Thanks!

ColomboD said:
Hi Guys,
First post. I installed Chromi x 5.2a to my TF700 and it was working great.
I was looking at the options and it said I was using the 4.1 JB theme but I could switch to 4.2 Theme of JB. I did, and when my tablet restarted, I get a black screen and a bunch of errors once in a while.
Is there a way I can change it back to 4.1? I can't access the OS only TWRP.
Thanks!
Click to expand...
Click to collapse
Weird. I would re-flash the rom. It installs to the 4.1 launcher by default - but something is off... That shouldn't have happened.
Did you clean install CROMi-X?

[Q] TWRP cannot read my sdcard (encrypted?)

So, my previous post was a bit too optimistic. I've managed to get TWRP onto my phone, but when I went to actually load a custom ROM into it, I found that it couldn't read anything from my sdcard.
I'm having what appears to be a common problem: when I boot into Recovery, TWRP asks for a password. When I cannot provide it (because I have no idea what it is), TWRP is unable to access the data partition. Apparently, the partition is encrypted and I have no way to de-crypt it.
I've found dozens of other posts by users having this problem and the solution everyone is giving is to fully wipe the data partition and start over. But I *can't* wipe the data partition, because TWRP can't access it and fails almost immediately. I have tried a multitude of options, including:
* Installing old versions of TWRP - same behavior; asks for a password, fails to wipe/format the data partition.
* Installing ClockWork's recovery - same thing; fails to format/wipe the data partition
* Flashing back to stock recovery, using that to format my data partition; this worked fine but as soon as I put TWRP back, the problem came back.
On my last attempt, I used the stock recovery to completely wipe the data partition, and made absolutely sure that it never booted into anything but Download or Recovery modes after that. I was hoping that would prevent the stock software from ever re-encrypting the data, but somehow, when I booted TWRP, it still can't read my partitions. Note that my phone itself is not "encrypted" as far as the Settings application is concerned, but apparently Android is doing something behind the scenes anyway. There doesn't seem to be any option in the stock settings to turn off this encryption.
Is there any hope for getting a custom ROM onto this phone?
Thanks for the help!

Any solution? I'm running into the same issue where TWRP is asking for a password.

[Q] Boot loop problem after restore to stock 2.3.5 backup from custom ROM 4.3.1

Hi,
First time posting Reasonably Nooby...-ish to hacking around with android but pretty techy in general and have done a lot of reading to try and fix this myself before posting.
Setup: HTC Desire S, ClockworkMod ver 5.8.1.5, HBOOT 2.00.0002 S-ON Unlocked bootloader
I have been running the stock firmware Gingerbread 2.3.5 from new (rooted by me) running CWM Recovery ver 5.8.1.5. I took out my SD card and put a blank one in (possibly stupidly, didn't re-format first), I took a nandroid backup of the phone. Rebooted then changed a few phone settings/apps and restored the backup to test it was okay, and it worked fine.
I then flashed a custom rom (Carbon_4.3.1_1114_saga.zip) and (gapps-jb-20130813-signed.zip) from the same sd card, cleared all cache, dalvik, data etc which boots and works fine except that I have major issues with the sound in that it doesnt ring, no notification sounds and terrible in call audio, so have restored my backup through CWM.
As soon as I restored my backup and reboot, the phone goes into a boot loop where by it tries to boot showing the white HTC screen, the screen then goes black it then boots into ClockworkMod Restore. I tried clearing all data, cache, dalvik cache but it made no difference. I have tried a number of things including;
I then tried flashing boot.img to the phone from my nandroid backup in fastboot but again that made no difference.
I read through and followed the boot loop post on here but that made no differnce either.
I tried copying all data off sd card, formatting (through windows) and copying data back, no difference (more of a desperation attempt).
I can flash the custom ROM back to the phone and it boots again into that rom fine
One thing to note which may or may not have anything to do with this at all, is that when I originally wiped the dalvik cache before installing the custom ROM: from my memory, it did so with no errors. Now as soon as I select wipe Dalvik cache in CWM before even confirming to wipe, I get an error: "E:unknown volume for path [/sd-ext]", however when I do a "wipe data/factory reset" in CWM it shows it wipes /sd-ext. (this part is something I have not much knowledge on).
I cant help thinking theres something I've missed or can do that will get this to suddenly boot. Any help would be really appreciated as I've put a lot of hours/late nights into this so far and would now really like a fully working phone back.
As a side note; I believe from reading, putting a stock RUU update back on will solve the problem but after devoting a lot of hours trying to find one for my phone, I've not had much luck as nothing on HTCdev any more and cant find one for UK on Orange (now EE). And a lot of old links are now dead. As a side question does it have to be the firmware that my carrier sent out exactly for my country, I've read you can extract the rom.zip file from the RUU.exe so could I flash one that is world wide or a uk from another network provider or my network provider from another country, and then restore my backup to my own one, would that actually work/make any difference or just fail?
Thanks for any help

[Q] flashing from cm11 to 12 nightly then PA bootloop help needed

ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo

kanjo said:
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
Click to expand...
Click to collapse
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
EDIT: Exactly which thread are you getting these instructions from? Neither of the PA threads that I'm aware of contain those instructions.

Heisenberg said:
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
Click to expand...
Click to collapse
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.

kanjo said:
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
Click to expand...
Click to collapse
Just to be clear, you've wiped system, data, cache, and dalvik cache directly before flashing PA? No CM flashes since wiping all of those partitions?
Also, which thread are you getting those install instructions from? Neither of the PA threads that I'm aware of contain those instructions.

ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
going to go back to twrp. wipe all data and flash PA again without gapps and without root. will report back in about 10 minutes. will flash by using TWRP and ADB sideload.
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom) at the moment i am trying to sideload PA rom after wiping data, system, cache and dalvik. is this why i am having the issue?
im dead tired so i admit i can be making mistakes though everything i have done seems to be what i am meant to do. flashed from cm11 to cm12, cleared all data, then flashed PA+gapps and root. = upgrading boot loop and errors mentioned above. tried flashing just PA and it booted with same errors, flashed gapps and errors.
all the files MD5s look good. not sure what is wrong.
--edit--
okay now i am at homescreen on PA.
when enabling/disabling adb in dev settings i get a reboot. is this normal now? does it need to reboot to mount the filesystem or something?
when it does boot after enabling adb i get "settings has stopped"
going to go to TWRP and flash GAPPS now and leave root not installed. will report back in a sec.

kanjo said:
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
Click to expand...
Click to collapse
Please define wiped all data.
kanjo said:
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom)?
Click to expand...
Click to collapse
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.

Heisenberg said:
Please define wiped all data.
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Click to expand...
Click to collapse
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.

kanjo said:
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
Click to expand...
Click to collapse
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.

Heisenberg said:
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Click to expand...
Click to collapse
balls, was hoping to us PA, haven't used it since my old s3 and figured it was the rom for me again. will have to check the rom comparison spreadsheet and look into others.
right now i have sideloaded PA alone. will copy PA and gapps to the internal storage to make things easier.
but it doesnt look like it is going to work for me.
going to try it once more like you said but locally rather than through sideload. though the internal storage is deciding when it does and doesnt want to show up.
TWRP
wipe system, cache, dalvik cache, and data.
and flash them both in tandem.
and for the fun of it when it asks if i want to install root i will let it go right ahead.
maybe this time it will work. if not then its a different rom for me. sadly.

okay so now **** got retarded. TWRP has been replaced by the stock cm11 recovery and i am too pissed off to think straight and cannot remember how to get this son of a ***** rooted again let alone to flash TWRP. i dont want to use any toolkits they all seem broken as hell.
can anyone point me in the right direction because ive just about lost my **** and this phone is going to meet my fist head on very shortly...
**edit**
done. after all this i am now on cm11 stock rooted ....seriously. hours upon hours, just to get back to where i started.
man i love when things go smoothly. anyway cheers for your help @Heisenberg . n

[SOLVED] Google Apps Not Working And Recovery Refusing To Open

About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat

Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.

acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.

NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.