I have been having many issues flashing roms on this phone, the number one issue is that my phone often gets stuck in boot loop after flashing aosp/cm/aokp etc roms. What I figured out is that everytime I reboot the device it will get stuck in boot loop, the only solution is to flash kernel via fastboot quite inconvenient as I do not always have my netbook with me. Perhaps it could have something to do with the update, however I have used the ruu to stock many times and this last time I did not update. Unless the hboot got permanently up dated and using the ruu back to stock doesn't revert back to the old one...
In any case am I the only one having these issues? I really don't mind sense and I love all the cool widgets but I want Jellybean so I would rather not go back to ics.
dude, both the kernels sense and aosp are seperate, only solution is take a backup via cwm or TWRP AND restore it whjen u want
I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.
md1008 said:
I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.
Click to expand...
Click to collapse
ok try this, download sick kernel fastboot it, the flash the image via cwm
I figured out my own mistake, I was using fastboot boot boot.img which does not flash the kernel but is more of a test drive. So I now did this and all is right with the world fastboot flash boot boot.img. I do not have a lot of experience with fastboot or bootloaders. Sorry to clutter the Q&A
Ohhhh lol good
Sent from my One V using xda premium
Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.
mastertr said:
Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.
Click to expand...
Click to collapse
Here are the steps
*Download rom, gapps, kernel
*in recovery factory reset, wipe system ( optional)
*install ROM, gapps, kernel
*reboot into boot loader(hboot)
*Mount USB and extract boot.IMG from ROM and put it in c:/Android
*make sure phone days fastboot, if not press power button
*open up adb
*CD c:/Android
*fastboot flash boot boot.img
*restart phone and out sticks
Important part is to add flash to the fastboot commands
Sent from my SGH-T999 using xda premium
Here
http://forum.xda-developers.com/showthread.php?t=1996665
Sent from my One V using xda premium
Related
So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
5.to flash a custom Rom just flash a custom recovery in the fastboot
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Edit: (credits to cpv5 for this info)Make sure you don't go to recovery when you're on stock recovery as it will wipe everything on your phone & virtual sdcard and you will be back to setup screen again.
gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
I've done that now, ta for that.
Sent from my HTC One X using XDA Premium HD app
gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
even better is that once you have done the OTA update to 1.28 you get the new Hboot which can boot properly so you never have to replace the stock recovery. just fastboot boot recovery.img if you need to change rom or nandroid
I dont think that the 1.28 Hboot has fixed the fastboot boot commands...
You can fastboot boot a recovery? not just a boot.img?
broncogr said:
I dont think that the 1.28 Hboot has fixed the fastboot boot commands...
Click to expand...
Click to collapse
it has because i have used it
flakz0r said:
You can fastboot boot a recovery? not just a boot.img?
Click to expand...
Click to collapse
and yes, you can boot a recovery aswell as a boot.img
bagofcrap24 said:
it has because i have used it
Click to expand...
Click to collapse
Very interesting, seems to be working for recoveries here as well (s-on unlocked hboot 0.94).
I'm really interested if this works properly for zImages as well. I thought PaulOBrein was working with htc for a solution for this "fastboot boot" though? Maybe some parts ain't working?
This is a great tip, thanks!
and is it just me, or does adb work when fastboot booting clockwork with the stock recovery flashed?!
bagofcrap24 said:
it has because i have used it
and yes, you can boot a recovery aswell as a boot.img
Click to expand...
Click to collapse
Are you using windows to fastboot boot or linux?
broncogr said:
Are you using windows to fastboot boot or linux?
Click to expand...
Click to collapse
Just tested it here, works on both host-machine types
It also lead to a nice find: http://forum.xda-developers.com/showthread.php?t=1594819&page=21
gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
I just add further note on your question here
See the edit part.
Thanks a ton ckpv5
Has a question here, how do we flash stock recovery in hboot? I only know the way of flashing stock recovery via fastboot with the command of "fastboot flash recovery [recovery name].img*
Is my way wrong or there is some other way?
Where do I get stock recovery from? Tempted to do this until cwm supports charging....
Sent from my HTC One X using Tapatalk 2
landwomble said:
Where do I get stock recovery from? Tempted to do this until cwm supports charging....
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You can get it from the link below
http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Btw bro, wanna ask if you are able to guide me on flashing the stock recovery? Is it the same way as flashing custom recovery?
williamyi said:
You can get it from the link below
http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Btw bro, wanna ask if you are able to guide me on flashing the stock recovery? Is it the same way as flashing custom recovery?
Click to expand...
Click to collapse
yes same thing. not a single change except from the name
fastboot flash recovery (stock name).img
gunswordx said:
Edit: (credits to cpv5 for this info)Make sure you don't go to recovery when you're on stock recovery as it will wipe everything on your phone & virtual sdcard and you will be back to setup screen again.
Click to expand...
Click to collapse
ok so...when you mean this, you are saying that by simply going to hboot and afterwards "recovery", it will wipe it all?! wtf?!
any reason for it?
casca said:
ok so...when you mean this, you are saying that by simply going to hboot and afterwards "recovery", it will wipe it all?! wtf?!
any reason for it?
Click to expand...
Click to collapse
Because the stock recovery doesn't have menu like the CWM recovery, so once you choose recovery, the recovery process will run. Not like the CWM recovery, you need to choose which function to run.
So two things can happens when you go to recovery when you're on stock recovery:
1) the recovery will runs and wipe everything on your phone (I tested this)
2) the recovery will runs and there is error where you see the phone logo with red triangle, then you need to shutdown and restart to your current ROM.
ckpv5 said:
Because the stock recovery doesn't have menu like the CWM recovery, so once you choose recovery, the recovery process will run. Not like the CWM recovery, you need to choose which function to run.
So two things can happens when you go to recovery when you're on stock recovery:
1) the recovery will runs and wipe everything on your phone (I tested this)
2) the recovery will runs and there is error where you see the phone logo with red triangle, then you need to shutdown and restart to your current ROM.
Click to expand...
Click to collapse
ok, tks for explaining mate
What is the meaning of the error where you see the phone logo with red triangle
Hi,
I would like to ask how can I fix this problem. Whenever I fastboot any kernel (tried on ArcKnight and Trinity), sometimes it wont install. After trying 2-3 times, it will install normally. But, whenever I restart my phone, the kernel returns back to stock ICS kernel. I don't know what to do.
The things I've done before flashing the kernel:
~flash stock ICS rom
~then fastboot recoveryarc.img
~wipe everything
~install jelly sandwich rom
~fastboot custom kernel
Thanks in advance.
When you do fastboot, check what you are typing...
fastboot flash boot boot.img
-- or --
fastboot boot boot.img
The 1st one should make the new kernel stick around. The 2nd one is to test the kernel, so the new kernel is forgotten after 1st boot.
Good luck
sent from my supercharged LT15i using xda app
oh i see.. haha.. i was confused between flash and boot
and to follow up, can i install CMW using recoveryarc.img using that method?
Deicidium said:
oh i see.. haha.. i was confused between flash and boot
and to follow up, can i install CMW using recoveryarc.img using that method?
Click to expand...
Click to collapse
No, you should not flash recoveryarc.img to install CWM.
If you do, then you will only be able to enter recovery, and not be able to use your phone as a normal phone
(until you flash a custom kernel to replace recoveryarc.img)
This is the way you get CWM on your phone permanently...
When you fastboot the custom kernel (last step in your initial post), then you should flash it to make it permanent.
Most custom kernels have CWM recovery built-in, and here's the trick to enter recovery -
After you turn on the phone, wait for the hardware keys to light up.
Just in case you miss this, the coloured led will light up purple at the same time :cyclops:
When this happens, press (and release) the "volume down" button once or twice.
Then you should see CWM recovery in a few seconds.
Enjoy your new freedom
oh thanks a lot.. will try this when i get home..
ha ha, i lost many times for stupid flashing method: fastboot boot boot.img
TKS so so much!
I tried installing a custom rom today and I think I messed up really bad, because my phone does not get pass the boot screen and I cannot enter the recovery setting. I think I messed up after entering
fastboot flash boot boot.img
in the command prompt and restarting because I forgot to put the rom zip on my phone. Since then I could not get pass the boot screen and even tried running a backup using CWM, but it didn't help. I then managed to mount my phone and put the rom onto it and installed it, but again it didn't help.
Now my phone can only enter the bootloader, I select hboot and fastboot, but nothing else works. Everytime I select recovery or factory reset I get the htc boot screen and it gets stuck. Does anyone have any solutions?
Thanks
did u backup your phone rom???
if you did u can go to recovery and restore it
and never try to change rom again trust me in that
otherwise i can't help bcuz i did the same mistake
I did make a backup, but like I said I can't enter recovery anymore, so I can't load the backup.
Thanks for trying to help anyway though.
fastboot erase cache
Often fixes recovery problems.
BenPope said:
fastboot erase cache
Often fixes recovery problems.
Click to expand...
Click to collapse
Still not working, thanks anyway.
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
BlueSingA said:
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
Click to expand...
Click to collapse
I have hboot 1.39.0000 and I was trying to install the latest cyanogenmod cm-10-20130106-NIGHTLY-endeavoru.
Yeah I realized this after I restarted and did it get the zip onto the phone. I think I installed it, but the phone is still stuck on the boot screen
UPDATE: Okay I've managed to install CWM recovery, so I think I'm making progress
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
BlueSingA said:
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
Click to expand...
Click to collapse
Yeah CWM didn't load up, but I got it working again. Well it seems I'm back to getting the rom to install and being stuck at the boot screen again, so maybe I just need to use a different rom. Thanks for the help though
Okay, I've tried installing a few roms, but unfortunately I'm still on the boot screen, I can sometimes even reach the cyanogenmod boot screen, but get stuck there. I've read that this might be kernel issue, does anyone have any ideas?
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
You are a goddamn hero! Thanks, this solved everything.
No problem!
Sent from my EndeavorU using xda app-developers app
I'm pretty new to installing ROMs and I seem to have screwed something up. I was trying to install CM10 but it didn't work. I wiped system and installed from my sd card and all I got was a black screen. I went to restore from my backup, but somehow it got corrupted. I've tried flashing different ROMs, following youtube tutorials, even tried the ROM Update Utility, but no luck.
I'm out of ideas... any help for a poor, ignorant beginner?
Are u able to get into bootloader?if yes,then again flash cm10 and flash the Hellboy kernel,this step u missed that's why it isn't booting.
Sent from my HTC One V using xda app-developers app
mihirengg19 said:
Are u able to get into bootloader?if yes,then again flash cm10 and flash the Hellboy kernel,this step u missed that's why it isn't booting.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
I can get into bootloader. I tried as you said and flashed cm10 and then the hellboy kernel. Now it goes to the white htc screen w/ the red lettering... any ideas?
For going into bootloader press and hold power for 10+ seconds and when screen goes black release power and press and hold volume down until u get into bootloader.then select fastboot from the menu and then flash kernel.then go back to bootloader and from there go into recovery and do a full wipe and then flash cm10
Sent from my HTC One V using xda app-developers app
mihirengg19 said:
For going into bootloader press and hold power for 10+ seconds and when screen goes black release power and press and hold volume down until u get into bootloader.then select fastboot from the menu and then flash kernel.then go back to bootloader and from there go into recovery and do a full wipe and then flash cm10
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Same result... it seems like everything's working when I do it, but when I reboot I just go back to the same screen w/ the red letters.
i'll help you:
these steps are to be made in the EXACT order:
reboot into bootloader, flash Hellboy latest kernel (for GSM if you are GSM, i don't know if this kernel is for CDMA also. If you have CDMA, please flash Super Sick kernel).
after the kernel is installed, use the menu to reboot to your recovery or use adb and type
Code:
fastboot reboot recovery
when you are in the recovery, do these:
factory reset
wipe system
flash the desired rom - in your case CM10
reboot the phone
let it stay for 1 min after the reboot
reboot again in the recovery (use the menu from within the rom to reboot to recovery)
flash gapps package for jellybean;
reboot the phone
the phone will now stay a little longer until it reboots because dalvik will decompile the google apps you've just installed.
congrats, your phone is working
P.S: the line to flash your kernel onto your device, is:
fastboot flash boot boot.img (you have to rename the kernel you downloaded to "boot.img")
Why u know post in correct sections
Sent from my One V using xda premium
1ceb0x said:
i'll help you:
these steps are to be made in the EXACT order:
reboot into bootloader, flash Hellboy latest kernel (for GSM if you are GSM, i don't know if this kernel is for CDMA also. If you have CDMA, please flash Super Sick kernel).
after the kernel is installed, use the menu to reboot to your recovery or use adb and type
Code:
fastboot reboot recovery
when you are in the recovery, do these:
factory reset
wipe system
flash the desired rom - in your case CM10
reboot the phone
let it stay for 1 min after the reboot
reboot again in the recovery (use the menu from within the rom to reboot to recovery)
flash gapps package for jellybean;
reboot the phone
the phone will now stay a little longer until it reboots because dalvik will decompile the google apps you've just installed.
congrats, your phone is working
P.S: the line to flash your kernel onto your device, is:
fastboot flash boot boot.img (you have to rename the kernel you downloaded to "boot.img")
Click to expand...
Click to collapse
Thanks! One hiccup, when I try to do factory reset it fails saying, "unable to mount '/sd-ext'. What does that mean?
Okay, I think I'm getting closer! I guess the twrp recovery I was using was bad or bad for my phone, because I flashed an old version and on reboot it went into loading the rom, I guess from a previous flash. I went back into bootloader, flashed supersick kernel, factory reset, wiped system, went to recovery and flashed the rom. I let it reboot and now it's stuck in a boot loop. I went ahead and put it into recovery and flashed gapps and rebooted. Still in a boot loop. Any ideas now? I really appreciate the help...
Try with Cwm...
Sent from my One V using Tapatalk 2
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.4.5-primou.zip
this is the latest CWM Recovery for HTC one V GSM *(primoU)
http://goo.im/devs/maxwen/CM10-primou/boot-HELLBOY-CM10-201212011716.img
Hellboy Kernel for CM10 *from maxwen's post.
http://d-h.st/FSE
All in one tool for HTC one V
so, to start, reboot in recovery by using volume DOWN + Power. Once you are in the bootloader press fastboot and plug the USB cable in the phone ( you will see fastboot will change into "fastboot usb") then open the All in one tool and flash the kernel from the link, flash the recovery from the link *(all in one v interface is prety intuitive you cant get lost). and after you do this follow Icebox's steps into CWM. Factory reset, wipe data, flash room, reboot, flash gapps, reboot. enjoy phone!
thanks to all the devs that created these tools !
bahubali67 said:
Try with Cwm...
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Same bootloop....
Oh and it said it couldn't mount "sd-ext" during the wipe
I have the could not mount error in CWM sometimes aswell, but what i do is, factory reset, reboot in recovery, wipe data, reboot in recovery, flash rom, reboot to ROM, reboot recovery, flash gapps, reboot rom.
rzarectha said:
I have the could not mount error in CWM sometimes aswell, but what i do is, factory reset, reboot in recovery, wipe data, reboot in recovery, flash rom, reboot to ROM, reboot recovery, flash gapps, reboot rom.
Click to expand...
Click to collapse
Still boot loopin'.... but the loop is getting longer at least..
did you try to flash the recovery provided in the All In One tool ? there's a recovery image included in the archive there, try to flash that recovery and with that recovery see if you can run the reset to factory
rzarectha said:
did you try to flash the recovery provided in the All In One tool ? there's a recovery image included in the archive there, try to flash that recovery and with that recovery see if you can run the reset to factory
Click to expand...
Click to collapse
I forgot to mention that I'm virgin mobile cdma version so I can't use that cwm because it's gsm, right? I'm also flashing supersick kernel instead of hellboy. Can I use hellboy with cdma?
gdubya9 said:
I forgot to mention that I'm virgin mobile cdma version so I can't use that cwm because it's gsm, right? I'm also flashing supersick kernel instead of hellboy. Can I use hellboy with cdma?
Click to expand...
Click to collapse
U must use cdma kernel. (for gsm, there different. Kernel)
Sent from my One V using Tapatalk 2
ah sorry, i did not know you are primoC, in allinone you also have a CDMA recovery, i dont know about the CDMA kernel but everyone talks about supersick so yeah, try to research what version of supersick you need for CM10 and flash that one
Well, I seem to just be going in circles... nothing I've tried has worked.. still getting boot loop. Flashing supersick and CM10 hasn't worked. I've tried it with cwm and twrp. My factory reset still says failed to mount sd-ext.
I dont know how much different is primoc from primou, but i remember i had a reset to factory in the bootloader aswell. and, as i said, i had the problem with mounting but i rebooted recovery and did each task (reset, flash) in a new recovery boot. i am brainstorming here but i am out of ideas, we are missing something here clearly, but as long as you have acces to the bootloader hope is not lost