Database Users

[ROM] OS_Acer_4.002.14.EMEA.GEN1_A22F_A

This is official ROM (bin) from acer. Is for Liquid E. For Liquid - visit modaco forum.
http://tranz.it/load.php?id=pywW4rpuHxQ1lsGx685901

Since yesterday also available on the acer site (support section)!

nietnicks said:
Since yesterday also available on the acer site (support section)!
Click to expand...
Click to collapse
Yep- it is from there, but only BIN file.

Hmmm seems that with the official acer update the upgraded S100 is going to be a problem.
I've got a message that the froyo update can only be done on liquid e devices because of the RAM space. s100 has 256Mb and the liquid e 512Mb. Because of that the official acer update tool stops.
Is this the reason the froyo alpha version i've installed now is a bit laggy???
[update] Gonna try the modaco version now! (4.002.14.EMEA.GEN1 bin for 256M)
hmmm, stopped at fastboot succesfull, now rebooting. and then it stopped. powerbutton does nothing, repluggung usb does nothing. Bricked?
Not bricked as it seemes. Used the following tips by malez and got out of the bricked mode (where it did nothing):
1. Pull battery in and usb cable to phone and pc
Press in order and without releasing
1. < (back button)
2. Camera
3. (power) not always necessary
Bootloader should appear. If that doesn't work unplug usb and unplugg battery and retry.
If this still does not work you can also try this
1. turn off your phone (and unplug usb if plugged)
2. press camera + volume up and then without releasing this two buttons hit power and the phone will vibrate two times. Release all buttons.
3. take the battery out and put it back (don't touch any button on the phone)
4. connect the usb to your computer and you will the acer logo and then bootloader will pop up.
Second list of tips got me up and running again with the new bin!

Is there any way to install this upgrade from SD card, I use Linux and therefor do not have windows.
Thanks.

nimnull said:
Is there any way to install this upgrade from SD card, I use Linux and therefor do not have windows.
Thanks.
Click to expand...
Click to collapse
Yes, you can... amm... somewhere in modaco i saw this kind of update... see there: http://android.modaco.com/category/418/acer-liquid-liquid-modaco-com/
I hope you find it!

nietnicks said:
[update] Gonna try the modaco version now! (4.002.14.EMEA.GEN1 bin for 256M)
hmmm, stopped at fastboot succesfull, now rebooting. and then it stopped.
Click to expand...
Click to collapse
Same here.
After "fastboot" successful it show a warning like "restoration is needed".
Taking the battery out (to turn off the phone) and putting it back and after turning on the phone worked for me

[How To] Update you QuadCore R16 Tonghai AllWinner TopWay Eincar from 4.4/5.1 to 6.0

Hi guys. as promised, i decided to make an how to, so you can update your headunits, commonly known as QuadCore R16, to android Marshmallow. First i wanna thank @dickjones for all is help in 4pda forum
Files Needed - Android 6.0 Image and software to update - https://yadi.sk/d/CEZ8Rwe_3KbMbj
Recovery in Case of first attempt Bootloop - https://yadi.sk/d/1krDlyPP3JXFaD
Final FW recomended with root included - https://yadi.sk/d/suOSRwtd3KSbw4
Apk to put the unit in flash state - http://www9.zippyshare.com/v/ujNIf42V/file.html
Hardware Needed - Male to Male USB. i made mine from two old usb cables. just cut them and join black with black, red with red, white with white and green with green. Isolate so they wont touch each other.
I advise to this with the unit next to the PC. For this, use a PC power suply, cut two yellows and join them with the red and the yellow from the Unit. Then cut two blacks from the PSU and join them with the black from the Unit. After this, find the green wire of the PSU, cut it and join it with another black from the PSU. this will make that when you turn on the PSU, it will start without an assist from a PC.
Last before you start, in the ANDROID 6 files you will download there is a video of the process, but you dont need to follow any step till step 10, due to the PCUpdate.apk, that allows you to put your unit in flash state withou the need of dismantling the unit.
1- Install Phoenix Suit. Also install the Google USB Driver provided with phoenixsuit installation. if it gives an error on the driver instalation, continue with the instalation and download the google driver usb from any site. Copy all the driver files and paste them in the AllWinnerTech Driver folder. Install Phoenix Suit again, and at the driver instalation you'll notice that there is no error anymore.
2-After instalaltion finished, open phoensuit, press the Ancor Icon, second from the left, then blue box and select the image provided with Android6.rar, named sun8iw5p1_android_d7_uart0
3-Now in your headunit install PCUpdate.apk and open it. Proceed with flashstate. Unit will turn dark. Its now in flashstate. Now connect your USB Male to Male from your PC to the usb from the unit. If you have two usb cables in the unit, if pc doesnt detect on the first one, change to second cable. Only one will work for flash purposes.
4-As soon as the pc detects the unit, if some driver begin to install, let it finish, and then, on the PhoenixSuit, press the GREEN BOX in the Ancor Menu. Unit will start to update. Let it finish.
5-Unit will reboot after finish
6-The first boot may take a few minutes. If it boots fine, Proceed to step
7-This part is for units that got in bootlop after phoenixsuit flashing. you will flash the recovery in case of bootloop provided above. USB PEN Fat32, put the file in the root of the usb. This part may differ from unit to unit. On the ones with hardware buttons, the force flash state is turning off the unit, insert usb with the recovery file, press home button and let it pressed, turn on the unit and as soon as it turns on, press once the reset button. let the home button pressed till flash screen appears. let it finish. Again, if it dosent detect the file, repeat the process but in the second usb cable from the unit.
8-after finish, unit will enter recovery. insert a usb keyboard in the unit to navigate recovery. factory reset and the wipe cache. when its done turn off the headunit and emove usb.
9-download the Final Firmware provided above and put it on the root of the formated fat32 usb.
10-insert the usb in usb cable from headunit, force flash the FW again like you did in step 7. Unit will flash the final firmware, takes about 2 minutes to boot.
VOILA, you are in 6.0
Im not responsable for broken devices. do this at you own risk.
This was tested in two units, one from eincar with fake 5.1 and in another with already two years bought in aliexpress. one said astar y3 cortex a7, other astar d3 cortex a9. both are working perfect with android 6.0

HI, thank you for the detailed process. May i ask for the reason behind flashing sun8iw5p1_android_d7_uart0 prior to the final firmeware

Thats because you need to use phoenixsuit to upgrade the unit first, and that file is the one phoenixsuit will accept. If you try to flash the final firmware first, the unit simply wont flash the fw

I have a problem, te app that put my android in flash state puts it with black screen and horizontal green lines, after that, my unit its connected and just after that the unit reboots and it says windows doesnt recognice it.
can anyone help me? Thank you!
It looks like that app doesnt put the radio in flash state

Thanks for the guide. Has this been tested with a unit that has been flashed with the re-partitioned 7.2GB internal memory from IQ Navi? Don't want to lose the space and revert back to the 1.5GB from before.

elrafita said:
I have a problem, te app that put my android in flash state puts it with black screen and horizontal green lines, after that, my unit its connected and just after that the unit reboots and it says windows doesnt recognice it.
can anyone help me? Thank you!
It looks like that app doesnt put the radio in flash state
Click to expand...
Click to collapse
sounds like you dont have google usb driver instaled properly. you have to download google usb driver manually, take all the files from the driver, copy them to the driver folder of phoenixsuit and reinstall the phoenixsuit

nosidefcp said:
sounds like you dont have google usb driver instaled properly. you have to download google usb driver manually, take all the files from the driver, copy them to the driver folder of phoenixsuit and reinstall the phoenixsuit
Click to expand...
Click to collapse
I have it installed, when rebots after begin the flash in dispositives i have this one with yellow triangle usb device vid_1f3a_pid_efe8,.
I couldnt find the drivers on the internet.
Thank you for your help!

This its how my screen looks after use the update apk
{
"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"
}
the radio still sound at this moment.

it will only update when you solve the issue of it showing yellow in the pc

nosidefcp said:
it will only update when you solve the issue of it showing yellow in the pc
Click to expand...
Click to collapse
Im using windows 10, which windows do you use? 64 bits?

Windows 64bits. Go here http://www.teamandroid.com/2017/05/24/download-google-usb-drivers
Method 1 manual download zip. Extract, copy all files except source.properties and paste them in
C:\Program Files (x86)\AllWinnertech\PhoenixSuit\Drivers\ADB_Driver
Install the phoenixsuit again and when prompted to install.google usb driver click yes. You wilk see that the driver has been correctly installed. Finish phoenixsuit instalation. After this the pc should detect fine the flash state of the headunit

Will this work on my unit?

Yes it will if you do it correctly

I format the comnputer, didi all the steps fine, but when te radio reboots after push the green button it said that didint recognice the usb(error 10 cant iniciate ), dont khow if its a issue with the flash state in my radio.
offtopic: I dont have rds text on the radio, its checked in extra options, do you know how fixit?
Thankyou

ive made a video of a 4.4 unit upgraded to 6.0

Hey! I was able to do it al the end, but after reebot (end of point 6) radio boots on normal mode, and im not able to update from the radio menu to put the last firmware, i will try to enter recovery mode to use it.
Do you know if i can use iqnavi with android 6.0?
Thanks a lot

what last firmware? the one ive put, 4 files, is the most updated one, already with root, etc. yoy have to put the 4 files in the root of a formated usb fat32 and force flash of the device. with the home button pressed, turn on unit, maintain home pressed, click reset one time, maintain home pressed, when flash screeen appears, release home button.

Thanks, i will try tomorrow!

Hey, can someone upload photos of the installation and android 6 on the head unit?
Does it support Android usb audio source?

I did it finaly! Thank you, ay the last i bought red mod soft for 6.0 the only thing i still want its the rds text
Thank you again

Lenovo Yoga 2 1050F Bricked

Hello,
A friend give to me his Yoga2 1050F Tab, because it's bricked...
"After a kind of upgrade he said"
So, here's the situation,
Tab is really bricked, stuck on Lenovo Android Screen.
I've tried to factory restore, no success.
I've searched all the web after factory image to flash, I've found 3 of them... But nothing works !!
The 1st one, the only we can still found here, is a factory image from 2015. And the result is, no more lenovo android screen, i'm stuck on a kind of Bios (?) And can't do anything more...
2nd one, (YT2-1050F_S100196_151123_ROW-fastboot), best result, back to an android boot, but stuck on recovery screen, without any possibility to boot...
3rd one (YT2-1050F_S0198_150422_ROW) impossible to flash, it's always failed at "flash easyimage.zip" step.
Other thing, I don't know what xml file I need to use (flash, flash-blankphone, flash-factory ... )
Here, i'm totally lost. Tab is stuck, And I've no idea what can I do next...
Maybe here anyone can help me ?
Many Many thanks !

Hello,
It seem's i got the same problem.
The tablet downloaded an upgrade by it's own.
The tablet rebooted alone and the try to apply the upgrade but never success.
Now i'm booting on a BIOS type screen.
"VALLEYVIEW C0 PLATFORM"
I can access to different options but the tablet is not reconized by my PC anymore.
I can flash anything on it.
If someone have a solution, it would be great !

Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts. Make sure the flash tool is running on your local drive (usually C).
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers

OMG ! OMG ! OMG !!!
Man, you're THE MAN !!!
I've followed all your explanations, and... IT WORKS !!!
Yes it was hard to find again the "restore-kitkat-bios-830-1050-v2" (China links to Russian Servers...) But I've finded it !
Many many MAAAAANYYYY Thanks my friend !!!
Thanks a lot !
And thanks a lot to All XDA DEV !

dallivadr said:
Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts.
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers
Click to expand...
Click to collapse
Cant find anywhere to download restore-kitkat-bios-830-1050-v2 file. Any chance you could pm a Google drive link?
Thanks

Sansiro2 said:
Cant find anywhere to download restore-kitkat-bios-830-1050-v2 file. Any chance you could pm a Google drive link?
Thanks
Click to expand...
Click to collapse
Managed to sort it out - many thanks for your guide. One thing to note is the Kitkit restore file needs to be in the root of the C drive and also the file for the flash in my case was the flash.xml file

Glad the post helped you guys out and that you were able to get back up and running. If the post was helpful, why not click the 'thank' button under my post

Hi Hi Hiiii
For those who need the famous "restore-kitkat-bios-830-1050-v2"
HERE'S THE LINK (Personal re-upload) : https://drive.google.com/file/d/13vV6fpNAbWWZUk9_fzmJpMAMax2tlyyB/view?usp=sharing
Be aware that you probably need to do this if your OTA updates Fails :
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update
(Original Post here : https://forum.xda-developers.com/showpost.php?p=57846051&postcount=233)
Enjoy Friends

NeedaVirus said:
Hi Hi Hiiii
For those who need the famous "restore-kitkat-bios-830-1050-v2"
HERE'S THE LINK (Personal re-upload) : https://drive.google.com/file/d/13vV6fpNAbWWZUk9_fzmJpMAMax2tlyyB/view?usp=sharing
Be aware that you probably need to do this if your OTA updates Fails :
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update
(Original Post here : https://forum.xda-developers.com/showpost.php?p=57846051&postcount=233)
Enjoy Friends
Click to expand...
Click to collapse
Thanks - when setting the country code if you get the 'ERROR : could not read factory ota patch from sd card,or the patch is not correct.' then you need to take the easyimage.zip from the extracted rom folder and copy it on the sdcard (on the root of it not in some folder) then try again (with at least 30% battery level).

Guys,
If someone wants to ROOT his tablet, I can write the procedure. (Many try for me before it really works...)
See ya !

hi everyone , i hope someone be able to help me with this , i also just got this tablet as one that does not even turn on , ive played with it a bit and managed to get some writings on the display, then i found this topic here and tried to follow as instructed, nothing happens, and the screen with fastboot starting goes off. any suggestion ?
thank you in advance.
{
"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"
}

THANK YOU!!
i have been battling with the TY2 1380f for a whole week with just a black screen. This helped as I was able to find the kit kat restore for the 1380 and following your guide, got things back to normal.
Life Saver!!!
dallivadr said:
Hey @NeedaVirus,
Sorry to hear that the device is bricked. Just this past weekend, I've been sifting through all my old resources because a recent OTA (Yep, a 2020 update!) left both me and my partner's 1050F devices in an unbootable state. You can see we're not alone by checking out the thread on the Lenovo forums (https://forums.lenovo.com/t5/Androi...Tablet-2-1050f-system-update-2020/m-p/5007166). Unfortunately a large number of the very helpful resources on xda seem to have been redacted/removed over the past few years, which leaves a few people scratching their heads (I was for a while too).
Basically, the way I've always done this on the 1050F (and what worked yesterday again), is as follows:
1. Install the "IntelAndroidDrvSetup1.10.0". Google will find this easy enough.
2. Install the flash tool. Nowadays, "Intel Platform Flash Tool Lite 5.8.4.0" (might also be called Phone Flash Tool Lite v5.8.4.0 and again google will find this for you) seems to come bundled with all required drivers, so it's a simple process to install.
3. Plug the device in and put it in DNX mode. This mode is achieved by holding vol up + vol down and pressing the power button until the device vibrates. When you feel the buzz, let go of power but hold the other two until you see a "Fastboot starting..." message on a black screen. This is DNX mode.
4. Restore stock KitKat bios using the "restore-kitkat-bios-830-1050-v2" tool. This one might take a little finding and I'm not sure if sharing it here is acceptable any more. Provided the device is plugged in and in DNX mode (and you have the Intel Platform Flash Tool closed too), it's just a matter of running the bios restore tool and following the prompts. Make sure the flash tool is running on your local drive (usually C).
5. Once the bios is pushed, we need to restore the stock KitKat ROM using the platform flash tool.
First we need to set up the Platform Flash Tool, so open that and select "File" -> "Options". Under "Flash options" tick the "Force fastboot sparsing" option and select "500MB" for the size.
6. Now, we want to use the "YT2-1050F_S0198_150422_ROW" image and you'll need to extract it first. It sounds like you already have the right archive file for this, which is good because I'm not sure if a copy still exists here still.
In the Platform Flash Tool, hit "Browse" and the file we're looking for is "target_bin\flash.xml". Select that. (Side note: I suspect that if your device has been updated to Lollipop in the past, you wouldn't have had any luck flashing this rom without rolling the bios back first).
7. Put the device into DNX mode again, and the Platform Flash Tool should see it (a "Baytrail" device is listed).
Now it's just a matter of starting the flash process by clicking the button.
8. Once the device is flashed, you'll need to reboot it (via the device) but wait for the flash process to report 100% first. Hitting the device power button is the way to confirm this reboot btw. It might take a few mins to get into Android here. This is normal.
9. Now, the device will boot into stock KitKat. We need to set the region though:
Open contacts, add new contact (only if you have none, we just need one).
Now, using the contact search, enter ####6020# and you'll be prompted to select your region. The device will reboot and you'll need to set a few things up again.
10. Run all the OTA updates to get right up to date. Just do this via android itself.
Optional: Do any other crazy bootloader unlocks, roots as desired. A lot of the original resources have been removed for these processes, but where there's a will, there's a way.
I'm sure there are other shortcuts to this process too. I think tontonfraguer was able to just flash a newer rom directly to resolve his bootloop, judging by his forum post over on the Lenovo thread. This is just the process I use, any feedback/improvements are most welcome!
Hopefully it helps someone being hit by the recent bootloops.
Cheers
Click to expand...
Click to collapse

hello

hoooman008 said:
hi everyone , i hope someone be able to help me with this , i also just got this tablet as one that does not even turn on , ive played with it a bit and managed to get some writings on the display, then i found this topic here and tried to follow as instructed, nothing happens, and the screen with fastboot starting goes off. any suggestion ?
thank you in advance.View attachment 5176433View attachment 5176431
Click to expand...
Click to collapse
any help would be greatly appreciated

hoooman008 said:
any help would be greatly appreciated
Click to expand...
Click to collapse
on your screen, attached, at device manager, i can see the driver for intel adb fastboot blabla is not correctly installed, try:
1. restarting windows while holding SHIFT button till it restarts
2. go through advanced restart option and select startup settings
3. when it reboots and offers to select in black-white options 1-8, select wit button F7 the "driver signature.." part
( you are now allowing to installing unsigned drivers )
4. wehn it reboots, INSTALL intel plattform flash tool.exe again and re-install everyting, this time u will see windows pop-ups in red notifiying you installing unsigned extra extra drama drivers, say yes to all of them
5. flash again, using above instructions, make sure to change intel plattform flash tool settings to force flash 500MB
6. go everyting that is instructed above - step by step - through and report, i had exact same problem and solved it remembering the driver-stuffs weirdness on windows, still not a problem at all, just anoying extra steps

NeedaVirus said:
Hello,
A friend give to me his Yoga2 1050F Tab, because it's bricked...
"After a kind of upgrade he said"
So, here's the situation,
Tab is really bricked, stuck on Lenovo Android Screen.
I've tried to factory restore, no success.
I've searched all the web after factory image to flash, I've found 3 of them... But nothing works !!
The 1st one, the only we can still found here, is a factory image from 2015. And the result is, no more lenovo android screen, i'm stuck on a kind of Bios (?) And can't do anything more...
2nd one, (YT2-1050F_S100196_151123_ROW-fastboot), best result, back to an android boot, but stuck on recovery screen, without any possibility to boot...
3rd one (YT2-1050F_S0198_150422_ROW) impossible to flash, it's always failed at "flash easyimage.zip" step.
Other thing, I don't know what xml file I need to use (flash, flash-blankphone, flash-factory ... )
Here, i'm totally lost. Tab is stuck, And I've no idea what can I do next...
Maybe here anyone can help me ?
Many Many thanks !
Click to expand...
Click to collapse
Download Lenovo's official "Rescue and Smart Assistant" it reflashes stock rom for you.

Huawei P9 Lite The phone does not get up / 5% instalation error / soft brick?

Hi!
As in the title, something wrong with my P9 Lite happened. Namely, the day before yesterday he decided to turn off by himself with a 50% battery there, but turned on normally after 2minutes. At night from Wednesday to Thursday it discharged and in the morning after charging I couldn`t start it.
The phone either booted and stopped several times on the Huawei logo and the note "Powered by Android". I can enter by using a key combination the eRecovery mode. Ultimately, it started up one time, and it worked until the evening and until it was discharged again. After that it has been charged to 60%, one time he turned on but after an hour of further charging he fell on the amen. I've been trying to fight him since the morning that maybe he'll turn on like yesterday, but no. I had this situation for the first time in August 2018, then in February and July 2019 with that it was probably a decent brick then, because this black screen was constantly displayed with an exclamation mark and some error. A visit in smartphone service has always helped, but I can't spend 80 PLN again to fix that issue. After the repair in July, I specially wrote the system version so that I would have knowledge for the future in the event of a repeat. The phone had the firmware as below:
{
"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"
}
Today I downloaded the system from this link: huawei-firmware.com/rom/huawei-p9-lite/vns-l21/9618
However, at 5% installation the error crashes and I can only restart the phone. I tried using two different sd cards, so the option of the card being faulty is 99% out of the question. I hope that some good soul will help me, because I believe that I can solve this problem independently at home and not necessarily after paying with a GSM spec. : P
I forgot to add that the phone has not been updated since it was repaired or anything. I didn't do any treatments myself with loading custom systems. He just turned himself off, without any previous signs of malfunction and end. I was surprised that the phone doesn`t want to accept the software that was uploaded by a service technician ... but maybe I am doing something wrong.
At the end fastboot situation:
PHONE: unlocked
FRP: locked
EDIT:
In another forum I got instructions to upload rollback and then soft "C432B160" and everything will be good. I took it up and the rollback installation was completed, after a minute the phone rebooted. Unfortunately, this problem caused another problem, because since I installed rollback I can`t enter the erecovery mode, where I have possibility to shut down...so phone stuck with the Huawei logo all the time. I was supposed to upload this software, but I had to leave the house and the phone was completely discharged when I returned. From that moment only fastboot mode starts, or after switching on and trying with different phone buttons, it always becomes a logo and got freezed. I was charging it for an hour, but after disconnecting from the charger the LED was blinking red and I saw on the screen message about 0% battery. After that another situation...I connected it to the charger and after a second showed me message of 100% battery, but after a second phone started automatically and hung on the logo again. After unplugging it from charger and trying to start without charging, the LED flashes red and message about disscharge was on the screen. Now I`m seriously starting to wonder, if anything from this phone will still be..... :/
Links to rollback and software (according to which I did not manage to upload before discharging the phone):
http://download-c1.huawei.com/downlo...00&siteCode=pl
http://huawei-firmware.com/rom/huawei-p9-lite/vns-l21/9571

Nicramcio said:
Hi!
As in the title, something wrong with my P9 Lite happened.
Namely, the day before yesterday he decided to turn off by himself with a 50% battery there, but turned on normally after 2minutes. At night from Wednesday to Thursday it discharged and in the morning after charging I couldn`t start it.
The phone either booted and stopped several times on the Huawei logo and the note "Powered by Android". I can enter by using a key combination the eRecovery mode. Ultimately, it started up one time, and it worked until the evening and until it was discharged again. After that it has been charged to 60%, one time he turned on but after an hour of further charging he fell on the amen. I've been trying to fight him since the morning that maybe he'll turn on like yesterday, but no. I had this situation for the first time in August 2018, then in February and July 2019 with that it was probably a decent brick then, because this black screen was constantly displayed with an exclamation mark and some error. A visit in smartphone service has always helped, but I can't spend 80 PLN again to fix that issue. After the repair in July, I specially wrote the system version so that I would have knowledge for the future in the event of a repeat. The phone had the firmware as below:
Today I downloaded the system from this link: huawei-firmware.com/rom/huawei-p9-lite/vns-l21/9618
However, at 5% installation the error crashes and I can only restart the phone. I tried using two different sd cards, so the option of the card being faulty is 99% out of the question. I hope that some good soul will help me, because I believe that I can solve this problem independently at home and not necessarily after paying with a GSM spec. : P
I forgot to add that the phone has not been updated since it was repaired or anything. I didn't do any treatments myself with loading custom systems. He just turned himself off, without any previous signs of malfunction and end. I was surprised that the phone doesn`t want to accept the software that was uploaded by a service technician ... but maybe I am doing something wrong.
At the end fastboot situation:
PHONE: unlocked
FRP: locked
EDIT:
In another forum I got instructions to upload rollback and then soft "C432B160" and everything will be good. I took it up and the rollback installation was completed, after a minute the phone rebooted. Unfortunately, this problem caused another problem, because since I installed rollback I can`t enter the erecovery mode, where I have possibility to shut down...so phone stuck with the Huawei logo all the time. I was supposed to upload this software, but I had to leave the house and the phone was completely discharged when I returned. From that moment only fastboot mode starts, or after switching on and trying with different phone buttons, it always becomes a logo and got freezed. I was charging it for an hour, but after disconnecting from the charger the LED was blinking red and I saw on the screen message about 0% battery. After that another situation...I connected it to the charger and after a second showed me message of 100% battery, but after a second phone started automatically and hung on the logo again. After unplugging it from charger and trying to start without charging, the LED flashes red and message about disscharge was on the screen. Now I`m seriously starting to wonder, if anything from this phone will still be..... :/
Links to rollback and software (according to which I did not manage to upload before discharging the phone):
http://download-c1.huawei.com/downlo...00&siteCode=pl
http://huawei-firmware.com/rom/huaw...
Your device is natively single or dual sim ?
Click to expand...
Click to collapse

Dadditz said:
Hey dude, let me know if i understood well...
Your device won't boot up anymore, isn't it ?
VNS-L21C432B120 ?? It's one of the oldest firmware you can have..
I really don't know if i can help, but if you agree we can give a try..
Your device is natively single or dual sim ?
Click to expand...
Click to collapse
Yas, my device won`t boot up since 1st of July and I don`t know why...because I don`t tried to update firmware, unlock bootloader etc.
I know that, but year ago I have a same problem and GSM service installed that soft.
My device is dual sim.
Thanks for help!

Nicramcio said:
Yas, my device won`t boot up since 1st of July and I don`t know why...because I don`t tried to update firmware, unlock bootloader etc.
I know that, but year ago I have a same problem and GSM service installed that soft.
My device is dual sim.
Thanks for help!
Click to expand...
Click to collapse
Ok let's go..
Take a working (at least 4gb) SD,
move away all your stuff then format it as FAT32.
Download this >> update.zip << file (VNS-L21C432B160/dual sim).
Unzip it, you find UPDATE.APP file.
Turn off the phone.
On your PC create a folder and rename it DLOAD.
Copy/paste (only) UPDATE.APP file into DLOAD folder
and put it into SD, then insert the SD into your device.
Turn the device on keeping vol+ & vol- then power button
all together till an update screen appears.
Ok, release now the buttons...
After the flashing process, your device should reboot to system.
If passes over 15 mins, reboot into the e-recovery
(press vol+ & power button) and do a factory reset + wipe cache.
Done !!
NOTE: the firmwrare link is taken using Firmware Finder repo,
all credits go to this fantastic app team/users that created it.

Dadditz said:
Ok let's go..
Take a working (at least 4gb) SD,
move away all your stuff then format it as FAT32.
Download this >> update.zip << file (VNS-L21C432B160/dual sim).
Unzip it, you find UPDATE.APP file.
Turn off the phone.
On your PC create a folder and rename it DLOAD.
Copy/paste (only) UPDATE.APP file into DLOAD folder
and put it into SD, then insert the SD into your device.
Turn the device on keeping vol+ & vol- then power button
all together till an update screen appears.
Ok, release now the buttons...
After the flashing process, your device should reboot to system.
If passes over 15 mins, reboot into the e-recovery
(press vol+ & power button) and do a factory reset + wipe cache.
Done !!
NOTE: the firmwrare link is taken using Firmware Finder repo,
all credits go to this fantastic app team/users that created it.
Click to expand...
Click to collapse
Thank you, but I tried to install by dload method some kind of softwares B120,130,150,160 if I remember...but no effects. In other forum, they said that I need to install rollback, and after that firmware B160. Ok, I installed rollback perfectly but after that I can`t go to erecovery mode...only fastboot is avaliable and whene I turn on phone it would stuck on Huawei logo. Now it`s discharged and i don`t have any idea how can i charged it to over 30% of battery.

Nicramcio said:
Thank you, but I tried to install by dload method some kind of softwares B120,130,150,160 if I remember...but no effects. In other forum, they said that I need to install rollback, and after that firmware B160. Ok, I installed rollback perfectly but after that I can`t go to erecovery mode...only fastboot is avaliable and whene I turn on phone it would stuck on Huawei logo. Now it`s discharged and i don`t have any idea how can i charged it to over 30% of battery.
Click to expand...
Click to collapse
Dude if there is some hardware problem
it will be a little difficult to recover..
so when you bringed it to service have they replaced the motherboard?
If not you may still have hardware problems, but let's keep this aside ...
Try again what i wrote..
In the meantime I give you the correct rollback link, maybe you used the wrong one.
Dude, the rollback package is used only to revert from android 7 to android 6.
In order to unbrick the device, in android 6 environment, dload method is enough..
Visit the UNIFIED HELP THREAD, post #6, see by yourself..

Dadditz said:
Dude if there is some hardware problem
it will be a little difficult to recover..
so when you bringed it to service have they replaced the motherboard?
If not you may still have hardware problems, but let's keep this aside ...
Try again what i wrote..
In the meantime I give you the correct rollback link, maybe you used the wrong one.
Dude, the rollback package is used only to revert from android 7 to android 6.
In order to unbrick the device, in android 6 environment, dload method is enough..
Visit the UNIFIED HELP THREAD, post #6, see by yourself..
Click to expand...
Click to collapse
I know it`s some kind of big problem.
3 times it was unbricked in service, but that is non authorized and they don`t do anything with motherboard...only installed me somehow new software for money circa 20 USD/EUR.
Okay i`ll try that tomorow and show results. I keep my fingers crossed, that my Huawei tomorow boot normal.

Nicramcio said:
I know it`s some kind of big problem.
3 times it was unbricked in service, but that is non authorized and they don`t do anything with motherboard...only installed me somehow new software for money circa 20 USD/EUR.
Okay i`ll try that tomorow and show results. I keep my fingers crossed, that my Huawei tomorow boot normal.
Click to expand...
Click to collapse
Sorry, i forgot to add the LINK to correct rollback package,
here you are..
Cheers
Edit: next time, maybe tomorrow i will post how to extract
firmware (BOOT,RECOVERY,SYSTEM) from UPDATE.APP
and how to flash it via fastboot commands.

Dadditz said:
Sorry, i forgot to add the LINK to correct rollback package,
here you are..
Cheers
Edit: next time, maybe tomorrow i will post how to extract
firmware (BOOT,RECOVERY,SYSTEM) from UPDATE.APP
and how to flash it via fastboot commands.
Click to expand...
Click to collapse
I don`t have time to do something with my bricked phone over a week, but today I tried to install software B160 and rollback by dload mode. It didn`t work. I can`t charge my phone over 30% of battery, and when I plug off the charger, phone have probably not enough battery to turn software installation. Also when I tried to hold 3 buttons, and then connected the charger cable...the installation didn`t start. So I think, that you must tell me how to flash soft via fastboot commands...because this is the only one mode that I can turn on my phone. I feel completely helpless, because today my replacement phone broke...so I have to bring Huawei back to life.
EDIT:
I forgot to mentioned...When i hold 3 buttons to start installation process phone vibrate one, then shown red lightning sign that battery is empty, and LED flashed 3 times red...then screen go black and device is powered off...nothing else. Also I tried 4 different SD cards, so I think now the problem with dload mode is that phone is not charged over 30 or 50% (I don`t remeber that) of battery what is required to start the installation process.
Also when I try to charge it, only LED flashes red all the time and on the screen I don`t have information that phone is charging.

Nicramcio said:
I don`t have time to do something with my bricked phone over a week, but today I tried to install software B160 and rollback by dload mode. It didn`t work. I can`t charge my phone over 30% of battery, and when I plug off the charger, phone have probably not enough battery to turn software installation. Also when I tried to hold 3 buttons, and then connected the charger cable...the installation didn`t start. So I think, that you must tell me how to flash soft via fastboot commands...because this is the only one mode that I can turn on my phone. I feel completely helpless, because today my replacement phone broke...so I have to bring Huawei back to life.
EDIT:
I forgot to mentioned...When i hold 3 buttons to start installation process phone vibrate one, then shown red lightning sign that battery is empty, and LED flashed 3 times red...then screen go black and device is powered off...nothing else. Also I tried 4 different SD cards, so I think now the problem with dload mode is that phone is not charged over 30 or 50% (I don`t remeber that) of battery what is required to start the installation process.
Also when I try to charge it, only LED flashes red all the time and on the screen I don`t have information that phone is charging.
Click to expand...
Click to collapse
Hi dude,
I suspect your device has some serious hardware problem.
If the device has fallen off, it may have broken or unstuck / unsoldered something,
hence the need for a check by specialized technicians / service point.
I suggest, if you have the possibility,
to replace the device with a new or even used one,
functioning and a little more updated / upgradeable.
But trying won't cost anything, so let's do it !!!
Make sure you have minimal adb & fastboot
or a complete platform-tools (link in the same page / it's your choise)
and huawei drivers /HiSuite on your PC,
then in fastboot mode do the command > fastboot devices.
If you have a response like > numbers/letters........device <
then you're ok to go, otherwise it means your PC don't "see" your phone...
From XDA download Huawei Update Extractor and use it
to extract BOOT.img, RECOVERY.img (not RECOVERY2.img)
and SYSTEM.img from your UPDATE.APP file
you extracted from update.zip...(see attachment)
Put those three files into a folder and rename it as you want
(maybe the same where you extracted UPDATE.APP),
then tap in the folder address bar (see attachment) and type cmd then hit enter.
A command window will appears, now you're ready to flash.
In order type following commands:
1 - fastboot flash boot BOOT.img; (let it flash)
2 - fastboot flash recovery RECOVERY.img; (let it flash)
3 - fastboot flash system SYSTEM.img; (let it flash)
Once finished type > fastboot reboot and cross your fingers...
If all will take right direction your device will reboot correctly,
otherwise (if passes over 15 mins) reboot recovery (vol+ & power buttons)
and do a factory reset..
Hope sincerely it will boot up... :angel:
P.S.: I don't know why i can't post jpg directly, so i zipped into one file...

Dadditz said:
Hi dude,
I suspect your device has some serious hardware problem.
If the device has fallen off, it may have broken or unstuck / unsoldered something,
hence the need for a check by specialized technicians / service point.
I suggest, if you have the possibility,
to replace the device with a new or even used one,
functioning and a little more updated / upgradeable.
But trying won't cost anything, so let's do it !!!
Make sure you have minimal adb & fastboot
or a complete platform-tools (link in the same page / it's your choise)
and huawei drivers /HiSuite on your PC,
then in fastboot mode do the command > fastboot devices.
If you have a response like > numbers/letters........device <
then you're ok to go, otherwise it means your PC don't "see" your phone...
From XDA download Huawei Update Extractor and use it
to extract BOOT.img, RECOVERY.img (not RECOVERY2.img)
and SYSTEM.img from your UPDATE.APP file
you extracted from update.zip...(see attachment)
Put those three files into a folder and rename it as you want
(maybe the same where you extracted UPDATE.APP),
then tap in the folder address bar (see attachment) and type cmd then hit enter.
A command window will appears, now you're ready to flash.
In order type following commands:
1 - fastboot flash boot BOOT.img; (let it flash)
2 - fastboot flash recovery RECOVERY.img; (let it flash)
3 - fastboot flash system SYSTEM.img; (let it flash)
Once finished type > fastboot reboot and cross your fingers...
If all will take right direction your device will reboot correctly,
otherwise (if passes over 15 mins) reboot recovery (vol+ & power buttons)
and do a factory reset..
Hope sincerely it will boot up... :angel:
P.S.: I don't know why i can't post jpg directly, so i zipped into one file...
Click to expand...
Click to collapse
Oh men i appriciate that you wrote everything. Only one problem, I can`t download the zipped file. :/ Also I keep in mind another type of solution for my Huawei, but more on that later. Now I gonna try to flash software by fastboot my hero.
EDIT: beginning gone well
EDIT2: commands not work properly. I done everything like you told me, but you can see error in cmd (cmd is enabled as administrator).

I download adb from this tutorial:
https://www.youtube.com/watch?v=OKRTbv-6Kzc
because previous didn`t work.
As you can see I typed "fastboot flash boot BOOT.img" as you told me, but I get info FAILED. :/
Searched for information and I found, that I need to unlock bootloader once again...and after that every command should work.

Nicramcio said:
I download adb from this tutorial:
https://www.youtube.com/watch?v=OKRTbv-6Kzc
because previous didn`t work.
As you can see I typed "fastboot flash boot BOOT.img" as you told me, but I get info FAILED. :/
Searched for information and I found, that I need to unlock bootloader once again...and after that every command should work.
Click to expand...
Click to collapse
Good work dude.
I previously readed on your post
phone = unlocked
frp = locked
i was thinking you was ready to flash
but evidently that was not correct...
For some unknown reason i cannot post
screenshots so i decided to add them on postimage...
As you can see they are quite same as yours...
https://i.postimg.cc/fTNZvWY9/VNS-L21-C432-B160.jpg
https://i.postimg.cc/x1s2YKhv/Extractor-select-your-update-app-file.jpg
https://i.postimg.cc/5t6MtXWZ/extract-BOOT-RECOVERY-SYSTEM.jpg
https://i.postimg.cc/LswFgmHh/open-command-window2.jpg
Let me know how the work goes on ...
Cheers

Dadditz said:
Good work dude.
I previously readed on your post
phone = unlocked
frp = locked
i was thinking you was ready to flash
but evidently that was not correct...
For some unknown reason i cannot post
screenshots so i decided to add them on postimage...
As you can see they are quite same as yours...
https://i.postimg.cc/fTNZvWY9/VNS-L21-C432-B160.jpg
https://i.postimg.cc/x1s2YKhv/Extractor-select-your-update-app-file.jpg
https://i.postimg.cc/5t6MtXWZ/extract-BOOT-RECOVERY-SYSTEM.jpg
https://i.postimg.cc/LswFgmHh/open-command-window2.jpg
Let me know how the work goes on ...
Cheers
Click to expand...
Click to collapse
Grazie molto!
I done everything with software, step by step just like in your images...
...but again no working commands.
I`ve got only info in CMD that FAILED (remote: Command not allowed).
In other threads I menaged to get info that,
if phone has never been rooted and get custom ROM the bootloader is not unlocked and I need to relock it.
The threads are old and then you have to get a special code from Huawei site,
and then tap fastboot oem unlock "special number" or something like that.
Now I don`t know how to get that code and is there any way to try unlock bootloader and take a step forward?
Yas, we done step forward tomorrow because we know that PC see my device correctly,
we have good firmware but CMD commands caused another problem. :/

Nicramcio said:
Grazie molto!
I done everything with software, step by step just like in your images...
...but again no working commands.
I`ve got only info in CMD that FAILED (remote: Command not allowed).
In other threads I menaged to get info that,
if phone has never been rooted and get custom ROM the bootloader is not unlocked and I need to relock it.
The threads are old and then you have to get a special code from Huawei site,
and then tap fastboot oem unlock "special number" or something like that.
Now I don`t know how to get that code and is there any way to try unlock bootloader and take a step forward?
Yas, we done step forward tomorrow because we know that PC see my device correctly,
we have good firmware but CMD commands caused another problem. :/
Click to expand...
Click to collapse
Due to the conditions your device is in,
I don't know if you can unlock the bootloader.
To read the code you can use DC-Unlocker
(PC or smartphone versions), buy credits for € 4 and try.
The risk is that if it doesn't work, you throw away your money.
A user HERE suggested the idea of using a method
a little more spartan and without money,
but honestly I have never tried it and you could physically break something ...
The choice remains yours, keep me informed for future developments.
P.S .: Bardzo dziękuję za opinię ...

Dadditz said:
Due to the conditions your device is in,
I don't know if you can unlock the bootloader.
To read the code you can use DC-Unlocker
(PC or smartphone versions), buy credits for € 4 and try.
The risk is that if it doesn't work, you throw away your money.
A user HERE suggested the idea of using a method
a little more spartan and without money,
but honestly I have never tried it and you could physically break something ...
The choice remains yours, keep me informed for future developments.
P.S .: Bardzo dziękuję za opinię ...
Click to expand...
Click to collapse
Ciao!
I`ve tried to use this spartan method...but all that nordic combinations were useless...because I still have fake unlocked bootloader. I`ve decided that motherboard in my phone is a piece of **** and merda, so I`ll buy a little damaged phone. The cost of it is 27EUR, so it`s around DC-Unlocker+DC-Phoenix...but I`ll get a device that work properly and have some scratches.
I don`t want to spend money to my damage and dumping motherboard...because I have done this in the past 3 times (the cost of these repairs are around 60EUR). If I had enough knowledge that my motherboard will break down regularly in the future, I`ll buy used P9 Lite much much earlier.
https://allegro.pl/oferta/huawei-p9-lite-lekkie-pekniecie-prawy-gorny-rog-9523407957
Thanks you all, because we tried a lot of methods and solutions! I'm really thankful for all help!
Grazie mille Dadditz mio eroe. Ciao ragazzo! :laugh:

Nicramcio said:
Ciao!
I`ve tried to use this spartan method...but all that nordic combinations were useless...because I still have fake unlocked bootloader. I`ve decided that motherboard in my phone is a piece of **** and merda, so I`ll buy a little damaged phone. The cost of it is 27EUR, so it`s around DC-Unlocker+DC-Phoenix...but I`ll get a device that work properly and have some scratches.
I don`t want to spend money to my damage and dumping motherboard...because I have done this in the past 3 times (the cost of these repairs are around 60EUR). If I had enough knowledge that my motherboard will break down regularly in the future, I`ll buy used P9 Lite much much earlier.
https://allegro.pl/oferta/huawei-p9-lite-lekkie-pekniecie-prawy-gorny-rog-9523407957
Thanks you all, because we tried a lot of methods and solutions! I'm really thankful for all help!
Grazie mille Dadditz mio eroe. Ciao ragazzo! :laugh:
Click to expand...
Click to collapse
I am in complete agreement with you, you made the right choice.
I was very happy to try to help you, especially because
you are a polite and kind person.
I hope to meet again in the future, but not for device's issues ... :highfive:
I wish you all the best.
Regards

stuck on 5% , software install failed, getting package info error
i used huawei p9 lite vns L22 dual sim , device has got failed verfication ,asking for update latest version, then its stuck on 5% .software install failed, i have a poor knowledge about techniqal issues, please help me out

Help!! I accidentally soft-bricked (or hard-bricked) my PX6 Rk3399 Android 10 HU!

First of all, thank you so much all for any help!! It's my first time posting in the forum which I think speaks to my desperation state right now:crying:, so anything is greatly appreciated!
I bought an Android 10 unit with the PX6 Rk3399 processor, but it had some bloatware that I wanted to get rid of (mainly a knock-off android auto that started when I plugged my phone in even after disabling the app and it got pretty annoying). I decided to root the unit, but it wouldn't stay rooted after restart. I then decided to let SuperSU update the SU binaries despite knowing that something could go wrong, and of course the unit went straight into bootloop!
I then accessed Recovery mode by long pressing the power button (waiting for the unit to flash 5 times) then releasing and pressing again (don't ask me how I found this out). It had an option to flash updates, so I tried flashing the Kal9k Android 9 ROM, with no luck (kept getting error 1001). Then I found a firmware in update.zip form for a similar radio, with my processor and ram and etc from sygav, so I decided to flash that one using the update option on recovery. No luck though, as it was still stuck on boolook with a ford logo (as if the original system partition wasn't flashed and was still there). I couldn't access adb from recovery to see if I could delete the SU folder (if I plugged a USB cable on recovery, the computer didn't seem to see anything), so I booted into bootloader from recovery. Which by the way, was a black screen but did get picked up through USB by windows.
After tinkering with drivers for hours, I don't know how, but my unit got connected and recognized by fastboot. But in trying to erase the system partition, there was no way for system to be found. Every other partition (i.e. cache) could be erased but not system. I also couldn't flash the firmware I found because it being an update.zip, it didn't have a system.img (but it did have an image for everything else, such as boot, recovery, etc).
So I decided to flash a firmware from a guy on the internet that had a soft brick, and I flashall'd it. Now I'm starting to think this guy's firmware was for another completely different system (oh and by the way, System.img failed to flash as it couldn't find the partition, but it really was the only firmware I could find that had a system.img, so since I was completely desperate I stupidly went for it).
Now I can no longer boot into recovery, and I might be booting straight into bootloader mode, but I am not that sure. After I do the trick with the lights flashing and all, the device gets picked up by my computer, but as an unknown device:
{
"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"
}
I manually update it's drivers with the downloaded bootloader drivers from the android sdk (google USB drivers) and it gets detected as a Kedacom USB device, not an Android Device, so no fastboot:
Then if I disconnect it and connect it again, it shows up as an unrecognizable USB device or something like that.
It seems like the same problem I had when I first connected to bootloader, but I don't even know what I did to fix that . I think I might have rebooted into recovery, and then from there booted into bootloader, and somehow my computer then had Android drivers available for install and I manually installed them and it worked? Maybe? I really have no idea, but I can't try that because I can't get to recovery.
I have an update.zip with what I think is the closest firmware to what my radio had originally, an Android 10 PX6 firmware, from which I was planning to install the boot, bootloader and recovery if I had access to fastboot (which I really don't know how to make windows see that it might be a bootloader device), however, since I don't have a system.img to flash and bootloader doesn't even find the system partition, I don't even know where I would go from there.
What do you guys think I should do? What are my options? Did I just hard brick my unit? I wouldn't think so because windows detects "something" even if it can't assign it the driver. But if it is hard bricked, I am not scared to open it up and to do whatever I have to do, if just am really unsure on what to do and how to do it!
Again, any help is highly appreciated! And thank you so much in advance!:fingers-crossed:
SOLUTION:
Alright, this was a ride! It took me about two weeks to find the solution. No matter what I flashed from the recovery, the unit would still be on bootloop, but the last thing I flashed was an update.zip I found on the internet from some guy, and that made my unit completely hard bricked and irrecoverable (no access to recovery). So here's what I did.
Apparently, reading around Rocketchips (PX3,PX5,PX6) have like a "if everything else fails" kind of mode, for stupid people like me, called MASKROM Mode. It's the last resort mode that lets you flash something on the unit when everything fails. That mode is not flashable (you can't mess it up). It's kind of like if a computer had an integrated last resort in case you mess up and break the BIOS.
To get to it though, it is kind of complicated. You need to get to the PX6/5/3 board, which is basically the heart of your radio. So start unscrewing!
The board will look something like this one:
https://sc01.alicdn.com/kf/HTB1f6tCE.R1BeNjy0Fmq6z0wVXaC.jpg
Where the top part is a heatsink that you might also have to remove. PX5s and PX3s may not look exactly like so, but look for something of more or less the same characteristics and form factor, you'll know when you see it.
Go ahead and remove the board from the unit VERY CAREFULLY (the female pin sockets break VERY VERY EASILY from what I've heard, so be very careful).
Next, we will need to connect the PX6/5/3 to the computer through USB. For that, we will have to make a custom cable. Here's the link to the forum where they explain how to make that cable in detail: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Shoutout to @marchnz , he's a genius and without his help I certainly would have wasted my $400 I spent on the headunit.
So long story short, take a USB to something cable (the ones for your phone, for instance), strip it, and solder some resistances to it in the EXACT SAME WAY as in the pictures in the first post of the forum.
Now, connect the cable in the same way as the pictures if you have a PX5 or PX3.
IF YOU HAVE A PX6 find out which pins to connect in PAGE 2 of https://forum.xda-developers.com/an...s-development/px6-maskrom-mode-t3989407/page2 , in the pictures of a post by @oton .
Now download Androidtool here: https://github.com/rockchip-linux/tools/blob/rk3399/windows/AndroidTool_Release_v2.52.zip . This is the software that is going to let us access the mode I was talking about earlier.
Once you have it install, restart and plug in your USB end of the cable. Open the device manager on windows. If you see an Unrecognized device pop up, or a malfunctioning USB, you will need to install the drivers. Here's the link to where you can find an autoinstaller: https://github.com/rockchip-linux/tools .
If, after all, you still are having issues with the drivers, you'll need to install them manually. So right-click on the unrecognized device, update driver, browse my computer, let me pick, Have Disk, and then you find the drivers that we just downloaded (unzip them, of course). Choose the driver, and close and re-open Androidtool.
If you see Maskrom device detected on the bottom, you're all set! If you see recovery device detected, you'll have to put it on Maskrom, for good measure. It might work on recovery, but I'd put it in maskrom mode anyway. To do that, you'll have to disconnect the usb from the computer (while the other end with the cables is still hooked to the board), short two pins on the other side of the board (where the heatsink was) (for a PX6, you can find out which ones here https://forum.xda-developers.com/showpost.php?p=80641439&postcount=435) (for a PX5, I belive it will be on the thumbnails of the first post here: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892) (if you can't figure out which ones, google search for pins to put your unit in maskrom). While you are shorting those pins (maybe with some metallic tweezers), plug in the usb, stop shorting the pins, and the unit should show up in maskrom.
Now dowload an update.img from the following repository: https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/YB . If it tells you to download something, just click on the file until you get to the .rar screen and click on the download arrow on the top right of the screen.
Important: FOR MY UNIT, I HAD TO DOWNLOAD MANY UPDATE.IMG BEFORE 1 WORKED. ONLY ANDROID 8.1 WORKED FOR ME, SO KEEP TRYING! YOU'RE ALMOST THERE!
ALSO, DO NOT DOWNLOAD ANY OTGs (update.zip), ONLY DOWNLOAD IMAGES (update.img).
Now go to upgrade firmware on Androidtool, click on firmware, choose the update.img you downloaded, and start flashing it!
You'll get a progress readout on the right side, and you'll know when its done. Now it's time to put everything back together and hook up the unit and see if it worked. If it didn't or if it's in bootlooop, download another image from the repository and try again. The only one that worked for me was android 8.1.
Okay, so now everything worked and you got your Head Unit back! But what if you had to downgrade android for it?
Here's how to bring it back to its former glory:
From where I stood (android 8.1), the android 8.1 recovery wouldn't allow for android 9 or android 10 flashing. And I found some info on how to flash PX5s recoveries, but nothing on PX6, so I went to Hal9k's website and purchased his modinstaller 2 and followed instructions. Through there, you'll have the chance to update to android 9 or 10 (up to you), by running his apk that will install a new recovery on your machine, and then flashing any update.zip you want. In my case, I decided to also go for his ROM, because of the features it offered. The whole process was 10 bucks but I think it was completely worth it (honest opinion, not sponsored). You can also opt for installing and Android 10 ROM, as I had at the beginning, but I've heard they're pretty unstable.
So that's all! Not an easy project, but at the end you'll have your unit back and running!

I'm guessing you've seen this rom thread? There's a link to the stock stm firmware in the thread, if that's what you have.
https://forum.xda-developers.com/an...rom-malaysk-rom-px6-mcu-stm32-rk3399-t4111653
When mine was stuck on the black screen, I had to short 2 pins out on the board which entered recovery mode. I then managed to get it working from there. I can post a photo of which pins if it's any use to you?

skipraider said:
I'm guessing you've seen this rom thread? There's a link to the stock stm firmware in the thread, if that's what you have.
https://forum.xda-developers.com/an...rom-malaysk-rom-px6-mcu-stm32-rk3399-t4111653
When mine was stuck on the black screen, I had to short 2 pins out on the board which entered recovery mode. I then managed to get it working from there. I can post a photo of which pins if it's any use to you?
Click to expand...
Click to collapse
Hi! I saw that ROM, but when I went to download it it still gives me an update.zip file with all the recovery.img, boot.img bootloader.img but no system.img. I guess I could boot it to recovery and apply the update there, but I think my recovery is also gone :/
Regarding what you said though, are you talking about the maskrom mode? or something like that? Or do those pins just take you into recovery? I could try it but I don't know if Recovery will even work :/
And if they put the radio in maskrom, where do you go from there?? And sure! A picture would be more than greatly appreciated!!
Thank you so much for all your help!!!

To be honest with I'm not sure if it is the maskrom mode, I'm no expert with these things.
All I was getting out of mine was a black screen, but shorting these pins out and powering it up entered a recovery mode each time. Might be worth a try.

skipraider said:
To be honest with I'm not sure if it is the maskrom mode, I'm no expert with these things.
All I was getting out of mine was a black screen, but shorting these pins out and powering it up entered a recovery mode each time. Might be worth a try.
Click to expand...
Click to collapse
My board looks different from that one and I can't seem to find any pins that look like could be shorted :/
I'm at the point where I can flash update.img into the board with my computer (through connecting pins to some USB cable), but I cannot find any full OTG flash for my PX6!
Any ideas? This might be too much to ask but is there any chance you could provide me with a full otg backup of yours to flash on mine maybe?

alfondehesa said:
My board looks different from that one and I can't seem to find any pins that look like could be shorted :/
I'm at the point where I can flash update.img into the board with my computer (through connecting pins to some USB cable), but I cannot find any full OTG flash for my PX6!
Any ideas? This might be too much to ask but is there any chance you could provide me with a full otg backup of yours to flash on mine maybe?
Click to expand...
Click to collapse
Hi,
I have no idea how to do that, and the unit is back in the car now. I ended up keeping the stock rom to be on the safe side! Sorry.

I'm stuck in bootloop on Android 10 PX6 MTCE, headset has no HW buttons only a reset button, can't seem to access recovery.
What step should I try first? I am a total noob and don't own a soldering iron.
Paperclip and recovery?
Update.zip won't flash before rom boot will it.
If all else fails can someone post me a USB OTG?
I only started messing as Malaysk rom had no software volume change for me. Xposed install then reboot looks like a bootloop. Was my Christmas present as well

Hello My Threecar device crashed.
I could not connect to the port in the picture.
The computer does not see the device at all. Does not detect.
Red square. I shorted the feet and the computer never detected it
How can I do PC device detection

Hi, What kind of connector are you using ? can you send a link for that connector or give the connector name ?

radskin said:
Hi, What kind of connector are you using ? can you send a link for that connector or give the connector name ?
Click to expand...
Click to collapse
Hi.
JST-SH 1.0 mm 4 pin Connector

bicer79 said:
Hi.
JST-SH 1.0 mm 4 pin Connector
Click to expand...
Click to collapse
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.

Sorry mate.
I confused it with another device
jst 1.25 connector 4p female

if you want i can pay you

radskin said:
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.
Click to expand...
Click to collapse
radskin said:
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.
Click to expand...
Click to collapse

bicer79 said:
if you want i can pay you
Click to expand...
Click to collapse
Tanks for the offer, but I work at a company that sells this type of material. I ill look for the right type of connector.

radskin said:
Tanks for the offer, but I work at a company that sells this type of material. I ill look for the right type of connector.
Click to expand...
Click to collapse
This is the correct connector
JST 1.25 mm connector 4 pin female

Hi,
I have same board like skipraider, when I short these two pins there is no results. Should I connect board to PC by USB cable. My radio is freezing on black screen after car logo. It happend after updating software and it was take very long time on erasing part so then I restarted radio and it never woke up If I should connect to PC by USB using 4 pin connector has someone pinout description of this connector. Where is Ground, 5V+ , DP+ and DP-?

welcome
Sorry, I don't know English, but I translate from Google. I have a problem. I updated the screen and an error occurred. And because a black screen appears after the logo appears. I can not enter the recovery recovery. The computer refuses to recognize the screen. There is someone who said it must be a 6pin. How do I get the cable that holds the 6 pin. Or is there a way to revive?

[ROM][PX6][STM32][9.0] Malaysk ROM for PX6 MCU STM32 RK3399 with Android 9
Only for devices processor Rockchip PX6, MCU - STM32. Mod Pie 9.0 Android PX6 STM32 RK3399 Not suitable for those who have a real 10 android installed. Install the Device Info HW application in Google Market and look at the API level. 28 API - 9...
forum.xda-developers.com
Examine this topic. Here is how to recover bricked device.
jst 1.25 connector 4p required