Develop Bugs

help!!

i think i f.... bricked my phone. i was tryin to install rd miui. did a fastboot flash boot boot.img, fastboot clear cache, than booted into recovery and installed the miui zip. when i restarted my phone, it wont open, it got stuck on htc logo. got back to recovery, insalled the last rom i had, but nothing. again stucked on htc logo. what can i do? help me guys

Install the boot.img for your last ROM.

Install the stock kernel(boot.img)

for any rom you install you should flash boot for that rom or you will stuck at htc logo.

Issue with flashing roms with s-on

I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated

tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.

I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks

tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:

Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks

tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.

It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help

Can only boot into fastboot mode anymore

Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy

Reapy1804 said:
Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy
Click to expand...
Click to collapse
Shut down your device and press volume up button while connecting it to your computer. Then it will boot into fastboot mode and you should be able to flash stock firmware in flashtool, and then you can start from scratch.
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
Another option is to follow this guide to install Recovery and When done you can boot into Recovery and flash a custom rom. http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719

Reapy1804 said:
Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy
Click to expand...
Click to collapse
Try Rashr app from play store. It sounds to me like incompatible kernel/recovery combo. Download a recovery IMG, (latest TWRP, for example), then use Rashr to flash it. You can also use it for flashing a boot IMG. Its probably the same reason you had trouble flashing ROM.
Besides that, you can install real recovery, which works the same regardless of the kernel-
http://forum.xda-developers.com/xperia-e3/general/bootloader-devices-real-recovery-t3096837

Okay, after flashing it with flashtool it starts again. I now put the RR rom with Android 5.1 on.
I have again the CM recovery, but at least it starts how it should.
I will try to flash the real recovery, thanks!

Update:
Currently running RR with Android 5.1.
I would now like to use RR with Android 6, but again, I can only boot into the Cyanogen recovery, which cant make a backup of the currently running OS. I have tried to flash the boot.img from RR 5.1 with fastboot, Rashr, but nothing seems to work, as it puts me back to the Cyanogen recovery every time. How can I replace the Cyanogen recovery?
And one more question: When the phone starts, the notification light turns into red before the Sonmy logo appears and then turns into pink. What does the red light mean?

Reapy1804 said:
Update:
Currently running RR with Android 5.1.
I would now like to use RR with Android 6, but again, I can only boot into the Cyanogen recovery, which cant make a backup of the currently running OS. I have tried to flash the boot.img from RR 5.1 with fastboot, Rashr, but nothing seems to work, as it puts me back to the Cyanogen recovery every time. How can I replace the Cyanogen recovery?
And one more question: When the phone starts, the notification light turns into red before the Sonmy logo appears and then turns into pink. What does the red light mean?
Click to expand...
Click to collapse
You need a recovery img, not boot img. Try this one - http://forum.xda-developers.com/showpost.php?p=65361797&postcount=78 or this one - http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719 Open Rashr, choose ' recovery from storage'.

Okay, i flashed the 2.8.6.0 version via Rashr and now Im stuck on the Sony logo...the notification light is orange all the time, but I cant restart the phone anymore...any suggestions?
Edit: Worked! Used the combination between power and Vol+ to reset, and now it starts!

You should disable CM Recovery Protection – On your phone go to Settings > Developer options. Then disable the ‘Update recovery with system updates’ option. Otherwise it will keep installing cm recovery itself.

Semi-bricked XA1, possible recovery?

So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!

Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.

Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader

Problems getting rooted (touch not working)

Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse

Update:
I ran the "flash-all.bat" on both slots and booted up twrp using fastboot and installed the magisk zip (not the img) before installing the manager, I then installed the manager once I booted up the rom. So I guess it's stock with root for now...

hapse said:
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Click to expand...
Click to collapse
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.

Lughnasadh said:
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Click to expand...
Click to collapse
Ah I see, thank you