Database Info

[Q] Help needed - stuck on CM10 boot-up animation

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!

[Q] How to wipe cache Partition

I try to wipe the cache partition on my Galaxy Tab 7.0 P3100 by booting up by pressing volume button up and power button and chose wipe cache partition and when it start erasing after 5 second it's sowing error and boot to system without wiping the cache.
I'm using JB 4.2.2 with no root.
Any way to wipe the cache?

godsmack_dmx said:
I try to wipe the cache partition on my Galaxy Tab 7.0 P3100 by booting up by pressing volume button up and power button and chose wipe cache partition and when it start erasing after 5 second it's sowing error and boot to system without wiping the cache.
I'm using JB 4.2.2 with no root.
Any way to wipe the cache?
Click to expand...
Click to collapse
The may be a write problem with the cache. Does the tab works fine in normal usage?
Alternatively, you could root it and flash CM Recovery, and then try wiping cache. If it works good, otherwise its a failing hardware.

用odin3重新刷一遍recovery，一切难题迎刃而解。和楼上解法差不多。先root再用固件管家刷第三方clockworkmod。
(英语不好没法输英文抱歉。(

I had the same issue after the 4.2.2 update. I was going to wipe it because the Tab was real laggy. I got the same error. Mine is a gt-p3113.
Sent from my GT-P3113 using XDA Premium 4 mobile app

I don't think it's a hardware problem. Try installing a custom recovery and then wiping cache. A good process should be like this:
1. Root device
2. Install Custom Recovery (CWM or PHILZZ)
3. try to wipe cache
Once you have rooted and have installed custom recovery, you may also like to try out new roms.
I would suggest not rooting if you have warranty left. If you have, best option is to send it in warranty and ask them to try wiping cache.

obmahmood said:
I don't think it's a hardware problem. Try installing a custom recovery and then wiping cache. A good process should be like this:
1. Root device
2. Install Custom Recovery (CWM or PHILZZ)
3. try to wipe cache
Once you have rooted and have installed custom recovery, you may also like to try out new roms.
I would suggest not rooting if you have warranty left. If you have, best option is to send it in warranty and ask them to try wiping cache.
Click to expand...
Click to collapse
My tab still in warranty but I'm willing to trying every solution cause warranty will simply will reset factory sittings and they will say it's fixed and come to get it. But in the same time I don't want to lose the warranty.

godsmack_dmx said:
My tab still in warranty but I'm willing to trying every solution cause warranty will simply will reset factory sittings and they will say it's fixed and come to get it. But in the same time I don't want to lose the warranty.[/COLOR][/SIZE]
Click to expand...
Click to collapse
Yeah, that's basically what I am thinking. I only have until February when my warranty runs out, then I may do the root and mod deal.
Sent from my GT-P3113 using Tapatalk

I did a downgrade to JB 4.1.2 but the tab stuck at samsung animation boot screen but I did manged to enter recovery mode and do a wipe cache partition and restart to know if it gone boot but it did stuck at samsung animation screen than I used odin to but it back to 4.2.2 and it worked fine with no restart for the first 24 hour but it did restart once while I'm using it in the half of the second day and two while I'm recharging it at the end of second day.
And here we are at the third day with no restart for about 15 hour since the last restart.
I hope it's the end for this problem.

[Q] can't flash custom rom with TWRP after my brother do the factory reset

i used slim lollipop on my device , suddenly my brother do factory reset via twrp
after that , it makes random reboot
reboot to desktop and reboot again in a few second
i try wipe everything like system, data, cache , dalvik and internal
but that can't erase them
my data and internal still there
i try to flash new rom but it still slim lollipop with random reboot
any solution? please help
thanks

[Q] Stuck on boot loop and cannot flash other ROM

Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance

Try to delete everything in data manually through twrp file manager (Advanced->File Manager)

john99ap said:
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
Click to expand...
Click to collapse
Im using CWM recovery T.T

iqbaladeee said:
Im using CWM recovery T.T
Click to expand...
Click to collapse
Then, install the latest common twrp by Andi from here: http://andi34.github.io/recoveries_tab2.html
and try it (first try also to wipe data with twrp)

iqbaladeee said:
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Click to expand...
Click to collapse
I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get “read only”, so you can’t perform any write actions (also you can’t format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a rebootFormating the storage doesn’t work (after reboot the old rom and apps are back)You can flash whatever you like via Odin - it showes “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.
source: http://andi34.github.io/faq.html

Galaxy S7 930f can't access twrp

Hello, thanks for your help.
It seems I bricked my galaxy s7 while trying to format the /data partition.
I installed TWRP 3.2 and a custom rom, and everything went smoothly until then.
I tried installing an audio mod which throwed a " can't mount /data" error, searching for solutions I read that formatting the data partition to fat and back to ext4 should solve the problem, I tried formatting it to fat with TWRP, however on the first try I got a message that it suceeded, followed by a message that /data could not be mounted, TWRP seemed to be still working (there was no reboot button or any other buttons, just a "working" bar). After giving the phone 3 hours I decided to restart it, now I can't access TWRP; it stays on it's "splashcreen", and of course the phone won't boot.
I'm having a rough time with this so I will appreciate it a lot if you can help me.
Thank you.

Boot to download mode, flash stock firmware using Odin, then retry the TWRP installation.
For wiping data, you have to make sure you use the wipe option that makes you type out 'yes' to wipe, the other factory wipe methods don't actually properly wipe the partition.
iirc you also then need to flash the dm no verity zip from the TWRP thread.

Bro you didn't have to do anything but just formating the phone in the first place. Aassuming you're on oreo , it happens to a lot of people and myself, after flashing a kernel twrp was unable to munt data, all i had to do is a data format in twrp that fixed the problem .