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?
Related
I have clockworkmod recovery installed and rooted. It's been a few months since I rooted, and can't remember exactly what I did, but OTA updates stopped working. Hence, I am still on gingerbread.
Trying to flash a custom rom now, CM9. I tried the rom manager method several times, found out that wasn't recommended, and then tried the recovery method.
The same thing happens either way: it boots into CM9, but the boot animation keeps playing.
With the rom manager method, I tried wiping nothing, then tried wiping dalvik only, then tried... whatever the other option was, wipe cache and data?
With CMW recovery I downloaded CM9 zip and the appropriate GAPPS, moved onto the internal SD card, booted into recovery mode Wipe data/factory reset, then Wipe cache partition, then install both.
I'm able to restore from backup each time, but this is annoying.
Thank you
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
UZ7 said:
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
Click to expand...
Click to collapse
So "UCLF6" appears to be rom that is similar to stock, I'm guessing the idea here is that I'm resetting the phone but retaining root, the idea being that something on my phone is messed up and preventing CM9 from booting but doesn't prevent the current rom from booting?
Two other questions
1. Won't format/system wipe out all my backups in addition to my data?
2. Have you had or seen this problem before? I'm hesitant to commit myself to something, especially with no backups, if it's just a theoretical fix. I do appreciate it either way.
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I had a similar boot animation loop when I went from stock GB to stock ICS. What seemed to fix it was updating my CWM from 5.0.2.6 (non-touch) to 5.5.0.4 (touch). (BTW, I couldn't find an advantage of stock ICS over stock GB. I have since put on CM9 which I'm liking).
UZ7 said:
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Still got the boot loop.
When I did the "Wipe data/factory reset" I did get an error message during one of the processes"
"Error mounting sdcard/.android_secure!
Skipping format"
I had a boot loop problem when I first tried to flash JB. I went from GB to ICS with a custom rom a few months back, but I couldn't get any of the new JB roms to work. I ended up having to upgrade my CWM to the touch version in order to get JB flash to work. Also, a tip-- the boot animation will take a minute or two even when it is working. Don't assume it is still a problem if you see it more than once.
Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie
maybe yall need to "fastboot flash boot boot.img" now
robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.
Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!
Ok, i'm trying to install Cromi x JB 4.2.1 by flashing it from my SD card
I'm on bootloader 10.6.1.14.0
TWRP 2.6.1.0.
I flash the zip from the sd card like i've done many times with other ROMS. Everything looks fine. I go through the install steps for Cromi-x, everything appears to install correctly. I get a friendly message telling me that everything went great, to reboot my tablet, and to enjoy!
But TWRP tells me that no OS is installed. When I reboot, it goes to the ASUS splash screen and just sits.
What could I be doing wrong?
bbryantuf said:
Ok, i'm trying to install Cromi x JB 4.2.1 by flashing it from my SD card
I'm on bootloader 10.6.1.14.0
TWRP 2.6.1.0.
I flash the zip from the sd card like i've done many times with other ROMS. Everything looks fine. I go through the install steps for Cromi-x, everything appears to install correctly. I get a friendly message telling me that everything went great, to reboot my tablet, and to enjoy!
But TWRP tells me that no OS is installed. When I reboot, it goes to the ASUS splash screen and just sits.
What could I be doing wrong?
Click to expand...
Click to collapse
Did you mean 10.6.1.14.10? It happens to me once in a while with that issue... If you don't have anything to save and I guess that you don't. First, you could try to wipe your system, cache, and data from your twrp. Then go to mount button and manually mount your system, cache, and data then try to install your ROM again..:fingers-crossed: If it still doesn't mount your system, you have to go through the steps above with a complete shut down of your device and don't install anything if ask.. Then boot back into your twrp and manually mount all your partitions then install your ROM. Good luck...:fingers-crossed:
That usually happens when /system can't be mounted correctly or the installer didn't actually finish (even though it reported it did).
Try rebooting and wipe /system and flash again as said.
Here are the particulars.
rooted
Display JZO54K
Fingerprint = motorola/tervigon/wingray:4.1.2/JZO54K/.....
Loaded elementalx - xoom- v1.3 three months ago ran fine. Stupidly, I did not flash a backup. Now after deleting cache, factory reset, stuck in "loading apps" after splash, the boot loops back to motorola screen where I can launch CWM v4.0.0.4 - I want to get a ROM on there and continue using this mission-critical dinosaur. Can someone help?
I guess the real question is can a rom be copied onto the ext-sd card via windows out of the xoom? If so will CWM see it and will it work?
Have not tried connecting and using ADB. Not feeling confident enough at this point. ext SD still has data but when in CWM device does not show up in Windows.
TIA for any help
Geoff
sasquatchgeoff said:
Here are the particulars.
rooted
Display JZO54K
Fingerprint = motorola/tervigon/wingray:4.1.2/JZO54K/.....
Loaded elementalx - xoom- v1.3 three months ago ran fine. Stupidly, I did not flash a backup. Now after deleting cache, factory reset, stuck in "loading apps" after splash, the boot loops back to motorola screen where I can launch CWM v4.0.0.4 - I want to get a ROM on there and continue using this mission-critical dinosaur. Can someone help?
I guess the real question is can a rom be copied onto the ext-sd card via windows out of the xoom? If so will CWM see it and will it work?
Have not tried connecting and using ADB. Not feeling confident enough at this point. ext SD still has data but when in CWM device does not show up in Windows.
TIA for any help
Geoff
Click to expand...
Click to collapse
I pushed a stock rooted rom via ADB (I found the internal sdcard is accessible via the ADB shell) . The stock rom showed up in the CWM select zip file list. Installed the rom and the xoom animation freezes then continues the boot loop - regardless of rom installed. Cleaned system cache and davik cache as well after factory wipe. I am beginning to think hardware issues. No amount of cajoling will get this thing to boot into its OS. Either memory or processor - when it worked, I did have it running incredicontrol and 1.4 ghz and the max memory limitation upped to 64MB in order to run a lecture player for school.
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.