Boot loader is bricked, but the OS works fine.
If HTC releases a firmware update over Zune, will it flash my bootloader?
Will the broken bootloader prevent my phone from functioning in any capacity? People say "you can't update," but I've reverted to NoDo twice since the half brick, and on both occassions I've been asked to update to Mango.
bricked phone
Can the phone be able to get a future update?? or it is blocked to do it also?
pantsaregood said:
Boot loader is bricked, but the OS works fine.
If HTC releases a firmware update over Zune, will it flash my bootloader?
Will the broken bootloader prevent my phone from functioning in any capacity? People say "you can't update," but I've reverted to NoDo twice since the half brick, and on both occassions I've been asked to update to Mango.
Click to expand...
Click to collapse
How did u revert to nodo, the last i checked, the backup in my zune is 7403
Bricked boot loader i guess is still all right, but bricked phone isn't .
Related
Before the NoDo update I unlocked my phone (Omnia 7) with the Chevron unlock. I encountered some terrible bug(s) so I applied the NoDo update to see if that'd help. It didn't. The phone still stayed unlocked even with the update, so I was wondering if it's worth it to reset my phone and (maybe) lose the unlock for good (since it won't work with phones with NoDo installed and I think that's what I'll get if I reset the phone). So, anyone think it's worth it?
thenewperson said:
Before the NoDo update I unlocked my phone (Omnia 7) with the Chevron unlock. I encountered some terrible bug(s) so I applied the NoDo update to see if that'd help. It didn't. The phone still stayed unlocked even with the update, so I was wondering if it's worth it to reset my phone and (maybe) lose the unlock for good (since it won't work with phones with NoDo installed and I think that's what I'll get if I reset the phone). So, anyone think it's worth it?
Click to expand...
Click to collapse
I think you don't need to "Re-Lock" your phone before getting NoDo update.
shawchyn said:
I think you don't need to "Re-Lock" your phone before getting NoDo update.
Click to expand...
Click to collapse
You don't need to. What I'm wondering is if the phone will re-lock itself if I reset it. I'm thinking it'll use the NoDo version to reset itself, which doesn't work with the Chevron unlock, and I won't be able to unlock the phone again. I wonder if it's worth it to reset the phone and probably lose the unlock I applied to the phone. I'm experiencing bugs where i can't use the marketplace on the phone to buy or update anything, and apps that didn't come with the phone crash after ~15 minutes.
Sounds like reset time... I would say better to have the device working properly without unlock than not at all with it...
Sent from my HTC HD2 using XDA App
@4m8 since you are the only guy here who knows best about HTC Desire 300.
Well my friend gave his Desire 300 to me for repair. i thought its going to be easy as like 1,2,3. but guess i was wrong.
I tried several options already.
USB DEBUGGING might be off as well since my friend doesnt know about flashing or unlocking bootloaders. i cant unlock the bootloader i think.
Its S-ON. (Dont know what it actually means).
I tried going to recovery but it shows me a PHONE with A RED ''DOWNLOAD MODE ARROW'' i think recovery is corrupted?
i tried already flashing boot.img and recovery.img over FASTBOOT. but it says ''failed remote signature verify fail''. its just isnt like my sony device which says OKAY all the time lol. those two files were found on a Google drive website.
i have no other options left to revive this phone.
Help will be a very good option :good: thanks in advance.
Well i read a lot of sites which says stuck at boot. and i cant find a Official Stock firmware for this device. is it that HTC didnt released one?
That sounds really bad. So let's recap to see if I understand your situation correctly:
Phone doesn't boot, can't enter recovery and will only load the bootloader. (b-loader status is S-ON Locked)
Now unless you are able to unlock the bootloader (which you aren't as you have stated) there is no way to flash a custom recovery.
The locked bootloader will prevent it because it requires anything you want to flash to be signed by HTC.
The only way out is to flash an actual official update by HTC which afaik is not available for this device.
To make matters worse, if the phone is branded you couldn't even revive it this way because some providers, like mine, actually force HTC
to prevent those phones from flashing an official HTC update that is not branded.
But there is a bright side to your situation. Since you weren't able to unlock the bootloader your friends warenty should still be intact.
And even if this was a branded phone try to claim a replacement from the manufacturer, that way you might have the chance to get
an unbranded device in return for the trouble you and your friend had to endure. :fingers-crossed:
Sorry if I had to shatter the last piece of hope that you were clinging on to but without an unlocked bootloader the only option that
remains is getting a replacement or begging HTC to release an update or the version that is installed by default as a RUU exe
PS:
Just to be certain, you did try the factory reset option in the bootloader before giving up, right?
4m8 said:
That sounds really bad. So let's recap to see if I understand your situation correctly:
Phone doesn't boot, can't enter recovery and will only load the bootloader. (b-loader status is S-ON Locked)
Now unless you are able to unlock the bootloader (which you aren't as you have stated) there is no way to flash a custom recovery.
The locked bootloader will prevent it because it requires anything you want to flash to be signed by HTC.
The only way out is to flash an actual official update by HTC which afaik is not available for this device.
To make matters worse, if the phone is branded you couldn't even revive it this way because some providers, like mine, actually force HTC
to prevent those phones from flashing an official HTC update that is not branded.
But there is a bright side to your situation. Since you weren't able to unlock the bootloader your friends warenty should still be intact.
And even if this was a branded phone try to claim a replacement from the manufacturer, that way you might have the chance to get
an unbranded device in return for the trouble you and your friend had to endure. :fingers-crossed:
Sorry if I had to shatter the last piece of hope that you were clinging on to but without an unlocked bootloader the only option that
remains is getting a replacement or begging HTC to release an update or the version that is installed by default as a RUU exe
PS:
Just to be certain, you did try the factory reset option in the bootloader before giving up, right?
Click to expand...
Click to collapse
Yes i did. Factory reset. But still no luck.
Yes, i cant enter recovery as well.
Well it actually started ones it told me "Process System Not Responding". And on that point i knew the system files are corrupted.
My friend told me, he left the phone in deep sleep after that it didnt turned on again.
Thanks for your help @4m8 :laugh: :good: (IT ISNT MINE SO I DONT HAVE A PROBLEM) I will give this phone back to my friend.
*FACEPALM TO HTC FOR NOT RELEASING A OFFICIAL FIRMWARE*
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, everything but I am still unable to take OTA updates like a new phone would be able to. I think this is because they banned my device from OTAs which I believe they do if you have messed with the device. I need to RMA my device so my question is would it be better to say that I didn't tamper with the device and run the risk of them finding out I did, which is pretty likely seeing as how my device has been banned from OTA updates, or tell them that I did unlock it and all of that but that I have relocked it and I am back to stock? If any of you have had a similar issue how did ASUS handle that? Thanks!
E3AANG11E3 said:
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, and all of that but that I have relocked it.
Click to expand...
Click to collapse
How to you relock bootloader?
mr_gourav2000 said:
How to you relock bootloader?
Click to expand...
Click to collapse
Since I am a new user I cannot post links. But Google "Zenfone 2 bootloader unlock" and I followed the instructions of Grekky's Blog.
there is no such thing as relocking the bootloader. only thing you can do it flash the stock image to make it look stock (since an unlocked bootloader has a white splash screen) but im sure asus knows of this and will still check and see that the bootloader is indeed unlocked and not warranty it.
This is just something we all accepted as a consequence of unlocking our bootloaders. hell i have a screen thats getting worse and worse with a yellow/brownish line coming from the top of the phone, but alas i have an unlocked phone too.
You can replace the white splash screen by flashing a black splash screen image to try and cover up unlocking your bootloader. http://forum.xda-developers.com/zenfone2/themes-apps/551-black-white-splashscreen-twrp-flash-t3141945 . If the reseller has no clue about custom recoveries and trying to flash a rom you'll be safe.
They fixed it, no questions asked. And yes, I was able to relock the bootloader.
I did some searching and I see the threads for unlocking and rooting 8.1 and 9 but couldn't find much reference to updating from 8.1 to 9 when I am already unlocked and rooted.
So if I accept the update Verizon is pushing down, is this going to basically lock the bootloader and unroot me back to stock essentially?
I just don't want to brick my phone because I am not comprehending some details I am reading in all these threads.
Just decided to go for it and see what happens..
after taking the OTA it restarted and bootloader still unlocked..
Android launched fine
had to reactivate Developer Options
OEM Unlock grayed out but says "Bootloader already unlocked" so that's good
Thanks for posting this. I'm assuming from your post that you're using the Verzon branded model?
I'm using the unlocked version on Verizon, and there's no way in hell I would take an OTA update. However, I'm about to update to 9 via image.
MuGGzyx said:
Just decided to go for it and see what happens..
after taking the OTA it restarted and bootloader still unlocked..
Android launched fine
had to reactivate Developer Options
OEM Unlock grayed out but says "Bootloader already unlocked" so that's good
Click to expand...
Click to collapse
Yes you'll be fine on Android P it give Verizon Pixel the option to unlock the boot loader
absolvi said:
I'm using the unlocked version on Verizon, and there's no way in hell I would take an OTA update. However, I'm about to update to 9 via image.
Click to expand...
Click to collapse
I'm back with an update. I used the Google notification on my rooted phone (Magisk/TW) to begin the installation. The update went okay, but custom recovery and Magisk root were wiped out. I was still able to use OEM Unlock to unlock the bootloader. The downside is, if I install custom recovery again I will lose access to my encrypted storage, meaning I'll have to reset my phone.
If your going to update, backup everything you can first; you'll need to reset.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
My advice has always been to never OTA update between Android versions, always better to fastboot flash a fresh image with a complete wipe of the system.
Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Amitie10g said:
Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Click to expand...
Click to collapse
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Spaceminer said:
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Click to expand...
Click to collapse
1.- Maybe, depending the country. So, the agent who attended me told me the warranty is void just when unlocking the Bootloader. Motorola's technical service will give the last word about that, as I have re-installed the stock rom.
2.- As I told, the phone don't seems to power on and no charging light. I've connected to the computer and it never identifies as anything than a brick.
3.- Per above, Fastboot won't recognize the device and unable to send commands to the device in any way. In other words, the device seems to be completely dead.
The vendor where I purchased the device just told me they will replace the device under the warranty.
So, I'll apply the updates via OTA and tell you the results, but I'll not unlock the bootloader, but backup upload the ROM via Fastboot and TWRP, and upload it.
I've finally gone to the vendor to retire the replacement device.
However, they don't have the Moto G6 Play available anymore. Instead, they gave me the Moto G6 (better device except for the battery) for free, as the failure has been covered under the warranty.
Advices:
Ask your vendor the repair costs for failures caused by failed firmware updates. I assume Motorola didn't checked even if the bootloader is unlocked (as the device seems to be completely dead), they just decided to replace the device.
Don't send the device to the technical service if it powers on and Fastboot is working unless you're prepared to pay the repairs.
Don't try to install the Android Pie update with the bootloader unlocked and firmware altered.
acutally, updating with unlocked bootloader causes nothing. that might have been a hardware problem of some source, idk...
---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------
but unlocking the bootloader does void your warranty tho
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Amitie10g said:
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Click to expand...
Click to collapse
Not true. My bootloader is unlocked, and Motorola is well aware of that since I had to ask them for the key. Unlocking it by itself doesn't void it. It's what you do afterwards that might void it. Like running an over volted kernel and frying something. Check the screen shot. My warranty is still good until Aug of this year. And if I really wanted to I could just relock the bootloader before sending it in, which blows that theory out of the water.
i replaced one under warranty with no issue. with an unlocked boot loader. twice.