Develop Bugs

My N5X doesn't charge anymore, anyway to relock Bootloeader?

I left my 5X charging in my room, went the to the kitchen, I took me like 20 minutes to go back and noticed that it didn't charge at all, I smelled this 'burned chip' aroma and I unplugged it in the moment.
Now it does not charge even with other cable I got.
Is there going to be a problem if I have the bootloader unlocked? As I can't connect it to the PC, I can't do anything to revert it to stock.
http://imgur.com/iEKkG4w

adb via wifi?

What happens if I lock the bootloader with System modified ? I have Arise Sound System installed, is it going to brick?

I have no idea how LG handles it.
Sent from my Nexus 9 using Tapatalk
From a reddit forum (https://www.reddit.com/r/Android/co...l_not_repair_screens_on_unlocked/?limit=500): "Actually when my nexus 5 broke, I definitely got my original device back. It had a relocked bootloader but LG didn't care and just repaired my power button under warranty."

It should not void your warranty.
Sent from my Nexus 5X using Tapatalk

I dont understand if we screw our phones up flashing crap google will replace it!?! Its not the phones fault that someone screwd up flashing! Is this true? I wouldnt replace it

hilla_killa said:
I dont understand if we screw our phones up flashing crap google will replace it!?! Its not the phones fault that someone screwd up flashing! Is this true? I wouldnt replace it
Click to expand...
Click to collapse
Nexus is very hard to brick with unlocked bootloader, though I guess anything is possible. The point should be that you should always be able to go back to stock with flashall.
Sent from my Nexus 5X using Tapatalk

hilla_killa said:
I dont understand if we screw our phones up flashing crap google will replace it!?! Its not the phones fault that someone screwd up flashing! Is this true? I wouldnt replace it
Click to expand...
Click to collapse
No, google will not replace your phone for software issues (unless perhaps it's google's fault). Hardware failures are another issue entirely. A bootloop is likely to be a software issue. A phone not powering on issue likely to be a hardware issue. An unlocked bootloader will not cause a hardware issue.
Sent from my Nexus 9 using Tapatalk
---------- Post added at 11:04 AM ---------- Previous post was at 10:27 AM ----------
Kusoo said:
What happens if I lock the bootloader with System modified ? I have Arise Sound System installed, is it going to brick?
Click to expand...
Click to collapse
I wouldn't relock the bootloader unless I restored stock. If you can relock bootloader, you should be able to run the flash all.bat. Are you able to access your device while connected to power? Go to recovery and factory reset from there. It will probably be factory reset anyway with repair. Also, it is possible that the no charging could be software related so factory reset is always first troubleshooting step.
On the other hand, if the device is not powering on, it won't for repair service, either, until it's repaired.
Sent from my Nexus 9 using Tapatalk

unlocking bootloader of Lenovo p2 will void my warranty?

hi bought Lenovo p2 and i wants to know that unlocking bootloader of Lenovo p2 will void warranty of the phone ?

Not in Scandinavia.
Thank you strong state that can give the little ppl some space against corps such as Lenovo

kongha said:
Not in Scandinavia.
Thank you strong state that can give the little ppl some space against corps such as Lenovo
Click to expand...
Click to collapse
what about INDIA?

satya365 said:
hi bought Lenovo p2 and i wants to know that unlocking bootloader of Lenovo p2 will void warranty of the phone ?
Click to expand...
Click to collapse
Yes it will, no point in unlocking now,....No custom rom is available with good base and volte supported.....wait some time, before check hardware issues with touch screen(some areas on touch dont work...open lenovo help app and do calibrate everything, speaker. etc
finally if you want to unlock, update to latest stock and unlock,....bcz to avoid major and minor modem issues.
also remember that 15 day timer has nothing to do, only unlocking command puts lock symbol on boot screen, this only void warranty when its collected. unlike some other phones there is no going back,its one way and you cant flash fastboot images completely.
i suggest you to use lawnchair.apk(google it) as launcher and wait, bcz existing custom roms dont make a difference to you, except problems like missing volte and other modem issues like no sim errors.....wait some more time......dont mess your new phone party.

pranavateja99 said:
Yes it will, no point in unlocking now,....No custom rom is available with good base and volte supported.....wait some time, before check hardware issues with touch screen(some areas on touch dont work...open lenovo help app and do calibrate everything, speaker. etc
finally if you want to unlock, update to latest stock and unlock,....bcz to avoid major and minor modem issues.
also remember that 15 day timer has nothing to do, only unlocking command puts lock symbol on boot screen, this only void warranty when its collected. unlike some other phones there is no going back,its one way and you cant flash fastboot images completely.
i suggest you to use lawnchair.apk(google it) as launcher and wait, bcz existing custom roms dont make a difference to you, except problems like missing volte and other modem issues like no sim errors.....wait some more time......dont mess your new phone party.
Click to expand...
Click to collapse
Firstly from the heart I would like to say you thanks. I check xda thread of each custom ROMs and i found that in every custom ROMs there is problem of volte & LED (as you also told this) but i wants to root my mobile for installing DOLBY VIPER4ANDROID etc. So is there any way to root without voiding my warranty? You told that on the boot logo it shows the lock symbol which indicates warranty void. What if i use custom boot logo? Also, give me your telegram id. I need some small help.

satya365 said:
Firstly from the heart I would like to say you thanks. I check xda thread of each custom ROMs and i found that in every custom ROMs there is problem of volte & LED (as you also told this) but i wants to root my mobile for installing DOLBY VIPER4ANDROID etc. So is there any way to root without voiding my warranty? You told that on the boot logo it shows the lock symbol which indicates warranty void. What if i use custom boot logo? Also, give me your telegram id. I need some small help.
Click to expand...
Click to collapse
No way to root any Android phone without unlocking bootloader. What ever you do, you loose warranty for p2. Why to waste new warranty for Dolby requirement. Better you buy good earphones than this Dolby..
If you can find p2 stock oedexed rom with Dolby then you work can be done without unlocking bootloader....I don't think it will....if I can find I reply you.

pranavateja99 said:
No way to root any Android phone without unlocking bootloader. What ever you do, you loose warranty for p2. Why to waste new warranty for Dolby requirement. Better you buy good earphones than this Dolby..
If you can find p2 stock oedexed rom with Dolby then you work can be done without unlocking bootloader....I don't think it will....if I can find I reply you.
Click to expand...
Click to collapse
ok... Does the default ROM which are on Lenovo p2 is AOSP (stock) based rom?

pranavateja99 said:
Yes it will, no point in unlocking now,....No custom rom is available with good base and volte supported.....wait some time, before check hardware issues with touch screen(some areas on touch dont work...open lenovo help app and do calibrate everything, speaker. etc
finally if you want to unlock, update to latest stock and unlock,....bcz to avoid major and minor modem issues.
also remember that 15 day timer has nothing to do, only unlocking command puts lock symbol on boot screen, this only void warranty when its collected. unlike some other phones there is no going back,its one way and you cant flash fastboot images completely.
i suggest you to use lawnchair.apk(google it) as launcher and wait, bcz existing custom roms dont make a difference to you, except problems like missing volte and other modem issues like no sim errors.....wait some more time......dont mess your new phone party.
Click to expand...
Click to collapse
What do you mean with "open lenovo help app and do calibrate everything, speaker. etc" i can't find a calibration option in that app

alese13 said:
What do you mean with "open lenovo help app and do calibrate everything, speaker. etc" i can't find a calibration option in that app
Click to expand...
Click to collapse
Did you find Lenovo help or Lenovo companion app. If not download from playstore.
Calibrate means test everything of your phone using that.
https://play.google.com/store/apps/details?id=com.lenovo.serviceit

alese13 said:
What do you mean with "open lenovo help app and do calibrate everything, speaker. etc" i can't find a calibration option in that app
Click to expand...
Click to collapse
Last time, I am about to root, I found my display is malfunctioning, market area didn't worked, got my display unit replaced.. So if I have unlocked bootloader. I would have lost warranty.
Before that I had a speaker issue, bcz it's still under 15 days,....got replacement. So I tell users to check everything is good before unlocking bootloader.

In theory, on europe no, because the warranty it's for the hardware and the company must show the proof that the problem with the smartphone hardware are related with the bootloader unlock.

Modified, Locked, S-on, Security warning. Bricked?

So it seems I'm in a very similar situation to people in other posts, and it's looking like my phone could be broken beyond repair.
UK, 02, stuck in a boot loop, Bootloader shows: Modified, S-On, Locked, Security Warning. I cant get into download mode (Download Mode failed to launch) but I can get into recovery mode (I get the red triangle with exclamation mark, Power+Vol Up gets me in). However, from what I read here in most other posts S-On + Locked + Modified means I wont be able to do anything. I have not flashed anything before I encountered this problem, merely let my battery run flat.
Is there anything I can do? I almost gave up, but this post here
HTML:
https://forum.xda-developers.com/one-m9/help/m9-locked-s-bootloader-download-mode-t3547560
gives me hope, as they seem in a similar situation with the exception of being able to get into download mode. Gives me hope I might be able to get into that and at least find out what firmware version I'm running.
Is there anything I can do or should I give up now and save my energy for sending HTC an angry email since this seems to be quite a common fault that's left quite a few people with bricks through (seemingly) no fault of their own?

Try "fastboot oem rebootRUU", if this isn't working you have a dead nand.

Strictly speaking, it's not an HTC specific problem. All phones with the Snapdragon 810 sooner or later suffer from similar issues. The heat of the processor kills the rest of the phones' hardware.
lucyr03 said:
Try "fastboot oem rebootRUU", if this isn't working you have a dead nand.
Click to expand...
Click to collapse
That command only works if the phone is booted to download mode which isn't possible according to the OP.
Sent from my HTC One M9 using XDA Labs

Ah! Thanks for that. I was scratching my head wondering how to get my pc to recognise my phone!
Dead NAND it is then?

blzbob said:
Dead NAND it is then?
Click to expand...
Click to collapse
Most likely. Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Most likely. Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah don't mention it. Thank you both for your quick replies. Last question (big long shot) is there any hope of recovering any of the files on there? I don't mind long projects and I'm quite handy with a soldering iron. Prise it open, try to locate something resembling a flash drive, try to remove that without further damage and find a relevant adaptor? I'm assuming even if i were to attempt this I'd be in for a lot of headaches and probably wasted time, but figured I'd try to explore all avenues.
Obvious even if there were ways to do this, the NAND problem is probably going further hinder any remote chances of success.

Did I brick my device? :(

I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement

i am just curious, how were planning on flashing a rom with locked bootloader?

ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.

Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.

gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."

gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?

Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?

ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.

ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.

ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!

I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.

My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?

dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!

Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.

ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs

mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.

ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs

mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.

ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs

Help to revive my HTC10

Dear Community,
My HTC10 is apparently dead but I trust that someone could have a great idea.
How it happened:
1st my config
- S Off
- Unlocked BL
- Running custom Rom - MHD latest version
- Custom kernel from tbalden
So the phone was at 65% of battery.
I rebooted in download mode to check some info (CID and version Mailly).
Then selected System Reboot.
It rebooted fine but then it became impossible to type in my pin code.
So tried to reboot with hardware combination... No sucess...
Then pressed and hold vol up + power for a while then the button at the bottom of the screen blinked 5 times then nothing.
Now it is not responding at all and even when I plug it to charger the led remains off.
I have also tried adb devices from pc... No success
Sent from my HTC EVO 3D X515m using XDA Free mobile app

Any advises or recommended testing méthod ?

chrisftlse said:
Any advises or recommended testing méthod ?
Click to expand...
Click to collapse
If it's not booting to any mode with all button configurations than we can't suggest or do anything.
Let it charge with the wallcharger for a while and try to power it up, connect the phone to a laptop and try to power it up with various button combinations.
See if the phone is in the devices list of the laptop/pc when you connect it, if you see a Qualcomm device it's probably bricked.

chrisftlse said:
Any advises or recommended testing méthod ?
Click to expand...
Click to collapse
Hold the volume down and Power together until it reboots.

leonardojt said:
Hold the volume down and Power together until it reboots.
Click to expand...
Click to collapse
Like that wasnt suggested in my post

Thanks Guys !
I have tried this but no success...
I am now trying to apply another possible solution as I read somewhere that if I am still able to see my device (even if it is the qualcomm HS-USB QDLoader 9008 plugged in my PC)... Then still chances exists to revive it.
But I still have to dig down this website (http://www.androidbrick.com/kategori/teknik-unbrick/)
I any of you here have reach this success a good experience sharing is more than welcome
BTW : HAPPY NEW YEAR

Can you reboot into TWRP? Re-flash from SD card.

hack14u said:
Can you reboot into TWRP? Re-flash from SD card.
Click to expand...
Click to collapse
No he can't ..... if it would only be that simple

Still no success so far...
I will continue to keep you updated (as it could help others within the same situation).
I have joined a team project from another community to work on the QFIL reflashing using qualcom tools.
But seems difficult as HTC are less open than LG or others manufacturer.
Anyway... Happy New year to you all

Hi community,
I have contacted HTC support and sent them my device, their diagnosis was a mainboard issue.
They have swapped the motherboard and sent it back.
I am sooooo happy.[emoji16]
They have also changed the entire screen...
So pleased with HTC support.
Very happy customer
Sent from my [device_name] using XDA-Developers Legacy app

chrisftlse said:
Hi community,
I have contacted HTC support and sent them my device, their diagnosis was a mainboard issue.
They have swapped the motherboard and sent it back.
I am sooooo happy.[emoji16]
They have also changed the entire screen...
So pleased with HTC support.
Very happy customer
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Glad to hear this story coming to a happy ending.
The 10 is still a wonder device!

andybones said:
Glad to hear this story coming to a happy ending.
The 10 is still a wonder device!
Click to expand...
Click to collapse
It still is a wonderful device.
Now I have to redo all steps to Unlock BL/Root/S-Off...etc..as I am back to 100% pure stock.
But first... Reading activities as these steps have been done like 1.5 year ago and do not remember exactly what to be done in which order.
Currently my system notification is pushing me to update to Oreo but I have read that it is preferable to root and other while in N as in O it will not be possible (yet).
Thanks for your support

chrisftlse said:
It still is a wonderful device.
Now I have to redo all steps to Unlock BL/Root/S-Off...etc..as I am back to 100% pure stock.
But first... Reading activities as these steps have been done like 1.5 year ago and do not remember exactly what to be done in which order.
Currently my system notification is pushing me to update to Oreo but I have read that it is preferable to root and other while in N as in O it will not be possible (yet).
Thanks for your support
Click to expand...
Click to collapse
I can't empirically speak for unlocking the bootloader Oreo since I already unlocked it a long time ago but, unless the process has changed on htc's site, it's still the same.
I can't speak for S-Off; read the Sunshine docs; I can't imagine that changing either. (My _opinion_ is that if one doesn't have a specific need for S-Off, then one only gains the risk of bricking the device, as evidenced by the numerous, redundant oopsie threads that would have been prevented by remaining S-On. This is why htc has S-On.)
I can say from experience that installing TWRP, Magisk, rooting all work the same post-Oreo update. (RUU Nougat, accept OTA/update apps, FDR, follow TWRP/Magisk instructions, install F-Droid/AdAway, clear Dalvik//cache, install everything else, profit). Give battery estimations a few days to get more accurate before thinking, "Oreo battery sucks!". The FDR and clearing caches is necessary to remedy bugginess and sluggishness, which would have also averted the numerous "my phone doesn't work right/is slow" posts.

Rolo42 said:
I can't empirically speak for unlocking the bootloader Oreo since I already unlocked it a long time ago but, unless the process has changed on htc's site, it's still the same.
I can't speak for S-Off; read the Sunshine docs; I can't imagine that changing either. (My _opinion_ is that if one doesn't have a specific need for S-Off, then one only gains the risk of bricking the device, as evidenced by the numerous, redundant oopsie threads that would have been prevented by remaining S-On. This is why htc has S-On.)
I can say from experience that installing TWRP, Magisk, rooting all work the same post-Oreo update. (RUU Nougat, accept OTA/update apps, FDR, follow TWRP/Magisk instructions, install F-Droid/AdAway, clear Dalvik//cache, install everything else, profit). Give battery estimations a few days to get more accurate before thinking, "Oreo battery sucks!". The FDR and clearing caches is necessary to remedy bugginess and sluggishness, which would have also averted the numerous "my phone doesn't work right/is slow" posts.
Click to expand...
Click to collapse
Thanks for feedback,
One of my aim is also to change CID (as it came back with the carrier one ORANG219, and I would prefer to 11111111 or HTC__001
But you are right S-Off could be risky if further actions are not made with caution