I am trying to install the Flumics rom 3.0 its installs fine but the problem is when i reboot it reboots but then goes back to TWRP. I also get a message saying
'TWRP can leave your ststem partition unmodified to make it easier for you to take offical updates. TWRP will be unable to prevent the stock ROM from replacing and will not offer to root your device'
Installing zips of performing ADB operations may still modify the system partition
I really want this rom to work on my phone Im not sure what to do now.
I followed this forum to get my recovery
https://forum.xda-developers.com/redmi-note-3/help/official-twrp-askibg-password-to-t3492362
Your help would really really be appreciated.
Thanks
Related
good morning, I need help because I can not fix my TF201, I commented that I did a factory reset and start the tablet remains in the clockwork recovery v5.8.2.0 I have installed, it is as if he had no operating system installed as reboot and go to recovery, I tried to install several roms sending the file via adb to sdcard and install the TF201 but the same thing keeps happening restart fails the recovery entoces perform the necessary wipes and install went back to normal and recovery recovery touch to test and nothing at all is sending me the recovery is as if he had done nothing, I went back to install another rom follow the steps and went out to the installation was a success and zilch restart sending me the recovery continues as if it had no operating system , the truth and not to do someone please help me with this big problem adb I can enter the terminal, the driver and nose work well I can do that but please help and thanks for your attention
first of all, reposting on multiple forums will get you ignored by most peole
secondly, your statement is extremely hard to read, i suggest you don't speak english.
lastly, we need more information. are you getting errors in the install? is this the first time you're flashing? what rom did you flash that started the issue?
-what you can try now-
Try flashing a rom with TWRP instead of CWM, i've seen issues with CWM that TWRP doesn't have. (http://forum.xda-developers.com/showthread.php?t=1615990)
Use NVFLASH to flash your backed up files. If you didn't backup with NVFLASH prior to all this work then, sir, you should not be flashing in the first place and maybe this is the lesson you need.
biggem001 said:
first of all, reposting on multiple forums will get you ignored by most peole
secondly, your statement is extremely hard to read, i suggest you don't speak english.
lastly, we need more information. are you getting errors in the install? is this the first time you're flashing? what rom did you flash that started the issue?
-what you can try now-
Try flashing a rom with TWRP instead of CWM, i've seen issues with CWM that TWRP doesn't have. (http://forum.xda-developers.com/showthread.php?t=1615990)
Use NVFLASH to flash your backed up files. If you didn't backup with NVFLASH prior to all this work then, sir, you should not be flashing in the first place and maybe this is the lesson you need.
Click to expand...
Click to collapse
ok sorry friend but my english is not good, I commented that when installing a rom gives me no problems, the installation ends well and seems to install something, when I asked to restart the tablet back to the recovery ..
how install the TWRP as if I have no operating system?
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.
I recently installed TWRP custom recovery on my phone so I could install the "Carbon" custom ROM. When it turned out that I apparently need CWM, not TWRP in order to do this, I had already installed TWRP. Some other things I can't remember well enough to describe happened while I was tinkering further, and what I know now is that there is NO operating system installed on my phone, just TWRP (which is the only thing into which my phone will boot) and it's telling me it's "unable to mount preload." I vaguely remember it telling me something to the effect of "you may need to [some action here] before you'll be able to use 'data' again" when the process of trying to install Carbon through TWRP failed. Now I can't seem to put the stock firmware back on the phone. When I select the ZIP file to install, it tells me "skipping MD5 check: no MD5 file found" even though the ZIP file is definitely on the SD card. I'm guessing this has something to do with its inability to mount "preload"? I honestly don't know. I just know I'm stuck.
What I want to do is reinstall the stock firmware and recovery program that comes with my phone, get rid of TWRP completely, and then try installing CWM from the play store, the simple way. All this bootloader stuff is too advanced and risky for me. But first I need to get my phone working/booting into the android OS in the first place.
Can anyone give me instructions on how to fix this? If so, please be *extremely* specific and explicit, tell me every single step very clearly, as though you were explaining it to a child. Please don't assume I know what you're referring to with slang, shorthand or anything else. This is my first experience with custom recovery managers and ROMs, so please don't take anything for granted.
Hi guys
Apologies if this has been posted in the wrong section.
I have recently inherited a Galaxy S2 (GT-I9100) running the CyanogenMod 12.1, Android Version 5.1.1
I have spent the last two day trying to and failing miserably to install Xposed Installer V3.0 Alpha 2, I have searched Google and read through numerous forums on how to resolve this, but the more I read the more confusing it becomes. I would really appreciate any help/assistance in helping me fix the problem, so that I can run the app without any issues. When I access the app's log it states:
data/data/de.robv,android,xposed.installer/log/error.logpen failed. ENOENT (No such file or directory)
Also, when I try to run Titanium Backup 6.1.0, I get an error stating:
Sorry, I could not acquire root privileges. This application will *not* work! Please very that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
I have gone into Developer Options and set Root Access to Apps and ADB.
As I new to Android my understanding (please correct me if I am wrong) that the CyanogenMod 12.1 was actually a ROM and therefore Titanium Backup should work. FYI SD Maid not working.
Any help on both of these issues would be most appreciate, please bear in mind I am a noob where Android and Galaxy S2 are concerned.
Thanks in advance.
The forum for the i9100 is located here, but because it's so close to the i777 we can probably help a bit.
Sounds to me like your phone isn't rooted, as none of the apps you mention will work without root privileges. Install the latest SuperSU; you should be getting access prompts if you're correctly rooted.
If you are not prompted for root access when opening apps such as Titanium Backup, you'll need to install Framaroot and use the Aragorn exploit in order to easily root your device. Let us know if either of these work for you.
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
pops1368 said:
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
Click to expand...
Click to collapse
Strange. In that case have you tried doing a complete wipe in recovery, then reinstalling the ROM? In your case you would boot into recovery, wipe /system and dalvik cache, then install ROM and gapps. Just make absolutely certain you're running a custom recovery before doing this, such as CWM (ClockworkMOD) or TWRP (TeamWin), or you could damage your device if you're on stock recovery. And, of course, make sure you have the ROM/gapps already on your device before wiping everything!
Because you inherited the device the best method would normally be to flash back to stock and start all over - if for nothing else it's a good learning experience. Hope this helps.
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
pops1368 said:
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
Click to expand...
Click to collapse
As long as you have a custom recovery there's very little that can go wrong with a full wipe. I would suggest booting into recovery first (power button + both volume keys, then release at the Samsung logo) and make sure you're running either CWM or TWRP. While in recovery do a backup first, as a "just in case". You can always restore your device fully from a backup.
The next thing to remember is to make sure your ROM/gapps are compatible with one another. For instance, if you're installing a CM12 (Android 5.0+) ROM make sure your gapps are also 5.0+.
Best of luck!
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
pops1368 said:
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
Click to expand...
Click to collapse
Best option for you is to go to the i9100 forum and download a kernel for your phone that is compatible with the OS version you want to install (CM12, which is 5.1. in your case). With your device (as well as our i777), the kernel and recovery are fused together, so you cannot use ROM Manager to install a recovery to a separate partition.
Once you have an i9100 5.1 kernel downloaded on your phone you can flash it through the current recovery you have, then immediately reboot back into recovery. You'll then have the correct recovery and can proceed as normal with the ROM installation.
CWM absolutely has a backup/restore option, but it's hidden in a sub menu. My personal recommendation is to use TWRP recovery, as it's still being developed and is more robust/user friendly.
So as a general rule stay away from ROM Manager for system specific changes.
Thank you so much for the information/advice, I really do appreciate all of it.
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!