Develop Bugs

twrp causes bootloop

Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).

Lip0ly said:
Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).
Click to expand...
Click to collapse
Just had an similar issue,
Try flashing first boot.img from the rom you will flash
then flash the recovery twrp big
then do the wipes ..
then flash boot.img and then rom
I thought this worked for me. (i flashed with the unboxed rom)

Just tried it, didn't work for me.

Bump

Unable to boot after unlocking bootloader and installing TWRP

Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?

chinhodado said:
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
Click to expand...
Click to collapse
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.

I actually solved this myself before k23m's reply by flashing the stock rom (MOB30X), then completed the initial setup, then reflashed TWRP (twrp-3.0.2-0-flo.img, not the multirom version). After that I booted up then restarted into recovery but then realized that TWRP had been wiped (only the android with the red triangle showing). So I re-flashed TWRP again and this time rebooted directly into recovery, and renamed the file recovery-from-boot.p into recovery-from-boot.backup. Then I flashed su and all went well.

k23m said:
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
Click to expand...
Click to collapse
Thank you for the hint!

Phone wont boot to recovery and installing stock fails

Device: Sony Xperia M dual (C2005/nicki)
Problem:
Tried to install CM 14.1 (official), flashing the boot.img worked, i got into cm recovery and tried to factory reset. It failed and i tried it one after another, it got stuck at wiping Cache (or i was impatient, sorry) and rebooted. Since then i cannot enter recovery because it says no command and reboots the recovery in a loop.
OK, then try to Flash it back to stock.
I tried to Flash the stock in flashmode but i got an error (this is from the log file)
Code:
flashsystem.X10FlashException: Error in processHeader : 1 : Unzulässige Funktion.
at flashsystem.X10flash.uploadImage(X10flash.java:329)
at flashsystem.X10flash.sendLoader(X10flash.java:361)
at flashsystem.X10flash.flashDevice(X10flash.java:754)
at gui.tools.FlashJob.run(FlashJob.java:44)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Can anyone help?
Its not my device and i have to give it back really soon

me too

Ok lol got it to flash stock. Just redownloaded the ftf file and updated flash tool.
After first fail it works.
Will report if I'm having success installing CM.

Ok I got to install CM but none of the SIM slots are working. This is a no.
Back to stock with 4.3 ftf and it worked.
Just use the newest builds and redownload if it fails more than 3 times.

Can't upgrade TWRP from 2.8.7 to 3.0.2

Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?

Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.

Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.

H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img

Strange issue with mi5s not booting flashed rom

Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.

goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer

crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp