Develop Bugs

[Q] HELP. HTC One X Stuck in bootloop. Almost all famous solutions tried out

So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?

anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there

dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing

anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha

anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks

Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.

Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help

Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.

No Custom ROM? Help!

My Xperia ZL won't allow me to install a custom ROM.
Here are the steps I've taken.
1. Updated to 10.6.... (Lollipop fw) via Flashtool
2. Boots correctly, everything seems to work.
3. Flashed boot.img from Paranoid Android and went into TWRP to flash the ROM zip (wiped cache, system and data before).
Did step 3 to test the same for OmniRom too.
4. Phone boots, shows Bootanimation, shows Optimizing apps, then hangs after finish and does step 4 again.
Please help me, I could install custom ROMs on the device before, suddenly it does not work anymore.
Note: EVERYTHING works fine with Stock. Flashed stock ftf multiple times and tried these steps.
Thanks for your help

It seems to be a Bootloop. Try below steps;
1. Through TWRP wipe (system+cache+dalvic cache+data+android secure)
2. Install ROM.zip
3. Wipe cache+dalvic cache+data
4. Reboot
Hope the above steps helps you
Regards,
hitman-xda

@hitman-xda I've tried these steps, except for android secure.
What is that partition and what does it do?
Cannot find it in Advanced Wipe of TWRP.
Thanks

It is the mysterious part. Actually no one knows about it. Some says, it contains secured links/data of some apps.
If you are clean flashing ROM, that's means you have to wipe everything except storage part. That's the reason I mentioned it.
If you can't find it, just leave it

@hitman-xda So I've already done what you suggested, with no luck.
Guess I'm stuck on stock till someone helps me
Thanks for your reply

did you install de correct kernel?
maybe you should wipe everything, install the correct kernel and after that, install the custom ROM
i don't now if it will work, but at least try

I did fastboot flash boot boot.img (got it from ROM zip)
Then erased everything and flashed ROM.
No luck

Does that Paranoid Android was built for your phone?
Your phone loops from 'optimizing apps' , that means your phone is unable to load dalvic/art for the apps.
Also check weather PA ROM can be flashed over lollipop, if not then you have to downgrade an then try the same procedure.
Also you can download stock kernel with recovery, flash it and then directly try to flash your respective ROM.
Usually ROM.zip contains kernel and get flashed during installation of zip, just the thing is they can be flashable over some selective android versions.

CM13 not booting

After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.

Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.

RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.

Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.

RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.

I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((

ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))

1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.

yes it stock rom, after it was installed, I was able to install 13 cm

How to revery back to stock rom?

Now I am on custom rom, what to do to flash stock rom? just flash zip file in TWRP? or should I flash stock TWRP or what?

You got some options:
But first a heads-up: you will lose all your data.
Zip-flash method:
Copy the stock rom flashable zip to your micro sd. Make sure you got the flashable zip! To be flashed in twrp.!
Boot to twrp.
Factory reset
Then wipe system partition
Now flash the zip.
Wipe dalvik and cache.
Reboot
Enjoy
Fastboot method: (will surely wipe everything)
Search for team one rescue firmware on our XDA.
Download the firmware package.
Boot your phone into bootloader.
Connect your phone to your PC.
Make sure you got your backup to your PC. Or micro SD.
Extract the firmware package and start
Flash-all stock recovery.bat
Or a name similar.
Wait until the phone reboots in its own, and DO NOT , disconnect the phone while in process of flashing.
Once the the Google setup is visible, you can safely disconnect your phone.
You should be back on marshmallow stock rom.
Do some ota updates. Enjoy,

sm00th4f3 said:
You got some options:
But first a heads-up: you will lose all your data.
Zip-flash method:
Copy the stock rom flashable zip to your micro sd. Make sure you got the flashable zip! To be flashed in twrp.!
Boot to twrp.
Factory reset
Then wipe system partition
Now flash the zip.
Wipe dalvik and cache.
Reboot
Enjoy
Fastboot method: (will surely wipe everything)
Search for team one rescue firmware on our XDA.
Download the firmware package.
Boot your phone into bootloader.
Connect your phone to your PC.
Make sure you got your backup to your PC. Or micro SD.
Extract the firmware package and start
Flash-all stock recovery.bat
Or a name similar.
Wait until the phone reboots in its own, and DO NOT , disconnect the phone while in process of flashing.
Once the the Google setup is visible, you can safely disconnect your phone.
You should be back on marshmallow stock rom.
Do some ota updates. Enjoy,
Click to expand...
Click to collapse
Now I have custom TWRP and a custom rom, I will choose Zip-flash method.
Can I flash stock rom with this custom TWRP? I mean can I flash stock rom like custom ones via twrp?
Can I flash custom rom later after installing stock rom?

Egyptiandroid said:
Now I have custom TWRP and a custom rom, I will choose Zip-flash method.
Can I flash stock rom with this custom TWRP? I mean can I flash stock rom like custom ones via twrp?
Can I flash custom rom later after installing stock rom?
Click to expand...
Click to collapse
For starters, twrp is a custom recovery, so you don't have to put the word "custom" before twrp everytime you mention it. X)
There are flashable zips that contain the stock rom. So, in a sense, yes, but you can't do any ota updates.
Download any needed file before beginning to flash a new rom:
Custom Rom, Gapps and if you want root: Magisk or SuperSu. Put those files on your micro SD in your phone.
Create a backup in twrp. You Just have to slide from left to right, no need to select anything more than what is already selected from the start.
Before installing a custom rom, you have to always wipe system, data, dalvik and cache partition in twrp recovery.
Only then you can flash the stock rom, which can be downloaded in one of the threads here in our XDA Lenovo p2 forum.
Little need to know: before flashing any rom, do a factory reset in twrp and wipe system partition.
Be aware that by deleting the four partitions you will lose your app data, sms,call log and so on.
Internal storage however isn't affected, so your music und Pictures won't be deleted.

sm00th4f3 said:
For starters, twrp is a custom recovery, so you don't have to put the word "custom" before twrp everytime you mention it. X)
There are flashable zips that contain the stock rom. So, in a sense, yes, but you can't do any ota updates.
Download any needed file before beginning to flash a new rom:
Custom Rom, Gapps and if you want root: Magisk or SuperSu. Put those files on your micro SD in your phone.
Create a backup in twrp. You Just have to slide from left to right, no need to select anything more than what is already selected from the start.
Before installing a custom rom, you have to always wipe system, data, dalvik and cache partition in twrp recovery.
Only then you can flash the stock rom, which can be downloaded in one of the threads here in our XDA Lenovo p2 forum.
Little need to know: before flashing any rom, do a factory reset in twrp and wipe system partition.
Be aware that by deleting the four partitions you will lose your app data, sms,call log and so on.
Internal storage however isn't affected, so your music und Pictures won't be deleted.
Click to expand...
Click to collapse
Thanks for your detailed answer I am now on custom rom, i will download stock rom from the sticky thread, although all links are dead but I will try to find a working link
BTW, what is the latest stock rom?

I think S251 ...i'm not sure though. It shiuld be the one with the highest number=latest version ?
I still think that custom roms are better than stock though but do what you think is right.

Phone won't boot to OS after installing magisk. My experience

So i rooted my phone sometimes ago, and it worked fine at first but after some reboots it is now stuck at Redmi logo and would boot to fastboot mode after a while. Now i want to share my experience so people can be more careful, i may be a newbie but i do want to help people too.
So here's what my phone is using, CorvusOS 7.0 and SiLonT kernel and no more modifications other than that. Now i have read stuff online that some people have experienced bootloops and some can't boot to the OS they rooted their device with magisk. I have also read that dirty flash may solve the problem. But if you're already facing this problem maybe you can try these methods below:
Method 1: probably the easiest one, wipe the Dalvik and the cache
1. Reboot to your custom recovery
2. Go to advanced wipe (location and UI may differs between custom recoveries)
3. Simply tick Dalvik and cache and untick anything else
4. Reboot
Method 2: uninstalling magisk (this will unroot your device)
1. Download magisk uninstaller.zip (if you didn't downloaded it already from the start. Also make sure the uninstaller is the same version as your magisk version, idk what will happen if you do it with a different version but just in case )
2. Reboot to your custom recovery
3. And simply just flash/install the magisk uninstaller.zip, this will delete all magisk's files
4. Wipe Dalvik and cache (just in case)
5. Reboot
Method 3: dirty flash (for custom ROMs)
1. Uninstall magisk (follow method 2)
2. Get/download your custom ROM you are using (make sure it's the same ROM and version as the ROM you're using rn)
3. Flash it without wiping anything
4. Wipe Dalvik and cache (just in case, again)
5. Reboot
Method 4: reinstall/install your ROM, for custom ROMs users (I'm sorry i am not experienced with XiaomiFlashTool so i can't tell you how to flash stock ROM)
1. Backup all data cause this will erase all your data
2. Reboot to recovery
3. Uninstall magisk (follow method 2)
4. Wipe system, data, cache, Dalvik (the usual stuff you would wipe before installing a custom a ROM)
5. Install your chosen ROM
6. Wipe Dalvik and cache (just in case)
7. Reboot
If those methods above doesn't work you can try searching a tutorial on flashing the stock ROM on the internet, but if you still didn't manage to get your phone boot to the OS again then i am sorry to say that you have to take your phone to the nearest repair center.
So, what's the cause of this problem?
Well, it's simple, every human make mistakes, At least once. So it is normal to make mistakes. The developers are humans too so it is normal for them to make mistakes too, so instead blaming them we should support them and give them advice. But on the other side you may did a mistake too, probably a similar mistake that i did. Like maybe you did something wrong according to the tutorial, or you flashed an incompatible version of magisk, and etc. So from now on always ask if it's compatible, whether it's about magisk versions, ROM compatibility, kernel compatibility, recovery compatibility, and etc. And always double check just in case.
If i did something wrong tell me down below and I'll fix it as soon as possible.
Peace.
One quick little note: i fixed my device by doing a dirty flash (method 3) just to let you know
Edit: Phone won't boot after uninstalling magisk*, that was supposed to be title. Sorry I just realized sometimes ago

This happens to me all the time when flashing Android 11 ROMS. Curiously this doesn't happen when flashing Android 10 ROMs. I also never had this issue with TWRP, only OrangeFox.
But it could be other things too. For example, Xiaomi.eu 12.5 always go into a bootloop here, and trying to go back to any other ROM after flashing it leads to a boot loop. The fix is to flash disabled vbmeta if you're flashing xiaomi.eu 12.5. That might be the fix for A11 roms too but I never tried.
More than once it happened to me too that no matter what I did the phone would be stuck in bootloops with any ROM, any recovery. In that case, flashing stock rom via fastboot fixed the issue.