yashsingh1/xdaforums huggingface dataset:
[Android General] :
Well... I finally did it and succeeded in installing the android 5.1.1 beta (D6000_COMMON_V1.0).

Figured I'll post how I fixed it, for it might help others too.

I'll recap where I got stuck all the time.

In QFIL, my device could be found in a port through the driver Qualcomm HS-USB Diagnostics 9091. Then, when starting the procedure when pressing 'download', my device would go into fastboot mode just fine. When switching to fastboot mode, the device's state changes and becomes visible in a different port. To be recognised by the PC, a different driver (called Qualcomm HS-USB Diagnostics 9008) is needed to continue the process. For most users, this driver gets installed automatically and you can continue the wirebrush/firehose process in QFIL.

However, my computer kept installing a different driver called Forge HS-USB QDLoader 9008. Result: the procedure ends in 'Download Fail: Fail to Switch to Emergency Download mode / Download Fail: Switch To EDL FailFireHose Fail'. Of course, in the PC's device manager I tried to update said driver to the Qualcomm version. However, the installer will tell you that's not possible.

So here is the fix.

In Windows device manager, delete the Forge HS-USB QDLoader 9008. After this, let device manager search for altered/changed devices. This will cause windows to attempt to reinstall the Forge HS-USB QDLoader 9008 driver. This time, it will partially fail, and the new Forge driver will be accompanied by a yellow exclamation mark. Now is the time to disconnect your phone from the computer. Next, in windows device manager you must show the hidden devices. Find the Forge driver again and now update the driver with the Qualcomm one. If you try to do this with your device still connected, the installer will tell you that the driver is not suitable for the device (I couldn't for the life of me figure out how to get past this). With your phone unplugged, however, you can upgrade the Forge driver to the Qualcomm driver just fine!

In the meantime, on your phone, press the power button until it restarts. When it is rebooted, plug it in the the PC again. Now it is time to revisit QFIL and restart the 'download' process. This time, it will work perfectly fine.

Remember the installation instructions?

This QDloader error will not even take place this time and the installation process will smooth you through the port change automatically. Voila!

Also, I'd like to point out some observations on the beta.

It supports a ton of system languages that you won't find on the stock 5.0 rom (such as Dutch, which is the reason that I wanted to install the beta anyway).

Very stock experience.

In fact, it looks like they actually built this on top of CM sources as I can see a CM icon for the System profiles settings.

The soft keys are arranged in the way they are supposed to be! (back, home, recents)

Anyway, sorry for the long post, but it felt like a breakthrough! :victory:
[Android General] dragonuk.test:
Finally received the innos d6000 after 7 days. Quality is great but external battery is draining quite fast 70mins of web browsing and setting configurations have drained 9% battery. Is this normal? Also some apps won't work due to detected rooted device. Unsure how to get around this without root. Anyone know? The rom version is v1.1
[Android General] OC-Freak:
Good thing you figured it out. Guess I never had any problems (except it only being detected on my usb 2.0 ports) because I installed the drivers before connecting the phone.
[Android General] Chinaphonearena:
We got 13 hours 45 min. 140 lux (50% brightness on 5.0 1.1), WiFi, YouTube, 720p

www.chinaphonearena.com/forum/Threa...ttery-performance-charging-and-screen-on-time
[Android General] Chinaphonearena:
70 min is far too short. What are you doing during that time? Try discharging and charging a few times to see if it improves.
[Android General] mtkc:
The service providers in my country are going to shut down the 2G network at the end of next year. :(

Hence, I would like to know if this phone supports concurrent 3G standby? Meaning, even without a 2G network, will dual standby still be functional on both sims? Or does setting one sim to 4G/3G force the other sim to be 2G-only?
[Android General] dragonuk.test:
Web browsing on chrome and changing configurations settings on phone. The battery is also discharging external only. Not seen the internal loose any power yet.

In 4hours when phone is not used the external battery have loss 4%. I have 4 gmail account sync.
[Android General] Chinaphonearena:
Yes, that's the way it should be. You want it discharging external before internal.
[Android General] dragonuk.test:
Have experienced the chrome browser going black. Also tethering does not work. I get the connection with phone but there is no internet. There is nothing wrong with my sim or network provider as tethering work fine with my LG. Anyone with 1.1 rom manage to get tethering working?
[Android General] :
Unfortunately, all the documentation that comes with the phone explains that only sim1 can be active on 2g/3g/4g and sim2 only on 2g or vice versa. So no dual 3g or dual 4g connectivity simultaneously.

---------- Post added at 11:34 AM ---------- Previous post was at 11:28 AM ----------

Saw your post and now trying wifi tethering and it is working perfectly fine. I'm on the 5.1.1 beta rom (COMMON_V1.0). Did not try it on the stock rom though.

Also, there have been multiple reports on chrome going black. I have not experienced this – I'm not using chrome. Others browsers seem to be unaffected.
[Android General] dragonuk.test:
Not too worried about Chrome issue, I read that USB tethering may work but not tried. However the battery is more an issue, at one stage I thought it may be faulty external but then took it out and the internal one also dropped 1% within 5 mins. I am unsure whether it is the 4G (LTE) or some app that is causing issues. Have removed all the widgets from screen. I am using Nova Launcher and not the default (folders in default are limited). In the last 1 hr 52 mins the phone external have dropped from 81% to 55%, internal 1%. Can someone tell me what their % drop per hour is during a constant use session where the screen is on and interaction with the touch screen.

If the beta rom is 5.1.1 why does it show as V1.1 in COMMON? What is the 2.1 ROM, is that COMMON V2.1 running 5.1.1?

Android Version 5.0.2

Build number: D6000_ROM_COMMON_V1.1
[Android General] :
The naming of the roms is somewhat confusing yes.

Stock international rom is COMMON_V1.1. There is no other update in the international stable channel (yet).

All the V2.0/2.1 roms are Chinese/English only without gapps and these too have a beta channel as well without any apparent name difference.

Confusingly, the international beta channel did not receive a different name either and is also called COMMON_Vx.x. The android 5.1.1 beta is COMMON_V1.0.

So for the global roms we get:

Android 5.0.2 - D6000_ROM_COMMON_V1.1

Android 5.1.1 beta - D6000_COMMON_V1.0

As for the battery, I'm not sure. It is now 18 hours since I unplugged my phone at 100%. I have 7h of SOT now and the battery stands at 12% as I've been heavily using to get everything set up since I flashed the beta yesterday. Mind you, this is just the external battery. My internal battery is still at 100%. Haven't been through a full cycle yet. All things considered, I'm quite pleased with that so far.
[Android General] Chinaphonearena:
5.0 Common v1.1

WiFi hotspot 3G tethering working for me.
[Android General] OC-Freak:
I got around 7-8 hrs SOT with streaming youtube before the external battery was empty. With constant screen on that works out to be around 13% battery drain per hour, seems about identical to your running times with screen on.
[Android General] OC-Freak:
[IMG="SOT"]https://lh4.googleusercontent.com/-is53QeLnEtc/Vf7t9c8jhVI/AAAAAAAAAW0/GiGa5FGX05I/w540-h960-no/Screenshot_2015-09-20-19-30-20.png[/IMG]

[IMG="youtube"]https://lh4.googleusercontent.com/-3lHNDzSTUqU/Vf7t79gDCeI/AAAAAAAAAWs/CmmaxNW64ks/w540-h960-no/Screenshot_2015-09-20-19-29-43.png[/IMG]

Streaming youtube. Stopped streaming during the night - continued today.
[Android General] sonhy:
Has anyone tried to stick a wireless charging receiver pad inside their d6000 yet?

there are so many pin options, im sure one will fit the d6000... hoping the plastic lid is thin enough.

www.ebay.com/sch/i.html?_from=R40&_sacat=0&_nkw=wireless+charging+receiver&_sop=15
[Android General] dragonuk.test:
After 24 hours the D6000 finally ran out of juice with constant SOT. I charged up yesterday to 100%, but I think the reading for external battery is not right, it read 100% but when I took out and put back in it read 98%.

Have now tested the tethering with USB, Bluetooth and Wifi, can create connection but no internet access. Have tried with two sims cards and same issue. Tethering is not working with 5.0.2 (Common V1.1).

I would like to use the beta roms but unsure what is really required. Do we need additional cables or will the out of box be sufficient? Can we not put the beta rom onto the SD card and use the system upgrade (from SD card)? Can someone explain the brush wire / brush tool, is this a special term as not seen it when l roms to more known phones / smart watches. Also in the INNOS forum even if you mange to upgrade to a new rom they say you have to brush wire it and then perform factory reset.
[Android General] Chinaphonearena:
Procedure for wire brush (PC flash) is in the first post of this thread.

WiFi access point of 3g working for us no problem on 5.0 Common v1.1.
[Android General] dragonuk.test:
Finally solved tethering issue, the D6000 DHCP provided a local IP for DNS, I had to update the DNS on the laptop / tablet to use the network provider DNS servers IP. Everything else can stay the same, just the DNS needed changing.
[Android General] forserg:
nvrmd
[Android General] vladakster:
Lots of commercials on this site, I bet they have root for every single imaginable device :).

Unfortunately for you, it would be too easy.
[Android General] dragonuk.test:
Here is a workaround to the Chrome black screen.

Go to chrome:// flags and scroll to Delegated Renderer (AKA bercompositor) then switch it from default to enabled.
[Android General] forserg:
Agree:D
[Android General] dragonuk.test:
Due to the absence of NFC. No Android Pay, Samsung Pay ... It is still possible to make contactless payment via Vodafone Smartpass. You will need a contactless vodafone SIM card. You need to register a new account with Vodafone Wallet (the software will detect root). Workaround without a rooted device is to use another hand set to register the new account. Once all created you not need this app anymore as all account management can be done online. To use contactless you will use the Vodafone Smartpass app together with a NFC tag sticker (put on cover). This Vodafone app will let you use with no issue. Smartpass is supported already in many places with visa contactless. Reason why I mentioned Vodafone is that you can use the service with pay as you go SIM. No need to be montly like EE. Free service.
[Android General] decayed.cell:
He's got 5 positive feedback now maybe he's on to something
[Android General] Chinaphonearena:
Exactly. This is a scam post.

Thank you. Will add to OP.

This will not work. I recommend removing the link so people don't waste their time.
[Android General] forserg:
Good idea
[Android General] kuzimoto:
I have a feeling that it does, but can anyone confirm if it supports the Camera2 API?
[Android General] Chinaphonearena:
According to this app:

https://play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en

Innos D6000 Android 5.0 Common v1.1 does not support camera2 API. X's across the board (according to the app, the build does not support any of the Camera2 API features).
[Android General] kuzimoto:
Aww, that stinks :/ thanks for taking a look though. I wonder if it's at all possible for it to support it in the future.
[Android General] OC-Freak:
Same with 5.1.1 beta ROM.
[Android General] spendrup:
Apart from the missing Google Apps: Would those who have installed the 5.1.1 beta recommend it over the 1.1 stock version?

How are the overall performance and battery life/reception/heat in comparison? Was it worth all the wire brush and driver Odyssey?

I am quite satisfied with the 1.1, but wifi signal is pretty weak and it does not feel too snappy
[Android General] kinggherkin:
Yeah I wish to know the same, the wifi signal is too weak for me and is really annoying me and id love for this to fix it.
[Android General] OC-Freak:
I use the 5.1.1 beta with google apps.

*Wifi signal is weaker than on my other android phones - my guess this is hardware/antenna related.

*It feels snappy, more snappy than moto X play which has same SD615 CPU.

*Battery time seems to be about the same as the original 5.0 install, compared to my moto x play the standby battery time could be improved, innos d6000 drains more battery when just being in my pocket than moto x play.

*SMS bug: Some messages comes up as empty - and checked with senders - they are not empty.

*My phone has no heat issues, during gaming it slightly heats up, but that is hardly noticeable.
[Android General] spendrup:
So you would highly recommend the update?
[Android General] OC-Freak:
The difference is not huge really. I'd wait to see if a newer 5.1.1 build will be released with G-apps.

The SMS bug can be annoying.

---------- Post added at 07:25 PM ---------- Previous post was at 07:21 PM ----------

As for battery time, this is a rough estimate comparison with phone 90% in standby (not being used, but connected to 3g/4g and wifi).

Motorola moto X play - 3650mAh battery - about 8 days.

Innos D6000 - 6000mAh battery - about 6 days.

This is where it could use some improvements.
[Android General] Chinaphonearena:
Sure, but Innos needs to implement it in the ROM.
[Android General] :
For me, the most compelling reason to install the 5.1.1 beta rom (with gapps!) was that it supports basically all the aosp languages rather than only the very limited system languages that come with the 5.0 stock rom.

The second biggest reason to upgrade is that the beta actually has the proper onscreen navigation button layout (back, home, recents). The layout on the stock rom (menu, home, back) annoyed me greatly.

Apart from that, I have not experienced a single instability compared to the stock rom. Standy battery drain could indeed be better, but imo this is also wanting on the stock rom. Performance is better, although this is a subjective assessment.
[Android General] mustafa000xxx:
Omg 6k battery
[Android General] VladimiroCampus:
Tethering issue

Excuse me, but when wifi hotpot is active, pc or tablets use the default gateway and dns servers given by Innos Hotspot. In this way pc cant surf thw web at all. I use ip address managed by a dhcp. If y use router web is avaiable... Please can u explain where did u change dns when u connect pc or tablets to Innos wifi hotspot?? Maybe are u using static ip?
[Android General] avello2005:
OMG! Amazing specs.
[Android General] OC-Freak:
There is a new ROM version 2.3 out, but judging from file size (520.7Mb) it is an china version without google apps. international ROMs are usually around 700Mb or more.
[Android General] dragonuk.test:
IP / gateway is dhcp, but DNS you can change and give static. Just need to edit the connection when you have connected.

Chromebook - double click on the WiFi connection twice and you see option.

Ubuntu - once you are connected just click the edit connection from the network settings.

Windows - click the WiFi setting and right properties on the ssid name.

IPad or iPhone - you modify the connection and u see a tab for DNS

Android - select the WiFi and modify then go advanced

---------- Post added at 05:43 PM ---------- Previous post was at 05:35 PM ----------

Also to add please find the DNS your Android mobile is using.
[Android General] forserg:
Is anybody have problem to send MMS messages? I found out I can get them, but I cant send them., checked APN settings from my previous android, the same.
[Android General] dragonuk.test:
If changing DNS not work try this

Adb shell

Type "Settings put global tether_dun_required 0"
[Android General] vladakster:
No, you're not the only one :(. I can send Mms only when I'm connected to WiFi. Also, I can't receive Mms!

And some good news from Russia : http://4pda.ru/forum/lofiversion/index.php?t688153-80.html

Use Google translate if you don't speak Russian :)
[Android General] dragonuk.test:
Can someone tell me how to put the phone in download mode or get the boot up options?
[Android General] VladimiroCampus:
ADB Shell

sorry but i'm a dummy.

where can i set this option?

Is it a hidden option?
[Android General] forserg:
Saw it yesterday, waiting for it:o

---------- Post added at 02:57 PM ---------- Previous post was at 02:41 PM ----------

I can get MMS without Wi-fi, no problem. Is it strange? Hm I hope it is ROM related.
[Android General] dragonuk.test:
You need to download the ADB tool to your computer and connect your innos via USB.
[Android General] Zatchbellize:
Usually you can get into download mode by holding the home, volume down, and power button on many smart phone devices and then when the screen pops up about are you sure you want to go in download mode press the volume up button to accept. Let me know if this works for you?
[Android General] bzz11g:
ROOT & TWRP !!!!!

http://4pda.ru/forum/index.php?s=&showtopic=688153&view=findpost&p=43260958
[Android General] forserg:
Nice. I'm in.

---------- Post added at 09:50 PM ---------- Previous post was at 09:31 PM ----------

I couldn't dowlnload TWRP_2870_fastboot_Innos_D6000.zip though.
[Android General] dragonuk.test:
Del
[Android General] Evocatorum:
Del? you mean Delete?
[Android General] Chinaphonearena:
Excellent news. Means we can use Lollipop 5.1.1 stable v2.3 and flash gapps.

First version guide, easy DL links and tutorial. Pictures and revisions to come, but even beginners should be able to slog through this

http://www.chinaphonearena.com/forum/Thread-Innos-D6000-root-gapps-temporary-TWRP-custom-recovery
[Android General] OC-Freak:
Not working for me.

ADB driver package didn't install anything (0 files copied), so thought I probably had the drivers needed already.

When running run_test.bat it doesn't find my device.

My innos D6000 is connected in charging mode and "OEM unlocking: allow the bootloader to be unlocked" is enabled under developer options. Running latest 2.3 ROM.
[Android General] spendrup:
Is there a way to install drivers in Windows 7 64bit? I tried it for 1 hour with different sources, never getting rid of the 3 yellow triangles in the device manager...
[Android General] shisaya24:
I am also unable to get the drivers running in any way, tried different sources but when flashing with QFIL it alsways stops in the middle...
[Android General] vladakster:
Well, started this morning, and I'm already rooted!!!

There is mainly problem with right drivers, especially if you had previously installed similar drivers.

At the end, I have to instal fastboot minimal to run the command "fastboot oem unlock-go".

If you are lucky, maybe you will succeed in first try , but that wasn't my case :(
[Android General] FunnierThanVos:
I know we all compromise when we go to Chinese smart phones, but this is a bit out of hand for me. I think Xiaomi is working on Cyanogen-supported phones which are more appealing.
[Android General] Chinaphonearena:
Thanks for the report Vlad, I will add to the tutorial. You are on which version currently?
[Android General] vladakster:
I flashed 2.3 before rooting because I didn't have an option to unlock bootloader in developer menu. Whatsoever, it appeared that it wasn't necessary, because I had to unlock bootloader manually via ADB.

But, upon successful rooting party just started!

Seems I can't login to my Google account, phone and messaging app acts wiredly, and many other apps misbehave.

I did factory wipe prior to flashing V2.3 but it seems like I have to repeat it.

Maybe V1.1 wasn't so bad when I look back ;).
[Android General] adojames:
I can also confirm that when the phone reboots to the bootloader and it install TWRP, the reboot into recovery does fail and you have to use cmd prompt and fastboot oem unlock-go.

It also took several attempts. Had to reinstall V2.3 twice, then re-root. Also on gapps, I finally got the to install,ended up using a different gapps package in the end.

Ive also installed Xposed, and now have Amplify, Greenify and Kernel Adiutor all working :)

Also removed all the bloat! with root uninstaller.
[Android General] OC-Freak:
Same happened to me.

And I decided to flash it with QFIL again (factory reset didn't remove gapps/fix the problem), and that killed my phone. Flashing went fine, but now it is completely dead, and QFIL fails with Download fail: Failed to switch to emergency download mode, "Download fail: Switch to EDL FailFireHose Fail" message.

Guess that means R.I.P.
[Android General] :
Perhaps not.

At that point, QFIL tries to reboot your phone into fastboot mode and the driver that is used to connect to your phone changes in the process. Does your fastboot driver happen to be a Forge HS-USB QDLoader 9008 instead of a Qualcomm driver?
[Android General] OC-Freak:
Driver is Qualcomm HS-USB QDLoader 9008.

But maybe I have managed to fix it by using my laptop to flash with. But using my laptop was troublesome as well as I had to reboot and allow unsigned drivers to be installed (running win 8.1). My desktop still runs win 7 64bit.

Now it's alive and running 2.3 china ROM.
[Android General] OC-Freak:
Aaaaaand I'm back at same issue.

After installing Gapps ( mini package for ARM64 from http://opengapps.org/ ), the phone is slow and hot, battery draining like crazy and programs crashes (play fails to start, gmail exits after I type in my email and so on).

Looks like Gapps on 2.3 china ROM is not possible at the moment.

I'm flashing back to the international beta ROM for now.
[Android General] OC-Freak:
I did some further testing after resetting to 2.3 china ROM again by installing APK files. As soon as google play services is installed the phone heats up like crazy, becomes dirt slow and laggy and programs crashes.

I think I installed the correct APK file as well. So it seems the 2.3 ROM hates google play services like a plague.
[Android General] vladakster:
I managed to log in using old Titanium backup of accounts - simply restored the backup from my old phone, and after restart I was logged in.

Now I just have to find a way to read SMS and emails...
[Android General] Chinaphonearena:
Thanks for the report. Good to know you're at least unbricked.
[Android General] OC-Freak:
I flashed 2.3 again in qfil to reset phone since flashing gapps package ( from opengapps.org) cripples my phone. After that I installed google services APK from: http://www.apkmirror.com/apk/google-inc/google-play-services/

As you see there is A LOT of different versions based on device type and CPU/OS type, some are for android TV, some for phones, then there are for 64bit OS/CPU ad for x86 CPU and so on.

I did a mistake and downloaded the wrong version first, but that did not even install. After downloading the version for ARM64 it installed fine, but crippled the phone, just like when I installed gapps in TWRP.

So 2.3 ROM seems to hate google services, or maybe they hate each other ;)
[Android General] Chinaphonearena:
Just downloading and installing apk Google Services generally never works. Did you install the correct gapps package the first time on a clean install of 2.3?
[Android General] OC-Freak:
After installing Gapps ( mini package for ARM64 from http://opengapps.org/ ) it crashes. Should be correct, as it has 64bit OS. 32bit version refuses to install - since it has 64 bit OS, already tried that.
[Android General] adojames:
For V2.3 I recommend used the following gapps install from the "Dirty Unicorns" x64 gapps mini package. http://download.dirtyunicorns.com/files/gapps/arm64/du-gapps-arm64-signed.zip

At first boot, it does take a while to set up and yes the phone does get a tad hot, but it does settle down.

Also installed xposed 5.1.1 x64, and everything works fine.