Develop Bugs

Problem with Desire

Hey guys,
I went to flash a new stable build of Froyo on my Desire this morning.
And i backed up using Clockwork, and then the ROM all installed fine. But once the phone had booted up, it stayed on the custom boot logo, despite the keypad lighting up, the green charge LED coming on and me being able to lock and unlock the phone.
So i figured that this was a problem and went to back to restore my old ROM and carry on like i have done many times before. However once i have booted into Clockwork, and gone to the recovery section, i select my most recent backup and the device then says "No Files Found" in the recovery zip.
And when i try to install update.zip from my SDCard the device just flashes up with installation text for about 2 seconds then vanishes and goes back to the clockwork menu having done nothing
What can i do?

i wouldnt worry about it too much
your phone completely works and youre not restricted of any access
seeing that clockwork is not finding any files have you tried making a new backup?
have you tampered with the recovery lately?
if recovery is not finding any files then maybe there is a problem with it, and if i were you i'd reroot my phone with unrevoked to re-install recovery.
if your recovery actually just does not work it could mean that the recovery image is corrupt, this can be fixed by installing a RUU (note that this will unroot your phone but re-install the recovery image).
if this is not the case then im sure im soon to be corrected by someone more knowledgeable than me

Well, i wiped the Cache and Data and now the phone boots up and functions fine, however both mobile internet and Wi-Fi both dont work, but i figure this is just the rom i am using.
So i'm just gonna reroot, sideload clockwork and what not and then try putting the Desire HD rom on it haha.
Thanks for the help

won't boot stuck on encryption, did not activate!

Woke up this morn and grabbed the phone to check the time and if any messages came in to find that it was stuck in the could not encryption unsuccessful screen with the reset button....
I've had this before and been able to go around it by booting into recovery and starting the phone normally, but this isn't working anymore. I was on OctOS.
When in Download Mode noticed that the Qualcomm Secure Boot was active, could this be the problem? I never activated it or any encryption for that matter.
Tried wiping cache/davlik/system and installing another rom (PAC) and not TWRP is failing to wipe correctly... Keep getting "cannot mount E:/". Flashed the latest TWRP through Odin and no luck either. Can't upgrade for now :/
Also, when I go through file manager in TWRP to check if my media (pics/vids) are still there and nothing :crying:
Any help is greatly appreciated!
Thanks!

Intalled Philz Touch and tried to wipe and it says the same thing as TWRP "unmount of /data failed, no such volume"
Am I screwed? :/

Flashed Philz Touch via Odin, flashed PAC AOSP in recovery, booted and it happened again except this time it booted into Philz did something... didn't say what on the screen and rebooted. This time android app optimization came up for all apps (missed to mention that before it was showing 15apps only) and brought up the initial process of Android.
Lost all my pics and data since it wiped the internal data partition including media... Never had this problem before, but guess lesson learned ALWAYS HAVE A BACKUP OF MEDIA AND TITANIUM BACK UP on the PC or cloud.

Possible hardbrick of s4 sgh m919 after twrp restore

Hi, I have a rooted s4 sgh m919. I am running twrp custom recovery. So I just flashed cm 13 nightly build for the s4 and it worked and ran through boot up and everything. Then I realized that I had stupidly forgotten to backup my apps(I though I had but it was a twrp backup). So I returned to recovery mode using adb because my up volume buttons dont work(biggest problem for me now) and used twrp restore of a backup I made before the new rom. Now I know that my twrp backups work because I have successfully restored before but that was using the same rom, this is the first time flashing a new rom. Since I am a noob, I didn't know that I have to factory reset and delvik cache wipe before I restored my backup since they were different roms. Now after booting up and getting past the boot animations it goes straight to a black screen with a bunch of "Unfortunately ______has stopped" for just about every single app I have including system apps and UI. I can boot into the download mode prompt(where it says volume up to download mode, down to reboot) but since my volume up button doesn't I cant boot into recovery or download and do a factory reset. I can boot into safe mode but I still get the same black screen with a bunch of "Unfortunately ______has stopped". I also can't do it through adb since I have no access to phone settings and when I connect to the computer, the computer make a sound recognizing something was plugged in but won't show my phone in the libraries and when I use "adb devices" my phone isn't there. I stored my backup onto my ext sd card if that helps. Is there anyway to get into recovery mode or even just do a factory reset without using volume buttons or the computer? And has anyone else had this problem and if so what is it called(hard brick, soft brick, bootloop.....). Thanks!

You need to fix your up-vol button.
There is also a special micro USB loopback plug which I think can make the device boot into a special firmware loader mode. Then you would use heimdall/odin to replace the firmware, but I have never done that.
As for what to call the problem, I say "dumb user with broken hardware". You knew that your up-vol button was broken and what would happen if you could not get into recovery. Now that it has happened you want a magical fix instead of doing what you already know you need to do. Sorry for honesty.

1st- buy a usb jigg, they go for less than $5 amazon, eBay etc.
2nd - while phone is powered off use the USB jigg to put it into download mode
3rd- use Odin to flash the latest ok3 firmware.
4th - use Odin again to flash cf auto root. (No need to check if it has root the recovery you flash should be able to root it)
5th- use Odin again to flash Philz touch cwm recovery.twrp causes lots of problems when flashing. Philz recovery has been flawless.
6th- flash any rom of your choice. If you can't get into recovery theres an app called quickboot that can put you in recovery as long as you're rooted.

I ticked everything on advanced wipe to delete. Now my phone is stuck on the bootload

I'm currently trying to root my Moto G5 but I can't seem to get a rid of the password it asks at the beginning. I wiped everything by ticking the whole lists on advanced wipe, format data then swiped to factory reset. Now my phone won't boot up normally and stays stuck on this screen. I can however use the bootloader. What can I do to fix this?
It stays stuck on this screen i.imgur.com/OeRczD6.jpg

I told you in the other thread you created to NOT advanced wipe as this will not remove encryption
You have two options
1- flash stock rom firmware via fastboot
2- remove encryption and flash a custom rom
Oh and your phone obviously won't boot as you have wiped system (the rom) so there's nothing on your phone to boot!
See my reply on how to remove encryption in the other thread you created
https://forum.xda-developers.com/g5/help/twrp-password-install-files-ill-pictures-t3913693

[SOLVED] Bootloop after flashing IMEI qcn file, caught in vicious circle

/EDIT:
Alright, the thread can be closed. I somehow managed it.
In case someone faces the same issue, I used twrp to dd the sdf files back on the phone which stopped the reboots. After that, just wiped and formatted everything again and reinstalled the ROM.
Hello guys,
I hope you can help me with this issue since I've tried everything I know to fix this problem.
The plan:
Unlocking bootloader, installing TWRP and xiaomi.eu ROM on a new device.
Changing its IMEI with QPTS/QFIL afterwards.
What happened:
Unlocked successfully. Installed TWRP, xiaomi.eu ROM and Magisk.
After pulling the QCN backup and editing the file I pushed it back to the phone what seemed to work.
After rebooting, I noticed that the phone rebooted 5 seconds after showing me the "Enter PIN" screen.
Booted up again and the same thing happened.
I booted into TWRP, wiped and formatted "data", installed the ROM again. The phone started up normally and there was no reboot.
I went back to TWRP and flashed Magisk, the phone crashed again and everytime I boot it up, it immediately reboots after some seconds. Installing Magisk somehow triggers the phone to reboot on its own.
I thought to start over, flashed everything from stock using Mi Flash Tool and the newest China Rom.
After starting up the phone, the issue still exists. This time with this rom there is no difference between installing Magisk or not, the phone always reboots after showing up the miui welcome/setup screen.
Current situation:
The phone boots up Android, reboots after some seconds and goes into fastboot automatically. After the fastboot timeout it again reboots automatically, goes into the OS and crashes again and on and on.
No matter what I do, I can't keep the phone from rebooting.
And since I can't flash Magisk, I have no root.
This means that I can not use root to put the phone into diag mode to restore the original qcn file.
I have backups of the EFS partition and also sdf7/8/9/10 files. I just don't know how to restore them given the current situation.
Thank you very much in advance for your support!
Cheers