[note] read before posting all kitkat users - Droid RAZR M General

Dear, friends who got the latest ota update.
Note these things before posting:
1: if you took the latest OTA then you CANNOT root or unlock bootloader
2: if you got bricked at update latest OTA , then simply you can't unbrick at situation
3: their is such NO solution for battery problems of KitKat (only greenify works)
4: if you have bootloader unlocked and want to go back then Check pinned post.
5: Before Posting, always check forum because a lot peoples already asked questions about kitkat
6: You CANNOT install custom recovery if you don't have BL already unlocked.
Thank you!

future official updates????4.4.4
will our device got future official updates?

livecouk said:
Dear, friends who got the latest ota update.
Note these things before posting:
1: if you took the latest OTA then you CANNOT root or unlock bootloader
2: if you got bricked at update latest OTA , then simply you can't unbrick at situation
3: their is such NO solution for battery problems of KitKat (only greenify works)
4: if you have bootloader unlocked and want to go back then Check pinned post.
5: Before Posting, always check forum because a lot peoples already asked questions about kitkat
6: You CANNOT install custom recovery if you don't have BL already unlocked.
Thank you!
Click to expand...
Click to collapse
*1) latest update being 182/183.46.15
*2) if you brick (as I believe you are referring to a soft brick where you can still access fast boot) on 182/183.46.15 you can "unbrick" it the same as you would for any other system firmware we have had (I believe).. Download whatever version you were on and flash it via rsd lite...
*4) you could grab and post the link if you want...
*5&6) is valid for most everything here on XDA
iamankit said:
will our device got future official updates?
Click to expand...
Click to collapse
It is highly unlikely maybe minor bug fixes but even that is unlikely
We cannot teach people anything; we can only help them discover it within themselves.

dbreezy187 said:
*1) latest update being 182/183.46.15
*2) if you brick (as I believe you are referring to a soft brick where you can still access fast boot) on 182/183.46.15 you can "unbrick" it the same as you would for any other system firmware we have had (I believe).. Download whatever version you were on and flash it via rsd lite...
*4) you could grab and post the link if you want...
*5&6) is valid for most everything here on XDA
It is highly unlikely maybe minor bug fixes but even that is unlikely
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
NO. latest KitKat ota is only 182/183.186.15 so no need to mention --_-......I think u can't unbrick device if you don't have unlocked bootloader ain't am right?

livecouk said:
NO. latest KitKat ota is only 182/183.186.15 so no need to mention
Click to expand...
Click to collapse
There is no such version.
As dbreezy187 mentioned, the latest OTA is 182/183.46.15.
livecouk said:
I think u can't unbrick device if you don't have unlocked bootloader ain't am right?
Click to expand...
Click to collapse
It depends on the brick, but for most of them you can.

livecouk said:
NO. latest KitKat ota is only 182/183.186.15 so no need to mention --_-......I think u can't unbrick device if you don't have unlocked bootloader ain't am right?
Click to expand...
Click to collapse
Its always best to put which update you are referring to I have learned as if another update is pushed when someone comes across this post in the future it may be confusing to them...most of the bricks that occurs on here can be fixed by a simply flash of the current firmware.. If you are flashing the firmware you are on the bootloader status is irrelevant
We cannot teach people anything; we can only help them discover it within themselves.

dbreezy187 said:
Its always best to put which update you are referring to I have learned as if another update is pushed when someone comes across this post in the future it may be confusing to them...most of the bricks that occurs on here can be fixed by a simply flash of the current firmware.. If you are flashing the firmware you are on the bootloader status is irrelevant
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Hmmmm yeh its right. But my post is ruined now :/

Related

How to change status ROOTED to UNROOTED on Download Mode ?

Hi,
this is from G2 anyone can try it on G3 and update us what he did ?
I being told try to delete rct file .
http://forum.xda-developers.com/showthread.php?t=2715114
Q:
If i flash to other frimware from other contry on the same Model when i got update it will update to the orignal Ver. of where i did buy the device?
if it does can i dod somting to Prevent it to get update to only the contry i did flash it on Purpose?
Anyone?
jcase said:
These questions are outside the scope of what I will be covering, and are not frequently asked.
Click to expand...
Click to collapse
but where i can found that Answers ?
it will be much easier if it will be in the 1st post or the 2 post,
to prevent repetitive questions...
u1988 said:
@jcase
Thank you!
can you please add more info to your FAQ ?
*like will i get updates with FOTA or LG Mobile Phone ?
*there is any way to get updates with out flash new Ver. ?
*unroot will work with Super SU or i need to install Stump again?
*The root will change status to ROOTED in Download Mode?
can you chack this out if it will work on G3 too UNROOTED with this?
http://forum.xda-developers.com/lg-g3/help/how-to-change-status-rooted-to-unrooted-t2850096
Click to expand...
Click to collapse
u1988 said:
but where i can found that Answers ?
it will be much easier if it will be in the 1st post or the 2 post,
to prevent repetitive questions...
Click to expand...
Click to collapse
Answering for the team so if the guys want to correct me, feel free, just attempting to head off more distracting lines of "not" frequently asked questions. THANKS FELLAS!
1. YES, this is simply a method of gaining root, nothing more, nothing less. Your FOTA will likely fail OR worse due to a) being rooted and failing checks or b) system changes you may or may not make after you ROOT but this is a "Method TO ROOT" so again, nothing more, nothing less. (Question is out of scope)
2. NO, why would you even want to get an updated root method app that you are supposed to uninstall after you have rooted? (Question doesn't really make much sense)
3. NO CLUE and out of scope, this is a "Method TO ROOT", nothing more, nothing less.
4. Probably but if you want to help, you tell @jcase but it's out of scope and as an exploit creator, not really his/the teams deal or worry.
5. Out of scope, this is a "Method TO ROOT", nothing more, nothing less.
Good day to ya... :good:
What device model do you have? Carrier (I assume AT&T)?
TonyStark said:
What device model do you have? Carrier (I assume AT&T)?
Click to expand...
Click to collapse
for any G3 model , but right now D855

Remove bump(twrp)+ unroot

Hi guys
I installed [ROM] AndroidNow HD 1.7 G3 D855 [V10L/support ART] on my LG G3 via BUMP(TWRP)
Now I want to know if there is any way to install STOCK ROM back(this one which was on phone when I get it) If answer is yes, where do I get flash file for it?
Also can I unroot and remove BUMP ? I'm asking because of warranty...Thank you
you have NO warranty as you have flashed a custom rom/recovery and rooted (depending on country and/or fault with device) also use the search button as this has already been covered plenty.
Kl3m3n_G3 said:
Hi guys
I installed [ROM] AndroidNow HD 1.7 G3 D855 [V10L/support ART] on my LG G3 via BUMP(TWRP)
Now I want to know if there is any way to install STOCK ROM back(this one which was on phone when I get it) If answer is yes, where do I get flash file for it?
Also can I unroot and remove BUMP ? I'm asking because of warranty...Thank you
Click to expand...
Click to collapse
flash kdz with lg flash tool and you are unrooted with stock recovery
your latest kdz get you from here.
flash tool from here.
vesspa08 said:
you have NO warranty as you have flashed a custom rom/recovery and rooted (depending on country and/or fault with device) also use the search button as this has already been covered plenty.
Click to expand...
Click to collapse
I simply dont care who u are but there is absolutely no need to be such a butt hole about it if u are not going to help the guy out.. The other guy above me gave the link for getting both kdz and lg flash tool. We need more people like him and not a arrogant ..
vesspa08 said:
you have NO warranty as you have flashed a custom rom/recovery and rooted (depending on country and/or fault with device)
Click to expand...
Click to collapse
so what? does he have warranty or not?
you don`t know the fault and you don`t know the warranty restrictions of slovenia (europe) in this case.
please tell only facts about warranty and no assumptions. thanks.
paratox said:
so what? does he have warranty or not?
you don`t know the fault and you don`t know the warranty restrictions of slovenia (europe) in this case.
please tell only facts about warranty and no assumptions. thanks.
Click to expand...
Click to collapse
technically you void the warranty by modifying the phone, however, there are arguments especially in the EU that a software fault cannot breach the warranty for faulty hardware etc.
also if you flash back to stock they have no way of knowing what you did, also from experience they tend to not care anyway.
Thank you guys for all your answers to my question.
Specially to the guy , who gave me the link to the KDZ image file and FLASH tool.
I will try to restore my LG G3 back to STOCK ROM because of update to android L(Lolipop).
Kl3m3n_G3 said:
Thank you guys for all your answers to my question.
Specially to the guy , who gave me the link to the KDZ image file and FLASH tool.
I will try to restore my LG G3 back to STOCK ROM because of update to android L(Lolipop).
Click to expand...
Click to collapse
If you are returning to stock only for the Lollipop update you might want to just wait because I'm sure we'll have a working Bump'd port by the time LG starts rolling out the update near the end of this year. That being said, you may still receive the update before us, but Autoprime and TheCubed have warned us not to take OTA updates because Qualcomm is rolling out its anti-rollback updates soon that may prevent you from ever unlocking this phone again and may make you lose root for a long time. I'm sure that LG is working on patching Bump in the 5.0 update so just be warned that you may never get a custom recovery on this phone again if you choose to take the official update. I am relying on the devs here to get us a Bump'd version so I can keep this beast free. That's just my two cents and it's your decision I just wanted to warn you about the risk. Have a good day man!
Thank you for your answer. Yes I heard about this news(qualcom,..) but I will go back to stock, after that I will ROOT my phone again and install BUMP. Do you have any information about when the BUMP tool will be released so cyanogenmod and other ROM's will come?
EDIT: Will this method also work: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html ?
Kl3m3n_G3 said:
Thank you for your answer. Yes I heard about this news(qualcom,..) but I will go back to stock, after that I will ROOT my phone again and install BUMP. Do you have any information about when the BUMP tool will be released so cyanogenmod and other ROM's will come?
EDIT: Will this method also work: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html ?
Click to expand...
Click to collapse
i think it will work but i find the method with lg flash tool 2014 and kdz easier because you dont have to set so "many" things
As the original question has been answered and there are existing threads for any follow up's ....
I have closed the thread

help phone wont boot into recovery and system after using blankflash

so i was flashing a nougat 7.0 update on moto z play and then all of a sudden my phone wouldnt even power on the screen was all black so i decided to use blank flash. Blank flash did take me to the bootloader but even when trying to boot to recovery and system it wont work.
help plz.
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
what do you mean
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
ahmed12389 said:
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
Click to expand...
Click to collapse
Do you see the device listed in Windows?
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
yes I can see it
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
what do you suggest I do
ahmed12389 said:
what do you suggest I do
Click to expand...
Click to collapse
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
Yes I have flashed stock firmware on my device I remember downgrading to marshmallow then updating back to nougat then my device fully shut down it was all black. After this incident, i did what you would normally do and that was to use blank flash to at least get the bootloader back, as I did get the bootloader I could not use the boot options such as recovery mode. so I am basically stuck on the bootloader and can do nothing. My device is an addison XT1635-02 and before I flashed nougat ota I had the marshmallow December security update.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
I also believe my device is hard bricked as I cant access boot options at all it just keeps boot looping once I try to access a boot option. also is it normal for my bootloader to say that my software status is modified because I think after you flash blank flash your software status modified. finally, I have been trying to flash stock firmware but for some reason, gpt and bootloader.img always fail to flash. Thanks for the reply I hope you can help.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
ahmed12389 said:
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
Click to expand...
Click to collapse
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
ok the thing is I am certain I used the wrong blank flash zip therefore meaning that I flashed the wrong things this is probably why I'm boot looping do you have any idea how to revert the changes of blank flash so I can flash the propper blank flash. Is their even any blank flash for Moto z play anyways
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I was flashing the July security patch stock firmware and it's giving me these errors
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
if i flash that stock frimware it takes straight to 7.1.1 is that correct
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
ahmed12389 said:
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
Click to expand...
Click to collapse
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
ahmed12389 said:
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
Click to expand...
Click to collapse
If your device was ever on stock Nougat (7.0 or 7.1.1), then flashing that marshmallow ROM won't likely work in repairing your bootloader. You need a firmware that is the same or newer than the latest firmware your device had. Downgrading stock firmware does not usually downgrade your bootloader, hence the corruption and need to have same or newer firmware to repair. Your bootloader would otherwise reject old firmware via preflash validation errors.
Hopefully the 7.1.1 firmware will help fix things. You will lose data however in the process of flashing your device, so hopefully you have backups.
echo92 said:
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
Click to expand...
Click to collapse
oh my freaking god you fixed it!!! you are literraly my idol thanks to you i dont need to take it to service from now on I'm never flashing again. but thank you very much you fixed my phone you absolute legend.
ahmed12389 said:
what do you mean
Click to expand...
Click to collapse
how is it recognized by the PC in device manager?

Does the 7x have a/b partitions?

I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
I Could Be Dead Wrong But..
epickid37 said:
I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
Click to expand...
Click to collapse
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
RaiderWill said:
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
Click to expand...
Click to collapse
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Damn.. It's Been So Long..
epickid37 said:
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Click to expand...
Click to collapse
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
RaiderWill said:
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
Click to expand...
Click to collapse
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
A Virgin...
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
When It Comes To Huawei.. I'm A Virgin...
Every other phone I've seen, the O.T.A. will notify you that your system has been "Modified" and will not attempt the update.
When you root.. Your Phone Becomes Insecure.. and is vernable to Malware, Virus, Hacks and god knows what else.
O.T.A.'s are Signed Packages.. They Ain't Going To Da Hood To Do Business...
Keep it locked if you want everything on day 1.. Then you can Root to your hearts content.
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
epickid37 said:
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
Click to expand...
Click to collapse
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Ah, ok. Thank for your help!

Will my H812 have less problems on lollipop?

This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
shatheone said:
This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
Click to expand...
Click to collapse
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
sdembiske said:
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
Click to expand...
Click to collapse
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
shatheone said:
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
Click to expand...
Click to collapse
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
sdembiske said:
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
Click to expand...
Click to collapse
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
shatheone said:
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
Click to expand...
Click to collapse
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
sdembiske said:
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
Click to expand...
Click to collapse
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
sdembiske said:
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
Click to expand...
Click to collapse
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
shatheone said:
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
Click to expand...
Click to collapse
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
sdembiske said:
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
Click to expand...
Click to collapse
if you took 10 seconds, you would see i actually posed in that thread. and all they did was direct me to the OP which says nothing about lineageos working for h812, or that the h815/ or h811 roms work for this variant. all it says is that i can flash nougat based roms. so the thread isnt too helpful, im not sure why you think it is.
shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
Hey man, i'm agreeing with you for most of this...
I'm also not going to risk anything until 10 H812 users have successfully unlocked bootloader and flashed a custom rom (one thats intended for h815 or h811) with steadfasterx's method. Maybe you can flash H815 custom roms once the bootloader is unlocked... but just to be safe, let's flash other stock carrier firmwares in the meantime...... in the end no matter what anyone says, its your phone at risk...
Member TheLatios381 and I were asking same question here:https://forum.xda-developers.com/g4...10-q2-2017-t3567402/post75742903#post75742903 because no answer to our question on steadfasterx's thread...

Categories

Resources