howto bring a likebook mars t80d back to life under gnu/linux? - Page 2

prout · 05-04-2021, 04:20 PM

OK, nothing happen.

So, restart all :
- remove batterie
- "holding in the small hole near the bottom and pushing in a USB cable" connected to my computer
- fast check with "rkflashtool p" to be sure that the computer detects the mars likebook
- running the "upgrade_tool" non-free software provided by rockship

Quote:

root@my.computer:/tmp/Linux_Upgrade_Tool_v1.21# ./upgrade_tool uf /tmp/update-10225.img
Loading firmware...
Support Type:RK330A FW Ver:7.1.00 FW Time:2020-08-19 16:24:25
Loader ver:2.60 Loader Time:2019-03-13 23:09:52
Upgrade firmware ok.
root@my.computer:/tmp/Linux_Upgrade_Tool_v1.21#

then, the device reboot
- fast white screen
- fast old image about "likebook starting up..."
- black screen
- ~30 seconds of a black screen with a white border circle in the center with "ereasing" under the circle (not in the center of the circle like I said before)
- black screen
- nothing happen

Did I miss something?

Quote:

Originally Posted by bazz2004

"No, the battery was ok I've checked it before posting (it was 3.9 V)"

A car battery can show 12v but not have enough juice (amps) to get things going. Saying that I've no idea how the different technology of these batteries holds up in an e-reader. All batteries fail sooner or later. The Mars is a few years old so you can't rule it out.

indeed, it's a 4.35 V battery (3100 mAh), maybe it was a bit low at my first try 4 days ago.
So just to be sure that it is fully charged, I plug it in a charger and the black screen turned into a white one with a usb cable, a lightning and a battery like icon with a diagonal line in it. Not really sure what does that says…
Why a diagonal line, does it says "I am connected to a charger but I can't charge the battery" ? o_O I guess not, but…

prout · 05-04-2021, 04:31 PM

(oops, I forgot to say that I have replugged the battery before starting the "upgrade_tool")

bazz2004 · 05-05-2021, 03:02 AM

I just realised that these are throwaway devices. Try finding a replacement battery for an e-reader. The only ones you will find are for early Kindles or Sony devices. There have already been questions raised about the Boyue batteries but they do not supply or fit replacements.

Ideally the device would show a battery reading when you try to turn it on but that feature presumably can't be incorporated into the firmware.

ottischwenk · 05-05-2021, 04:24 AM

Quote:

Originally Posted by bazz2004

I just realised that these are throwaway devices. Try finding a replacement battery for an e-reader. The only ones you will find are for early Kindles or Sony devices. There have already been questions raised about the Boyue batteries but they do not supply or fit replacements.

Ideally the device would show a battery reading when you try to turn it on but that feature presumably can't be incorporated into the firmware.

I don't know of any device that can correctly display the battery level during startup.

As for your comment about a replacement battery, replacing the battery in an Apple is not cheap either - so it's also a throwaway product.

bazz2004 · 05-05-2021, 05:19 AM

Boyue is not a religious experience for the rest of us ottischwenk. iPads aren't relevant here although mine has worked with zero issues for years now. There are replacement batteries available to buy for them and Apple have numerous service centres. Chinese made android devices are unable to offer meaningful support - you are it.

ottischwenk · 05-05-2021, 05:56 AM

Quote:

Originally Posted by bazz2004

Boyue is not a religious experience for the rest of us ottischwenk.

Relgious experience? No - practical application!

Quote:

iPads aren't relevant here although mine has worked with zero issues for years now. There are replacement batteries available to buy for them and Apple have numerous service centres.

Are Apple Cervice Centers even used when a repair can be more expensive than buying a new device?
If so, then Apple followers are even bigger fools than I already imagined.

Quote:

Chinese made android devices are unable to offer meaningful support - you are it.

Apart from that, Chinese devices (Windows, Android) give me what I need; Apple is not able to do that, an experience I paid a lot of money for.

prout · 05-05-2021, 07:23 AM

excuse me but can we stay on topic please?

So, I restarted the update.img (with a full batterie, so no problem here, batterie doesn't drop voltage so it is not a batterie problem) with "upgrade_tool", but I have exactly the same problem with a black screen as mentioned before.

Is it a image problem? Is it normal and I have to wait 150 hours? What should I have after this update (like: you have a "circle with ereasing writing under, then it happens this and that for ~ X time" etc.)

issybird · 05-05-2021, 11:01 AM

Moderator Notice
An OP’s request to stay on topic is to be honored. Also, issues are to be reported and not moderated by individual posters and language must remain civil. Two posts have been deleted.

rvcjew · 05-05-2021, 12:18 PM

Quote:

Originally Posted by prout

excuse me but can we stay on topic please?

So, I restarted the update.img (with a full batterie, so no problem here, batterie doesn't drop voltage so it is not a batterie problem) with "upgrade_tool", but I have exactly the same problem with a black screen as mentioned before.

Is it a image problem? Is it normal and I have to wait 150 hours? What should I have after this update (like: you have a "circle with ereasing writing under, then it happens this and that for ~ X time" etc.)

The erasing step is what should be happening, It has been months since I did this on my mars and then I sent it to a friend in Canada so can't even test this method your doing. It should flash, erase, say updating system with a bar going across (this might only be OTAs) then boot like normal for like I'd say only 10 minutes max then be at the setup screen like when it was new. Hard to diagnose as the nature of the screen makes it hard to tell if its frozen or off. I also have no idea how to use that tool your using as I thought you could just use the flash tool which I still have no experience using. Does it make a log saying what it flash from that img? Looking at the link you sent about the tool it sounds like it only understands perhaps 4 of the like 10 img files it would be flashing that's is inside the main img. It might just be to OLD of an app perhaps. It does sound like it thinks it's doing its job though but might only be flashing some of the imgs.

Do you have over 50GB of space free on your own PC? At this point I have no idea how to help other then saying do the VM which I can help with.

At least the Device is not bricked and I know for a fact can be fixed under the windows tool (maybe a friend has a laptop you can borrow for an hour or something?).

EDIT: I thought maybe your image could be bad but I don't think so as I could not find any other update img for this device and I know I Flashed mine with that one.

rvcjew · 05-05-2021, 12:54 PM

Quote:

Originally Posted by prout

excuse me but can we stay on topic please?

So, I restarted the update.img (with a full batterie, so no problem here, batterie doesn't drop voltage so it is not a batterie problem) with "upgrade_tool", but I have exactly the same problem with a black screen as mentioned before.

Is it a image problem? Is it normal and I have to wait 150 hours? What should I have after this update (like: you have a "circle with ereasing writing under, then it happens this and that for ~ X time" etc.)

Sorry for double post but I thought about something and searched boyue tweets and found someone asking about the mars upgrade and they linked a new pdf with a new upgrade file.

https://twitter.com/BrioMex/status/1363882767319142402

Which has this file link in it direct from Boyue.

https://mega.nz/file/PBpnDY5C#oD2LP-...q7daI5T9WK-xlE

My MD5 of the file extracted is: 0FB77268916C3C54DE7FA57E39DBDD2E

Use this file instead with your Update Tool.

prout · 05-06-2021, 10:55 AM

Quote:

Originally Posted by rvcjew

The erasing step is what should be happening, […]. It should flash, erase, say updating system with a bar going across (this might only be OTAs) then boot like normal for like I'd say only 10 minutes max then be at the setup screen like when it was new.

OK, thx, so I shouldn't have any black screen

n.b.: just after the "erasing" under the circle, it looks like to reboot (really fast white screen), then I can see the picture of the bridge with "likebook starting up..." for ~1 or 2 seconds, then the black screen appears, so I guess it fails when it tries to read the kernel? or it succeed but with a wrong output screen?
I've seen in the parameter.txt "androidboot.console=ttyFIQ0" but it was "ttyS2" before trying to install android 8.1, like in my first post, but I guess that it is not the problem if the image works for others.

Quote:

Does it make a log saying what it flash from that img?

yes it does :

Code:

$ cat log/log2021-05-06.txt 
14:18:14 	Upgrade Tool ver 1.24
14:18:14 	Test Device Start
14:18:14 	Test Device Success
14:18:14 	Check Chip Start
14:18:14 	Check Chip Success
14:18:14 	Get FlashInfo Start
14:18:14 	<LAYER 1-1> INFO:FlashInfo: 0 0 CD 1 0 4 4 0 28 0 1
14:18:14 	Get FlashInfo Success
14:18:14 	 Prepare IDB Start
14:18:14 	<LAYER 1-1> INFO:CS(1)		(14752MB)		(SAMSUNG)
14:18:14 	Prepare IDB Success
14:18:14 	Download IDB Start
14:18:14 	Download IDB Success
14:18:14 	Reset Device Start
14:18:16 	Reset Device Success
14:18:16 	Wait For Loader Start
14:18:17 	Wait For Loader Success
14:18:17 	Test Device Start
14:18:17 	Test Device Success
14:18:17 	Download Firmware Start
14:18:17 	<LAYER 1-1> INFO:Start to download trust,offset=0x4000,size=                                                         4194304
14:18:18 	<LAYER 1-1> INFO:Start to download uboot,offset=0x2000,size=                                                         4194304
14:18:20 	<LAYER 1-1> INFO:Start to download misc,offset=0x8000,size=                                                           49152
14:18:20 	<LAYER 1-1> INFO:Start to download resource,offset=0xa000,size=                                                          251904
14:18:20 	<LAYER 1-1> INFO:Start to download kernel,offset=0x12000,size=                                                        21174292
14:18:27 	<LAYER 1-1> INFO:Start to download boot,offset=0x22000,size=                                                        22941696
14:18:35 	<LAYER 1-1> INFO:Start to download recovery,offset=0x32000,size=                                                        30859264
14:18:45 	<LAYER 1-1> INFO:Start to download system,offset=0x18c000,size=                                                      1345618164
14:26:20 	<LAYER 1-1> INFO:Start to download vendor,offset=0x594000,size=                                                       242786464
14:27:43 	<LAYER 1-1> INFO:Start to download oem,offset=0x696000,size=                                                          360596
14:35:25 	Download Firmware Success
14:35:25 	Reset Device Start
14:35:27 	Reset Device Success

(n.b. for this one I used another version of upgrade_tool with the new update.img from below, but it was the same with the previous version (of software and image))

all .img that are in the update_xxx.img are seems to be correctly uploaded (according to the dump from imgRePackerRK) :

Code:

update-10456.img.dump/Image-rk3368# du -b *
22941696	boot.img
21174280	kernel.img
21174292	kernel.img.krnl
237902	MiniLoaderAll.bin
49152	misc.img
360596	oem.img
887	parameter.txt
899	parameter.txt.parm
30859264	recovery.img
251904	resource.img
1345618164	system.img
4194304	trust.img
4194304	uboot.img
242786464	vendor.img

Quote:

Looking at the link you sent about the tool it sounds like it only understands perhaps 4 of the like 10 img files it would be flashing that's is inside the main img. It might just be to OLD of an app perhaps. It does sound like it thinks it's doing its job though but might only be flashing some of the imgs.

if I try with a newer version of update_tool, it stops and returns an error about the chip (and then rkflashtool that I use to be sure that the device is still responding froze and I have to remove battery and restart from begining) :

Code:

Linux_Upgrade_Tool_v1.57# ./upgrade_tool uf /tmp/update-10456.img
Program Data in /root/.config/upgrade_tool
Loading firmware...
Support Type:RK330A	FW Ver:7.1.00	FW Time:2020-10-21 12:13:56
Loader ver:2.60	Loader Time:2019-03-13 23:09:52
Check Chip Fail

Linux_Upgrade_Tool_v1.57# rkflashtool p
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3368...
rkflashtool: info: interface claimed
^C
(froze here, so ^C)

with the following log :

Code:

15:39:29 	Current process in Linux_Upgrade_Tool_v1.57
15:39:29 	Using /root/.config/upgrade_tool/config.ini
15:39:29 	Command Line: ./upgrade_tool uf /tmp/update-10456.img
15:39:29 	Current Device Location ID:11
15:39:29 	Test Device Start
15:39:29 	Test Device Success
15:39:34 	Error:RKU_Read_EX failed,err=-7
15:39:34 	ERROR:ReadCapability-->RKU_ReadCapability failed,err(-4)
15:39:34 	Check Chip Start
15:39:39 	Error:RKU_Write failed,err=-7
15:39:39 	ERROR:CheckChip-->RKU_ReadChipInfo failed,RetCode(-3)
15:39:39 	Check Chip Fail
15:39:39 	Command mode out

Quote:

Do you have over 50GB of space free on your own PC?

No I don't

Quote:

At least the Device is not bricked and I know for a fact can be fixed under the windows tool (maybe a friend has a laptop you can borrow for an hour or something?).

neither

Quote:

EDIT: I thought maybe your image could be bad but I don't think so as I could not find any other update img for this device and I know I Flashed mine with that one.
[…]
Which has this file link in it direct from Boyue.

https://mega.nz/file/PBpnDY5C#oD2LP-...q7daI5T9WK-xlE

My MD5 of the file extracted is: 0FB77268916C3C54DE7FA57E39DBDD2E

Use this file instead with your Update Tool.

OK, ty a lot.
same md5 here, and I used that image too with same results, so I guess that it is not a problem with the update img.

About options with upgrade_tool :

Code:

Linux_Upgrade_Tool_v1.24# ./upgrade_tool -h

---------------------Tool Usage ---------------------
Help:             H
Quit:             Q
Version:          V
Clear Screen:     CS
------------------Upgrade Command ------------------
ChooseDevice:		CD
SwitchDevice:		SD
UpgradeFirmware:	UF <Firmware>
UpgradeLoader:		UL <Loader>
DownloadImage:		DI <-p|-b|-k|-s|-r|-m image> [parameter file]
DownloadBoot:		DB <Loader>
EraseFlash:		EF <Loader|firmware>
LowerFormat:		LF
----------------Professional Command -----------------
TestDevice:		TD
ResetDevice:		RD [subcode]
ResetPipe:		RP [pipe]
ReadFlashID:		RID
ReadFlashInfo:		RFI
ReadChipInfo:		RCI
ReadSector:		RS  <BeginSec> <SectorLen> [-decode] [File]
WriteSector:		WS  <BeginSec> <File>
ReadLBA:		RL  <BeginSec> <SectorLen> [File]
WriteLBA:		WL  <BeginSec> <File>
EraseBlock:		EB <CS> <BeginBlock> <BlokcLen> [--Force]
-------------------------------------------------------

According to others the lf (low format) or even ef (erasing flash) options can be used when having errors. I'm really not sure about those options, but maybe erasing flash at first then upload the image like I did before could make all more clean? :/

rvcjew · 05-06-2021, 02:03 PM

Quote:

Originally Posted by prout

OK, thx, so I shouldn't have any black screen

n.b.: just after the "erasing" under the circle, it looks like to reboot (really fast white screen), then I can see the picture of the bridge with "likebook starting up..." for ~1 or 2 seconds, then the black screen appears, so I guess it fails when it tries to read the kernel? or it succeed but with a wrong output screen?
I've seen in the parameter.txt "androidboot.console=ttyFIQ0" but it was "ttyS2" before trying to install android 8.1, like in my first post, but I guess that it is not the problem if the image works for others.

yes it does :

Code:

$ cat log/log2021-05-06.txt 
14:18:14 	Upgrade Tool ver 1.24
14:18:14 	Test Device Start
14:18:14 	Test Device Success
14:18:14 	Check Chip Start
14:18:14 	Check Chip Success
14:18:14 	Get FlashInfo Start
14:18:14 	<LAYER 1-1> INFO:FlashInfo: 0 0 CD 1 0 4 4 0 28 0 1
14:18:14 	Get FlashInfo Success
14:18:14 	 Prepare IDB Start
14:18:14 	<LAYER 1-1> INFO:CS(1)		(14752MB)		(SAMSUNG)
14:18:14 	Prepare IDB Success
14:18:14 	Download IDB Start
14:18:14 	Download IDB Success
14:18:14 	Reset Device Start
14:18:16 	Reset Device Success
14:18:16 	Wait For Loader Start
14:18:17 	Wait For Loader Success
14:18:17 	Test Device Start
14:18:17 	Test Device Success
14:18:17 	Download Firmware Start
14:18:17 	<LAYER 1-1> INFO:Start to download trust,offset=0x4000,size=                                                         4194304
14:18:18 	<LAYER 1-1> INFO:Start to download uboot,offset=0x2000,size=                                                         4194304
14:18:20 	<LAYER 1-1> INFO:Start to download misc,offset=0x8000,size=                                                           49152
14:18:20 	<LAYER 1-1> INFO:Start to download resource,offset=0xa000,size=                                                          251904
14:18:20 	<LAYER 1-1> INFO:Start to download kernel,offset=0x12000,size=                                                        21174292
14:18:27 	<LAYER 1-1> INFO:Start to download boot,offset=0x22000,size=                                                        22941696
14:18:35 	<LAYER 1-1> INFO:Start to download recovery,offset=0x32000,size=                                                        30859264
14:18:45 	<LAYER 1-1> INFO:Start to download system,offset=0x18c000,size=                                                      1345618164
14:26:20 	<LAYER 1-1> INFO:Start to download vendor,offset=0x594000,size=                                                       242786464
14:27:43 	<LAYER 1-1> INFO:Start to download oem,offset=0x696000,size=                                                          360596
14:35:25 	Download Firmware Success
14:35:25 	Reset Device Start
14:35:27 	Reset Device Success

(n.b. for this one I used another version of upgrade_tool with the new update.img from below, but it was the same with the previous version (of software and image))

all .img that are in the update_xxx.img are seems to be correctly uploaded (according to the dump from imgRePackerRK) :

Code:

update-10456.img.dump/Image-rk3368# du -b *
22941696	boot.img
21174280	kernel.img
21174292	kernel.img.krnl
237902	MiniLoaderAll.bin
49152	misc.img
360596	oem.img
887	parameter.txt
899	parameter.txt.parm
30859264	recovery.img
251904	resource.img
1345618164	system.img
4194304	trust.img
4194304	uboot.img
242786464	vendor.img

if I try with a newer version of update_tool, it stops and returns an error about the chip (and then rkflashtool that I use to be sure that the device is still responding froze and I have to remove battery and restart from begining) :

Code:

Linux_Upgrade_Tool_v1.57# ./upgrade_tool uf /tmp/update-10456.img
Program Data in /root/.config/upgrade_tool
Loading firmware...
Support Type:RK330A	FW Ver:7.1.00	FW Time:2020-10-21 12:13:56
Loader ver:2.60	Loader Time:2019-03-13 23:09:52
Check Chip Fail

Linux_Upgrade_Tool_v1.57# rkflashtool p
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3368...
rkflashtool: info: interface claimed
^C
(froze here, so ^C)

with the following log :

Code:

15:39:29 	Current process in Linux_Upgrade_Tool_v1.57
15:39:29 	Using /root/.config/upgrade_tool/config.ini
15:39:29 	Command Line: ./upgrade_tool uf /tmp/update-10456.img
15:39:29 	Current Device Location ID:11
15:39:29 	Test Device Start
15:39:29 	Test Device Success
15:39:34 	Error:RKU_Read_EX failed,err=-7
15:39:34 	ERROR:ReadCapability-->RKU_ReadCapability failed,err(-4)
15:39:34 	Check Chip Start
15:39:39 	Error:RKU_Write failed,err=-7
15:39:39 	ERROR:CheckChip-->RKU_ReadChipInfo failed,RetCode(-3)
15:39:39 	Check Chip Fail
15:39:39 	Command mode out

No I don't

neither

OK, ty a lot.
same md5 here, and I used that image too with same results, so I guess that it is not a problem with the update img.

About options with upgrade_tool :

Code:

Linux_Upgrade_Tool_v1.24# ./upgrade_tool -h

---------------------Tool Usage ---------------------
Help:             H
Quit:             Q
Version:          V
Clear Screen:     CS
------------------Upgrade Command ------------------
ChooseDevice:		CD
SwitchDevice:		SD
UpgradeFirmware:	UF <Firmware>
UpgradeLoader:		UL <Loader>
DownloadImage:		DI <-p|-b|-k|-s|-r|-m image> [parameter file]
DownloadBoot:		DB <Loader>
EraseFlash:		EF <Loader|firmware>
LowerFormat:		LF
----------------Professional Command -----------------
TestDevice:		TD
ResetDevice:		RD [subcode]
ResetPipe:		RP [pipe]
ReadFlashID:		RID
ReadFlashInfo:		RFI
ReadChipInfo:		RCI
ReadSector:		RS  <BeginSec> <SectorLen> [-decode] [File]
WriteSector:		WS  <BeginSec> <File>
ReadLBA:		RL  <BeginSec> <SectorLen> [File]
WriteLBA:		WL  <BeginSec> <File>
EraseBlock:		EB <CS> <BeginBlock> <BlokcLen> [--Force]
-------------------------------------------------------

According to others the lf (low format) or even ef (erasing flash) options can be used when having errors. I'm really not sure about those options, but maybe erasing flash at first then upload the image like I did before could make all more clean? :/

Yeah I'm at a loss, I did find out that I was dumb and I sent my Mars to my friend with 6.1 they said, but that other img has been used before and Both of those at this point have used to flash the device successfully. I would only continue to try to use the newest img going forward though. Perhaps you could try like you said to erase the device beforehand. Also maybe before you do see if you can get into recovery (hold power long enough for the device to fully be off , then hold the reset button in while pressing power to boot the device and don't remove the reset pin till you see a recovery options screen or a broken looking android.) Then it should be the reset pin to move up and down that screen, and power to select. If you can get in there try to wipe the cache or pick factory reset.

EDIT: WALDY on here also long a time ago uploaded their fresh non touched dump of the 6.1 version and it is what people use normally to un soft brick.

https://mega.nz/#!v24TgaTS!wfsf9f0r8...omSX0OA4Mr27Gc

it is normally used by loading the config file for it in the windows tool and the respected imgs though. Perhaps you can find a way to get it to load those as well.

these are the instructions.
https://mega.nz/#!yug3wKSS!WMb2ZAzcj...Tdw8ZU2l4F7hSM

ilyats · 05-09-2021, 02:55 PM

Many people, including myself, tried to reflash a Likebook device under linux, AFAIK nobody succeeded. I suspect Linux driver for Rockchip tablets is faulty. I'd advice just get Windows running (possibly in a virtual machine) and use the Windows tool.

rvcjew · 05-09-2021, 03:27 PM

Quote:

Originally Posted by ilyats

Many people, including myself, tried to reflash a Likebook device under linux, AFAIK nobody succeeded. I suspect Linux driver for Rockchip tablets is faulty. I'd advice just get Windows running (possibly in a virtual machine) and use the Windows tool.

They said they don't have enough free space to make a vm at this time. I thought about doing this and was like someone had to have done this for something and yeah it does exist.

https://7labs.io/tips-tricks/usb-network-gate.html

Cross platform usb. Could technically link their tablet to a windows user on here and we could flash it lol. Theoretically it should pass through the usb device to windows as if plugged in. But I bet you need to open the ports they talk about which is generally not a good idea.

At least their are options. Maybe they have a friend who can help them this way.

ilyats · 05-14-2021, 01:58 AM

Quote:

Originally Posted by prout

OK, I've tried the the holding part, but still no device with adb.

adb will only see your device if its system is running and debug over USB is enabled. If rkflashtool and RockChip update tool see it, than it is in the correct mode for reflashing. According to my experiences with reflashing Muses (which has the same motherboard and SoC as Mars) described here it should be listed by lsusb as

Code:

 ID 2207:0006 Fuzhou Rockchip Electronics Company rk30xx

05-05-2021, 03:02 AM	#18
bazz2004 Groupie Posts: 197 Karma: 14745 Join Date: May 2020 Device: Boyue Alita	I just realised that these are throwaway devices. Try finding a replacement battery for an e-reader. The only ones you will find are for early Kindles or Sony devices. There have already been questions raised about the Boyue batteries but they do not supply or fit replacements. Ideally the device would show a battery reading when you try to turn it on but that feature presumably can't be incorporated into the firmware. Last edited by bazz2004; 05-05-2021 at 03:05 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Likebook Mars If you want to go back to 2.3.0	bekar	Boyue	2	08-29-2022 01:34 PM
Boyue Likebook Mars T80D boot starting problem	asuagar	Boyue	55	06-08-2022 12:27 AM
Likebook Mars battery life for e-book reading	Incanus	Boyue	14	05-06-2019 11:15 AM
Apps for Boyue Likebook Mars T80D (Android 6)	nick2011	Boyue	0	12-31-2018 12:04 PM
KIndle Touch bring back to life	cameleon2605	Amazon Kindle	0	11-25-2012 03:59 PM

05-04-2021, 04:31 PM	#17
prout Member Posts: 10 Karma: 146 Join Date: May 2021 Device: none	(oops, I forgot to say that I have replugged the battery before starting the "upgrade_tool")

05-05-2021, 05:19 AM	#20
bazz2004 Groupie Posts: 197 Karma: 14745 Join Date: May 2020 Device: Boyue Alita	Boyue is not a religious experience for the rest of us ottischwenk. iPads aren't relevant here although mine has worked with zero issues for years now. There are replacement batteries available to buy for them and Apple have numerous service centres. Chinese made android devices are unable to offer meaningful support - you are it.

05-05-2021, 07:23 AM	#22
prout Member Posts: 10 Karma: 146 Join Date: May 2021 Device: none	excuse me but can we stay on topic please? So, I restarted the update.img (with a full batterie, so no problem here, batterie doesn't drop voltage so it is not a batterie problem) with "upgrade_tool", but I have exactly the same problem with a black screen as mentioned before. Is it a image problem? Is it normal and I have to wait 150 hours? What should I have after this update (like: you have a "circle with ereasing writing under, then it happens this and that for ~ X time" etc.)

05-05-2021, 11:01 AM	#23
issybird o saeclum infacetum Posts: 21,295 Karma: 234636059 Join Date: Oct 2010 Location: New England Device: Mini, H2O, Glo HD, Aura One, PW4, PW5	Moderator Notice An OP’s request to stay on topic is to be honored. Also, issues are to be reported and not moderated by individual posters and language must remain civil. Two posts have been deleted.

05-09-2021, 02:55 PM	#28
ilyats Connoisseur Posts: 95 Karma: 144 Join Date: May 2018 Device: Boyue Likebook Muses T78D	Many people, including myself, tried to reflash a Likebook device under linux, AFAIK nobody succeeded. I suspect Linux driver for Rockchip tablets is faulty. I'd advice just get Windows running (possibly in a virtual machine) and use the Windows tool.

Advert

Advert