yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
I don't understand why anyone WOULD relock the bootloader of not stock:confused:
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Some people are not as experienced as us. Not hard to imagine, just noobs, no offense guys. You live and learn, no biggie. I say respect them and help them, I say welcome noobs.

If we expect our community to grow, we need to be respective of new comers.
[Google Pixel XL Guides, News, & Discussion] Alpione:
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
[Google Pixel XL Guides, News, & Discussion] arcanexvi:
This is honestly the biggest reason I can see as to why this happens
[Google Pixel XL Guides, News, & Discussion] ScytheSniper:
DELETED
[Google Pixel XL Guides, News, & Discussion] jcase:
There is nothing misleading about the post. The statements are true. Wait til tomorrow, when complaints start coming in about how people cant seem to unlock.
[Google Pixel XL Guides, News, & Discussion] jcase:
I'm not sorry. You are lacking information/knowledge on the subject. The OP statement is accurate.

The statement was made with good reason, based on fact and prior knowledge. You will see why tomorrow, when people start complaining.
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
The next security release should rollout tomorrow... And with that there will be a fix for VZW models preventing depixel8 from working. So IF you relock your bootloader after taking this update, we'll you'll be SOL. It's only misleading if you don't have prior knowledge of pretty much anything android.

I mean of course you can lock and unlock as many times as you want right NOW. Tomorrow will be a different story I guarantee.... But go ahead and be our guinea pig. I for one just say thank you [MENTION=2376614]jcase[/MENTION] and [MENTION=711482]beaups[/MENTION] and listen to their advice. They've been around a long time and given us lots of goodies. I don't question them.
[Google Pixel XL Guides, News, & Discussion] jcase:
I'm guessing you dont understand how depixel8 works.

I'm guessing you dont realize that google could remotely nix this in the butt any any moment

I'm guessing you are unaware of NDE63X at this point and it's effect on the situation.

Why don't you lock your bootloader for a few days, then try? or just sit back, watch ppl ignore the PSA, then start compaling about being stuck locked.
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
Clearly you don't know of jcase. You've been warned. If you want an unlocked bootloader on Verizon pixel... Leave it that way. Depixel8 is about to be blocked.
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
I for one would love to know more about all of this... But since I don't I listen to your recommendations. I got my popcorn ready for those that don't though that's for sure.

Just a side question for you... Do you know exactly what Google Verizon is using to differentiate between a Verizon pixel vs a GPS version? I was under the impression that they were the same hardware so curious as to what's in the software that determines which pixel bootloaders get locked down, and which one remain open to unlock.

You are an advocate of locked bootloaders I know, so does that make a GS version less secure than a Verizon one?

---------- Post added at 04:59 AM ---------- Previous post was at 04:57 AM ----------

Dude, now you're just playing on weak semantics. Depixel8 has been out for what? 1 week? 10 days? It will be patched tomorrow making it a completely valid statement.
[Google Pixel XL Guides, News, & Discussion] jcase:
Its patched in the DF update that has been rolling out for the last couple days. Meaning... there are devices that are ALREADY patched against dePixel8. Tomorrow it will cease being a DF update, and be a general update, meaning even MORE devices will be patched.

In addition to that, there are other reasons to not relock if you want to be unlocked again, but instead of asking why you just wanted to tell me how wrong I am.

Again, please lock your bootloader, keep testing your theory for me.
[Google Pixel XL Guides, News, & Discussion] jcase:
I dont know all the differences. I believe security wise, its the same.
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
Tell that to Samsung S4 users who tried to root after the MDK bootloader was updated and got a brick. Or countless other threads on here with bounties for unlocked bootloaders that were never cracked. It's possible, but until it happens, if you want it unlocked, leave it that way.
[Google Pixel XL Guides, News, & Discussion] jcase:
I think you need to stepback and realize how rude you are being, and how bad the advice you are suggesting is. There will be people that follow your advice get stuck locked. They will come cry to me, it will suck for them and annoy me.

It is entirely possible (not saying probable, as I suspect they will go another route) that his patch could stop the bootloader unlocking on the device for good. I'm quite familiar with the Pixel's bootloaders. One minor change could nip this in the butt entirely. I will say that their hasnt been anyone else for the last few years releasing HTC hacks, besides beaups and I. I can say it is unlikely we will target the Pixel again. Just because people can do it, also doesnt mean they will.

It is more likely that you WONT see another pixel unlock tool than you will. If we do see another one, it will probably be limited to a subset of firmwares, and unlikely it will work on whatever the current firmware is.
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
Yes. But if you follow jcase at all (I suggest you do if you own any HTC Android device) you would know that prior to releasing depixel8 they reported this vulnerability to Google (among others they didn't release publicly) and warned many times to use it prior to the update coming Nov 7th. So if you or anyone else didn't see those warnings, then your jumping in to quickly. It's been said from day 1 of the release and tomorrow is D-day. I was going to wait for a 128gb version to be in Stock. I kinda figured it was something that once cracked would remain cracked. But I jumped in the best buy deal ($100 gift card and new chromecast) when I heard it would be patched by Nov 7th. So the warnings out there... And has been out there. I'll make do with 32 for an un locked bootloader and payments on my bill.
[Google Pixel XL Guides, News, & Discussion] jcase:
I'm quite calm. You are being quite rude, and your posts are going to get people stuck. They are going to come to me, blame me, complain to me, and in general annoy me.

My explanation is fine if you want to go make another one, go for it, go do it in your own thread.

Its not misleading, it is accurate.
[Google Pixel XL Guides, News, & Discussion] jcase:
You didn't ask me to elaborate, read your post again. Asking me to elaborate would have been polite, I would have elaborated on the reasons the statement is true.

You are being rude, you are suggesting things that are not true for everyone, you are making statements as facts without knowing the whole story.
[Google Pixel XL Guides, News, & Discussion] jcase:
Read you post again, I read it several times, no where do you ask me to elaborate. Instead of asking me to elaborate, you went into to how I was wrong, or that I shouldnt say what I said.

No one called you stupid, I said you lacked information, which you do.

Unprofessional would be stepping into something you dont know about, and start correcting people who do.
[Google Pixel XL Guides, News, & Discussion] george241312:
Damn i went full retard and locked my boot loader while it was modded heavily ended up with softbrick with no way to flash stock system.

I got lucky after using fastboot continue it started hanging on boot screen then did a hard reset and ran the command again and it booted up.

Lucky as hell.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Omg jcase is right your wrong simple as that I understood the post just fine explained everything just cause your interpretation of it made you not understand doesn't mean it's misleading at all just reread it until your brain gets it simple as that like enough is enough this is just a stupid argument your picking on some that was never wrong to begin with also it ever said you can't unlock your bootloader after relocking it said don't do unless phone is stock also first posts every about this said it will be patched so if you want a unlocked bootloader yo basically make sure it's unlocked before such date
[Google Pixel XL Guides, News, & Discussion] joderme:
People still wonder why the devs run away or simply refuse to release exploits...
[Google Pixel XL Guides, News, & Discussion] krypto1300:
Very good info here. Thanks!!!
[OnePlus 3 Questions & Answers] mrbright25:
I have been trying Nougat builds pretty much since the first test builds came out. Since the start, I noticed that the resizeable window function is not a available as it is for say the Nexus 6P. Is there a reason why the multiwindow view mode isn't adjustable on the OP3?
[OnePlus 3 Questions & Answers] HellsDelight:
You mean the feature to e.g. have 2 Apps showing on the same screen? Multi-Window was integrated in Android 7.0:

https://developer.android.com/guide/topics/ui/multi-window.html
[OnePlus 3 Questions & Answers] AJay27:
Correction :

It's working on AOKP 7.1 for me. I can resize the multi windows.
[OnePlus 3 Questions & Answers] AJay27:
Screenshot : [MENTION=5992494]mrbright25[/MENTION]
[OnePlus 3 Questions & Answers] mrbright25:
What rom are you using? I am not able to resize any of the apps I use, look:
[OnePlus 3 Questions & Answers] AJay27:
AOKP N 7.1 4th Nov Build.
[OnePlus 3 Questions & Answers] mrbright25:
Could you give me the link, please? I can't seem to find it.
[OnePlus 3 Questions & Answers] AJay27:
ROM

https://www.androidfilehost.com/?fid=312968873555011515

Full Thread : http://xdaforums.com/oneplus-3/development/rom-android-kang-project-aokp-t3417693/page43
[OnePlus 3 Questions & Answers] mrbright25:
Thank you!
[OnePlus 3 Questions & Answers] AJay27:
Happy to help :)
[OnePlus 3 Questions & Answers] mrbright25:
For some reason i still can't resize the windows! Did you flash a different firmware before flashing AOKP or did resizing just work out of the box?
[OnePlus 3 Questions & Answers] mrbright25:
I know but I've never been able to use it! Is it functioning for you?
[OnePlus 3 Questions & Answers] AJay27:
I was on stock OOS3.2.7. And I did a clean flash to AOKP.

Also I've flashed the pixel experience zip from here.

http://xdaforums.com/google-nexus-5...her-7-1-3231428-flashable-zip-t3477798/page14

Not really sure the ability to resize is due to this but give it a try.
[OnePlus 3 Questions & Answers] mrbright25:
That's strange, I'll try reflashing 3.2.7, thanks!
[OnePlus 3 Questions & Answers] mrbright25:
I've tried flashing to full stock 3.2.7 and flashing just the firmware and nothing works. I legitimately don't understand why I can't get it to work.
[Samsung Galaxy S7 Questions and Answers] Z123456990:
The phone model: SM-G930W8

Software Build: G930W8VLU2API1

This is my father's phone and he went overseas to travel. During his travel he wanted to unlock his phone so he went to some shady area and they apparently rooted his phone but messed up somewhere. They told him to reinstall the firmware and it will be good. Unfortunately that isn't the solution and I have no clue what is the problem.

The mobile networks always has the cross symbol and no option for it exists in the settings. The IMEI and Baseband number here was unkown. I then got the latest firmware from sammobile with the same network as the phone, Koodo 6.0.1 and installed that. The problem still existed so I found this thread http://xdaforums.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 and have been successfully executing all the steps except for flashing the binary firmware which seemed like it would solve the problem. It has however, removed the no network symbol. The IMEI is now all zeros. I have the original IMEI number, just trying to find a way to put it back in.

I noticed that the factory binary filename is a little different compared to the firmware version the phone has. The one that the factory binary is referring to G930W8VLU1APG1 and the one on the phone is G930W8VLU2API1. Then I thought maybe if I downgrade the firmware to the one that is the same one as the factory binary one, it would then work. I went to sammobile and downloaded that too, but the same problem occurs, an error in Odin thats preventing me from doing this. Not sure how to proceed from here.

The problem that showed up on Odin was:

Thanks for any help.
[Nexus 4 Q&A, Help & Troubleshooting] MotoMileCm7:
My nexus 4 had Red light anytime when i try to charger it. I try ro replace a new battery . any solution?? Thanks
[Nexus 4 Q&A, Help & Troubleshooting] lebidou:
Hi I just solved the same issue today.

I opened the phone up, unplugged the battery, then unplugged everything I could find, replugged everything back, and that did it.

It is to be noted that I replaced the card with the USB port on it. Twice in less than six months. I hope I won't have to open that phone again, and that your phone will run again.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Q&A, Help & Troubleshooting] stuart_f:
I replaced my battery with one from eBay hoping for the battery life to be restored. Sadly, although it works, battery life remains about 6 hours :(

I also get the red flashing light when I charge (even with the new battery) but it eventually goes away and starts charging.
[Nexus 4 Q&A, Help & Troubleshooting] lebidou:
Maybe the part with the USB port is damaged somehow. I also had battery life issues. Looking at the wakelocks it turned out it was the slim port (the USB hdmi thingy). Since I replaced that part, my battery life seems restored.

Have a look at wakelocks and alarms with apps such as Better Battery Stats.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Ascend Mate 7 Q&A, Help & Troubleshooting] estellebety:
Good evening, help me update my Huawei mate 7 (MT7-L9 B329 single sim) French version of android I want to update to 6 or more. I'm not an expert and I need a good Detailed tutorial.thanks to help me .
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] KarhU:
There have been multiple cases of Radios suddenly stopping to work lately. This is not related to NO GSM error as these occur while phone is in use and not while flashing.

Symptoms are as follows:

- Radio suddenly ceases to work (no signal with any SIM), or its condition deteriorates over the time.

- While trying to flash a different Radio ROM, the upgrade stops at 0% and bricks the device

- Devices can be recovered to operating state, however only OS is intact and GSM radio does not work.

- MTTY gives no feedback

- Information about device resembles these symptoms:

Radio Version : Nothing

Protocol Version: Nothing

IMEI : Nothing

Possible causes of this problem:

- Hardware fault

- Radio ROM corruption

- Bad blocks in NAND

This phenomena seems to be the new source of bricked Hermes devices and the number of occurences is growing.

Threads of people with this kind of bricks:

http://xdaforums.com/showthread.php?t=346315

http://xdaforums.com/showthread.php?t=345230

http://xdaforums.com/showthread.php?t=347145

http://xdaforums.com/showthread.php?t=346894

http://xdaforums.com/showthread.php?t=338413

http://xdaforums.com/showthread.php?t=322587

http://xdaforums.com/showthread.php?t=325018

http://xdaforums.com/showthread.php?t=343260

There also were some threads with this issue in the Hermes WM6 forum.

What we do not know is:

- What was the last radio version those people used?

- Did they use custom ROMs or did it happen with official ROMs too?

- What do these cases have in common?

- Is it really a hardware fault (no results from the service centers so far)?

- Can something be done to prevent this kind of bricking?

- Anything that might help those people recover the phone capability of their devices.

Please share your knowledge about this problem so we can know what kills our device's radio.

Common symptoms:

ROM with radio (both official and unofficial) - flash stops at 12% (magic number?)

Radio ROM stops at 0%
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Asxetos:
After reading a lot about flashing - upgrading the Tytn, i think the first question to be answered is:

Has anyone with an official untouched device had the radio death situation??

(i.e never had any cooked-baked-boiled rom or radio other than the official flashed on the device)

On every incident i have read, there was at least one mentioning of "Unlock, SuperCID, HardSpl, cooked XXXX-WM6 rom, and so on.

Is it a coincidence?

Dont get me wrong, i my self love this forum and have used tools and roms many times (previously on my MDA Pro and now on my Tytn).
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] chicharon:
my unit started the NO GSM syndrome just 3 days after i upgrade to 1.54.00 radio..

ROM without radio - flashes 100% working

ROM with radio (both official and unofficial) - flash stops at 12% (magic number?)

everyone else has thier rom + radio flash stop at 12%
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] acr80:
I would add: http://xdaforums.com/showthread.php?t=343260
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] KarhU:
First post updated with your comments&link.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] trion:
I opened mine this week, cleaned the inside and also taken the metal covers inside off. One very small chip looks like it has a little brown spot on it, like it has gotten too hot.

Don't know if this is the problem or not, but i think it has to do with the radio and that it's fried :(

my radio rom was 1.54 something i believe.

and before it broke my phone started to hang short times for a few weeks and when it got back the radio signal was also lost,so i guess it was starting to break down :(

now it is just a pda, i connect it to internet through my old phone, but it takes 5 minutes after turning on before it will use bluetooth, some programms also refuse to start in the first 5 minutes.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] sbrown138:
I have been seeing what I think is the beging of this issue. It started about a week or so ago, my phone locked up on a call so I soft reset it. IT cam back and I was able to use the phone again. About ten minutes later it locked again and this time when it came up my passcode would not work. After trying to log in 8 time it hard reset itself. I let it reset and then I upgraded my radio from 1.48 to 1.54.07.00 as I thought the radio was hanging the phone. A few days went by and everything was fine. Then I started to notice the radio was completely loosing signal and seeminlgy locking the phone. The only fix seemed to be a soft rest (at the time) This went on for a few days and eventually my password died again after a soft reset. and it hard reset me. At this point I upgraded from vp3G 3.0 to schapps 4.20 and 1.54.30.10 for the radio. Again it helped for a day or two maybe but it has not started to loose radio signal completely (no service and modem disconted error etc were I always have signal) I have tryed a few diffrent rom and radios in additon to all of these and still get the issues. Last night I got some more clues after installing the new google maps with the my location "soft gps". I was playing with it on my ride home folling my trip etc and about 25 min in my radio started acting up. This time the only thing that fixed the issue was to remove the battery and sim card and put them back in. I am startign to think this is a heat issue in one of the radio components. I also have a ruberized cover which could contrinute to a heat issue. Also for the record I have IPL-1.04 and SPL-2.10-0lipro.

Can anyone comment on ROM botloader etc AT&T would want to see on the phone if I got them to replace it? It is only like 3 months old.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Prerna:
Ma

Great idea to open this post. Here's my experience of 2 issues I had this week:

First, I changed the ROM to HC Lite, and the Radio to 1.54.30 last week-end.Before that I never had an issue with GSM.

3 days later I operated a clean-up, using Oxios Close-Apps and Hybernate.1 or 2 hours later, the GSM signal disappeared, and the green button stopped responding. I also noticed I was unable to open "Contacts". Nothing would make it come back, not even a soft reset.

What I did is a Sprite backup, in case, then a hard reset. Everything was then back to normal, so I restored the backup, and it kept working! Now the sad part is that the exact very same event occurred today.

I'm a bit confused whether the issue is hardware related, or is it to do with the radio, the rom..? Anyway, I will right now change the Radio so as to see if any improvement. Your comments will surely be appreciated.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] sdemon:
It seems to be related to the newer radio versions. I am running the 1.47 that came with the official Dutch WM6 Rom and have had no problems what so ever with Schaps Rom. So my guess is that it is related to the 1.54 versions of the Radio.

Anyone had these problems with the older radio versions?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] blackout128:
Just thought I'd add some info to this topic. I have been running Radio 1.54.00.10 for about 1.5 months with Schaps 4.20 and vp3G's 3.62.3 and have not had any problems with reception, phone use, etc, but I ran 1.54.07.00 radio for 2 days and it was terrible.

It would hunt forever for a signal. If I went into a building and lost reception, I would have to soft reset to get a signal (after I left the building). I figured something was gonna get damaged(too much heat).

I don't know if anybody's experience with that version was as bad as mine, but I hope this problem can be narrowed down to a particular radio rom.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Alcibiade:
I had the same kind of behavior with mine. Radio was 1.47

After a few days of similar misbehavior... the radio died
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Alcibiade:
Nope, I had it with 1.47 back 6 months ago...
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Alcibiade:
By the way

To me it is obviously hardware related: if I try to flash the radio 5 or 10 times I end up managing in flashing it (I have to try, retry, etc...) with another radio. However... I still have the No GSM issue, even after the new radio has been flashed

It's the best proof soemthing is broken inside, not just the radio
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] eagercrow:
I've had this issue with every radio after 1.47, and multiple cooked ROMS, I've tried every radio newer than 1.47 with a bunch of different ROMS. My phone hasn't died....yet but I wouldn't count on it in an emergency or any urgent situation.

I haven't even had this phone 1 year, no way I'm going to spend 300+ AGAIN because of a ****ty HTC product.

What error messages are you guys getting?

I get (not verbatim) the following very often:

phone not ready, wait 15 seconds

answering modem has disconnected

(not a message) searching for signal

(not a message) no signal, just a ! in the signal meter

call not completed

(not a message) phone hangs when dialing a call

(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.

I have noticed lately that I have less problems in 3G areas.