yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] alray:
So you have followed all instructions at htcdev.com?:

Get your token:

fastboot oem get_identifier_token

Submit your token to htcdev

received an Unlock_code.bin file in your em-ail

Flash the unlock code using:

fastboot flash unlocktocken Unlock_code.bin

Select "yes" at the bootloader unlock screen using volume up/down and power

and the bootloader is still locked?

Try to reflash the stock firmware for your version and try the unlock process again.

You can extract the firmware.zip from this ota update file: https://www.androidfilehost.com/?fid=23329332407568203

To flash the firmware:

fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader

Then try the unlock again:

fastboot flash unlocktoken Unlock_code.bin
[One (M7) Q&A, Help & Troubleshooting] DeeZZ_NuuZZ:
Can you Screenshot the process on PC when you use the commands in cmd to flash the unlock token? Because if you flash the unlock token it should give you a screen where you have to choose yes for unlocking...also in the bootloader, is something different written on top? Like tempered or something with security or so? Sometimes photos and Screenshots can help much further :)

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
Thank you for your answer,

for now i cant provide screenshots, i will try it later.

But i can assure you;

- i get the question on the phone like "do you really want to unlock the bootloader?"

- i select yes

- it takes some moments and restarts into bootloop (home screen is visible with a black background, the bar on top and a jellybean icon, clock and battery status in it // i cant interact with anything, no touch support, no buttons working)

- after shutting it down i press power + volume down and get into the bootloader

- there is only "locked" written on top
[One (M7) Q&A, Help & Troubleshooting] alray:
When entering "fastboot flash unlocktoken Unlock_code.bin", the phone does 2 things:

1: It boot the stock recovery to wipe the /data partition for security reasons (so someone can't access your data simply by unlocking your bootloader)

2: Some data is changed on the PG1FS partition to tells the bootloader that the phone is unlocked.

In some situations, the bootloader can not be unlocked because someone re-locked it with a custom recovery instead of the stock recovery (required at step 1) or simply because the stock recovery is corrupted. Flashing the firmware (this include the stock recovery) should solve this problem, you did it and nothing changed.

It might also be a bad emmc chip (memory chip). If the phone is unable to write on the memory chip, it can't change the data in the PG1FS partition to "unlock" the bootloader. So the phone will simply reboot to a still locked bootloader. The output of "fastboot oem dmesg" and "fastboot oem last_dmesg" might tell us if its the case.

You might want to consider flashing a full RUU to eleminate any software/firmware issue. If after flashing a RUU you can't unlock the bootloader and/or the phone is still bootlooping, its likely to be an hardware problem, maybe the one I have explained above...
[One (M7) Q&A, Help & Troubleshooting] alray:
[MENTION=6931289]Dafuqhappned[/MENTION] and what about "fastboot oem last_dmesg" ?
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
... (bootloader) [8] check_ramlog_region: Backup last hboot ramlog.

OKAY

Can you say something about this?
[One (M7) Q&A, Help & Troubleshooting] alray:
Well this should be the last line of maybe a hundred of lines... :confused:

Maybe its time to try the ruu and see if your phone is not completely dead.

You can try the 4.19.401.9 ruu but you'll first need to update the firmware to be able to flash it.

fastboot oem rebootRUU

fastboot flash zip 4.19.401.9.zip

fastboot flash zip 4.19.401.9.zip

fastboot reboot-bootloader

then flash the 4.19.401.9 ruu.exe (run the exe file with your phone in bootloader mode).

https://www.androidfilehost.com/?fid=23991606952612442

http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
[One (M7) Q&A, Help & Troubleshooting] alray:
Everything is normal. The green bar won't go to 100% so you can see the "OKAY" message to be sure everything flashed successfully before rebooting the phone using "fastboot reboot-bootloader". You can disregard the few

(bootloader) verified fail

(bootloader) ..... Bypassed

its normal when flashing the sbl

So its safe to "fastboot reboot-bootloader" now.

Before flashing the ruu.exe, please post an updated "fastboot getvar all" so we can see if everything looks normal
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 4A.23.3263.28

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.19.401.9

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: FA389W914018

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__102

(bootloader) battery-status: good

(bootloader) battery-voltage: 4299mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dab9d12

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

Looking good?
[One (M7) Q&A, Help & Troubleshooting] alray:
Yes, go ahead with the ruu.exe. Flashing the ruu should take maybe 10 mins. If everything works fine, the phone should reboot to the OS. First boot can take longer than usual after flashing a ruu, so be patient if it hangs at the white HTC splash screen. (shouldn't take longer than 10-15 min). Then you can try to unlock the bootloader again, would recommend to submit your token to htcdev.com again to get a fresh Unlock_code.bin, just in case.
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
Just to be sure, should i flash in bootloader or fastboot mode?
[One (M7) Q&A, Help & Troubleshooting] alray:
boot the phone in bootloader mode and make sure you see the red "fastboot usb" caption then launch the ruu.exe
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
It worked! Thank you so far, but after booting it up it says "Process com.htc.dialer isn't responding" and shows a white background with a green htc logo (bootscreen).

Edit: At least i can interact with it now, i see a lockscreen, i can reboot, shutdown and so on.
[One (M7) Q&A, Help & Troubleshooting] alray:
Can you unlock the bootloader now?
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
If i try to unlock it now, it says:

sending 'unlocktocken' (0 KB)... OKAY

writing 'unlocktocken'... (bootloader) signature checking...

FAILsignature verify fail

FAILED (remote: signature verify fail)

Execution time is 156(ms)

What happned?
[One (M7) Q&A, Help & Troubleshooting] alray:
Can you post a screenshot of your command window + a screenshot of your working folder (where you have fastboot, adb and your Unlock_code.bin)
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
Heres the Screenshot.
[One (M7) Q&A, Help & Troubleshooting] alray:
Its a typo, its my fault, you copy/pasted my command from post #4. Sorry.

"fastboot flash unlocktocken Unlock_code.bin

its

"fastboot flash unlocktoken Unlock_code.bin"
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
Alright it worked, i pressed yes and it rebooted.

From the not visible homescreen (htc logo on white background), i pressed the power button, selected restart and went into the bootloader.

It still says "locked"
[One (M7) Q&A, Help & Troubleshooting] alray:
:( Looks like there is really something wrong with the hardware, that would also confirm the htc.dialer error when booting in the OS. IRC, this dialer error othen happen when the modem chip is fried. :eek:

The ruu should have fixed any issue caused by software or firmware... so it smost likely hardware related..

---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------

is "fastboot oem last_dmesg" still showing only 1 line?
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
Is there no way, to make it somehow usable? I mean i can the the lockscreen perfectly, the bar on top and so on.
[One (M7) Q&A, Help & Troubleshooting] alray:
Are you able to drop down the top bar to access the settings menu? If yes go to settings --> about --> phone info and look for the IMEI number. Don't tell me the number, just want to know if there is an emei number there or if its "unknown"
[One (M7) Q&A, Help & Troubleshooting] Dafuqhappned:
I cant pull it down, but i get an imei with getvar all.
[One (M7) Q&A, Help & Troubleshooting] alray:
Sometime you can have the imei from the getvar but from the OS it will shows "unknown" confirming a problem with the radio. Except reflashing the RUU there is not much you can try with a locked bootloader... I don't think its recoverable unfortunately. :(
[AT&T LG G3] umiteks:
After I choose Touch Firmware Update in Hidden Menu, touch is not responding :(

I was using Lollipop

-Factory resetted

-Flashed 4.4.2

But nothing has changed...

I tried my device with another screen & it works.

I tried another device with my screen: doens't work:

When I connect with OTG it say:

Touch Firmware Version: -1

Any idea :crying:
[8125, K-JAM, P4300, MDA Vario General] artisticcheese:
I never used bluetooth GPS device so what I found so far with IOgear GPS receiver is strange.

Whenever I switch on my Wizard and GPS device within a range, I'm prompted to establish pair with it (even though I already done it before), then I have to manually setup outgoing COM port in Bluetooth manager and only after that mapping software can see GPS device.

I have to do each time I switch off and on GPS bluetooth receiver, is it expected or something is broken with my Wizard OS or GPS receiver?

I use WM6.
[Elephone P8000] neonero:
Hi all,

My Elephone P8000 is always in roaming mode on both sim slots.

The phone is suposed to be unlocked and free network.

I use 2 sim card (free and virgin mobile), on the top bar i hace 4GR and 4GR. In order to have 4G network i have to allow the roamming in network menu.

Thanks for your help,
[Android Head-Units] Georgetech:
Hi, fellows

I have tried to root my head unit using: KingRoot, TowelRoot, Root Master etc and every single one failed. It is something that I am doing wrong? or it is not possible.

Please help!:confused:
[Android Head-Units] nleitao:
Aparently, not possible...
[Android Head-Units] mike.s:
What is a "Pumpkin Android rckPX2 4.4.4?" Searching for rckPX2 on the Pumpkin website turns up nothing.
[Android Head-Units] Georgetech:
My unit is this one on their website LM-C0676-US-A General:eek:S: Android 4.4 Kit KatCPU: Rockchip PX2 Cortex A9 Dual Core 1.4GHzRAM: DDR3 1GBNand Memory: 8GBAudio output: 4*45W maxScreen Resolution: 800*480 Cold Boot time: about 25-30s - See more at: http://www.autopumpkin.com/car-dvd-...-control-for-toyota.html#sthash.FlVuWSf2.dpuf
[Android Head-Units] Georgetech:
Mike the Rockchip 3066 and the Rockchip PX3 seems to be the same processor just that the 3066 is used only in consumer products and the PX2 is used for consumer products and industrial applications.

I did post the link to both processors PDF to see if somebody can compare them and determine if I can use the Malaysk room with my unit.

Thanks for your help!
[Android Head-Units] Georgetech:
Sorry is PX2 not PX3.
[Android Head-Units] mike.s:
The first 2 characters of Pumpkin model numbers indicate the OEM. I don't know who "LM" is, but it's not one of the known manufacturers of HuiFei type units. So, Malaysk's firmware is very unlikely to work.
[Android Head-Units] Georgetech:
Mike I was told by Pumpkin that my unit is made by Senzchen Winmark Electronics Ltd in China. I went to their website and they sell my unit under a different part number DQ6514
[Android Head-Units] nleitao:
Do you know were I can find more info about that? I'm really with itches to flash Malaysk's firmware in my AL-C0241 or AL-5701 (they are the same unit) and I really would love to have the original firmware to put back if something goes wrong...
[Android Head-Units] Georgetech:
Unfortunately I have not being able to find a workaround solution yet. I want to flash Malaysk rom like you but I do not want to brick the unit so I keep looking and asking for help. I have read and being told the following:

a) You need to be rooted to be able to backup your original rom.

b) You cannot go back to 4.2 either.

So the only solution is to find someone that can look in my case to both processors the rk3066 and rkpx2 and respond yes they are the same go ahead and do it.
[Android Head-Units] nleitao:
How I understand you! But in my case I have the same CPU and display :D
[Android Head-Units] Georgetech:
I just checked your unit in Pumpkin website and it has the rk3188 processor. Malaysk rom is for the rk3188 and 3066. If the only requirement to flash this rom is just about the processor then you should be fine but I do not know this, maybe somebody else in this forum could help with answers.
[Android Head-Units] nleitao:
I believe it's not the only but it's the most important. Come on guys, enlight the nooblets here!!! :angel:
[Android Head-Units] mike.s:
Malaysk's firmware is meant for HuiFei type units. It is not known to work with others, even if they happen to use the same processor.

For instance, the Winlink/Ownice units (they have their own thread) will not work with Malaysk's firmware, even though some use the RK3188 and have the same resolution as some HuiFei type units.
[Android Head-Units] nleitao:
thanks for your input Mike! this is the input that was missing.

that means I MUST put my fingers on my original firmware before try a rooted image.

Thanks again

Nuno
[Android Head-Units] Georgetech:
Thanks Mike!

That closes this chapter. Next option is to learn how to code.

Thanks

Georgetech
[Android Head-Units] MikeChannon:
Some posts moved to new thread:

http://xdaforums.com/android-auto/android-head-units/al-c0241-al-5701-t3229364
[Android Head-Units] Jettaboi2k:
My 2 cents

I would just try to install the rk3066 version of the ROM and see if it works. I don't think you will have a problem, it should work.

I accidentally was trying to install the wrong one on my radio and it just didn't install didn't mess anything up.

Unzip the Rom and put it on a SD card with nothing else on it.

Put the SD card into the GPS sd card slot while the headunit is on and it will pop up a box saying it found a update or something and

just reboot the until and it should start installing it.

Well at least this worked on mine. Just do it you don't need the old ROM. Hope this helps
[Android Head-Units] ervius:
Hi all, I've a similiar car unit, same CPU, same screen resolution, I've found a link to sownload an original rom:

http://www.autopumpkin.com/pumpkin-...i-odb2-steering-wheel-control-for-toyota.html

and here direct link:

https://mega.nz/#F!UE9ElapD!A-uTerI11qQ86r2ModVnyg

inside there are both firmware and mcu, but I didn't find something to dump it to explore system files, from images seem to be better than MCU I have mounted on mine (specific Fiat Punto Evo car unit), I cannot Root it, cannot install CWM (bad update.zip message!), please, there is someone that can suggest me with (if there are) utility to use to dump it? it will be interesting also to investigate about it, to try to find some easy ways to root kk 4.4.4 rockchip px2 devices.

Thanks in advances.

here some sources: (JB)

http://www.marsboard.com/marsboard_rk3066_download.html
[Android Head-Units] Airrage:
I rooted mine very easy with couple key presses. There is a youtube video of it, takes 30 seconds
[Android Head-Units] ervius:
post the youtube link...
[Android Head-Units] Airrage:
it wont let me post a link cuz I don't have 10 posts yet.

Try putting this after youtube, watch?v=wkfs856DQyg
[Android Head-Units] spyderr:
I can confirm that the latest version of Kingroot works on RKPX2 unit, it takes a good few minutes for Kingroot to do its thing but it does work. There is also a pop up halfway through the process warning you that a program is trying to access the system, if you select more information from the pop up you can then select to let the application to proceed.

If anyone wants to access the Factory setting the password for my unit was "3368", I have also completed a Rom dump I can share if anyone is interested.

---------- Post added at 12:10 PM ---------- Previous post was at 11:49 AM ----------

Some info from the build.prop

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=KTU84Q

ro.build.display.id=PX2_LEIMA_DAZHONG-V1.00.0043.00.00-2015-07-30

ro.build.version.incremental=2015-07-09

ro.build.version.sdk=19

ro.build.version.codename=REL

ro.build.version.release=4.4.4

ro.build.date=2015年 07月 10日 星期五 00:33:36 CST

ro.build.date.utc=1436459616

ro.build.type=eng

ro.build.user=leima_bmw

ro.build.host=and215-empty

ro.build.tags=test-keys

ro.product.model=rkpx2

ro.product.brand=rockchip

ro.product.name=rkpx2

ro.product.device=rkpx2

ro.product.board=rk30sdk

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=rockchip

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=rkpx2

# ro.build.product is obsolete; use ro.product.device

ro.build.product=rkpx2

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=rkpx2-eng 4.4.4 KTU84Q 2015-07-09 test-keys

ro.build.fingerprint=rockchip/rkpx2/rkpx2:4.4.4/KTU84Q/2015-07-09:eng/test-keys

ro.build.characteristics=tablet

# end build properties
[Android Head-Units] ervius:
Post your dump, also if my device is different, could help, my factory reset password is 8888.

For airrage, We cannot use reset password to root the device, becouse only numbers are present in keypad, so only password numbers we can compose.
[Android Head-Units] spyderr:
System Dump

Here is the link for the system dump, I cant post links as I have less than 10 posts but if you insert "drive google com" it might work"

h***s//**************/folder/d/0B6-b9HATa9gebDlNZmpEQ3ptV2s/edit
[Android Head-Units] ervius:
well, some news:

can confirm that last version of kingroot is able to root px2 with kk 4.4.4, Done it!, now, new question: I'm not able to connect the pc to the car unit, only one usb port on it and only to connect usb-keys, my question is: there is a method to dump/backup my original firmware without PC, directly from car unit?, and also, for CWM, is usuable the rk3066 one, or there is something specific, and how to flash ? (maybe from the original recovery?) thanks a lot, and thanks to the kingroot's author!

Spyderr, thanks , I got it, but I'd like to have my original rom so, if I try something else and is not 100% compatible, I can reflash mine.

See you.
[Android Head-Units] ervius:
ok, we need above of all a custom recovery for our PX2 CPU, we can obtain it with xda tools, but I need the original recovery.img for PX2, and I cannot extract it, me no, but you... if you dumped system, you can extract also recovery.img, so, extract it and then send to me, I'll try to convert into CWM, and then, converted, finally I can do everything on my car unit, can you make it for me?

thanks in advances.
[Android Head-Units] spyderr:
Extract recovery.img

Yeh I can give it a go no problems, I will try to do it tomorrow and post the link.
[Android Head-Units] ervius:
Ok, well, today, I'll try too, with ROM dumper 0.82 beta, so, I'll have also my system.tar and, hope, also the recovery image, I've seen your system, and into hardware there is a new library, that not found into rk3066 dumped (/lib/hw/power.rkpx2.so instead of /lib/hw/power.rk3066.so), so, I think upping one of them in our car unit, the result will be half usuable, or less..... We need to work on our specific ROM. For recovery, I'll try to dump one of RK 3066 and copy all modified files in our recovery.IMG (If I'll be able to extract them, as I know, the recovery image can be extracted as a normal boot.IMG into the kitchen), we'll see.....
[Android Head-Units] spyderr:
I have uploaded a copy of my recovery into my g drive folder that i posted previously. I will have try and start on a custom recovery tomorrow night.thanks for your help ervius.
[Android Head-Units] ervius:
ok, some notices:

I've dumped cwm and twrp for RK3066, and obviously your recovery with this tool: "RK3xxx_firmware_tools_5.23.18", and no error dumping all of them, now, my problem is: I don't have an original recovery to compare with one of the modded (CWM or TWRP), so, I can see some differences in scripts and in binary files, but I cannot recognize witch of them must be replaced or not.... this is a problem... someone that knows better than me how to proceed to transform the Rockchip PX2 original recovery to CMW or TWRP?, also only with a guide...

Thanks.
[Android Head-Units] ervius:
No news, bad news... I'll try to search an original recovery for 3066 chip and compare with modofied ones, hopeing to find something usefull to modify the px2 downloaded here...
[Android Head-Units] zzEvilGeniuszz:
I just got my unit and I realized that I do not have developer options. Even in the ABOUT, clicking the build number 7 times does not make it appear.

This is very odd.

Plus, I cannot seem to root the device after numerous attempts and numerous methods and apps.
[Android Head-Units] ervius:
ok, no custom recovery for now, no have idea how to upload, how to buils, but inside system/app there is an apk (converted to jar), with some interesting funcions, for example night_brightness, or the capabiluty to turn off screen canbus commands.....

you can check and see here:

http://www119.zippyshare.com/v/P9a9gmsa/file.html

seems that this car unit is different from other ones, there is a service mcuservice that works to comunicate with unit reading and writing on a serial port.

I have made a little apk to turn off automatically the screen after some seconds, so in the night no problem to drive, while listen music, with screen off is better for me, but this is only the beginning...
[Android Head-Units] ervius:
ok, little apk, here:

hxxp://www52.zippyshare.com/v/YebcO9IX/file.html

you must:

1) have rooted your device;

2) Put apk into /system/app folder (and then restart yur car unit to start it.)

what:

the apk launches a service that:

set screen brightness according whit sunset/sunrise (by latitude/longitude);

(from 1/2 hour before sunset, increase the light, until 2 hours after sunset)

(from 1/2 hour before sunrise, it decrease the light until 2 hours after sunrise)

so in the day, max brightness, while during night, the value is 1, and no problem for your eyes, while drive.

increase (or decrease) volume by 1 step, if tou are over 70/90/110/130 kmh;

if you press "mute" key, no mute, but screen-off.

all configurable in main app window.

see U.
[Android Head-Units] dave5777:
I'm in the same boat, I have a RK3188 that I flashed the wrong TWRP on its a 800x480 Quadcore Pumpkin. I can find versions of TWRP that will boot but none will mount the partitions, if anyone has a stock recovery I'd appreciate it.
[Android Head-Units] dave5777:
I was finally able to extract the stock recovery from the Update.img https://www.dropbox.com/s/9b3azwgmqmz87u6/recovery.img?dl=0

This is from RK3188 800x480 KitKat 4.4.2 KLD6 2.81

Thanks to [MENTION=4582467]RedScorpioXDA[/MENTION] for his Rockchip Unpacker Tool http://xdaforums.com/showthread.php?t=2257331
[G3 General] Aevum:
The people on HTC Mania forum are reporting a new 20S Firmware being pushed as a OTA on Vodafone Spain´s network

Since the link posted there is Adfly i cant copy it directly, im currently downloading to repost it to another host.

Dont know if its 5.0 or 5.1 (probobly still 5.0) and dont know what changes have been done.

EDIT : By mistake i typed 355 instead of 855, this is for the D855.