Error after newly update Android 8 oreo on Philips 55PUS6412/12 - Philips, Sony, TCL Android TV

Hi guys,
I have a problem after my tv is updated to android 8 oreo version.
The HDMI's are gone from the "sources" menu and also they are gone even when the cables are connected properly to the box(for example) and to the tv.
I tried to update the software via USB but it says that unknown fs_type "emmc" for /linux_rootfs.(On Android Recovery mode)
Could you please give me some info how i can proceed in order to change the software or to downgrade to the working version.
For the usb i forgot to say that its FAT32 formatted, i tried with FAT also but its not working. the fs_type error is still present.

You mean the problem is caused by Android 8?

kkfashion said:
You mean the problem is caused by Android 8?
Click to expand...
Click to collapse
Yes , all of these problems are caused after update the new Android 8.
But i'm not sure why is this problem with the "cannot mount fs_type rootfs" from every USB flash drive, when i'm trying to reinstall the version of Android.

Related

Nextbook Flexx 11 how to dual boot android and 8.1/10

ok! where to even start...
I like many got this 2in1 at wal-mart and I live it. unfortunately I like many am not yet familiar with the new UEFI bootloader bios SOC stuff
heres what I do know and please correct me if im wrong. also please tell me if this 2 in 1 is and can be flashed the same as the asus t100
ok the Flexx11 has a bayntrail-t CR quad core processor 1.33-1.83ghz model Z3735F the t100 is3740
11.6" screen ips touchscreen at 1366x768 res
Efun is the corp and yifang vers.NX1106.1.02.008\139
THE BIOS IS YFG0315009112
it is a 32bit EFI bootloader
the reason I mention all of this is I have tried several times to dualboot androoid and each time ruined the computer and had to return it and I simply no longer wish to return it and love it to much to get something else
the first try the time began to lag and was unfixable for some reason the second time i somehow lost the keys booting and formatted wrong or something and the tablet bricked it would remain black with keyboard lit and no button combo could get it back no boot at all.
I am currently using AMIDUOS to run android kitkat and I love it but from what I understand it isnt compatible with win10 and really still isnt the same as the full android being on the tablet although really really close and awesome
but honestly I have been doing this stuff for years and now with this new windows secure boot and system on a chip stuff im lost
ever get anywhere with this?
I'm curious as well.
It has to be possible. I say that because I recently owned a ChuWi dual-boot device with the same Baytrail processor and SOC.
I wonder if it wouldn't be possible to take a system dump from one of the chuwi dualboot devices and flash it to the nextbook.
Sent from my Ascend Mate 2 using XDA Free mobile app
I'm also interested in doing this. It appears that the Nextbook Ares has the same hardware (minus 1GB RAM) but has Android. I contacted Nextbook to see if I could get a copy of the Ares Android firmware but was denied. If someone with the Ares could upload a backup that would be helpful.
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
64 bit processor?
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
Click to expand...
Click to collapse
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
GeneticJulia said:
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
Click to expand...
Click to collapse
It just won't boot the USB. At all. Unless it's 32-bit.
rowdyrocket said:
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
Click to expand...
Click to collapse
I'm loving Remix OS on here with dual boot. Having some issues though and I really want this to work.
Main and I mean main issue is no sound at all, no rotation is next in line and Bluetooth isn't working. Everything else works great.
This is so awesome its like Android lollipop with windows desktop functionality. Now if I can get the bugs fixed I will be in android hog heaven.
GREAT FIND BRO!!!!! EXACTLY what I was looking for maybe even better than.
for those interested here is the XDA section for all things REMIX OS
http://forum.xda-developers.com/remix
By the way for those who may want to know I installed dual boot onto the hard drive it went with no issues.Here's some tips for flexx 11
1. I used a partition manager such as easy partition manager to partition the C: drive regardless of what the tutorial said. Couldn't use windows disk management. I deleted the recovery for an extra 5 gigs (make a backup if you do) I used about 19 gigs from the C: drive and made an E: NTFS.
2.Also do not use the remix files from that tutorial use the ones here from the main site http://www.jide.com/remixos-for-pc they are newer and the ones from the other post where incomplete. Also the newer ones on the site now include OTA updating which is totally awesome.
3. I'm hoping this will help someone..... After I was all finished I expected it to dual boot as any other dual boot restart and then i would see options for the OS's not the case here I got stuck on this I was using easy BCD and trying all sorts of stuff, once I looked at the tut a little closer I realized you don't need any of that. Once your all done do a restart and it will go back to windows as usual. Now go to settings, then recovery, then advanced startup and choose from devices I think its the second option on the left list. There you will find Android OS click that and it will take you to your dual boot options. Sounds a lot more complicated than it really is. But believe me once you know this your better off.
And that's all I've got please and I mean please post here with any fixes especially for sound and if you have questions I will try to help.
Thanks
PS: I AM GETTING OCASIONAL LOCK UPS, MEANING THE OS FREEZES AND I HAVE TO RESTART BY HOLDING POWER.
Im not sure if this is good news or not...
Using the methos outlined I was not able to get audio bluetooth autorotate and other things to work but after a bit of digging I found out that remix os has an image specifically for nextbook baaytrail (Our PC) here: http://www.jide.com/remixos/devices
click other upper left.....
I cannot find instructions to install this though and using the other install instructions from here fail because the only part of the file to replace is the system image.
I also attempted the other install methods and easy BCD does not work for this PC
So if anyone can help to install this file specifically for our computer as well as verify that it works and what works and how you installed would be great
OK this is really cool I have made headway sort of.
I have installed kit kat android-x86-4.4-r3.img using the Androidx86-Installv24-5800.exe installer and i have rotation, root and it works pretty good for the most part wifi works great so far no bluetooth, it freezes during shut down and the major issue as in most cases is the sound. Im not sure about the camera now that I think about but i will check and report back here.
I really want the sound working on this and I woud be bigtime happy this forum could be solved as far as im concerned
From what I understand there is a bug with baytrail and linux where the spp port is pointed automatically to the usb or something. but for the life of me after weeks of scouring the internet cannot find a laymens guide to a simple fix for this. I'm really not even sure there is one because I'm yet find a rock solid confirmation of a solution
Update: camera doesn't work either
So far the 4.4.3 port is the best. I just can't seem to find any help whatsoever so its looking like so close yet so far away. Its a pure shame that audio and a few other major bugs are the only things in the way of this being a fully working and easy dual boot method.
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
murlig123 said:
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
Click to expand...
Click to collapse
Sorry for the late reply, use the installer and create a separate drive using C: like a D: or E: and get android 4.4 the .IMG that should work for you and the installer should do everything for you.
So use the uefi android installer after you partition a drive to load android 4.4 the uefi IMG
Its just going to piss you off though because there's no audio and seemingly no way to fix it, which is a crying shame ��
P.S. typically secure boot is off in the bios on this machine, but if by any chance you turned it on or the newer ones come that way make sure it is off or this will not work.
UEFI Settings
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
korycooper said:
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
Click to expand...
Click to collapse
Okay. So I was able to test this one of my co workers Nextbook and it seems like its a problem with mine.
This might be beneficial for us Flexx 11 users. It's a full port of Remix 2.0 to the Ares 8 with everything working except the camera rotation issue. Very promising. I've heard the hardware is similar. Working on attempting to install on mine. Anyone else tried it?
http://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
KorishanTalshin said:
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
Click to expand...
Click to collapse
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Wiebenor said:
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Click to expand...
Click to collapse
I realize this is a dead thread, but I had to chime in... I bought my NextBook Flexx 11 from Walmart 3 or 4 years ago and it shipped with Windows 10 Home, not Windows 8.1... However, IMHO, Windows 10 is a resource hog on this little device. I'm currently looking in to installing Linux...

SM-P607T stuck in 4.4.2

Hello everyone,
i bought the SM-P607T during my deployment in Afghanistan over Ebay USA . Spending my time there i tested the device and installed all updates etc. Back in Germany just my wife used it. Some weeks ago i noticed that an update to Lollipop should be avaible so i took the device to bring it up to date and i noticed some problems.
(Please note that i am just a noobie to flashing and rooting android and just follow guides to get to my goal.)
1. Device only loading while shut down. (After rooting and installation of TWRP it strangely started to load while on again even on PC USB connection)
2. Its not possible to connect the device with any PC.
3. OTA updates stop at around 27% and fail (KitKat 4.4.4)
[In TWRP shown
"E: Error executing updater binary in zip /data/fota/update.zip
E: Error installing zip file /data/fota/update.zip"]
Strange enough that the update info shown in android is Chinese Version
Tried to get some support with Samsung Europe but unfortunately they say US device US problem......
So what did i do in the meantime
1. Tried different loading devices frome Samsung and 3rd party companys. No changes.
2. Tried several different data cables to connect to 4 different PC. Even the one wich worked good with my Honor7 or the Galasy S4 mini dont do with the 607
3. My last try to fix this problem was to change the USB charging dock completely. Also didn´t change anything.
4. Now the step where i am currently stuck. I managed to root the device and install TWRP(v2.8.7.0) . Now tried to install Version P607TUVUBOI2 via SD Card.
Just followed diffenrent Guides on youtube and forums but im stuck at this.
Here is the message i got in TWRP recovery:
"Installing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
Checking for MD5 file....
Skipping MD5 check : no MD5 file found
Error flashing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
updating partition details......
Checked the *.zip on my PC there was just this file in: P607TUVUBOI2_P607TTMB1BOI2_P607TUVUBOI2_HOME.tar.md5
Downloaded the file from a different source again with same result
It would be very nice if someone is capable to help me with this and give me a hint what i possibly did wrong (Please do not mention not to buy in the US). For me it doesnt matter if i got a rooted or not routed version to install my main goal is to get rid of 4.4.2 . The problem with the not working USB connection is the biggest show stopper for me.
[email protected] said:
Hello everyone,
i bought the SM-P607T during my deployment in Afghanistan over Ebay USA . Spending my time there i tested the device and installed all updates etc. Back in Germany just my wife used it. Some weeks ago i noticed that an update to Lollipop should be avaible so i took the device to bring it up to date and i noticed some problems.
(Please note that i am just a noobie to flashing and rooting android and just follow guides to get to my goal.)
1. Device only loading while shut down. (After rooting and installation of TWRP it strangely started to load while on again even on PC USB connection)
2. Its not possible to connect the device with any PC.
3. OTA updates stop at around 27% and fail (KitKat 4.4.4)
[In TWRP shown
"E: Error executing updater binary in zip /data/fota/update.zip
E: Error installing zip file /data/fota/update.zip"]
Strange enough that the update info shown in android is Chinese Version
Tried to get some support with Samsung Europe but unfortunately they say US device US problem......
So what did i do in the meantime
1. Tried different loading devices frome Samsung and 3rd party companys. No changes.
2. Tried several different data cables to connect to 4 different PC. Even the one wich worked good with my Honor7 or the Galasy S4 mini dont do with the 607
3. My last try to fix this problem was to change the USB charging dock completely. Also didn´t change anything.
4. Now the step where i am currently stuck. I managed to root the device and install TWRP(v2.8.7.0) . Now tried to install Version P607TUVUBOI2 via SD Card.
Just followed diffenrent Guides on youtube and forums but im stuck at this.
Here is the message i got in TWRP recovery:
"Installing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
Checking for MD5 file....
Skipping MD5 check : no MD5 file found
Error flashing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
updating partition details......
Checked the *.zip on my PC there was just this file in: P607TUVUBOI2_P607TTMB1BOI2_P607TUVUBOI2_HOME.tar.md5
Downloaded the file from a different source again with same result
It would be very nice if someone is capable to help me with this and give me a hint what i possibly did wrong (Please do not mention not to buy in the US). For me it doesnt matter if i got a rooted or not routed version to install my main goal is to get rid of 4.4.2 . The problem with the not working USB connection is the biggest show stopper for me.
Click to expand...
Click to collapse
I really confused about your description? you using twrp to flash a .zip rom? then you mentioned about .md5 rom on your pc? how did you flash? With .md5 rom you need to use Odin to flash. Can you boot into download mode (hold down volume down + Home buttons then press power button)? If you able to boot to download mode, your pc should able to see the device and you would use Odin to flash the .md5 rom from your pc to the device. Also where did you download the .zip rom?

Out Of The Blue ZE551ML Internal Storage No Longer Accessible In Windows 7

I only connect my ZE551ML to my Windows 7 x64 when I've got to do firmware updates or transfer music, and I haven't done either in a while.
On my "MTP USB Device" driver I'm now getting: This device cannot start. (Code 10)
The ASUS Android Composite ADB and PC Link Interface drivers are loaded and fine.
Things that I've tried:
- the Asus android drivers
- the Intel android drivers
- the universal ADB drivers.
- different USB cables
- different USB slots
The perplexing thing is that the image that allows you to install "ASUS ZenUI PC Suite" is available as a CD drive, "PC Link" works when mirroring my phone onto my computer and using ADB from a command prompt can see my device.
I don't know what I've installed between the last time it worked to now, and I'm at wit's end with what I can do.
Anyone have a suggestion at a possible next step?
Do you by any chance have Windows 7N (one without media player)?
Mine did the same when i connected the missus MTK device.
Unfortunately i need hers to stay for future updates and for using MTK flashtools too.
Great news is the( share link ) built in asus app in M - never used it before until this , click asus share link app on phone whilst connect to PC (for the first installation) and then you can transfer to an from pc to sd (either sd) in share link settings.
Then after - uses your network for transfer ,no cables , saves charge port i guess and its -- Fast !
USBdeview can be used if you want to see/want/remove if old/new drivers might be causing conflicts but am quite happy with the share link app now,ps i`m on windows 10 and too also not sure whether an update came whilst installing MTK destroyed it too
chiudikas said:
Do you by any chance have Windows 7N (one without media player)?
Click to expand...
Click to collapse
No, I'm running Home Premium, and have both media player and media center.
timbernot said:
Mine did the same when i connected the missus MTK device.
Unfortunately i need hers to stay for future updates and for using MTK flashtools too.
Great news is the( share link ) built in asus app in M - never used it before until this , click asus share link app on phone whilst connect to PC (for the first installation) and then you can transfer to an from pc to sd (either sd) in share link settings.
Then after - uses your network for transfer ,no cables , saves charge port i guess and its -- Fast !
USBdeview can be used if you want to see/want/remove if old/new drivers might be causing conflicts but am quite happy with the share link app now,ps i`m on windows 10 and too also not sure whether an update came whilst installing MTK destroyed it too
Click to expand...
Click to collapse
I'm still on Lollipop... Though it does have a sharelink app as well. I've tried setting it up, and on my phone it can't see my microSD card.
I'll give USBdeview a go and see if uninstalling all the Samsung/Asus/Intel drivers does anything.
It's the strangest thing... why would I be able to see it in ADB, be able to install the PC Link programs from the ROM and yet not be able to see internal storage?
azthemansays said:
No, I'm running Home Premium, and have both media player and media center.
I'm still on Lollipop... Though it does have a sharelink app as well. I've tried setting it up, and on my phone it can't see my microSD card.
I'll give USBdeview a go and see if uninstalling all the Samsung/Asus/Intel drivers does anything.
It's the strangest thing... why would I be able to see it in ADB, be able to install the PC Link programs from the ROM and yet not be able to see internal storage?
Click to expand...
Click to collapse
Share link app - 3 dots -settings - storage location - click on /sdcard -- opens up to show internal sd and whatever your ext sd is called --select your choice -- click OK , you may have to allow rights to it in file manager :good:
Usbdeview should be ok
Why it happens ? conflicts with drivers i suspect
timbernot said:
Share link app - 3 dots -settings - storage location - click on /sdcard -- opens up to show internal sd and whatever your ext sd is called --select your choice -- click OK , you may have to allow rights to it in file manager :good:
Click to expand...
Click to collapse
That's the issue, when I get to that point it only shows "Internal Storage." As an aside, my phone's bootloader is unlocked and it's rooted.
*EDIT* - When I get to the part where I choose the directory, the file manager comes up with the "Recent" page. if I press the menu button, I get the option to hide SD card and file size, but in the list to the left it only lists "Internal Storage"
timbernot said:
Usbdeview should be ok
Why it happens ? conflicts with drivers i suspect
Click to expand...
Click to collapse
I just removed all the drivers that I could tell were related and am about to reboot.
phone settings - storage -- eject sd -- remount , set up sd for ext storage ? Never used this before so am at a loss , my ext sd was there when i clicked on /sdcard along side internal and after OK i followed on screen commands to allow it . Again , this is in M and never used it before on LP.
When you open file manager , your sd is there alongside internal or blanked out ?
Good luck hope you get it sorted , keep us posted BBFN
timbernot said:
phone settings - storage -- eject sd -- remount , set up sd for ext storage ? Never used this before so am at a loss , my ext sd was there when i clicked on /sdcard along side internal and after OK i followed on screen commands to allow it . Again , this is in M and never used it before on LP.
When you open file manager , your sd is there alongside internal or blanked out ?
Good luck hope you get it sorted , keep us posted BBFN
Click to expand...
Click to collapse
Still run into the same issue after remounting. It lets me select my internal, but not my SD. I guess it'll have to do for the time being - use it to move from computer to internal, then move it from internal to external.
And Removing selective ones in USBdeview still gave me the same issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so I went ahead and uninstalled all the ones that were for the specific USB slot, and am about to reset. Fingers crossed...
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
ps , the time you spent trying to fix this
upgrade to M latest , better battery etc etc
timbernot said:
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
ps , the time you spent trying to fix this
upgrade to M latest , better battery etc etc
Click to expand...
Click to collapse
I can't upgrade to M without being able to transfer files to my phone :laugh::crying:
And more importantly, I don't know if upgrading would change anything when it comes to the Windows 7 drivers. I keep trying to update driver to the Asus ones, but it keeps reverting to the generic "MTP USB Device" one. I've even tried to go into the windows inf files and remove that generic driver, but then windows won't accept the Asus ones at all.
When I go into the "feedback and help" section I get an error:
I've just about had it up to here with this phone. At the beginning it was giving me similar issues but I managed to sort it out... and now we're back to the issues that occurred back near the phone's launch. Full goddamn circle.
What build /date in settings ?
We gonna get you updated v soon .
First you need to unroot it.
Then fastboot flash stock recovery which corresponds with your build..
Then adb sideload a fresh copy of the build your on .You know how to perform these tasks above ???
If not , we do it soon
last but least don't smash it up
Have a read thru here to get general idea what needs doing
http://forum.xda-developers.com/zenfone2/help/how-recovery-t3514205
---------- Post added at 02:53 AM ---------- Previous post was at 02:44 AM ----------
azthemansays said:
I can't upgrade to M without being able to transfer files to my phone :laugh::crying:
And more importantly, I don't know if upgrading would change anything when it comes to the Windows 7 drivers. I keep trying to update driver to the Asus ones, but it keeps reverting to the generic "MTP USB Device" one. I've even tried to go into the windows inf files and remove that generic driver, but then windows won't accept the Asus ones at all.
When I go into the "feedback and help" section I get an error:
I've just about had it up to here with this phone. At the beginning it was giving me similar issues but I managed to sort it out... and now we're back to the issues that occurred back near the phone's launch. Full goddamn circle.
Click to expand...
Click to collapse
keep cal.m
timbernot said:
What build /date in settings ?
We gonna get you updated v soon .
First you need to unroot it.
Then fastboot flash stock recovery which corresponds with your build..
Then adb sideload a fresh copy of the build your on .You know how to perform these tasks above ???
If not , we do it soon
last but least don't smash it up
keep cal.m
Click to expand...
Click to collapse
Haha, thank you. I'll try to stay calm.
I'm sitting at 194 right now and the security patch level was last updated July 1, 2016.
This phone is my daily driver and I need to go to bed, but I'll Titanium Backup the apps and make a nandroid backup tomorrow as soon as I get home from work so I can start flashing.
It's been awhile... should I flash back the stock recovery before I unroot? And it's been giving me issues with the micro SD card occasionally unmounting on it's own as well as Google Play services crashing at random times (I've tried all the tricks & tips up to uninstalling it to get rid of corrupted installation, but it still persists)... Should I do a factory reset after flashing the stock image just to try to clear everything up? I'd have to move everything to my microSD card first though...
azthemansays said:
Haha, thank you. I'll try to stay calm.
I'm sitting at 194 right now and the security patch level was last updated July 1, 2016.
This phone is my daily driver and I need to go to bed, but I'll Titanium Backup the apps and make a nandroid backup tomorrow as soon as I get home from work so I can start flashing.
It's been awhile... should I flash back the stock recovery before I unroot? And it's been giving me issues with the micro SD card occasionally unmounting on it's own as well as Google Play services crashing at random times (I've tried all the tricks & tips up to uninstalling it to get rid of corrupted installation, but it still persists)... Should I do a factory reset after flashing the stock image just to try to clear everything up? I'd have to move everything to my microSD card first though...
Click to expand...
Click to collapse
First - transfer your stuff to pc off internal thru sharelink
unroot , flash back stock recovery .194 - reboot to recovery , update over adb , adb sideload .196 stock firmware , which should be renamed to MOFD_SDUPDATE and put in your fastboot/adb folder previously
adb cmd >
adb sideload MOFD_SDUPDATE.zip
set up not connecting to wifi - skip everything you can-- factory reset .
Set up correctly this time . Run for 3 days without any modifications . Make sure everything is running correctly :good:
timbernot said:
First - transfer your stuff to pc off internal thru sharelink
Click to expand...
Click to collapse
Already running into issues with the first step. Share Link gets to about 100mb transferred, then my phone's screen blacks out and is non-responsive, though it shows touchscreen presses (I have that turned on in developer settings). The transfer hits around 200mb and then the transfer gets cancelled. It's also rebooted twice.
This is getting to ludicrous levels.
*EDIT* - I tried uninstalling all the USB controllers in Windows Device manager in case they were corrupted, but I'm still getting the same failure with the generic "MTP USB Device" being installed instead of the Asus one and still getting that yellow exclamation mark. When I try to update it to the Asus one, it fails and disappears when I unplug and replug the phone. This is maddening because it was working in October...
*EDIT 2* - I'm thinking of testing it on another windows installation... I've got some spare HD space that i could partition and install another copy of my Win 7 on to see if it's my Windows or phone that's corrupted. If it's not my phone, I'll be able to transfer everything out...
Hey some news , after reading what you are experiencing - I remembered i have another lappy with windows 10 on in bedroom wardrobe - Not been used for nearly a yr , fired it up with wifi off and both my drives are visible
So , mine IS either MTK driver conflict or a windows update or both
Whatever , i will update it today and test further.
This does`nt explain your sharelink probs tho, mine transferred 443mbs of CM14.1 in 3 mins just now with the same prob you have.
Use file manager instead to transfer to ext SD. Instead of sharelink
And go about sorting it out , with whats already mentioned and with the fresh copy of 7 - hopefully it is windows and not the phone you said you had probs with from new
So it failed to install the driver in the new Windows 7 install, but somehow booting into recovery allowed me to access and copy everything off of internal storage. But of course, booting back into normal mode breaks it again.
I'm just going through backing up my SMS and using Titanium backup for the apps and I'll be ready to take the next step.
azthemansays said:
So it failed to install the driver in the new Windows 7 install, but somehow booting into recovery allowed me to access and copy everything off of internal storage. But of course, booting back into normal mode breaks it again.
I'm just going through backing up my SMS and using Titanium backup for the apps and I'll be ready to take the next step.
Click to expand...
Click to collapse
Are you familiar with flashtools ?
It's just another method to flash a raw file in fastboot boot loader state .and boots you into system by itself after about 10 mins..but I'm a bit unsure you should use it with the probs re screen blanking earlier with share app.
Maybe we keep that as a last resort
good luck
timbernot said:
Are you familiar with flashtools ?
It's just another method to flash a raw file in fastboot boot loader state .and boots you into system by itself after about 10 mins..but I'm a bit unsure you should use it with the probs re screen blanking earlier with share app.
Maybe we keep that as a last resort
good luck
Click to expand...
Click to collapse
My usual method of Flashing OTAs and ROMS was using this guide. I'm not familiar with flashtools, but I've used Odin before and I'm a quick study.
Now, I've got a few things that I would normally take back to stock/remove before unrooting and updating:
- Adaway hosts files
- busybox
- Viper4android sound.conf mod
- build.prop modification for permissive SELinux
- might be more but I can't remember.
I also recall flashing a new kernel at some point, but it was a while ago and I don't remember how to find out if what I have now is stock or not. I think it was this one.
Do I need to worry about taking all that back to stock before reflashing .194?
I usually edit the OTAs so I could flash them with TWRP, so I never had to flash stock recovery back in the past... what's the ADB name for the recovery partition?
*EDIT* - I'm also not familiar with all this new stuff like Magisk 8 and seamless root. Is this the go-to method for rooting 6.0? I like the sound of being able to root and unroot on the fly to bypass root detection by apps. I think I want to flash CleanSTOCK rather than just stock MM if it's less bloated.
azthemansays said:
My usual method of Flashing OTAs and ROMS was using this guide. I'm not familiar with flashtools, but I've used Odin before and I'm a quick study.
Now, I've got a few things that I would normally take back to stock/remove before unrooting and updating:
- Adaway hosts files
- busybox
- Viper4android sound.conf mod
- build.prop modification for permissive SELinux
- might be more but I can't remember.
I also recall flashing a new kernel at some point, but it was a while ago and I don't remember how to find out if what I have now is stock or not. I think it was this one.
Do I need to worry about taking all that back to stock before reflashing .194?
I usually edit the OTAs so I could flash them with TWRP, so I never had to flash stock recovery back in the past... what's the ADB name for the recovery partition?
*EDIT* - I'm also not familiar with all this new stuff like Magisk 8 and seamless root. Is this the go-to method for rooting 6.0? I like the sound of being able to root and unroot on the fly to bypass root detection by apps. I think I want to flash CleanSTOCK rather than just stock MM if it's less bloated.
Click to expand...
Click to collapse
Lets just get you up and running stock for a few days -- No mods ok ?
I think its best we flash raw at bootloader state , refresh here i will add files to download ready and info how to:good:
Flashtools - http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar install and run as admin
Raw collection of and thanks go to Realyoti there - choose .196, bottom one last of the LP
https://yadi.sk/d/FijRoAVJtvRiG
Video
Ignore the first 2:17 mins - fast forward to 2:18 mins for flashtool flash and adding raw and general settings > choose wipe data to prevent any bugs from previous state
Note -- you just let it complete on its own , the video goes to show how to correct serial number , you dont need to -- once it starts flashing - let it finish
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
When up n running say a thank you to Realyoti here please
http://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
timbernot said:
Lets just get you up and running stock for a few days -- No mods ok ?
Click to expand...
Click to collapse
Haha, sorry for putting the cart before the donkey at the end there...
But I was asking if I need to remove any/all of these mods before flashing the raw file? And does the raw file also include the recovery partition? That's why I was asking where to flash "recovery.img" to go from TWRP to stock recovery...
Just 19% into transferring all my Titanium backups to Google Drive right now.

Enable apps to read OTG USB contents in Marshmallow/Nougat

If you are trying to use your OTG USB as music or video library in Marmshallow or Nougat, but your media player doesn't recognize the content of your usb, then follow these instructions.
Download the terminal from store in case you don't have one. Root is required. You only have to do this once:
Simply open terminal and type:
Code:
su
sm set-force-adoptable true
Now just insert OTG USB and it will be immediately recognized by music players and all other apps.
Additional info:
Do not safely eject the usb, in my case doing this I noticed some bugs, just directly unplug the otg.
My phone is LG G2 d802 and the rom is CM13 snapshot 20161220.
It Works, than you!
I tested in Lineage OS 14.
I want to try this, but I am using Nougat now. So, just in case it didn't work, how should I revert the code above? I am new to this thing actually. Thanks!
geraldalcos said:
I want to try this, but I am using Nougat now. So, just in case it didn't work, how should I revert the code above? I am new to this thing actually. Thanks!
Click to expand...
Click to collapse
Change "true" to "false".
I'm using jetAudio plus, everything works great, thanks!
(Nexus 5, 7.1.2)
I am not sure what happened or why, but this has suddenly stopped working for me. ?
Edit: Appears I might have been a bit hasty, looks to be working just fine now. Only thing is, there's no notification for the connected drive. It's a tiny little inconvenience, I know, but I prefer it was there. Any help would be much appreciated.
It's been a while since I thank you someone from Xda and all I can you are a genius!
I have been looking for a solution for days now for my nexus tablet car project. I bought a Tpms from China (I am about to return it actually) and it is not working due to some stock Rom external restrictions for Android 6.1 even I am rooted.
Again! Thanks to you Buddy!
Does the "sm set-force-adoptable true" setting change how sdcards are managed?
Do SD cards and USB sticks become readable only from the Android device?
Are SD cards and USB sticks formatted / deleted when connected to Android?
Sorry for the perhaps stupid questions, but until now I was sure that an adoptable memory was not readable by other devices.
Does this trick still work in Android 9?
I have this problem in Android 9, on a PX6 unit.
I cannot use external USB SSD disk, or USB stick for my MP3 archive.
Can anyone point to a solution for this that does not require rooting, or can anyone point to a very simple solution for rooting this device?
Very thankful if anyone knows.
I tried the command "sm set-force-adoptable true" and it will not work, it does not find the command SM.
Als the SU command will not run. I guess because i am not rooted.
Any suggestions here?
thanks!
/GF

help "your device has loaded a different operating system"

after trying to install PCT-L29 10.0.0.172 (C432E10R3P4) [Dload Method] I can't get out of this situation, "your device has loaded a different operating system"
did anyone happen? what can I do? or nothing? thanks
Flash the 171 and not 172, see this topic: https://forum.xda-developers.com/honor-view-20/development/stockroms-t3955026
Best Regards,
Toetje
Sadly you didn't read the warnings that you cannot upgrade to 10 with dload method and you have bricked your device. And there is 99% chance that you wont get it back. At least for now.
You'll need to wait for global android 10 release for view 20 and hope that somehow or someone will figure out working solution to upgrade with dload method. If not, sadly your phone is gone. (some user already took the device to huawei service centre and only sollution was changing the motherboard, it is not covered by warranty, so it is expensive.)
SOLVED
cheers SOLVED for those who were in my situation you should know that I installed the PCT-L29 10.0.0.171 (C432E10R3P4) version following the dload Force Upgrade method but you have to turn on the device only with the volume up and power on keys and it is reset screen from OTG Stick or Adapter C to A with USB Stick. :victory:
looneylv said:
Sadly you didn't read the warnings that you cannot upgrade to 10 with dload method and you have bricked your device. And there is 99% chance that you wont get it back. At least for now.
You'll need to wait for global android 10 release for view 20 and hope that somehow or someone will figure out working solution to upgrade with dload method. If not, sadly your phone is gone. (some user already took the device to huawei service centre and only sollution was changing the motherboard, it is not covered by warranty, so it is expensive.)
Click to expand...
Click to collapse
This is not true, the dload method works just fine for 171, however we cannot upgrade using hstool/hisuite.
Best Regards,
Facing same problem
ofleda7 said:
cheers SOLVED for those who were in my situation you should know that I installed the PCT-L29 10.0.0.171 (C432E10R3P4) version following the dload Force Upgrade method but you have to turn on the device only with the volume up and power on keys and it is reset screen from OTG Stick or Adapter C to A with USB Stick. :victory:
Click to expand...
Click to collapse
Hi mate,
I'm facing the same problem right now, after my try to update it manually to Android 10.
After turning on its showing me thread: help "your device has loaded a different operating system"
And don't know how to fix it. When I try to flash it in the update mode with a dload file on a sd card, it stops installing after 5%
I really dont know what to do
Same problem here
Binban88 said:
Hi mate,
I'm facing the same problem right now, after my try to update it manually to Android 10.
After turning on its showing me thread: help "your device has loaded a different operating system"
And don't know how to fix it. When I try to flash it in the update mode with a dload file on a sd card, it stops installing after 5%
I really dont know what to do
Click to expand...
Click to collapse
The same goes here, I successfully updated my Honor V20 phone to "Huawei Honor View 20 PCT-L29 hw eea HLRCF Princeton-L29D 10.0.0.195" and now my phone is a vegetable and saying "your device has loaded a different operating system". Any solution? I think I just burnt 400 dollars.
My old version was PCT-L29 9.0.1.169(C636E1R2P1).
Se me bloqueo un p30 pro VOG-L04 y solo sube modo eRecovery, favor ayudarme con la solucion
Hello,
First of all, I'm sorry if I'm not in the right forum, but on the Mate 20 Lite forums, I'm not getting any responds...
I have a Huawei Mate 20 Lite, SNE-LX1 C432
I upgraded to EMUI 10 using the sd card update method a while ago, and ever since when I boot the phone "your device has loaded a different operating system" shows up.
I searched every thread I could, even this one, and tried a lot of things, but I just can't fix it...
Every time I download a firmware for the SNE-LX1 C432 and unzip it, I always get the SNE-LO1 cust file and preload file, but I can't find the SNE-LX1 cust file and preload file anywhere.
Does anyone know how to get the right cust file and preload file?
Any help is appreciated...
Thanks
your device has loaded a different operating system
i dont know my old cust number please help i just know PCT-L29
Hi,
I have p30 lite, Mar-lx1m(c185e2r2) with wrong operating system, please assist

Categories

Resources