I have a lenovo P2a42(of my late brother) with data locked inside.
Developer options not enabled
Don't know password
bootloader not unlocked
So, my plan was to download flash tool and flash a custom recovery and then proceed from their by deleting password.key file from /data.
The flash tool I got was Lenovo_Downloader_v1.0.3 and Lenovo_Downloader_v1.0.2. Both of them do not have an option to flash only recovery.
Has someone flashed only recovery before? Let me know your suggestions.
Related
attached is a semi-working recovery, you can flash it with "fastboot flash recovery recovery.img".
update: the recovery can flash boot.img's too, if the custom rom uses "dd" instead of "write_raw_image" to flash the boot.img. i hope mike updates his rom
don't use anything except for "install from sdcard"
i take no responibility for any harm to your device or data
it's basicaly a repacked cwm recovery combined with the stock 1.26 recovery kernel/ramdisk with modifications to init.rc
it is intented for developers wanting to toy around with custom roms, until someone makes a real recovery
no support nor updates will be made for this
is it tested or not yet.
I've tested it
ok thanks, since currently there is no other option to unlock bootloader other than htcdev & lack of RUU sources is too risky to flash custom recovery at this point. so technically it will skip zip package signature check? so we can start working on working custom rom.
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
looks nice!
could you maybe share your knowledge about creating this recovery? i'm trying the same for the one s but can't get it packed together correctly...
blubbers said:
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
Click to expand...
Click to collapse
Understand. My concern is no RUU for my device available yet & im afraid to use from other region stock rom Thanks for ur effort.
Do I have to unlock my phone to install this recovery?
moom999 said:
Do I have to unlock my phone to install this recovery?
Click to expand...
Click to collapse
yes, there are only 2 ways of installing a recovery.
fastboot and adb
fastboot requires you to unlock in order to "fastboot flash recovery"
and in order to possibly do it through adb you need root and in order to get root at the minute you need to be able to flash an insecure boot image through fastboot, which again, you need to unlock in order to "fastboot flash boot"
Hi blubbers,
There is a guy on general thread who wants to dump a developer phone. It's s4 not tegra but might help.
http://forum.xda-developers.com/showthread.php?p=24496390
sent from my HTC one X using tapatalk
I was careless with odin and whiped my efs partition while flashing some stock firmware.
Tried flashing more than a few other stock builds, deleted the cache file like you see on a few other dm-verity threads. Nothing I have tried works.
So I am wondering how much it would cost to send to Samsung to un-brick. Open to any other suggestions also.
If there was a way to flash or bootstrap TWRP or CWM with the bootloader locked I would be so happy. Either that or would it be possible to flash a TWRP backup of the userdata with odin? (If the setting for the FRP lock is stored in userdata land anyway.)
Any help would be greatly appreciated.
Sent from my SM-G935P using Tapatalk
Just recieved device a few days ago and unlocked the bootloader, was expecting a data wipe but it rebooted right where I left it. Unlock was confirmed in dev options. Booted into TWRP (but did not flash it) with the intent of doing a full untoched ROM backup to SD card. Really couldn't get past the opening screen asking me for password to decrypt data. Tried my lock screen pin and defaut_password but no luck. Went to reboot and it wouldn't boot so I booted back into TWRP, formated and installed pre-rooted ROM. Would like to download the stock firmware if possible. Could any kind person point me in the right direction? Thanks,
Go here to download rom http://en.miui.com/a-234.html
On left select either fastboot flashing method or recovery flashing method choose which one you'd prefer to use
Sent from my MI MAX using Tapatalk
So, I had an unlocked BL, rooted phone, with TWRP 3.3.1 deestroy.
For some reason, I booted into my recovery, wiped all my data, through format and advanced wipe feature. I even changed slots (just to make sure) and formatted data, and advanced wipe.
I then locked my bootloader, through adb fastboot command. Rebooted my phone, which had nothing to boot to. Then I unlocked my bootloader, rebooted my phone again, and it got booted into TWRP 3.3.1
Now my understanding is, unlocking bootloader, and using formatting options from TWRP should have wiped my data completely.
Then why did my phone boot into TWRP 3.3.1 after I unlocked the BL?
This might be helpful for you:
https://github.com/tkchn/daisyinstall
Lol. I didn't ask for how to flash a custom ROM.
Just need help understanding how the bootloader works? Where does TWRP get installed? Why after wiping did TWRP survive?
shazee666 said:
Now my understanding is, unlocking bootloader, and using formatting options from TWRP should have wiped my data completely.
Then why did my phone boot into TWRP 3.3.1 after I unlocked the BL?
Click to expand...
Click to collapse
Different things live on different partitions.
TWRP does not live on the userdata partition so wiping data cannot remove TWRP.
You need to use fastboot or miflash to do a full flash and restore a phone to stock.
Okay. This cleared somethings...
If you have tampered with the phone's partitions (TWRP patches itself into boot.img) you should never lock the Bootloader. Basically when the Bootloader is locked, the phone checks all the partitions of the phone if they've been tampered or still the same as Xiaomi designed it. In the case that they've been tampered, the phone won't boot itself, this helps with a lot of security issues. Never lock your Bootloader if you've made changes to the system, boot or other partitions (except userdata, this is why enabling cam2api and locking the BL won't mess up your device because the persist command stores the command in data partition). If you want to lock the BL, just flash the stock rom beforehand. Cheers.
Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear