yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Minto107:
Yeah you're absolutely right about that Bro. I had Samsung Galaxy Tab 3 3G before and it was lagging so much and also battery life was only a bit better than on Tab S8. And our S8-50 is 1200p not 1080p ;) it's quiet good but for now where most monitors are 1080p and 16:9 ratio 1200p is useless and we have stripes on YouTube or watching 720/1080p videos

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] smogan:
were you able to recover? I just tried to flash back stock 4.4 with intel flash tool and it fails. just tried to install xposed, but doesnt boot anymore
[Android Q&A, Help & Troubleshooting] haerwu:
Just go to recovery and install "xposed-uninstaller".
[Android Q&A, Help & Troubleshooting] luckypatak:
LENOVO tabs8-50f unknown bootloader isuess? what this mean*?
[Android Q&A, Help & Troubleshooting] Minto107:
Where did you get that? I never heard about something like that

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] luckypatak:
I use intelandroid-FBRL 07-24-2014 to enter in twrp recovery and then when tablet restart to recovery they give me message fastboot cmd wait and there is in info bootloader unknown
[Android Q&A, Help & Troubleshooting] RTouris:
No feedback on the GPS-battery-affecting issue of the stock camera app? hm...
[Android Q&A, Help & Troubleshooting] social-design-concepts:
It doesn't know the status of secure boot.

Edited : The fastboot drivers are not installed or installed wrong.

It's in the new version of droidboot

But I figured out how to boot custom boot.img too. Process won't be shared until after all 3 version of the S8-50 receive lollipop.

I knew 64bit would bring good things :) time to start roasting marshmallows this weekend.
[Android Q&A, Help & Troubleshooting] Minto107:
I bet it'll be working very nice with our hardware :D CM13 coming? :D we need to be thankful to Lenovo for that goodies :D

Wysłane z mojego GT-I9305 przy użyciu Tapatalka

---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------

PS. Where are you fetching links to firmware? Just curious ;)

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] luckypatak:
so for now i cant root my device ,till fix this isuess?
[Android Q&A, Help & Troubleshooting] social-design-concepts:
logcat

but these address generate the xml file that the update app looks at for download links :

Tab S8-50F : http://fus.lenovomm.com/firmware/3....OW&devicemodel=LenovoTABS8-50FROW-5&locale=en

Tab S8-50L : http://fus.lenovomm.com/firmware/3....OW&devicemodel=LenovoTABS8-50LROW-5&locale=en

Tab S8-50LC : http://fus.lenovomm.com/firmware/3....W&devicemodel=LenovoTABS8-50LCROW-5&locale=en

the &devicemodel= could change so you might need to logcat
[Android Q&A, Help & Troubleshooting] Minto107:
I understand ;) it's probably the command that is sent by an updater app yeah? I saw something similar on my old HTC phone ;)

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] KainXSS:
thats great, do you think you will be able to cook a build on the weekend though, still its great news its possible to modify boot.

also, I tried getting windows 10(had to use 64bit) to work but still got acpi error. So after booting back to android and trying ./efibootmgr -v I noticed the output changed.

root@S8-50F:/data/local/tmp # ./efibootmgr -v
./efibootmgr -v
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0000,0001,0003,0005,0004,0002
Boot0000* EFI Hard Drive ACPI(a0341d0,0)PCI(17,0)Controller(0)
Boot0001* EFI Internal Shell MM(b,fff68000,fff97fff)
Boot0002* EFI Internal Shell MM(b,fff50000,fff8ffff)
Boot0003* EFI USB Device ACPI(a0341d0,0)PCI(14,0)USB(3,0)USB(0,0)
Boot0004* Enter Setup
Boot0005* EFI USB Device ACPI(a0341d0,0)PCI(14,0)USB(3,0)USB(1,0)

works fine but wondering why it changed.
[Android Q&A, Help & Troubleshooting] luckypatak:
on cmd when i start the faastboot tethered recovery launcher 07.34.2015 stay this _

DEVICE STATUS ADB-ONLINE

DEVICE INFORMATION Baytrail0E674A18 device

and waiting device

and on my lenovo tab s8-50F is message

E:no valid installer medium found

any idea?
[Android Q&A, Help & Troubleshooting] Shump:
Nice job!!

Does this mean we should take the Lollipop update instead of holding onto Kit Kat in the hope for custom ROMS?
[Android Q&A, Help & Troubleshooting] Minto107:
You should update ASAP mate! Lollipop brings not only new Android OS version but UEFI and kernel is 64 bits, also someone discovered method how to unlock bootloader and how to run custom kernels(Cyanogen Mod for example) some things are broken but I bet Lenovo will fix that soon! Last KitKat firmware was very stable and bugless so we can hope same for lollipop ;)

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] smogan:
this is what i did. i have a lot of android devices and a lot of experience. but it seems the S8 is now bricked. Rigth after I turn it on, beneath the lenovo logo apears "Boot Failed. EFI Hard Drive". Same when I try to boot recovery. Even Fastboot Modes does not work.
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Check the three button power on. Let me know if you get a black screen that says fastboot starting.
[Android Q&A, Help & Troubleshooting] smogan:
yes, this works so far. but all attempts to flash images end with an error message.

---------- Post added at 02:14 AM ---------- Previous post was at 02:12 AM ----------

D:\Temp - 04>fastboot flash boot boot.img

sending 'boot' (9314 KB)...

OKAY [ 0.457s]

writing 'boot'...

FAILED (remote: unknown command)

finished. total time: 0.461s
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Did you back up with twrp after lollipop or do you need dumps? There are only two commands we run from that screen. But you'll need dumps from lollipop first.
[Android Q&A, Help & Troubleshooting] smogan:
sadly I didn't make any backup. cause I thought in worst case I can flash back stock 4.4 with Intel Flash tool as I already did for a couple of times. but intel flash tool also only shows errors.
[Android Q&A, Help & Troubleshooting] social-design-concepts:
You can't downgrade yet. I'll get the dumps together and uploaded. You'll probably have to run the commands manually though. Power off and don't plug it in conserve your battery.
[Android Q&A, Help & Troubleshooting] smogan:
Aye aye, Sir :)

Manual Commands are no Problem. Thank You so far!

So it will not charge in the current state?
[Android Q&A, Help & Troubleshooting] social-design-concepts:
I don't believe so, it uses one of the kernel images for charge os mode.

uploading. . .
[Android Q&A, Help & Troubleshooting] hama2:
new update to Android 5 OTA

yesterday in germany the ota android 5 update ..

lcd dendsity 320
[Android Q&A, Help & Troubleshooting] gyb001:
Bootloader unlock

0. Install the latest firmware S00456 (lollipop)

1. turn on the ADB

2. download this S8unlocker.zip

3. unzip

4. run exe file

5. connect adb

6. wait for unlock

7. Enjoy it! :cool::cool:

This is REAL_BALIKA011 's job, not mine.

source
[Android Q&A, Help & Troubleshooting] social-design-concepts:
i don't run things that don't give a description of what it is actually going to be doing. i'll share mine method later. they look to be the same concept.
[Android Q&A, Help & Troubleshooting] Minto107:
I'll trust your methods mate! Hope it'll be for LTE model also but there isn't still lollipop on LTE variant. It's quite annoying because it was told to get update yesterday or today's morning and still no info about rolling out update :( it's pretty strange that more expensive version of S8-50 have to wait longer but we can only wait ;)

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] social-design-concepts:
I'm not saying I don't trust his method, I just have a personal policy that I don't run random .exe and I don't flash / run .efi that I can't verify the source they came from.
[Android Q&A, Help & Troubleshooting] gyb001:
He uses a semi-backdoor to bypass the signature check. It only works whit 64bit. He don't wants to share more details, because he wants to keep it unfixed. You want to keep your device unlocked, don't you? Ps.: Do not apply any ota uptate. This may fix the bug and relock your bootloader.
[Android Q&A, Help & Troubleshooting] Minto107:
You can install OTA but just without updating fastboot/bootloader like many S3 LTE users are doing to avoid Knox system

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] TommyDN:
I don't think Lenovo will release any more OTA's if you saw their lollipop release behaviour..
[Android Q&A, Help & Troubleshooting] Minto107:
And may they should release lollipop for all variants first(LTE users are still waiting, wtf) At least I hope that LTE will has Dolby fixed

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] khanghua:
*beep* Lienovo.........
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Oh I didn't have to use any "semi backdoors" to bypass signature checks. I'll stick with my method then, I still have to do some testing first before I release it.
[Android Q&A, Help & Troubleshooting] Minto107:
Are you trying on unsigned stock boot image or on custom stock based one? And also how is lollipop after 3 days? Can't wait to see on my LTE one...

Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] khanghua:
same here

can't wait for Lollipop :(
[Android Q&A, Help & Troubleshooting] Minto107:
Was hoping for update today but as we can see its today has nearly ended so no more hope for update today... Lenovo please...

Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] khanghua:
I think the more we f.*beep* them, the sooner we can get that f*beep*ing update :P
[Android Q&A, Help & Troubleshooting] Minto107:
I can wait but I want stable and bugless update ;) and I'll be very happy ;)

Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] TommyDN:
I'm getting the same error now, but for me it happened out of nowhere the next day i turned on my tablet.. :confused:
[Android Q&A, Help & Troubleshooting] Minto107:
This error was explained somewhere before. As I remember it's damaged eMMC memory or broken partition table... Try to write on Lenovo forums and get help from lenovo
[Android Q&A, Help & Troubleshooting] TommyDN:
I can enter some kind of stripped down fastboot mode with the 3 button boot method but the Intel phone flash tool won't work.
[Android Q&A, Help & Troubleshooting] Minto107:
Can you get to stock android recovery?
[Android Q&A, Help & Troubleshooting] TommyDN:
Nope just fastboot mode just like the other guy i replied to earlier.
[Android Q&A, Help & Troubleshooting] social-design-concepts:
I sent then some files I'll have to check with them
[Android Q&A, Help & Troubleshooting] smogan:
I am very curious but patient, how to unbrick the S8.
[Android Q&A, Help & Troubleshooting] social-design-concepts:
So fastboot boot droidboot.img doesnt work?
[Android Q&A, Help & Troubleshooting] smogan:
Just found your PM. Now downloading the big File and then we will see ;)
[Android Q&A, Help & Troubleshooting] TommyDN:
any chance you have the file for me too?
[Android Q&A, Help & Troubleshooting] smogan:
first let me try it. can now boot to bootloader again, and to stock recovery. but still problems with flashing system.img
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Let's see if it works first.

---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------

Its a sparse image it might need to be a raw image gzip. did you repartition?
[Android Q&A, Help & Troubleshooting] smogan:
I wrote a PM to you, seems it got lost :/

I used Phone Flasht Tool 4.4.2 to flash the package you sent me. all went fine until system.img

same error if I try to flash system.img via commandline.

D:\### ANDROID ###\Lenovo S8-50F\ANDROID-5.0.1_R2_S8-50F_S000456_151016_ROW>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.171s]
sending sparse 'system' (520512 KB)...
OKAY [ 18.723s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 20.053s

It seems Fone Flash Tool repartitioned.
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Try using simg2img to convert system.img back to a raw ext4 system.img and the compress it as a .gz and see if it flashes.
[Android Q&A, Help & Troubleshooting] smogan:
not sure if I did it right. used simg2img_win form https://github.com/KinglyWayne/simg2img_win

result: system.ext4.img / 2.147.483.648 Bytes

gzipped with Total Commander : system.ext4.img.gz / 1.172.472.177 Bytes

D:\...>fastboot flash system system.ext4.img.gz
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi

and fastboot.exe crashes. I do nit know a lot about gpiz, sorry :/
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Any errors with the starting the tethered twrp?
[Android Q&A, Help & Troubleshooting] smogan:
TWRP is working, but cant mount any mountpoints, except ESP and Factory
[Android Q&A, Help & Troubleshooting] RaawrItsTomi:
How's the "getting windows to run on this tablet" going? I'm really curious :angel::fingers-crossed:
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Run the partitioning commands manually and post the output.
[Android Q&A, Help & Troubleshooting] smogan:
not sure what are the commands?

>fastboot oem start_partitioning
...
(bootloader) Start partitioning

OKAY [ 0.104s]
finished. total time: 0.105s

>fastboot oem partition partition.tbl
...
FAILED (remote: Can't open partition file)
finished. total time: 0.069s

>

---------- Post added at 10:55 PM ---------- Previous post was at 10:35 PM ----------

Now I manually redone the commands from the Phone Flash Tool logfile:

>fastboot devices
Baytrail0E064B4A fastboot

>fastboot oem start_partitioning
...
(bootloader) Start partitioning

OKAY [ 0.101s]
finished. total time: 0.101s

>fastboot flash /tmp/partition.tbl partition.tbl"
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (1 KB)...
OKAY [ 0.070s]
writing '/tmp/partition.tbl'...
OKAY [ 0.090s]
finished. total time: 0.160s

>fastboot oem partition /tmp/partition.tbl
...
OKAY [ 0.129s]
finished. total time: 0.131s

>fastboot erase system
erasing 'system'...
OKAY [ 1.196s]
finished. total time: 1.196s

>fastboot erase cache
erasing 'cache'...
OKAY [ 0.233s]
finished. total time: 0.233s

>fastboot erase config
erasing 'config'...
OKAY [ 0.165s]
finished. total time: 0.166s

>fastboot erase data
erasing 'data'...
OKAY [ 6.335s]
finished. total time: 6.335s

>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning

OKAY [ 0.091s]
finished. total time: 0.092s

>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.179s]
writing 'ESP'...
OKAY [ 0.797s]
finished. total time: 1.976s

>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (16384 KB)...
OKAY [ 0.603s]
writing 'fastboot'...
OKAY [ 0.444s]
finished. total time: 1.048s

>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.601s]
writing 'boot'...
OKAY [ 0.444s]
finished. total time: 1.046s

>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.601s]
writing 'recovery'...
OKAY [ 0.437s]
finished. total time: 1.039s

>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.169s]
sending sparse 'system' (520512 KB)...
OKAY [ 18.295s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 19.620s
[Android Q&A, Help & Troubleshooting] social-design-concepts:
try :

fastboot -w

fastboot oem format system
[Android Q&A, Help & Troubleshooting] smogan:
>fastboot -w
erasing 'userdata'...
OKAY [ 6.335s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 12505296896
Block size: 4096
Blocks per group: 32768
Inodes per group: 8128
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3053051
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/764032 inodes and 88241/3053051 blocks
error: wipe_block_device: wipe not supported on non-linux platforms
sending 'userdata' (0 KB)...
FAILED ()
finished. total time: 6.487s

>fastboot oem format system
...
FAILED (remote: unknown OEM command)
finished. total time: 0.047s

>fastboot format system
formatting 'system' partition...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
error: wipe_block_device: wipe not supported on non-linux platforms
sending 'system' (0 KB)...
FAILED ()
finished. total time: 0.200s

>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.186s]
sending sparse 'system' (520512 KB)...
OKAY [ 18.341s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 19.677s

i believe it is time to give up?
[Android Q&A, Help & Troubleshooting] Minto107:
It's always stuck at flashing command error... You probably mentioned it before but were you on lollipop bootloader before this problem?

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] haerwu:
Is there a way to get some new threads and split this one into parts?

We have generic questions, unbrick studies, booting other systems discussions, lollipop update stories. All in one thread.
[Android Q&A, Help & Troubleshooting] smogan:
I upgraded from 4.4 to Lollipop a couple of days before. used the tablet for one or two days. then rooted it. all went fine. then I tried to install xposed, because I use(d) it on many devices before. after that the tablet refused to boot. I tried to uninstall xposed with the uninstall zip. still no boot. tried to flash it back with phone flash tool to 4.4. I did this already 3-4 times before. This Time it didn't work. Always got stuck. Tried it several Times. Suddenly the Tablet rebooted to this EFI Menu that looks like a PC BIOS. Because there was no other possibility, I powered the device off. After power on there was the message that there is no boot device or so. cant remember. nothing woked anymore, exept the three button fastboot mode.
[Android Q&A, Help & Troubleshooting] TommyDN:
I've been able to decompress the img and flash it but i'm also getting the error at system..

But using 'fastboot flash system system.img -S 0' seems to push the whole file, but the system bugs out when its flashing.. screen just flashes on and off? at least for me.
[Android Q&A, Help & Troubleshooting] Minto107:
Xposed framework isn't safe and I don't recommend it to anyone, I don't see a point of running Xposed on OEM's ROM(Like I do on my S3L just stock ROM some mods, Lenovo locked and still on 4.4). It's good for AOSP/CM just to get even more functionality. After updating to 5.0.1 there's no coming back for now. Flashing stock image is not possible(downupgrading bootloader probably) anyway it's very strange that after booting to UEFI you got hard bricked, my PC many times hangs at BIOS, and even turning off by PSU doesn't make any problem to boot it in next 5 mins... Helpful for you would be a full 5.0.1 image to flash thorough Intel Flash Tool but for now there isn't such image unfortunately

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] Spitras:
I am exactly on same page here :D Updated to lolipop, rooted, installed xposed ang got into bootloop afterwards. it didnt even came in mind that downgrading can mess things up like that :( Wonder if Service Center can reflash everything back to normal or will offer me to buy new pcb? :D
[Android Q&A, Help & Troubleshooting] smogan:
I had a lot of Android-Devices in the last five or maybe six years? dont know. this is the first one I bricked. I rooted so many devices. Modified them in any way. Sony, Huawei, Lenovo, Samsung, Motorola, Asus, and of course Nexus Devices. Smartphones and also Tablets.

The last couple of years Xposed did a good job for me. Allowed me to customize Stock Roms... or add just some nice features so there often was no need for a custom rom. I also had Xposed on the S8 with 4.4 ... everything fine. So it was just naturally for me to try this. Bad Luck, IMHO.

This is the first Android Device I ever bricked!!!

Within the next days I will start searching an alternate tablet for me. Sadly Motorola makes no Tablets anymore. Their Phones are updated very frequently with new Updates. And Nexus 9 is too expensive. Lenovo's Update Strategy sucks.
[Android Q&A, Help & Troubleshooting] social-design-concepts:
I'm going to upload the whole twrp back up so you can try to restore it from external sdcard.
[Android Q&A, Help & Troubleshooting] smogan:
nice idea my friend... ;) thankyou!
[Android Q&A, Help & Troubleshooting] social-design-concepts:
PM Sent also try formatting the data, cache, and system partition through TWRP.
[Android Q&A, Help & Troubleshooting] smogan:
I dont know why, but it seems I cant send PMs .... There was no link inside your PM this time, only the Filename is shown. And I have another Idea: do you have the big update file from 4.4 tpo 5.0 ? maybe i can flash this one with stock revocery?
[Android Q&A, Help & Troubleshooting] Minto107:
Here you go: http://tabdl.ota.lenovomm.com/dls/v6/S8-50F_S000456_151016_ROW_WCF3.zip

I didn't test it because I have LTE variant but it's stock update from last KitKat update(150629 probably). It's official source, from Lenovo OTA service(like you'd like to download OTA from About Tablet) hope it can help you ;)

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] Minto107:
S8-50L still no lollipop update... Lenovo is playing with us? It's not that funny... This is so ****ing unfair that some has lollipop while being ROW and some can't! All ROW versions should get it the same day! Please Lenovo do us that favour and give us that damn lollipop!!

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] smogan:
Thank You!

Now I tried everything I could imagine. Tried to install this ZIP via stock and TWRP recovery. It always failures because the recoverys cant mount any system partitions.
[Android Q&A, Help & Troubleshooting] Minto107:
Have you tried formatting system in TWRP? It's very advanced tool and may some feature will work. I'd help you but I don't use TWRP anymore(on i9305 TWRP is a bit laggy, so I use latest Philz)

Wysłane z mojego GT-I9305 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] smogan:
TWRP cant format partitions it dont see/mount.

I sold my I9305 a week ago, and TWRP was not laggy for me ;)
[Android Q&A, Help & Troubleshooting] social-design-concepts:
Sorry just woke up here is the twrp backup : TWRP_BACKUPS_S8-50F_S000456_151016_ROW.7z
[Android Q&A, Help & Troubleshooting] Blackadder51:
I agree. Everything here is very interesting, but it's all getting a bit confusing. I'd really like to know the answer to some simple questions.

Is the OTA update to Lollipop completely safe or is it likely to brick my device?

Does it stop the brightness flickering many people have complained about?

Has the battery life been improved at all?

Are there any noticable performance improvements?

Does it give any other real benefits over KitKat?

Does it bring any problems that KitKat didn't suffer from?

Can it be rooted safely, without any danger of bricking the device?