Related
Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).
SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .
zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.
I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.
Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.
Did you manage to fix it? I have the same probem.
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working
Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!
I do not have this device however I made these files for PETTYL users..
if you download it and it works, please hit the give THANKS button!
http://remainsilent.net/pettyl-twrp.img ------- fastboot flash recovery pettyl-twrp.img
http://remainsilent.net/pettyl-decrypt.zip TWRP ->> install ZIP ->> pettyl-decrypt.zip
I've instlled this "TWRP 3.2.1-moto-e5++-0" on Moto E5 XT-1920-16 (PETTYL) and works! Then successfully flashed Magisk 18.1 and now I have a root.
Thank you!
But now I have a problem. My phone tried to install OTA update and boot into Recovery to complete instalation. But because it's a TWRP the update can't be installed.
Now the phone only boot into TWRP. Can't start the system. Even on TWRP menu -> Reboot -> System then the phone boot again into TWRP. How to fix it?
Aalesund said:
I've instlled this "TWRP 3.2.1-moto-e5++-0" on Moto E5 XT-1920-16 (PETTYL) and works! Then successfully flashed Magisk 18.1 and now I have a root.
Thank you!
But now I have a problem. My phone tried to install OTA update and boot into Recovery to complete instalation. But because it's a TWRP the update can't be installed.
Now the phone only boot into TWRP. Can't start the system. Even on TWRP menu -> Reboot -> System then the phone boot again into TWRP. How to fix it?
Click to expand...
Click to collapse
You need kill the repeating OTA install sequence or, like you reporting, every time you boot into system, OTA installation get triggered and you get caught in the cycle. In TWRP menu, Mount System, go back main menu find your TWRP File Manager. Select System folder, Priv-App, find your OTA app (may be name 3C_OTA or something similar). Go ahead delete it if you don't plan on installing OTA on your device. You can also delete the OTA update zip package to stop your OS from continual trying to install it. In TWRP you need mount Cache, use TWRP File Manager again to open Cache directory, search for the OTA zip package and delete it.
whodat711 said:
I do not have this device however I made these files for PETTYL users..
if you download it and it works, please hit the give THANKS button!
http://remainsilent.net/pettyl-twrp.img ------- fastboot flash recovery pettyl-twrp.img
http://remainsilent.net/pettyl-decrypt.zip TWRP ->> install ZIP ->> pettyl-decrypt.zip
Click to expand...
Click to collapse
the links are dead i beg these files get re-uploaded please!!!!
TheLastAlphaUK said:
the links are dead i beg these files get re-uploaded please!!!!
Click to expand...
Click to collapse
You can get firmware for the xt1920 series PettyL from here https://mirrors.lolinet.com/firmware/moto/pettyl/official/
You can get custom recovery I built @ https://orangefox.tech
it should be all you need
TheLastAlphaUK said:
the links are dead i beg these files get re-uploaded please!!!!
Click to expand...
Click to collapse
Peetyl-[twrp+/decrypt zip
Can u reupload decrypt.zip?
Working recovery R9.0-3 on xt1920-16
i got this error C:\Users\GPS\Downloads\OrangeFox-R9.0-3-pettyl.zip: Unexpected end of archive. Using 7zip i extracted recovery.img and copied to external sd card and also to platform-tools folder. In fastboot i used "fastboot boot recovery.img" command , my phone booted to Orange recovery and there i used "Install Image" to flash recovery. If i try to flash downloaded zip file gives me an error Now i have working recovery and root (magisk 18.1) on E5 Play :victory:!
anyone still have pettyl-decrypt.zip? if so can you please upload it somewhere
Do someone have the pettyl-decrypt.zip?
In TWRP I cann't not find .Zip (/sdcard). What should I do?
Picture: https://uphinh.org/image/20200520-204525.uxojl7
wikiuse said:
In TWRP I cann't not find .Zip (/sdcard). What should I do?
Picture: https://uphinh.org/image/20200520-204525.uxojl7
Click to expand...
Click to collapse
TWRP is support MTP, you can use it
redymedan said:
TWRP is support MTP, you can use it
Click to expand...
Click to collapse
I know that but I can not find .ZIP file to flash module.
wikiuse said:
I know that but I can not find .ZIP file to flash module.
Click to expand...
Click to collapse
Hello,
Your files are still encrypted from when you came from the stock ROM.
Please flash the file that is attached to this reply in TWRP.
Help me,
After flash twrp and boot to twrp. I did fully wipe and flash multi-disabler.zip as introducetion.
Then flash magisk20.4.zip
1) at twrp, chose reboot => system. Phone boot successfully.
2) turn off phone, then boot to twrp, i choose reboot => recovery (to boot with magisk), got stuck on lock screen and alway reboot. (Bootlop)
How to fix my problem plz?
Hi,
Everytime I try to OTA update de weekly rom, I get the message that says that my memory is encrypted and directs me to recovery.
In recovery when I select the ROM, it returns ERROR 7, I know that it is related with 2 command lines in the updater script.
My question is, how can I fix this problems so I can normally OTA update?
Xiaomi MI 9 SE
TWRP 3.5.0_9-0
xiaomi.eu weekly (it happens in all versions)
Thanks
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
flairepathos.info said:
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
Click to expand...
Click to collapse
You're right, I think this is a generic problem, that's why I've not specified the model.
vmlc said:
You're right, I think this is a generic problem, that's why I've not specified the model.
Click to expand...
Click to collapse
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
flairepathos.info said:
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
Click to expand...
Click to collapse
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
vmlc said:
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
Click to expand...
Click to collapse
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
flairepathos.info said:
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
Click to expand...
Click to collapse
So this is not fixable, keep TWRP and have OTA update?
vmlc said:
So this is not fixable, keep TWRP and have OTA update?
Click to expand...
Click to collapse
Yes but now that you mention if you could edit the twrp recovery_id to match that of the stock recovery ,it might work because the system/ ota file calls for a specific recovery_id