After spending 2 days on the forums and softbricking my device for several times, here's my 2 cents about on how to do the upgrade from Andorid 10 to Android 11 or even to downgrade ... on the HA units from Dasaita.
First of all, a small disclaimer:
This worked for me, it might not work for you.
You might end up in bootloop, blackscreen, softbrick, be aware of this risk
My device is a Dasaita Max11, I wanted to downgrade to A10, in order to get Magisk and Hal9k v5 mod installed.
After purchasing modinstaller 3pro, and trying to install Andorid10 I ended up in a blackscreen. Hopefully @Hal9k_ will be able to fix this in his further releases.
Remember, this was ONLY tested and worked on a MTCE_HA device. A rather new model sold by Dasaita last december. If you have a HTC or other device this has no or litlle importance to you, since the images atached are ONLY for HA devices. Also, if you have an older Dasaita model, it might not work as described bellow:
What you'll need:
- a USB A to USB A cable (as short as possible)
- the purple usb plug cable (labeled carplay/android auto) that comes out of the back of de divice (this is the only one that recognized my device in bootloader mode. Feel free to try the others, in function of what configuration your device might have.
- driver assistant (see google drive link)
- flash tool (see google drive link)
- full system image of Android 11 or 10 regarding what you want.
- a pin or paperclip to push the reset button.
The procedure is rather simple:
1. Download and install the driver assistant (google drive link at the end), run it to install the drivers on your windows machine
2. Unpack rkdevtool and run the exe (google drive link at the end). At this point the program will display a huge message in the bottom part saying: "no devices found". That's good.
3. Connect the Usb cable to the HU and to the PC, while the device is turned off (like no power, not in sleep mode)
4. Push the reset button and keep it pushed. While doing this turn on the device. At this point if everything is setup correctly you should hear a notification sound from windows and RKDevTool should say: "Found one bootloader device".
4a) If you only hear the notification and the device is not found in boot loader mode by RKDevTool, check Device Manager and try to reinstall the drivers / install other drivers, try another USB port. (at this point, the usbA to usbA might be to long if the device manager shows: unrecognized device)
4b) If you hear no sound, RKDevTool still shows no devices: Turn off the HU, (really of, no power). After 10-30 seconds turn it on, while it is on, press the reset button and keep it pressed (even after side leds flashing) until the device enters bootloader mode and it is recognized by the RKDevTool.
4c) If none of the above work, switch the usb port on the HU, or try another combination of reset pushing (like trying to enter recovery)
4d) If the PC won't recognize the device in bootloader mode, it might be a situation in which the device is not capable of this, and you might need to take it apart and use the direct SOM flash method ... search the forums.
During step 4 the HU display should remain black, so the only indication of being in bootloader mode and connected to the PC, is the windows notification sound and the messege displayed by RkDevTool.
5)With the device in bootloader mode, connected to the PC, in RKDevTool go to the tab that says: Upgrade firmware. Click on the line(empty rectangle) that says firmware and browse for the desired android img. (10 or 11). See drive link. Attention: the zips from the drive MUST be unpacked and the update.img must be loaded in RkDevTool.
6)After selecting the desired update.img, click on the ERASE FLASH button, wait until the process completes. If everything goes well, the device should reboot in maskrom mode.
7)After the device enters maskrom mode, RkDevTool shoul display the message: "Found one MASKROM device". At this point, just click the UPGRADE button. The new android is flashed on the HU. When the process is finished the HU reboots ITSELF. If that doesn't happen after 1-2max, cut the power and power on.
It should boot in the new android.
Final thoughts after 2 days of thinkering:
This worked for me to downgrade from 11 to 10, and also to upgrade from 10 to 11. Be aware it might NOT work for you!
In theory, if one can get the device in bootloader mode it should work also to upgrade from andoid 9 to 10. This is just a theory and I did not test it.
The advantages of Android 10 over 11 are (for me):
- root access via Magisk (for the time being I could not root 11 with any of the tutorials found online)
- less crap and restrictions imposed by the growing Google censorship..
- the possibility to install the Hal9k v5 mod, one of the greatest and customizable mods ever made for MTCD/MTCE devices.
- using both 11 and 10 I could very certainly tell you, that (from my point of view), 11 has no advantages over 10, nor in stability nor in sharpness.
The images from the google drive are vivid for android 10 and max for android 11. Again, this are FULL images, not just OTA. I put them here after endless hours of searching the net. I respectfully thank to those that took the time to upload them on xda and dasaita forums.
Once you install the base 10 or eleven you can easily switch from vivid to max via update.zip flashed from an usbstick.
Also: there are many tutorials that involve a sdcard, sdcardtool and different combinations of zip images. I tested them ALL using the side sd card slot of the device. NONE OF THEM worked for me. I found the OTG flash method to be the fastest and most reliable, once I figured out how to connect de HU to my pc in bootloader mode.
PX6 MTCE_HA Android 10 full image, Android 11 full image, RkDevTool, Driver Assistant link: https://drive.google.com/drive/folders/1eigYrCKl8Z34KQxBoX3Q91Foy2K15CGm?usp=share_link
Nice! Do you perhaps know where to find the files for other headunits? I have a MTCE_HT and have no idea where to look!
Related
Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!
This can be done without a toolkit, Flashing factory image with fastboot instead.
Toolkits cause many of the issues on here, learning to do it manually with fastboot can both avoid issues, and fix issues. And teach people valuable skills.... As adb/fastboot are essential tools, especially with a Nexus. ?
But thanks for the info. Contributions like this are always good. ?
Problems with "Boot Failed"
visnkmr said:
Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!
Click to expand...
Click to collapse
Well I had a different kind of problem.
My Nexus was running fine in 4.4.4 when I rooted it since it was out of warranty. It upgraded to Lollipop 5.0 without a problem and continued to function in rooted state.
It made several attempts at updating to 5.0.2 but always ended with "Failed" message. I figured unrooting the device might help with the OS upgrade. It did not and screwed up everything. I then Set it to Factory default and it went to wiped 5.0 state. Then disaster struck. I tried rooting it , unfortunately with older Chainfire which bricked the device and would not let me install 5.0. So I tried to force install 4.4.4 and then the device got bricked. I simply get the message "Boot Failed" I boot into fastboot mode and I get the basic display with green start in the upper right corner, large Android icon in the center of the screen and the standard fine text on the lower let side. Unfortunately Windows ( x64 - Ultimate) insists on recognising the device as "Unknown Device" and when I go into properties this is is what is states ...
"Windows has stopped this device because it has reported problems. (Code 43)"
Do you think I might have better luck if I tried this on a Win XP machine ? I have both, x86 and x64.
Now, can you please tell me how I can get around this problem ?
BTW I do remember olden days of Cassiopeia PDAs before the flash memory came on the stage. The original OS would be on a plugged in masked rom daughter board in the event of losing all battery power. You could always force it to load it and get to factory mode. I think it is high time Android device manufacturers reverted to this process. I believe it can live side by side with the current system at a very marginal higher cost but have a whole lot of satisfied and LOYAL customers. It would give the user ability to go to factory mode albeit without any OS updates/upgrades but a fully functional device.
Would very much appreciate your feedback.
WHAT IS HARD-BRICK?
The Hard-Brick, translated means device NULL, without function neither one! This happens a lot for forced updating: AS ANDROID 4.4.4 FOR 5xx ....
Most of the time, the cell phone stays in BOOTLOOP (infinite loop), another case as hard brick gets on the black screen with LED access.
Then you ask me?
Wagner, I Brickei my device, how to recover?
YES! There is always a way to recover. More remembering that each device has a way of doing, some are easier and others more complicated. We just need to find the right files.
So let's go!
MOTOROLA DRIVER
Drivers required for device recognition on PC.
If you have already installed, you do not have to install again.
Download
HAND-BRICK.exe
It will install the drives, recover the cell phone and recover the fastboot.
Download
STEP BY STEP
1- Turn off the phone and enter the fastboot mode:
Yes, I know the phone is off!
Plus the device is in operation and we need the phone to be turned off and enter the Fastboot mode.
HOW DO I DO THAT? I discovered two ways!
- Fast and easy mode:
OPEN THE PHONE AND DISCONNES THE BATTERY, IT WILL PLACE THE FATBOOT MODE.
IF YOU MAKE ERRORS IN COMMANDS, YOU CAN GET THE FASTEST ANSWER.
- Time-consuming and need patience:
PLUG THE PHONE TO CHARGE "INTO THE SOCKET", THE LED GOES ON, WAITES THE LED OFF.
If the LED does not turn on?
SAFETY THE POWER BUTTON ON + THE DOWN VOLUME, FOR 2 SECONDS OR ACCOUNT UP TO 30!
THEN PLACE INTO THE OUTLET, AND OBSERVE THAT THE LED WILL TURN ON! And wait until the LED turns OFF.
Why did I say I had to be patient?
Well, you're going to do this straight, each made the commands go wrong.
And it will only work again if the phone restarts. Many times the LEDs do not light up among other things like not recognizing on the PC.
HOW DO I KNOW THAT IT WORKS?
When using the unbrick, it will show you a path:
EXP:
C: / USERS / NAME / DESKTOP / MOTO MAXX / PORTUGUESE [BR] / 2 - REVIVER FB / UNBRICK - 5.1> .QBOOT BLANK - FLASH
AND THEN HE SHOWS THE RECOGNIZED FILES.
When of FAILED?
(BLANK-FLASH: **********):
THE FILES WILL BE DEMANDED TO BE RECOGNIZED, THEN IN THIS CASE THE COMMANDS WILL NOT WORK! AND AI FOLLOW THE STEPS AGAIN THE LED!
OK! now that the phone is off and ready to use the unbrick.
Remember, every time you use the unbrick and appear errors, you will have to repeat the STEP to turn on the LED!
2 - Connect the device to the PC, and check that the device is being recognized as QUSB-BULK.
Search the device manager for your PC.
And look in the part (Ports (COM and LPT)) and see if you recognize the device!
3- Install the MOTOROLA + Qualcomm USB drives.
In the Device Manager will shows that the device is being recognized as QUALCOMM.
4- Choose the Unbrick option and execute the files "GO" and wait ends up to 100%
NOTE THAT: THE PHONE WILL BECOME LIFE, AND SHOW THE BOOTLOADER WITHOUT ANDROID!
If it looks like FAIL - You have to repeat STEP 1 to turn on the LED, done that, Test other files
Contains GPT.BIN files from Android 4.4.4 to the latest version 6.0.1!
CASE NOTHING WORKS USE THIS FILE "download"
1 - REMOVE THE ARCHIVE
2- EXECUTE THE FILE WITH THE NAME "GO.bat"
3- NOTHING EVEN? ENTER WITHIN THE "DATE" FOLDER AND EXECUTE THE "01 GO.bat"
4 - NOTHING EVEN? EXECUTE THE FILE "02 GO.cmd"
ONE OF THOSE FILES MUST WORK, BECAUSE THERE IS ONLY THIS FILE!
Now go to the Fastboot option and execute the files "GO"
Contains GPT.BIN files from Android 4.4.4 to the latest version 6.0.1!
THE NEW VERSION IS MARKED WITH RED!
6. Ready! the cell phone will restart with Android 5.0.2, but this one with ERROR does not connect in the WIFI!
To correct this error, turn off the phone
Enter Fastboot mode
Choose a ROM STOCK "here" and install.
If you want a customized ROM First:
Download the new version of TWRP "here"
Choose a CUSTOM ROM "here"
And the GApps according to Android Chosen "here"
READY! YOU CAN BE HAPPY AND INSTALL ANY ROM THAT YOU WANT.
REMEMBER THAT THE ROM Stock 4.4.4 CAN NOT BE UPDATED OVER.
Hope this helps!
do not forget to leave your LIKE and SHARE, leave your comment than you found.
Hi Wagner! The "HAND-BRICK.exe" download link isn't working. Could you provide a new download link, please? Thanks in advance!!!
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
wxtester said:
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
Click to expand...
Click to collapse
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
AeonFlux1603 said:
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
Click to expand...
Click to collapse
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
wxtester said:
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
Click to expand...
Click to collapse
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
AeonFlux1603 said:
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
Click to expand...
Click to collapse
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
wxtester said:
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
Click to expand...
Click to collapse
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.c...-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
I have the same issue. I dont know how but i got hard bricked completely. I was flashing rom on it and it got bricked. Now service centre guy is saying that i have to change motherboard altogether. But your post seems convincing. Please let me know the next detailed process.
i have the same issue.
one day stop working
AeonFlux1603 said:
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.cdn.ampproject.org/v/s/forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/amp/?amp_js_v=a2&_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&_ct=1551037935701&referrer=https://www.google.com&_tf=From %1$s&share=https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
Click to expand...
Click to collapse
what is next? i have a tab 3 710f that is very dead.. hardbricked in wont boot into nothing.. black screen like its shut down
Hi all, a need help. After an unsuccessful update, I received a bootloop. There are no physical buttons on the device. Found instructions for recovery through ANDROID TOOL. I connected it to the computer in maskrom mode, but I can’t find the firmware that needs to be uploaded in order for the device to work. Share a dump that suits me or give instructions on how I can restore the device.
They're all there in the MTCD forums.
Thanks for the answer, but all I found is different ota update.zip. And my device is loaded only in maskrom mode.
That's why I'm looking for a full recovery version.
Hi, you have to use the IMG file that contains the recovery and then update normally via OTA. For example, the IMG is:
CHS2_RK3399_10.0_IMG(20200424)
HCT7_rk3399_10.0_IMG(20200415)
OLS_rk3399_10.0_IMG(20201012)
Яндекс
Найдётся всё
disk.yandex.ru
I recommend reading this thread, you will find answers to your questions here:
[MTCD/E] Android 10 upgrade using official Free tools
To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads. First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported...
forum.xda-developers.com
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
s.danyliak said:
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
Click to expand...
Click to collapse
Erase first
I did, first cleared, reboot and firmware. The result is the same I read a lot of documentation, they wrote that there may not be enough power, but the power supply is 5A.
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
s.danyliak said:
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
Click to expand...
Click to collapse
I had the same problem I bricked my headunit (rk3399 PX6 Android 10) trying to recover root after updating magisk to 25.1 went into maskrom mode but device lost connection to my PC and flash fails at different percentage.
Cause ended up being the adapter i was using to power the device I used 12v 2A adapter
After switching to 12v 10A adapter it finished flashing. BUT make sure the chip has cooling like a heatsink or it will overheat during flash.
I changed the power supply to 10A. Installed cooling. The result is the same. The device reboots even if nothing is done.
Have you tested another USB cable? @s.danyliak
I have tried two different cables. But I connect via usb which is from the device kit and also the usb a - usb a cable is possible in this problem. There are also only 4 contacts, and for otg you need 5. I did not find information on the board I attached the photo.
Does anyone have any ideas ?
Ask seller for schematic and share here for feedback
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
s.danyliak said:
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
Click to expand...
Click to collapse
Short the two pads while powering on. Lift short after powering on
I tried, I can no longer enter maskrom with this method
EDIT: Instructions for updating the ROM are in the third message and they work for everyone, rooted or not.
This is specifically for the RFinder B1+ with 6 GB of system RAM and 128GB of built in ROM but with or without the First Responder designation or Band 14. It will likely work with all three RFinder B1+ radios as they use the same MediaTek chipset.
***THE B1 CLASSIC ROOT METHOD IS TOTALLY DIFFERENT***
***I AM NOT RESPONSIBLE IF YOU DAMAGE OR DESTROY YOUR DEVICE***
***I AM ALSO NOT RESPONSIBLE IF YOU VIOLATE FCC RULES OR WHATEVER THE EQUIVALENT AGENCY US IN YOUR COUNTRY***
In a nutshell, if something goes wrong, it's up to you to fix it. Though there are very few ways to brick the RFinder, keep in mind it's also a two way radio, so don't blame me if yours falls apart, you burn yourself on an exposed part of the antenna, the family cat runs off, you manage to summon security on their local DMR channel, or if it gets stuck in an infinite loop showing sample Pac Man footage.
For those unfamiliar, there are a few combo radio and Android units. The RFinder B1+ is one of them. I see no advantage to rooting on the radio side; most amateur radios offer you as much access as you need. AnyTone offers access to *everything*, they're completely unlocked. Motorola Solutions (not the Motorola seen most often here) keeps strict control of what you can access. Analog only devices vary but have a lot of access through the program Chirp.
Now that we've worked out you're here to root the Android part instead of the radio, let's dive on in.
Here's what I used:
A laptop running Windows 11
My Moto G7 (Mobility, not Solutions)
A typical USB-A to USB-C cable
ADB tools
MediaTek drivers
Magisk 23
The latest RFinder firmware, which can be found here:
Index of ./B1-Plus-APKs/
While there you may need to grab the latest APKs. Towards the end of this post I'll explain a bit about DMR and analog radio, this will help you understand what the B1 does and if it's worth the investment ($1,600 currently) to you.
Please be patient, it may take a couple of tries to download the firmware.
I don't see a need to change the recovery. If you have other ham radios with you, you will likely have a computer as well which can be used to reflash the ROM to the radio if need be.
First, back everything up. Files and whatnot can be backed up to SD cards, radio info is to be backed up to the cloud. Install the latest firmware (this will include the ROM) as per RFinder's instructions. It takes a little digging to find it. My B1 has the firmware I linked to, so I used that. With the latest firmware installed, shut the B1 down and either charge it or attach a fully charged battery.
Over on the G7 (you may use any phone that runs Magisk Manager 23) I extracted boot.img from the downloaded firmware. You also need to extract vbmeta and lk.bin (depending on your preferences). lk.bin can be added to clean up the boot screen. I used a blank vbmeta intended for a rooted Onn 10.1 tablet, but it's better to use the one that comes with the firmware.
Next I patched the boot.img with the Magisk Manager 23 on my rooted G7 and took note of the file name. I have several patched boot images for different devices, no need to risk flashing the wrong image and possibly turning my radiophone into a light bulb.
Then I hooked up the laptop to the phone. ADB tools are in the most basic directory I could make: c:\adb. I put the patched boot.img in there. You'll need to copy vbmeta and lk.bin as well. I disconnected the laptop from the G7 and hooked it up to the B1, then started the B1 normally. Windows 11 recognized it immediately and installed the drivers. I enabled developer options (settings->system->about phone, then tap build number several times) and enabled OEM unlocking through Developer Options.
Next I unhooked the B1 and rebooted it to the super simple MediaTek bootloader by holding power and volume UP together for a few seconds. I followed the on screen prompts to get into fastboot mode.
With the laptop and the B1 connected, I went to C:\adb on the laptop, right clicked, and opened a terminal. This may be listed as open PowerShell or command prompt depending on your version of Windows.
For the next part, we're telling certain programs to do certain things to certain partitions within the radiophone with certain files. Imagine giving someone a command: "Fastboot, please flash the boot partition with the boot.img. file." That's the flow of each command.
The first command was to verify the laptop and PC could communicate, so I typed (without quotes)
"fastboot devices"
The RFinder put a number up on the laptop screen. All good so far.
Next
"fastboot flashing unlock"
This unlocks the bootloader and frees up every bit of storage on the radio's installed ROM storage.
Next, without quotes or parentheses, I typed "fastboot flash boot (whatever Magisk named the patched boot image).img
Last was "fastboot flash vbmeta vbmeta.img"
At this point if you want to patch the lk.img file and have that nice, clean battery warning specific to the B1, patch it in a hex editor, put it into the ADB folder, and type:
"fastboot flash lk (whatever you named the patched lk.img).img
If for some reason you want to re lock the boot loader,
"fastboot flashing lock" should do it. I left mine unlocked.
Once that's done, reboot the B1. You can power cycle it or type
"fastboot reboot"
That will either get it booted to Android 9 or into a boot loop. If it boot loops, re check your work and try again. Worst case scenario you can flash the respective files from the firmware you downloaded, start with vbmeta, though!
The last step is to install Magisk Manager 23. It should recognize the Android part is rooted.
You can use a later Magisk or even a different root solution. I used 23 because it's the latest one I'm familiar with.
Now... just what exactly does this oversized, bulky piece of hardware do?
Most any radio, your cell phone included, has to connect to a central point and identify itself to be allowed to use that connection. For a cell phone, we call that a "tower", for ham radios, it's called a "repeater". Shocking idea...they both do the exact same thing: take in information and then repeat it either over the air or via physical connection (backhaul for cell, network for radio) so that other devices can receive it. Some radios can talk directly to one another without all of this.
When your radio connects to a repeater, it also sends certain information to activate that repeater. Both analog and digital modes require this, but the digital identification carries more information.
Enter DMR radio. An analog repeater has one or maybe two "channels". A DMR repeater accesses a network called Brandmeister or sometimes DMR_MARC which contains thousands of channels known as "talkgroups".
In either case, someone has to program those ID signals and the desired channels into the radio. No two repeaters are exactly the same, but someone with a lot of patience can set the radio up to automatically access each repeater on a long trip much the way a cell phone roams from tower to tower.
Most programmable two way radios have to have all this info entered at least once by hand. The B1 does it automatically.
Aside from that, there are obvious advantages to an amateur radio operator with a single device that can serve as their cell phone, their handheld radio, and possibly even their wallet. There's also an advantage to being able to simply switch out a dead battery for a charged one, the B1 is offline for perhaps a minute while this is done rather than being captive to a power bank and cable for an hour or two.
OK, post #2. I like to put my ham and GMRS call signs on my radios' boot screens, and I hate that orange mode warning, so a good place to put change that is in the lk.bin file.
Dumb skull moment #1: fastboot flash lk onn_10_lk.bin (should have flashed the B1+'s lk.img, not some bin file from a cheap tablet...oops!)
Dumb skull moment #2: fastboot reboot.
Step 3: Enjoy my new $1,800 brick. Smartphones ain't cheap!
I went through the same steps I normally would to unbrick a Walmart tablet because the chipsets are almost identical. Bob designed a next gen B1+ and added some lifesaving features to a few of them for first responders, then ran a batch or two with the better hardware but no access to US cell band 14 for the rest of us. In the end, we got a good ham radio with a solid cell phone as the front end and batteries that absolutely devastate what would normally be in the phone.
Here's the catch: the RFinder B1+ flash memory is formatted a little different than a standard MTK 6765. The scatter file used in the ROMs doesn't play nice with SP flash tool because of this. This is actually fairly common among different radio models, but before now I've had to do some soldering to repartition a handful of AnyTone units. What I did was grab a generic MTK 6765 scatter file and compare it to the B1+. I changed line numbers and memory addresses on the generic file to match the RFinder official ROM, but left the generic file structure intact. I double checked my work and it matched up. Next I loaded it into SP Flash Tool and hit download without the B1+ hooked up. It stalled where I expected it to. A quick driver update, some frustration with Windows 11 (I said the magic words a few times), then back to Windows 10 because that laptop is working still... another driver update and presto! The radio swallowed a stock lk.img faster than I wolf down steak and taters.
Another warning: on the B1+, if you need to use SP Flash Tool, only use the "download" function and untick ALL the boxes except just what you need! If you're hacking up the scatter file, one mistake can soft brick the radiophone, but if that mistake isn't on a partition you're flashing it won't matter.
Anyway, back to hackin' devices and yakkin' on the radio!
-73
ROM updating:
If you open the RFinder HAM app and go to "Advanced Settings" it may prompt you for an update. If it's updating the app itself, follow the on screen instructions.
If it's updating the ROM, follow the instructions to download the file, then STOP. Back everything up including the radio memories, then unmount any SD cards you have, power down, and remove them from the radio.
Re attach the battery to the radio and charge it fully. Once it's charged, unplug the USB and remove the radio from the cradle.
ROOTED USERS ONLY (all others skip to "ALL USERS"):
Get the radio into fastboot mode and connect a USB cable. Locate the downloaded zip file that matches the ROM you have, unzip it into a folder on your PC that's easy to find, and then use fastboot to flash *stock* files from that zip file into the radio to replace any files you've patched or modded. Specifically you'll need the boot.img and the vbmeta.img and they MUST match the ROM currently in the radio. Open a command prompt, then change to the directory where your fastboot is installed. I recommend you put the official vbmeta and boot files in this directory.
"fastboot devices" and wait for your B1+ to show up.
"fastboot flash boot boot.img" where boot.img is the official boot image that matches the one in the radio. Double check your typing, then hit enter.
"fastboot flash vbmeta vbmeta" Again, you need to be sure it's the matching official vbmeta.img. Double check typing, then hit enter.
Double check everything.
"fastboot reboot" Your B1+ will boot back into Android.
Go to Settings -> Reset Options -> Erase All Data, then read the text and hit "Reset Phone".
Alternately you can reset from the B1+'s Recovery Menu (power +vol down IIRC, if not try power +vol up).
Sideload the Magisk app. Again, I used 23, which is older but it's the one I understand best.
ALL USERS:
Plug in a live USB cable (preferably to a USB power outlet, not a computer).
Go to settings -> System -> About Phone -> System Upgrade. Click that and choose update from local storage, then choose the update file the radio downloaded or that you received from the customer support team. Follow the instructions. The radio will shut down. You may have to power it up manually. It'll go into a mode that looks like recovery, then it'll say it's updating. If something isn't right the update will abort and generate an error message. If everything is OK the update takes around five minutes. The first reboot hangs on the tower splash screen for a while, so please be patient!
Non rooted users are done. Hooray!
ROOTED USERS:
Once the update is finished, go to your fastboot folder on the PC and replace vbmeta with the empty one you used with the old *rooted* boot.img.
Unpack the new update file, copy it to the radio's internal storage, and use Magisk to patch it. Copy the patched file back to your PC, preferably into the folder with fastboot.
Get the radio into fastboot mode and connect it to your PC with a USB cable.
Use fastboot the same way you did above except this time, flash the patched boot.img and the empty vbmeta.img.
Double check everything you just flashed, then type "fastboot reboot" and hit Enter.
Once the radio loads up, download a root verification app and run it. You should get a superuser request. Hit grant, read the root checker output, and voila!
Next find the RFinder HAM apk and install it. Ideally you should have a backup of it, if not, get it from RFinder.wiki.
Make any other mods you need to make, then reinstall any SIM and SD cards, update the RFinder HAM and IMEI apps if necessary, restore your memories into the RFinder HAM app. Reload your other apps, restore any backups they have, re grant root access as needed, and you're done.
B1 Classic rooting.
If you got hold of one of these, you're in for a rough ride. If it's got the latest update, version 25, you have your work cut out for you. The best way to get hold of the ROM is from Bob Greenberg with RFinder support. RFinder has an official and an unofficial Facebook group and a Zoom channel. Bob is proactive in contacting people who post with issues in either of those groups. He has a number of beta roms available as well as beta RFinder software. Serious, go sign up and ask.
If you're NOT on 25 or you'd care to chat via Zoom, things are a lot easier.
I started with a B1 classic from a silent key That operator was part of a Jeep club out of Oregon and for whatever reason they sold off his B1 Classic as part of the estate.. That's a term of respect for a ham operator who has passed on. Obviously if the person had a startup PIN on the device, it soft bricks when hey pass on unless someone knows it. You also have the FRP lock to deal with, however, this operator had either logged out of Google before he passed or never logged in.
Here's what I did:
To remove the startup lock, shut the unit off and remove the battery. Cherge the battery it its cradle (the B1 Classic will not charge via USB). Reinstall the battery, press and hold "Power" and Volume down, release them after a few seconds. This gets you to recovery. Factory reset the radiophone from here.
Once the B1 restarts, head over to RFinder.wiki and get the latest RFinder ham apk. Install it, go into settings, and Advanced Support. If you're not on version 25, you'll get a notice to update an an option to download a ROM. Do both, and save the ROM file whe n you're finished.
Unzip the ROM file and locate the boot.img and the scatter.txt. You know what to do with the boot imagw: get it onto a device that has the Magisk apk, rooted or not, and patch it. Put it back into the folder with the unzipped ROM file.
Shut down the B1 Classic and remove the battery. Unplug the USB cable from your PC.
Next grab a scatter file for a stock MTK 6763. Go through it and the scatter file from RFinder, match up the start points of all the partitions and as man of the sizes as you can. You'll need to delete one of the partitions in the stock file and do all of your edits on the *stock* MTK file, not the RFinder one. Chenge the "is download" value on ALL partitions except the Preloader and the Boot to FALSE. Save that in the unzipped ROM folder.
Now grab SP Flash tools. The B1's bootloader can be unlocked, but it's difficult and I happen to like my data. Open SP Flash tools (unzip, find flashtool.exe and double click it). Hit "browse" and go to the unzipped ROM folder, then click on your scatter file. If everything went well, you should have only two lines showing on the download screen: Preloader and Boot.
UNDER NO CIRCUMSTANCES ARE YOU TO MODIFY THE PRELOADER! Uncheck that option. You have to have the line populated or SP Flash Tools will throw an error, but you MUST UNCHECK IT. If the two lines don't populate, find the respective images in the unzipped rom. Click the empty line, then find the image and click that. Ensure the Boot line is checked, preloader unchecked, double check your work, then hit "download".
Grab the B1, plug the loose USB cable into it. Press and hold Volume Up and Volume Down while you plug the other end of the USB cable into your computer where SP Flash Tools is waiting. You do not need a battery. SP flash Tools will connect to the B1, the progress bar will turn RED, then it will verify your work and attempt to download your changes to the B1. If that's successful, the bar will turn yellow. When it's finished, it'll notify you of the results.
DO NOT FORMAT ANYTHING IF IT ASKS YOU TO. That's an error which needs addressed, so fix it and try again.
Unplug the cable, attach the battery, and boot the B1. You will not need to reinstall anything save for an SU manager (Magisk is fine) and a root checker.
Keep in mind that we didn't touch the bootloader, it is still LOCKED. I was all over it trying to unlock it to no avail, and I didn't care to dig out my old Toughbook for Ubuntu. Not everyone has an old Toughbook with Ubuntu on it anyway, you may be on Windoze.
I strongly suspect this method will work for future updates to the other B1 models as well, and since we're not fooling around with the bootloader, no data will be lost. Runbo puts out quit a few ROM updates for their stuff (yes, Runbo) so those who own the newer devices will be re rooting a time or two.
E81 owners: if these methods work, please let us know! Or if you flashed a B1 to an E81 or vice vera, let us know how that went.