Hi, i hv not been successf intalling twrp img for my redmi 6a global v10.2.8.0(ocbmixm) using twrp v3.3.0 -0 cactus -v3.2.3-0 cactus. Fastboot show no error. Bootloader is unlock.
{
"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"
}
tomtombak said:
Hi, i hv not been successf intalling twrp img for my redmi 6a global v10.2.8.0(ocbmixm) using twrp v3.3.0 -0 cactus -v3.2.3-0 cactus. Fastboot show no error. Bootloader is unlock.
Click to expand...
Click to collapse
How did you proceed ?
tomtombak said:
Hi, i hv not been successf intalling twrp img for my redmi 6a global v10.2.8.0(ocbmixm) using twrp v3.3.0 -0 cactus -v3.2.3-0 cactus. Fastboot show no error. Bootloader is unlock.
Click to expand...
Click to collapse
how many you've been tried??
i'm 10 times maybe more.... :laugh::laugh::laugh::laugh::laugh::laugh: until i cant remember... :laugh::laugh::laugh:
@ Adista :HV tried twrp cactus from v3.3 to 3.2 all. what version of rom and twrp ar you using. @Ryu--X using adb fastboot methods:
"C:\adb>adb devices
List of devices attached
xxxxxxxxxxxd29 device
:\adb>fastboot flash recovery twrp-3.3.0-0—cactus.img
target reported max download size of 134217728 bytes
sending 'recovery' (17040 KB)...
OKAY [ 0.547s ]
writing 'recovery' ...
OKAY [0.391s]
finished. total time:. 0.953s
:\adb>fastboot flash recovery twrp-3.2.3-2—cactus.img
target reported max download size of 134217728 bytes
sending 'recovery' (16982 KB)...
OKAY [ 0.547s ]
writing 'recovery' ...
OKAY [0.375s]
finished. total time:. 0.922s
C:\adb>"
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Binbin Qian said:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
You don't need this, install the TWRP-3.0.3.0 OMFG mod or the LR-Team one and then use the "Sign Boot" patch...
I had a problem of recovery replacement, it happened to me after installing TWRP and rebooting the phone. This is what I was doing:
- Installed TWRP.
- Reboot phone.
- Keep volume up + power booting while rebooting.
- Recovery overwritten automatically.
My mistake was to keep the power button pressed after the first vibration. Therefore, while rebooting when you feel the vibration release the power button and wait for TWRP to start. Just in case, in my phone after releasing the power button it kept in black screen, if you have this, just press once the power button.
tomtombak said:
@ Adista :HV tried twrp cactus from v3.3 to 3.2 all. what version of rom and twrp ar you using. @Ryu--X using adb fastboot methods:
"C:\adb>adb devices
List of devices attached
xxxxxxxxxxxd29 device
:\adb>fastboot flash recovery twrp-3.3.0-0—cactus.img
target reported max download size of 134217728 bytes
sending 'recovery' (17040 KB)...
OKAY [ 0.547s ]
writing 'recovery' ...
OKAY [0.391s]
finished. total time:. 0.953s
:\adb>fastboot flash recovery twrp-3.2.3-2—cactus.img
target reported max download size of 134217728 bytes
sending 'recovery' (16982 KB)...
OKAY [ 0.547s ]
writing 'recovery' ...
OKAY [0.375s]
finished. total time:. 0.922s
C:\adb>"
Click to expand...
Click to collapse
im on global rom 10.2.8 and all 3.2/3.3 twrp with no luck..
now im trying on rom 10.3.2 global rom and still searching unofficial twrp for cactus. @jonaaa said that unofficial would be better, even it start with chines language. :laugh:
jonaaa said:
You don't need this, install the TWRP-3.0.3.0 OMFG mod or the LR-Team one and then use the "Sign Boot" patch...
Click to expand...
Click to collapse
Where did you find LR Team for 6a? Or the omfg mod, can't find anywhere.
How to fix?
Hey, if you updated MIUI to Android Pie, install this recovery (includes the batch install file), 100% no bootloops.
Just reboot into fastboot, run the batch file and that's it.
https://drive.google.com/file/d/1gjD_MYakltiRLtwgTyS9oAvQQNeOHGYg/view
Hope I helped.
rond14 said:
I had a problem of recovery replacement, it happened to me after installing TWRP and rebooting the phone. This is what I was doing:
- Installed TWRP.
- Reboot phone.
- Keep volume up + power booting while rebooting.
- Recovery overwritten automatically.
My mistake was to keep the power button pressed after the first vibration. Therefore, while rebooting when you feel the vibration release the power button and wait for TWRP to start. Just in case, in my phone after releasing the power button it kept in black screen, if you have this, just press once the power button.
Click to expand...
Click to collapse
Hey man, i got exectly what u said. After fastboot i pressed power key and volume up, unitill i heard vibration. Than i relased power key, still volume up key, and got mi sign. Than black screen, and after that when i press power key, phone just turned on instead going into recovery...
Gvex95 said:
Hey man, i got exectly what u said. After fastboot i pressed power key and volume up, unitill i heard vibration. Than i relased power key, still volume up key, and got mi sign. Than black screen, and after that when i press power key, phone just turned on instead going into recovery...
Click to expand...
Click to collapse
Hi, it's tricky, that's the reason I use a different procedure now, you can follow it as it worked for me:
https://runakay.blogspot.com/2020/03/installing-twrp-recovery-in-xiaomi.html
Related
This is a Custom CWM-Based Recovery 5.0.2.7 for HTC JetStreamCredits and special thanks to Koush and everyone else involved in Cyanogenmod project!
so even tough i dont have this device with me i have got ROOT access and custom RECOVERY for you guys!
{
"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"
}
[ info ]
This Recovery can be flashed directly to the /recovery partition of the device and will give you lots of features!!!
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
FreeXperia Team for too many things
special thanks to bmw-boy for helping out with testing and risking his device for the sake of development!!! and NO, his device was NOT damaged during testing
ME for creating this for u guys!
[ Requirements ]
Bootloader unlocked
working fastboot
[ features ]
features derived from CWM5
ability to backup & restore to/from internal SDCARD
ability to flash custom update.zip from internal SDCARD
faster .TAR backups
my additions
changes to graphics (ported some graphics from CWM5.5 ICS edition)
revamped layout for recovery menu (to improve navigation) [renamed few options and changed their order]
changed "wipe data/factory reset" option to just "factory reset", and detailed the partitions which will be wiped
added reboot options
reboot into system
reboot into recovery
reboot into fastboot mode
some modification in "Partition SDCard" section:
put up a confirmation to warn the user that this option will wipe sdcard
added ability to select filesystem when creating new layout
add confirmation to "backup" option in Nandroid menu... it used to keep getting pressed by mistake and start making backups immediately... now it will ask u before starting backup
removed tons of "NO"s from some menus...
u can now flash to /boot /recovery & radio partitions
[ WARNING ]
THIS RECOVERY IS STILL IN TESTING... MAKE SURE THAT U HAVE UR COMPLETE DATA BACKED-UP (INCLUDING SDCARD DATA)...
and incase this doest work correctly make sure that u can restore to factory condition...
"Partition SDCard" option in CWM5 WILL WIPE UR EXTERNAL SDCARD!!!
we have tested this to work on the US version of HTC JetStream (but i think it will work on the Canadian version too)
[ how to flash this recovery ]
download the recovery image
reboot device into fastboot mode
Code:
adb reboot bootloader
now flash the recovery using
Code:
fastboot flash recovery filename.img
[where filename.img is the name of the recovery image u downloaded]
thats it!
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ download links ]
[JetStream] CWM-Based Recovery 5.0.2.7 by DooMLoRD v02 < NEW >
MD5HASH: d0454eec0c7787992b1cdaef41ca0248
[JetStream] CWM-Based Recovery 5.0.2.7 by DooMLoRD v01 (OLD)
MD5HASH: b74c3b3e13c8801636794e0019c214f5
KINDLY DO NOT MIRROR MY FILES
please do intensive testing and let me know!
enjoy!!!
reserved for later
thanks for your great effort bro together
@MODS
may be u can sticky this?
sure!
Wondermous!
anyone else tried this?
will it factory-reset the device?
I have try most of the functions and are working
My bootloader is unlocked and device rooted, but when i try to flash recovery in fastboot , i get this:
sending 'Recovery' (4986 KB)... OKAY
writing 'Recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Does anyone know what i did wrong?
Daniehabazin said:
My bootloader is unlocked and device rooted, but when i try to flash recovery in fastboot , i get this:
sending 'Recovery' (4986 KB)... OKAY
writing 'Recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Does anyone know what i did wrong?
Click to expand...
Click to collapse
fixed it by re rooting, maybe it didn't like that i did a factory reset between my rooting and attempt to flash recovery.
Working - Confirmed !
Flashed as instructed - worked 1st time.
Thanks !
howdy,
in one of the posts i read someone mention a howto, can somone direct me the howto for installing CWM to my jetstream?
thanks in advance
cheers,
disco
first page of this thread?
I did a backup from recovery mode and chose to backup to the sd card. Where is the location of this backup? I think it may be /sdcard/clockworkmod/backup but I wanted to make sure. Any input would be greatly appreciated. Thanks.
scitech09 said:
I did a backup from recovery mode and chose to backup to the sd card. Where is the location of this backup? I think it may be /sdcard/clockworkmod/backup but I wanted to make sure. Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Yes it will be at :
/sdcard/clockworkmod/backup
Or
/sdcard/ext_sd/clockworkmod/backup
Or
/sdcard/external_sd/clockworkmod/backup
Sent from my HTC Flyer P510e using XDA App
what would "factory reset" in the recovrey menu do to the device? will it void the root and recovery?
and what about hard-reset (buttons combo)?
i'm having crashes for a while and i'm considering theas steps, but i'm a bit scared of the consequences.
Thanks for the hard work on this one, will download and give it a go!
guru_shastri said:
what would "factory reset" in the recovrey menu do to the device? will it void the root and recovery?
and what about hard-reset (buttons combo)?
i'm having crashes for a while and i'm considering theas steps, but i'm a bit scared of the consequences.
Click to expand...
Click to collapse
it will format a few partitions... list is shown before wiping...
no idea abt hard reset
updated recovery to v02 thanks to ATT Intruder for the partition map
[ changelog ]
now u can flash to /boot, /recovery and radio partitions
so u can now flash custom kernels using recovery
[ EXPERIMENTAL ]
WARNING: DO THIS ONLY IF U KNOW HOW TO REVERT BACK TO STOCK/FACTORY SETTINGS
if someone is willing to test see if u can flash radio using this new recovery
do test out and let me know if u run into any issues
regards,
DooMLoRD
DooMLoRD said:
updated recovery to v02 thanks to ATT Intruder for the partition map
[ changelog ]
now u can flash to /boot, /recovery and radio partitions
so u can now flash custom kernels using recovery
[ EXPERIMENTAL ]
WARNING: DO THIS ONLY IF U KNOW HOW TO REVERT BACK TO STOCK/FACTORY SETTINGS
if someone is willing to test see if u can flash radio using this new recovery
do test out and let me know if u run into any issues
regards,
DooMLoRD
Click to expand...
Click to collapse
Can't test it there's not kernel yet developed or roms to do so
I'm more than welcome to start developing or mod the actual rom but, not that cool I am jiji.
{
"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"
}
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: twrp-montana-3.2.3.0.img
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2 @lohanbarth
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.3-0
Stable Release Date: 2018-10-08
Created 2018-07-05
Last Updated 2018-10-08
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
lohanbarth said:
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Source Code:
Github
Contributors
@[email protected]@[email protected]
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.2-0
Stable Release Date: 2018-07-05
Created 2018-07-05
Last Updated 2018-07-05
Click to expand...
Click to collapse
Support on Arm64 rom's?
Adamask said:
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
Click to expand...
Click to collapse
go to wipes and click on data format.
rssxda said:
Support on Arm64 rom's?
Click to expand...
Click to collapse
Yes
twrp 3.2.3 in op.
after wipe data and reboot the phone twrp is not there
Cesarcami53 said:
after wipe data and reboot the phone twrp is not there
Click to expand...
Click to collapse
it's normal you have to flash a .zip file so that it stays
Where is the twrp zip..??
Hello ! guys ... I'm without pc can I flash it for this app?
zanduo said:
Hello ! guys ... I'm without pc can I flash it for this app?
Click to expand...
Click to collapse
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
I have root and twrp and bootloader .... the problem and that I am without pc ...
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
Thanks man i use flasify And Works! Thanks ! Now i waiting for 64 roms
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
RuKlowd said:
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
Click to expand...
Click to collapse
flash a .zip file (magisk or a custom rom) to fix it
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
lohanbarth said:
flash a .zip file (magisk or a custom rom) to fix it
Click to expand...
Click to collapse
Thanks, it worked! So the recovery partition won't really (permanently) flash unless you root the device, right? Do I always need to root to permanently flash any other partition, too?
ilovepanda said:
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
Click to expand...
Click to collapse
Sorry, I had difficulties to understand you :/
if you make a backup, the backup will also add the recovery stock, so when restoring, it will also restore the backup of the recovery stock, it would be better to install the stock and before the first boot, install the twrp via .img
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
PhoenixGamer said:
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
Click to expand...
Click to collapse
You can
{
"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"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1 . Download twrp-3.4.0-0-PL2_sprout.img & twrp-installer-3.4.0-0-PL2_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-PL2_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 11 Twrp-3.4.0-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 6.1
Contributors
Raghu varma
Source Code: https://github.com/Nokia-SDM660/android_device_nokia_PL2_sprout-TWRP
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2020-06-25
Created 2020-06-25
Last Updated 2020-06-25
Changelog - Thu Jun 25 12:41:03 UTC 2020
================================
* https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Great work bro
This can work with locked bootloader ?
Is it compatible with android 9?
When you first start TWRP can you allow changes in the system ?
ativi said:
Is it compatible with android 9?
Click to expand...
Click to collapse
i think yes, cause it booted right away! and installation was successful. I am curently using aosp extended 9.0 official and it works
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
hizaoui said:
Great work bro
This can work with locked bootloader ?
Click to expand...
Click to collapse
No! You need to unlock your bootloader before using this.
Hi,
First thanks for your great work.
But I have a problem.
After doing a full backup and doing some testing, I restored my whole backup. The process succeeded. But I am stuck in a bootloop,my phone boots to the point, where I can see the LOS 17.1 Logo, But does not continue. Have waited for 30 minutes a few times now.
I tried the built in bootloop fix, But it does not fix my problem.
Thanks in advance
Good day every one
Well, yesterday Google released android 11 for pixel handsets.
Soon you people can expect custom roms from my hand mean while i released android 11 twrp builds and with the help of my builds we will go forward accordingly on time for future releases towards custom roms and ports.
Soon I will release road map towards beta program make sure to keep an eye on my xda profile , threads and project updates & don't forget to donate if you love my work and also make sure to hit thanks button.
TWRP Changelog
* initial android 11.0 twrp builds released
Thank you
Thanks, finally a permanent TWRP for the device. (sticking to 10, as a game I play can't handle 11 correctly)
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen any idea why ?
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
KappaTheCapper said:
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
Click to expand...
Click to collapse
While phone is in fastboot mode, open device manager. Locate the unknown device and update its driver. Choose fastboot driver from existing drivers. It will install the driver and will work
KappaTheCapper said:
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
Click to expand...
Click to collapse
While phone is in fastboot mode, open device manager. Locate the unknown device and update its driver. Choose fastboot driver from existing drivers. It will install the driver and will work
Follow this,
fastboot flash recovery (drag recovery here or insert path)
press enter, it will fail saying something about a-b slots
Then finallay do,
fastboot boot (drag recovery here or insert path)
press enter
should boot your TWRP now
dmilz said:
fastboot flash recovery (drag recovery here or insert path)
press enter, it will fail saying something about a-b slots
Then finallay do,
fastboot boot (drag recovery here or insert path)
press enter
should boot your TWRP now
Click to expand...
Click to collapse
Thanks, I had same problem and this is working. Anyway the problem is, I have to do this every time I want to TWRP. Is there any way how to fix this and be able to avoid `flash recovery` part?
edit: removed
Looks like can't decrypt with Android 11. I'm 100 % sure that password is correct. With Android 10 it worked fine.
Are there any plans for updates? Thanks.
Hello people,
I accidently flashed the twrp-3.4.0-0-PL2_sprout.img file and now I am stuck in the androidone loading screen anytime I try to boot to that file in order to flash the twrp-installer-3.4.0-0-PL2_sprout.zip file.
Also when I try to boot the recocery I am stuck in the loading screen of TWRP.
any suggestion to fix that ?
maxischr said:
Hello people,
I accidently flashed the twrp-3.4.0-0-PL2_sprout.img file and now I am stuck in the androidone loading screen anytime I try to boot to that file in order to flash the twrp-installer-3.4.0-0-PL2_sprout.zip file.
Also when I try to boot the recocery I am stuck in the loading screen of TWRP.
any suggestion to fix that ?
Click to expand...
Click to collapse
The device has 2 boot slots. Try switching with fastboot --set-active: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
I cannot file the download link for the twrp installer.zip file. I have the image file but cannot find the zip file on the github download site.
Hi there,
The phone data was somehow disabled for no reason, I tried to enable mobile data and roaming, but it did not work.
In addition,
- "Developer options" was also disabled -- the options in "Developer options" disappeared within second after I entered it and the screen went blank, except "Developer options" remaining on the top;
- centre (homescreen) and right (opened apps) buttons in the navigation on the bottom of the phone were stuck, but left button (return) was still working.
To fix this issue, I booted into recovery mode and tried
- wiping cache and dalvik cache;
- repairing and resizing system, vendor, userdata, cache, dalvik cache partitions;
- (re)mounting the above 5 partitions,
but to no avail.
I checked the debloater and made sure that no system apps were removed via debloater.
I changed vendor partition to "ext2" and back to "ext4". And I rebooted the device to system, which subsequently booted into fastboot mode instead.
How to fix it?
Recovery is still usable.
Thanks in advance.
May you need any further information, please feel free to contact me.
Regards,
change of file system is same as formatting. restore vendor from backup
aIecxs said:
change of file system is same as formatting. restore vendor from backup
Click to expand...
Click to collapse
Unfortunately, I do not have vendor backup of this OS...
Would it be possible to flash / reinstall
- vendor.new.dat.br;
- vendor.patch.dat;
- vendor.transfer.list;
from the rom
or other ways to fix it?
Why do you have TWRP in first place? Next time backup beforehand, thats the purpose of TWRP
you need to convert into raw vendor.img first
https://github.com/xpirt/sdat2img
Code:
brotli --decompress vendor.new.dat.br -o vendor.new.dat
python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img
then you can flash from fastboot or adb
Code:
fastboot flash vendor vendor.img
or flash the whole ROM from stock recovery and start from scratch.
python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img
produced an error
Code:
File "sdat2img.py", line 1
Python 3.11.1 (v3.11.1:a7a450f84a, Dec 6 2022, 15:24:06) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin
^
SyntaxError: invalid syntax
maybe wrong line encoding, or that python is too new? can't tell you why it failed. probably not your fault. ask in support thread. https://forum.xda-developers.com/t/...-7-o-unpack-re-pack-android-dat-files.2978952
meanwhile you can send me link to firmware so I can convert for you.
Following hours of work, I was finally able to reboot into system after flashing vendor.img created by sdat2img.
Thank you very much for your help.
Code:
Sending sparse 'vendor' 1/1 (414215 KB) OKAY [ 9.252s]
Writing 'vendor' OKAY [ 68.242s]
Finished. Total time: 78.368s
But the issues remained in the system newly accessible
- I cannot use data network;
- two buttons (centre and right) at the bottom are not usable either.
I used the same method to restore system.img.
adb push failed
Code:
adb: error: failed to copy 'system.img' to '/dev/block/bootdevice/by-name/system': remote write failed: No space left on device
system.img: 1 file pushed, 0 skipped. 32.3 MB/s (3221225472 bytes in 95.099s)
But fastboot flash system system.img was ok.
Code:
Sending sparse 'system' 1/3 (515380 KB) OKAY [ 13.746s]
Writing 'system' OKAY [ 4.438s]
Sending sparse 'system' 2/3 (510053 KB) OKAY [ 13.414s]
Writing 'system' OKAY [ 3.462s]
Sending sparse 'system' 3/3 (264688 KB) OKAY [ 7.015s]
Writing 'system' OKAY [192.959s]
Finished. Total time: 240.702s
But even after system.img was restored back, data and navigation bar problems were not solved.
the adb error 'No space left on device' is strange. I guess it tried to copy a file into a dir (/dev/block/bootdevice/by-name/system/system.img) instead of writing partition. maybe some bug in adb. I have never tested. but it seems bootloader is unlocked so you can just flash from fastboot, as you finally did.
you can try to flash other partitions from stock firmware, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msadp. exist there some txt or xml file with mapping, partition label = file name?
if that doesn't help, maybe it is related to bootloader unlocking?
https://forum.xda-developers.com/t/how-do-i-recover-the-imei-after-unlocking-the-bootloader.4536397
aIecxs said:
the adb error 'No space left on device' is strange. I guess it tried to copy a file into a dir (/dev/block/bootdevice/by-name/system/system.img) instead of writing partition. maybe some bug in adb. I have never tested. but it seems bootloader is unlocked so you can just flash from fastboot, as you finally did.
you can try to flash other partitions from stock firmware, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msadp. exist there some txt or xml file with mapping, partition label = file name?
if that doesn't help, maybe it is related to bootloader unlocking?
https://forum.xda-developers.com/t/how-do-i-recover-the-imei-after-unlocking-the-bootloader.4536397
Click to expand...
Click to collapse
In the stock rom, it seems that there were not many flashable files, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msad...
{
"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"
}
that is only update ROM. what you need is full firmware for blank flash.
I re-downloaded and extracted the rom and it seems it is just the same.
yes, that's the difference between update ROM and full firmware. crystal ball says, you want firmware for OnePlus2?
https://www.full-repair-firmware.com/p/oneplus-2.html
or Xiaomi maybe?
https://xiaomifirmwareupdater.com/miui
there is always two files. smaller one is OTA update ROM (tag: recovery)
bigger file is full ROM/firmware bundle (tag: fastboot)
wenyendev said:
In the stock rom, it seems that there were not many flashable files, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msad...
View attachment 5814327
View attachment 5814329
View attachment 5814331
View attachment 5814333
Click to expand...
Click to collapse
It looks like what you're showing is a custom ROM, you may need to flash a stock ROM, that contains a stock vendor image too, to fix things.
yeah we might able to provide link, but OP won't tell us what device brand/model he's talking about...
Hi,
Yesterday while I was browsing normally, the phone suddenly froze and I couldn't do anything, not even turn off the screen. Then after like 3 mins the screen went blank. (it was turned on, but blank)
Some background,
this problem with the screen happened a few times before, at first it would happen randomly when trying to turn on the screen, it would turn on, be blank, flash a few times and turn off again, but a reboot would fix it. This happened like once a month.
Then it stopped happening when trying to turn on the screen, instead it started happening everytime I try to reboot. The Huawei logo and animation would show, but instead of showing the lockscreen it would again be blank, flash and turn off. It would be back to normal after a few hrs and/or after a reboot or two.
THEN the only thing that changed is that it would be blank even when booting up. The Huawei logo wouldn't show up.
However, the phone worked, sometimes the screen, instead of flashing, would stay turned on then dim down and turn off like it would normally do on the lockscreen. The touchscreen also worked because I managed one time to shut the phone down. I would also hear that startup sound after rebooting. At this point I thought it's a hardware issue, something with the display.
Now back to what happened yesterday, I think I rebooted the phone some time after it went blank, but now I couldn't hear the startup sound anymore, and I still couldn't turn off the screen.
I left it like that until the battery died, then when I plugged the charger the red led turned on, I waited for it to charge a bit, then when I tried to turn it on the red led started flashing. And maybe I'm paranoid but the flashing was a bit off, it wasn't the normal flashing you get when you have a notification for example.
I was tired so I went to sleep and left it like that overnight.
In the morning the screen was still blank, the red led was still flashing, and after I rebooted the screen went back to normal and I finally saw that the phone is stuck on this screen:
{
"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"
}
(image taken from a yt video)
I tried Power + Volume Up to try to go into recovery, it didn't work. It just reboots and stays stuck on that screen. Actually the only thing that worked was going into fastboot. (with Power + Volume Down)
The bootloader and FRP are both locked.
Some info from fastboot:
Code:
Z:\adb\platform-tools>fastboot oem get-build-number
(bootloader) :ANE-LX1 9.1.0.401(C432E13R1P7)
OKAY [ 0.006s]
Finished. Total time: 0.007s
Z:\adb\platform-tools>fastboot oem get-product-model
(bootloader) ANE-LX1
OKAY [ 0.007s]
Finished. Total time: 0.008s
Z:\adb\platform-tools>fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.006s
Z:\adb\platform-tools>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX1-CUST 9.1.0.13(C432)
OKAY [ 0.006s]
Finished. Total time: 0.007s
I was thinking maybe I can unlock the bootloader using the hardware testpoint method, with PotatoNV, then install TWRP and try to backup the data at least. (I never used TWRP, I just saw there's a Backup button, idk how/if it works)
But since it can't go into recovery, I wonder if I would be stuck on some screen again.
What should I do?
jdxgfty said:
I was thinking maybe I can unlock the bootloader using the hardware testpoint method, with PotatoNV, then install TWRP and try to backup the data at least. (I never used TWRP, I just saw there's a Backup button, idk how/if it works)
Click to expand...
Click to collapse
Yes, it's possible, using build-in File manager (Advanced > File manager > sdcard ) .
jdxgfty said:
But since it can't go into recovery, I wonder if I would be stuck on some screen again.
Click to expand...
Click to collapse
Good question...
Have you made any software modifications? (build.prop editing etc.)
Edit.:I mean, wrongly editing build.prop or systemUI can also cause similar screen issues.
-Alf- said:
Have you made any software modifications?
Click to expand...
Click to collapse
No, I don't think so.
I forgot to mention, I tried this command at one point: fastboot getvar rescue_enter_recovery
And it gave me this error: FAILED (remote: 'FAIL:need all image flashed!')
Does this help with anything?
Edit: Also when I held the Power + Volume Up buttons, the logo would take slightly longer to appear. Not a big difference, but it seemed like it was longer compared to just holding the power button.
jdxgfty said:
fastboot getvar rescue_enter_recovery
And it gave me this error: FAILED (remote: 'FAIL:need all image flashed!')
Click to expand...
Click to collapse
It is normal, it's not related to your problem.
If you want to try to save data from the phone, in your case you have only one chance - the mentioned method with TWRP.
Any method of restoring the software in your case means the loss of your data.
Personally, I would try replacing the battery first. If nothing else, you will have your phone ready for the test point .
-Alf- said:
I would try replacing the battery first
Click to expand...
Click to collapse
Why's that?
I have some questions about the testpoint method..
How do I glue the back cover after taking it off?
And on PotatoNV's readme it says I need some conductive tweezers, but I don't think I have any. Can I use something else?
Edit: To be more clear. Do you think the battery might've caused the issue? Recently I started seeing this type of notification, which I didn't see before:
Edit2: Ok, I'm sorry but I keep having questions..
I saw that fastboot has an option to boot from an image file, do I have more chances with this if flashing doesn't work?
And what if do the other way around, try the TWRP method first then replace the battery if that doesn't work?
jdxgfty said:
And what if do the other way around, try the TWRP method first then replace the battery if that doesn't work?
Click to expand...
Click to collapse
Well, I don't know, but logic tells me that if there is a problem with the battery, it is not certain that the TWRP method will work. Or other processes.
The battery thing is just a theory, you can ignore it. I'm not a specialist, I'm just a hobbyist.
jdxgfty said:
I saw that fastboot has an option to boot from an image file,
Click to expand...
Click to collapse
What exactly do you mean by that?
-Alf- said:
What exactly do you mean by that?
Click to expand...
Click to collapse
I saw this command somewhere: fastboot boot recovery twrp.img (or without the recovery)
jdxgfty said:
I saw this command somewhere: fastboot boot recovery twrp.img (or without the recovery)
Click to expand...
Click to collapse
that command doesn't work on Kirin devices.
Your priority is to save data, right? The methods of reviving the phone will come later.
For example this one
(of course, assuming TWRP is successfully installed and if there really is a software problem).
Hi @-Alf-
I unlocked the bootloader, but FRP is still locked. FB lock is disabled.
Code:
Z:\adb\platform-tools>fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.000s]
Finished. Total time: 0.001s
Z:\adb\platform-tools>fastboot oem lock-state info
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.002s]
Finished. Total time: 0.003s
Flashing TWRP fails:
Code:
Z:\adb\platform-tools>fastboot flash recovery_ramdisk Z:\TWRP-9.1.img
Warning: skip copying recovery_ramdisk image avb footer (recovery_ramdisk partition size: 0, recovery_ramdisk image size: 31006720).
Sending 'recovery_ramdisk' (30280 KB) OKAY [ 0.812s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Is it because of the FRP lock? What should I do from here?
On this video, the pinned comment says:
if you want to unlock the bootloader without wiping data, just check the "DISABLE FBLOCK (not recommended)" option, then no command needs to be used "fastboot oem unlock".
Click to expand...
Click to collapse
I don't understand if I'm supposed to not use any command (I didn't) or if I'm supposed to use fastboot oem unlock without the unlock code.
Also wanna note that now the "You device has been unlocked and can't be trusted" screen shows up and it's stuck on "Your device is booting now..."
jdxgfty said:
Is it because of the FRP lock?
Click to expand...
Click to collapse
In fastboot mode PHONE Unlocked and FRP Unlock?
(both red?)
-Alf- said:
In fastboot mode PHONE Unlocked and FRP Unlock?
(both red?)
Click to expand...
Click to collapse
No, FRP is locked, in green. Phone is unlocked, in red.
That's why I asked about the commands, I didn't wanna use any and mess up something.
jdxgfty said:
No, FRP is locked, in green. Phone is unlocked, in red.
That's why I asked about the commands, I didn't wanna use any and mess up something.
Click to expand...
Click to collapse
As far as I know, there are two types of bootloader blocking:
User lock:
This lock is managed using the "fastboot oem unlock <bootloader code>" command.
With such an unlock, it becomes possible to flash part of the partitions from fastboot. But not all. And of course, this procedure automatically triggers a factory reset on A7 and above.
FB Lock:
This lock is controlled using the "fastboot oem hwdog certify set <0 or 1>" command . For this command to work, FB Lock must already be disabled. In fastboot, which is launched through a testpoint!
With this unlock, it becomes possible to flash almost all partitions from fastboot, without wiping data.
When FB Lock is unlocked, the User Lock state is ignored. The phone behaves like it is completely unlocked.
As for this problem:
Warning: skip copying recovery_ramdisk image avb footer (recovery_ramdisk partition size: 0
- I saw the same one on another forum with the Honor 9lite, there was the cause locked BL, I don't know how it turned out in the end...
I personally have no experience with potatonv. And I don't want to give you any advice that would cause data loss.
jdxgfty said:
Is it because of the FRP lock?
Click to expand...
Click to collapse
If that were the cause, you would get the "command not allowed" error, imo.