Related
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
dalviking said:
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
Click to expand...
Click to collapse
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Extentho said:
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Click to expand...
Click to collapse
Thanks a lot Extentho for your feedback.
I've already tried your fair suggestion: unfortunately, I'm stuck at the end of sideloading the signed .zip.
In fact, I see on screen logs that it's applying the update "unconditionally" (that sounds good), but nevertheless, when finished it returns "xfer: 1.00x" on PC shell and in recovery menu, on device.
Now, either if I reboot or power down and boot it again, the result is the same: still bootloop-ing.
Of course, at any other attempts leveraging on administrative privilege, it says that "device is locked", including those done through the shell tool.
Some excerpts from my last launched commands:
c:\_APP\CM>adb devices
List of devices attached
51f8941d sideload
c:\_APP\CM>adb shell
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb root
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
51f8941d sideload
c:\_APP\CM>adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip
Total xfer: 1.00x
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
my zuk z1 stuck to bootloop,
and android debugging is disabled.
phone can not detecting in fastboot mode.
please help.
Extentho said:
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
Click to expand...
Click to collapse
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
dalviking said:
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
Click to expand...
Click to collapse
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Extentho said:
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Click to expand...
Click to collapse
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
dalviking said:
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
Click to expand...
Click to collapse
Try to post some pics about the troubles you encounter. If we receive a solution, this may be helpful for all of us in the future. Now, exactly, what can you acces on phone(recovery, fastboot, )?
Also, check varios threads from other phones with the same problems(one plus one, lg , htc) ,etc. Find a solved situation like yours, and we may adapt that solution to you
Hi guys,
Just to close this topic.
I was finally able to install the ZUI ROM through the QFIL program.
It's a little bit tricky, due to the fact that it is strongly suggested:
- to use a Windows 7 machine started without Signature Enforcement enabled;
- to start QFIL (admin mode) and be prepared with all needed files loaded in its GUI;
- to power off the phone, then, while pressing volume up button, inserting the USB cable, attached (better if) on a 2.0 port to PC;
- to be fast pressing "Download" button on QFIL program.
After that, I unlocked the bootloader and performed a lot of alternative recovery process.
So, I installed on the device:
- ZUI ROM
- Cyanogen OS convert from ZUI ROM
- Cyanogen OS last updated ROM
- CyanogenMod 12.1 last nightly ROM
- CyanogenMod 13.0 last nightly ROM
and the winner is...
...
...
...
... none of the above.
Each time the very same behaviour: bootloop. So, my last conclusion is: hardware failure (I guess wi-fi module).
I give up.
But for anyone searching a safe way to unlock a bootloader without accessing to developer options: the QFIL method works like a charm (once installed properly).
Thanks for support.
Messed my zuk z1
I tried to flash stock room in my zuk z1 , I downloaded Qualcomm file for the ROM and installed the required in my laptop,I wiped all data in my phone using TWRP .though my power button is not working I used tool kit to reboot my phone by connecting into fast boot mode,here comes the prob by mistake I entered the wrong command which locks my bootloader .I don't know what to do...help me.....
Hey everyone, think its a bit sad that we dont got our own phone section since ShotX/7i and the regular 7 doesnt share the same cpu architecture so forgive me for cluttering down but just wanted to try and help our fellow honor comrades
The files to do this is taken from the chinese huawei forum (http://club.huawei.com/thread-5761110-1-1.html) and thus I take no credit for the files, im merely making a english guide with chinese files to hopefully spur some development.
The root itself was made for Honor 7i which is the asian market version (I believe?) but ShotX is the same phone but for international market (with LTE 800Mhz band, not sure if there are any other differences) and root was performed and confirmed working by me on my ShotX with Lollipop 5.1.1/B130 firmware so no guarantes if it will work on other firmwares. Im also not responsible if you brick your phone or it catches on fire etc.
First you need to unlock your bootloader
and to do so you will first need to turn on the "allow bootloader oem unlock" so enter settings, about phone, and then press build number 10 times to activate "developer mode".
Go back one step into main settings and the open developer settings, find and enable "allow bootloader oem unlock" (if you have fingerprint or any other code activated then it will ask you for that code) and while you are in here make sure to click "enable usb debugging" aswell.
You will also need a bootloader unlock code from huaweis site by filling out the necessary information on this page http://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
Product model: HUAWEI ATH-UL01 (settings->about phone->model number)
Product serial number: EGQ7Nxxxxxxxxxxx (settings->about phone->Status->Serial number)
Product IMEI: xxxxxxxxxxxxxxx (*#06# IMEI1 or settings->about phone->Status->IMEI1)
Product ID: xxxxxxxx (*#*#1357946#*#*)
So once youve got the code, make sure to write it down on a safe place, next you need adb toolkit. May I recommend Minimal ADB? http://forum.xda-developers.com/showthread.php?t=2317790
Now when you´ve come this far, remember that as soon as you unlock your bootloader, the phone will factory reset and you will loose any data and settings made unless you make a backup before
Insert usb data cable into pc and phone, open command prompt and be in your adb installation directory.
Start with typing "adb devices" to see if your phone is detected and make sure to check on your phone when it asks for permission that you allow your pc. I was running windows 10 x64 when I rooted my phone and I didnt need any driver but your mileage may vary if on w7 or w8. Remember to use "adb kill-server" if you experience issues when trying to connect phone with adb.
If phone is detected then you should get something like
Code:
EGQ7Nxxxxxxxxxxx device
Then all is good and you can type
adb reboot bootloader
Now to check if phone still is with us you type
fastboot devices and you should see something like
Code:
8b0dd496 fastboot
If you are still with us then type fastboot oem unlock xxxxxxxxxxxxxxxx where the xxxx´es represent your bootloader unlock code which you should have retrieved earlier from huaweis site.
To confirm that your bootloader is unlocked, simply type fastboot oem get-bootinfo and you should see
Code:
(bootloader) Bootloader Lock State: UNLOCKED
Congrats! Now youre ready to root the phone
If you recently unlocked bootloader then you need to activate developer settings again and turn on usb debugging aswell.
Download the files below
https://mega.nz/#!BsQiiYpL!xVwbyHTRsVGFsO6LpJacxP64gFrOlCNTRHTI1-vdLLw TWRP install program
https://mega.nz/#!9hQi2I7A!JX121sJ2vChMuxrx1puxf-L1rP9LSPaJW-JnqvEAzIg Root
Put the EMUI3.1 Android 5.1 ROOT补丁（不要双清不要解压.zip file somewhere on your phones memory storage where you can find it.
Unzip the 荣耀7i TWRP recovery.zip and open it up and then you press the second button which says TWRP REC and it should flash twrp. Power off phone and then press vol+ and power where you keep pressing vol+ but let go off power as soon as screen is lit and you should be in recovery in a bit. If you still got the default huawei recovery then redo the procedure (I pressed TWRP REC at first but didnt see any twrp installed so I then just pressed REC just to be disapointed again but 3rd time with TWRP REC it worked so not sure what goes on but just so you know if you also fail to get TWRP installed)
Once youre in twrp you will be greeted with chinese again but buttons are located on same spots so just compare it to a english twrp image https://en.wikipedia.org/wiki/TWRP#/media/File:TWRP_2.7.0.0.png
Just press top left button and select the root file you should have putted on your phone earlier and flash it, when its done just hold the physical power button to reset incase you´re unsure of the reboot button and you should be good to go
Grats on your rooted phone, after some cleanup (possible with root) this phone is flying like never before
Some highly recommended root apps
Rom toolbox lite, so you can flash roms/mods without knowing your way in the chinese twrp and uninstall apps etc
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=sv
Kernel adiutor, great for getting a bit more performance out of the phone by tweaking cpu and gpu speed
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=sv
And lastly the great snapdragon camera which is pretty fast and nice to use which you need to flash in twrp (or with rom toolbox)
http://forum.xda-developers.com/showpost.php?p=64410821&postcount=44
Its for one+ x but it works as expected for our ShotX/7i aswell (Obvisually dont use this if youre on a regular Honor 7 device since it doesnt have snapdragon processor)
thank you very much , I'll be trying my XShot
Theres a translated twrp now for those that wants
http://forum.xda-developers.com/honor-7/development/unsupported-twrp-honor-7i-shotx-t3323072
-help twrp bootloop
hey i rooted my shot x and worked fine, but then i did a factory reset and now its on twrp bootloop. any ideas to fix this? do you have a rom for this phone? because im trying to donwload one but its slow as f**
I think if i install a rom with twrp it will work but not sure
help pls
TY!
lucaspsara said:
hey i rooted my shot x and worked fine, but then i did a factory reset and now its on twrp bootloop. any ideas to fix this? do you have a rom for this phone? because im trying to donwload one but its slow as f**
I think if i install a rom with twrp it will work but not sure
help pls
TY!
Click to expand...
Click to collapse
Sorry, sold my shot x as there was so little dev interest. The only moderate source of files for it was on the chinese huawei forums :/
something changed? still no intrested by developers?
Please help me. Honor ShotX flash tool firmware.
ATH-UL01-C185B310
Android version 6.0.1 firmware.
Please help me.
Did u root your shotx?
tndb said:
Sorry, sold my shot x as there was so little dev interest. The only moderate source of files for it was on the chinese huawei forums :/
Click to expand...
Click to collapse
Did you tried russian forums? 4pda or others, often they have good devs there for some devices,which are not supported here on XDA.
Anyone who can't get to bootloader unlock site after login. Follow this [GUIDE] :
https://forum.xda-developers.com/ge...nor-bootloader-unlock-code-t3441130?nocache=1
This helped me. Hope you also get the help.
Credits to : Thor
Is there any solution for ShotX with android 6.0?
Please upload android 6.0.1 rooted room
Hello XDA
As title say, I 'm going share my experience in this thread.
History
I purchased this device almost 8 month back.Purchased from a local store.Was very smooth and i was satisfied with the performance.Battery was good.Got regular update and these updates are from google,so why not install it,right?Then this Android N came,and i was so happy.7.0.0 was good.Then the nightmare 7.1.2 came.Phone started to lag continuously,Battery drained too much.But I was like Okay.May be this will fixed in new update.Then suddenly one day my phone was stuck.Not booting.Stucked at Google.I understood that phone already booted and fingerprint was too working but it showed nothing on display just black light.I was afraid as i didn't purchase it from Google Play or any authorized seller.So no warranty or chance of having replacement.So I started searching about this issue and found not only me many people are facing this.But there are no proper guideline or solving this issue.Tried everything and ended up with Locked Bootloader Irony!
Journey
As i never try to mess with my phone because it was Nexus 5x! So i never touch OEM or try to unlock the bootloader.So i tried to access stock recovery,But Alas! in recovery Volume up and down wasn't working.So I couldn't wipe or factory reset.So Now ended up with :
1.Locked Bootloader
2.Locked OEM
3.Recovery Stuck
Googled and found many solutions but none of them came to solve my issue.So i thought why not flash stock rom.But HOW! Cause fastboot only work with unlocked bootloader.And you can't unlock bootloader when your OEM is locked and you can't unlock it with fastboot.It can be only unlocked from developer option only.GOD!
Now I have only 2 options left:
1.Fastboot mod where no functions working
2.Download Mod (This will save you)
Now fastboot option is out and only download mod option is available.So what can i do with Download Mod?
LGUP TOOL helped me.Downloaded a tot file for Global version (LGH791) and flashed it and stucked at google logo and in recovery too.But next time i flashed the same file in a different way.Ok here it is:
1.Drivers are important here.I'm using windows 10.I have adb and fastboot and Lg drivers.Workplace okay.
2.Opened device manager and change the com port of Android phone 3 to 41. Port Changed!
3.Connected my phone to pc using 3rd party cable (Careful here,try to use original cable.) and entered into download mod and.
4.Opened LGUP Tool ,checked REFURBISHED mod,checked BIN file and select the tot file downloaded before.And quicky close it.(No need to click start)
5.Then again opened lg tool and click start.(BIN Checked and it showed the previously selected tot file).No need add anything new this time,just open and click START.
6.Rebooted and again stucked at Google screen.But wait! recovery is working.Pressing and holding volume up button for a while then a android logo with red cross inside will come up.Now holding power button and volume down button at the same time,Recovery will show and menu is working.Great!
7.Now Wiped cache and factory reset.And after that selected Apply update from Adb sideload
8.My device was connected to pc from the beginning,right? Now i downloaded a file previously called bullhead-ota-opp2.170420.019-c449d2bb.zip from Google Nexus 5x OTA update page.
9.In Adb folder,copied the file and named it ota.zip.Opened a command prompt using shift+right click in the folder.Phone was on Adb sideload mode.Typing this command adb sideload ota.zip
10.This took more than 8-9 minutes to finish.After flashing and phone rebooted.WOW
11.Couldn't believe my eyes.The OTA update was about Android O.I quickly enabled the developer menu and made oem unlcocked and usb debugging on.Boot into bootloader and unlock bootloader with this command fastboot flashing unlock
12.Now bootloader is unlocked and i flashed TWRP recovery for future need.
13.Rebooted the phone and after using for 1 minute the phone freezed again
14.This is the end of the story for today.
Planning
I'm thinking the OTA update was the problem.Now I'm downloading 6.0.1 version.And will do a clean install.Let's see what happens next.
Any kind of help is appreciated.If you think there is something i'm missing here then please suggest.
And Thanks to XDA.I got all these helps from here.Will update the post tomorrow.
You downloaded Android O Developer Preview. Final OTAs are here:
https://developers.google.com/android/ota
Just try flashing newest Factory Image via fastboot, but don't forget to flash TWRP back:
https://developers.google.com/android/images
TBH I NEVER thought this phone will be dead by hardware failure all of a sudden, I dont mind another few hundreds bucks but the problem now is the fking data within it.
Cant even pass google logo if you choose Recovery Mode
GG LG, well played
I have a 16gb variant dead....same issue like urs .....can i use the same lgh791 tot file?... in fastboot it says lgh791 16gb
usefully
usefully
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
same of my expirience, flash 4CoreOreo..
my nexus 5x now is fully working
the_uker said:
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
Click to expand...
Click to collapse
I suppose that makes sense. Then again, when an instruction is telling you to boot into download mod.....using common sense I'm gonna understand that's a typo and they meant download mode. But you're right, for some folks that may be a bit of a challenge. Common sense isn't as common as it was when I was young.
And the links?
I'm brazilian and i'm having a hard time to find the links to download stuff. Mine is dead and bootloader blocked. The tutorial seems to work but i can't understand well
Interesting. Thanks
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.
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.