LG G4 H811N Boot Loop - T-Mobile LG G4

LG G4 H811N Boot Loop - T-Mobile LG G4

I am having a lot of trouble with my LG G4.
It started bootlooping about a week ago, and ever since I have been trying to get the data off of it. For some reason, when I put the phone into download mode, fastboot does recognize it (fastboot devices has no output) so I cannot recover that way. I have flashed the original T-Mobile H81110N KDZ and it still did not work. I am aware that there is a solution for international G4 variants that disables the big cores, but not one for US variants. I have been trying to modify the KDZ that I have to disable the big cores, but I have no clear idea of how to do this, and there is no overall guide in modifying TOT/BIN and KDZ, only how to unpack them (which I have done). If anyone has a T-Mobile KDZ that has big cores disabled (or is willing to make one) that would be greatly appreciated.
The only thing that even remotely works is freezing the phone, which, on occasion, gets the phone to boot completely up (only for it to crash and bootloop shortly thereafter, not enough time for me to get data off of the phone).
At the moment I have another G4 on its way (warranty). Is there any way I could disable big cores on that phone and make a KDZ to flash on this phone?
Any and all help is greatly appreciated.

KhanPower said:
I am having a lot of trouble with my LG G4.
It started bootlooping about a week ago, and ever since I have been trying to get the data off of it. For some reason, when I put the phone into download mode, fastboot does recognize it (fastboot devices has no output) so I cannot recover that way. I have flashed the original T-Mobile H81110N KDZ and it still did not work. I am aware that there is a solution for international G4 variants that disables the big cores, but not one for US variants. I have been trying to modify the KDZ that I have to disable the big cores, but I have no clear idea of how to do this, and there is no overall guide in modifying TOT/BIN and KDZ, only how to unpack them (which I have done). If anyone has a T-Mobile KDZ that has big cores disabled (or is willing to make one) that would be greatly appreciated.
The only thing that even remotely works is freezing the phone, which, on occasion, gets the phone to boot completely up (only for it to crash and bootloop shortly thereafter, not enough time for me to get data off of the phone).
At the moment I have another G4 on its way (warranty). Is there any way I could disable big cores on that phone and make a KDZ to flash on this phone?
Any and all help is greatly appreciated.
Click to expand...
Click to collapse
did LG refuse to repair.? why.
and so far there isnt one.. someone said to use the one available and need a hex editor to change name.. someone try it and it bricked phone..

Related

Deep flash (EDL) cable

Hi everyone, just wanted to let you all know that using a deep flash cable to force EDL mode works on this phone. So if you are, for some reason, unable to reach the bootloader using conventional methods, this is a good way to restore the firmware on your phone and hopefully manage to boot normally again.
I stupidly managed to brick my phone when downgrading to android 9 from the 10 beta - no matter what I did the phone would only launch to Qualcomm Crashdump mode (900E).
But, following the guide here: https://forum.xda-developers.com/zenfone-5/help/hard-unbrick-unbricking-hard-bricked-t3915137/ I managed to create a deep flash cable myself, and, to my surprise, that forced it to EDL (9008) mode! I had a backup of all the partitions on the phone, so it was a simple matter of reflashing them, and when that was done it booted normally again (phew).
If you are a tinkerer I would highly recommend either creating one yourself, of buying a premade one (there are multiple shops that have them, including eBay and Amazon). Just in case the worst were to happen!

Fffff, wish I read this before I sent in my bricked phone.. dang it.. well, just gotta hope it will get fixed then, lol. At least I now have a backup-plan, THANKS for sharing this :good::laugh:

HomerSp said:
Hi everyone, just wanted to let you all know that using a deep flash cable to force EDL mode works on this phone. So if you are, for some reason, unable to reach the bootloader using conventional methods, this is a good way to restore the firmware on your phone and hopefully manage to boot normally again.
I stupidly managed to brick my phone when downgrading to android 9 from the 10 beta - no matter what I did the phone would only launch to Qualcomm Crashdump mode (900E).
But, following the guide here: https://forum.xda-developers.com/zenfone-5/help/hard-unbrick-unbricking-hard-bricked-t3915137/ I managed to create a deep flash cable myself, and, to my surprise, that forced it to EDL (9008) mode! I had a backup of all the partitions on the phone, so it was a simple matter of reflashing them, and when that was done it booted normally again (phew).
If you are a tinkerer I would highly recommend either creating one yourself, of buying a premade one (there are multiple shops that have them, including eBay and Amazon). Just in case the worst were to happen!
Click to expand...
Click to collapse
The same thing happened to me but I dont have a backup of the partitions on my phone can I use the raw firmware found on this xda thread https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042.?
Thanks

Help! I tried to cross flash my T-Mobile V40 and ended up bricking it.

I ignored the warnings... I know, idiot.
But I went ahead and it completed.
But now the phone has a black screen and nothing else.
When plugged in, my computer recognises it as Qualcomm 9800 port 30.
Still nothing on screen though.
Anyway to get it back? Or get it to stock rom? Really don't want tmobile bloat all over it if possible.

Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner

Double post.

What is it about the T-Mobile version that makes it so different to the others.

NGOwner said:
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Click to expand...
Click to collapse
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.

shawnmos said:
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
Click to expand...
Click to collapse
It's not the modem partition, it's the ftm (and maybe some others too)

I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!

aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
Why would you want to flash a T-Mobile stock ROM?

Ainz_Ooal_Gown said:
Why would you want to flash a T-Mobile stock ROM?
Click to expand...
Click to collapse
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).

aw2a said:
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
Click to expand...
Click to collapse
Ahh I see well we do have Android 10 in the flavors of LOS 17.1 and Havoc OS 3.5..

No firehose loader for the T-Mobile one so you can't fix in 9008 mode. It is a paperweight. You need to replace the motherboard.

Bump? Any way to revive it?

slebeau1988 said:
Bump? Any way to revive it?
Click to expand...
Click to collapse
You could try asking tmobile for help and see how much they'll charge you. You may get lucky if the phone is still in warranty

HELP Recover files: Moto G 2014 16GB XT1033 low battery, bootloop, now hard bricked

Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.

After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.

oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?

Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.

V40 is it possible to change NT Code without Root?

I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.

lexih said:
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code here is a list of NT codes:View attachment 5134107unfortunately needed root!
Click to expand...
Click to collapse
Thank you for your reply. Yes, I have read many instructions even on this page how to edit, cust_path_mapping.cfg, and that it's surely easy once the phone is rooted. But that's why I first wanted to see the possibilities to do this without that I have to root the phone.

suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers

AsItLies said:
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers
Click to expand...
Click to collapse
Thank you for your reply. No I don't know if they're related either, it was just a guess since the problems started at the same time. Well, I always had a kind of "problem" since I never have been able to upgrade from LG Bridge. And that I guess is from the NT-code. But the sign in the start appeared after the Android 10 upgrade. However, I'm using LGUP 1.16.0.3 and I have used it everytime, with DLL version 1.9.39.7.
And actually it wouldn't bother me too much having this sign in the start anyway, I only restart the phone like once per week. But of course it bothers me that I can't make the upgrade like before. And I can also mention that I have never tried to refurbish with LGUP, only upgrades, because I have some bank apps etc. that are a bit complicated to reinstall. Of course it's possible, but I have to be mentally prepared for it. So I'll only do that when I know there's no other option. And the phone work good today, so I'm not in a rush, but in a couple of months I should be doing an upgrade of course.
And thanks for telling me the other option too, I will surely try it one day but since it also requires refurbish I will try after I fail to make the normal refurbish.
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.

suain81 said:
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.
Click to expand...
Click to collapse
No, to root, you loose all data and have to start again. Part of rooting is to flash dm-verity which turns off encryption. But, that allows you to do a backup of the data partition once you've reinstalled everything. The positive side there is that in the future, you could back up that partition (data), make any other changes, then flash data back, and your apps would be back as they were.
Other risks? Well, maybe, if the phone was stolen I guess, it would be easier for someone to steal your data. Your situation, with serious banking apps, it **may be** you don't want that risk...
Maybe for just trying a refurb to lose nt-code, look at LG's 'restore' from previous device ability, use it to save off the apps somewhere, then restore after refurb? no root needed.
cheers

Question Bootloop Issue

Hi all,
Quick backstory: I bought a Google Pixel 5a (from the USA) for my cousin who lives in India. The phone was working fine for him until about a few weeks ago when the phone was stuck in a boot loop. Unfortunately, my cousin did not have USB Debugging on and the OEM is locked.
I was able to help my cousin adb sideload the latest Full OTA update. The install completed successfully but when we try to restart the device, the phone bootloops once again. If we leave the phone to continue bootlooping, it gets very hot (which seems obvious but wanted to share this as well).
I cannot think of any other steps to take and it feels like this is a hardware driven issue. Worse yet, since my cousin is in India, we cannot service the phone. Posting here to see if anyone else has had a similar issue and was able to figure out what it was. Any advice helps, thanks!

did you try to extract the payload.bin to get the boot.img file and flash it to slots a & b .i think you can do that with twrp. with the bootloader you might not be able to do that.

Database Develop

welcome