Getting a bit bogged down here. I managed to get TWRP installed, my first question is how to change the language. Next question is if I format data, will the encryption be gone?
invisiblewave said:
Getting a bit bogged down here. I managed to get TWRP installed, my first question is how to change the language. Next question is if I format data, will the encryption be gone?
Click to expand...
Click to collapse
Google how to change language, easier to follow with pictures.
And yes it will remove encryption
Thanks for the speedy reply, this it turning into a bit of a nightmare. You have to be quick on the buttons to get TWRP to stick. After installing the ROM, do I have to reboot to recovery before system? The first time it booted back to what appeared to be the original stock rom. I'm trying again now in English, which might help....
Whatever I do, it seems to always boot back to the stock rom. WTF am I missing?
Mackay53 said:
Google how to change language, easier to follow with pictures.
And yes it will remove encryption
Click to expand...
Click to collapse
After install, it boots to the original ROM, then rebooting to recovery goes to MiRecovery, I have to reflash TWRP (even after rebooting to TWRP) but it remembers the language settings. Do I have to install, then reboot back to TWRP or something, before booting to system?
Hot damn, that was a trial! I think I'm finally running the eu rom with Magisk!
Related
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
I have Cyanogenmod recovery so that updates auto install. I downloaded the 20151005 update, and hit install. Things went fine until the part where apps optimize. It would finish, then show the Cyanogenmod boot logo for a few minutes and restart optimizing, over and over. I tried downloading the update on my computer and putting it on my SD card to see if it was just the download was messed up, and it did the same thing. I downloaded a previous update the same way, because my phone can't boot into android, and it did the same thing again. So now I want to get TWRP to see if the recovery is the problem, but I don't know how. That's where your help comes in. (hopefully!) Or, if there is a way to fix this without that, that would be preferable. And yes, I already wiped the media partition, cache partition, and did a data/factory reset, which are the only things I can wipe in Cyanogenmod recovery.
Hi
Thank you for using XDA Assist.
Here you go
http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
TWRP is better recovery. I do recommend it
Yes, I agree. But if you read my post, or at least understood it fully, you would know that I was asking how to install TWRP from the Cyanogenmod Recovery. It only lets you flash Cyanogenmod update zips, and it replaces the stock bootloader as well, so I don't know if the regular ADB method of flashing TWRP will work. I can't break this phone, you see.
MatreyuC said:
Yes, I agree. But if you read my post, or at least understood it fully, you would know that I was asking how to install TWRP from the Cyanogenmod Recovery. It only lets you flash Cyanogenmod update zips, and it replaces the stock bootloader as well, so I don't know if the regular ADB method of flashing TWRP will work. I can't break this phone, you see.
Click to expand...
Click to collapse
I guess you can since CM Recovery is almost a stock recovery.
Since you have 10 posts now, you can directly have a confirmation by posting in the above thread.
I didn't know where to post this so i am posting it here.
I tried to flash the latest version of CrDroid some hours ago and although the installation began with no errors, the whole thing got stuck on an infinite installation of the ROM. The log displayed "Patching system image unconditionaly."
After about 30 minutes i just lost faith and held down power button to force a reboot. Then, TWRP got reset to the screen which you see when you first flash TWRP, the one ascing about wether to keep system read only or not.
I will post screenshots too as soon as i figure out how to do it
.
Set it back to RW mode from RO mode. If it constantly turns back to RO, try reflashing the recovery image.
If you are lucky enough to abruptly abort a ROM installation, you will be able to atleast use the device. I had aborted a nandroid restore and my entire data partition was corrupted.
In any case you should post it in the appropriate ROM thread.
Make sure system is mounted writable, wipe system, data, and caches, and flash... it's that simple. If it fails use another ROM.
BTW, it is usually useful to tell which device (specifically), what ROM/Gapps, what version of TWRP, etc... the devil is usually in the details, the more the better.
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
mike.... said:
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
Click to expand...
Click to collapse
Weird... We can pretty much guarantee nothing is working in TWRP though, or at least it's not processing even the boot image of your ROM or the device wouldn't boot.
What is bootloader status?
Hello everyone,
I don't know much about partitions but I know something is not right with mine
So, A few days ago my phone got bricked because I flashed crDroid rom. (I did something wrong)
So, after a lot of research, I found an solution to unbrick my phone. So it worked, I booted into software again and I was free to use.
So later, I decided to install an custom rom again (Havoc OS). I installed the rom but after I clean flashed the rom, I got stuck on booting logo.
So, I thought lets see what partition B does. So I booted into partition B and I got stuck on the logo of TWRP. Not sure why.
I really wanna know why this happend and how to fix my device.
(Btw, now my phone is working again and I am on stock os with rooted using Magisk 16,7.)
But just wanna know what I did wrong
I used the instruction in this thread: https://forum.xda-developers.com/oneplus-6/development/enchilada-romcrdroid-t3827070. And after I did that it got bricked.
I hope anyone knows what happend and how to fix my partition!
Friendly regards,
Crewz
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
whizeguy said:
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
Click to expand...
Click to collapse
I did the exact steps as in the thread.
ItsCrewz said:
I did the exact steps as in the thread.
Click to expand...
Click to collapse
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
iElvis said:
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
Click to expand...
Click to collapse
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
ItsCrewz said:
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
Click to expand...
Click to collapse
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
iElvis said:
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
Click to expand...
Click to collapse
Yes I know what it means. But it isn't normal that it boots into twrp and get stuck on the logo
I'm using a Custom Rom but when there-'s an update I download the new Rom, using OTA process. It enters in the recovery but I can't update it. What is wrong? If i Try making a dirty flash inside the recovery my Smartphone gets encripted. Can someone help me?
For many custom ROMs, the so-called OTA is just using recovery to dirty flash what OTA downloaded and everything should be Okay. I never found my data gets encrypted after the update. Maybe u could check the log if there's some update that needs a clean flash.
You had you rom flashed with DFE?
If yes you need to flash DFE zip after rom before booting.
Anyway it's supposed a rom encrypt data, but if recovery can't decrypt data you going for a bad time, last twrp has working decryption ...
Or you talking about something else?
Please provide more details....
As the first reply said, at least in the Roms I use, it just downloads the zip, reboots in twrp and flashes it. It worked pretty good in Havoc-Os
TioCareca said:
You had you rom flashed with DFE?
If yes you need to flash DFE zip after rom before booting.
Anyway it's supposed a rom encrypt data, but if recovery can't decrypt data you going for a bad time, last twrp has working decryption ...
Or you talking about something else?
Please provide more details....
Click to expand...
Click to collapse
I'l try to explain in details what my problem is.
I was on Havoc 4.8 and the 4.9 came out. I entered config, selected System and Update. It showed me the new Rom to download. That's what I did. It was downloaded perfectly and then asked me to continue. Só I pressed the button and it entered TWRP (35.2 Nebrasy) and there I was. Stopped in recovery and no other process was going on. Should I have chosen Install, the rom (probably in download folder)?
I was thinking it should have done the whole process autmaticaly, as it always did using Miui Rom.
So, that's my problem. Thanks for your help.
Fmeyen said:
I'l try to explain in details what my problem is.
I was on Havoc 4.8 and the 4.9 came out. I entered config, selected System and Update. It showed me the new Rom to download. That's what I did. It was downloaded perfectly and then asked me to continue. Só I pressed the button and it entered TWRP (35.2 Nebrasy) and there I was. Stopped in recovery and no other process was going on. Should I have chosen Install, the rom (probably in download folder)?
I was thinking it should have done the whole process autmaticaly, as it always did using Miui Rom.
So, that's my problem. Thanks for your help.
Click to expand...
Click to collapse
If your phone is not encrypted, then I don't think that the automatic OTA update (which uses an openrecovery script) will run. You will need to install the update manually, and your device will probably be encrypted when the ROM boots (unless you disable forced encryption).
DarthJabba9 said:
If your phone is not encrypted, then I don't think that the automatic OTA update (which uses an openrecovery script) will run. You will need to install the update manually, and your device will probably be encrypted when the ROM boots (unless you disable forced encryption).
Click to expand...
Click to collapse
When I install the new custom rom i usually flash DFE. So, by your words, it is not encrypted. If so, I'll run it manually as I prefer not to have an encrypted rom. Thanks for your support.
Could you please explain the correct steps to make a proper dirty flash in X3P? Asking this 'cause this smartphone needs a format data.