Related
So, I've been banging my head against the wall for a few days now, and though I usually don't post questions (90% of the time I find the answer somewhere on the interwebs) I'm a bit stuck.
So I'm trying to get used to creating my own boot images, and have found the article android-dls article among others very helpful in understanding everything (would post the link, but can't yet)
It was easy enough to find the boot image on the Fire, and I have been using the unpack_bootimg.pl to unpack the boot image, then make the necessary changes, and mkbootfs to pack up the ramdisk. Everything goes swimmingly.
The problem arises when using fastboot to boot the new boot image using the command below:
fastboot boot boot.img-kernel.gz boot.img-ramdisk.cpio.gz
It loads it to the Fire fine, but never boots. My guess is it has something to do with offsets, but to be honest, it's a bit of a blind guess. I have also attempted to repackage the boot image into a testboot.img with the same results. I've even tried just unpacking an re-packing the known good image thats already there, without changes.
Also, not sure if this is relevant information, but mkbootfs and mkbootimg was compiled in OS X (10.6.8 for those that care) directly from the android 4.0.3 source.
Does any one have any suggestions on what to try next? Or even better, any additional articles, threads, etc. that I may have missed. Any help would be appreciated.
Oh, forgot to mention, I also have the firefirefire bootloader installed (1.2) and TWRP. Don't think it matters though.
This may not apply as I do not own a KF...
Have you ever successfully used fastboot in that manner with the KF? Any kernel I mean...
I was never able to use fastboot like that with my inspire 4g... but could use it to flash the very same image quite successfully.
Dont know if that helps or not...
I've found that those scripts do not play nicely with the Fire's boot images for whatever reason, and repacking with them renders all of my images unbootable as well. I've ended up using dsixda's ROM kitchen just for the boot image scripts because those work fine. I'm not entirely sure where the disconnect is on the perl scripts, but I haven't looked at them truly extensively.
Unpacking and re-packing boot images
gumbi2400,
Have you tried loading another boot.img/rom and going back to the one you have edited? I am only asking for my own stupidity. with your post it has my mind going places, well it should not go just yet in the Kindle. I am pretty sure it not much different then myself building GhostBSD. Let me know please!
Thanks,
JohninLex
Changed the Boot Logo and now stuck at boot
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
wayoung said:
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
Click to expand...
Click to collapse
you could try to get to twrp by issuing:
fastboot oem idme bootmode 5001
fastboot reboot
in the case it says <waiting for device> power off the kf by holding pwr ~20sec
power on again - at some point the command gets finished
power off and on again
once in twrp you have adb available and can copy a good file over the bad one
take care of the permissions !
or just restore a backup or flash a new rom
maybe you have to check your drivers in device manager:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Sorry it took me so long to reply, got distracted by other modding projects.
@JohninLex:
I actually tried simply unpacking and re-packing the stock image that was already on there, just to make sure I was packing it back properly, but got no love.
@eldarerathis:
I think I had stumbled across the ROM Kitchen previously, but wasn't sure if it was what I was looking for. I'm fairly new to this low level of messing with Android, I have a tad bit of experience with Linux proper, but I know things can get pretty murky. I may end up ripping the scripts apart and seeing whats actually in there. Thanks for the tip!
Life is busy right now, and I haven't gotten a chance to mess around with modding my Kindle more, may be time to start again.
I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!
shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.
I have a problem
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.
dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.
Just uninstall the kindle driver and replace it with the generic fastboot one
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.
there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?
hw = hardware?
MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.
Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?
uhg
Facepalm
just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608
I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?
I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.
All instructions were performed on an Atoto A6 A62721P. There may be variations with other models.
What you will need:
Mediatek VCOM drivers ---> https://mtkusballdriver.com/download/mtk-usb-v1-0-8
SP Flash Tool for Mediatek Devices. ---> https://drive.google.com/file/d/1pkJ6lXKZ0IBAljHw3f0N7eeU9f4iW6b-/view
MTK Droid Tools with mod by Bovirus ---> https://forum.xda-developers.com/attachment.php?attachmentid=4458732&d=1522117513 (has added info to recognize MT8127) Original file is from---> https://forum.xda-developers.com/showthread.php?t=2160490
Notepad++ ---> https://notepad-plus-plus.org/download/v7.5.5.html
MT8127 Scatter File ---> https://forum.xda-developers.com/attachment.php?attachmentid=4437810&d=15202295
(Most of this can be executed in linux, there is an SP Flash Tools, but I couldn't find an MTK Droid tools version)
To connect to the unit you need a male to male usb cable or mini male to full male usb adapter and usb cable.
Using the SP Flash tool requires full reboots. Since I didn't have the unit installed in a vehicle, I simply made up a 12 volt cord with two
light switches, one switch to 12V constant wire(yellow) and feeding other switch, which then goes to ACC wire(red).
You can also use the pull down and reboot, you just have to get the timing for plugging in the usb cable.
Connection is made to the quick charge usb port. You will want to disconnect and reconnect at that port, not at the computer.
All processes assume you have Developer options enabled, with OEM unlocking and USB debugging enabled. Also allow install from unknown sources
enabled in Security.
Backup and Recovery with SP Flash Tools and MTK Droid tools
With the unit turned off and not connected, open the sp flash tool folder and run sp flash tool as Admin.
For the Scatter-loading File, click choose and select the downloaded scatter file, MT8127_Android_scatter.txt.
Now click the Readback Tab.
Select add, to add an entry to the list below. Double click the the entry. You can make a folder to save it in, but leave the
name ROM_0.
After selecting save, you will get the Readback block start address screen. Type will be Hex, Region - EMMC_USER.
Start address will be left at 0x0000000000000000.
The length we can get from the scatter file. Open the scatter file in Notepad++.
The scatter file is your partition table along with other info. You can use the start address for the cache, so that will backup everything
to that point. The address is 0x00000000D4000000.
Select ok and then make sure the box on the left for the entry you created is checked.
Now click Readback.
With Sd Flash Tool Readback running, turn on both constant and acc to the unit.
Connect the usb cable to quickcharge port in four to five seconds after powering.
If you are too late it won't work and you will have to reboot. If you are too early it won't work either. If the Atoto screen appears on the
unit, you need to try again.
Once you connect, the bottom process bar in SP tools will first turn red, and then you will see the process as it is backing up your system
in blue.
I was having issues with the unit timing out before completing. I found that turning off the power to the ACC after about two minutes,
and then back on in two minutes, would keep the process from timing out. Just keep doing that until it finishes.
Once it has finished, disconnect and restart the unit. You can close the message that it finished in SP Flash.
Now you want to run MTK Droid tools downloaded from here, as admin.
When the unit is up and running, and MTK Droid tools up, connnect the usb to the unit.
In a few seconds, MTK Droid tools should recognize the unit and display some info. When that happens, click the "root.backup.recovery" tab.
Now you want to select "To process file ROM_ from Flash Tool".
Now go to the folder where you saved the ROM_0 and select it. This cut the rom into the actual partitions, making it flashable.
When asked "To make CWM recovery Automatically" select no, and then it will ask for an optional file to use, just click cancel.
When it has finished, go into the MTK Droid Tools folder, and in the backups folder, will be a folder with all of the partitions.
You will want to change the name of factory_NONmodified_recovery.img to just recovery.img.
To restore, run SP flash tool, and select the the scatter file from the backup folder. Always make sure that the Preloader is never checked.
Typically Preloader and Uboot are not checked, but make sure anyway. If the Preloader if erased, or accidently written over, you will have hard
bricked your device. Other mediatek devices(mainly phones) are able to recover from this by either booting into a hidden metamode, or by
finding a test point on the board marked KCOLO or COLO and grounding it. I have not found either of these methods to be available.
So don't mess with the preloader.
Flashing is the same method as before. When you see all the partitions loaded if SP Flash tool, click Download.
Power up the unit and connect the usb in four to five seconds. Turn ACC power on and off to keep it from timing out.
If you get an error in sp flash that it is the wrong scatter file, you should replace the scatter file in you backup folder with the one
downloaded from the link above.
Flashing a partition, such as recovery is the same process, you could simply put the recovery in a folder with the scatter file and then
select that in scatter in SP flash tool. (Flashing a custom recovery requires the system to be rooted)
Rooting
The easiest way to gain root I found, was by running KingOroot in windows, connected to usb. Once KingO has root, you have to replace KingOroot
with SuperSu. The first time, I replace files manually through ADB with root privileges.(Could also use ES File Exploer)
But an easier way is once KingOroot has root, do not reboot. Install SuperSU and then Run SuperSU, and when it fails, run it again. Eventually you will
see a prompt that SuperSU is asking KingOroot for root privileges. Grant it and run it again. When it fails, reboot the system. SuperSU should now have
root. Make sure kingoroot is gone. When you make SuperSU a system app, the only way to lose it is by unrooting in the SuperSU options.
If you got this far, you might have realized that a custom recovery is not exactly necessary, due to the SP Flash Tool. Once rooted, you could use Flashfire for apps
that need to be flashed, such as Xposed. However I did compile a TWRP recovery from Omnirom source using ---> https://forum.xda-developers.com/showthread.php?t=2798257
There is an issue with it that it keeps going to lock screen, you just have to keep swiping to unlock.(Was able to 'cut out' the lock screen issue, no longer locking)But everything seems to be functioning.
You can get the custom TWRP recovery here ---> https://drive.google.com/open?id=1k_9rrG0_4dkw45cetUzbq0m0Q3VgZ7P1
I don't credit take this, there is tons of info on Mediatek devices on here, just do a search. I just took the info and found what works for this device.
Some other info: Fastboot is not enabled on this device. If you use adb reboot bootloader, You will see a fastboot mode screen for a moment, until the unit automatically reboots. I was able to get the screen to last for a while by either turning off power to the ACC or disconnecting and reconnecting the USB. Even though the screen remained on for a bit, there is no way to connect. You can also get to an odd Recovery like menu if you do adb reboot sideload and wait for it to timeout.
Could not find a way to connect to or control that either. And if you flash a custom recovery without having root, it will go to a factory reset.
My biggest issue with this unit is Atoto's Gui, I have been trying Nova Launcher and CarWebGuru, both seem to be much better options. After looking at some of the other units stock setup, I think this has to be one of the worst. Maybe one day atoto will decide to update it.
Thats really my only major gripe. There is the issue with radio being attached audio device, but it seems to be with a lot of these units.
Hope this helps anyone interested and gain's some interest in this unit.
Awesome! Thanks for this. I will have to look in to this this weekend.
Stabone00, you never disappoint.
Thanks so much as always.
stabone00 said:
Rooting
The easiest way to gain root I found, was by running KingOroot in windows, connected to usb. Once KingO has root, you have to replace KingOroot
with SuperSu. The first time, I replace files manually through ADB with root privileges.(Could also use ES File Exploer)
But an easier way is once KingOroot has root, do not reboot. Install SuperSU and then Run SuperSU, and when it fails, run it again. Eventually you will
see a prompt that SuperSU is asking KingOroot for root privileges. Grant it and run it again. When it fails, reboot the system. SuperSU should now have
root. Make sure kingoroot is gone. When you make SuperSU a system app, the only way to lose it is by unrooting in the SuperSU options.
Click to expand...
Click to collapse
Well, after some trial and error, I have this thing rooted, permanently! Here is how it went for me...
I hooked up the head unit via the USB B (Fast charge) cable.
Then ran KingoRoot on the computer and hit the root device button and once the head unit showed I has root via SuperUser (The KingoRoot SU app), I then installed SuperSU v2.79 (v2.82 WILL NOT work!!!! It will complain that there is already and SU binary or some junk and wont even let the app start so its a no go).
Now open SuperSU aand let it run, attempting to update the SU Binary. Just let it run for a while, took mine almost 5 minutes, then when the SuperUser prompt pops up, grant/allow SuperSU root access. If it fails and the root access prompt doesnt pop up, just close and reopen SuperSU again to try and update the SU binary until it asked for root permission. It will always fail so dont worry. Once it does and you allow/grant SuperSU permission via SuperUser, try to update the binary again in SuperSU. It will fail but dont worry, thats normal.
Next, uninstall SuperUser (The KingoRoot SU app), then reboot your head unit. Once you have rebooted, open root checker and the SuperSU prompt should pop up asking for permission and click allow and should show you have root. Now, open SuperSU and it go to settings and change it to a system app. Once its done changing it to a system app, SuperSU will just close and SuperSU will be gone from your app drawer until you reboot. Once you reboot, SuperSU will be back in your app drawer. Thats all there is to it. Enjoy having permanent root access. I have rebooted my device at least 10 times and still have root access. Happy camper here. Thanks for the tips on rooting this thing. I was going crazy the first time I tried a couple weeks ago trying to keep it rooted.
I completely forgot about the issue with supersu 2.82. When I was first trying to root, I downloaded it from the play store. When I installed it manually I used the zip of 2.79 which I already had. I even tried installing 2.82 manually, later, but it never worked.
i'm a little lost with this
The scatter file is your partition table along with other info. You can use the start address for the cache, so that will backup everything
to that point. The address is 0x00000000D4000000.
Select ok and then make sure the box on the left for the entry you created is checked.
this is whats shown on scatter file.
partition_index: SYS26
partition_name: CACHE
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0xD4000000
physical_start_addr: 0xD4000000
partition_size: 0x10000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
what do i change??
thanks again for any info.
scoolro
scoolro said:
i'm a little lost with this
The scatter file is your partition table along with other info. You can use the start address for the cache, so that will backup everything
to that point. The address is 0x00000000D4000000.
Select ok and then make sure the box on the left for the entry you created is checked.
this is whats shown on scatter file.
partition_index: SYS26
partition_name: CACHE
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0xD4000000
physical_start_addr: 0xD4000000
partition_size: 0x10000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
what do i change??
thanks again for any info.
scoolro
Click to expand...
Click to collapse
When you load the scatter file into SP Flash tool, it brings up the list under the Download tab. There you can see that the addresses are listed with all sixteen numbers, so that's that's what I used for the readback.
where can i get
MTK Droid Tools with mod by Bovirus??
the link is down
Thanks Again
Scoolro
Didn't know it wasn't working.
Thanks again Stabone,
I took care of the back up and recovery partitons on the mtk tools.
Now how do i flash twrp that i download from above into stereo do i use flashfire and how do you access recovery on stereo when installed in car??
again as always thanks for all the help. appreciate it so much.
scoolro
stabone00 said:
Didn't know it wasn't working.
Click to expand...
Click to collapse
i beleive i inserted twrp but i do not know how to get into recover mode, can you let me know?
many thanks as always,
scoolro
adb reboot recovery
But from the system, lots of apps will reboot to recovery, Twrp app, flashfire, etc... or just search the play store for reboot recovery.
stabone00 said:
adb reboot recovery
But from the system, lots of apps will reboot to recovery, Twrp app, flashfire, etc... or just search the play store for reboot recovery.
Click to expand...
Click to collapse
oh understand now.
was hoping to not use a computer to the stereo when i install in my car. i was hoping to hit some buttons to activate twrp on stereo when it is installed, just in case i mess something up and want to restore stereo.
activate restore as i do like my phone.
any info on installing xposed??
thanks stabone once again.
You could reboot to recovery from xposed. You can install xposed installer 3.1.5. You need to flash version 89. If you have the Twrp recovery installed, you could flash it from there.
i hope i'm not asking way too many questions for you, if i am i appologize but just installed xposed
and its working. as always you helped so much with my stereo. Im sure everyone here appreciates your wisdom.
thanks stabone,
scoolro
Not a problem.
hello stabone, thanks for all your great posts and not going postal on all the newb questions. I've not posted much here, but I have a hopefully simple question for everyone. I have 3 ATOTO units, one bricked (hardware accident, not software brick) and one I just received which is the 1/16GB model with PB. This latest unit is a gift for stepdad, and I picked up the PB mainly because of the radio app thing and his eyesight being poor, his wrangler has no SWC so I figured when he needed to turn down volume quickly he would appreciate the buttons. After playing with the unit I really dont like the PB, the recess is too deep and it doesn't have that nice thick glass look like the touch models, not to mention they actually fixed the radio app issue. Anyways...… So I swapped the screens from the touch only to the PB unit, it fired right up and the touch is calibrated perfect. My issue is, the touch buttons on left side, I only get response from volume down button, which equates to volume up, the power/back/vol.up are unresponsive. Obviously, in my mind, the MCU is loaded for the other panel. I have a working touch model as well, can I simply pull the MCU file off the touch model and load it onto the PB model? I only ask because I have a couple other bricked Sofia units and really nervous about doing ANYTHING to these units anymore. With the MCU update happening parallel to the firmware update, I am unsure how to initiate only an MCU load and which exact file I need to pull. Thanks for any direction, I appreciate anything.
Just to add, I have an APK with the name com.zhonghong.mcu_20170527 . could it be that easy??
I haven't messed around with the mcu too much. You could try but should probably make a backup with the sp flash tool first. The unit that you said is bricked, is the preloader still accessible? You would be able to connect with sp flash tool and re-flash if it is.
Tthanks so much for your reply, I forgot to respond last week. It all ended up being a waste of time anyhow, because my stepfather preferred the physical buttons..........
Now, I'm plagued again. My wifes unit, got the update from ATOTO website which fixes the radio app opening thingy, but it killed the mic, internal or external the mic is totally unresponsive. I didn't even play with the mic on that other unit, so ill need to check it next time I'm over there. Did this happen to everyone, or is my unit having another issue? I've tried rerunning the update package a couple times as well as resets.
stabone00 said:
All instructions were performed on an Atoto A6 A62721P. There may be variations with other models.
What you will need:
Mediatek VCOM drivers ---> https://mtkusballdriver.com/download/mtk-usb-v1-0-8
SP Flash Tool for Mediatek Devices. ---> https://drive.google.com/file/d/1pkJ6lXKZ0IBAljHw3f0N7eeU9f4iW6b-/view
MTK Droid Tools with mod by Bovirus ---> https://forum.xda-developers.com/attachment.php?attachmentid=4458732&d=1522117513 (has added info to recognize MT8127) Original file is from---> https://forum.xda-developers.com/showthread.php?t=2160490
Notepad++ ---> https://notepad-plus-plus.org/download/v7.5.5.html
MT8127 Scatter File ---> https://forum.xda-developers.com/attachment.php?attachmentid=4437810&d=15202295
(Most of this can be executed in linux, there is an SP Flash Tools, but I couldn't find an MTK Droid tools version)
To connect to the unit you need a male to male usb cable or mini male to full male usb adapter and usb cable.
Using the SP Flash tool requires full reboots. Since I didn't have the unit installed in a vehicle, I simply made up a 12 volt cord with two
light switches, one switch to 12V constant wire(yellow) and feeding other switch, which then goes to ACC wire(red).
You can also use the pull down and reboot, you just have to get the timing for plugging in the usb cable.
Connection is made to the quick charge usb port. You will want to disconnect and reconnect at that port, not at the computer.
All processes assume you have Developer options enabled, with OEM unlocking and USB debugging enabled. Also allow install from unknown sources
enabled in Security.
Backup and Recovery with SP Flash Tools and MTK Droid tools
With the unit turned off and not connected, open the sp flash tool folder and run sp flash tool as Admin.
For the Scatter-loading File, click choose and select the downloaded scatter file, MT8127_Android_scatter.txt.
Now click the Readback Tab.
Select add, to add an entry to the list below. Double click the the entry. You can make a folder to save it in, but leave the
name ROM_0.
After selecting save, you will get the Readback block start address screen. Type will be Hex, Region - EMMC_USER.
Start address will be left at 0x0000000000000000.
The length we can get from the scatter file. Open the scatter file in Notepad++.
The scatter file is your partition table along with other info. You can use the start address for the cache, so that will backup everything
to that point. The address is 0x00000000D4000000.
Select ok and then make sure the box on the left for the entry you created is checked.
Now click Readback.
With Sd Flash Tool Readback running, turn on both constant and acc to the unit.
Connect the usb cable to quickcharge port in four to five seconds after powering.
If you are too late it won't work and you will have to reboot. If you are too early it won't work either. If the Atoto screen appears on the
unit, you need to try again.
Once you connect, the bottom process bar in SP tools will first turn red, and then you will see the process as it is backing up your system
in blue.
I was having issues with the unit timing out before completing. I found that turning off the power to the ACC after about two minutes,
and then back on in two minutes, would keep the process from timing out. Just keep doing that until it finishes.
Once it has finished, disconnect and restart the unit. You can close the message that it finished in SP Flash.
Now you want to run MTK Droid tools downloaded from here, as admin.
When the unit is up and running, and MTK Droid tools up, connnect the usb to the unit.
In a few seconds, MTK Droid tools should recognize the unit and display some info. When that happens, click the "root.backup.recovery" tab.
Now you want to select "To process file ROM_ from Flash Tool".
Now go to the folder where you saved the ROM_0 and select it. This cut the rom into the actual partitions, making it flashable.
When asked "To make CWM recovery Automatically" select no, and then it will ask for an optional file to use, just click cancel.
When it has finished, go into the MTK Droid Tools folder, and in the backups folder, will be a folder with all of the partitions.
You will want to change the name of factory_NONmodified_recovery.img to just recovery.img.
To restore, run SP flash tool, and select the the scatter file from the backup folder. Always make sure that the Preloader is never checked.
Typically Preloader and Uboot are not checked, but make sure anyway. If the Preloader if erased, or accidently written over, you will have hard
bricked your device. Other mediatek devices(mainly phones) are able to recover from this by either booting into a hidden metamode, or by
finding a test point on the board marked KCOLO or COLO and grounding it. I have not found either of these methods to be available.
So don't mess with the preloader.
Flashing is the same method as before. When you see all the partitions loaded if SP Flash tool, click Download.
Power up the unit and connect the usb in four to five seconds. Turn ACC power on and off to keep it from timing out.
If you get an error in sp flash that it is the wrong scatter file, you should replace the scatter file in you backup folder with the one
downloaded from the link above.
Flashing a partition, such as recovery is the same process, you could simply put the recovery in a folder with the scatter file and then
select that in scatter in SP flash tool. (Flashing a custom recovery requires the system to be rooted)
Rooting
The easiest way to gain root I found, was by running KingOroot in windows, connected to usb. Once KingO has root, you have to replace KingOroot
with SuperSu. The first time, I replace files manually through ADB with root privileges.(Could also use ES File Exploer)
But an easier way is once KingOroot has root, do not reboot. Install SuperSU and then Run SuperSU, and when it fails, run it again. Eventually you will
see a prompt that SuperSU is asking KingOroot for root privileges. Grant it and run it again. When it fails, reboot the system. SuperSU should now have
root. Make sure kingoroot is gone. When you make SuperSU a system app, the only way to lose it is by unrooting in the SuperSU options.
If you got this far, you might have realized that a custom recovery is not exactly necessary, due to the SP Flash Tool. Once rooted, you could use Flashfire for apps
that need to be flashed, such as Xposed. However I did compile a TWRP recovery from Omnirom source using ---> https://forum.xda-developers.com/showthread.php?t=2798257
There is an issue with it that it keeps going to lock screen, you just have to keep swiping to unlock.(Was able to 'cut out' the lock screen issue, no longer locking)But everything seems to be functioning.
You can get the custom TWRP recovery here ---> https://drive.google.com/open?id=1k_9rrG0_4dkw45cetUzbq0m0Q3VgZ7P1
I don't credit take this, there is tons of info on Mediatek devices on here, just do a search. I just took the info and found what works for this device.
Some other info: Fastboot is not enabled on this device. If you use adb reboot bootloader, You will see a fastboot mode screen for a moment, until the unit automatically reboots. I was able to get the screen to last for a while by either turning off power to the ACC or disconnecting and reconnecting the USB. Even though the screen remained on for a bit, there is no way to connect. You can also get to an odd Recovery like menu if you do adb reboot sideload and wait for it to timeout.
Could not find a way to connect to or control that either. And if you flash a custom recovery without having root, it will go to a factory reset.
My biggest issue with this unit is Atoto's Gui, I have been trying Nova Launcher and CarWebGuru, both seem to be much better options. After looking at some of the other units stock setup, I think this has to be one of the worst. Maybe one day atoto will decide to update it.
Thats really my only major gripe. There is the issue with radio being attached audio device, but it seems to be with a lot of these units.
Hope this helps anyone interested and gain's some interest in this unit.
Click to expand...
Click to collapse
Thanks for your tutorial but it seems KingOroot is reported as a malware buy every antivirus software and even by Android. What do you think about this?
Hello,
If my OnePlus 5 is powered off: and I then plug it in; it will semi turn on and go to the battery charging graphic. The phone wont boot into Oxygen OS
I would like to figure out how to get the phone to boot up when plugged in.
I have searched the web and have not come up with any working results. I have tried the following 2 methods:
- Go Into Fastboot and run fastboot oem off-mode-charge 0 ( the system accepts the command and says "okay" but this doesn't get the phone to power on.
- change the lpm or playlpm file ( these files dont exist on this phone so I have no idea which file is in place of lpm)
Thanks!
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.