yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] jwleonhart:
UPDATE:

OK I'M BACK INTO RECOVERY.

Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?

When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?

I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

so I received a new Nexus 6 device from T-Mobile for my girlfriend.

In our area unfortunately Wi-Fi calling is a must, so she went ahead and did both of the OTA updates. After doing the second update the phone was stuck optimizing apps, and then the screen wouldn't work...

So I then hooked the phone up to the PC and through ADB did the following commands

fastboot erase userdata

fastboot erase cache

That was supposedly the commands I had found on the internet to go ahead and factory reset the phone.

Now the phone is stuck at the balls swirling and it won't stop. Try and hold the power button down and the phone just restarts itself, won't shut down so I can't even get back into the recovery.

I tried to first load up a factory image before doing something silly like that but when I tried to run the command "fasboot oem unlock" it says I need to enable developer options in Android... which I couldn't get to anyways...

Can someone please help with this issue. Her old phone got stolen and now she has this one which is completely messed up.

Thank you for anyone who can help me!
[Nexus 6 Q&A, Help & Troubleshooting] USMC retired:
none

You have to hold power and down on the bottom button, or since you have adb, you can do "adb reboot recovery". Push volume down first then power. After that you can enable MTP and toss a rom on the phone. Do a complete wipe with the exception of the internal storage ( I did storage one time accidentally, yuk) flash a ROM and you should be good
[Nexus 6 Q&A, Help & Troubleshooting] jwleonhart:
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.

When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
It should shut down if hold the power button long enough. Takes like 20 seconds or so. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] jwleonhart:
OK I'M BACK INTO RECOVERY.

Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?

When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?

I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
As far as I know with stock recovery about all you can do is try to format cache and try to factory reset again. Otherwise will have to take back to T-Mobile and RMA. Make them update it. Lot of OTA updates have been failing. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] jwleonhart:
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.

Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.

Seems like a whole pile of sh*t if you ask me.

Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
There is no way to flash a recovery without the bootloader unlocked. On these devices it is best to unlock bootloader first thing before trying to update so have some control if things go bad. Moto has the ability to reflash them like J-Tag. TMobile store may replace it. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] jwleonhart:
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.

So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Yea. It a bad situation. We have seen a lot of them choke on the OTA flash. Best to unlock upfront and fastboot the updated factory image. You are always safe once it is unlocked. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] jwleonhart:
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
I understand. They look at unlocked bootloader as a security problem. It even tells you it disabled security when you flip the unlock switch. From the many OTAs we have seen brick it is best to just unlock even if running stock. Once it is up and running can always relock. Do not relock if have custom recovery or kernel tho. It will more than likely bootloop. I tried it for grins but made sure the unlock option was enabled and was able to unlock and reflash. Many have flashed new software and relocked before first boot to find out it bootloops and can't unlock again. Best to have TWRP so that if is locked have a adb/MTP option. We pretty much discourage OTA. I haven't tried but have seen a post that says must be locked to OTA. If that is the case you always have the chance of a bad OTA flash and end up same place you are now. With TWRP there are also OTA files that have been converted to flashable zip and can be flashed in recovery. :cool:
[HTC One X+] PEPPARO:
Dear All

I have HOX+ Pattern locked

- WiFi Off

- Mobile data Off

- USB Debugging Off

sorry , but relay need your help Pleas :rolleyes:
[HTC One X+] Lloir:
Factory reset
[G4 Q&A, Help & Troubleshooting] Fma15:
I want to root my g4, but in the video im using I was told to get the KDZ firmware from this website http://devtester.ro/projects/lg-firmwares/#imei. When I enter my IMEI it says Nothing found for ______. So where else can I go to get it? Why isnt my KDZ on this website? This is the link to the video Im using https://www.youtube.com/watch?v=mZM-...ature=youtu.be
[G4 Q&A, Help & Troubleshooting] Fma15:
Bump.
[G4 Q&A, Help & Troubleshooting] trickie69r:
Try here: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI

(Replace the word IMEI with your actual IMEI number which you can find by dialling *#06# on your LG G4 Dialer)

Then look for something like:

<sw_url>h t t p://csmgdl.lgmobile.com/dn/downlo...D81510A_00.kdz</sw_url>
[G4 Q&A, Help & Troubleshooting] Fma15:
Thanks for the reply! There is no link beside my <sw_url>.
[G4 Q&A, Help & Troubleshooting] faizalotai:
Because its not available yet or forever..
[G4 Q&A, Help & Troubleshooting] Fma15:
So is it necessary for me to have it before I try to root.
[G4 Q&A, Help & Troubleshooting] clockcycle:
Only as a backup in case something goes wrong and you need to recover. Risk BRICKING phone. YMMV

---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------

http://xdaforums.com/g4/general/lg-g4-sticky-roll-thread-t3128004

http://xdaforums.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
[Galaxy S6 Q&A, Help & Troubleshooting] TheNakedGun:
i have a vodafone s6, italian one.

I'm getting "cell standby" as a drainer on my battery stats.

I found some threads on the verizon an at&t s6 saying that turning off VoLTE and "Advanced Calling", then rebooting in recovery and wiping cache solves the problem.

Only problem is that my vodafone s6 (on android 5.1.1.) doesn't list these options on the menus.

I already tried wiping cache in recovery but no luck!

Can anybody please help?
[Galaxy S6 Q&A, Help & Troubleshooting] TheNakedGun:
Really? No one?
[Galaxy S6 Q&A, Help & Troubleshooting] Skin1980:
I've got that drain too under Vodafone until I turned off fast dormancy. Maybe it's a placebo but I don't see anymore that voice I the first places.

So try to add to your build.prop

ro.ril.fast.dormancy.rule=0
[Galaxy S6 Q&A, Help & Troubleshooting] roydok:
Try flashing this updated stock 5.1.1 Italian Vodafone ROM via odin. ;)

http://www.sammobile.com/firmwares/download/52358/G920FXXU2POGJ_G920FVFG2BOG2_OMN/
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Hey folks,

Any of you have Google Cardboard V2? I've found some odd things and just trying to find out what everyone else's experience is.

Firstly, what I thought I had worked out and, I'm not so sure now...

Older cardboard / VR apps are pretty much full screen side-by-side, where as newer apps, since Cardboard v2, seem to be smaller portals side-by-side. The full screen apps, I cannot focus on, so nothing really works right. Where you're supposed to see one object, the focal point seems to be out, so I see two objects. In contrast, the newer apps focus much better and I see one object.

That said, I did notice that with the fuller screen apps (this one can do both settings: https://play.google.com/store/apps/details?id=com.fibrum.crazyswingvr&hl=en_GB) that even though the image is not looking right, there is a much greater sense of movement, to the point where my head actually felt like it was moving with that game I just linked. But putting it to the "right" setting, the sense of movement was much less.

But here is where it gets complicated. I set my DPI to 400 as I like things pretty small on screen. I actually didn't think it would affect these apps, but I was wrong. I thought I'd change it back to stock (560) just to test it. The portals on the newer apps got much bigger (almost full screen) but the problem re-occurs that I cannot focus properly on the screen, just like with the older full screen SBS views.

I've set my DPI to 460, which seems to be a sweet spot. I get the sense of movement with the app above yet can still focus on the objects in the screen. What I don't get though, is why it won't focus with Stock DPI. Don't get me wrong, I don't want to use Stock DPI, and if I am forced to use 460, it's not the end of the world. It just strikes me as odd that the Nexus 6 stock DPI is out of focus for me in the Cardboard v2 and that perhaps it shouldn't be... and that maybe even the older full screen SBS should be working for me.

I'm hoping other cardboard users who mess with their DPI may be able to share their experiences with me here.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Further, the older apps don't seem to be DPI aware, and I think that because V1 would not fit up to 6" phones, these apps don't focus right because they're designed for smaller screens.

I still don't understand why the Stock Nexus 6 DPI would appear to be "too high" for cardboard v2 though
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
No one has a cardboard v2?

With 460, the eye portals seem to match up with the cut outs on the cardboard. Perhaps it really is the case and what we felt was always true, google set the DPI far too big on this device.
[Nexus 6 Q&A, Help & Troubleshooting] Unb0rn:
Hey, Op! Ordered myself a chinese clone of Cardboard v2, got it yesterday, aaaand... all I've got was a double vision. Thought at first, maybe all the problems were in lenses or assembly, checked it, next thought was about difference in inter-lens distance(it's really too small for my face), so I decided to try using it with another phone(Nexus 5 running latest stock ROM)-everything was fine with it. After that tried to play with DPI on my CM12.1 Nexus 6, and it seemed to work! On 480 DPI everything matches and on 520(it's the next step in CM's setting, I don't want to change prop myself) it starts to double. Maybe it's some kind of ROM issue? What ROM are you using?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Its definitely not a rom issue.

Here is what I have noted myself.

Google cardboard sdk1 is full side by side. If you put a full side by side app in the cardboard, the nexus 6 is too big, means you cannot focus on it because the centre of each side is too far apart.

If you put a full side by side on a smaller screen, such as nexus 5, the centre of each side is closer together, so they focus correctly.

The only way to get a big screen phone to work is to make the "screen" smaller. That's why google invented sdk2. This new development kit allows apps to be scaled according to dpi, so on a small screen they are correct and a larger screen also, they scale down correctly.

That said on the nexus 6, the stupidly high dpi 560, makes everything look stupidly big on the screen, and I think this makes the sdk2 apps too big on the screen too.

460 dpi seems to work for me.
[Nexus 6 Q&A, Help & Troubleshooting] Unb0rn:
Made additional tests on two nexuses(nexii? :) )-it were two Nexus 5's, one running latest stock Android 5.1.1, and another-one of the latest CM 12.1 builds. Issues were only with CM12.1's nexus, it has a wider-split images and the only way to make double vision disappear was by crossing eyes a little. On stock android everything was fine, just when I plugged it into cardboard. I don't have second Nexus 6 to make a test with it, but it looks like custom ROMs may be an issue...
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Interesting. We should compare screenshots or something :)
[Nexus 6 Q&A, Help & Troubleshooting] Unb0rn:
Will do, next time I gather up my friends with their devices)
[Nexus 6 Q&A, Help & Troubleshooting] Unb0rn:
Hey there! Made a test on my Nexus 6-all the images are inside attachment.

Tried Cardboard v2 on stock Dev Preview 3 (it worked) and on latest CM12.1(it failed-double vision)
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Thanks got testing but I don't think the cardboard app itself does justice to the results.

I'm using snow mountain, SDK 2 app. I've taken images on Slim Rom at 420 dpi, 480 dpi and 560 dpi.. Because of how the app looks, you can see how dpi effects it..

420 looks best for focusing.

480 looks ok, and gives a good sense of immersion and movement in games like rollercoasters etc....

560 though, it's too big and cannot focus.. It's like the older games.. Also notice that the size of the "eyes" is bigger than the actual cut out on cardboard 2 devices..

I personally believe that 560 dpi is just too big for this display and for cardboard.. To make things work in cardboard, things on a big screen must be the exact same size as on a little screen. I think SDK 2 is supposed to scale using dpi to do this, but the dpi is too high on nexus, meaning it gets proportionally bigger to the screen size, meaning too big...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Paul Koty:
Hi,

can You help me pls with ny LTE i9305 S3? I have problem with signal (antena OK, any sim any network), is just good outside but whan I go somwhere in house, is very bad or stop working network. I am not sure if can be some chip on motherboard problem, or if I solve this problem by some flash.

Thanks
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] juliancarney:
Does it happen when you go inside in any place or just in your house? If it's just in your house then clearly it is just a problem of coverage on your area. I9305 international version supports bands 800, 1800 & 2600 for LTE where both 1800 and 2600 have bad coverage inside buildings. Check as another test if selecting 2g (pure GSM 900) you still have bad coverage. Can you try with a SIM of another carrier? This could also be the definitive test.

If it is a common problem (anywhere, any carrier...), then maybe you can solve it by flashing with Odin a different modem baseband (also called radio).

You have some basebands for download here:

http://sourceforge.net/projects/djb-tgp/files/CWM_Flashables/Modems/4.3 Modems/

I'm using the XXUENA2 with very good results, been used before others also with no major problems (XXUEMK1 and XXUFNI3 for example).

This is my "About device" screenshot where you can see the Baseband I'm using. Works fine in Europe as well as in Brasil:

https://mega.nz/#!Mh1RkbAY!k7l1vTQlxlas5S6OopO9054X-5P7yBpkJrXL_bv5-Fw

-jc
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Paul Koty:
Hi, thanks for Your reply

my problem is in house, but anyway problem with signal is without any sim always.

So I have now 4.4.4 and pls can You show me where I can download good one modem for this Android for my LTE? I´ll try it

thanks so much

EDIT: I have one. Is South Africa 4.3, there is XXUENA2 Modem, so I´ll try it and let You know.

EDIT2: So I have problem, I can´t downgrade 4.4.4 to 4.3 because will EFS faulty, so You have some idea how I can choose repair my modem for signal repair?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] juliancarney:
Hey Paul...

1) About signal: how do you expect to get signal without SIM? Or maybe are you meaning signal for just the 112 emergency call?

2) Modem/baseband: I already provided the link in my original post, check it.

3) No need to downgrade. You will only flash the modem/baseband without touching any partition, neither the ROM nor the EFS. You can do that via Odin (check any Odin How-To document -search Google-) or via the recovery if you have TFRT or QWM (at recovery menu select flash zip file and choose the one for the modem -you need to copy the zip file previously to your sd card or internal memory).
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] sunny1739:
Signal problem

Hello.Sir I have a s3 i9305 when i am on LTE auto network mode then i was unable to make any phone call it always show wrong mmi code or connection problem and then it lost signals after that i rebot it then it pick the network can you tell me how to fix
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] tkontonis:
I have a connectivity problem with my S4 mini. I own a Nikon camera with connection feature to a mobile device through wifi. The camera starts transmitting a wifi network like a hot spot, in which i can connect my phone and through Nikon's app to take pictures or download existing ones to my phone. If i use a Samsung A3 i own with stock rom the connection is immediate. When i try to connect with my Samsung S4 mini (i9195) running the latest cyanogen 12.1 rom, i never pass the "getting ip address" stage of the wifi connection. Can anyone help me with this problem?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] ddebeer:
The same problem occurs on two Oneplus One phones, running resp. CM12 and CM12.1

On the CM12 opo I by now get as far as getting connected, but further negotiations keep on going until the camera gives a 'refused' message.

On the CM12.1 opo I still am in the phase of getting the WiFi connected. Setting it to WPA2 AND adding the network's gateway did help on the other phone.

The same camera connects without any problems on our Galaxy NotePro tablets, running resp. stock Android 4.4.2 and 5.0.2

There should be a solution, but until that moment I consider this a probable bug in cyanogen mod.
[G2 Android Development] ferreirawax:
Hello,

A few days ago I wrote a new implementation inspired by the work of CyboLabs and Codefire that in harmony contributed for the creation of Open_Bump. Basically I rewrote Open_Bump using POSIX C to run directly on LG G2 or any compatible device with Open_Bump. So now you can bump any kernel or recovery using the target device, validate images to know if they have been bumped and other things.

The source code and binaries for Linux and Android found at: https://github.com/ferreirawax/cbump

Cheers!
[G2 Android Development] iko11:
It will be useful for developers, thanks for the effort
[G2 Android Development] wulsic:
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.

Just some questions:

so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?

And with your usage:

usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]

Is it both stdin or must the last one be stdout?

usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]

Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.

Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
[G2 Android Development] ferreirawax:
Hello,

I know that Python works well, but Cbump was thought to be portable. I did not even know about MultiROM, I checked now and discover that he used the unrepresentative signature in many standard unicodes which is not an elegant method. About -f, yes. I had not thought about Loki up because I have no reason to use Loki instead of Bump (Without disregarding the Dan's splendid work), Maybe I can add support for Loki verification later. About streams take look here, I'll add more information/instructions in thread soon.

Thanks. :)
[G2 Android Development] RenderBroken:
[MENTION=5859397]ferreirawax[/MENTION]

Very cool work. Can't wait to expand on this and find more use cases!
[G2 Android Development] Sj12345:
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
[G2 Android Development] jeebspawnshop:
[IMG="o.O"]http://i60.tinypic.com/ern9s2.jpg[/IMG]

You're in the WROOOOOONG thread, buddy...
[G2 Android Development] Sj12345:
haha,no I dont buddy, LG exploits can be used for all LG devices (we have root on g2,g3,g4,gflex,gflex2 with the SAME EXPLOIT) He understands how the exploit "bump" works... so I need help from HIM to try this in my devices :)

....... thanks

From Readme.txt

"The flash function uses MSM identifier to detect partition block, Tested only on LG G2, Probably works too with LG G3 and others LG devices powered by Qualcomm."
[G2 Android Development] Sj12345:
Sorry its me again

I have a lot of question???? can you help me? [MENTION=5859397]ferreirawax[/MENTION]

I have two partitions on my phone (aboot and boot), which should be used???

I will dump the correct partition with

dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/boot.img

then use your tool like

cbump /data/media/0/boot.img /data/media/0/cboot.img

flash partition with

dd if=/data/media/0/cboot.img of=/dev/block/bootdevice/by-name/boot

and try to booting up....so if this boot up means it works?

and my next step will be make a TWRP recovery???? I will be carefull cause My phone doesnt have kdz or tot for go back to stock... I only have my own backup from dd