Related
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
Make/buy a factory cable and fastboot the proper bootloader from the stock update package.
Sent from my myTouch_4G_Slide using XDA App
I was a little confused about this myself at one point... There are a bunch of 'low-level' partitions that are really important not to mix up.
'bootloader' contains the basic bootloader, which loads everything else and you should pretty much never touch it, except to install FireFireFire.
'recovery' is the partition where TWRP or ClockWorkMOD should go.
Finally, 'boot' is what launches Android.
I almost made the same mistake last night installing CWM (it was 2am and my brain+fingers were being stupid)
Anyway OP, it sounds like a factory cable would be your best bet, unless that just tells something to the bootloader, in which case getting a warranty replacement from Amazon might be your only option...
Just remember next time that you want to flash recovery ;-)
dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
I have had a similar situation on my KF. I used a factory cable to solve my issue. Send a private message to SkOrPn with Factory Cable in the subject. His cable is well built and arrived very quick via USPS. Not to mention he sells them at a good price.
Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...
Try adding the device ID 0bb4:0c01 to your USB configuration
Sent from my Amazon Kindle Fire using Tapatalk
dietomant said:
Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...
Click to expand...
Click to collapse
I think you've gotten somewhat misleading information from the previous posters. The factory cable will always put the KF into fastboot mode if (this is a HUGE if) the device has a working bootloader. The bootloader is the piece of software that will put the device into fastboot mode, so without that the factory cable cannot do its job.
I'm quite surprised you were able to break the bootloader by trying to flash that image onto it. In my experience, fastboot flash checks for the size and would fail when I tried to give it something > 256KB for the bootloader... but that's neither here nor there...
If you cannot get a "kindle fire" or the "yellow triangle" to come up on the display, your bootloader is broken. Your last hope is to open up the case and use usbboot to temporarily load a bootloader into memory via USB and use that to flash a permanent bootloader. You'll probably need a case pry tool to do this fairly safely and linux installed because I don't believe usbboot was ever ported to Windows.
Additional information: http://forum.xda-developers.com/showthread.php?t=1405052
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
OMG!
edit:
how the hell do i get those files inside with only wastboot mode ... FFS
2nd edit: @Neuer_User, I have the pulled mmcblk0p7 on the storage, is there any possible way of pushing it back into the system via fastboot?
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
Interesting. See if you can make it reproducable. That would be great!
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
I wrote some unbricking instructions and a flash script to recover bricked watches with @kiralex1995 method of entering fastboot.
Hope, it helps recover the small number of watches known to be bricked through flashing.
https://forum.xda-developers.com/sm...tches/tutorial-unbrick-huami-amazfit-t3547300
Neuer_User said:
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Click to expand...
Click to collapse
You're welcome
@kiralex1995 , Thanks a Gazillion !!!
it worked and with @Neuer_User help, the watch came back to life !!!
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
MyriaBoa said:
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
Click to expand...
Click to collapse
maybe you need to explain a little bit more detailed? is the watch running and completely booted when you connect to usb and type those adb commands or is it switched off? when you turn it on, how fast do you turn it off? i didn't get it yet. please explain a bit more.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
It is interesting. Does it work with out th.e adb kill-server and adb start-server commands? I do not see, how they could be involved...
The adb wait-for-server might be the key. So, when the watch is started, there is some USB communication on-going. I'd love to do some testing on that. Will do that for sure, when I get the development watch
I' m not near my computer, so I can't do more tests now.
As I wrote in my first post, it wasn't my intention to open fastboot, when it accindentally happened for the first time.
The kill and start commands were given, because my Windows 7 machine pretended not to see the watch in adb (only as usb), and I thought, maybe it's detected, when I turn it on while adb is waiting for device and the usb notification 'kicks in'.
But nothing happened, so I pushed the button, to turn the watch off again.
To my surprise the result was fastboot.
I repeated the same steps today on my Windows 10 computer that always detects the watch in adb and it opened fastboot again.
Could you specify for which build or version you tried this? I (unfortunately) had the update to 1.3.5 and there seems to be no way to enter fastboot. It also is not recognised as an adb device
I have a amazfit pace but he is stucked on a update screen and when I try entring in fast boot mode he doesn´t enter and goes to update again and don´t conclude that. What can I do?
Did anybody managed to get Amazfit 2 (stratos) to fastboot using this method? thx...
EDIT: Yes, I can confirm it works! However it is really kind of tricky. Embrace yourselves!
Many thanks to you guys for finding this out, you are the best!
Thanks.
kiralex1995 said:
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
Click to expand...
Click to collapse
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Hello my device is waiting for the logo, it is not opening.
endrancer said:
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Click to expand...
Click to collapse
Hi all together,
yes I can confirm that plugging the cable is not neccessary. Went back to stock yesterday. Got into fastboot on first try.
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
E-lian said:
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
Click to expand...
Click to collapse
Hello
I've bricked my Pace and cannot enter fastboot.
When I try to enter fastboot I have the same behaviour on my Amazfit Pace. Have You managed some how to enter the fastboot without connection to the PC?
[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom
Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed
Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:
Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*
After reading for hours, I was successful to find an OTG micro-USB adapter with male USB-A end which allowed a Logitech dongle to be inserted and the mouse allowed me to start afresh from a factory reset. The touch screen didn't work.
There was an OTA update and I got all excited thinking, "This will be the update that fixes the touch (or lack thereof) issue."
Sadly, after the message said this was the final update, the touch screen still didn't work.
I was successfully able to enable USB Debugging because of the OTG Mouse.
When I connect to the PC and run an ADB command (e.g. adb devices), a message pops up asking to verify I trust the RSA Fingerprint for that computer and to remember that device.
Now my huge predicament: there is no way for me to touch the checkbox and choose OK.
Once I unplug in the cable to connect the OTG Mouse, the dialog box disappears.
I read about TeamViewer on the PC and TeamViewer Host from the Play Store. I installed both and was able to see the Essential Phone on the computer but whenever I touched the screen of the computer (or used the trackpad), nothing happened on the phone.
I tried pressing spacebar thinking that might enable the checkbox but no remote response on the phone.
I'm so close...all I need is one checkbox and one ok and it'll remember the USB Debugging settings.
From there I can then figure how to either downgrade from Android 10 or hopefully some kind soul can let me know what file to install so I can get this stupid touch screen to work.
I explained in a lot of detail as I wanted you folks to know I've tried many options to troubleshoot this problem before asking for help.
If there's a non-USB Debugging checkbox checked way in Fastboot Mode (e.g. ADB Sideload in Recovery), I'm willing to try that.
Thanks.
Update 2020-07-07: I had an idea to connect a SteelSeries Stratus XL wireless gaming controller to the phone via bluetooth and was successfully able to use the controls of the controller to enable the checkbox and remember the RSA Fingerprint for USB Debugging. Whooo-hoo! Now for the rest of the matter...getting this darn touch screen working with an device image that solves the problem....
I had the same problem after flashing the newest (and final) Image on top of a rooted, very old marshmallow build.
I found a fix on reddit however, and hopefully it works for you too.
I tried the second method described there:
1. Connect to fastboot to unlock bootloader and critical
Code:
fastboot flashing unlock
(didn't do anything for me since I was already unlocked)
Code:
fastboot flashing unlock_critical
Let the phone wipe itself and reboot, then go into fastboot again
2. Then flash the image of September 2018 (PH1-Images-PPR1.180905.036) via the "flashall.bat". After a reboot my touchscreen worked again.
3. Upgrade to the newest image or whichever one you like.
I don't understand the whole problem exactly, so maybe you could try flashing the newest image directly after the unlock_critical step, but I just followed the instructions I found.
Good luck!
Thanks for the suggestion and the link for the file.
When I try and run the command
Code:
fastboot flashing unlock
in fastboot mode, I keep getting the message "Waiting for device".
Same thing, when I try and run the flashall.bat file.
I booted in to FastBoot mode, but when I type adb devices in an admin command prompt, it doesn't show any devices listed, even though adb devices does show the phone listed when the phone has booted up normally.
I have:
uninstalled the Essential Phone driver and reinstalled it (multiple times).
installed the 15 Seconds ADB installer and uninstalled it (multiple times).
rebooted the Windows 10 computer multiple times.
IconBoy said:
Thanks for the suggestion and the link for the file.
When I try and run the command
Code:
fastboot flashing unlock
in fastboot mode, I keep getting the message "Waiting for device".
Same thing, when I try and run the flashall.bat file.
I booted in to FastBoot mode, but when I type adb devices in an admin command prompt, it doesn't show any devices listed, even though adb devices does show the phone listed when the phone has booted up normally.
I have:
uninstalled the Essential Phone driver and reinstalled it (multiple times).
installed the 15 Seconds ADB installer and uninstalled it (multiple times).
rebooted the Windows 10 computer multiple times.
Click to expand...
Click to collapse
Make sure to use a proper cable and not the one that comes with the phone for charging.
I use the one from my Nexus 6p. The cable from Essential is only for charging, not data transfer.
I'm using a USB-A TO USB-C cable which shows device in normal boot mode.
I have tried three different cables which all work when using adb devices in normal boot mode.
Still no phone when List of devices attached is shown.
Just for clarity: adb and fastboot are completely different modes. To test if you successfully booted into fastboot and have a working connection, you have to type "fastboot devices". "adb devices" doesn't work here.
But the unlock command should have worked anyway. How did you boot into fastmode? Can you see this fastboot screen?
If not, the easiest way to get to fastboot is to connect the turned off phone to the PC while keeping the volume down button pressed, until you see the screen linked above.
But if you do see the fastboot screen, and still don't get anything from "fastboot devices", I'd try Google's official adb/fastboot tools.
xxera said:
...you have to type "fastboot devices".
Click to expand...
Click to collapse
Yes! I can see the device listed now! I had no idea that you had to type that command! Wow....years later of working with phones and I am still learning. :good: I guess I didn't progress because I mistakenly thought the device was not being found.
I ran both commands fastboot flashing unlock and fastboot flashing unlock_critical successfully.
Once the phone wiped itself and booted up (without progressing from the startup screen prompts), I shut it down then went back in to fastboot mode and successfully ran the flashall.bat command.
I shut it down and restarted it. Touchscreen is still not working. :crying:
When I finally get this working...would I just run the commands fastboot flashing lock and fastboot flashing lock_critical to relock the phone...? I need Google Pay and other banking apps to work so want the phone to be secure.
There is always more to learn
Shame that it didn't work, though :/ Did you flash the image from September 2018 that I linked, or the newest build? If you directly flashed the newest one, maybe try the 2018 build, since that worked for me. Alternatively, from the same reddit post I linked before, someone got it working by flashing the August 2018 build, and sideloading the September 2018 OTA Update after. But I never did this sideloading thing, so can't help much there. All builds and OTAs are available on this neat website by the way.
Regarding relocking, it is generally advised to only relock if you have a good reason to do it. You can only relock a completely unmodified stock image, otherwise your phone won't boot, so no root, magisk or anything.
My banking apps still work on my unlocked and rooted phone, but I'm using a Pixel 3, and not sure about Google Pay.
But yes, if you want to relock, make absolutely sure you're stock, and use the commands you mentioned. Just be aware that this also wipes the phone again.
xxera said:
Shame that it didn't work, though :/ Did you flash the image from September 2018 that I linked
Click to expand...
Click to collapse
Yes, I used the link you gave me for the Sep 2018 build.
I will try the Aug 2018 build and see if I get any joy with that.
Thank you so much for your patience and help!
Just to be clear, you should sideload the September OTA after that, the August build itself won't do much as far as I understood.
Glad to help, I just had the same hunt for clues behind me, I know how frustrating it can be
I tried the Aug 2018 build then sideload flashing the Sep 2018 build. No joy...touchscreen still not working.
The whole fastboot flashing worked except for this one error:
fastboot format userdata
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
This message came up once the flash was complete and the phone rebooted itself):
Android Recovery
essential/mata/mata
9/PPR1.180610.091/249
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
--------------------------------------------------
Try again
Factory data reset
--------------------------------------------------
There was no choice to Apply update from ADB so I can sideload the Sep 2018 update so I went ahead and chose Factory data reset.
Once it factory reset, I was able to go in to recovery and sideload the Sep 2018 update.
Have I missed anything in this procedure...?
I also tried fastboot flashing the Apr 2019 build but that hasn't helped either.
(Attached is a screenshot of the two files I downloaded. The links are the purple ones I chose). Did I get the correct ones?
The files look right to me.
After some research I found that updating the adb tools worked for some people with that error. The creator of the 15 Seconds ADB installer even edited the post and said the tool is outdated by now. There's a newer version in this post, and maybe you are already using that, but I'd strongly recommend the official ADB from google, since I never had a problem with that one.
Also, I read that you should use a USB-3 cable. The official one from essential itself is USB-2 which can cause some problems in flashing sometimes (which is pretty stupid tbh).
Yes, after you updated ADB/fastboot, I'd just try the Aug image + Sept OTA again. Or directly the Sept image.
Not sure about the factory reset message, I'd say yes again just in case.
Edit: Ah, since it says "can't load android system", I guess the flashing failed.
I managed to fix phones with flashing a second time exactly the same way many times, sometimes fastboot is just moody. But may updating ADB can help here.
I updated fastboot and adb from the Google site.
Reflashed Aug and Sep 2018 files.
No joy. Touchscreen still doesn't respond.
An idea...I tried to install TWRP to see if the touchscreen is actually working but get the error fastboot: error: Couldn't parse partition size '0x' when running the command to install the TWRP Mata recovery image file.
Any way to check if the screen/digitizer is not a hardware fault?
Weird error... Can you post the whole log? If the partition size was read as 0, something went wrong with identifying the partition (if I interpret the error message correctly). Did you correctly flash to boot_a/boot_b depending on which one is active?
But TWRP might not help diagnosing the issue, I think touch stopped working in TWRP for essential phone a while ago, because it is also very outdated...
But to me it sounds like the usual problem after updating that many people had. The screen stopped working after an update, right?
Also, did you make sure to use the new platform-tools fastboot? Google's version doesn't automatically install itself system-wide, so if you just type "fastboot" in the command line, that might still be the old "15 Seconds ABD installer" fastboot. You can type "adb --version"to find out, it tells you in which folder the adb.exe file is.
I was looking to install LineageOS 18.1 and was having a hell of a time.
I was following the instructions, and I can get as far as booting into the LineageOS recovery, but then I can't navigate to ADB using the front button on the box. I am also finding it difficult to find a working OTG cable that works and has the ability to provide power. (so I can remove the USB cable from my laptop and plug in a USB keyboard without powering off the android box)
Anyone have any tricks or suggestions on a OTG cable or USB switch they know works on this? Or better yet, how to get the front navigation button working on the Onn Box working ot how I can enter recovery mode if I try fastboot flash (Impossible to enter recovery instead of boot to OS) instead of fastboot boot?
Here are the instructions I was using. Great until you get to the fastboot flash, since once you reboot it goes straight into the OS and will over right the custom recovery. Then when I fastboot boot, it works, but then the navigation button doesn't work to get to the next step. lol.....
Install LineageOS on dopinder | Odd Solutions Wiki
wiki.oddsolutions.us
on a side note, I have a OTG cable that splits and works on my laptop to fastboot boot the recovery. But once I am in the LineageOS recovery and connect a USB keyboard, it doesn't respond either. (So maybe the LineageOS recovery is the problem?)
I've tried both from https://updater.oddsolutions.us/#/devices/dopinder/builds
lineage-18.1-20220324-recovery-dopinder.img
lineage-18.1-20220317-recovery-dopinder.img
I also tried the 19.0 revoceries (stays in Onn fastboot even after successful fastboot boot) I also tried the earliest 18.1 recovery.
Tried:
lineage-19.0-20220228-recovery-dopinder
lineage-19.0-20220114-recovery-dopinder
lineage-18.1-20210804-recovery-dopinder
Releases · ods-releases/dopinder
Contribute to ods-releases/dopinder development by creating an account on GitHub.
github.com
Has anyone had success getting LineageOS 18.1 flashed on the Dopinger devices? If so, which recovery did you use? (maybe an earlier release works?) If so, where can I get it? (the above link only has the last 2 releases)
Right now I am very suspicious that the recoveries are not working properly for this device.
Here's the extra instructions after you adb reboot into the bootloader using the guide:
1) fastboot flash recovery <recovery file name >
2) fastboot boot <recovery filename> **to get into lineageos recovery mode
At this point the recovery is unresponsive to any inputs (i.e onn 4k button pushes or USB keyboards)
3) In lineageOS recovery mode you can use the basic adb command to reboot recovery into sideload mode
adb reboot sideload **Devs apparently specially enabled this as a workaround for the no input in the recovery
From here you can continue to use the official guide to sideload the lineageos. At this point I was basically dirty flashing, which worked. But I'm sure people can format and erase the stock OS via adb commands if they're motivated enough.
Two issues I noticed with Onn 4k is that plex was super stuttery for almost everything I played (never tested plex on stock OS).
I also performed a factory reset, and afterwards WiFi was unable to reconnect. So I gave up for now and went back to my mibox s until I have time to look further.
Thanks again for the information to help me get lineageos on this device!
htc_softbank said:
I was looking to install LineageOS 18.1 and was having a hell of a time.
I was following the instructions, and I can get as far as booting into the LineageOS recovery, but then I can't navigate to ADB using the front button on the box. I am also finding it difficult to find a working OTG cable that works and has the ability to provide power. (so I can remove the USB cable from my laptop and plug in a USB keyboard without powering off the android box)
Anyone have any tricks or suggestions on a OTG cable or USB switch they know works on this? Or better yet, how to get the front navigation button working on the Onn Box working ot how I can enter recovery mode if I try fastboot flash (Impossible to enter recovery instead of boot to OS) instead of fastboot boot?
Here are the instructions I was using. Great until you get to the fastboot flash, since once you reboot it goes straight into the OS and will over right the custom recovery. Then when I fastboot boot, it works, but then the navigation button doesn't work to get to the next step. lol.....
Install LineageOS on dopinder | Odd Solutions Wiki
wiki.oddsolutions.us
Click to expand...
Click to collapse
What I ended up doing was hardwiring an extra USB cable internal, wasn't too hard soldering isn't my strongest skill by any means, but it's held up. I don't know exactly what the connection beside the USB is, but if I'm remembering correctly that's where i ended up wiring to it. Actually just tried to stay as close to the other power input as possible Just because it seemed like it would be best practice.
Also in case anyone needs them. decent internal photos
Best of luck, I've been running it this way for almost 6 months now
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
iamnotsunshine said:
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
Click to expand...
Click to collapse
[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices
Amlogic G12*/SM1 Family Devices - Your warranty is now void. - You have been warned. - Use at your own risk. Introduction: This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices. Downloads: Please follow...
forum.xda-developers.com
iamnotsunshine said:
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
Click to expand...
Click to collapse
note that on dopinder, unofficial LOS19.1 installs & works, but L1 still not working (as of today ... hopefully npjohnson & others can fix it) in the lineage19.1 version linked by BTK19 in previous post. so, if you are set on DRM content, might want to wait. I bought a Dynalink/wade while I wait, and Lineage19.1 unofficial works well on that. just costs 2X $ !