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
Related
I know what you are thinking: "Another root/flash tutorial??, it's already explained multiple times right?"
Yes that's true. But for some reason it did not work when I followed the exact steps described (I tried it on 2 different elephone P8000 phones), and I believe I'm not the only one so i created this post to help others.
I folled these step: bbs.elephone.hk/thread-6616-1-1.html#.VkcZqL8WCnN (the guide link in the "Eragon v.5.9.2" thread.
Flashing instructions:
1. Install the usb drivers and reboot your PC.
(Download link: mega.co.nz/#!55BQkKiR!OPBrnj7SXxsUbuchAjV8orT9SMAOMpbDesYTMO2DDHY)
2. Check if the drivers are installed correctly.
Go to "Device manager" on your windows PC and check if there are no yellow question marks appearing when connecting the phone to the PC3. Download the flashtool and firmware you would like to flash:
Latest version of the Flash tool: (androidmtk.com/smart-phone-flash-tool)
Stock Rom from official forum: (bbs.elephone.hk/forum-270-1.html#.Vkcc878WCnM)
Eragon ROM: (forum.xda-developers.com/elephone-p8000/development/rom-06-9-eragon-1-0-android-5-1-t3195007)
Philz recovery Touch 6.59.0 Port P8000 Version 2: (forum.xda-developers.com/elephone-p8000/development/recovery-philz-touch-6-59-0-port-p8000-t3224478)
?CWM Recovery (didn't work for me): (bbs.elephone.hk/thread-6616-1-1.html#.VkceZL8WCnN)
4. Open the flash tool and select the scatter download file included in your firmware you downloaded.
!the next steps differ from every tutorial I've read but seem to work perfectly.
5. Turn your phone on (normal no recovery).
6. Click on the download button in the flash tool.
7. turn your phone off (the normal way)
8. The flashing should automatically start while the phone is turning off.
9. Wait for the conformation in the flash tool (green check mark).
10. Remove the usb cable from the phone and hold to power button till the phone boots.
To root:
Just install superSU from the playstore and root. (confirm with rootchecker app, also from the playstore).
If that does not work for you. Install a custom recovery following the flash instructions above. Put de SuperSU binary's on your sd card. Boot into recovery by turning off your phone. Now hold the power and volume up buttons till you see a selection menu. Select "recovery" with the volume up button and confirm using the volume down button. In recovery use the install from zip function to install the superSU binary's.
To install latest stock firmware:
Follow the flash instructions and flash the stock ROM. I recommend doing this instead of updating from the phone itself. Because I updated the firmware from the phone itself to the latest firmware using the updater on the phone and there were some small bugs. After flashing everything worked perfectly.
(sorry the links are not clickable, Because I'm a new user with <10 post I can't add clickable links in the threats i create)
I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?
elerraoind said:
I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?
Click to expand...
Click to collapse
Please use google.
"Flashing a custom ROM" basically means to load a different version of the Android OS. This site actually explains it very well. A custom ROM is the full Android OS customized by the ROM builder usually to make it faster, provide better battery-life or add new features.
AOSP ROMs like CyanogenMod offer stock Android which will remove things like HTC's Sense or Sprint's Apps. CyanogenMod's ROM is one of the more popular ROM.
Other Roms like Fresh 3.5 offer a ROM very similar to the default experience (with added speed and battery-life) by leaving Sense (or whatever skin your device has) and incorporating over the air updates into an updated version of the ROM.
In order to flash a custom ROM you must first root your device. For information about rooting see Matt's comment on the OP or my original answer below:
When I had the same question this is where I found it: .talkandroid.com/7686-what-is-rooting-and-why-should-i-do-it-the-pros-cons-of-android-rooting
Depending on what device you have the rooting method will be different though. Personally I suggest reading up on your device at XDA.
Click to expand...
Click to collapse
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom
vetkak said:
Please use google.
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom
Click to expand...
Click to collapse
Appreciate your detailed response. Thanks.
Flashing Problem
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris
xhris1337 said:
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris
Click to expand...
Click to collapse
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000
bjbirch said:
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000
Click to expand...
Click to collapse
Cheers for the reply, I should have mentioned that I tried that also and it still says "there is no SU binary installed, and superSU cannot install it" I found OEM unlocking yesterday and it got my hopes up then shot me straight back down, I was hoping that it OEM unlocking was the reason I could not access recovery,
Thanks again, Chris
To access recovery, switch phone off completely, then press power and volume UP together, you will see three options in tiny white writing,use the volume UP to move marker to recovery which is the first option, then press volume DOWN to choose recovery, you will get a screen with a green android man with a red triangle, you then have to press power and then volume up this should get you into recovery
If recovery is broken. Turn off the phone, connect to PC. Open flashtool. Load philz recovery. Click in download. Turn phone on and flashing should start automaticly. Hope this helps
Verstuurd vanaf mijn Elephone P8000 met Tapatalk
I think it's easier when you use Kingroot for root and Flashify for the recovery
ok sp flash tools wont let me flash just a recovery. It wants me to format and flash the whole phone which wipes out my imei. any suggestions?
{
"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"
}
No matter what I try, my computer will not install the drivers. I keep getting "A service installation section in this INF is invalid". Any ideas on what to do?
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
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?
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 :/
I recently upgrade to realme UI 2 beta but decided to roll back. So I downloaded my rom from the official website. And entered recovery mode and Install from the phone the ROM installed and then It prompted me to reboot. I rebooted the device but now It stuck in the infinity boot loop and restarts after the Realme Logo in white fonts... My bootloader is locked... Experts, please guide me on what went wrong and how can I fix this.. As it's a holiday in India, Service centers would be close for 2 days. But since this is my only phone, 2 days is a looooong period. Please Help
really bad decision to install rom when you have locked bootloader have u tried factory reset via recovery mode?
Recovery mode is not accessible when pressing (power + vol down). Is there any other way to do so??
anonymous178 said:
I recently upgrade to realme UI 2 beta but decided to roll back. So I downloaded my rom from the official website. And entered recovery mode and Install from the phone the ROM installed and then It prompted me to reboot. I rebooted the device but now It stuck in the infinity boot loop and restarts after the Realme Logo in white fonts... My bootloader is locked... Experts, please guide me on what went wrong and how can I fix this.. As it's a holiday in India, Service centers would be close for 2 days. But since this is my only phone, 2 days is a looooong period. Please Help
Click to expand...
Click to collapse
I think you just need to download Realme ui latest version from official website and install it. Also need to wipe your data after installation.
I Also have the same problem as you and no one still replying in this thread That was sad
Press the volume+ and power button to stop the looping and turn the phone off then try going to bootloader mode with volume- and power button.
Sounds like you possibly have UI2 recovery with UI1 ROM if that is the case I think you should go to recovery mode and reinstall UI2 then unlock your bootloader and roll back to UI1 the proper way.
You might also try to use recovery mode wipe to format data. Then your phone should start as if it were fresh.
This is the proper way to roll back:
Roll back to UI1 from UI2 put it in you phone and run from recovery mode--->https://download.c.realme.com/flash/Rollbackpack/realme_6Pro/RMX2061_11_OTA_0410_all_DOWNGRADE.ozip
anonymous178 said:
I recently upgrade to realme UI 2 beta but decided to roll back. So I downloaded my rom from the official website. And entered recovery mode and Install from the phone the ROM installed and then It prompted me to reboot. I rebooted the device but now It stuck in the infinity boot loop and restarts after the Realme Logo in white fonts... My bootloader is locked... Experts, please guide me on what went wrong and how can I fix this.. As it's a holiday in India, Service centers would be close for 2 days. But since this is my only phone, 2 days is a looooong period. Please Help
Click to expand...
Click to collapse
Bro same with my device have you got any solution please help
oxbowlarry said:
Press the volume+ and power button to stop the looping and turn the phone off then try going to bootloader mode with volume- and power button.
Sounds like you possibly have UI2 recovery with UI1 ROM if that is the case I think you should go to recovery mode and reinstall UI2 then unlock your bootloader and roll back to UI1 the proper way.
You might also try to use recovery mode wipe to format data. Then your phone should start as if it were fresh.
This is the proper way to roll back:
Roll back to UI1 from UI2 put it in you phone and run from recovery mode--->https://download.c.realme.com/flash/Rollbackpack/realme_6Pro/RMX2061_11_OTA_0410_all_DOWNGRADE.ozip
Click to expand...
Click to collapse
Can you please advise how to install ui2 I am stuck in recovery mode with same issue. can't even use online update option getting error " can not find the available network " please help
Rajdeep1994 said:
Can you please advise how to install ui2 I am stuck in recovery mode with same issue. can't even use online update option getting error " can not find the available network " please help
Click to expand...
Click to collapse
Try using the latest Realme Flash Tool and flash the proper UI1 to get your phone back to factory stock.
[Tool] RFT - REALME Flash Tool to flash stock ROM (For Unlocked Bootloader)
REALME FLASHTOOLS V 1.1.3 This tool can make you easier to install stock roms, Rollback, Downgrade This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program What the tool can do: - Flash phone - For now the tool...
forum.xda-developers.com
Then try again to put your phone in UI2. Read the directions carefully and follow them precisely. The following instructions are from Pixel extended and I know it works.
FLASHING INSTRUCTIONS
FROM ANDROID 10 TO ANDROID 11
1) GO TO A10 OFRP (Flash if not flashed)
2) FORMAT DATA
3) FLASH C.09 MOD ZIP (905MB)
Link :
RMX2061_C.09_mod.zip
{
"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"
}
drive.google.com
PS: DONT TRY TO BOOT THIS . THIS IS NOT FULL SYSTEM
4) REBOOT TO BOOTLOADER
5) FLASH A11 VBMETA
6) FLASH A11 STOCK RECOVERY
7) GO IN STOCK RECOVERY ONCE
8) POWER OFF AND AGAIN GO TO BOOTLOADER
9)FLASH A11 VBMETA
10)FLASH A11 OFRP
11) FORMAT DATA
12)FLASH A11 ROM
Credits : @Ctapchuk for c9 mod
oxbowlarry said:
Try using the latest Realme Flash Tool and flash the proper UI1 to get your phone back to factory stock.
[Tool] RFT - REALME Flash Tool to flash stock ROM (For Unlocked Bootloader)
REALME FLASHTOOLS V 1.1.3 This tool can make you easier to install stock roms, Rollback, Downgrade This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program What the tool can do: - Flash phone - For now the tool...
forum.xda-developers.com
Then try again to put your phone in UI2. Read the directions carefully and follow them precisely. The following instructions are from Pixel extended and I know it works.
FLASHING INSTRUCTIONS
FROM ANDROID 10 TO ANDROID 11
1) GO TO A10 OFRP (Flash if not flashed)
2) FORMAT DATA
3) FLASH C.09 MOD ZIP (905MB)
Link :
RMX2061_C.09_mod.zip
drive.google.com
PS: DONT TRY TO BOOT THIS . THIS IS NOT FULL SYSTEM
4) REBOOT TO BOOTLOADER
5) FLASH A11 VBMETA
6) FLASH A11 STOCK RECOVERY
7) GO IN STOCK RECOVERY ONCE
8) POWER OFF AND AGAIN GO TO BOOTLOADER
9)FLASH A11 VBMETA
10)FLASH A11 OFRP
11) FORMAT DATA
12)FLASH A11 ROM
Credits : @Ctapchuk for c9 mod
Click to expand...
Click to collapse
Or can simply after booting go to software update and UI2 install.
I tried from Recovery "Online update" option and receive a message "Can not find the available network!" but here around I have many wifi networks on the air.
I can see in "Install from storage" all my data files in the device but I don't know how to backup this because ADB & Fastboot not working, only boot to recovery