Hi sorry if i post in bad section so i need help i downloaded an CWM ClockWorkMod Recovery for SM-G318H Samsung Galaxy Trend 2 lite i apply the update so it was almost done but an error marked in red and reboot after update failure.
Any suggestion it happens with any zip file for Temp Recovery i have here an picture :crying:
I Attached an picture with the failure so if you have any suggestion reply there.
P.S. I Don't trust changing permanent recovery and even download mode odin.
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Flashing CWM on stock recovery
jwoegerbauer said:
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Click to expand...
Click to collapse
This i know so i try flashing the CWM so this not work so to sign the custom recovery with signed stock rom so how i fix thanks for replying
@AlinTecsan
Look inside here.
Looked Here
jwoegerbauer said:
@AlinTecsan
Look inside here.
Click to expand...
Click to collapse
I Looked here so fastboot it flash and erase sorry so my phone will not support the advanced boot options and no match found for my model at all so thanks again for the link
Use TWRP instead of CWM
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
TWRP Will work for my device?
jwoegerbauer said:
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
Click to expand...
Click to collapse
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
AlinTecsan said:
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I Flash an 2.8.7.0 TWRP
jwoegerbauer said:
Click to expand...
Click to collapse
It work fine so i need to change to red if possible so work good so i sent pictures soon I like to know how i restore the stock recovery i backup the whole firmware so i like to change to red .TWRP Work with all devices?
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Stock ROM And recovery
jwoegerbauer said:
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Click to expand...
Click to collapse
I have to say i extract from my correctly firmware code the recovery.img so i will made an tar file or i guess to restore recovery stock in case of problem so i know with .tar.md5 backups.
Related
Hi,
I have a Lenovo A516 rooted. I deleted some Lenovo pre-installed files that made my phone unstable and now it's stuck in boot.. I can get into my Android System recovery but what can I do from here? Can I try loading a custom ROM or should I find Lenovos factory ROM and load that?
This is my first time using Android System Recovery.
Help is greatly appreciated! I just bought this phone! :crying:
at system recovery can I try wipe data/factory reset or wipe cache partition?
I'm guessing I should install the ideafriend APK in recovery mode or ADB?
Sojuncoke said:
I'm guessing I should install the ideafriend APK in recovery mode or ADB?
Click to expand...
Click to collapse
Does anyone have instructions to install APK files in recovery without going into the phone and turning on developer mode?
Sojuncoke said:
Does anyone have instructions to install APK files in recovery without going into the phone and turning on developer mode?
Click to expand...
Click to collapse
I'm guessing I'm screwed?
Sojuncoke said:
I'm guessing I'm screwed?
Click to expand...
Click to collapse
Probably.
Do you have a custom recovery? If so I can probably create a flashable zip to get the APK back.
jerbear294 said:
Probably.
Do you have a custom recovery? If so I can probably create a flashable zip to get the APK back.
Click to expand...
Click to collapse
Hey Thanks for the reply. Yes I can get into my recovery by pressin power and volume buttons. And I did find the apk files i deleted. I am in the process of making a zip file out of them. Do I choose "update from SD Card" in recovery mode?
Sojuncoke said:
Hey Thanks for the reply. Yes I can get into my recovery by pressin power and volume buttons. And I did find the apk files i deleted. I am in the process of making a zip file out of them. Do I choose "update from SD Card" in recovery mode?
Click to expand...
Click to collapse
Is this a custom recovery or is it the stock recovery? You might get license errors if you are on the stock recovery.
EDIT: It seems there isn't a custom recovery for your device- Am I correct? That makes things harder.
jerbear294 said:
Probably.
Do you have a custom recovery? If so I can probably create a flashable zip to get the APK back.
Click to expand...
Click to collapse
Looks like I am having trouble with the zip file because it says installation aborted.
jerbear294 said:
Is this a custom recovery or is it the stock recovery? You might get license errors if you are on the stock recovery.
EDIT: It seems there isn't a custom recovery for your device- Am I correct? That makes things harder.
Click to expand...
Click to collapse
Yeah I never installed a custom recovery. So I guess its a stock recovery huh?
this is all it says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sojuncoke said:
this is all it says
Click to expand...
Click to collapse
Yep, that's the stock recovery. You can try the zip you're making but you might get a signature verification later.
Hello there.
A couple of months back my friend was having trouble with her S3 and she had to reset e every couple of days. So I instructed her to install Cyanogenmod via the official installer. She did and it worked.
A few days back she told he it won't update and I guessed that it won't for the lack of CWM so I told her to get Rashr from the Play Store and flash a custom recovery, which she did successfully. Even though the phone wouldn't update anyway.
So last night she told me that her phone stopped booting up completely. When booting to recovery and trying to flash a zip through CWM doesn't work because it keeps telling her "E: no sd card" or something like that. Now she doesn't have an SD card, but my understanding is that this refers to the internal storage too. So why can't the recovery read it?
Furthermore I tried to get her to flash another recover via Odin, but Odin fails to flash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have no idea what to do now. Do you guys know what could be going wrong?
Mr0nLine said:
Hello there.
A couple of months back my friend was having trouble with her S3 and she had to reset e every couple of days. So I instructed her to install Cyanogenmod via the official installer. She did and it worked.
A few days back she told he it won't update and I guessed that it won't for the lack of CWM so I told her to get Rashr from the Play Store and flash a custom recovery, which she did successfully. Even though the phone wouldn't update anyway.
So last night she told me that her phone stopped booting up completely. When booting to recovery and trying to flash a zip through CWM doesn't work because it keeps telling her "E: no sd card" or something like that. Now she doesn't have an SD card, but my understanding is that this refers to the internal storage too. So why can't the recovery read it?
Furthermore I tried to get her to flash another recover via Odin, but Odin fails to flash
I have no idea what to do now. Do you guys know what could be going wrong?
Click to expand...
Click to collapse
Seems ok from what i can see. Maybe rookie mistake, usb debbuging on?
if it is on then you need to flash stock rom and root again.
andjeomilosrdja said:
Seems ok from what i can see. Maybe rookie mistake, usb debbuging on?
if it is on then you need to flash stock rom and root again.
Click to expand...
Click to collapse
Thanks for your response.
To be honest I'm not sure if it's on or not since the device isn't booting up anymore.
How can I flash the stock Rom from recovery when it can't even see the storage?
Mr0nLine said:
Thanks for your response.
To be honest I'm not sure if it's on or not since the device isn't booting up anymore.
How can I flash the stock Rom from recovery when it can't even see the storage?
Click to expand...
Click to collapse
By going into download mode , power,volume down and menu button
You needed to be in download mode for flashing recovery also,right?
Mr0nLine said:
Thanks for your response.
To be honest I'm not sure if it's on or not since the device isn't booting up anymore.
How can I flash the stock Rom from recovery when it can't even see the storage?
Click to expand...
Click to collapse
You can't you need odin to flash any stock rom not a recovery.
Can you still get into download mode? If so try to flash a full stock rom from Sammobile with odin if that fails try the emergency recovery here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
It has reached me a Mate 10 Lite with error when unlocking the Bootloader ... once made it sends you to the custom recovery TWRP but it shows in its description that they wipe the system and do not load it, I have tried to recover with backups uploaded by other users but it does not ... someone has gone through this ... and what suggestion they give ... The same does not allow to install the Stock recovery, to use the file update.app ... Nor does it allow to i
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nstall other types of recoverys.
Try a different twrp that has helped me kingmezi is working for my but keep in mind you need to format data (and check the mount setting and swipe to modify at start)
Thks
KOALAaufPILLEN said:
Try a different twrp that has helped me kingmezi is working for my but keep in mind you need to format data (and check the mount setting and swipe to modify at start)
Click to expand...
Click to collapse
Thanks for the answer, but it does not allow as the previous message says ... it does not allow to install any type of recovery either stock or custom ...
It does not allow to mount any partition, Boot, Recoery, etc ... from the TWRP Menu
Unlock bootloader install via command
thks
I do not think I'm spying.
1. The Bootlaoder even if it is released ... it sends you immediately to the TWRP ... once inside it says no OS installed, and it does not allow doing anything because it does not load any of the partitions.
2. Even if you release the Bootloader, it does not allow you to install another type of TWRP ... nor restore backup files ... it only allows you to flash the different OEMINFOs as if it were a rebrand.
KOALAaufPILLEN said:
Unlock bootloader install via command
Click to expand...
Click to collapse
Then you might try dc phoenix but its not free
That can install even if you have a locked bootloader firmware or even if you are bricked like your cellphone
you can download the latest firmware without problems googe it and try it (cost about 15dollar to unbrick)
If the twrp dont work cause the parameters are wrong what twrp are you using we have here 3 differents for the Huawei if im right try kingmezi twrp its working fro my l21-b432 i think it was
Thks
I managed to install another custon recovery, that allows to see the partitions, and that the team has a system ... but at the time of restart the bootloader error comes out ... and giving low CMD fastboot has the same unlocked ... perfect ... when I send the command fastboot flash (Boot, recovery, recovery2) it says Failed ... and I can not install the recovery stock.
P.S: Thanks for the advice of DC Phoenix ... I had seen it and I will try ...
KOALAaufPILLEN said:
Then you might try dc phoenix but its not free
That can install even if you have a locked bootloader firmware or even if you are bricked like your cellphone
you can download the latest firmware without problems googe it and try it (cost about 15dollar to unbrick)
If the twrp dont work cause the parameters are wrong what twrp are you using we have here 3 differents for the Huawei if im right try kingmezi twrp its working fro my l21-b432 i think it was
Click to expand...
Click to collapse
solved?
hi men, please you can solved this?, i have de same problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OFFICIAL DOWNLOADS FOR SUZU:
https://twrp.me/sony/sonyxperiax.htmltwrp-3.x.x_x-x-suzu.img: Official TWRP image
DEVELOPMENT DOWNLOADS FOR SUZU:
Folder: https://sourceforge.net/projects/loire-development/files/twrp-recovery/suzu/twrp-3.x.x_x-x-YYYYMMDD-suzu.zip: Flashable unofficial TWRP to FOTAKerneltwrp-3.x.x_x-x-YYYYMMDD-suzu.img: Unofficial TWRP image
INSTALLATION
MANUALLY TO FOTAFastboot: Adapt the image name and install this way:fastboot flash recovery twrp-3.x.x_x-x-suzu.imgfastboot rebootFROM EXISTING RECOVERY
Enter to the current recovery
Install flashable TWRP
Reboot/Power off
HOW TO ENTER TO THE RECOVERY:
Power off your phone
Press Power and Vol- buttons at the same time until vibration
Wait for TWRP load
Sources:
TWRP device tree: https://github.com/TeamWin/android_device_sony_suzu/tree/android-9.0Kernel: https://github.com/Chippa-a/kernel-copyleft/tree/34.4.A.2.xxxThanks to the TWRP Team!
Backup-Restore function working fine so far, only issue I am seeing is phone is heating up pretty faster than before while backing up in compression mode.
Another minor thing is that earlier when entering recovery mode a purple light used to blink, now its missing.
Just saw this now and I'm really grateful. Big ups to you, man. Great work.
And I was afraid there would be no 3.2.1 for this device;
@Chippa_a makes it possible - intensified thanks! :highfive::good::good:
Thank you!!
I can't flash the zip because twrp does not give access to that part of the storage, weird.
fusk said:
I can't flash the zip because twrp does not give access to that part of the storage, weird.
Click to expand...
Click to collapse
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Updated from TWRP, backup/restore works, no problems so far apart from it needs more than a minute till TWRP GUI appears after boot. Thanks for update.
Do you use the stock kernel? I installed the recovery built by oshmoun in the omnirom thread. It uses the aosp kernel. It starts faster, has a better sdcard naming and can flash oem images. Maybe you could try this kernel.
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
I mean the kernel used with the recovery, not the rom kernel.
I_am_Blackford said:
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Click to expand...
Click to collapse
This is what i did. Download img, place file on phone. Download twrp app, pick choose a file, browse to recovery.img, flash. Power off, boot to recovery = win.
Reboot to system, retry installing new update = great success.
mase76 said:
I mean the kernel used with the recovery, not the rom kernel.
Click to expand...
Click to collapse
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
privatim said:
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
Click to expand...
Click to collapse
I dont know if there is a connection, but i've tested the recovery with OmniROM 7.1.2, where display is not responding. It can be installed, shows 3.2.1, but display remains dead 4 touch.
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
mase76 said:
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
Click to expand...
Click to collapse
Same result, whether fastboot or flashtool, display is dead.
Certainly missed ODM LOIRE v12, v11 is installed.
Not really sure is the latest bootloader.
Does restoring a backup change the bootloader as well?
Edit: Solved: the answer is 'yes'.
3.2.1 does not work @7.1.2 restore because of outdated bootloader.
privatim said:
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
Click to expand...
Click to collapse
Moved to XGEN ROM and now TWRP starts without delay. :good:
privatim said:
Moved to XGEN ROM and now TWRP starts without delay. :good:
Click to expand...
Click to collapse
What I do not understand, maybe bootloader or encryption, but why is 3.2.1 not backwards compatible on Suzu?
Is Omni 7.1.2 kernel (more I have not tried) or not current boot loader the reason?
Installed on last nougat internal storage 0 help
Inviato dal mio F5121 utilizzando Tapatalk
I'm glad that you finally managed to crack this damn decryption. I felt really bad with my broken promise of delivering the working build. I'm sorry, guys. @Chippa_a congratulations on your hard work
I just want to finally try and install a custom rom into my Mi A3 which I rooted a while ago. I know I need this tool called TWRP, after encountering a myriad of errors trying to follow this guide step-by-step, I finally got to the point when I need to type "fastboot boot twrp.img" to boot into TWRP temporarily. But alas that couldn't be so easy now could it... Now I get this thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it's 11:41 PM and I'm about to burst a vein. I made an account solely to make this post because I can't seem to get an actual answer anywhere else... Any ideas before I give up?
is the bootloader unlocked ?
i think i got same message and it was because i forgot this.
I think there are better guides. Not sure what state your system is in. I would re-install the stock rom and start afresh. Unlock your bootloader, check which slot 'a' or 'b' is the current slot, and then follow the instruction of the Custom ROM you are trying to install. It might need TWRP but Lineage Recovery is equally as good.
#1jonna said:
is the bootloader unlocked ?
i think i got same message and it was because i forgot this.
Click to expand...
Click to collapse
Yes sir it very much is, don't think it'd have been possible to get this far otherwise
bjlabuk said:
I think there are better guides. Not sure what state your system is in. I would re-install the stock rom and start afresh. Unlock your bootloader, check which slot 'a' or 'b' is the current slot, and then follow the instruction of the Custom ROM you are trying to install. It might need TWRP but Lineage Recovery is equally as good.
Click to expand...
Click to collapse
how do I do this?
2. does Lineage Recovery even work on Mi A3s? I don't find anything about this device on their website
Follow the guide in the thread 'Slot A is destroyed'.
bjlabuk said:
Follow the guide in the thread 'Slot A is destroyed'.
Click to expand...
Click to collapse
I assume this means I can just go back to magisk and hit restore images, then return to fastboot and switch to slot b and install twrp there?
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ said:
View attachment 5554333
I assume this means I can just go back to magisk and hit restore images, then return to fastboot and switch to slot b and install twrp there?
Click to expand...
Click to collapse
As I said, as I am not sure what state your system is in I would suggest 're-installing' the stock rom from your PC, rather than 'restoring' an image from your phone. If you have backed up your data etc (eg on Google Drive) you can restore it after you have re-installed the stock rom. You can then start again from scratch.
The latest stock rom fastboot images can be found here
https://xiaomifirmwareupdater.com/miui/laurel/
Tbh I haven't restored an image from magisk myself so I can't confirm what you are proposing, though yes I switched to slot b and installed TWRP.
You might also want to read this article on A/B partitions
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Try this
https://play.google.com/store/apps/details?id=com.smartpack.smartflasher
Flash TWRP installer through the app
Just a few tips when you do get to TWRP:
Disable dm-verity
Format data and wipe cache after you flash the new rom before first boot
Use a patched boot method instead of flashing magisk in TWRP on custom ROMs. High chance of soft brick.
DM me if you need help.