Related
Hi everyone,
I was in the process of installing the stock Android factory 5.1 image from Chroma -- During this process I wiped everything (System data, user data, cache, etc) in TWRP and then went to fastboot to start the factory image flashing process. However, I accidently relocked my bootloader by executing my commands in the wrong order. I am now in the position where I can't unlock my phone's bootloader, as I need to enable "Allow OEM Unlock" in the developer settings, however, I can't do that as my phone currently has no OS installed.
I am at a gridlock currently, not sure how to proceed. Any ideas as to how I can fix this?
Any help would be much appreciated, as at this point, I am totally locked out of my device
Format cache and userdata via fastboot.
Edit: TWRP for the win
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ
DebianDog said:
See @rootSU a tool might have saved him
Click to expand...
Click to collapse
@DebianDog, I never need saving
DebianDog said:
Format cache and userdata via fastboot. If that doesn't work, nothing you can do.
Edit: no OS? Yeah....
Sorry bro RMA
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3
Ooohhh Nice! Nothing like having a backup Good job!
Sent from my Benzo'd Google N6 on VZ
curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?
BladeRunner said:
curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?
Click to expand...
Click to collapse
Cutting and pasting while not paying attention is what I figured.
Not something I've done on my phone but at work once or twice....
Sent from my Benzo'd Google N6 on VZ
Glad it's all sorted.
Just noticed the avatar, very appropriate
rootSU said:
Glad it's all sorted.
Just noticed the avatar, very appropriate
Click to expand...
Click to collapse
I was thinking the same thing actually haha
No TWRP backup...
p011uX said:
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3
Click to expand...
Click to collapse
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?
NDAMT said:
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?
Click to expand...
Click to collapse
Do you have TWRP recovery installed?
rootSU said:
Do you have TWRP recovery installed?
Click to expand...
Click to collapse
Yes. Luckily. :good:
NDAMT said:
Yes. Luckily. :good:
Click to expand...
Click to collapse
Just download a stock rom.zip and put it on your sdcard.
rootSU said:
Just download a stock rom.zip and put it on your sdcard.
Click to expand...
Click to collapse
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
Where did you get that? Got a link?
NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk
rootSU said:
Where did you get that? Got a link?
Click to expand...
Click to collapse
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
zephiK said:
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
No you need a flashable rom.zip from XDA.
NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Sent from my Nexus 6 using Tapatalk
rootSU said:
No you need a flashable rom.zip from XDA.
Click to expand...
Click to collapse
zephiK said:
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Click to expand...
Click to collapse
OK, at this point treat me like a noob. What rom.zip would you recommend for someone who is trying to get their phone back to factory?
Hi ,
I am not a noob, but yesterday out of curiosity flashed the flyme build in the unified section. However, after the TWRP reboot to system, it did not boot. So tried to reboot the recovery and success. But the villian was there, encryption password. I tried giving my phone PIN, it said wrong password.
After half an hour, i installed the stock image(3.5.1) using the msm tool. Well it booted fine and phone is usable. Unlocked the bootloader and flashed the latest TWRP,.
The villian is back, asking for password. Now it is taking any password, always say wrong password. Ok in case i skip the decrypt screen, i cannot access the sdcard to flash new rom.
Is this the end of story of my op3t?
Have you tried "default_password"?
Didgeridoohan said:
Have you tried "default_password"?
Click to expand...
Click to collapse
Tried everything. The phone boots into OOS 3.5.1 after msm tool flash without password. Even it behaves very well. Only after the TWRP installation. It is stuck for password. I think its end of story.
Prashanthme said:
Tried everything. The phone boots into OOS 3.5.1 after msm tool flash without password. Even it behaves very well. Only after the TWRP installation. It is stuck for password. I think its end of story.
Click to expand...
Click to collapse
Then I don't know... Usually if TWRP suddenly starts asking for a password without having set one, using "default_password" will work.
You could try flashing a kernel that disables forced encryption and then format data to unencrypt.
You have to make sure to restore system to the version using the same encryption libraries as used the last time you could decrypt the data partition. If all fails you will have to format your data partition and loose it all.
pitrus- said:
You have to make sure to restore system to the version using the same encryption libraries as used the last time you could decrypt the data partition. If all fails you will have to format your data partition and loose it all.
Click to expand...
Click to collapse
I have already lost the data. TWRP not allowing me to enter the sdcard storage to flash anything. Can u brief me how to format the data partition.
Just bootup phone into fastboot mode from the unlocked bootloader menu, then connect to PC and run "fastboot format userdata" from a path with either fastboot in or anywhere of you've added the folder with fastboot in you PATH variable.
pitrus- said:
Just bootup phone into fastboot mode from the unlocked bootloader menu, then connect to PC and run "fastboot format userdata" from a path with either fastboot in or anywhere of you've added the folder with fastboot in you PATH variable.
Click to expand...
Click to collapse
Did this. But after should i flash the stock image again? Because system is not booting and stuck in oneplus logo.
How about fastboot erase options?
I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.
pitrus- said:
I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.
Click to expand...
Click to collapse
Let me try once i go home and update u. Thanks for the response..
Will format the data from fastboot. and flash the stock image. Hope this works.
Finally happened to work.
Installed a different version twrp made the trick. But this time i erased the recovery and flashed again. After that wiped all the data and then sideloaded the rom from adb and it did the trick..
pitrus- said:
I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.
Click to expand...
Click to collapse
Can you please tell me how you disabled encryption?
Vidicgapi said:
Can you please tell me how you disabled encryption?
Click to expand...
Click to collapse
You do this by flashing the latest no-verity-opt-encrypt zip file after formatting the data partition and also after each update of the OS.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
lcarolo said:
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
Click to expand...
Click to collapse
Hey, the same is happening to me since today, i'm looking why but i can't find the reason its drivin' me crazy i can't setup encryption...
edit : couldn't achieve to unlock TWRP with a custom ROM encryption, stock ROM encryption with MIUI is working fine tho... If someone has any infos
lcarolo said:
Hello, I installed AOSIP, everything works great but into twrp I can't decrypt data...
I've tried twrp R2.3.2.1 and R2.3.2.5, it says wrong password... I use the pin code of the ROM...
What can I do?
Click to expand...
Click to collapse
@Displayer
Your data from the last install appears to be encrypted. If you have a backup the easiest way to resolve the issue is to format your storage. You could also use the All in One tool and use its encryption removal option. Please keep in mind that it will wipe out all of your memes, so hopefully those are backed up.
tsongming said:
@Displayer
Your data from the last install appears to be encrypted. If you have a backup the easiest way to resolve the issue is to format your storage. You could also use the All in One tool and use its encryption removal option. Please keep in mind that it will wipe out all of your memes, so hopefully those are backed up.
Click to expand...
Click to collapse
I mean, i formatted to have a custom ROM booting, encrypting my data. I can use the phone, my pin code works in android but it's impossible to decrypt with TWRP...
Édit : found that message from argraur on telegram, so basically we have to wait for an updated twrp ? "Android release 9.0.0_r36 (r37) with May security patch has updated FBE encryption that breaks decryption in TWRP."
Displayer said:
I mean, i formatted to have a custom ROM booting, encrypting my data. I can use the phone, my pin code works in android but it's impossible to decrypt with TWRP...
Édit : found that message from argraur on telegram, so basically we have to wait for an updated twrp ? "Android release 9.0.0_r36 (r37) with May security patch has updated FBE encryption that breaks decryption in TWRP."
Click to expand...
Click to collapse
That doesn't even make sense. Twrp will not decrypt your phone.
Install Miui again, backup your data, to your desktop, by manually dragging your files over.
Go here and download DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER you will use it to flash between updates or for dirty flashing Miui updates.
Next go back to TWRP the choose format and type yes reboot to TWRP ( you will se a message that says you have no OS are you sure?) Yes, reboot to TWRP
TWRP is not your issue, go read
and read the first comment here
Format storage, or wait for the TWRP and you still need to the format storage, Again a TWRP update will not resolve the issue. We have all had this exact issue.
I'm using another workaround:
With the all in one tool, we can flash .zip from a PC.
So I could install a custom kernel file from my pc directly into phone without loosing data.
Annoying thing is that I need the PC... Can't flash files that are in phone memory... Not such a big issue...
Another question, can I make a backup from the PC? Used to do it via twrp, but it is not safe with that issue...
lcarolo said:
I'm using another workaround:
With the all in one tool, we can flash .zip from a PC.
So I could install a custom kernel file from my pc directly into phone without loosing data.
Annoying thing is that I need the PC... Can't flash files that are in phone memory... Not such a big issue...
Another question, can I make a backup from the PC? Used to do it via twrp, but it is not safe with that issue...
Click to expand...
Click to collapse
Today i found a TWRP with decryption for may patch working for me here : https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
I think u can pull img if i remember well but now its working for me
Displayer said:
Today i found a TWRP with decryption for may patch working for me here : https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
I think u can pull img if i remember well but now its working for me
Click to expand...
Click to collapse
This twrp is working! Thanks a lot!
I used fastboot to flash twrp-3.5.0_9-0-raphael.img. I used TWRP make a full backup to internal memory. Then I flashed xiaomi.eu_multi_HMK20ProMI9TPro_21.2.24_v12-11.zip which didn't work. So back to fastboot->TWRP to restore backup.
But it doesn't ask for my pattern anymore! All my files remain encrypted. Command line adb shell twrp decrypt fails too.
Is there a special TWRP version that can help me out? Or is it game over?
what problem did u face while flashing eu rom
Redsandro said:
I used fastboot to flash twrp-3.5.0_9-0-raphael.img. I used TWRP make a full backup to internal memory. Then I flashed xiaomi.eu_multi_HMK20ProMI9TPro_21.2.24_v12-11.zip which didn't work. So back to fastboot->TWRP to restore backup.
But it doesn't ask for my pattern anymore! All my files remain encrypted. Command line adb shell twrp decrypt fails too.
Is there a special TWRP version that can help me out? Or is it game over?
Click to expand...
Click to collapse
If possible try using oxfox to flash eu rom
Ezio553 said:
what problem did u face while flashing eu rom
Click to expand...
Click to collapse
On boot I noticed screen no longer said "Mi 9T Pro" but "Redmi", and it can only boot to "Mi-Recovery 3.0"
Ezio553 said:
If possible try using oxfox to flash eu rom
Click to expand...
Click to collapse
What is oxfox? No search results.
So it appears I made the mistake of dirty-flashing Android 11 over Android 10.
Is there any file from old ROM I can manually push back to restore the encryption key?
you are rooted via magisk?
Have you tried erasing and formatting userdata partition it might generate itself with the new encryption key you rom running
ineedroot69 said:
you are rooted via magisk?
Click to expand...
Click to collapse
No, I just flashed the ROM and rebooted. No magisk.
EDIT: I had magisk on the old/previous ROM though, if that matters.
ineedroot69 said:
Have you tried erasing and formatting userdata partition it might generate itself with the new encryption key you rom running
Click to expand...
Click to collapse
This will probably work, but I'm trying to decrypt and download my encrypted files from internal storage first.
Redsandro said:
On boot I noticed screen no longer said "Mi 9T Pro" but "Redmi", and it can only boot to "Mi-Recovery 3.0"
What is oxfox? No search results.
Click to expand...
Click to collapse
orangefox reovery and if u are storage is encrypted then u will have to format it once to decypt it
Rom OneOS based A715FXXS7BUJ1
read to all
Hi guys, here I share my ROM for the Galaxy A71, I am not responsible for damaged phones, install at your own risk.
This rom was born from the need to have root or some other modification in stock but Samsung has included many limitations which make it difficult to modify in stock.
Features
Debloat
vaultkeeper disabled
FRP removed
knox counter at 0 (Samsung Health)
Fingerprint animation changed
optimizations
Google Discover enabled
Dolby without headphones
Apply themes without trial time limit
Deknoxed
Full Edge Lighting (extra effects unlocked)
Secure Folder working
Floating Feature tweaks
Mock Locations
Mock Providers
High Volume Warning (disable)
Secure Flag
Recovery Reboot (this is when you press Reboot and he Reboot to recovery)
Click to expand...
Click to collapse
BUGS: At the moment it has not reported any bug.
Installation:
Extract OneOS ROM with an unzip program
Reboot recovery
Format data
Install ROM as "super" image in TWRP
Flash muiltidisabler
Flash Magisk (optional)
Reboot
Downloads:
Version 1:
Link: Google Drive
Credits: Kernel Source (Link)
Hello from Greece
I try this rom for 2 days . Everything looks fine . I have not any problem.
Thank you very match
ZhandarbekD said:
Rom OneOS based A
Click to expand...
Click to collapse
Please check your PM inbox. Thank you.
-Regards: Badger50 FSM
Getting error 255 when flashing custom rom how to fix
Unable to flash any custom rom due to this error occurring
Here the error
Is it possible to dirtflash with NcX?
How to install ?
I get 255 error on TWRP.
papgr00 said:
Hello from Greece
I try this rom for 2 days . Everything looks fine . I have not any problem.
Click to expand...
Click to collapse
Any bug ?
How i can install ?
I getting 255 error on twrp
josegarcia01 said:
Any bug ?
How i can install ?
I getting 255 error on twrp
Click to expand...
Click to collapse
What TWRP version do you use?
Pupet_Master said:
What TWRP version do you use?
Click to expand...
Click to collapse
Twrp 3.5.1
josegarcia01 said:
Twrp 3.5.1
Click to expand...
Click to collapse
Well you may not like to risk but i feel that the error is due to TWRP not being able to write on the device.
First things first, try to download again the ROM, and don't flash the zip file, but flash the .img file inside.
Pupet_Master said:
Well you may not like to risk but i feel that the error is due to TWRP not being able to write on the device.
First things first, try to download again the ROM, and don't flash the zip file, but flash the .img file inside.
Click to expand...
Click to collapse
I did, tried to flash The img file.
And tried With twrp 3.6 too
josegarcia01 said:
I did, tried to flash The img file.
And tried With twrp 3.6 too
Click to expand...
Click to collapse
It could also be TWRP not being able to access the internal storage to write the ROM.. but im not positive
Pupet_Master said:
It could also be TWRP not being able to access the internal storage to write the ROM.. but im not positive
Click to expand...
Click to collapse
Can you help-me to solve this ?
or, how i can find on the internet ?
josegarcia01 said:
Can you help-me to solve this ?
or, how i can find on the internet ?
Click to expand...
Click to collapse
I think you should try to flash magisk and see if it flash ok
If so, i dont know what the issue is... if it wont flash ok, you will need to format your phone data
Pupet_Master said:
I think you should try to flash magisk and see if it flash ok
If so, i dont know what the issue is... if it wont flash ok, you will need to format your phone data
Click to expand...
Click to collapse
Flash ok, i tried magisk, and multidisabler, both Flash ok.
The system img as a super i get these error.
josegarcia01 said:
Flash ok, i tried magisk, and multidisabler, both Flash ok.
The system img as a super i get these error.
Click to expand...
Click to collapse
Ok, i don't know what is the problem.
Either risk format the phone data (but you will lose everything) and try to flash again... or well... wait for the author to reply.
Pupet_Master said:
Ok, i don't know what is the problem.
Either risk format the phone data (but you will lose everything) and try to flash again... or well... wait for the author to reply.
Click to expand...
Click to collapse
Everytime i tried formating data.
I dont tried withouth format data.