I followed a guide to dual boot my Linx7 tablet using the Cube iWork 7 download with Android and Windows 10. I got this working fine and over the last few weeks have setup both how i want them. However, at some point i seem to have lost the ability to choose which OS to boot. Normally I'd turn the tablet on, see the American Megatrends screen then it would boot to the EFI Shell/Bootloader?? which would give me the choice of booting Android or Windows. I get none now and it will just boot to the last used OS.
In Android i noticed an app that is called 'Boot to Windows' which works as expected, reboots into Windows. However when I was booting to Windows, to get back to Android i rebooted about 6 times and just hammered volume down which happened to work and boot it into Android. I'm not afraid to boot back into Windows in case i can't get back into Android.
Does anyone know what I've done, how i can fix it, ideally without having to reinstall both OS's again or is there a way of changing the OS to boot to without the menu (like volume down which i feel shouldn't have worked for me but did)
Any help would be really appreciated as I've searched for hours to find answers without any luck.
Related
Rooted stock Kit Kat tablet (V500) 2 weeks ago, and all went well. Used ioroot24. however 3/4 days ago started tablet, and tablet in boot loop.
Have searched and tried LG Hard Reset , gets to android robot deleting (only for very short time) and restarts in root loop
Also Used LG mobile support tool which d/loads recovery file, appears to load on tablet (in d/Load mode) and reboots in boot loop again.
Button set to factory reset does not work either.
Should I install Linux distro and use adb/fast boot commands? Am using win 8.1 x64 at present.
On starting shows LG logo, seems to boot for 15/20 seconds then reboots.
Point in the right direction would be greatly appreciated. Thank you in advance.
If you wish to register you will be able to ask that question here There are lots of knowledgeable users there to help you.
Good luck
So I just purchased a used Oneplus One off of Swappa (seller claimed phone had been used for 1 week, minimal damage, etc.) and upon receiving it and trying to boot it, I was greeted with a bootlook where the phone never makes it past the boot animation (the oneplus logo with android at the bottom). I figured the easy solution was to simply sideload a stock image of the latest software. However, when I put the phone into fastboot, it would not be detected by either adb or fastboot. I know the phone is rooted and unlocked, but because I cannot turn it on, I cannot tinker with any USB-related dev settings. I have reinstalled android sdk, adb, fastboot, and the google usb driver, all to no avail. Even tried all of this on a second Windows laptop. Is there something I'm missing or is there some fix to have this phone detected while in fastboot? The phone is the Cymd edition with stock recovery. Thank you.
i was given this tablet, when the tablet is charged and turned on it displays the nextbook loading screen until the battery dies hours later, i have been looking for a stock recovery image to flash back to the tablet to at least boot into android, i have tried to factory restore the tablet and it keeps doing the same thing, can anyone tell me what im doing wrong? can anyone help me get twrp installed from fastboot so i can try to flash a few of the dumps that i have found for this tablet? any help getting this tablet working again would be appreciated, i have no idea what caused the recovery to not work, every tablet and phone i have ever did a factory reset on has worked, this is a first for me, also since this tablet is running an intel chip, is it possible to install windows 10 on it ?
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.
I tried to install Lineage 18.0 ( lineage-18.0-20201109-UNOFFICIAL-m8.zip ) on my old HTC m8.
I had previously installed CyanogenMod on it 6(?) years ago, so it was rooted, unlocked, and already had an old TWRP.
I updated TWRP to twrp-3.5.2_9-0-m8.img and got an unofficial lineage 18.0 zip
TWRP installed this fine, I went through the Lineage setup - wifi, time zone etc. It seemed to be working fine. I wanted to sideload an APK from TWRP so restarted the whole phone.
Now there are two problems that prevent me using the phone, and fixing either one of them should be enough for me to fix things.
1) TWRP seems to have disappeared to be replaced with nothing interactive. If I hold power+vol down to get to the menu that le5ts me choose RECOVERY and select RECOVERY it will do one of two things, unpredictably - (1) stay on the white 'entering recovery' 6 seconds, then black 2 seconds then back to 'entering recovery' in a loop, OR (2) it will move onto the Lineage OS boot screen (black with a little animation), get to the home screen and crash back to the Lineage OS loading screen then loop through this continuously.
I see from the Lineage official site that the m8 is only up to 17.1, and they have their own Recovery (I didn't install Lineage's recovery). So this is perhaps mostly my own fault, but I'd like to get back control of the phone and try an official ROM.
Some questions:
1) How do I tell if I still have TWRP somewhere? Can I get back into it to load up a more stable older Lineage OS?
2) Is there any recovery at all? I assume there must be to get the Lineage OS loader started. There's nothing interactive or message about what recovery is running.
3) As I can't get to a functional normal working phone I can't do USB debugging. Can I use the adb commands against the phone if I have it connected by USB and sitting on the FASTBOOT screen from the boot loader? (not sure if I've got the right terminology there, this is the white screen with the two or three bootup items that you navigate with vol up / down and power).
4) Is there anything I can do with the Lineage OS startup so it doesn't just loop upon showing the home screen? Some sort of safe boot mode? I saw an older post saying to hold vol down once the OS boot animation screen starts, but that doesn't seem to do anything for me.
5) Complication - ADB didn't seem to work with this phone any more, even before I got it into this state, perhaps because of age, but it did work many years ago (different PC, USB cable). I think the only way I can get any new content onto the phone is through the external SD card, but even then I need to get to TWRP or something interactive to do anything with the card content.
Thanks for any advice you can offer.
My recommendation:
Take it to authorized service center and let them try to fix it.
jwoegerbauer said:
My recommendation:
Take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
Ebay has them from something like $30 - $60 used, so I don't think its going to be worth paying for a fix. Given that it's rooted and about 7 years old I strongly suspect that it is no longer covered by the warranty (is HTC still in business?). Still a very nice phone for its time - brushed metal body, solid, great stereo speakers, reasonable screen, in 'near new' condition even now. In a few ways better than my S8.
I suspect it will be going for recycling or an aggressive 'ifixit teardown' style post mortem if nothing comes up here.