Develop Bugs

[Q] Performed factory reset, now won't boot

I'm selling my HTC One (stock ROM, unlocked) so I wanted to wipe my data, apps and settings. I performed a factory reset/data wipe in CWM and rebooted and it would get stuck at the Verizon logo. I cleared cache, tried again, and got stuck at "Android is updating, Starting apps" for a good 20 minutes. Now it goes back to the Verizon logo.
Does the factory reset not leave the ROM intact? What can I do now just so it'll boot to a clean slate?

kram12085 said:
I'm selling my HTC One (stock ROM, unlocked) so I wanted to wipe my data, apps and settings. I performed a factory reset/data wipe in CWM and rebooted and it would get stuck at the Verizon logo. I cleared cache, tried again, and got stuck at "Android is updating, Starting apps" for a good 20 minutes. Now it goes back to the Verizon logo.
Does the factory reset not leave the ROM intact? What can I do now just so it'll boot to a clean slate?
Click to expand...
Click to collapse
Download the stock rooted odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
After you flash it, wipe data and boot up.
Then flash the latest firmware and stock recovery through Fastboot (also that thread), and do another factory wipe using stock recovery.
Your S-Off / Unlocked status will not be affected by this.

NotATreoFan said:
Download the stock rooted odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
After you flash it, wipe data and boot up.
Then flash the latest firmware and stock recovery through Fastboot (also that thread), and do another factory wipe using stock recovery.
Your S-Off / Unlocked status will not be affected by this.
Click to expand...
Click to collapse
Thanks for your help. Unfortunately, I've been at it for a good 5 hours now and I can't get past the first step.
Using TWRP, I've tried adb push <rom.zip> to /sdcard/, /mnt/sdcard/ and /data/media/ and every time it says it's successful, but the directories show up empty in TWRP. Without a removable SD card, I'm not sure how else I can get the ROM on the phone for flashing. I'm not sure if it's related or not, but everytime I reboot from TWRP, it says my phone isn't rooted. I select "Install" but it occurs again, even though supersu.apk is on the internal storage.
I also tried CWM but couldn't get past "format () expected 5 args, got 4. Installation aborted (Status 7)".
Does anyone have any suggestions on how I can get TWRP to flash the ROM? Thanks.

Try this cmd instead.
Code:
adb push nameofrom.zip /data/media/0/nameofrom.zip

kram12085 said:
Thanks for your help. Unfortunately, I've been at it for a good 5 hours now and I can't get past the first step.
Using TWRP, I've tried adb push <rom.zip> to /sdcard/, /mnt/sdcard/ and /data/media/ and every time it says it's successful, but the directories show up empty in TWRP. Without a removable SD card, I'm not sure how else I can get the ROM on the phone for flashing. I'm not sure if it's related or not, but everytime I reboot from TWRP, it says my phone isn't rooted. I select "Install" but it occurs again, even though supersu.apk is on the internal storage.
I also tried CWM but couldn't get past "format () expected 5 args, got 4. Installation aborted (Status 7)".
Does anyone have any suggestions on how I can get TWRP to flash the ROM? Thanks.
Click to expand...
Click to collapse
I recently returned my phone to stock in order to reset all the firmware and RIL data. Here is how I did it:
Enter recovery TWRP 2.6.3.4 (if you have 2.6.3.3 you may experience issues)
Boot into recovery, then format Data, System, Cache, and Internal Storage (this will leave the phone with NO ROM installed)
Reboot back into recovery. Answer No to the prompt to root your device.
Once back in recovery, Internal Memory will be available again (if you push the ROM before rebooting, it will not be there afterward)
Push the ROM using adb push ROM.zip /sdcard/ROM.zip (this will take 5-7 minutes for a 1.4GB file)
Flash the ROM in TWRP
Reboot when done, phone should boot up corrrectly
Reboot into Fastboot, push firmware.zip package
Reboot into ROM verify connectivity
Reboot into Fastboot, push stock recovery
Reboot into stock recovery, perform a Factory Reset
Boot into ROM
Once you are up and running on the latest 4.4.2 ROM with stock recovery, boot into Fastboot one last time and push TWRP 2.6.3.4. Your S-Off will not be affected and the new owner will be able to flash any ROMs they like.
If all of the above fails, then try using ADB Sideload from the Advanced menu in TWRP.

You guys are a life saver. TWRP 2.6.3.4 did the trick, it just wasn't available on the TWRP site so I didn't install it in the first place. Flashed the ROM and everything back to normal! Thanks for the help!
FWIW, none of the m7 versions of TWRP would load (stuck at "Entering Bootloader" screen). The Sprint version would load, but wouldn't mount the filesystem properly.

kram12085 said:
You guys are a life saver. TWRP 2.6.3.4 did the trick, it just wasn't available on the TWRP site so I didn't install it in the first place. Flashed the ROM and everything back to normal! Thanks for the help!
FWIW, none of the m7 versions of TWRP would load (stuck at "Entering Bootloader" screen). The Sprint version would load, but wouldn't mount the filesystem properly.
Click to expand...
Click to collapse
So what state is the phone in now? Stock w/ HTC recovery, or the Sprint TWRP?

NotATreoFan said:
So what state is the phone in now? Stock w/ HTC recovery, or the Sprint TWRP?
Click to expand...
Click to collapse
The former, stock. The Sprint TWRP loaded but didn't work right. I ended up finding 2.6.3.4 for VZW m7 on an xda thread, it's not on the TWRP site for some reason. That worked great.

kram12085 said:
The former, stock. The Sprint TWRP loaded but didn't work right. I ended up finding 2.6.3.4 for VZW m7 on an xda thread, it's not on the TWRP site for some reason. That worked great.
Click to expand...
Click to collapse
Excellent. Glad to see it all worked out.

[Q] Bootloop on recovery

Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!

offti1 said:
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
Click to expand...
Click to collapse
Flash the PIT file together with a 4.1.2 stock firmware downloaded from SamMobile. Root and do whatever you want after.

My mix is CyanogenmodX (by UtkarshGupta)+f2fs+agni. It's kinda weird and I did not found someone else with this problem except this topic. I did a lot of reflashing to nail it down to the following:
I'm stuck with a twrp loop (twrp logo appears and then reboots) when using f2fs (/data only) and the system is installed. This problem is now for some months, before it worked fine with the same setup. Also complete wipes of all partitions and even repartition did not help.
-It works as long as there is no OS present or not booted for the first time.
-To fix it, I can either format /system or /data (to ext4). To do that, I have to flash an other recovery.
-It does not matter if I use the format script (as provided in the OT), or with twrp advanced wipe/change partition type (which only works if TWRP is not newer than 2.8.1.0 - newer versions give an error: unable to wipe data).
-The OS itself runs fine.
A strange thing to note: there was a time, where this problem occurred, to fix it, I had to flash an other recovery via odin, boot into that recovery, do nothing(!), reflash twrp with odin again, and I could access twrp again until I booted the OS again. This suddenly stopped and the only fix is the way I described above.
And a site note: the "loop" only occurs when using the advanced reboot options from the OS (or any other tool from the OS to boot into recovery), as it sets a recovery flag. When using volup+home to access recovery, it only happens once, still allowing the workaround to flash another recovery to remove the flag, and able to reboot system afterwards again (but no access of twrp anymore).
I also tried updating bootloader (and modem) with no success.
Process on installing: wiping everything except externalSD, change /data to f2fs, reboot recovery, install CMx, gapps, supersu, agnikernel.
Aaaaany input that might help to resolve this is really appreciated.

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

Always boot into recovery mode

Today I wanted to upgrade to OOS 5.1.1. But after flashing and reboot, my 5t went into recovery mode again. Then after that, the phone always reboot into recovery mode.
I tried flash stock recovery, blue spark recovery, tried to flash oos 5.0.4, none works.
What can I do to save my 5T? TIA.
I noticed that I have this error in my twrp codeworkx recovery:
failed to mount /vendor (invalid argument)

This happened to mine as well. I did a full wipe and flashed the stock recovery and then flashed the most recent Stock OOS.

What do you mean by a full wipe?
cache+davlink+system+data? I did.
Internal storage needs to be wiped too?
Floss0324 said:
This happened to mine as well. I did a full wipe and flashed the stock recovery and then flashed the most recent Stock OOS.
Click to expand...
Click to collapse

lyrebird said:
Today I wanted to upgrade to OOS 5.1.1. But after flashing and reboot, my 5t went into recovery mode again. Then after that, the phone always reboot into recovery mode.
I tried flash stock recovery, blue spark recovery, tried to flash oos 5.0.4, none works.
What can I do to save my 5T? TIA.
I noticed that I have this error in my twrp codeworkx recovery:
failed to mount /vendor (invalid argument)
Click to expand...
Click to collapse
First thing, the error about /vendor in TWRP can be ignored because you will not have that partition if you have not installed a trebelized ROM (MOKEE treble rom).
Next is your issue:
There are two approaches I can Think of:
Approach 1) - Download official full rom from this thread
- Boot into TWRP and copy this ROM to your phone
- Wipe Clean (standard TWRP clean flash step) keeping internal storage intact
- Install ROM and try to boot.
- Sometimes it will boot back into recovery, you can try to install again.
- If it boots up fine, then follow this guide to install TWRP correctly again.
- If it didnt boot up and you are ok to wipe everything, Boot into TWRP
- Wipe Everything (you will lose all data, photos everything)
- Boot back into twrp
- Now follow install steps again.
Approach 2) if 1 didnt work:
- use this guide to unbrick your device
- You can then ROOT, install recovery etc by following this thread
I have recently experienced this problem, there was little help and finally I have to wipe all data on the phone. It was a pain in the ass and i hope you wont have to go through it !

Did many rounds of flashing of recovery and rom, tried many combinations. It eventually worked.
While I am not 100% sure, i think what makes it work is to use compatible recovery (8.0 or 8.1) with rom, and wipe both cache, system, and data after (?) flashing.
Thanks!
krispuniq said:
First thing, the error about /vendor in TWRP can be ignored because you will not have that partition if you have not installed a trebelized ROM (MOKEE treble rom).
Next is your issue:
There are two approaches I can Think of:
Approach 1) - Download official full rom from this thread
- Boot into TWRP and copy this ROM to your phone
- Wipe Clean (standard TWRP clean flash step) keeping internal storage intact
- Install ROM and try to boot.
- Sometimes it will boot back into recovery, you can try to install again.
- If it boots up fine, then follow this guide to install TWRP correctly again.
- If it didnt boot up and you are ok to wipe everything, Boot into TWRP
- Wipe Everything (you will lose all data, photos everything)
- Boot back into twrp
- Now follow install steps again.
Approach 2) if 1 didnt work:
- use this guide to unbrick your device
- You can then ROOT, install recovery etc by following this thread
I have recently experienced this problem, there was little help and finally I have to wipe all data on the phone. It was a pain in the ass and i hope you wont have to go through it !
Click to expand...
Click to collapse

What TWRP were you using? Had basically the same problem with "twrp-3.2.1-x_blu_spark_v8.74_treble-op5_op5t.img", flashed an older version and it worked fine.
Seeing "failed to mount /vendor (invalid argument)" as you mentioned happened to me too. I think it means it's only for treble compatible ROMs.

if you were rooted with magisk, you have to flash the magisk uninstaller before flash the rom.

I had the same problem after flashing XXXnolimits rom (bluespark recovery 8.73). I just power off the phone pressing the power button for a while (10-20 seconds). It worked for me and the rom was succesfully flashed. Hope this help for the future.

i will keep this in mind and will try it next time when we have an update! Thanks.
caluz78 said:
if you were rooted with magisk, you have to flash the magisk uninstaller before flash the rom.
Click to expand...
Click to collapse

Unable to Install any custom rom.

So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?

So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?

JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?

SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.

JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.

SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.

JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.

SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.

hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good: