Reason For Loss of root when flashing new CM roms?? - G1 Q&A, Help & Troubleshooting

ok if someone doesnt have the latest radio the htc rom flashes it automaticly..(it just happend to me)
so when the radio flashes then could the recovery menu get flashed as well??

YES. YOU MUST go back into recovery mode (should do it automatically after flashing htc "recovery") but hold the home button after the package unloader image blinks off. Flash the cyanogen update immediately after. If you dont reboot into your custom recovery, it will boot adp1.6 and you lose your recovery image.

Related

[Q] HELP can ONLY get into Fastboot, cant do anything else!!! Brick???

I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Have you used ADB to delete cache, Then re-flash a recovery ? Then full wipe etc and clean install a Rom ?
Sent from my HTC One using Tapatalk 2
jthornton71707 said:
I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Click to expand...
Click to collapse
type fastboot erase cache from PC while phone is in fastboot. you should be able to get into recovery afterwards. If not, flash another recovery from fastboot. fastboot flash recovery RECOVERYNAME.img

[Q] No recovery anymore after flashing tilal's 10.2 build

Hi,
as the tilte sys, I don't have a recovery anymore after flashing tilal's 10.2 build. Do I have to flash a new boot.img with fastboot as in stock?
That's odd. You can extract the boot.img from the zip and flash the image with fastboot:
fastboot flash boot boot.img
fastboot reboot
If this not works you also can flash an older cm10.2 version: http://goo.im/devs/tilal6991/roms/mint/cm-10.2/
After doing this you should flash the last 10.2 again. I never have lost CWM.
Edit: Sorry, youst reading this: http://forum.xda-developers.com/showpost.php?p=44230652&postcount=9
Maybe you have to flash an boot.img from the last 10.1 nightlies.
Another idea was to install this recovery (tilal advised this): http://forum.xda-developers.com/showthread.php?t=2115726
Download GooManager from PlayStore and load/install TWRP. But be sure that there is no backup you want to recover with CWM. I havn't found a way to recover older backups done with CWM.
I flashed a twrp image and the tilal build again from there. After reboot the recovera is away again. Later I will try to flash the boot.img from inside the rom.
So I flashed boot.img from inside the rom with fastboot but I still don't have a recovery. Does the keys to hold at start have changed?
Ok, I read in the roms thread that recovery is broken. Recovery should be installed in a fota partition. Do I have to simply flash the twrp fota image or do I have to do some other steps before flashing this.
Sorry for this noob questions but I rather ask before I will brick my device.
The last link in my answer above gives you all needed informations..
Phone screen dead after installing cynagenmod
Hi guys,
i am in reaaly a very big trouble,
just bought an xperia tx and i somehow rooted it then got cwm mode. Now after i installed the cynagenmod 10.1 by cwm i directly rebooted the phone and now the screen is staying black n the phone is not booting. The notification led is blinking and after pressing the power button its vibrating but not booting.
People say i didnt clear cache so this is the problem.
I am a rookie in this so please give me a detailed guide.
Need urgent help please it would be very kind.
Indy500xl said:
Hi,
as the tilte sys, I don't have a recovery anymore after flashing tilal's 10.2 build. Do I have to flash a new boot.img with fastboot as in stock?
Click to expand...
Click to collapse
I think that your issue comes from the fact that the ROM comes with advanced recovery options disabled. HW buttons don't work to go into recovery with this build for some reason. Having said that, you can boot into recovery from within the ROM.
Go to Settings > Developer Options and in there you will have an option called "Advanced Reboot". When you check that and you try to reboot your device (hold power button until menu pops up), hit "Reboot" and you will be prompted with a few options, one of which is "Recovery".
I hope this helps.
egzthunder1 said:
I think that your issue comes from the fact that the ROM comes with advanced recovery options disabled. HW buttons don't work to go into recovery with this build for some reason. Having said that, you can boot into recovery from within the ROM.
Go to Settings > Developer Options and in there you will have an option called "Advanced Reboot". When you check that and you try to reboot your device (hold power button until menu pops up), hit "Reboot" and you will be prompted with a few options, one of which is "Recovery".
I hope this helps.
Click to expand...
Click to collapse
Yeah, thank you. That did it.

[Solved]C5503 Softbrick Red LED is flashing

hey guys!
I've done something stupid with my ZR and not the vibra call just vibrates twice and the red LED is flashing when i wan't to turn on the phone.
But step by step: the phone has XZDualrecovery 2.8.26 with TWRP 2.8.7.0 and the "lastest official stockrom which is 5.1.1 and root.
I tried to update to TWRP 3.0 in the TWRP menu, but i've done something wrong i guess. there was only one option to choose, i cant remember exactly -perhaps it was something with boot partition?! And now it stucks at the red led right after pressing the power button.
is there any chance to bring it back to life again? is it possible to flash just the boot partion again? Which files should i include/exclude in flashtool?
flashtool can detect the phone in flashmode and also in fastboot mode!
flashed the ftf again, but excludes the wipe of user data and apps! -problem solved! :good:
a mod can delete this post.
Is that your phone bootloader unlocked?It will be easy if your phone UB so only by command shell you can flash the recovery img and flash rom from the recovery.What you have tried is wrong.You should install the recovery to recovery partition.Or if you want to flash stock rom from the flashtool do nothing and flash directly.
well,remember the first line to get job easily done.

Missing Factory boot menu / factory mode menu on Roidmi2 (WT86047)

As described here (https://forum.xda-developers.com/showpost.php?p=73658433&postcount=1883) I installed the LineageOS 14.1.
But since then pressing Volume Up + Power buttons doesn't bring me to the factory boot menu anymore (in which I could statt TWRP), it stucks in the Mi-boot logo.
I already reflashed the ROM again and the current TWRP via fastboot but also via TWRP itself, but the problem still persists.
I can only acces TWRP if I start it via the TWRP app (and reboot) or via fastboot "from outside" (fastboot boot recovery.img).
Any idea how to fix it? Is there a factory recovery image fot the WT86047?
chaosp said:
As described here (https://forum.xda-developers.com/showpost.php?p=73658433&postcount=1883) I installed the LineageOS 14.1.
But since then pressing Volume Up + Power buttons doesn't bring me to the factory boot menu anymore (in which I could statt TWRP), it stucks in the Mi-boot logo.
I already reflashed the ROM again and the current TWRP via fastboot but also via TWRP itself, but the problem still persists.
I can only acces TWRP if I start it via the TWRP app (and reboot) or via fastboot "from outside" (fastboot boot recovery.img).
Any idea how to fix it? Is there a factory recovery image fot the WT86047?
Click to expand...
Click to collapse
Volume Up + Volume Down + Power Buttons
That helps to get into TWRP during boot. Thank you!
But how abot the original factory mode menu? Is it gone with the current TWRP on all Roidmi2 devices or just on mine?
chaosp said:
That helps to get into TWRP during boot. Thank you!
But how abot the original factory mode menu? Is it gone with the current TWRP on all Roidmi2 devices or just on mine?
Click to expand...
Click to collapse
Factory Mode Menu is exclusive to MIUI ROMs or ROMs who include the files or partition of FMM (correct me if I'm wrong), TWRP has nothing to do with FMM missing. Basically, devs of Redmi 2 custom ROMs don't include FMM, and LineageOS (you flashed it) certainly doesn't include FMM. So if you want FMM, better stay stock, or find a way to build a flashable zip that enables/install FMM in any ROM, regarding stock or custom.
Umm.. by Factory Mode Menu, are you talking about the menu that can do HW tests? or are you talking about stock recovery?
Just do the fastboot method, and it'll come back. I even flashed a custom MIUI (xiaomi.eu's Custom MIUI ROM) via TWRP and factory mode menu exist in it. Just to make sure, if you are going to flash xiaomi.eu's CusMIUI ROM, I suggest you to backup your efs and modem partition (modem-firmware) before flashing it, because installing that ROM flashes firmware's too, in some cases, the phone couldn't detect the SIM card, or signal lost because of incompatible bootloader firmwares. If you're familiar in editing updater-script, trying deleting the rows that flash firmware, and make sure to delete the firmware files too inside the zip. (<- Extra info, just incase, I don't want to be blamed for these type of problems)

Fix boot

So I was restoring the stock boot image so I could flash magisk, and I ran into a bit of a problem. I tried booting it up after flashing, and it's stuck on the boot screen so I'm assuming I flashed a bad boot. This wouldn't normally be a problem, except that my volume up button doesnt work meaning I can't boot back into recovery mode/bootloader. Is there a way to get to the bootloader or recovery screen without using the volume up button?
I think you might have accidentally flashed the stock boot image to your recovery. Have you checked the option to flash the boot image and not recovery?
frosted.efizzle said:
I think you might have accidentally flashed the stock boot image to your recovery. Have you checked the option to flash the boot image and not recovery?
Click to expand...
Click to collapse
I'm pretty sure I flashed to boot, I can turn it on and it just shows the blu logo. Before I had a custom boot image though and it's not showing that anymore though.
I'm assuming that custom boot image came prerooted right? You might need to flash the rom that came with the custom image to boot. An easier way to get Magisk which I've done is to flash rom, then flash the unSU zip to remove traces of root then you can flash Magisk like normal.
frosted.efizzle said:
I'm assuming that custom boot image came prerooted right? You might need to flash the rom that came with the custom image to boot. An easier way to get Magisk which I've done is to flash rom, then flash the unSU zip to remove traces of root then you can flash Magisk like normal.
Click to expand...
Click to collapse
I would do that, except with the volume up button broken I'm unable to get to recovery mode, and without being able to boot into the system I can't use adb

Categories

Resources