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 :/
Related
Dear Xda,
This is my situation, i had a bootloop so i ran the temporary recovery method explained in the thread "Nokia N1 Rooted with Google Play!" in the general forum of the Nokia N1
But i accidentaly removed the system partition (which boots the system and shows the boot animation etc, after the splash screen)
I can however boot into the bootloader with volume down+power as well as going into the temporary recovery to wipe and flash stuff.
I figured a way to fix this, this is to push or copy a update.zip from my pc (with the original nokia n1 files) to my nokia n1,
but the problem is adb does not recognize this device in the cmd with the command adb devices, and the hardware id is having ???? in device manager (Windows).
Does anyone maybe know a way to push files to this device in either bootloader mode or temporary recovery or maybe another way, as i am stuck with this.
If something is not clear or if i need to post images of my situation of more information please say so,
also i have the taiwanese version not the chinese and i have also all the zip files for android 5.0.1 and 5.1.1 (latest) which 1 of the 2 i need to push to my device to restore the system partition.
Ok, so far i have not gotten an answer from someone,
so i went to look around other forums and identical devices, the closest being the zenphone 2, as they use the same intel processor the intel atom z3580.
I have also looked around alot in the nokia n1 forums on search for the original taiwenese firmware as i have found a way to custom flash the device if it is hard bricked (as in no adb, system or recovery)
I found out that the new intel phone flash tool required a flash.xml file to (re)flash firmwares in order to restore it, so i have been googling around for older phone flash tool programs as i have stumbled upon a nokia n1 thread somewhere where it showed a picture of a custom flash (without the flash.xml file)
I have managed to get a fastboot connection with an old intel phone flash tool program and been trying to flash chinese firmwares to it, but so far it keeps on failing for some reason
I have a feeling that it might be possible to resurrect a broken nokia n1 with the right firmware when you only have access to the fastboot (power up+volume down), we might as well use this method if succesfull to fix bootloops if no recovery is available (as it was with my taiwanese version for some odd reason)
I will attach screenshots of what i have so far, if anyone is interesting in helping me or have an idea please say so.
p.s. i keep on trying to do more research and fiddle more with it, as it cant be more broken than it is now.
{
"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"
}
Sadly, i can not go on any further, i have tried and flashed to much files and the nokia bootloader has locked itself, neither does oem unlock commands work with a fastboot flash file, i feel like i was very close to recover the nokia n1, but now it will forever be paperweight, as i have no recovery, no system, no adb, and a locked bootloader so no fastboot anymore.
If anyone have a solution or advise i'm open for this, but until then i can not proceed to test further for people who have like me bricked their device and turned it into useless paperweight (and i feel like the nokia was really vulnerable for bricking) i kinda regret buying the nokia now though.
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
2111002640 said:
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
Click to expand...
Click to collapse
Yes i do have, do you perhaps know which CN version you had? if not i can attach/link you a CN version.
It is possible to install the same or newer Version of the Firmware, which was installed on your N1
You need a full Firmware package for your tablet (CN or TW Version).
Sent from my N1 using Tapatalk
do you have full ROM for N1 tw or cn, if you have this can you share for me plêas
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
2111002640 said:
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
Click to expand...
Click to collapse
I don't have a Facebook account. Could you post your solution on here please? Thank you
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
srsface said:
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
Click to expand...
Click to collapse
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
defendos said:
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
Click to expand...
Click to collapse
It's been a week and it was the first time I ever tried to flash anything, but I think that in fastboot I just selected recovery mode with the volume buttons and then pressed the power button to confirm the selection. Since I had previously managed to flash in a recovery image of the Taiwan version, it worked. My saviour was that the recovery image wasn't corrupted even though my Android itself was, so I guess there was no magic trick - I just managed to do the right things finally after wrong physical button presses. If you can't get to recovery then maybe you are truly bricked. Would these suggestions be of any help? forums.oneplus.net/threads/solved-stuck-in-fastboot-bootloader-is-locked-need-help.435522/
same boat bump!
accidently wipe data cant boot stuck on android logo
i can access fastboot but no adb (unauthorize)
on 5.0.2
I tried to follow directions here but in my haste and stupidity I may have followed incompatible directions.
Here's where I'm at. I have TWRP 3.0.2-M1 installed. I cannot install any system images and have them run (CM13 for example). I've tried unlocking my bootloader with no success.
I don't know what to do. I cannot load any images properly, but I am desperate to get things going. Am I totally screwed?
Would really, really appreciate direction. ZE551ML. I want the nightly CM13 image to run on my phone.
When I start my phone up, I get the Red Error that tells me my system isn't verified.
Please, please help.
EDIT: I have no OS installed.
You can boot into twrp.
Your bootloader is unlocked with the warning screen .
Do you know how to flash a Rom ?
What did you use to unlock ?
If you want people to help you need to describe what you used and why
timbernot said:
You can boot into twrp.
Your bootloader is unlocked with the warning screen .
Do you know how to flash a Rom ?
What did you use to unlock ?
If you want people to help you need to describe what you used and why
Click to expand...
Click to collapse
Yes, I tried to a flash a ROM but it keeps putting me back in the Recovery.
I used Giarmix's automatic tool to unlock and it said FAILED but I guess it worked once to get me TWRP.
I'm sorry, I'm trying to provide as much info as possible.
roach9 said:
Yes, I tried to a flash a ROM but it keeps putting me back in the Recovery.
I used Giarmix's automatic tool to unlock and it said FAILED but I guess it worked once to get me TWRP.
I'm sorry, I'm trying to provide as much info as possible.
Click to expand...
Click to collapse
Giovix modder tool ?
There is an option to return to stock.
Or gimme link to the one you used if not this one
timbernot said:
Giovix modder tool ?
There is an option to return to stock.
Or gimme link to the one you used if not this one
Click to expand...
Click to collapse
Yes, that one. Returning to stock doesn't work.
I also ran the following program in an attempt to get TWRP 3.0.2-M1 to install CM13:
M_BL_upgrade_for_zf2_551ml_6.0
After this, nothing works anymore.
EDIT: TWRP 3.0.2-M1 is installed, but when I go to install a ROM, I get an error:
When I try to wipe any partition, I get "ARGUMENT INVALID".
Sigh
You put the extracted folder in C/: of PC and run batch as admin?
timbernot said:
You put the extracted folder in C/: of PC and run batch as admin?
Click to expand...
Click to collapse
What extracted folder are you referring to?
Modder
timbernot said:
Modder
Click to expand...
Click to collapse
I have been running as admin and certain commands did work, but this is not. I erased my system/cache partitions in a panic.
{
"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"
}
EDIT: Is there a magic thing I can do within TWRP? **** I'm an idiot.
Can you fastboot flash stock recovery ?
Can you get into fastboot to flash stock recovery too ?
I flashed the newest stock recovery but it didn't work, I can only boot into my bootloader now.
I tried ASUS Flash Tool and it sees my device but it remains "Connected" and doesn't want to install the .raw file.
Wow just wow.
I'm going to bed lol
timbernot said:
Wow just wow.
I'm going to bed lol
Click to expand...
Click to collapse
Sigh.
I am an idiot. Thank you for trying ot help.
I will help later but need some rest
timbernot said:
I will help later but need some rest
Click to expand...
Click to collapse
I truly appreciate your time and assistance.
Okay, here's the issue I have.
When I install CM13 and GApps, it works fine. System patched unconditionally, success, etc.
When I reset my system, I get a red screen that says "Your device has failed verification and may not work properly. Go to www.g.co/ahg (just a guess)"
Then it boots back into my recovery, where normally, it should have gone to CM.
What gives? I have no idea what to do.
I tried to use the Asus Flash tool but it cannot install to my device.
I can still use fastboot.
I suspect that my problem is that I installed a MM Bootloader without rooting or without unlocking properly and it's not all effed.
I want to cry.
EDIT 2: I've spent all night doing this. I followed this:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
But then I got caught up. xFSTK wasn't work so I unplugged my USB, BUT THEN IT STARTED RUNNING when it was unplugged?! But GET THIS. CM 13 RUNS.
But now when I turn on my phone, I get a weird line screen and I cannot boot into my Recovery OR my Bootloader. I can only load my ROM.
What the **** is going on?!?!?!?!?
Android version before bricking device?
CM 13, so Marshmallow.
Now the screen won't even turn on. This is ****ed.
EDIT: No screen at all. Nothing works. In boot cycle. Sending it to Asus and hopefully they fix this and send me it back. I'm never unlocking the bootloader or rooting, or doing anything to a phone ever ****ing again. This should not be that hard to do.
If u can boot cm then u can install recovery using adb
Download the latest recovery image file (.img) depending on which bootloader u have (MM/L).
Place it in the root of your /sdcard folder and rename it to twrp.img.
Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery
Recoveries link http://theflamingskull.com/zenfone2.html
roach9 said:
CM 13, so Marshmallow.
Now the screen won't even turn on. This is ****ed.
EDIT: No screen at all. Nothing works. In boot cycle. Sending it to Asus and hopefully they fix this and send me it back. I'm never unlocking the bootloader or rooting, or doing anything to a phone ever ****ing again. This should not be that hard to do.
Click to expand...
Click to collapse
Wow and wow and more wow !
1)What firmware did you have on when you first used the modder ..........?
2)You can use the unbrick procedure in my signature below !
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?
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
Greetings everyone!
I'll try to resume my case:
I unlocked the bootloader like 3 weeks ago, installed the eu rom and everything was working fine. Today I decided to flash Arrow OS and the process finished succesfully, but I was having a lot of reboots, so I decided to go back to stock.
I entered fastboot mode, and after that, launched xiaomitools (latest version), selected the "my device is bricked, fastbood mode" and then it started to download the latest firmware and then it tried to flash it.
It flashed some img's but it got stuck when the program tried to flash the "super" img, I got an error message, I choose the "try again" option, and left the phone for like 20 minutes, nothing happened, the program got stuck trying to flash the super.img.
After that, I downloaded the latest MiFlash and tried to flash the stock firmware, but it won't finish, after 1,200 seconds, it shows a timeot and an 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"
}
Does anyone know what can I do in order to flash the stock rom again? D=
My device is unlocked:
Thank you guys!
have you tried a USB 2.0 port? can be fussy about the ports...
also, which rom version are you flashing, do you have the exact title?
Not sure why it's timing out offhand (i am not overly experienced with xiaomi either), but super.img does take quite some time... but not 20mins, strange
Have you tried clicking 'driver' tab in miflash and installing necessary drivers?
I like the title of your thread, seems like you did some searching on the forum for answers before you decided to make the post!
I'm pretty sure the experts on this forum will be able to provide you with some assistance.
Too bad I'm not much help in terms of unbricking steps, I don't have any experience with it since I've haven't bricked a device before.
Good luck!
deleted...
Thank you for your answers guys!
The exact version of the rom that im trying to flash is:
alioth_global_images_V12.0.3.0.RKHMIXM_20210416.0000.00_11.0_global_b716fd8a83
Also, I tried editing the flash_all.zip taking out the "crc" lines (2 lines) and after that I'm trying to flash the rom via cmd adb, so far it seems it's working, super just finished flashing and now the rest of the rom is also flashing.
I'll report back when it finishes!
Ok, the rom finished the flashing process:
The device rebooted, showed the initial logo and then it got into a bootloop.
After I don't know, 20 restarts from the bootloop, it entered in fastboot mode.
Meh, I don't know what to do anymore. D=
I don't know if this has something to do, but on the arrow os flashing instructions, you had to flash their boot and vendor images:
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot --set-active=a
I suposse that those images get replaced by the stock ones when you install the stock rom, am I right?
Also, when I restart the device, it goes directly into fastboot mode in like .5 seconds.
D=
If it fails for some reason.. could try what Dadovvv writes here
Kimbaroth said:
Ok, the rom finished the flashing process:
View attachment 5326777
The device rebooted, showed the initial logo and then it got into a bootloop.
After I don't know, 20 restarts from the bootloop, it entered in fastboot mode.
Meh, I don't know what to do anymore. D=
I don't know if this has something to do, but on the arrow os flashing instructions, you had to flash their boot and vendor images:
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot --set-active=a
I suposse that those images get replaced by the stock ones when you install the stock rom, am I right?
D=
Click to expand...
Click to collapse
yes, they all get replaced by stock again. see my post above, Dadovvv recommends to run flash_all.bat directly without miflash if you're having issues. kinda forces the flash i guess. up to you though
reg66 said:
yes, they all get replaced by stock again. see my post above, Dadovvv recommends to run flash_all.bat directly without miflash if you're having issues. kinda forces the flash i guess. up to you though
Click to expand...
Click to collapse
Yup, that's what I did, i ran the flash all script in order to flash everything, but when it finishes, it reboots and bootloops for like 20 loops and then enters fastboot mode.
If I try to enter recovery, it also goes straight to fastboot mode.
reg66 said:
have you tried a USB 2.0 port? can be fussy about the ports...
also, which rom version are you flashing, do you have the exact title?
Not sure why it's timing out offhand (i am not overly experienced with xiaomi either), but super.img does take quite some time... but not 20mins, strange
Have you tried clicking 'driver' tab in miflash and installing necessary drivers?
Click to expand...
Click to collapse
atm i changed the usb port from 3.0 to 2.0 and tried by 2ble clicking the flash_all.bat, it's flashing the rom again.
I'll report back when it finishes.
Kimbaroth said:
Yup, that's what I did, i ran the flash all script in order to flash everything, but when it finishes, it reboots and bootloops for like 20 loops and then enters fastboot mode.
If I try to enter recovery, it also goes straight to fastboot mode.
Click to expand...
Click to collapse
hmm. a couple more possible solutions...
1. try this tool, it includes an older version of miflash under one of the tabs (no need to sign in, just close the mi account box that opens) and try flashing from there. scrap that, i thought that tool linked to it's own older version of miflash, but it doesn't... my bad
2. it could be as simple as a factory reset that's needed... could fastboot boot twrp, factory reset typing 'yes', power off the device and try booting to system once more...
(sorry!) and a quick question, before flashing arrowOS, did you come from stock 12.0.3 like you said above or did you have a later version of stock or xiaomiEU?
---- i'm wondering if miflash is thinking you're trying to downgrade and won't flash because of ARB. (although i would have thought you would get and error message before the flash started if this was the case... anyhow, can't see how it would hurt to try without the ARB checks. i would advise checking your ARB (anti rollback) status before, just to be on the safe side... see my post here
I'm go
reg66 said:
hmm. a couple more possible solutions...
1. try this tool, it includes an older version of miflash under one of the tabs (no need to sign in, just close the mi account box that opens) and try flashing from there.
2. it could be as simple as a factory reset that's needed... could fastboot boot twrp, factory reset typing 'yes', power off the device and try booting to system once more...
(sorry!) and a quick question, before flashing arrowOS, did you come from stock 12.0.3 like you said above or did you have a later version of stock or xiaomiEU?
Click to expand...
Click to collapse
I'm gonna try your 2nd solution, lets see if it works, ifthat doesnt works i'll try the miflash solution.
And I was on the 12.0.3 firmware before flashing the latest eu rom, after that I just installed the rom with their instructions (using their recovery, not TWRP) and aaaaaafter that, i tried to go back to stock and this hell started =(
Kimbaroth said:
I'm go
I'm gonna try your 2nd solution, lets see if it works, ifthat doesnt works i'll try the miflash solution.
And I was on the 12.0.3 firmware before flashing the latest eu rom, after that I just installed the rom with their instructions (using their recovery, not TWRP) and aaaaaafter that, i tried to go back to stock and this hell started =(
Click to expand...
Click to collapse
ahh ok.... so yeah, try a factory reset in booted twrp. But, see my other post after regarding ARB. i suspect that's the issue. xiaomiEU is a later version than the stock you are trying to flash... you need to take out some lines in the flash_all.bat by changing the .bat to .txt
remove all lines near the top regarding ARB (but leave all fastboot lines intact), save, exit, change back to .bat and run it again in miflash
reg66 said:
ahh ok.... so yeah, try a factory reset in booted twrp. But, see my other post after regarding ARB. i suspect that's the issue. xiaomiEU is a later version than the stock you are trying to flash... you need to take out some lines in the flash_all.bat by changing the .bat to .txt
remove all lines near the top regarding ARB (but leave all fastboot lines intact), save, exit, change back to .bat and run it again in miflash
Click to expand...
Click to collapse
My ARB # is 1, the ARB # of 12.0.3 is 0 (lower than mine), so... just taking out the anti version lines from the .bat it will work?
Edit: I'm flashing the .bat without those lines, I'll report back.
Kimbaroth said:
My ARB # is 1, the ARB # of 12.0.3 is 0 (lower than mine), so... just taking out the anti version lines from the .bat it will work?
Click to expand...
Click to collapse
well sorry to report i can't say for certain. i had that issue but ended up flashing stock 12.0.5 rom (still lower than the xiaomiEU version i had before. all went fine. So yeah, basically i haven't tried on 12.0.3. But... i think the arb = 1 on your device simply means arb is not activated yet. so i would assume any version is fine to flash, just by removing said lines from the bat file...
sorry, no promises though. do so at your own risk hopefully someone else in the 'know' will be able to chip in...
DONT DO IT
not sure sure this applies to your/our device but for poco f1
'Don't flash a ARB 0 firmware/ROM onto an ARB 1 device. Even though some people disagree, they cannot link to success stories. Likely, this concerns very old firmware.' taken from here
One moment, i'll link you to 12.0.5 fw that has arb=1 which i've rolled back to myself...
reg66 said:
well sorry to report i can't say for certain. i had that issue but ended up flashing stock 12.0.5 rom (still lower than the xiaomiEU version i had before. all went fine. So yeah, basically i haven't tried on 12.0.3. But... i think the arb = 1 on your device simply means arb is not activated yet. so i would assume any version is fine to flash, just by removing said lines from the bat file...
sorry, no promises though. do so at your own risk hopefully someone else in the 'know' will be able to chip in...
Click to expand...
Click to collapse
OMG, it worked!
I removed the anti rollback comments and the crc check ones from the flash_all.bat, flashed the firmware via miflash and miflash showed an error:
But miui started booting on the phone! =D
THAAAAAAAAAANK YOU!!!!!!!!!
To flash the latest stable release (it was released today AFAIK, miui_ALIOTHGlobal_V12.5.1.0.RKHMIXM_e9845255d6_11.0) can I just flash it via TWRP, right?
THANK YOU THANK YOU THANK YOU!!!
Kimbaroth said:
OMG, it worked!
I removed the anti rollback comments and the crc check ones from the flash_all.bat, flashed the firmware via miflash and miflash showed an error:
View attachment 5326791
But miui started booting on the phone! =D
THAAAAAAAAAANK YOU!!!!!!!!!
To flash the latest stable release (it was released today AFAIK, miui_ALIOTHGlobal_V12.5.1.0.RKHMIXM_e9845255d6_11.0) can I just flash it via TWRP, right?
THANK YOU THANK YOU THANK YOU!!!
Click to expand...
Click to collapse
well thank FcK for that!!! so you flashed the 12.0.3 rom right?
and yeah... for 12.5.1 stable (at least what i did is...) fastboot boot twrp. copy twrp.img over to phone, go to advanced and select 'install to ramdisk' then flash your twrp.img. Reboot twrp, copy over rom and flash, factory reset after and boot (going from memory, but pretty sure that's it. back on arrowOS right now, so can't verify)
BTW, after flashing with miflash - it seems to always give that error at the end. i just assumed it's because the 'lock' cmd wasn't run/requested. maybe it's a bug, who knows!!
reg66 said:
well thank FcK for that!!! so you flashed the 12.0.3 rom right?
and yeah... for 12.5.1 stable (at least what i did is...) fastboot boot twrp. copy twrp.img over to phone, go to advanced and select 'install to ramdisk' then flash your twrp.img. Reboot twrp, copy over rom and flash, factory reset after and boot (going from memory, but pretty sure that's it. back on arrowOS right now, so can't verify)
BTW, after flashing with miflash - it seems to always give that error at the end. i just assumed it's because the 'lock' cmd wasn't run/requested. maybe it's a bug, who knows!!
Click to expand...
Click to collapse
Yeah, I flashed 12.0.3 taking out those lines (the anti rollback ones and the crc check ones), miflash gave me an error at the end, but it worked lol
I think i'm gonna stick with the latest stable firmware for a while. I really wanted to try Arrow OS, but as I said earlier, after flashing it it gave me a lot of crashes/reboots, do you know by any chance why that happened?
Thanks again man!!! I learned something new today thanks to you! =D