Related
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Zugshad said:
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Click to expand...
Click to collapse
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
XxZombiePikachu said:
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
Click to expand...
Click to collapse
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Zugshad said:
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Click to expand...
Click to collapse
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
XxZombiePikachu said:
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
Click to expand...
Click to collapse
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Zugshad said:
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Click to expand...
Click to collapse
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
XxZombiePikachu said:
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
Click to expand...
Click to collapse
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
edit... ok that is the ota file.... thanks again )
Zugshad said:
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
Click to expand...
Click to collapse
yep that should be it; just delete and goodbye updates should stop working as a whole (if you want to get tibu to freeze you can always log in with your play account on her device and download the pro version)
edit: just noticed you solved it
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
davidpage said:
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
Click to expand...
Click to collapse
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
venu123 said:
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
Click to expand...
Click to collapse
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
davidpage said:
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
Click to expand...
Click to collapse
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
venu123 said:
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
Click to expand...
Click to collapse
Thanks for the links. I tried what they suggested but during the update it says the following:
Installing update...
Verifying current system...
"/system/xbin/dexdump" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What should I do now? Seems more complicated than I'd like it to be
Nope, OTA is a no go on your phone. Flash the factory image.
updating to Lollipop
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Prettygrim said:
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Click to expand...
Click to collapse
Do you have a custom recovery? CWM gives that untrusted package message if you have signature verification turned on. If yes, you need to revert to stock and also unroot. Supersu does have the option of unrooting so you could try that. You could check out the toolkit, at least it can be used for backing up your data to the PC.
tnx for the info, venu123. progress made so far. i downloaded the Lollipop image and put it into the folder within Android Toolkit. i then let it do it's thing. the phone is now updated but i am struggling to get root again and also need some instructions on how to get it to sync again as a lot of the apps i had on the phone are not there now. anyone able to help with this please?
gonna have another try to get root on the phone. if successful, willpost back
---------- Post added at 08:12 PM ---------- Previous post was at 07:47 PM ----------
ok then. Android Toolkit didn't work. i can only assume that it's something to do with the Lollipop image not being in the program. however, i did get root by using the latest wugfresh app. many tnx to you for your efforts, wugfresh.
the one thing left for me to do now is somehow get the apps i had before the Lollipop update on the phone again. any help would be great, as i cant even see an option to sync the phone.
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
Is there a way to flash without wiping my data? Clearing my data is the last thing I'd want to do and, if this is unavoidable, I might just stay put.
I have a thought: since the message is telling me that dexdump has unexpected contents (that file actually doesn't seem to be there, as I've just checked), is it possible to just replace this file to bypass the problem? Thing is I cannot find this file anywhere for download.
Nevermind.. I copied that file from the factory image and the installation went smoothly!
Ive tried to root my phone and cant seem to get it to root. I have 4.4.2 version VS98026A kernel 3.4.0 perf g95fa932. I firsted installed united drivers, enabled debugging, put phone on internet/ethernet, and allowed unknown sources. Then:
I tried Kingo root first. It failed. Tried several times, it said my phone was connected, but when I clicked root, the program got stuck in a loop.
I then tried ioroot25. After clicking root, it wold get to the initial prompt, I pressed a key to continue the phone wold restart and there'd be a greed robot with his gut open and a red exclamation. After sitting awhile, the phone would restart and then after trying again, the same thing would happen.
I then tried towelroot. I went to towelroot.com, downloaded the file, renamed it tr.apk... opened it, installed it, clicked make it rain, and then it said my phone wasnt supported.
What program should I be using, and can anyone assist?
THanks. I apologize if I havnt dont things correctly, I'm very new to this. I appreciate any help.
Did you do every step using ioroot? http://forum.xda-developers.com/showpost.php?p=48709232 follow this thread
Step 2 doesn't happen. It says something about damean tools, restarts my phone and a green robot with his gut open shows up. And the program essentially terminates.
mistachy said:
Step 2 doesn't happen. It says something about damean tools, restarts my phone and a green robot with his gut open shows up. And the program essentially terminates.
Click to expand...
Click to collapse
is your phone connected as a adb device?
Krenol said:
is your phone connected as a adb device?
Click to expand...
Click to collapse
I followed the instructions and did the initial things listed in my first post, and my phone does say im connected as an installer... but how do i verify that i am connected as a adb device?
Personally, i would kdz back to stock, then use towleroot. Make it rain!
As stated in my first post, towel root isn't working. Says phone not supported.
It seems that ioroot25 is not compatible with 26A. Has anyone had any experience with stomp root?
mistachy said:
It seems that ioroot25 is not compatible with 26A. Has anyone had any experience with stomp root?
Click to expand...
Click to collapse
If so then just flash a suitable kdz for rooting and root your device follow the steps for back to stock after root and you are good to go (hopefully)
Edit: thread: http://forum.xda-developers.com/showthread.php?t=2797190
Make sure you flash the right Version (there is a d802 and a d802T !) And the right storage version
Krenol said:
If so then just flash a suitable kdz for rooting and root your device follow the steps for back to stock after root and you are good to go (hopefully)
Edit: thread: http://forum.xda-developers.com/showthread.php?t=2797190
Make sure you flash the right Version (there is a d802 and a d802T !) And the right storage version
Click to expand...
Click to collapse
ThrThee issue im having is a master reset was done and i need to recover data lost. If i reflash, i run the risk of writing over that unused space and losing that data permanently .
I don't understand hat you mean. You can easily backup your data on your computer and then use the flash tool and then put the data back on your pone
Krenol said:
I don't understand hat you mean. You can easily backup your data on your computer and then use the flash tool and then put the data back on your pone
Click to expand...
Click to collapse
A master reset was done, the data was deleted. So i have to run recovery software to scan tge hardrive. If i start using space on the hard drive, i run the risk of overwriting it and losing it permanently.
are you talking about your pc oder your phone?
Krenol said:
are you talking about your pc oder your phone?
Click to expand...
Click to collapse
I have only been talking about the phone.
then try to restore your data and then follow my steps. the recovery you are flashing after root is not capable of restoring deleted data
Krenol said:
then try to restore your data and then follow my steps. the recovery you are flashing after root is not capable of restoring deleted data
Click to expand...
Click to collapse
Recovery software deep scans for raw content and deleted data, so thats why i cant flash, as flashing could write over data thats alrwady been deleted. I must do a root then scan the phone. Thats my only option, to root the current firmware.
aaah now I understand your point. So the scan software needs root access... mhm. Which phone model do you have?
mistachy said:
Ive tried to root my phone and cant seem to get it to root. I have 4.4.2 version VS98026A kernel 3.4.0 perf g95fa932.
Click to expand...
Click to collapse
This one, LG g2
no the variant, i have the d802 for example
Krenol said:
no the variant, i have the d802 for example
Click to expand...
Click to collapse
Is that found under hardware information?
Thought I was good at this. Never mind.
So I have managed to brick my device after 6 hours of having it.
Managed to unlock the BL, install TWRP, but the OS has gone, and I have no way of getting the thing mounted to copy over a ROM or anything.
What's the best way for me to sort this out ?
I'm thinking I could buy an SD card, copy a ROM to it, then flash it via TWRP.
Is this the only option ?
Help
grifforama said:
Thought I was good at this. Never mind.
So I have managed to brick my device after 6 hours of having it.
Managed to unlock the BL, install TWRP, but the OS has gone, and I have no way of getting the thing mounted to copy over a ROM or anything.
What's the best way for me to sort this out ?
I'm thinking I could buy an SD card, copy a ROM to it, then flash it via TWRP.
Is this the only option ?
Help
Click to expand...
Click to collapse
If you can get to the bootloader then just use the restore to stock tool from shawn5162. Should work fine as long as you have successfully unlocked the bootloader. Here is the link http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
Should be clear that this will put your device to LP 5.1.1 without root or TWRP. Then just do the OTA MM update and re-root and flash TWRP. You can follow this guide I created if you like.
http://forum.xda-developers.com/moto-x-style/help/updating-to-mm-lp-moto-x-pure-t3270473
robn30 said:
If you can get to the bootloader then just use the restore to stock tool from shawn5162. Should work fine as long as you have successfully unlocked the bootloader. Here is the link http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
Should be clear that this will put your device to LP 5.1.1 without root or TWRP. Then just do the OTA MM update and re-root and flash TWRP. You can follow this guide I created if you like.
http://forum.xda-developers.com/moto-x-style/help/updating-to-mm-lp-moto-x-pure-t3270473
Click to expand...
Click to collapse
Thanks for this, and I now have a booting , but wifi is not working ? I cannot connect to any wifi at all ? And when I try to turn wifi on, it turns itself off immediately ?
grifforama said:
Thanks for this, and I now have a booting , but wifi is not working ? I cannot connect to any wifi at all ? And when I try to turn wifi on, it turns itself off immediately ?
Click to expand...
Click to collapse
You have to flash correct modem to your device. Check that thread for more info.
kadopt said:
You have to flash correct modem to your device. Check that thread for more info.
Click to expand...
Click to collapse
I have never had such issues when setting up a phone before. Now I have this message
"there's a problem signing in to your google account on this device
Please sign in from a browser on your computer or tablet first, then try signing in again on this device"
Needless to say, I've done this numerous times, and I still cannot sign in on the phone.
Ugh.
grifforama said:
I have never had such issues when setting up a phone before. Now I have this message
"there's a problem signing in to your google account on this device
Please sign in from a browser on your computer or tablet first, then try signing in again on this device"
Needless to say, I've done this numerous times, and I still cannot sign in on the phone.
Ugh.
Click to expand...
Click to collapse
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
pizzlewizzle said:
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
Click to expand...
Click to collapse
Think I'm screwed. No backup. No ability to log into the OS to reset from within. Just keeps looping on the input screen.
I think I read somewhere that if you wait 72 hours it fixes itself. We'll see.
Joyful start to the year
grifforama said:
Think I'm screwed. No backup. No ability to log into the OS to reset from within. Just keeps looping on the input screen.
I think I read somewhere that if you wait 72 hours it fixes itself. We'll see.
Joyful start to the year
Click to expand...
Click to collapse
Why not use the restore to stock tool then before taking the update just make sure your phone has no security on it or the OEM unnlocked turned on...
pizzlewizzle said:
Why not use the restore to stock tool then before taking the update just make sure your phone has no security on it or the OEM unnlocked turned on...
Click to expand...
Click to collapse
That's what I've tried. I used the return to stock tool, and when it asks for my google email address and password, that's what it won't go past. that's exactly where I'm at right now. Stuck at the verification screen.
Is this an xt1575? If so, try my TWRP stock backup?
gokart2 said:
Is this an xt1575? If so, try my TWRP stock backup?
Click to expand...
Click to collapse
Can you give me me a link ?
grifforama said:
That's what I've tried. I used the return to stock tool, and when it asks for my google email address and password, that's what it won't go past. that's exactly where I'm at right now. Stuck at the verification screen.
Click to expand...
Click to collapse
hmmm thats weird... the new security feature wasn't implemented until MM... The restore to stock should take you to 5.1.1. not sure what else to try. Hopefully you can get in after the wait...next time you get your phone running make a backup to save a headache down the road
edit: you couldnt use the restore to stock then before it loads flash a 5.1 ROM?
gokart2 said:
Is this an xt1575? If so, try my TWRP stock backup?
Click to expand...
Click to collapse
Do you have a link ?
I keep trying and trying. I just keep getting sent back to a screen saying "This device was reset. To continue, sign in with a Google account that was previously synced on this device"
infuriating
http://www.androidpolice.com/2015/03/12/guide-what-is-android-5-1s-antitheft-device-protection-feature-and-how-do-i-use-it/
OK looks like this is a "feature" I guess. I'm stuck for 72 hours
grifforama said:
Can you give me me a link ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Its the stock TWRP backup from either 5.1.1 or 6.0....whichever you are currently supposed to be on.
wait, if this is a new phone and you had added your google account before "bricking," why cant you just sign in using that google account. My understanding is that the lockout is to prevent a NEW google account that was not associated with your phone from being used to set it up
pizzlewizzle said:
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
Click to expand...
Click to collapse
That error means you don't have a 72 hour lock yet. Go to https://accounts.google.com/b/0/displayunlockcaptcha on your computer. Login, hit the accept button, then try logging in your phone. Your phone is not locked out, just to to the website. If you changed your password, though, then you shot yourself in the foot with the Google protection.
Not sure if this is the right place to post this.
This is the first time I've tried to system update my Razer Phone 2 since rooting it. I use Magisk. When I try to update, the download finishes, then a red error message at the top says "Installation Problem." I'm not sure the problem comes from the fact I rooted the phone. But I don't know where to begin to solve the problem.
Benjiax2 said:
Not sure if this is the right place to post this.
This is the first time I've tried to system update my Razer Phone 2 since rooting it. I use Magisk. When I try to update, the download finishes, then a red error message at the top says "Installation Problem." I'm not sure the problem comes from the fact I rooted the phone. But I don't know where to begin to solve the problem.
Click to expand...
Click to collapse
Yes it's due to being rooted.
Depending on which image you're currently running you can start over by reinstalling stock image let it update then root again.
JDBarlow said:
Yes it's due to being rooted.
Depending on which image you're currently running you can start over by reinstalling stock image let it update then root again.
Click to expand...
Click to collapse
Should I re-lock the bl as well? Apparently you can do that. I kind of regret rooting. You can do anything fun with the Razer Phone 2
Benjiax2 said:
Should I re-lock the bl as well? Apparently you can do that. I kind of regret rooting. You can do anything fun with the Razer Phone 2
Click to expand...
Click to collapse
If you'd like to yes you certainly can.
I'm sure you're aware of this site since you've already unlocked. Basically same thing just backwards ?
https://developer.razer.com/razer-phone-dev-tools/general-instructions/