I've always had my devices rooted and running a custom rom or at least a custom kernel or something of the sort "But" ever since I got my pixel about a year ago I haven't felt the need to root at all, stock rom is just perfect and so battery life and I don't see a reason to.
However I was just thinking that now with locked bootloader if for any reason my phone gets bricked then I'm probably [email protected]*t out of luck because I won't be able to flash a factory image to bring the phone back to life.
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Getting bricked is the direct result of flashing images.
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
I could not disagree more. There are countless threads of individuals taking OTAs and running into boot loop. Additionally I have read through multiple threads where individuals were simply using their phone to play a game, text, phone call etc and the phone shuts off and goes into a loop.
The users with an unlocked bootloader were able to salvage the device. Users without a locked bootloader looked for a RMA.
To the OP- I personally will never own an Android device with a constantly locked bootloader. The safety net of being able to factory reset and flash stock images is something I've always cherished and do not wish to get rid of.
There are security risks to having an unlocked BL. If an Android savvy criminal were to steal your device they could do a lot of damage with obtaining personal information. For me, I'm much more worried about my phone going in to boot loop than I am some criminal being able to take my phone from me.
Sab3elbromba said:
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Click to expand...
Click to collapse
if for any reason, something did get corrupted on your phone with a lockedbootloader and it tripped verified boot. you would be locked out, no course of action but to get an RMA... so if u plan on tinkering with your phone or just would like a failsafe, at least with an unlocked phone. you would be able to flash firmware, etc...
just remember, not to relock your bootloader; unless your phone is running stock firmware and is wiped.... otherwise you will trip verified boot and brick it...
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
no, it's not. getting a bricked phone is pretty much always because the person did something ill advised or dumb... like relocking their bootloader running custom firmware...
so a diect result of user error, nothing to do with flashing images.
Related
Fastboot Mode
PRODUCT NAME - tuna
VARIANT - maguro 16gb
HV VERSION - 9
BOOTLOADER VERSION - PRIMELC03
BASEBAND VERSION - I9230XXLH1
CARRIER INFO - NONE
SERIAL NUMBER - XXXXXXXXXXXXXXXX
SIGNING - production
LOCK STATE - unlocked
When it says unlocked, is it talking about my SIM or my bootloader?
Do Nexus's come bootloader unlocked, I mean; they are dev friendly.
Don't make fun of me, I'm only curious and trying to start learning about android and maybe even develop things considering I do know alot about graphics.
Thanks in advance.
Edit: I forgot it meant bootloader (blonde moment?), but is this regular for nexus devices?
I'm almost certain it's talking about your bootloader but to be certain reboot your device. If you see an unlocked padlock under Google when you turn on your device your bootloader is unlocked.
063_XOBX said:
I'm almost certain it's talking about your bootloader but to be certain reboot your device. If you see an unlocked padlock under Google when you turn on your device your bootloader is unlocked.
Click to expand...
Click to collapse
Yeah it is, I know that; i edited my post after realizing that.
But what I'm asking is; Is it typical for nexus devices to come with unlocked bootloaders or not?
I got my from i wireless and I believe it is a imported device.
It's not. Probably was returned/refurbished.
Haaah.
What are the chances that it's rooted and how can I check?
I traded in my One S and got this phone as a replacement.
Strange that it came in the original boxing with everything.
Thanks man.
If it doesn't have superuser then it isn't rooted.
Thanks.
I'm gonna be a noob and ask one more question.
Is it easy to brick your phone from rooting?
Or SuperSU. Try rootchecker. "Is it easy to brick your phone from rooting?" Not from rooting but perhaps flashing if you tend to jump into things..
brainfart moments can give you a softbrick pretty easily, but with fastboot and (we arent quite fans of this like the fascinate people were) ODIN you would have to realllllly screw up and probably try to completely brick it. make sure you have fastboot set up and working correctly before doing anything questionable. it will save your ass lol
edit: speaking of fastboot, i would probably use it to format and reflash all partitions with the latest stock image before messing around since it sounds like your phone has been screwed with before you got it (you never know what other people did to it). theres a really good guide about resetting to stock in either the general or q/a section here. dont worry about relocking the bootloader, there isnt really a way to unlock it wrong... it either works or doesnt. since you sound pretty tech savvy, please dont use toolkits, learn fastboot. it seems like toolkits are a one click problem, not a one click fix lol.
electro` said:
Thanks.
I'm gonna be a noob and ask one more question.
Is it easy to brick your phone from rooting?
Click to expand...
Click to collapse
Practically impossible. You'd have to not read anything and then willfully do something to ruin your device. And even then it's almost certainly recoverable so not bricked.
It seems nearly impossible to brick your device. x.x
I installed ParanoidAndroid last nigh but for some reason I tried installing a mod and I lost the status bar and home buttons.
I was so pissed off, I had to unroot my device and reflash the stock rom.
I'm going to try using CyanogenMod 10.1 and see where it gets me. It will probably be better considering you can make alot more customizations to your device ui and such.
Thanks 063_XOBX.
Hello everyone.
I'm new to the Nexus world, I have already flashed my Galaxy S4 and S2, and I did flash my Asus Transformer, but I am completely new to this.
When you say that in order to relock your bootloader you just have to send a command through fastboot, will this leave the bootloader as LOCKED, just as if you hadn't done anything? Or will it leave it to something such as RE-LOCKED?
I mean, is there any way they can know what you have done? If so, is there anything like Triangle Away?
Bootloader is always re-lockable? I mean, can they send an OTA that disables you to relock the bootloader so your warranty is void?
Thank you very much.
vagaerg said:
Hello everyone.
I'm new to the Nexus world, I have already flashed my Galaxy S4 and S2, and I did flash my Asus Transformer, but I am completely new to this.
When you say that in order to relock your bootloader you just have to send a command through fastboot, will this leave the bootloader as LOCKED, just as if you hadn't done anything? Or will it leave it to something such as RE-LOCKED?
I mean, is there any way they can know what you have done? If so, is there anything like Triangle Away?
Bootloader is always re-lockable? I mean, can they send an OTA that disables you to relock the bootloader so your warranty is void?
Thank you very much.
Click to expand...
Click to collapse
It is my understanding there is no counter, like on Samsung devices, regarding unlocking your bootloader or flashing custom ROMS, etc... Nexus devices are meant to be hacked/slashed/rooted so i don't think Google would disable you from re-locking it. Plus someone would find a way around it anyway.
railed said:
It is my understanding there is no counter, like on Samsung devices, regarding unlocking your bootloader or flashing custom ROMS, etc... Nexus devices are meant to be hacked/slashed/rooted so i don't think Google would disable you from re-locking it. Plus someone would find a way around it anyway.
Click to expand...
Click to collapse
Ok! Thank you very much
I suppossed Google wouldn't want to disable you from doing that because, as you said, they are made to be modified, but just wanted to make sure, as I'm new to this. What I didn't know was that relocking it left it as stock, so that's great
Thanks
vagaerg said:
Ok! Thank you very much
I suppossed Google wouldn't want to disable you from doing that because, as you said, they are made to be modified, but just wanted to make sure, as I'm new to this. What I didn't know was that relocking it left it as stock, so that's great
Thanks
Click to expand...
Click to collapse
No problem. Quite a few posts on here I've seen people unlock bootloader, flash custom stuff and find screen errors (dead pixels, light bleed or w/e) or GPS issues and they reflashed the stock image and re-locked bootloader and returned to store no problem.
railed said:
No problem. Quite a few posts on here I've seen people unlock bootloader, flash custom stuff and find screen errors (dead pixels, light bleed or w/e) or GPS issues and they reflashed the stock image and re-locked bootloader and returned to store no problem.
Click to expand...
Click to collapse
Ok, so there's no reason to worry about that, which was my main worry.
Thank you very much
Helo Guyz!!
I bought a new HTC One m8 a couple of days ago. I've made a call when I bought it, so the sim card was working earlier. I rooted it using "HTC M8 ALL IN ONE V2.0" yesterday so that I can restore the apps+app data via Titanium BackUp from my old Xperia Z. Just turned on my Rooted M8 and it doesn't recieve signals. It shows an icon with a simcard followed by an exclamation mark. Tried my brother's sim, no change!! Made a Factory reset(It didn't Unroot) still no change.
Please help me Guyz!!! Thanks.
I might have unlocked the bootloader while rooting as it was a necessary step in the TUT(All in one tool).
Kunnu2592 said:
Helo Guyz!!
I bought a new HTC One m8 a couple of days ago. I've made a call when I bought it, so the sim card was working earlier. I rooted it using "HTC M8 ALL IN ONE V2.0" yesterday so that I can restore the apps+app data via Titanium BackUp from my old Xperia Z. Just turned on my Rooted M8 and it doesn't recieve signals. It shows an icon with a simcard followed by an exclamation mark. Tried my brother's sim, no change!! Made a Factory reset(It didn't Unroot) still no change.
Please help me Guyz!!! Thanks.
I might have unlocked the bootloader while rooting as it was a necessary step in the TUT(All in one tool).
Click to expand...
Click to collapse
Unlocking the bootloader wouldn't affect your device in any means except factory resetting it.
Maybe the tool you used changed the radio? That's the only thing I can think of. Try flashing a different radio
Kunnu2592 said:
I might have unlocked the bootloader while rooting as it was a necessary step in the TUT(All in one tool).
Click to expand...
Click to collapse
You don't even know if you unlocked the bootloader? This is one of the big reasons why toolkits and step-by-step tutorials are a bad idea. You are modding your phone with absolutely no understanding of the primary concepts, or what you have even done with your phone. Although the no signal issue doesn't seem related to your lack of knowledge, I'd still recommend you slow down and do more learning and research before messing with the phone anymore, unless you want to risk permanent damage to the device.
Also, all a factory reset does is wipe user data, and doesn't affect the system in any way.
As mentioned in the previous response, simply unlocking the bootloader should not have resulted in no signal.
Are you presently s-on or s-off? You should list step by step what you've done to the phone. Still on the stock ROM, or otherwise? Did you try to restore any system data with Titanium? How precisely did you root the phone after unlocking the bootloader? What recovery and version?
redpoint73 said:
You don't even know if you unlocked the bootloader? This is one of the big reasons why toolkits and step-by-step tutorials are a bad idea. You are modding your phone with absolutely no understanding of the primary concepts, or what you have even done with your phone. Although the no signal issue doesn't seem related to your lack of knowledge, I'd still recommend you slow down and do more learning and research before messing with the phone anymore, unless you want to risk permanent damage to the device.
Also, all a factory reset does is wipe user data, and doesn't affect the system in any way.
As mentioned in the previous response, simply unlocking the bootloader should not have resulted in no signal.
Are you presently s-on or s-off? You should list step by step what you've done to the phone. Still on the stock ROM, or otherwise? Did you try to restore any system data with Titanium? How precisely did you root the phone after unlocking the bootloader? What recovery and version?
Click to expand...
Click to collapse
Sorry brother. I thought I was clear. Here is what I did to my phone. I followed this up. Get token, submit it, download a file which was sent via email and use it to unlock the bootloader. Root it at last using the perm root command in the tool itself.
http://forum.xda-developers.com/showthread.php?t=2699065
I haven't done anything to the phone after rooting it. No titanium restores.. Nothing. I would want to relock the bootloader want to relock the bootloader using the same tool. Is it safer? Does it makes it normal again? Do I get my warranty then? Does it wipes all the data if I lock bootloader after restoring my apps with titanium backup?
Please help guyz!!
Kunnu2592 said:
I would want to relock the bootloader want to relock the bootloader using the same tool. Is it safer? Does it makes it normal again? Does it wipes all the data if I lock bootloader after restoring my apps with titanium backup?
Click to expand...
Click to collapse
Nothing you did should have caused the no signal issue (simply unlocking the bootloader and rooting shouldn't have caused that). So its hard to say what would fix it.
You can try to re-install the stock ROM. Or try to relock the bootloader and see what happens.
Kunnu2592 said:
Does it wipes all the data if I lock bootloader after restoring my apps with titanium backup?
Click to expand...
Click to collapse
Not sure, but I believe relocking the bootloader will wipe data. So backup anything important before doing so.
redpoint73 said:
Nothing you did should have caused the no signal issue (simply unlocking the bootloader and rooting shouldn't have caused that). So its hard to say what would fix it.
You can try to re-install the stock ROM. Or try to relock the bootloader and see what happens.
Not sure, but I believe relocking the bootloader will wipe data. So backup anything important before doing so.
Click to expand...
Click to collapse
Okay bro... I would try that and be bck!!
ThanQ ?
brichardson1991 said:
Unlocking the bootloader wouldn't affect your device in any means except factory resetting it.
Maybe the tool you used changed the radio? That's the only thing I can think of. Try flashing a different radio
Click to expand...
Click to collapse
Idk what Radio is and how to change it. Is it some code that makes the signal receiver work? I just followed a guide and didn't miss any steps. Please enlighten me about it so that I could try something out. ThanQ brother.
Kunnu2592 said:
Idk what Radio is and how to change it. Is it some code that makes the signal receiver work? I just followed a guide and didn't miss any steps. Please enlighten me about it so that I could try something out.
Click to expand...
Click to collapse
You didn't answer my question whether you were S-off or S-on. But as you didn't mention it in the steps you performed, you are probably still s-on. That being the case its also likely the radio wasn't modified by anything you did (s-off is needed to write to the radio partition); and on the same note, you can't do anything to that partition now unless you s-off.
I'd go with my previous recommendations for now, and see how that goes before doing more.
Maybe a silly question, but toggling airplane more or rebooting the phone doesn't have any affect on the no signal condition?
Maybe it's not making proper contact in the tray? Tried to remove it and readjust it a bit and put it back? I recall someone mentioning a similar problem months ago and when I read up on it it seemed to be a problem with the Hox as well where they used to put some tape on the back of the sim and put it back in the tray. They did this to "thicken" it a bit so it can get pressed down properly on the circuitry?
Just throwing out my 2cents here...
BerndM14 said:
Maybe it's not making proper contact in the tray? Tried to remove it and readjust it a bit and put it back? I recall someone mentioning a similar problem months ago and when I read up on it it seemed to be a problem with the Hox as well where they used to put some tape on the back of the sim and put it back in the tray. They did this to "thicken" it a bit so it can get pressed down properly on the circuitry?
Just throwing out my 2cents here...
Click to expand...
Click to collapse
That's certainly worth exploring as well. It seems like too much a coincidence that this issue occurred right after unlocking the bootloader and rooting. But on the other hand, its odd as such modifications should not have caused the no signal issue.
redpoint73 said:
That's certainly worth exploring as well. It seems like too much a coincidence that this issue occurred right after unlocking the bootloader and rooting. But on the other hand, its odd as such modifications should not have caused the no signal issue.
Click to expand...
Click to collapse
Heh, to quote one of my favourite quotes from xxxHolic: There is no such thing as a coincidence in this world, there is only the inevitable.
Could be radio though as well. I went to do a search for this issue and found some of the old threads where they flashed radios, restored the nandroid backup etc.
But perhaps that's something that the OP can look into as well and learn some stuff.
htc one m8 sim card error site:forum.xda-developers.com In google returned many results.
[Q] Sim Card detection Error (m8)
HTC One (M8) Won't recognize Sim Card
etc etc...
brichardson1991 said:
Unlocking the bootloader wouldn't affect your device in any means except factory resetting it.
Maybe the tool you used changed the radio? That's the only thing I can think of. Try flashing a different radio
Click to expand...
Click to collapse
redpoint73 said:
Nothing you did should have caused the no signal issue (simply unlocking the bootloader and rooting shouldn't have caused that). So its hard to say what would fix it.
You can try to re-install the stock ROM. Or try to relock the bootloader and see what happens.
Not sure, but I believe relocking the bootloader will wipe data. So backup anything important before doing so.
Click to expand...
Click to collapse
It is S-on. My brother have the same phone and when I checked for his radio version in boot loader screen, Its something like "INVALID_VER_INFO" but my device shows a version number "RADIO-1.19.21331147A1.09G". We've bought both phones recently. His phone is untouched where as I messed up my device just for the apps and app data. I fee terrible now. Please help me to undo everything. I guess I cant even take it to the HTC service center as it says "TAMPERED" and "RELOCKED" banners on top of the bootloader screen.
I've used up all my savings on this device and it seems its wasted now.
Pease help me guyz... :crying:
Kunnu2592 said:
We've bought both phones recently. His phone is untouched where as I messed up my device just for the apps and app data. I fee terrible now. Please help me to undo everything.
Click to expand...
Click to collapse
You've been given several suggestions to try at this point, and haven't indicated whether you attempted them or not.
You can cry all you want. But if you fail to even try to help yourself, we can't help you either.
Kunnu2592 said:
I guess I cant even take it to the HTC service center as it says "TAMPERED" and "RELOCKED" banners on top of the bootloader screen.
Click to expand...
Click to collapse
If you are talking about a warranty claim, warranty doesn't cover damage done by mods you performed. When you chose to unlock the bootloader and root the phone, you accepted all responsibility for any damage that might occur. This is the game we play. If you can't afford to repair or replace the phone in the event of permanent damage done by mods you did; then you shouldn't be modding it in the first place.
If you are talking about paying HTC to fix it, they will still do it if its been tampered. They will likely replace the mainboard and charge you for it.
But honestly, I think your condition can be fixed by software; and sending to HTC is not necessary. But you have to be willing to put in the effort.
redpoint73 said:
You've been given several suggestions to try at this point, and haven't indicated whether you attempted them or not.
You can cry all you want. But if you fail to even try to help yourself, we can't help you either.
If you are talking about a warranty claim, warranty doesn't cover damage done by mods you performed. When you chose to unlock the bootloader and root the phone, you accepted all responsibility for any damage that might occur. This is the game we play. If you can't afford to repair or replace the phone in the event of permanent damage done by mods you did; then you shouldn't be modding it in the first place.
If you are talking about paying HTC to fix it, they will still do it if its been tampered. They will likely replace the mainboard and charge you for it.
But honestly, I think your condition can be fixed by software; and sending to HTC is not necessary. But you have to be willing to put in the effort.
Click to expand...
Click to collapse
Hieee bro..
I've relocked the bootloader and it doesn't help. There was no change. I tried to place a thin paper on back of the sim card to make a better connection. It still doesn't work. It now says TAMPERED and RELOCKED(after relocking the bootloader). I installed a stock firmware and it didn't solved the problem too.
I read endless posts but found nothing that can help the situation. Just waiting for help from my thread.
I want to try restoring my brother's backup. But is it possible to make a complete system backup to flash into my device without rooting? I don't want to mess his device too....
Thank you.
Kunnu2592 said:
I want to try restoring my brother's backup. But is it possible to make a complete system backup to flash into my device without rooting? I don't want to mess his device too....
Click to expand...
Click to collapse
Nope.
Nor will doing so yield anything that isn't already easily available here (so don't bother unlocking bootloader and rooting his phone just to help your own situation, its a waste of time): http://forum.xda-developers.com/showthread.php?t=2701376
Restore the appropriate stock ROM, and see if that helps.
redpoint73 said:
Nope.
Nor will doing so yield anything that isn't already easily available here (so don't bother unlocking bootloader and rooting his phone just to help your own situation, its a waste of time): http://forum.xda-developers.com/showthread.php?t=2701376
Restore the appropriate stock ROM, and see if that helps.
Click to expand...
Click to collapse
Yeahhh bro.. Ua right. I'll try a Stock Rom again and will be bck wid the result.
Thanks for ua help
Do google know that we've unlocked the bootloader? (as Sony do as they ask for email adresses etc and confirm the ulock)
Wondering about warranty.
there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.
dkryder said:
there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.
Click to expand...
Click to collapse
Ok thanks.
One last google noob question; does rooting usually need an unlocked bootloader?
On xperia root is more difficult to achieve with a locked bootloader, but can be done, thanks to the devs.
I guess I will read the 6P thread to get a feel for the situation.
Cheers again.
i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.
dkryder said:
i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.
Click to expand...
Click to collapse
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.
mskip said:
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.
Click to expand...
Click to collapse
I sure hope so. That's one of the only things keeping me from buying it already. It's kind of worrisome that the development forums are almost completely dead (save for the one thread trying to get root without a custom recovery, of course). I guess I'm just spoiled by using only Nexus devices, so having very active development is usually the norm.
well, the thing was only a rumor about sales start up until a report in a german site on 12/5 or so that sales would start 12/8 and then on 12/8 a confirm that at 1pm eastern u.s.a. sales would begin. talk about giving people a decent notice about a device this pixel c was a new low for google. it's almost they decided to sell them as android tablet at last moment instead of tossing in trash as a complete failure as chrome os tablet so, yeah, it will take a while for anyone that has skill to develop this device to ante up the funds and take delivery. if bootloader remains locked and boot temp recovery to flash supersu does that restrict the root in any way? i am just curious about this as my bootloader is unlocked.
some help pls?
That depends on what you are trying to do. You can use fastboot commands in bootloader-fastboot mode; which will still work even if OS and recovery are not accessible. But anything more (such as adb, storage access) you will need at least recovery.
What is the current condition of the phone, what were you trying to do, or want to do, etc.?
redpoint73 said:
That depends on what you are trying to do. You can use fastboot commands in bootloader-fastboot mode; which will still work even if OS and recovery are not accessible. But anything more (such as adb, storage access) you will need at least recovery.
What is the current condition of the phone, what were you trying to do, or want to do, etc.?
Click to expand...
Click to collapse
Thanks for willingness to help,i was already solving the problem.I went to a specialized server,and they repair it.
morrientes99 said:
Thanks for willingness to help,i was already solving the problem.I went to a specialized server,and they repair it.
Click to expand...
Click to collapse
That's too bad. You probably spent money to fix something we could have helped you with, for free.
redpoint73 said:
That's too bad. You probably spent money to fix something we could have helped you with, for free.
Click to expand...
Click to collapse
was not so bad..i was also replacing the battery and usb connector,so now looks like new..unfortunately they didnt install Android 7.0,but im afraid to try to do it
morrientes99 said:
unfortunately they didnt install Android 7.0,but im afraid to try to do it
Click to expand...
Click to collapse
Sounds like you haven't modded the phone before? No need to be afraid in my opinion. You won't brick (or otherwise damage) the device by unlocking the bootloader, installing custom recovery, and flashing a custom ROM. And the process is almost entirely reversible, with the slight exception of the fact that the bootloader will only ever say UNLOCKED or RELOCKED; versus LOCKED (stock condition). But this is almost entirely irrelevant, as RELOCKED is functionally the same as LOCKED, aside from the possibility that RELOCKED voids the warranty (indicates the phone was bootloader unlocked) but the huge majority of M8 devices don't have warranty at this point, as the phone is going on 3 years old.
Just be sure to properly read and understand the process before you start, don't use outdated methods, backup any personal data before bootloader unlock, and be sure to make a backup of your current stock ROM before flashing the new ROM. Also understand how to recover from problems, such as restoring a TWRP backup, etc.
Do the necessary due diligence before you start, and modding the phone will go just fine.