Develop Bugs

LG Phone returned from repair without OS

Hello,
I received my phone back from LG to fix the motherboard issue and it did not have an OS. Actually it did have an OS called Mini OS. The boot loader is locked and it won't verify proper google firmware when I adb sideload because it's using "test keys".
I was able to get root and adb into the device. Two questions:
1. Considering that I have root to the device, how can (is it possible) I put firmware to get back to a working state?
2. Because I have root on my device which is loaded with their keys and pre-OS flashed firmware, is there any value for the community here'?
Please forgive me if this is forbidden discussion and remove this post. I haven't been on XDA for more than a couple of years and don't know how things have changed.
Thank you.

FYI I fixed this issue. If you have this problem you can fix it by pushing twrp or other recovery to the device and dd-ing it to the boot loader block.
Let me know if you want help on this.
Also let me know if you want the system image I pulled from the stock weird LG manufacturer device.

Would be interesting to see, doubt it would be all that useful but interesting nonetheless
https://www.reddit.com/r/LGG3/comments/4g8d0p/g3_flash_tool_stuck_on_mini_os_screen_please_help/ This seems to be it running on a G3
https://www.youtube.com/watch?v=k8VWVzJJ0-U and on a G Flex2

This happened to me when i flash tot and unplug it before.
Sent from my Pixel using Tapatalk

Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.

AFK269 said:
Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification

konceptz said:
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification
Click to expand...
Click to collapse
I think that you will need to make a call to the service center to tell your situation.

I followed this and it booted just fine.

I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .

picodot said:
I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .
Click to expand...
Click to collapse
Hi @picodot , which bullhead image version did you use?

Bricked LG G3 [D855], cannot enter download mode

Hi, I was trying to flash a kdz to my LG G3 in order to downgrade the phone to 5.0. However, while the program start flashing and the progress bar on the phone reach 5%, the program shows " cannot reach the sever". The flashing process then stopped, no matter I keep clicking "retry".
As a result, I took out the battery and put it back attempt to get back to download mode.
However, the LG G3 do have a starting up screen as usual, but the phone didnt go in download mode, but get into black screen. The notification light is repetitively flashing blue and red color for couple second.
THe computer cannot detect the phone.
Any idea how I can save the 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"
}

Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana

Bananaphone64 said:
Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana
Click to expand...
Click to collapse
It can go into the recovery mode but not the normal OS. But what I can do in the recovery

voot566 said:
But what I can do in the recovery
Click to expand...
Click to collapse
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana

Bananaphone64 said:
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana
Click to expand...
Click to collapse
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"

voot566 said:
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"
Click to expand...
Click to collapse
drivers installed?

Bananaphone64 said:
drivers installed?
Click to expand...
Click to collapse
Yes, driver is installed :crying:
but windows doesnt seems to have detected my phone

Hm... i recently havent the stock recovery installed. I allways hat the possibility to use TWRP.

Thx so much, Bananaphone64.
I think what the real problem now is, the computer cannot recognize the phone. Anyone else have an idea?

In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana

Bananaphone64 said:
In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana
Click to expand...
Click to collapse
I have attempted on another computer, but the other computer also doesnt recognize the phone.
What is a SS?

A Screenshot or Picture from the Recovery Menu

Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS

I have seen that screen! 3 days before!
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!

yosmz1112 said:
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!
Click to expand...
Click to collapse
Yes. it was completely not able to enter into the download mode...........

Wh0CaREs said:
Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS
Click to expand...
Click to collapse
It is factory recovery. let me check the link, thx so much

deleted

Trying To Recover Data - recovery and system partitions wont boot

Hey all,​
Question: Can anyone offer any help recovering my data partition?
Problem: system and recovery partitions wont boot.
Why: I failed to fix a boot loop problem I was having. I tried to restore my system and recovery partition that I had backed up through TWRP. The restore failed and now I cannot boot into recovery mode (let alone system).
What I've Tried:
1. booting into a TWRP (booting TWRP image via fastboot off my desktop PC). FAILED
downloading boot.img completes ok.
I get an error when it tries to boot the image: "FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)"
my guess is my recovery partition system is broken.
Thoughts:
Can I flash my bootloader and recovery partitions from a stock ROM without interfering with my data?
can i do a partial flash (not a flashall.bat)? How?
I am not super familair with doing a partial flash. I have only ever ran flashall.bat on Google's stock ROMs.
Question: Does anyone have any ideas?
If you can help me out, I would love to buy you a 6 pack of beer!

I am recreating this thread in its proper place.
@XDHx86
XDHx86 said:
Can you boot to bootloader? Does fastboot detect your device?
Yes, fastboot detects the device. It lists my Pixel 3 XL a fastboot device and the Pixel 3 XL properly executes commands like fastboot reboot bootloader.
Other things I just tried:
I also tested the connection and I was also able to fastboot a TWRP.img (sailfish version--Pixel 1) for my Pixel 1 just now. So everything looks good on my desktop end. However, when I boot a TWRP.img (crosshatch version--Pixel 3) on the Pixel 3, the boot fails and gives the error i posted above.
I also tried three different TWRP.img revisions (including the oldest and newest revisions for the Pixel 3XL). None of the twrp.img images will load.

Here is the fastboot command and error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.

pritchfest said:
Here is the fastboot command and error.
View attachment 5254701
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.
Click to expand...
Click to collapse
I used this script when I ran into a similar issue before, you can use it to flash TWRP or sovle your bootloop.

@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.

pritchfest said:
@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.
Click to expand...
Click to collapse
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.

XDHx86 said:
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.
Click to expand...
Click to collapse
oh, no. As in, your suggestion might have worked but I didn't get to try it because I really needed to have my phone working for work. I didn't get to try your suggestion because in my haste I opted to just flash-all.bat and forefit the opportunity to recover my data.
After trying to flash several partitions separately and failing, including just the bootloader--and later just the recovery partition--, I kept getting the same error I wrote about above.

So you still get this error?? Even though you used the script, you still get the error?
Are you sure you have latest adb tools and device driver?
What about setting active partition first?
Try fastboot set_active a
Then fastboot boot twrp.img

As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
I can confirm I had the latest ADB setup.
I did not try your fastboot set_active a command before trying to fastboot into twerp.img. I can't say this wouldn't have worked.
The only other information I have is that on the fast boot screen, The triangle with an exclamation mark in it was colored red. Normally this triangle is a yellow color.
Hope that helps.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.

XDHx86 said:
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.
Click to expand...
Click to collapse
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.

pritchfest said:
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.
Click to expand...
Click to collapse
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.

Y
XDHx86 said:
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.
Click to expand...
Click to collapse
Yeah, it could be worse :/

Lineage on the Gigaset GX290 Plus - maybe the GS290 helps?

Hi there,
finally, after all this time living without, i was thinking about buying a smartphone. My first one. And i found a device that seems pretty nice, the Gigaset GX290 Plus (here is it's official website).
But i don't want to use "defalut-Android" and would love to install Lineage OS on it.
Sadly, that doesn't seem to be possible... or is it?
There are instructions for a very, very similar Gigaset phone - the GS290, for example here or there.
The GS290 is also available with the /e/ OS pre-installed (but i'd prefer Lineage OS).
And in the /e/ forum, this information from Gigaset states, that the GS290 and GX290 indeed are very similar. And as far as i can tell, the "Plus" version is just a minor update, but still having mostly the same hardware.
So... there are people out there having Lineage OS on the GS290. Thinking about the similarity to the GX290... could there be a chance to get Lineage running on this rugged phone?
Any ideas and thougts are welcome. Thank you!

Hello
I have had the same idea ..
As before i had installed /e/ on a samsung S9 + very easilywith the documentation and the software . Honestly i am not a real geek.
Before I had a Xcover with cynanogen mod and it took me some efforts to make it !
SO i had written to GS and /e/ about this matter .
GS : no communication and / Or knowledge of the situation ( but /e/ is selling already new GS 290 with /e/)
/e/: no answer yet .
I assume it could be possible , but not so easy .
BUT there is a big potential of buyers :
riders,hikers,building workers... needing a hard phone with long time battery and NO droid or gogol sttuff

Cheers, https://github.com/GS290-dev/android_device_gigaset_GX290-unified exists. Me or Erfan will probably create an proper thread here soon, with precompiled rom zips.

Hi @nift4, any update on this?
nift4 said:
Cheers, https://github.com/GS290-dev/android_device_gigaset_GX290-unified exists. Me or Erfan will probably create an proper thread here soon, with precompiled rom zips.
Click to expand...
Click to collapse

markdegroot said:
Hi @nift4, any update on this?
Click to expand...
Click to collapse
I'll create a fresh build and post it here in a few hours

https://dl.nift4.org/lineage/GX290/lineage-19.1-20220408-UNOFFICIAL-GX290.zip
Works fine in my testing, though I didn't try that build specifically. Please note that Android 12 is still kinda WIP, but report all issues you find.

Should I sideload this zip file?

whats-in-a-name said:
Should I sideload this zip file?
Click to expand...
Click to collapse
The concrete instructions are:
1. Unlock bootloader
2. Flash this recovery image: https://dl.nift4.org/lineage/GX290/recovery.img
3. Reboot to recovery
4. Sideload and factory reset

Bummer, it did not work. I have a gx290 (not plus)
E:failed to verify whole-file signature
E: error 21

whats-in-a-name said:
Bummer, it did not work. I have a gx290 (not plus)
E:failed to verify whole-file signature
E: error 21
Click to expand...
Click to collapse
Were there no other errors? Or a prompt asking you if you want to skip the verification?

Nice to see I'm not the only person with this phone. Overjoyed I unlocked my bootloader which, interestingly, didn't require fastboot oem unlock but instead fastboot flashing unlock and fastboot flashing unlock_critical. I then flashed the recovery - which seems to have worked - and sideload the version of the rom you provided. This has bricked my phone, as it won't progress past the bootloader and the unlocked bootloader warning.
I was - of course - fully aware of the risks, and realize it's probably my own fault, but I still don't really know what's wrong.

ewy0 said:
Nice to see I'm not the only person with this phone. Overjoyed I unlocked my bootloader which, interestingly, didn't require fastboot oem unlock but instead fastboot flashing unlock and fastboot flashing unlock_critical. I then flashed the recovery - which seems to have worked - and sideload the version of the rom you provided. This has bricked my phone, as it won't progress past the bootloader and the unlocked bootloader warning.
I was - of course - fully aware of the risks, and realize it's probably my own fault, but I still don't really know what's wrong.
Click to expand...
Click to collapse
If you get to the unlocked bootloader warning, can you get through to the recovery and format data? That might be enough to fix the soft brick

ewy0 said:
Nice to see I'm not the only person with this phone. Overjoyed I unlocked my bootloader which, interestingly, didn't require fastboot oem unlock but instead fastboot flashing unlock and fastboot flashing unlock_critical. I then flashed the recovery - which seems to have worked - and sideload the version of the rom you provided. This has bricked my phone, as it won't progress past the bootloader and the unlocked bootloader warning.
I was - of course - fully aware of the risks, and realize it's probably my own fault, but I still don't really know what's wrong.
Click to expand...
Click to collapse
GX290_android9_2019-07-31.zip | by gajus for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
you can go back to stock android 9 with flashtool (windows)
I did this five times at least, experimenting with the different buillds.

whats-in-a-name said:
GX290_android9_2019-07-31.zip | by gajus for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
you can go back to stock android 9 with flashtool (windows)
I did this five times at least, experimenting with the different buillds.
Click to expand...
Click to collapse
A precondition to installing is having Android 10 installed so don't forget to update afterwards

I loaded three updates, now on Android 10
1. fastboot flash recovery recovery.img
2. power down.
3. volume UP and power, release power button.
4. in custom recovery, factory reset + clear cache
5. sideload lineage
6. reboot to system
phone hangs at bootlogo.
{
"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"
}

whats-in-a-name said:
I loaded three updates, now on Android 10
1. fastboot flash recovery recovery.img
2. power down.
3. volume UP and power, release power button.
4. in custom recovery, factory reset + clear cache
5. sideload lineage
6. reboot to system
phone hangs at bootlogo.
View attachment 5605575
Click to expand...
Click to collapse
Edit: Does it hang or reboot?

Apparently both you have that issue which is strange as it works for me, I'll try to replicate what you guys did and report back, thanks for the feedback

nift4 said:
Edit: Does it hang or reboot?
Click to expand...
Click to collapse
It hangs at: orange state
this device cannot be trusted
wait for 5 seconds to boot (which takes forever)

I'm back to stock Android 10, installed custom-recovery and boot into recovery, all well. But after that, when I boot into system once... I cannot boot into custom recovery, I get the stock recovery back. So it is not persistent.

whats-in-a-name said:
I'm back to stock Android 10, installed custom-recovery and boot into recovery, all well. But after that, when I boot into system once... I cannot boot into custom recovery, I get the stock recovery back. So it is not persistent.
Click to expand...
Click to collapse
That is wrong, it is persistent. It's just that system is overwriting recovery to make your life more annoying

Question I think i may have bricked my device help pls

Hey guys i think i may have bricked my device, i keep getting this error whenever i try to use miflash to flash back to stock rom
{
"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"
}
Does anyone know how to fix this? i keep bootlooping back into fastboot mode and whenever i try to restart system it says no os installed

Try redownloading the ROM and the latest version of Mi Flash. Reboot PC and phone.
Go to Mi Flash's Configuration and check "Verbose" and "Erase all", and remove the argument in "CheckPoint".
Also, "Clean All and Lock" is selected in the bottom right corner, keep that in mind, because it'll lock your bootloader once the Flash succeeded.
If you don't want that happening, check "Clean All".
Make sure there are no spaces in the whole ROM path, and perhaps also try a different USB port, or a different cable.
Also, plug in the USB cable after you rebooted Fastboot Mode. Fastboot Mode may stop accepting input after an initiated Flash, so to try and flash again you may need to reboot Fastboot Mode again.
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com

newbo1211 said:
Hey guys i think i may have bricked my device, i keep getting this error whenever i try to use miflash to flash back to stock rom
View attachment 5405925
Does anyone know how to fix this? i keep bootlooping back into fastboot mode and whenever i try to restart system it says no os installed
Click to expand...
Click to collapse
Lucky that it failed... Always remember to disable lock before flashing otherwise you will really brick the phone.
Try a different firmware like eea 12.5.3, that one is the only one I can confirm to be working in all circumstances

Rstment ^m^ said:
Lucky that it failed... Always remember to disable lock before flashing otherwise you will really brick the phone.
Try a different firmware like eea 12.5.3, that one is the only one I can confirm to be working in all circumstances
Click to expand...
Click to collapse
No it doesn't brick the phone. It only locks the bootloader when the flash succeeded.

dreamytom said:
No it doesn't brick the phone. It only locks the bootloader when the flash succeeded.
Click to expand...
Click to collapse
Man off my dik. Ur setting this guy up for a massive headache , yes It bricks it the phone , the hardest way possible when you have no idea what you're doing and are following advices like this. Using community tool to lock bootloader ( Your only way of interacting with this phone ) when you don't even know how the flash went is pure fkin stupidity.
Locks bootloader assuming the phone is fully functional but what if it's not? Then you can't try again , you're screwed. No flashing anymore.
CRC bypass for example like what he's having issues with will flash just fine , report 0 problems but phone doesn't boot. What if he follows one of the many guides out there , removes CRC and then goes flashing ?
Therefore your answer above is nothing but bs. Bad flash is soft brick , locking bootloader after bad flash is a much harder brick

Rstment ^m^ said:
Man off my dik. Ur setting this guy up for a massive headache , yes It bricks it the phone , the hardest way possible when you have no idea what you're doing and are following advices like this. Using community tool to lock bootloader ( Your only way of interacting with this phone ) when you don't even know how the flash went is pure fkin stupidity.
Locks bootloader assuming the phone is fully functional but what if it's not? Then you can't try again , you're screwed. No flashing anymore.
CRC bypass for example like what he's having issues with will flash just fine , report 0 problems but phone doesn't boot. What if he follows one of the many guides out there , removes CRC and then goes flashing ?
Therefore your answer above is nothing but bs. Bad flash is soft brick , locking bootloader after bad flash is a much harder brick
Click to expand...
Click to collapse
No, I agree that he shouldn't accidentally lock his bootloader.
However, choosing to lock the bootloader in Mi Flash won't brick the device.
The command for locking the bootloader comes only at the end.
If any errors occur before that, the script will terminate.
If any of the commands prior to "fastboot oem lock" don't execute successfully, it simply will not lock the BL.
The .bat-files are the logic behind the Flashing-process in Mi Flash.
It's not necessary to use Mi Flash. You could use the naked .bat-files, but I wouldn't recommend it. Mi Flash provides additional info.
About removing the CRC commands to skip CRC errors: I don't have a ROM on my drive to check what those exact commands are, but it's probably not recommended.
I think it's only safe to remove the Anti-Rollback Commands.
I do agree that there's a lot of misinfo out there, and that you need to be careful.