Related
Greetings!
As the topic says, I have a Nexus, which is kinda bricked (soft or hard, don't know). The current situation is that it boots up -> Google logo -> Nexus logo -> "Unfortunately, the process android.process.acore has stopped..." followed by dozen other process kills. After pressing 'ok' for about twenty times, I get to see the welcome screen, which you get after factory reset. I'm also able to skip through almost all the set ups (while pressing 'ok' at the force closures), but usually I can't get past the last phase, which is 'finish' or something. When I press the button, it says the same thing with the process has stopped and reverts to the previous phase or sometimes reboots itself. However, during my repairing process, I've managed few times to get past the initial setup an into the android settings via notification bar. No idea when this happens, seems quite random. It also reboots randomly, followed by few more reboots with "android is upgrading" message. Randomness is a key word here.
So, how this happend? To be honest, don't really know. I got this from a friend, who said it just shut down in the middle of Clash Of Clans, possibly due to low battery. I have no idea what's been done to the phone after that apart from my desperate repairing experiments.
I've searched all over the internet and the most reasonable answer I found, was "flash stock image", which I tried and it gives some kind of 'flash write error'. Also, the bootloader is locked. I know how to unlock it, but for some reason it re-locks after reboot. I've tried all sorts of toolkits and also the command line "fastboot oem unlock", but no cigar. I get the unlocking screen and I'm able to unlock, but after I boot, the bootloader says "locked" again. Also, everytime I boot up, I get the welcome screen with the process stopped windows even if I somehow manage to surf through the initial setup.
I also tried to flash without unlocking and flash without rebooting after unlock command, but the phone gives a 'flash write' error. Needless to say, I've also tried factory resetting and clearing cache from recovery, but it doesn't seem to help anything. Cache wipe also gives an error saying "can't open /cache/recovery/last-log (+ /last_install) (read-only file-system). Don't know if this is due the locked bootloader?
Is there a way to flash Nexus 5 in a download mode? I managed to get into one by accident, but didn't really find any help from google... I'm more used to my Samsung Galaxy S3, which has download mode to help unbrick bad flashes etc. Nexus-LG is apparently a bit different.
I'm wondering, if it's possible that the flash memory is broken? Apparently it's somehow corrupted atleast, but is there any way to force flash or do something to clean up the whole thing without unlocking or can I unlock it some other way? I've already used all my knowledge and imagination over this thing, but can't seem to make any progress. Please ask me, if there's something I forgot to mention in my post. It's a shame there's no external-sd slot in this, 'cause I'm quite sure the phone should be totally working otherwise.
Thanks for your interest and answers in advance!
PS. Feel free to give me any sorts of experimental tricks; I've spent 0 euros on this thing, and I'm willing to try anything... it can't really get "more not working" :laugh:
Most likely your emmc is borked and you won't be able to recover it. But you might try following this thread from someone else who had the same problem http://forum.xda-developers.com/showthread.php?p=54333060
Edit, pay attention to bitdomo's suggestions
Sent from my Nexus 5 using XDA Free mobile app
If you want to enter download mode then check the my singature about LG flashtool, but don't give hopes.
I have no idea what causing these kind of errors.
I think it is not a bad sector error because the whole emmc affected with all the partitions. Partitions become non-writeable or completly messed up and cannot be formated or fixed because the emmc cannot be written.
It is not like the permanent or temporary write protect flag sets to 1 from 0 in the CSD register.
Could it be a bug in the emmc firmware or some other componets faulty which are connected to the emmc?
I also tried to find the connection points, which are exposed on the motherboard, to the emmc with the help of the service manuals. I have found everything except the grounds, Vss and VssQ. Here are the connection points I found.
Some documents:
Serivce manuals
data sheet of the emmc
something about how the emmc work: here, here and here
I dont have any messauring tool to find out more about this problem.
Thank you both!
I tried the LG FlashTool method, but as you expected, it didn't work. It gave an error saying 'user data erase failed', which I think finally means that nobody and no-thing is able to write stuff to that chip. I figure my only option to get this device working is to get a 'new' motherboard somewhere. I suppose it's not possible to change the flash memory chip itself? Do you guys have any experiences on motherboard changes? Is there something I should know before? The phone itself looks pretty easy to open, compared to other devices I've disassembled so technically I should be okay, unless there's some compatibility issues around. My device is not the north-american model, but can I use north-american motherboard as a spare part? Isn't all the information basically stored in the mobo? I think I could get a glass cracked phone from ebay, but it would be nice to be able to use it here in Finland...
And thank you again, it's always good to hear my phone has gone fubar from someone else than myself
McKis said:
Thank you both!
I tried the LG FlashTool method, but as you expected, it didn't work. It gave an error saying 'user data erase failed', which I think finally means that nobody and no-thing is able to write stuff to that chip. I figure my only option to get this device working is to get a 'new' motherboard somewhere. I suppose it's not possible to change the flash memory chip itself? Do you guys have any experiences on motherboard changes? Is there something I should know before? The phone itself looks pretty easy to open, compared to other devices I've disassembled so technically I should be okay, unless there's some compatibility issues around. My device is not the north-american model, but can I use north-american motherboard as a spare part? Isn't all the information basically stored in the mobo? I think I could get a glass cracked phone from ebay, but it would be nice to be able to use it here in Finland...
And thank you again, it's always good to hear my phone has gone fubar from someone else than myself
Click to expand...
Click to collapse
If you want to use LTE in finland then get D821 motherboard.
By the way why cant you or your friend claim the phone warranty?
bitdomo said:
If you want to use LTE in finland then get D821 motherboard.
By the way why cant you or your friend claim the phone warranty?
Click to expand...
Click to collapse
Hmm, now that you mentioned it... I assumed the warranty was already void, since it's only one year (bought from Asia), but it seems the Nexus 5 was launched less than a year ago. To be honest, I didn't even think about the warranty since he gave the phone directly (?) to me. I should probably ask him...
I assume the LTE restrictions are based on hardware of the chip and can't be dealt with software patching?
Anyways, thanks for your help, you've been really kind!
McKis said:
Hmm, now that you mentioned it... I assumed the warranty was already void, since it's only one year (bought from Asia), but it seems the Nexus 5 was launched less than a year ago. To be honest, I didn't even think about the warranty since he gave the phone directly (?) to me. I should probably ask him...
I assume the LTE restrictions are based on hardware of the chip and can't be dealt with software patching?
Anyways, thanks for your help, you've been really kind!
Click to expand...
Click to collapse
Yes, the differance with the LTE bands is hardware thing. If the phone you have is the international nexus 5 aka D821 then you can ask for LG in finland about the cost of the repair. It will be hard to find D821 motherboard or nexus 5 with broken screen on ebay, but there are many D820s.
I want ask one thing. Can you reboot to bootloader and check the variant line? For me it says "hammerhead D821(H) 16GB"
What is the letter you see between the ( )?
bitdomo said:
Yes, the differance with the LTE bands is hardware thing. If the phone you have is the international nexus 5 aka D821 then you can ask for LG in finland about the cost of the repair. It will be hard to find D821 motherboard or nexus 5 with broken screen on ebay, but there are many D820s.
I want ask one thing. Can you reboot to bootloader and check the variant line? For me it says "hammerhead D821(H) 16GB"
What is the letter you see between the ( )?
Click to expand...
Click to collapse
I have 'hammerhead D821(E) 16GB'. Yeah, it seems a lot of Nexuses sold are in fact the north american version (surprisingly). Well, maybe I'll check the warranty/repairing status first. Although, I don't mind not using LTE, since I've never trusted any mobile networks at all so it doesn't matter to me if I only have 3G speeds :silly:
McKis said:
I have 'hammerhead D821(E) 16GB'. Yeah, it seems a lot of Nexuses sold are in fact the north american version (surprisingly). Well, maybe I'll check the warranty/repairing status first. Although, I don't mind not using LTE, since I've never trusted any mobile networks at all so it doesn't matter to me if I only have 3G speeds :silly:
Click to expand...
Click to collapse
Thank you for your response. The (E) and (H) letters means the brand of the memory. E for Elpida and H for Hynx. Nexus 5s with Elpida ram are rare just like nexus 5s with faulty emmc. The memory, cpu and gpu are put together to one chip, the MSM8974 chip. This chip controls everything on the phone including the emmc.
I should make a survey about the emmc faulty devices to gain more infos before making theories.
bitdomo said:
Thank you for your response. The (E) and (H) letters means the brand of the memory. E for Elpida and H for Hynx. Nexus 5s with Elpida ram are rare just like nexus 5s with faulty emmc. The memory, cpu and gpu are put together to one chip, the MSM8974 chip. This chip controls everything on the phone including the emmc.
I should make a survey about the emmc faulty devices to gain more infos before making theories.
Click to expand...
Click to collapse
I was wondering what that letter meant lol.
bitdomo said:
Thank you for your response. The (E) and (H) letters means the brand of the memory. E for Elpida and H for Hynx. Nexus 5s with Elpida ram are rare just like nexus 5s with faulty emmc. The memory, cpu and gpu are put together to one chip, the MSM8974 chip. This chip controls everything on the phone including the emmc.
I should make a survey about the emmc faulty devices to gain more infos before making theories.
Click to expand...
Click to collapse
Sorry for necroing this post but it serve to anyone with my question that google nexus 5 elpida emmc.
Will elpida emmc fail and hynix is a lot better? Cause im having a n5 with 32g (e) and a 16g n5 (h)
Im using hynix one cause i reflash everytime and i dont want a bricked n5, is there anyway to know if my elpida n5 will brick or somewhat?
Tha kz!
Sent from my FX82-ms using Tapatalk
Can i back up the rom image of one of my devices and use that to revive a soft-bricked device of the same model?
If so what software should i learn about and use?
thewildnative said:
Can i back up the rom image of one of my devices and use that to revive a soft-bricked device of the same model?
If so what software should i learn about and use?
Click to expand...
Click to collapse
Hello,
We wouldn't recommend doing that.
Please follow a working known way to fix your soft bricked device.
May I please know the make and model of your device?
-Vatsal
Vatsal said:
Hello,
We wouldn't recommend doing that.
Please follow a working known way to fix your soft bricked device.
May I please know the make and model of your device?
-Vatsal
Click to expand...
Click to collapse
My device is an LG. Model "l21g". The name is "Destiny", by Tracfone for Walmart's Straight Talk service. Running 5.0.1
Be aware though it can be difficult to google the model name. Below are a list of variants the device can be referred to:
- LGL21G
- LG L21G
-LG LGL21G
Yeah it can get kinda annoying. But since my device is clearly not a flagship type, and is merely less than generic, there aren't many people out there publishing fixes for it. How could would i be able to bring my soft-bricked device of the identical model, to work again. It will still bring up the LG logo screen and just stay stuck there. I've been searching for months now and have not found a known working way of fixing it. Especially since it's just another cheap android. The crafted design of the device heavily resembles the design of the G3, where on forums like these [http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734], i've seen g3's and g4's have a natural booting dysfucntion due to an assumed LG's own lack of quality in hardware design. Of course though, different model will have different methods. I cannot find any other place on the internet offering firmware downloads for my device, except here [http://bbs.gaodi.net/Firmware-669539-1-1.html]. And you can see that i've tried reaching out to them as well. But with literary not responses. Not even from that site's support team, with regard to how their point system works to reveal download links to the zip files. Chances are its another shizzy site filled with malware.
So if you have any idea on how to help me. I'd be happy to try almost anything.
I mean this thing is a piece of junk, keys all over the place, I typo all the time from mismatched touches on the screen, it bug reports daily, it is slower than older phones, no bootloader, no root, I HATE LG and this piece of S###! I have contacted Sprint, LG, anyone I can, and LG doesnt care, they are the absolute worst company ever in existence of mobile phones. I CANNOT WAIT until they go bankrupt. This is the WORST DEVICE EVER IN HISTORY! I am SO upset with LG and Sprint and SO disappointed with LG mobile in general. I havent met one customer who is 100% satisfied with LG YET to date! They will soon become the next Blackberry, a distant bad memory but they dont have to be if they would just listen to us and unlock the damn bootloaders. THEN we can fix the issues ourselves and accept LG, not love LG, but at least not hate them. I would have AOSP on my device day 1, instead, I am stuck with this overbloated Sprint BS (yes I have Octoplus LG and can move to US-Open / non-branded) but then I run into CDMA issues with Sprint so I am stuck with a terrible device I wish I could toss. And Sprint actually ASKED me if I would be interested in purchasing the lease out and owning it (to get a new phone on a new lease), YEAH RIGHT, I am DONE with this piece of crap phone and Sprint! They can both bite me, Sprint overcharges now with hidden fees and terrible customer support, and LG just doesnt care, they dont give a hoot about the customer, once they get the money, you are a distant past memory (like they will soon be)!
I have had this phone since late September, and have never had the issues that you have. Yes, it does have its quirks, but nothing like you've described. Have you tried a factory reset to see if that fixes the issues?
Sent from my LM-G710VM using Tapatalk
Since I got mine, I have debloated what I can on the phone via application menu and adb.. It's ok, but would prefer having a unlocked bootloader, and root.
I am 100% satisfied, so I must be your first
Can you flash custom partitions with octopus box?
No!
Just use this beast with some nice headphones.
Go to compare with s10 or iPhone xs max screen. Max brightness on all, G7 wins!
Best screen, best Dac, best Amp, best camera software. Best USB-C 3.1 with 5Gbps, hdmi output. What else do you want? Updates? What for? Since Qualcomm introduced Trust Zone it's almost impossible to get hacked or root the phone. Software updates are just a gimmick.
Enjoy your phone. It's WONDERFUL! Trust me on this.
I wouldn't say I'm miserable with the phone but the lack of timely security updates and lack of update to Android Pie makes it unlikely I would consider getting another LG phone. The solution is simple, sell just 1 global version of the phone so you don't have to provide updates for multiple models but they aren't listening to me.
mr3p said:
I wouldn't say I'm miserable with the phone but the lack of timely security updates and lack of update to Android Pie makes it unlikely I would consider getting another LG phone. The solution is simple, sell just 1 global version of the phone so you don't have to provide updates for multiple models but they aren't listening to me.
Click to expand...
Click to collapse
Actually its only two versions.
The rest is carrier software that your carrier is responsible for.
maydayind said:
Actually its only two versions.
The rest is carrier software that your carrier is responsible for.
Click to expand...
Click to collapse
Interesting. So you are saying that G710TM, G710VMX, G710ULM, G710PM, G710VM, G710EM and G710EMW are all the exact same phone with interachangable firmware? For the record, try calling Google Fi and telling them they are responsible for providing updates, LOL. They will tell you its LG's responsibility but either way my comments still stands. I wouldn't recommend anyone who wants a phone which receives regular updates to ever purchase an LG device.
I loved my quirky V10, but that decided that it would not turn on or chrage one day so I got the flagship at the time - the G7. I think the V30 was still a month or more to release. G7 is or was ok - optimize phone seemed to screw it up, clearing cache in recovery was just an error message, it was not particularly fast, but I could live with that. Then there was a few weeks of the fingerprint scanner being wonky. Well fingerprint stopped working yesterday. Hard reset didnt fix it. So yeah after 4+ years with LG never again will I get one.
Update: fingerprint started working again for some unknown reason. Software conflict maybe?
mjl574 said:
I have had this phone since late September, and have never had the issues that you have. Yes, it does have its quirks, but nothing like you've described. Have you tried a factory reset to see if that fixes the issues?
Sent from my LM-G710VM using Tapatalk
Click to expand...
Click to collapse
done 5 times (through settings and through recovery as well, I tried both methods), still piece of junk
I am glad everyone else is happy, but not me. All I can say it, wait until you DO have issues and try to reach out through LG. LG wont respond, they dont care, trust me, we are on our own. I will NEVER again EVER purchase another LG product, not a phone, washer, TV, monitor, nada. I am far from the only one complaining, its everywhere on the internet but I am surprised to find so many happy LG users here on XDA (but thats actually a good thing). I was expecting to find more users like me who cannot stand bloat, corporate BS, locked bootloaders, ETC. Maybe its just me, but I cannot stand by any company that does not allow bootloaders to be unlocked, no one has the right to tell us what we can and cannot do with phones WE OWN!
LameMonster82 said:
Can you flash custom partitions with octopus box?
Click to expand...
Click to collapse
Yes but with the locked bootloaders, it is limited to "EMERGENCY FLASH" not the full bore flash. I can however cross-flash but I think that would only help if I had a .KDZ or .OCT that contains a rooted image for the EM model (or custom variant). I tried to load the EM model and unlock through the LG.DEV and it knew my IMEI was for a different model so it wouldnt give me the .bin file.
Octoplus LG:
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
GROOVYJOSHCLARK said:
Yes but with the locked bootloaders, it is limited to "EMERGENCY FLASH" not the full bore flash. I can however cross-flash but I think that would only help if I had a .KDZ or .OCT that contains a rooted image for the EM model (or custom variant). I tried to load the EM model and unlock through the LG.DEV and it knew my IMEI was for a different model so it wouldnt give me the .bin file.
Octoplus LG:
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
Click to expand...
Click to collapse
Maybe emergency flash could be enough. I know how to get root through flashing abl_a and ftm (I think) partitions from an EM module and using the unlock bin from the em model. Can you check if you can flash abl_a and ftm?
LameMonster82 said:
Maybe emergency flash could be enough. I know how to get root through flashing abl_a and ftm (I think) partitions from an EM module and using the unlock bin from the em model. Can you check if you can flash abl_a and ftm?
Click to expand...
Click to collapse
I actually deleted the .bin file a while back when it didnt work, if you have a new copy, I will try it. I am willing to try anything at this point to get off the stock OS, it is such junk! I am glad other users are happy, but I am surely not! I went from my own AOSP on my PME (HTC 10) to this over-bloated piece of junk that barely functions.
GROOVYJOSHCLARK said:
I actually deleted the .bin file a while back when it didnt work, if you have a new copy, I will try it. I am willing to try anything at this point to get off the stock OS, it is such junk! I am glad other users are happy, but I am surely not! I went from my own AOSP on my PME (HTC 10) to this over-bloated piece of junk that barely functions.
Click to expand...
Click to collapse
Yeah I have. Don't worry.
@GROOVYJOSHCLARK i need your help getting some info about the phone through your octopus box. Can you help me?
LameMonster82 said:
@GROOVYJOSHCLARK i need your help getting some info about the phone through your octopus box. Can you help me?
Click to expand...
Click to collapse
Not right this second but yes, just tell me what you need and I'll get it and reply. My box is home and I'm at the office in the city so it won't be until tonight or tomorrow morning but I will get it.
GROOVYJOSHCLARK said:
Not right this second but yes, just tell me what you need and I'll get it and reply. My box is home and I'm at the office in the city so it won't be until tonight or tomorrow morning but I will get it.
Click to expand...
Click to collapse
Just the box. The idea is to record how the box communicates with the phone and get a firehose file out of it. No need to flash anything. Just USB sniffing the recognition
Edit: tell me whenever you're ready and I will guide you if you don't know how
LameMonster82 said:
Just the box. The idea is to record how the box communicates with the phone and get a firehose file out of it. No need to flash anything. Just USB sniffing the recognition
Edit: tell me whenever you're ready and I will guide you if you don't know how
Click to expand...
Click to collapse
Just PM me whatever you need or here publicly if you think it's worth while for others.
Hi all,
So, my friend tried formatting the SD of this device and subsequently, the device turned itself off, now is not booting pass the loading icon, and will not turn off via hard shutdown (they just let the battery drain). I presume that the software has been corrupted. However, i am not familiar with this device or Pi etc. I have found the latest firmware and tool for the device amongst the comments. But the device isnt being picked up by Window.
I have gone ahead and started working towards forcing access to the device. I have started to install USBView to aid me. And will go from that. I suppose I'm more doing this out of interest.
But anywho, i just want some guidance on what i should be doing, or has anyone done this themself and or friend etc and could share what they did?
So, any help please would be great! And happy to answer any questions!
Thanks Kindly!
Leu Do said:
Hi all,
So, my friend tried formatting the SD of this device and subsequently, the device turned itself off, now is not booting pass the loading icon, and will not turn off via hard shutdown (they just let the battery drain). I presume that the software has been corrupted. However, i am not familiar with this device or Pi etc. I have found the latest firmware and tool for the device amongst the comments. But the device isnt being picked up by Window.
I have gone ahead and started working towards forcing access to the device. I have started to install USBView to aid me. And will go from that. I suppose I'm more doing this out of interest.
But anywho, i just want some guidance on what i should be doing, or has anyone done this themself and or friend etc and could share what they did?
So, any help please would be great! And happy to answer any questions!
Thanks Kindly!
Click to expand...
Click to collapse
You will have to solve the issue of getting Windows to recognize the device first. Then, you "might" have a chance, but, still no guarantees.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You will have to solve the issue of getting Windows to recognize the device first. Then, you "might" have a chance, but, still no guarantees.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Do you have any suggestions?
Leu Do said:
Do you have any suggestions?
Click to expand...
Click to collapse
When you connect the device to PC, does it make the connection sound? Does it show anything in Windows Device Manager? If either of these is no, you will not be able to fix this yourself. This will require expensive, specialized hardware/software tools or may even require replacing the motherboard.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
When you connect the device to PC, does it make the connection sound? Does it show anything in Windows Device Manager? If either of these is no, you will not be able to fix this yourself. This will require expensive, specialized hardware/software tools or may even require replacing the motherboard.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
It is no to those two. What software tools are you thinking I will need? I think the hardware would be fine, according to them nothing was broken. It was half formatted, so would make sense the hardware isn't speaking.
Leu Do said:
It is no to those two. What software tools are you thinking I will need? I think the hardware would be fine, according to them nothing was broken. It was half formatted, so would make sense the hardware isn't speaking.
Click to expand...
Click to collapse
The hardware/software tools are probably more expensive than replacing the device, then there is a matter of the significant technical skills required to use those tools, not an easy task, by any means. It's better to just replace the device as there are no guarantees that the process will even work, to begin with.
Or, replace the motherboard.
Edit: The hardware/software tools that I am referring to are things such as those required to run a JTAG service, RIFF box, Octopus box, etc. Pretty technical stuff, failure means replacing the motherboard or the device anyway, sooo....
Why waste the time and money?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The hardware/software tools are probably more expensive than replacing the device, then there is a matter of the significant technical skills required to use those tools, not an easy task, by any means. It's better to just replace the device as there are no guarantees that the process will even work, to begin with.
Or, replace the motherboard.
Edit: The hardware/software tools that I am referring to are things such as those required to run a JTAG service, RIFF box, Octopus box, etc. Pretty technical stuff, failure means replacing the motherboard or the device anyway, sooo....
Why waste the time and money?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I am doing it to learn, they are replacing the device. So, it isnt like a Pi? Ive never heard of these software tools either. Surely there is open source. I will dig around. I have experience to a degree.
Edit: as i said i am learning so i just want to ask why you have drawn that conclusion? Is that just general practice?
Droidriven said:
You will have to solve the issue of getting Windows to recognize the device first. Then, you "might" have a chance, but, still no guarantees.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
You have to reset with the Micro USB removed , otherwise it will not boot. that is the microsd card.
Hello I was wondering if there was a way to secure an Android device after unlocking it and installing a custom rom, maybe somebody has a thread or something.
Theoretically speaking anybody can take the device and do whatever he wants with fastboot or twrp.
Relocking it can have unforeseen consequences as some here have learned. I may be incorrect (depends on the variant too) as I don't root but the more you do, the more can go wrong.
I don't screen lock my device or encrypt my data because I don't want to be locked out, ever.
Physical possession is the only real security, relocking it isn't needed or desirable.
Anyone that tries to take my device is headed to the hurt locker. Consequences.
@fdor
Once an Android device's bootloader got unlocked ( disabling AVB included ) the device's Android is vulnerable.
blackhawk said:
Relocking it can have unforeseen consequences as some here have learned. I may be incorrect (depends on the variant too) as I don't root but the more you do, the more can go wrong.
I don't screen lock my device or encrypt my data because I don't want to be locked out, ever.
Physical possession is the only real security, relocking it isn't needed or desirable.
Anyone that tries to take my device is headed to the hurt locker. Consequences.
Click to expand...
Click to collapse
Thanks for the information, could you elaborate on screen locking? or link a thread I'm not sure what you speak of.
fdor said:
Thanks for the information, could you elaborate on screen locking? or link a thread I'm not sure what you speak of.
Click to expand...
Click to collapse
That's a separate subject but the concept is they same. Anything you lock especially will a password, you can get locked out yourself. Many times through no fault of your own as in a hardware failure.
An unlocked boot loader is a security risk... a bricked device much less so
On a stock Android Pie or higher (even not updated) security isn't an issue unless you do something stupid.
One reason I don't root.
Anytime you load unofficial firmware you're talking a risk plus it's distribution volume is much lower so if any malware is present it doesn't have as much exposure. Meaning it's likely to take longer to be detected.