Related
Hello! I need to get my E975 back on warranty, what is the way to relock bootloader again?
Install Kdz..
Sent from my LG-E975 using Tapatalk
Avantu said:
Hello! I need to get my E975 back on warranty, what is the way to relock bootloader again?
Click to expand...
Click to collapse
Your answer is in FAQ #3 go here
dalmm said:
Install Kdz..
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
You mean i can use KDZ Flasher in Fastboot mode?
sunyakram said:
Your answer is in FAQ #3 go here
Click to expand...
Click to collapse
There are 3 options, but aren't they for other Optimus versions than E975? Which do you prefer?
The thing is i can't go download mode cause i already have unlocked bootloader and it gets me to fastboot mode. I unlocked it with Freegee but the backup is gone. Is there any possibility to lock bootloader? The phone is fully working, only thing is yellow tints on screen and i wanted to get it back on warranty.
Avantu said:
You mean i can use KDZ Flasher in Fastboot mode?
There are 3 options, but aren't they for other Optimus versions than E975? Which do you prefer?
Click to expand...
Click to collapse
1st why you returning it back? 2nd i don't know too much about veriant compatibility so its batter to post there if you cant find satisfied solution here
---------- Post added at 09:27 PM ---------- Previous post was at 09:22 PM ----------
Avantu said:
The thing is i can't go download mode cause i already have unlocked bootloader and it gets me to fastboot mode. I unlocked it with Freegee but the backup is gone. Is there any possibility to lock bootloader? The phone is fully working, only thing is yellow tints on screen and i wanted to get it back on warranty.
Click to expand...
Click to collapse
I read somewhere about these yellow tints are not a big issue thay appear and disappears after some days without any repairing, (correct me if i am wrong)
sunyakram;48385401[COLOR="Silver" said:
---------- Post added at 09:27 PM ---------- Previous post was at 09:22 PM ----------
[/COLOR]
I read somewhere about these yellow tints are not a big issue thay appear and disappears after some days without any repairing, (correct me if i am wrong)
Click to expand...
Click to collapse
It can be true. I bought it used in my country from some shop. I think they have replaced the screen with new one. I talked with the shop owner and he told me that he checked the screen before sending me and it was ok, but if i want i can send them phone back so they will replace it with new one(but he didn't tell me that it was replaced already at all). But now i'm in trouble and i don't know if i can lock bootloader without EFS Backup :/ If u have any ideas, tell me please.
Avantu said:
It can be true. I bought it used in my country from some shop. I think they have replaced the screen with new one. I talked with the shop owner and he told me that he checked the screen before sending me and it was ok, but if i want i can send them phone back so they will replace it with new one(but he didn't tell me that it was replaced already at all). But now i'm in trouble and i don't know if i can lock bootloader without EFS Backup :/ If u have any ideas, tell me please.
Click to expand...
Click to collapse
If you bought it from shop so don't worry about unlocked.unlocking doesn't effect screen.
sunyakram said:
If you bought it from shop so don't worry about unlocked.unlocking doesn't effect screen.
Click to expand...
Click to collapse
Maybe, but he wrote on his warantee card that changing firmware void the warantee. So if i send him the phone back, i don't think he will want to replace screen with new one(which is quite expenisve) when he will see europe open firmware(i had brand before) with bootloader unlocked... i will just lost money sending him phone.
About yellow tints, i heard that iphones had similar problem, it was caused by glue between screen and digitizer or somewhere else, and tints disappeared after few days of using, but i can't tell if my LG will be the same.
use kdz updater and that's it. flash the original firmware the phone came with.it takes 5 minutes.
playis but
Avantu said:
The thing is i can't go download mode cause i already have unlocked bootloader and it gets me to fastboot mode. I unlocked it with Freegee but the backup is gone. Is there any possibility to lock bootloader? The phone is fully working, only thing is yellow tints on screen and i wanted to get it back on warranty.
Click to expand...
Click to collapse
Very strange! After using freege for unlocking bootloader and flashing CWM Recovery, I got a Kernel error. I tried to flash KDZ in download mode, but after start flashing process my phone reboot in fastboot. Are you in the same situation?
If u can get into recovery mode, you can flash any working ROM and then try the old version of freegee to avoid kernel errors. The update version from playstore gives this kernel error, since it flashes the bootloader of nexus4. But I think, the playstore version should be fixed by now... better to check it... search for the old version of freegee posted by davevinci...
Lol guys i'm very stupid... you can go into download mode by holding volume + and - and starting the phone. Then you can reflash it with stock firmware in LG Support Tool under emergency options or something like that(i'm not using english version so i don't know how it sounds in english) or with KDZ Updater. Ofc my phone is fully working, all i want is to get back to stock settings.
You already had the answer...use the damn kdz updater to flash stock firmware,then perform a hard reset. end of story. why the drama??why do you guys don't read the whole story?why don't you learn how to revert the changes you make BEFORE starting doing them?
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.
xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.
xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery
Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:
Yeah and the guy from Germany doesn't have the time to look into this anyway...
Morning all,
Im not S-off and I'm using a pretty dated firmware..
I was told that there is a way to obtain and flash a firmware WITHOUT wiping anything and without too much fuss.
My questions:
What is the COMMAND in CMD?
Where do you find the signed firmware?
How do you identify which one to use?
What does it actually change? As the phone does work on dated firmware, more optimised?
I highly doubt I'm the only one who would benefit from this, once I know the answers I'll leave them here and I'll write a guide on how to install them step by step I'll also link the firmwares do others can help themselves.
Thanks
Currently running: Viper 3.5.0
Firmware: 1.80.401.1
S-ON
Unecrypted.
Check out Krassermensch's Firmware Update Tool in the guide part of the forum.
Lindsten said:
Check out Krassermensch's Firmware Update Tool in the guide part of the forum.
Click to expand...
Click to collapse
Have come mate, but I've asked some other things plus there is apparently a way to do it without the use of a tool.
This is the specific thread for firmware update.
I think you can only flash the full stock zip since you are s-on. Do take note that flashing the stock firmware.zip will wipe your internal storage.
The firmware to flash should have matching CID and MID of your device.
To check your mid and cid type this command in cmd while the device is in download mode.
fastboot getvar all
side_flip15 said:
This is the specific thread for firmware update.
I think you can only flash the full stock zip since you are s-on. Do take note that flashing the stock firmware.zip will wipe your internal storage.
The firmware to flash should have matching CID and MID of your device.
To check your mid and cid type this command in cmd while the device is in download mode.
fastboot getvar all
Click to expand...
Click to collapse
Incorrect. All of @Sneakyghost's firmware.zips are for S-Off users only. It's stated in the OP of the thread right in the first sentence.
xunholyx said:
Incorrect. All of @Sneakyghost's firmware.zips are for S-Off users only. It's stated in the OP of the thread right in the first sentence.
Click to expand...
Click to collapse
Cheers,
Does anyone know the answers to any of the questions I've written?
sorry
side_flip15 said:
sorry
Click to expand...
Click to collapse
No reason to be sorry. You were trying to help, and I was just letting you know that it won't work for him.
---------- Post added at 06:16 PM ---------- Previous post was at 06:03 PM ----------
dladz said:
Does anyone know the answers to any of the questions I've written?
Click to expand...
Click to collapse
First make a backup. This will wipe your phone.
Then relock your bootloader. In fastboot fastboot oem lock
Download this RUU.zip
Rename the .zip to 2PS6IMG and place it onto your extSD
Boot to download mode and follow the prompts (vol up to flash ~ power button to reboot)
That's it. Super easy.
Delete the renamed .zip from your extSD or else every time you boot to download mode it'll try to update again.
Now unlock your bootloader again with the same bin code that HTC gave you when you first did it, or request a new one. Flash TWRP back onto your phone, then flash SuperSU or a custom ROM to regain root.
This is why I paid $25 for Sunshine.
For S-Off users, you just flash a small firmware package, and that's it. No data loss. No relocking the bootloader. No reflashing recovery. No re-rooting.
It really is worth the price in the amount of time and hassle saved through the lifetime of the phone.
xunholyx said:
No reason to be sorry. You were trying to help, and I was just letting you know that it won't work for him.
---------- Post added at 06:16 PM ---------- Previous post was at 06:03 PM ----------
First make a backup. This will wipe your phone.
Then relock your bootloader. In fastboot fastboot oem lock
Download this RUU.zip
Rename the .zip to 2PS6IMG and place it onto your extSD
Boot to download mode and follow the prompts (vol up to flash ~ power button to reboot)
That's it. Super easy.
Delete the renamed .zip from your extSD or else every time you boot to download mode it'll try to update again.
Now unlock your bootloader again with the same bin code that HTC gave you when you first did it, or request a new one. Flash TWRP back onto your phone, then flash SuperSU or a custom ROM to regain root.
This is why I paid $25 for Sunshine.
For S-Off users, you just flash a small firmware package, and that's it. No data loss. No relocking the bootloader. No reflashing recovery. No re-rooting.
It really is worth the price in the amount of time and hassle saved through the lifetime of the phone.
Click to expand...
Click to collapse
OK so this is where I've heard different.. There apparently isn't any need to return to stock so think you may need to read the originating post yourself mate
Otherwise how would the tool mentioned in the second post work? Appreciate you saying all that but it doesn't help my query.
As for sunshine I completely disagree, I've had every single htc bar two since the G1 and I've had S-off on all of them where available so I know the S-off method well, and have made a lot of donations to developers over the years, I also buy all my apps and support Devs when they deserve it for apps.
In regards to sunshine, I paid for this app for my m9 less than a year ago, I get one license, I can't use this for my 10 and I'll have another phone soon so see little point, they should offer more than one unlock for £25 and the only reason why they've got away with this daylight robbery is because they've monopolised the market, I'm sure I'm not the the only person who's noticed this.
Anyway, I'll wait to hear from someone who knows about the signed firmwares and how to install them. The tool can do it, so there must be a manual way, Id prefer to do that as I've had problems with tools in the past and with firmware you really want to get it right.
dladz said:
OK so this is where I've heard different.. There apparently isn't any need to return to stock so think you may need to read the originating post yourself mate
Otherwise how would the tool mentioned in the second post work? Appreciate you saying all that but it doesn't help my query.
As for sunshine I completely disagree, I've had every single htc bar two since the G1 and I've had S-off on all of them where available so I know the S-off method well, and have made a lot of donations to developers over the years, I also buy all my apps and support Devs when they deserve it for apps.
In regards to sunshine, I paid for this app for my m9 less than a year ago, I get one license, I can't use this for my 10 and I'll have another phone soon so see little point, they should offer more than one unlock for £25 and the only reason why they've got away with this daylight robbery is because they've monopolised the market, I'm sure I'm not the the only person who's noticed this.
Anyway, I'll wait to hear from someone who knows about the signed firmwares and how to install them. The tool can do it, so there must be a manual way, Id prefer to do that as I've had problems with tools in the past and with firmware you really want to get it right.
Click to expand...
Click to collapse
I think you misunderstood me. I'm sure there is a thread somewhere here with signed firmware (there is for M8), but I don't know of it. If I did, I would have linked you there.
But you asked if anyone could give you help, so I offered you a way to do it.
Even if you find a signed firmware.zip, you'll still need to re-lock your bootloader since you are S-On.
You might as well save some time searching and just run the RUU
xunholyx said:
I think you misunderstood me. I'm sure there is a thread somewhere here with signed firmware (there is for M8), but I don't know of it. If I did, I would have linked you there.
But you asked if anyone could give you help, so I offered you a way to do it.
Even if you find a signed firmware.zip, you'll still need to re-lock your bootloader since you are S-On.
You might as well save some time searching and just run the RUU
Click to expand...
Click to collapse
I'll check around, was speaking with @LeeDroid a while ago, can't remember him saying relock the bootloader, I'll ask him.
I'm pretty sure there is a way. Can't see that tool in the second post relocking your bootloader.
dladz said:
I'll check around, was speaking with @LeeDroid a while ago, can't remember him saying relock the bootloader, I'll ask him.
I'm pretty sure there is a way. Can't see that tool in the second post relocating your bootloader.
Click to expand...
Click to collapse
Actually, I have been following the method of @krassermensch's since before he started a thread about it. He posted to a different firmware thread about the method, and I've been curious about it since. In his OP he states that you need an unlocked bootloader, so his method is probably your best solution. I haven't tried it myself as I have always been S-Off on my HTC phones.
dladz said:
Have come mate, but I've asked some other things plus there is apparently a way to do it without the use of a tool.
Click to expand...
Click to collapse
My tool is on GitHub, read the content of the batch files and you know how to do it
https://github.com/nico151999/Firmware-Update-Tool-HTC10
krassermensch said:
My tool is on GitHub, read the content of the batch files and you know how to do it
https://github.com/nico151999/Firmware-Update-Tool-HTC10
Click to expand...
Click to collapse
Thanks :good:
xunholyx said:
Actually, I have been following the method of @krassermensch's since before he started a thread about it. He posted to a different firmware thread about the method, and I've been curious about it since. In his OP he states that you need an unlocked bootloader, so his method is probably your best solution. I haven't tried it myself as I have always been S-Off on my HTC phones.
Click to expand...
Click to collapse
yea same here man, looking at the tools code it seems that it asks you to back up first.
I'll check it out in the morning.
Thanks chaps
dladz said:
yea same here man, looking at the tools code it seems that it asks you to back up first.
I'll check it out in the morning.
Thanks chaps
Click to expand...
Click to collapse
The backup is necessary as the firmware update files overwrite the recovery and the boot partitions...
Hi all,
My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.
It might be worth mentioning it boots into extreme power saving mode too.
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
Click to expand...
Click to collapse
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.
carljames0603 said:
It is stock. Tried to root it but it didn't take.
Click to expand...
Click to collapse
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.
Always provide as many details as possible when asking for help and answering our questions.
carljames0603 said:
Don't know which version as it is stuck in a loop currently.
Click to expand...
Click to collapse
If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).
From there, tell us what OS number it says on the bootloader screen, near the top.
carljames0603 said:
It seems to me this is a hardware problem though.
Click to expand...
Click to collapse
What makes you think that? You haven't provided any details or evidence that would support the statement.
Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.
The OS is 3.28.605.4
carljames0603 said:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process.
Click to expand...
Click to collapse
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
redpoint73 said:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
Click to expand...
Click to collapse
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked, and it stays there until I push it to reboot.
carljames0603 said:
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked.
Click to expand...
Click to collapse
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
carljames0603 said:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Click to expand...
Click to collapse
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
redpoint73 said:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
Click to expand...
Click to collapse
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
did you read the post you quoted ?
redpoint73 said clearly what you need and where to find
you used a different RUU and it will not accepted by your device ( in red above )
carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app.
Click to expand...
Click to collapse
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
carljames0603 said:
(RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
redpoint73 said:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
Click to expand...
Click to collapse
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
carljames0603 said:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
Click to expand...
Click to collapse
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.
Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your posts is not the same as attacking a person (which you did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).
You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.
Hi, i am new to rooting and modding and i want to get away the warning message on my oneplus5t that remember me everrytime i turn it on i have a unlocked bootloader.
Is there a way to do it? I want to change also the boot animation becouse is cool but with this message is horrible, i want to remove it before changing the boot animation.
Can someone help me to find a solution? I searched and i found is not removable yet i just wanted to make sure is 100% impossible to do it
I know, it's horrible but impossible to remove ...
asnachan said:
Hi, i am new to rooting and modding and i want to get away the warning message on my oneplus5t that remember me everrytime i turn it on i have a unlocked bootloader.
Is there a way to do it? I want to change also the boot animation becouse is cool but with this message is horrible, i want to remove it before changing the boot animation.
Can someone help me to find a solution? I searched and i found is not removable yet i just wanted to make sure is 100% impossible to do it
Click to expand...
Click to collapse
You should use the Questions & Answers section. This is for original development only
There is no way as the bootloader is locked down. There was some guy claiming to be able to do this but it was just a hoax or a developer not knowing enough on this topic.
For the bootanimation there should be a bootanimation.zip in /system/media. That needs to be replaced.
Thanks and sorry if i putted this topic here
I will have always this **** when i boot it up so, damn oneplus
Silvio Scarani said:
I know, it's horrible but impossible to remove ...
Click to expand...
Click to collapse
un altro italiano
Macusercom said:
You should use the Questions & Answers section. This is for original development only
There is no way as the bootloader is locked down. There was some guy claiming to be able to do this but it was just a hoax or a developer not knowing enough on this topic.
For the bootanimation there should be a bootanimation.zip in /system/media. That needs to be replaced.
Click to expand...
Click to collapse
What are you talking about, at the top of the site it says;
xda-developers > OnePlus 5T > OnePlus 5T Questions & Answers.
I just got the OnePlus 5T, my understanding is it's the same on this phone as some others, the boot loader message is low level, more like in the boot image, and the bootanimation.zip is just the splash images.
DoR3M3 said:
What are you talking about, at the top of the site it says;
xda-developers > OnePlus 5T > OnePlus 5T Questions & Answers.
I just got the OnePlus 5T, my understanding is it's the same on this phone as some others, the boot loader message is low level, more like in the boot image, and the bootanimation.zip is just the splash images.
Click to expand...
Click to collapse
It was moved to this section by a mod.
Macusercom said:
It was moved to this section by a mod.
Click to expand...
Click to collapse
Ahh my bad...
You have to sign boot.img and recovery.img to remove the warning.
I have managed to eliminate it by signing those two images.
In my oneplus 5 and 5t I have twrp installed and with rom lineageos without warning.
Who wants to try to send me your boot and recovery and return it for you to try.
Remember that you have to close the bootloader whereby the phone will be wipe
Process:
fastboot oem unlock
unlock bootloader
You have to go back to fastboot mode
fastboot flash boot boot.img
fastboot recovery recovery_name.img
fastboot oem lock
Wuala
It can be done in any rom from firmware 5.1.5
superatmel said:
You have to sign boot.img and recovery.img to remove the warning.
I have managed to eliminate it by signing those two images.
In my oneplus 5 and 5t I have twrp installed and with rom lineageos without warning.
Who wants to try to send me your boot and recovery and return it for you to try.
Remember that you have to close the bootloader whereby the phone will be wipe
Process:
fastboot oem unlock
unlock bootloader
You have to go back to fastboot mode
fastboot flash boot boot.img
fastboot recovery recovery_name.img
fastboot oem lock
Wuala
It can be done in any rom from firmware 5.1.5
Click to expand...
Click to collapse
Although the above procedure may work, I wouldn't suggest locking the bootloader after making changes like this.
xocomaox said:
Although the above procedure may work, I wouldn't suggest locking the bootloader after making changes like this.
Click to expand...
Click to collapse
Because no, you avoid the annoying message, you enjoy your own kernel and the recovery you want, do you mean that you are going to send some malicious files?
I've been with Android for many years to get my reputation for it. : =
---------- Post added at 09:13 PM ---------- Previous post was at 09:12 PM ----------
[ro.boot.verifiedbootstate]: [green]
[ro.boot.veritymode]: [enforcing]
[ro.bootimage.build.date]: [Fri Sep 28 02:08:12 CEST 2018]
[ro.bootimage.build.date.utc]: [1538093292]
[ro.bootimage.build.fingerprint]: [OnePlus/OnePlus5T/OnePlus5T:8.1.0/OPM1.171019.011/1808081927:user/release-keys]
[ro.bootloader]: [unknown]
[ro.bootmode]: [normal]
[ro.build.date.utc]: [1538093292]
[ro.build.description]: [OnePlus5T-user 8.1.0 OPM1.171019.011 1808081927 release-keys]
[ro.build.display.id]: [superteam_dumpling-userdebug 8.1.0 OPM6.171019.030.K1 b8192e9518 test-keys]
[ro.build.expect.firmware]: [5.1.5]
[ro.build.expect.modem]: [2018-08-08 20:13:31]
[ro.build.fingerprint]: [OnePlus/OnePlus5T/OnePlus5T:8.1.0/OPM1.171019.011/1808081927:user/release-keys]
[ro.build.flavor]: [superteam_dumpling-userdebug]
[ro.build.host]: [Asus-Rog]
[ro.build.id]: [OPM6.171019.030.K1]
[ro.build.product]: [OnePlus5T]
[ro.build.selinux]: [0]
[ro.build.selinux.enforce]: [0]
[ro.build.tags]: [test-keys]
[ro.build.type]: [userdebug]
[ro.build.user]: [superatmel]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [b8192e9518]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [8.1.0]
[ro.build.version.sdk]: [27]
[ro.build.version.security_patch]: [2018-09-05]
---------- Post added at 09:27 PM ---------- Previous post was at 09:13 PM ----------
In this post it is asked how to eliminate the warning in the boot, I have offered to help to remove it nothing more, since in my terminals it eliminates it.
No words are needed
https://www.youtube.com/watch?v=Bzfd-dKgpes&feature=youtu.be
superatmel said:
No words are needed
https://www.youtube.com/watch?v=Bzfd-dKgpes&feature=youtu.be
Click to expand...
Click to collapse
You're locking the bootloader...
3:58 in Video; fastboot oem lock.
Not exactly the solution people are looking for.
DoR3M3 said:
You're locking the bootloader...
3:58 in Video; fastboot oem lock.
Not exactly the solution people are looking for.
Click to expand...
Click to collapse
Of course, that's the idea of locking the bootloader again to avoid the message.
Try locking it with a boot.img or recovery that is not signed to see what happens
my getprop
[ro.boot.verifiedbootstate]: [green]
bootloader locked+boot signed NO WARNING MESSAGE
[ro.boot.verifiedbootstate]: [orange]
bootloader unlocked+boot unsigned WARNING MESSAGE
[ro.boot.verifiedbootstate]: [red]
bootloader locked+boot unsigned SYSTEM CORRUPT, NOT BOOT
So you need to have the bootloader unlocked if you have already put any rom, any boot or any recovery on your phone?
The bootloader can not be edited but to avoid the warning message if boots and recoverys can be signed
superatmel said:
No words are needed
https://www.youtube.com/watch?v=Bzfd-dKgpes&feature=youtu.be
Click to expand...
Click to collapse
superatmel said:
Of course, that's the idea of locking the bootloader again to avoid the message.
Try locking it with a boot.img or recovery that is not signed to see what happens
my getprop
[ro.boot.verifiedbootstate]: [green]
bootloader locked+boot signed NO WARNING MESSAGE
[ro.boot.verifiedbootstate]: [orange]
bootloader unlocked+boot unsigned WARNING MESSAGE
[ro.boot.verifiedbootstate]: [red]
bootloader locked+boot unsigned SYSTEM CORRUPT, NOT BOOT
So you need to have the bootloader unlocked if you have already put any rom, any boot or any recovery on your phone?
The bootloader can not be edited but to avoid the warning message if boots and recoverys can be signed
Click to expand...
Click to collapse
I understand these things, but are you asking, or telling?
People want to keep the bootloader unlocked to hack on their phones, and locking it defeats this purpose.
The post is about trying to keep the bootloader unlocked and remove the message, but as I mentioned before, it's my understanding it's deep within the bootloader process, not an easy thing to get at, hack away. Also it seems, because of some Google Policy it's pushing on the phone manufacturers to have, as a requirement to their agreement with Google, at least it's what I've come to understand.
DoR3M3 said:
I understand these things, but are you asking, or telling?
People want to keep the bootloader unlocked to hack on their phones, and locking it defeats this purpose.
The post is about trying to keep the bootloader unlocked and remove the message, but as I mentioned before, it's my understanding it's deep within the bootloader process, not an easy thing to get at, hack away. Also it seems, because of some Google Policy it's pushing on the phone manufacturers to have, as a requirement to their agreement with Google, at least it's what I've come to understand.
Click to expand...
Click to collapse
I am saying.
But people do not need to have the bootloader unlocked to hack their phones. In fact I do not want to be hacked, but I do want to modify my boots to add things to the system. and also get not having the message at the start of the system
An example that for example I want
I would like to have the kernel blur but if I put it I have the warning message.
Solution:
I sign the blur kernel, I install it I close the bootloader and I have the kernel working and I do not have a warning message
Does not it help you to autopirate your phone?
---------- Post added at 01:32 AM ---------- Previous post was at 01:28 AM ----------
I could now have oxygen os 5.1.5 or higher with modified kernel, recovery twrp, add xposed modules and closed bootloader.
It's not useful?
superatmel said:
I am saying.
But people do not need to have the bootloader unlocked to hack their phones. In fact I do not want to be hacked, but I do want to modify my boots to add things to the system. and also get not having the message at the start of the system
An example that for example I want
I would like to have the kernel blur but if I put it I have the warning message.
Solution:
I sign the blur kernel, I install it I close the bootloader and I have the kernel working and I do not have a warning message
Does not it help you to autopirate your phone?
---------- Post added at 01:32 AM ---------- Previous post was at 01:28 AM ----------
I could now have oxygen os 5.1.5 or higher with modified kernel, recovery twrp, add xposed modules and closed bootloader.
It's not useful?
Click to expand...
Click to collapse
Well, it's always been my understanding, that if someone is always tinkering, playing with their phone, constantly flashing roms, kernels, etc., then keeping the bootloader unlocked is simpler.
I personally just got the OnePlus 5T, so I don't know if it's doing something different here over other devices, where you can simply lock it on a custom rom and have it boot ok.
It's suppose to be from my understanding that some devices you can lock it, and everything works ok, and other devices, where if you lock it, it wipes all data and encrypts it over, then the rom boots up all wiped, and I'm talking Internal Storage all gone, everything wiped, not a situation good. Locking bootloader on some devices means, loose all data.
So the safest route amongst all devices is to simply leave it unclocked, and getting hacked by someone with an unlocked bootloader, isn't very likely to happen.
DoR3M3 said:
Well, it's always been my understanding, that if someone is always tinkering, playing with their phone, constantly flashing roms, kernels, etc., then keeping the bootloader unlocked is simpler.
I personally just got the OnePlus 5T, so I don't know if it's doing something different here over other devices, where you can simply lock it on a custom rom and have it boot ok.
It's suppose to be from my understanding that some devices you can lock it, and everything works ok, and other devices, where if you lock it, it wipes all data and encrypts it over, then the rom boots up all wiped, and I'm talking Internal Storage all gone, everything wiped, not a situation good. Locking bootloader on some devices means, loose all data.
So the safest route amongst all devices is to simply leave it unclocked, and getting hacked by someone with an unlocked bootloader, isn't very likely to happen.
Click to expand...
Click to collapse
Sorry but I think you do not understand.
Your unlocked bootloader phone is vulnerable since it is ready for any option.
Mine to have it closed my data is safe because if someone opens it is completely deleted.
My phone with a oneplus recovery stock signed by me and a custom boot plus system modifications and closed bootloader is completely safe.
superatmel said:
Sorry but I think you do not understand.
Your unlocked bootloader phone is vulnerable since it is ready for any option.
Mine to have it closed my data is safe because if someone opens it is completely deleted.
My phone with a oneplus recovery stock signed by me and a custom boot plus system modifications and closed bootloader is completely safe.
Click to expand...
Click to collapse
Sorry for any misunderstanding, I understand about the bootloader.
My mistake, I wasn't paying attention that you signed your own image. Did you sign both the recovery and boot?
Now you signed the images, but you locked the bootloader and it's my understanding that if signed, you could get rid of the message and still leave it unlocked. So with your signed images, can you leave it unlocked and the message is gone?
DoR3M3 said:
Sorry for any misunderstanding, I understand about the bootloader.
My mistake, I wasn't paying attention that you signed your own image. Did you sign both the recovery and boot?
Now you signed the images, but you locked the bootloader and it's my understanding that if signed, you could get rid of the message and still leave it unlocked. So with your signed images, can you leave it unlocked and the message is gone?
Click to expand...
Click to collapse
Exactly, now you understand it. I sign boot.img and recovery.img and with that I can close the bootloader and the message disappears. That's what you see in the video.
Install twrp signed by me, lineageos latest version, extract by boot.img and sign it, so at the end of the whole I integrate the boot.img and then I close the bootloader
I have put lineageos to put something, but I create my own systems