Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
I installed TWRP on my phone, and went into Bootloader an hit RECOVERY so I can get to the program (the first time I did this it brought me to the TMRWP program). THIS time, it completely wiped my friggin' phone... after I sat there like 4 hours re-setting up everything PERFECTLY how I wanted it.
What's weird is it kept ALL my apps that I converted to SYSTEM APPS, but all my user stuff is gone.
Lesson learned... Don't click recovery from Bootloader.
That has yet to happen to me with any recovery and 3 devices currently with twrp. Might be a step missed with the install or maybe you left a bootloader update zip and ran it when you rebooted? Or it can be a bug as going to recovery from bootloader via a cold start is how to get there traditionally. I would email teamwin and try to sort it out or redo the recovery install, making sure to check the md5 of the file after you download it.
Sent from my Transformer TF101 using Tapatalk 2
Your supposed to click recovery at bootloader. Thats where you do backup, restore and flash new roms.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.3
Kernel. 3.0.30 Bricked
Radio 11.68.3504
That's what I thought too. If I'm not mistaking, I flashed the new firmware after I did the TWRP, so maybe that screwed it up somehow. I take it TWRP must be the LAST image you flash? Only flashes I remember doing were:
Customize bootloader screen
TWRP.
firmware update
Do I need to re-flash the new firmware before re-flashing TWRP, or is the firmware going to remain no matter what I do from this point on?
Just adb flash recovery. Put the recovery image in your platform tools folder. Adb reboot bootloader. when you are rebooted adb flash recovery recovery.img.
Or use one of the many tools made to do that on our forums
Sent from my ADR6425LVW using xda premium
Well I went ahead and used the GOO Manager to flash TWRP again, and this time it worked fine. I'm going to re-setup my phone again then before I customize it back like I had it, going to try to get to recovery and see if it works.
With it now being installed, does that mean I can't flash anything directly from SD Card or modify the bootloader anymore without it causing problems?
What I mean, moreso, is... if I ever put factory reset. will it reload the factory rom + keep the newest firmware I installed (etc.) or do I nee to back up the phone with TWRP and recover from that when I want to load it back?
Factory reset just puts things back to the way they were without the stuff in the data partition or any user apps or settings. This means that say you flash a custom rom, it will reset to as if that custom rom was freshly installed since the custom rom has replaced the factory rom in the /system/ parition and anything else related to it.
With that said it is usually a good practice after rooting a fresh device to do the nandroid and then transfer it to a computer before you do anything else. Note that while you probably won't be switching recoveries a lot, that nandroid backups generally work only with the recovery that generated them so don't get them mixed up.
Ok guys, Heres what I do & what happens,
(model # C6833)
1- root device
2- install new boot kernel (adv-stock-v4) (( Even tried v5))
3- unlock bootlader (only had to do it the first time, bootloader stays unlocked)
4- install cwm/TWiRP
5- get into TWIRP or CWM & wipe as I should
6- install rom. (It wont install)
7- reboot
8- stuck @ sony logo. & then reboots,
9- reinstall stock rom
This happens every time I try to install a rom.
I also get the message before I reboot, no root, would you like cmw/twirp to fix it, I go with yes. & ive tryed no as well. no difference. Still get stuck @ Sony logo & get reboot loop.
Any ideas ?
Im not new at rooting & roming.
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Triflot said:
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Click to expand...
Click to collapse
I did the flashtool thing. ( I'll edit my post ) I did the boot.img & Im trying to use SlimRom. Everything seems to be fine until I try & install the rom. Then it goes to hell.
Btw, Slimrom is compatable.
So what's the actual error message you get upon installing a ROM?
Something like, installation canceled. could not install rom. It goes threw a few steps. gets a few things installed (or so it seems) & then it hangs & I get that message. I thought, at first, it may have been a corrupt download. But after a few times of downloading it. I kinda think its no longer that.
Have you tried another ROM? Someone else is also having boot trouble with Slim in its development thread.
No actually, I have not. I will soon though now. And report back. First I need a stock U.S. rom. Just in case. Cant seem to find one.
Been using a CE (Central Europe) based stock rom.
Hey,
I'm kind of a newbie developer so please bear with me!
I have a WileyFox Storm, that runs Cyanogen OS 13 (kipper) as stock. A while back, I tried rooting it, and in the process installed TWRP Custom Recovery (which is a custom one made for the Storm). Well, the process of rooting didn't work (multiple times), so I gave up.
Right, it comes to today where my device can receive an OTA update. I pressed install, where it rebooted back into recovery. As it turns out, I forgot about the TWRP CR which was still there, thus, I could not update my device.
I now want a way to install the stock recovery (just the recovery), without having root access, and preferably without factory resetting my device (I have done this too many times and it just pisses me off!).
I assume I just install the .zip from CM's website, and side load the recovery.img using ADB but I simply do not know enough.
Please help, thank you!
)
Root has nothing to do with flashing ADB so you can go ahead and sideload it as long as you have the correct drivers for your phone
And my phone won't factory reset if I just sideload the recovery.img?
Yep you are correct
My SM-G900T is running Lollipop 5.1.1 rooted by installed twrp-3.0.2-2-klte + SuperSU using odin.
I am planning to update it to Marshmallow 6.0.1 (G900TUVS1GPK3) using odin. After the update, I believe the phone will be unrooted. Should I install twrp-3.0.2-2-klte + SuperSU again in order to bring back the root?
Yes, is the short answer. It's a pretty simple process, just flash the update, boot back to Download, flash TWRP, boot to recovery, then flash SU. However, after some experimentation, I'd recommend an extra step, especially if you're planning to run Xposed. After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
I'm not sure if you'll also need to wipe or not, all the updates I've done have been MM->MM. You can flash those without any wiping or restoring because they don't touch /data. I've found that switching between stock & modified MM roms without wiping appears to work but later causes severe performance problems. Between stock updates, I've had no problems even without wiping.
invisiblewave said:
Yes, is the short answer.
Click to expand...
Click to collapse
Thank you Invisiblewave. I understand that I need to reflash twrp, but since I installed SuperSU already and I think the update would not delete/uninstall it, if I flash SuperSu again, will there be a problem?
The update will remove your previous SuperSU install, so yes, you have to flash it again if you want root.
invisiblewave said:
After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
Click to expand...
Click to collapse
Thanks for the tips! I just did the same upgrade and wanted to make sure everything worked afterwards.
use this guide
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
That guide is incomplete. It needs an additional step after flashing the update to let the phone boot once normally, otherwise WiFi calling doesn't work. Flash update, reboot (stock recovery runs and does stuff), reboot to Download, then flash TWRP, SU, Xposed, etc.