Hello!
I have unlocked my bootloader but it is almost time for me to upgrade my phone. But when I come to sell it, it probably won't go because the bootloader is unlocked, so I want to flash the original boot logo instead of the Warning screen so that the new phone operator won't know the bootloader is unlocked.
Now, everytime I have attempted this using one I have downloaded, but it says "E: downgraded security version for logo"
Then, I tried where someone extracted the stock one, but everytime I try it, it says "E:none signed image detected"
If anyone can help me get around this it would be greatly appreciated.
Thanks in advance,
Paul.
Anyone?
Sent from my Hudl 2 using XDA Free mobile app
Nobody ATM had managed to change the ulogo without any side effects.
This one came close, but is easy to screw up.
The problem is because intel uses signed partitions and with an unlocked bootloader some partitions still can't be flashed and are protected. To get around this we need the key and security version they used for the last ulogo and we don't have it.
Okay, thank you for your reply but I need to have this done within 1 month (facepalm)
Has anything come up since I last posted here?
I don't know if this would now be classed as necro-posting but I need the solution, as expected, my phone never sold so it is now my testing device.
Thanks in advance.
Related
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
what exactly is happening when you try and unlock the bootloader?
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
Is urs the AT&T One? Then the bootloader unlock process is different. If urs is the standard international SIM unlocked, then ideally you should see a splash after you run the bootloader unlock command, which prompts you to unlock the bootloader. Please state what exactly ur issue is when u try to bootloader unlock
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
xxshererxx said:
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
Click to expand...
Click to collapse
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
http://rumrunner.us/downloads-2/
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
raghav kapur said:
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
Click to expand...
Click to collapse
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
xxshererxx said:
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
Click to expand...
Click to collapse
I think you'll find more help here: http://forum.xda-developers.com/verizon-htc-one
Greetings everyone!
Few weeks ago, I gave my device to a friend of mine to manually update it. Something went wrong so he decided not to go any further. Yday i tried to "Factory reset", after reset some error pop'd in the left upper corner of the phone.It says:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
Anyone had any similiar or even the same problem as i am facing right now? Thanks in advance.
best regards, Milan
Guy didn't know what he was doing apparently. Your handset is still locked and he apparently tried installing a 3rd party ROM, lemme guess, you wanted a newer version of Android than 4.1., which is a reasonable enough thing. Problem is that out of the box you can't do that because it only boots images signed by LG and they abandoned development after releasing 4.1 and a couple of minor point releases. You aren't totally screwed but if you were having somebody else do it for you, you might need to get some help. You can find the details elsewhere here, or more likely point a more skilled friend at it, but here it is in a nutshell.
You need to get LG's official updating software (from the LG website) and you need to fiddle with it a bit until you get it to do a rescue because it expects to have already paired up with the phone while it was still working. If you already had it installed, great because it will make it easier. Anyway, you will probably have to manually pick your model and input the IMEI since it won't already know those things and it will go out and fetch the most recent image. You will push VOL Down and insert the USB cable from a powered down state, it will then do the rest. Good chance you will even retain your data unless that 'factory reset' you mention actually succeeded.
Of course that will only get you back to stock 4.1. Read around for the official way and several un-official ways to unlock your boot loader. Once that is done you can install a better recovery and then a newer version of Android. But the first step is to restore the stock software since you have to have a running phone to be able to unlock it.
And no, nobody has ever been able to explain WHY they lock them, but every single manufacturer seems determined to do it, chipmakers put a lot of work and ad copy into how extensive and unbreakable the locks on their newest chip is, etc. And then they either bow to customer demand and add an unlock feature or we here at xda do it for them... as a courtesy of course. Truly we do live in the asylum. Wonko the Sane was onto something.
I'm running a P7 with the firmware it shipped with and I'd really like to get it up to date, but every package I've tried so far has failed during package verification. There seems to be very little info on how to update your phone from such an old build. Can anyone please help because I'm at my wit's end here. I have a limited date cap so can't just keep downloading updates in the hopes that one of them will work.
I would be greatly indebted to anyone who could help me. This issue is making me want to cry.
Do you have a phone with a provider/network lock? Which roms did you try so far? You may give B133 a shot, if that doesn't work you'd have to go the way over a custom rom and then getting back to the stock one. I can describe the process more detailed in case it's necessary.
Thanks for the response!
I think the issue is that it is a network locked ROM. I got the phone from a provider called Vodacom and get their splash screen and everything. I went to speak to them and they told me I'm not supposed to be able to update my firmware because that requires rooting the phone, which voids my warranty. Sales people being sales people, I'm not sure how truthful this is. I can't imagine a provider refusing to let you update your phone.
So far I've tried B133, B609, B617 and B853, none of which works, sadly. Someone suggested I unlock the bootloader and I got the unlock code through the Huawei site, but when I try to boot using the three-button method it tells me that no update.app file was found, so I'm not sure how to get to where I enter the unlock code.
Hm, you might search around a bit and find an easier way, but if not, unlock the bootloader, flash twrp and any emui 2.3 based custom rom. Then flash the stock recovery and make a forced update (3 buttons) with B133.
To access the bootloader you have to press volume- and power until a white screen with some text appears.
Anyway, to update would definitely be worth it.
Yeah, I did precisely that last night and ended up soft-bricking my phone. It wouldn't even work when I flashed the original firmware. It's currently in at a repair shop and I hope they can fix it. Lesson learned though.
Thanks for the help anyway.
It's not that easy to hardbrick the P7, it's very likely that he will be able to fix it! With some time for trying, you probably would have been able to do it by yourself, too.
Your very welcome
Yeah, the thing is I was up all night trying to fix it. Flashing it back the original software should theoretically have done it, so I have no idea why it didn't.
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
iantechie1979 said:
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
iantechie1979 said:
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Flash these files and it should, most probably, be fine.
use dload method as given here- https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
as there are many different opinions on this method of using only update.app file but thats not true and it should be all the files.
Main file - http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v71812/f1/full/update.zip
Data file- http://update.hicloud.com:8180/TDS/...1812/f1/full/hw/eu/update_data_full_hw_eu.zip
Flash both the files in order. 1st file will restore your system but then you need to have 2nd file so that apps are installed and all working fine.
After 1st file, it may reboot on its own and stuck on honor logo, reboot to recovery and then do factory reset, it will be fine.
Then let it boot to set up. Dont set your phone. Shutdown and flash the 2nd file.
boot and set up.
Good luck. Please provide feedback once done. In case of further issue, let me know and will dig more into this.
Oh this is hard.
chrisleLP said:
Oh this is hard.
Click to expand...
Click to collapse
What is hard?
shashank1320 said:
What is hard?
Click to expand...
Click to collapse
This problem.
chrisleLP said:
This problem.
Click to expand...
Click to collapse
you cant follow simple instructions? you shouldnt be on this forum if youre not ready to lose data or brick your device.
Thanks for your input so far people. Much appreciated. @shashank1320 I am downloading the files you suggested and will flash them exactly according to your instructions. I will get back to you in a couple of days with the result. Fingers crossed.
gopinaidu77 said:
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
Click to expand...
Click to collapse
Unfortunately my warranty has expired. The annoying thing is that if i had sent my device off six months ago when this first happened it would still be under warranty but in the UK there is only 1 service center, yes 1, and its hundreds of miles away! So i figured i could solve it myself. You live and learn.
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
iantechie1979 said:
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
Click to expand...
Click to collapse
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
shashank1320 said:
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
Click to expand...
Click to collapse
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
iantechie1979 said:
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
Click to expand...
Click to collapse
Did you flash those files i given? If not can try. Else i will have to look for other alternative
yeah i downloaded those files you had mentioned in your post and followed the instructions to the letter.
I've got a suggestion if you have tried all these above.
Can you try the following on ADB and then try to unlock OEM again.
fastboot oem relock YourUnlockCode
I've done the same and it helped, even when bootloader displayed UNLOCKED. Please try it. :good::good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
NameNotFound74 said:
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
Click to expand...
Click to collapse
Try unlocking the bootloader again even if it is unlocked. It will factory reset the device and it should boot fine. Have stuck on this many a time and this was the method i followed.
Hi all, I've an italian Nokia 7 Plus TA-1055 single SIM.
I was on Oreo 8.1, unlocked bootloader, tried many GSI roms for tests and then I wanted to came back to stock rom for some phone call problems.
In order to do it, during my tests, I did a big mistake, I relocked again the bootloader with fastboot oem lock command without having stock boot, but one with TWRP inside instead :crying:
Now, at every boot, phone shows me a message like this: "Your device is corrupt. it can't be trusted and will not boot[...] the device will shutdown in 30 seconds[...]".
Now, I can boot in download mode, but I cannot flash or boot anything via fastboot, in order to unlock again, and even "nb0 tools FIH Mobile" could not help me (like many others, stucked at "Reflashing service boot" or similar).
Now, what can I do?
Thanks for who wants to help me, every help is appreciated
death_jax said:
Hi all, I've an italian Nokia 7 Plus TA-1055 single SIM.
I was on Oreo 8.1, unlocked bootloader, tried many GSI roms for tests and then I wanted to came back to stock rom for some phone call problems.
In order to do it, during my tests, I did a big mistake, I relocked again the bootloader with fastboot oem lock command without having stock boot, but one with TWRP inside instead :crying:
Now, at every boot, phone shows me a message like this: "Your device is corrupt. it can't be trusted and will not boot[...] the device will shutdown in 30 seconds[...]".
Now, I can boot in download mode, but I cannot flash or boot anything via fastboot, in order to unlock again, and even "nb0 tools FIH Mobile" could not help me (like many others, stucked at "Reflashing service boot" or similar).
Now, what can I do?
Thanks for who wants to help me, every help is appreciated
Click to expand...
Click to collapse
Hi. U can't use any tools without unlocking bootloader in my knowledge. Me also faced same issue some months ago. I did same mistake as urs. Finally i give it to Service Centre. Got a replacement with warranty. I told them a different fake story
Rajeev said:
Hi. U can't use any tools without unlocking bootloader in my knowledge. Me also faced same issue some months ago. I did same mistake as urs. Finally i give it to Service Centre. Got a replacement with warranty. I told them a different fake story
Click to expand...
Click to collapse
The "failed update" story do you think that may be right?
death_jax said:
The "failed update" story do you think that may be right?
Click to expand...
Click to collapse
Absolutely
Thanks to all, this thread can be closed, I solved with the help of hikari_calyx