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
Hi, I was trying to flash a kdz to my LG G3 in order to downgrade the phone to 5.0. However, while the program start flashing and the progress bar on the phone reach 5%, the program shows " cannot reach the sever". The flashing process then stopped, no matter I keep clicking "retry".
As a result, I took out the battery and put it back attempt to get back to download mode.
However, the LG G3 do have a starting up screen as usual, but the phone didnt go in download mode, but get into black screen. The notification light is repetitively flashing blue and red color for couple second.
THe computer cannot detect the phone.
Any idea how I can save the phone ~_~?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana
Bananaphone64 said:
Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana
Click to expand...
Click to collapse
It can go into the recovery mode but not the normal OS. But what I can do in the recovery
voot566 said:
But what I can do in the recovery
Click to expand...
Click to collapse
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana
Bananaphone64 said:
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana
Click to expand...
Click to collapse
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"
voot566 said:
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"
Click to expand...
Click to collapse
drivers installed?
Bananaphone64 said:
drivers installed?
Click to expand...
Click to collapse
Yes, driver is installed :crying:
but windows doesnt seems to have detected my phone
Hm... i recently havent the stock recovery installed. I allways hat the possibility to use TWRP.
Thx so much, Bananaphone64.
I think what the real problem now is, the computer cannot recognize the phone. Anyone else have an idea?
In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana
Bananaphone64 said:
In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana
Click to expand...
Click to collapse
I have attempted on another computer, but the other computer also doesnt recognize the phone.
What is a SS?
A Screenshot or Picture from the Recovery Menu
Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS
I have seen that screen! 3 days before!
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!
yosmz1112 said:
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!
Click to expand...
Click to collapse
Yes. it was completely not able to enter into the download mode...........
Wh0CaREs said:
Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS
Click to expand...
Click to collapse
It is factory recovery. let me check the link, thx so much
deleted
I have problem with my a2 lite. Device sesnors like accelerometar, light sensor, proximity, screen rotate sensor etc. is not working after failed flash of android 10. I flashed stock rom through xiaomi flash tool but im thinking that partition may be corupted so i need to revert it back to stock. What do you guys think? Now im running latest october update and bootloder is unlocked. Plz help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hrvoje007 said:
I have problem with my a2 lite. Device sesnors like accelerometar, light sensor, proximity, screen rotate sensor etc. is not working after failed flash of android 10. I flashed stock rom through xiaomi flash tool but im thinking that partition may be corupted so i need to revert it back to stock. What do you guys think? Now im running latest october update and bootloder is unlocked. Plz help.
Click to expand...
Click to collapse
You can try flashing stock firmware in edl mode (fastboot OEM edl command via cmd on PC and you phone connected in fastboot mode) with MiFlash , if this doesn't help , pm me
nikoman1987 said:
You can try flashing stock firmware in edl mode (fastboot OEM edl command via cmd on PC and you phone connected in fastboot mode) with MiFlash , if this doesn't help , pm me
Click to expand...
Click to collapse
is there any other way than edl mode? Im not familiar with that metod
hrvoje007 said:
is there any other way than edl mode? Im not familiar with that metod
Click to expand...
Click to collapse
the method is simple , when you type the comand "fastboot OEM edl " in cmd.exe , that you have to open in your fastboot folder , your phone will turn the screen of like the phone is turned off , but actually it will be in edl mode , flash the stock firmware the same way you have flashed when your phone was in fastboot mode.
If you flashed Android 10 GSI version , you can try flash this zip via TWRP recovery, then flash stock firmware via miflash
Here is the link: https://drive.google.com/file/d/10o7WXe9YB31mvZBVVJtpINYQqpx4CH8D/view?usp=drivesdk
But I strongly recommend you to flash the stock firmware in EDL , there are many YouTube tutorials , and it's very simple , good luck!
nikoman1987 said:
the method is simple , when you type the comand "fastboot OEM edl " in cmd.exe , that you have to open in your fastboot folder , your phone will turn the screen of like the phone is turned off , but actually it will be in edl mode , flash the stock firmware the same way you have flashed when your phone was in fastboot mode.
If you flashed Android 10 GSI version , you can try flash this zip via TWRP recovery, then flash stock firmware via miflash
Here is the link: https://drive.google.com/file/d/10o7WXe9YB31mvZBVVJtpINYQqpx4CH8D/view?usp=drivesdk
But I strongly recommend you to flash the stock firmware in EDL , there are many YouTube tutorials , and it's very simple , good luck!
Click to expand...
Click to collapse
ok, thanks you first i thought i need to teardown my phone to do that, do you think this will fix sensors issue, becase my internet is painfully slow, everything will reset i need do download every single app i use again
hrvoje007 said:
ok, thanks you first i thought i need to teardown my phone to do that, do you think this will fix sensors issue, becase my internet is painfully slow, everything will reset i need do download every single app i use again
Click to expand...
Click to collapse
it will do the edl flash
I did edl flash but sensors stil not working at all. I really dont know what to do next
hrvoje007 said:
I did edl flash but sensors stil not working at all. I really dont know what to do next
Click to expand...
Click to collapse
Which rom version did you have before to flash?
Which rom version do you choose?
The result in MiFlash tool was suceed?
Do you choose Clean Flash option instead of Save User Data option?
Can you upload some screenie?
SubwayChamp said:
Which rom version did you have before to flash?
Which rom version do you choose?
The result in MiFlash tool was suceed?
Do you choose Clean Flash option instead of Save User Data option?
Can you upload some screenie?
Click to expand...
Click to collapse
i explained everything in original post. I tried to flash android 10, but something went wrong and device didnt boot up, so i did return to android 9 stock with xiaomi flash tool, and everything was working except device sensors. So i did again with EDL mode but didnt help. I choosed clean flash both times with regular fastboot before, and after with edl mode
hrvoje007 said:
i explained everything in original post. I tried to flash android 10, but something went wrong and device didnt boot up, so i did return to android 9 stock with xiaomi flash tool, and everything was working except device sensors. So i did again with EDL mode but didnt help. I choosed clean flash both times with regular fastboot before, and after with edl mode
Click to expand...
Click to collapse
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
SubwayChamp said:
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
Click to expand...
Click to collapse
i will try that in next couple of days, and i will let you know if problem is solved thank you, i can give any information you guys ask im not very experienced in this stuff like you but i appreciate your help.
SubwayChamp said:
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
Click to expand...
Click to collapse
I tried these steps but still didnt solve the issue, do you have any other sugestions?
hrvoje007 said:
I tried these steps but still didnt solve the issue, do you have any other sugestions?
Click to expand...
Click to collapse
Your issues remain as described in OP?
Did you use EDL mode (not fastboot ) to flash the whole rom?
And also did you use Clean All (not save userdata) in MiFlash tool?
And which rom did you try of Android 10 firstly that caused this damage?
SubwayChamp said:
Your issues remain as described in OP?
Did you use EDL mode (not fastboot ) to flash the whole rom?
And also did you use Clean All (not save userdata) in MiFlash tool?
And which rom did you try of Android 10 firstly that caused this damage?
Click to expand...
Click to collapse
Yes i used EDL mode to falsh rom, and yes i pressed clean all.
Firstly i installed twrp, then i tried to instal android 10 pixel experience rom, but then i was stucked in bootlop, then i cleaned the storage from the rom and tried to install another version of android 10 which is GSI. But then also everything went wrong and my phone said "Your sistem is destroyed, press power button to shutdown" or something like that and that is it something went teribly wrong and i dont know what else i can do to fix this, it is very strange that everything works except sensors. I dont know what could be releated to this problem.
hrvoje007 said:
Yes i used EDL mode to falsh rom, and yes i pressed clean all.
Firstly i installed twrp, then i tried to instal android 10 pixel experience rom, but then i was stucked in bootlop, then i cleaned the storage from the rom and tried to install another version of android 10 which is GSI. But then also everything went wrong and my phone said "Your sistem is destroyed, press power button to shutdown" or something like that and that is it something went teribly wrong and i dont know what else i can do to fix this, it is very strange that everything works except sensors. I dont know what could be releated to this problem.
Click to expand...
Click to collapse
It seems that the GSI that you used before is the culprit.
Some things you can try:
- Try other firmware versions, probably a downgrade like v10.0.3.0
- Try to erasing first in fastboot as many as partitions you can in both slot before to flash through MiFlash tool. I know that MiFlash tool overwite them but just to be sure.
- Probably you might try flashing with other tool like QPST or other qualcomm flasher tool, I´m not sure which actually works for our device.
- If you resized some partitions to flash a GSI you have to restore them to the exact size that was before.
I was watching youtube tutorial from iboy editz and something i probably did wrong, but it doesnt matter anymore because i can lieve with this isuse it just iritating and always deleting everything from the phone and instaling again takes to much of my time, but anyways thank you for help
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