Dear Reader,
As you could see on a video, the device is unlocked using official method ( SMS ), but after when trying to unlock the OEM bootloader it locks itself again.
Why and how to unlock it completely to flash TWRP and Root ?
Thank you.
Best regards,
V7
its already unlocked. try to flash twrp maybe? as you can see the bootloader is already unlocked, then you can flash custom recovery
why are you confused? the settings app already told you its already unlocked
Exodus4 said:
its already unlocked. try to flash twrp maybe? as you can see the bootloader is already unlocked, then you can flash custom recovery
why are you confused? the settings app already told you its already unlocked
Click to expand...
Click to collapse
Thank you for your reply, really.
As you could notice, the trigger sets itself to disabled when menu changes( it doesn't stay at its position ), so I though that the trigger just doesn't work, doesn't it ?
There is only ONE bootloader. You already unlocked it. That trigger is only for enabling lock and unlock from fastboot interface using the code "fastboot oem unlock", which many other android devices use, but probably not for xiaomi ones. That trigger is NOT for unlocking bootloader, or in other words, turning it on DOES NOT unlock the bootloader. There is no such thing as "OEM bootloader". Your bootloader is already unlocked. Go to fastboot and flash TWRP and do whatever you want.
NTLinhHaHa said:
There is only ONE bootloader. You already unlocked it. That trigger is only for enabling lock and unlock from fastboot interface using the code "fastboot oem unlock", which many other android devices use, but probably not for xiaomi ones. That trigger is NOT for unlocking bootloader, or in other words, turning it on DOES NOT unlock the bootloader. There is no such thing as "OEM bootloader". Your bootloader is already unlocked. Go to fastboot and flash TWRP and do whatever you want.
Click to expand...
Click to collapse
Thank you for your reply really.
By the way, I've already tried to flash a custom recovery like TWRP 3.2.1.0, but after rebooting into recovery the old recovery had been shown, even if fastboot tells that everything regarding flashing is OK, so I though it's just locked. Do you know why it loads old stock recovery ?
vv7v7 said:
Thank you for your reply really.
By the way, I've already tried to flash a custom recovery like TWRP 3.2.1.0, but after rebooting into recovery the old recovery had been shown, even if fastboot tells that everything regarding flashing is OK, so I though it's just locked. Do you know why it loads old stock recovery ?
Click to expand...
Click to collapse
Is it really the old recovery, or just a screen with a bunch of yellow buttons? If it's the latter, did you try touching the "recovery" button and THEN the left-side button (there will be a blue and a green button shown)?
After that the phone will boot twrp.
If it's really the old recovery, how did you flash twrp? Through adb? Did you try just booting twrp instead of flashing it? Like "fastboot boot twrp.img" ?
NTLinhHaHa said:
Is it really the old recovery, or just a screen with a bunch of yellow buttons? If it's the latter, did you try touching the "recovery" button and THEN the left-side button (there will be a blue and a green button shown)?
After that the phone will boot twrp.
If it's really the old recovery, how did you flash twrp? Through adb? Did you try just booting twrp instead of flashing it? Like "fastboot boot twrp.img" ?
Click to expand...
Click to collapse
Thank you for your reply really.
Yes, I've used adb and did everything like in this article ( where "Install via ADB" ). So, after that, when clicked on "recovery" ( in menu like you've described above ) it asked me something like "Am I sure to proceed ?", so I accepted this one with a blue button "OK" and it went to "MI-Recovery 3.0" like:
{
"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's from internet )
vv7v7 said:
Thank you for your reply really.
Yes, I've used adb and did everything like in this article ( where "Install via ADB" ). So, after that, when clicking on "recovery" and accepting with blue button "OK" it goes to "MI-Recovery 3.0" and shows:
( image's from internet )
Click to expand...
Click to collapse
While "installing via ADB", did your phone actually rebooted into Fastboot mode? (the screen showing an android and the word "FASTBOOT" on it)
Try it this way: while the phone is on, reboot the phone via power menu. When the Mi logo appears and the device vibrates a bit, start holding both "Power" button and "Volume down" button (Vol-) until the phone vibrates again. Release both buttons. THEN plug the phone to PC, open adb command prompt window. Assuming the twrp image on your computer is named twrp3210.img, here's the code you need to enter:
Code:
fastboot flash recovery twrp3210.img
After that, go to recovery like you normally do.
That should work.
Remember from now on: Power + Vol- = Fastboot; Power + Vol+ = Recovery. You cannot go to recovery or bootloader from adb in MIUI stock rom.
NTLinhHaHa said:
While "installing via ADB", did your phone actually rebooted into Fastboot mode? (the screen showing an android and the word "FASTBOOT" on it)
Try it this way: while the phone is on, reboot the phone via power menu. When the Mi logo appears and the device vibrates a bit, start holding both "Power" button and "Volume down" button (Vol-) until the phone vibrates again. Release both buttons. THEN plug the phone to PC, open adb command prompt window. Assuming the twrp image on your computer is named twrp3210.img, here's the code you need to enter:
Code:
fastboot flash recovery twrp3210.img
After that, go to recovery like you normally do.
That should work.
Remember from now on: Power + Vol- = Fastboot; Power + Vol+ = Recovery. You cannot go to recovery or bootloader from adb in MIUI stock rom.
Click to expand...
Click to collapse
Thank you.
So, I've done the same as you described:
The "fastboot" text was show with a rabbit like
( image's from internet ), so after I've executed the command:
Code:
fastboot flash recovery twrp3210.img
it shows something like:
( image's from internet ) and after just turned off the phone. Then I've pressed Power + Vol+ and it shows the chinese menu like:
( image's from internet )
vv7v7 said:
Thank you.
So, I've done the same as you described
Click to expand...
Click to collapse
Yes, and then press recovery and then the left-side button.
NTLinhHaHa said:
Yes, and then press recovery and then the left-side button.
Click to expand...
Click to collapse
Thank you.
As you could notice from previous messages
So, after that, when clicked on "recovery" ( in menu like you've described above ) it asked me something like "Am I sure to proceed ?", so I accepted this one with a blue button "OK" and it went to "MI-Recovery 3.0" like:
Click to expand...
Click to collapse
already done this one and got stock recovery.
vv7v7 said:
Thank you.
As you could notice from previous messages already done this one and got stock recovery.
Click to expand...
Click to collapse
How about typing into fastboot:
Code:
fastboot oem device-info
Does the returned message say that you are unlocked?
How about trying a different twrp image?
NTLinhHaHa said:
How about typing into fastboot:
Code:
fastboot oem device-info
Does the returned message say that you are unlocked?
How about trying a different twrp image?
Click to expand...
Click to collapse
Thank you.
The command above gave:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
I've tried to boot into TWRP with "fastboot boot twrp.img" exactly after flashing "twrp.img", so it booted into TWRP normally, but after reboot into bootloader and choose a recovery it booted into stock rom recovery as before.
Old TWRP versions don't have some features which has 3.2.1.0, so it's rather interesting why this one doesn't boot after flashing and rebooting.
Although, there's a chance that stock rom reflashes recovery each reboot, so that's why. What do you think, is it possible ?
vv7v7 said:
Thank you.
The command above gave:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
I've tried to boot into TWRP with "fastboot boot twrp.img" exactly after flashing "twrp.img", so it booted into TWRP normally, but after reboot into bootloader and choose a recovery it booted into stock rom recovery as before.
Old TWRP versions don't have some features which has 3.2.1.0, so it's rather interesting why this one doesn't boot after flashing and rebooting.
Although, there's a chance that stock rom reflashes recovery each reboot, so that's why. What do you think, is it possible ?
Click to expand...
Click to collapse
You can totally see from the returned message that your device is unlocked. Yes, and possibly stock rom reflashes recovery each boot. So your way should be to boot twrp.img, wipe System, Data and all caches. install a new rom, and then reboot to fastboot to flash twrp.img into recovery =)))
NTLinhHaHa said:
You can totally see from the returned message that your device is unlocked. Yes, and possibly stock rom reflashes recovery each boot. So your way should be to boot twrp.img, wipe System, Data and all caches. install a new rom, and then reboot to fastboot to flash twrp.img into recovery =)))
Click to expand...
Click to collapse
Thank you.
By the way, in case of leaving stock rom on board and wiping Data and Caches will turn rom to factory reset, but will leave it, is it right ?
vv7v7 said:
Thank you.
By the way, in case of leaving stock rom on board and wiping Data and Caches will turn rom to factory reset, but will leave it, is it right ?
Click to expand...
Click to collapse
Yeah, wipe data + cache = factory reset
Related
How to flash a factory image | Return to stock | Unroot your Nexus 5
Hello Nexus 5 Users!
I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to fix your mistakes.
This process consists of wiping and flashing every partition on your phone.
{
"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"
}
WARNING!!!
This process will wipe your phone completely. Backup your storage before you continue.
I am also not responsible if anything goes wrong.
You can backup apps and data using this app before you unlock the bootloader. No root required.
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
DO NOT USE TOOLKITS!!!
They have a high probability of something going wrong if you don't know how to use them (which, if you managed to ruin your phone, probably is true).
I don't mean to offend toolkit creators. They did a great job. But don't risk bricking your phone just because you're lazy.
FOLLOW EVERY SINGLE STEP
or you will end up in a bootloop, or with a bricked phone, and we don't want that
Let's get started!!
Setting up
For this process, you will need to:
★Install adb and fastboot drivers. To do this, use this simple program:
http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users:
http://forum.xda-developers.com/showthread.php?t=1917237
*Note: MAC users will have to write "./" before every command in this thread. For example : "./fastboot flash recovery recovery.img"
Linux users should know their stuff
http://forum.xda-developers.com/showthread.php?t=921169
★Download the latest factory images from here:
https://developers.google.com/android/nexus/images#hammerhead
★Extract the archive you downloaded (Use WinRAR). It should look like this:
★Unlock your bootloader (In case you haven't already)
http://forum.xda-developers.com/showthread.php?t=2507905
Flashing the factory images
There is more than one way to flash these images. Each give the same results, but the first is for lazy users
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
Method 2. Long method (Same thing actually, but I'll mention it, just in case)
★Extract the image-hammerhead-krt16m.zip somewhere easy to access (On C:\image-hammerhead-krt16m for example). You will have the following files:
★In the same folder, from the original archive, extract "bootloader-hammerhead-XXXXXX.img" (rename it to bootloader.img) and "radio-hammerhead-XXXXXX.img" (rename it to radio.img)
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Open a CMD window.
★Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
[B](Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)[/B]
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
For both methods:
Optional, but necessary for warranty purposes - Locking your bootloader+ Resetting the tamper flag
The Nexus 5 has a thing implemented in the bootloader called a tamper flag. This shows if the bootloader was ever unlocked, kind of like the flash counter with Samsung devices. You can check it out by using this command
Code:
fastboot oem device-info
. If the tamper flag value is "true", then you'll have to reset it. The following steps will reset this flag, and lock your bootloader.
•So, first, go here: http://forum.xda-developers.com/showthread.php?t=2239421 (Thanks @osm0sis for the wonderful script)
Under "Flashable Zips", you will find the Nexus BootUnlocker script. Download it.
•Put the zip on your internal storage.
•Download the latest TWRP recovery image for the Nexus 5 from here: http://techerrata.com/browse/twrp2/hammerhead. Rename it to TWRP.img.
Now boot it. You do this by booting your phone in fastboot, and typing the following command:
Code:
fastboot boot path\to\TWRP.img
*Replace path\to\TWRP.img with the path to where you placed the TWRP.img. For example: C:\Users\X\Desktop\TWRP.img
TWRP recovery should boot.
•When TWRP finished booting, select "Install", then navigate to the Nexus Bootunlocker zip, select and install it. After it finished, use the back arrow at the bottom of the screen to go back, and reboot.
Now your bootloader should be locked, and your tamper flag should show "false".
And now you have a brand new Nexus 5 (software wise, at least)
Video Guides
Thanks @techfanatic9.
For Windows:
For Mac:
Another easy and fast tutorial made by @iTzGavin96
These don't contain the tamper flag reset step. Follow the steps above to reset your tamper flag value to "False" for warranty purposes.
If you now have 12 GB of storage instead of 28 GB, go to post #2
32 GB phone now shows 16GB?
This is a common problem with Nexus devices. Minor error, don't panic. Here is how to fix it
★Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
★Clear cache
★Factory reset
If that didn't work, proceed with doing this:
Open a CMD window, boot your phone is fastboot, and write the following commands, in this order (Considering that you have extracted the images in C:\image-hammerhead-krt16m\)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
Credits and Thanks:
@efrant
For his thread in the N4 section (http://forum.xda-developers.com/showthread.php?t=2010312)
@osm0sis
For contributing a lot with the tamper flag part
@dombera
For inspiring me to make this guide
@Chromium_
For not replying to my Hangouts messages
@jd1639
For helping me out with this thread.
@Prodeje79
For pointing problems out.
abaaaabbbb63 said:
Chromium_
For not replying to my Hangouts messages
Click to expand...
Click to collapse
I do my best
Jk, my school has WiFi jammers in some of the classes.
Sent using xda-developers app
Chromium_ said:
I do my best
Jk, my school has WiFi jammers in some of the classes.
Sent using xda-developers app
Click to expand...
Click to collapse
Really? That's..... evil!!
abaaaabbbb63 said:
Really? That's..... evil!!
Click to expand...
Click to collapse
Evil...more like illegal.
Bleah.. The Dotted divider looks horrible on Tapatalk....
Meh
Because I don't know better, why do you consider method 2 safer?
Is there an easier "hide root" or any way to unroot where AirwatchMDM or other MDM corporate software control crap is hidden?
I'm wanting to try register on airwatch then lock down airwatch and see if I could still use touchdown.
jd1639 said:
Because I don't know better, why do you consider method 2 safer?
Click to expand...
Click to collapse
Well, safer in the sense that you are more in control, and can only flash certain images, not all. I'll delete de safe part.
fintheman said:
Is there an easier "hide root" or any way to unroot where AirwatchMDM or other MDM corporate software control crap is hidden?
I'm wanting to try register on airwatch then lock down airwatch and see if I could still use touchdown.
Click to expand...
Click to collapse
If you have root through the "SuperSU" app, it has an unroot option.
My keeps boot looping
sergiox209 said:
My keeps boot looping
Click to expand...
Click to collapse
Did you factory reset from the Stock Recovery?
abaaaabbbb63 said:
Did you factory reset from the Stock Recovery?
Click to expand...
Click to collapse
not the stock one a Rom
sergiox209 said:
not the stock one a Rom
Click to expand...
Click to collapse
Wait, what exactly did you do?
abaaaabbbb63 said:
Wait, what exactly did you do?
Click to expand...
Click to collapse
honestly i forgot but it keeps telling me in CMW error mounting /data if i try to wipe data
sergiox209 said:
honestly i forgot but it keeps telling me in CMW error mounting /data if i try to wipe data
Click to expand...
Click to collapse
You flashed CWM without booting in the stock ROM?
Please, follow the guide accordingly.
Try keeping it stock for the first boot. Then, you may install a custom recovery.
abaaaabbbb63 said:
You flashed CWM without booting in the stock ROM?
Please, follow the guide accordingly.
Try keeping it stock for the first boot. Then, you may install a custom recovery.
Click to expand...
Click to collapse
yes thats what im trying to do but it keeps boot looping. if there a way i can fix?
sergiox209 said:
yes thats what im trying to do but it keeps boot looping. if there a way i can fix?
Click to expand...
Click to collapse
The bootloop is most probably caused by you not factory resetting. Do you have the stock recovery right now?
abaaaabbbb63 said:
The bootloop is most probably caused by you not factory resetting. Do you have the stock recovery right now?
Click to expand...
Click to collapse
the file that you provide i have that download.
sergiox209 said:
the file that you provide i have that download.
Click to expand...
Click to collapse
Ok, so you installed using the flash-all.bat? Then you have stock recovery.
In bootloader, select "Recovery". When the small Android comes up, press Power Button + Volume UP. From the menu, select "wipe data/factory reset"
Hi friends,
I really hope somebody can help me out here..
My mum's Moto G 2014 (stock rom, just like it came out of the box, no tinkering, nothing) started acting weird. It had force-closes all over, nothing worked. So I boot into fastboot mode, select "Factory". The factory reset doesn't work - user data is clearly still there when I boot.
So I try wiping user data and cache with fastboot from the PC (linux). Command runs through, no error message. But the user data is still there when I boot - I still get 100 force-closes, the thing is unusable.
Next I go ahead and unlock the bootloader (which should wipe all data, right)? Again, userdata is still there when I boot.
Then I flash TWRP. But when I boot into fastboot and select "recovery", the screen just goes dark. Same after I flash CWM instead. (And the same, incidentally, as it was with stock recovery - selecting "recovery" just makes the screen go dark).
I am left clueless ... having voided the warranty by unlocking the bootloader. Any pointers?
Thanks, guys.
Power off your phone. When the screen goes black, press and hold the Volume Down button with one finger. Then, while still holding this button, press and hold the Power button with another finger. This will bring up the Bootloader menu, then tap the Volume Down button once to highlight Recovery Mode. From here, simply press the Volume up once, and TWRP recovery should come right up. Touch Wipe and you'll see the Factory Reset.
Tel864 said:
Power off your phone. When the screen goes black, press and hold the Volume Down button with one finger. Then, while still holding this button, press and hold the Power button with another finger. This will bring up the Bootloader menu, then tap the Volume Down button once to highlight Recovery Mode. From here, simply press the Volume up once, and TWRP recovery should come right up. Touch Wipe and you'll see the Factory Reset.
Click to expand...
Click to collapse
But I think as he said, he can't enter the recovery mode.
Did you try to flash a stock rom?
You're right, I missed that part about going dark when choosing recovery.
Lars124 said:
Did you try to flash a stock rom?
Click to expand...
Click to collapse
No - not yet. Where would I get the stock ROMs? I think I've got the XT1068 version of the phone, (Germany, dual-SIM).
Can I just flash the ROM with fastboot from the PC? Without having a custom recovery on the device? (as I said, flashing TWRP or CWM with fastboot didn't work, no error message but no success either).
EDIT: I now managed to get into the stock recovery - I just didn't know I had to press the Vol-Up-Key to confirm (and when the android on its back shows, then hold Power for a few seconds and tap Vol UP to enter the recovery). So I'm in the recovery now. However, selecting "wipe data / factory reset" still doesn't work. I get these error messages:
{
"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"
}
Doesn't look good, does it?
Thanks so much!
What commands did you enter when in download mode on the phone? What commands on the pc did you enter and what did your phone say in download mode while doing it?
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
dazeone said:
What commands did you enter when in download mode on the phone? What commands on the pc did you enter and what did your phone say in download mode while doing it?
Click to expand...
Click to collapse
First I entered
Code:
fastboot erase cache
The PC said:
Code:
erasing 'cache'...
OKAY [ 0.033s]
finished.
The phone said:
Code:
cmd:getvar:partition-type:cache
cmd: erase:cache
Then I hit
Code:
fastboot erase userdata
The PC said:
Code:
erasing 'userdata'...
OKAY [ 0.034s]
finished.
And the phone said:
Code:
cmd:getvar:partition-type:userdata
cmd: erase:userdata
So no error message there (unlike when I start a wipe/reset from the stock recovery). The userdata aren't erased in either case - all the apps are still there (and I'm bombarded with force-closes of all sorts of apps and services every 0.5 seconds)
Lars124 said:
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
Click to expand...
Click to collapse
Thanks! I'll definitely try that. But I don't dare get my hopes up after flashing CWM and TWRP didn't work (and factory reset neither). This really starts looking like a brick to me.
That's really strange.
Flash the stock rom and we will see what happens.
Lars124 said:
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
Click to expand...
Click to collapse
I downloaded and flashed all parts of the ROM in the order suggested in the .bat file. It turned out as I suspected: No error message (neither in fastboot on the PC nor on the device while flashing), but no change on the device. Even after flashing the stock ROM and erasing userdata and cache at the end of the process, my old apps are still there and nothing appears to have changed. Still getting a ton of force-closes, it's unusable.
It's as if the phone is in read-only mode, I erasing userdata or flashing new ROM doesn't do anything. The only thing I have to go on at this point are the error messages I posted in the photo above (after trying to wipe from the stock recovery:
Code:
Formatting /data
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed[/B]
Formatting /cache
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed[/B]
loxdp said:
I downloaded and flashed all parts of the ROM in the order suggested in the .bat file. It turned out as I suspected: No error message (neither in fastboot on the PC nor on the device while flashing), but no change on the device. Even after flashing the stock ROM and erasing userdata and cache at the end of the process, my old apps are still there and nothing appears to have changed. Still getting a ton of force-closes, it's unusable.
It's as if the phone is in read-only mode, I erasing userdata or flashing new ROM doesn't do anything. The only thing I have to go on at this point are the error messages I posted in the photo above (after trying to wipe from the stock recovery:
Code:
Formatting /data
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed[/B]
Formatting /cache
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed[/B]
Click to expand...
Click to collapse
This. I am also having exactly this problem (of endless force quits and inability to flash stock), with precisely the same error message when resetting from recovery. The thread I started '[Q] Custom Recovery Only Works By "fastboot boot"' turns out to have been the wrong title...it seems likely the reason I can't flash a custom recovery (despite unlocked bootloader) is the same reason I can't format partitions either (stock recovery can't, nor can TWRP format /data). Although adb shell can be used for manually formatting partitions, it is serious stuff not to be attempted casually ("instant expert" disease is a leading cause of death so I have not tried it.
Sadly, I can't offer you any help other than to add to link our threads in the hope that something I've discovered may lead a knowledgeable dev to the source of this problem.
Same problem here.
Any write operation fails, while fastboot claims anything was "OKAY".
Only "fastboot -w" gives some hint to the actual problem:
Code:
# fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.077s]
erasing 'cache'...
OKAY [ 0.014s]
finished. total time: 0.091s
However, I was not able to solve it.
I suspect this to be a hardware failure but I did not give up hope completely yet :-\
I have the exact same problem
Has anyone solved it yet?
bump
Thats seems to be my problem too.
With stock recovery and stock rom I didn't manage to wipe cache and user data. I also try it with fastboot but nothing. Nothing clear no erase at all.
Desparate and waiting a solution
Same problem - can't erase, can't flash.
Should ask help from Motorola Support.
Will call to their support and hope they will provide me 2nd level assist, not just advice to use warranty. No official Motorola in my country.
For anyone who would try to get support - chat on site is useless - they will tell you to do Wipe in recovery.
For additional support - call (US) Motorola Support 1-800-734-5870 and try to reach advanced support.
*Motorola chat support advised me to use Talkatone app to make a call, since I'm out of US.
**Get all of available phone docs - IMEI and other stuff.
I can't try their support since MotoG2 is of my girlfriends and is away now.
Support told me to call back only when I will hold the phone in my hands and will have IMEI to provide.
RSD Lite 6.2.4 works with Moto G, earlier versions would not work.
Same stuff - flashed ok but nothing changes.
If we use "mfastboot boot boot.img"
Device shows "updating android applications 1 of 7", then "Starting Android", but then black screen. Again.
But better than was - just black screen without any signs.
Is there any way to boot up different bootloader to get it's fastboot?
Anyone have tried to lock the bootloader, reflash the stock rom from fastboot and unlock again the bootloader?
A similar situation happened to me and this resolve the problem.
Poeta said:
Anyone have tried to lock the bootloader, reflash the stock rom from fastboot and unlock again the bootloader?
A similar situation happened to me and this resolve the problem.
Click to expand...
Click to collapse
When locking bootloader - reboot is required since no commands will work.
But after rebooting everything is still same. Bootloader still UNlocked.
Guys, what you think about this?
http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html
about partition images
Aaand this
http://android.stackexchange.com/questions/58027/updater-script-for-flashing-raw-partition-image
about dd flashing raw
Darksl1der said:
When locking bootloader - reboot is required since no commands will work.
But after rebooting everything is still same. Bootloader still UNlocked.
Guys, what you think about this?
http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html
about partition images
Aaand this
http://android.stackexchange.com/questions/58027/updater-script-for-flashing-raw-partition-image
about dd flashing raw
Click to expand...
Click to collapse
It seems to be a motherboard problem... Warranty.
hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
update 1: hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....
update 2: I got adb to work...gonna play with that and see if I can do anything.
update 3: Here is a link to a video showing what I am talking about when I say the "oneplus logo" just flashes...
Video starts out with me just pushing the power button..then it looks like it is going to boot up..then hits that decryption unsuccessful screen..so, I tap reset, at this point, it will reboot and attempt to go into the recovery partition and wipe data...but, you can see that it just reboots and the one plus logo flashes, screen goes black and eventually the notification LED turns solid white.
so, next in the video..I power the device off and try to manually enter recovery mode (vol- + pwr) and same thing, oneplus logo flashes and blank screen. Anyway, here is the link to the video.
https://goo.gl/photos/EU2ZSkFw1JrdExeQ8
update 4: Level 2 OnePlus Support did NOT fix the issue. He didn't even give me a reason when I asked what the issue was, however, I did see that it failed out when he attempted to use the MSM tool. he escalated to the next level of support.
I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads
cms062407 said:
hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
Click to expand...
Click to collapse
Can you try and install the file via normal, recovery?
Edu616 said:
Can you try and install the file via normal, recovery?
Click to expand...
Click to collapse
hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....
Bradl79 said:
I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads
Click to expand...
Click to collapse
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.
cms062407 said:
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.
Click to expand...
Click to collapse
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
going to try now! will update in a couple of minutes.
cms062407 said:
going to try now! will update in a couple of minutes.
Click to expand...
Click to collapse
best of luck, i hope it does work out for u
Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
{
"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"
}
cms062407 said:
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
Click to expand...
Click to collapse
what is the error u get when u try to unlock the bootloader via fastboot?
Bradl79 said:
what is the error u get when u try to unlock the bootloader via fastboot?
Click to expand...
Click to collapse
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.
Bradl79 said:
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.
Click to expand...
Click to collapse
sure, it wouldn't hurt to try to manually flash...but I bet we get the same error
cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
OEM unlock essentially opens up the system partitions to be writeable, so since your system is still locked, it makes sense that you can't flash anything. There are a number of OnePlus/Qualcomm unbricking tutorials that you can lookup, but you'll need the right files and I don't think anyone has made a full unbricking set of partitions with flash instructions for the OnePlus 3. I could be wrong though. I think there could be hope for your phone, just not quite right away.
thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.
Bradl79 said:
thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.
Click to expand...
Click to collapse
I think those partitions will be part of the final solution, but there has to be flash maps with them as well to correctly identify the sizes,locations, etc. Considering the OnePlus 3's level of developer support so far, I think a complete unbricking tutorial won't be far away.
@cms062407 - sorry that you're going through this, this is a little weird though, oneplus should have given priority to unlock bootloader even when the os doesnt work.. i mean what will people do if their phone soft bricks ? its a dead phone since you cant flash files, enter recovery or factory reset !! this is just stupid of oneplus.. but then again if this was the case anyone would steal a oneplus3 and use it as their own... damn this is messed up.
Thanks. But, there will be a fix, right?
Have you tried to just erase your userdata partition to remove encryption with the command
Code:
fastboot format userdata
Hope you'll get through.
cms062407 said:
Thanks. But, there will be a fix, right?
Click to expand...
Click to collapse
Even if bootloader is locked, there should be some recovery, OnePlus or twrp. Isn't it there?
HELP!
I installed platform-tools_r33.0.2-windows and UniversalAdbDriverSetup, now i'm trying to flash TWRP on the XA2 Phone by using this cmd command:
adb devices
- daemon not running, starting now at xxx
adb flash recovery twrp.img
- waiting for any device
What am i doing wrong?? Please help!!
{
"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"
}
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
LR7875 said:
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
How? Im pressing volume up and then connecting the phone to the pc, then i see a blue light. Is this fastboot mode? Thats what im already doing for 3 hours...
Yeah just did it again... volumeup+connect phone to pc, blue light appears on phone (fastboot mode i asume).
on pc in cmd i type adb devices, it starts the daemon.
then i type "fasboot flash recovery twrp.img"
result in cmd: "waiting for any device"
Wtf?
I swear this is so cancer can't handle this ****, the F is wrong with sony? This phone is buggy AF im trying to insall TWRP for like 4 hours now, this is a ****ing joke. What a waste of time.
Try the 15 seconds adb and fastboot driver if you haven't already
LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
This? https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
I doubt it will be any different from the platformtools adb? How could this help?
LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
You mean minimal adb ? or can you provide a link?
Connect the phone in fastboot mode (LED = blue) and open the device manager. Do you see the phone under "Other Devices" or "Android" with an exclamation mark? Then you need an ADB/bootloader interface driver. Get this for example:
https://developer.sony.com/file/download/xperia-xz2-driver/
(Yes, XZ2! There is no official XA2 driver)
Unzip it somewhere and force install the driver:
Right click on the device manager entry from above, "Update driver", "Browse my computer...", "Let me pick...", "List/show all...", "Have disk...", browse to the folder from above, open the selected .inf file and install.
Fastboot should work now. At least that's how I got it to work on a new PC.
BTW, just use "fastboot devices" to check whether it works. If your device doesn't appear, you don't need to try other fastboot commands - it won't work.
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Carljaynp03 said:
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Click to expand...
Click to collapse
Did you unlock the bootloader ?
Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
I agree with faraway, if i remember correctly when i had this issue i didn't unlock the bootloader.
I typed a specific number in the phone dial app and it said that the bootloader is unlocked, however there is another step you need to take that i had overlooked, you need a bootloader unlock code.
The code is free, not like with chinese spyware huawai they want your money for the code...
Unlock Bootloader - Open Devices - Sony Developer World
developer.sony.com
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-4
and use one of these commands in cmd/adb
fastboot flashing unlock
fastboot oem unlock
Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
irgendwer2 said:
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
Click to expand...
Click to collapse
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Privacydroid said:
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Click to expand...
Click to collapse
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
follow the next steps you mentioned use: fastboot flash boot recovery from LineageOS, and my phone went into a constant boot shutdown and restart, then this message appeared
and the bootloader is open
Shutdown the phone after flashing the recovery image (it doesn't seem like you did that). Then hold Volume Down + Power to boot into recovery.
irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
I get that the recovery is only for a temporary boot, when i tried it, it didn't work but i can't remember what the error was.
Today the A33 5G 128GB arrived, to flash twrp on it i had to enable oem unlock and usb debugging first in develeoper options.
To do that i had to complete the setup first, it's sick that the phone did NOT even let me complete the setup without connecting to the internet... this is out of control.
Now, i have oem unlock enabled aswell as usb debugging.
{
"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"
}
Next i connect the phone to PC and booted in download / odin mode.
Then i tried to flash this a33x_experimental_twrp.tar created by Zillion with odin, however as you can see on the next screenshot... the phone says "Custom Binary Blocked by OEM Lock"...
Why does the Phone say Custom Binary Blocked by OEM Lock even when i have it enabled in developer options??!
The Phone-Model is SM-A336B/DSN if that matters? I contacted my service provider from who i bought this phone and they told me that they are selling only this model.
Any help is welcome ...
My last hope is that someone from this forum can help me get twrp and lineage running, otherwise i'll have no choice but to return the phone within 14 days. No way i will use this device with the sick psycho spyware it contains.
PS: My only idea that might be worth a shot is booting twrp from adb terminal on pc, but i'm not sure how that works, how do i flash twrp permanently and how do i flash lineageos from adb, while i might be able to flash lineageos i'm not sure if that would work with the stock recovery..?
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
You can also use Adb ( Adb reboot download)
Privacydroid said:
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
Click to expand...
Click to collapse
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
V0latyle said:
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
Click to expand...
Click to collapse
Thank you Sir. i totally forgot about the bootloader, and i didn't know how it works on the newer models (android 12), thanks to your easy insturctions i was able to unlock the bootloader.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Privacydroid said:
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Click to expand...
Click to collapse
See Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
V0latyle said:
See Magisk installation instructions:
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
Click to expand...
Click to collapse
Well, i tried flashing twrp right now without using magsik, might have been a bad idea.. there's some error now.
Not really a surprise.. i never managed to brick a phone by all the idiotic things i'f done, no clue how to perceed now as the phone keep rebooting to the exact same screen with the exact same error message.
Did i damage the recovery?
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Arealhooman said:
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Click to expand...
Click to collapse
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
Privacydroid said:
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
View attachment 5790277
Click to expand...
Click to collapse
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Btw its in the AP file
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
Indeed the twrp i tried to flash is experimental and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Arealhooman said:
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Click to expand...
Click to collapse
Thanks, i managed to re-flash the stock firmware!
I actually didn't want to whole system (the os) the be re-flashed but only the recovery, however when i extract the AP file i do not get any recovery.img file.
`
Edit: i see recovery.img.lz4 (can i use that aswell to re-flash stock recovery, i never saw .lz4 whatever that is.
I tried flashing twrp with odin by placing it in the AP slot, so since that didn't work would it be worth a shot trying to flash it with adb via pc instead? Or is magisk a hard requirement now to bypass Vaultkeeper to be able and flash twrp?
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
actually theres a way of repacking using lz4 images, but i dont really know how to do it
Privacydroid said:
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
View attachment 5790319
Indeed the twrp i tried to flash is experimentla and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Click to expand...
Click to collapse
Wich device is that
*A33 TWRP was never meant for final users
The latest build was just a testing one