yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] netqer:
Hey,guys. I go for an android kernel porting for my SAMSUNG MSM8X55 phone, similar to GT-i9001. But I don’t know the fundamental technique of kernel debugging.

In addition, without any instruments, I can’t connect to UART. Trying to port kernel based on GT-i9001 cyanogen sources, then I compiled CWM recovery, but it couldn’t boot, and I can’t get any kernel log.

Any one has idea?
[Android Q&A, Help & Troubleshooting] netqer:
uppppppppppppp
[LG G Flex 2] hbcdfpq:
Has anyone had this issue when attempting to do OTA updates?

I had an F510S and I got a prompt to download the V15 software. Upon receiving the message, I unrooted the phone completely using the option in Super SU, even tried a factory reset afterwards..The update will download, restart to go through the installation process, fail, then upon rebooting I would get the message.

The only explanation I can think of is that I uninstalled some of the bloatware that came with the phone using Titanium Backup... does LG check for changes in the system files when doing OTA updates?

I ended up switching over to an H959 rom instead as I realized that I'd need to flash a complete stock rom before trying an OTA update again but it would be nice to know in case I decide to uninstall system apps in the future.
[LG G Flex 2] smouker:
Try updating via LG Pc suit
[LG G Flex 2] hbcdfpq:
PC Suite kept saying that I had the latest version available, even though I had a prompt for an OTA update
[LG G Flex 2] Drissouille:
Exactly the same problem here ! I also think it's caused by the uninstallation of some apps..
[LG G Flex 2] bonebeatz1234:
Must have all apps from factory bloatware and all. That's the only way i learned the hard way in the past . Flag stock tot
[LG G Flex 2] Kidsnd274:
Managed to overcome that by updating using the LGMobile Support Tool. It's like the Sony Update Service but for LG instead.
[LG G Flex 2] Drissouille:
I tried that.. Still no updates available but on my F510L there's the OTA... :crying:
[LG G Flex 2] hbcdfpq:
Have you tried using 'upgrade recovery' from the support tool? When I try it with mine, I get 'no upgrade items to fix'
[LG G Flex 2] Drissouille:
Same thing here
[LG G Flex 2] ShadowRii:
put your device in download mode: power off then keep holding volume op while plugging in the usb cable

then go to the LG tool on your pc and click on upgrade recovery
[LG G Flex 2] Drissouille:
Tried that too... Still the same
[LG G Flex 2] ShadowRii:
that's strange that's how I fixed mine
[LG G Flex 2] jimmydean2010:
Upgrade Recovery

Mine said there are no items to fix when I tried this. I guess I will just be stuck with 4.4.2. I really wanted the lollipop :(
[LG G Flex 2] hbcdfpq:
Has anyone been able to receive OTAs after flashing a KDZ?
[8525, TyTN, MDA Vario II, JasJam ROM Development] srhonkytonk:
First I'd just like to thank everyone in this community that helps me have the coolest and most useful device around. This forum is a wealth of information and there's no way I can describe how much I appreciate the work all of you put in. I do however have a problem that I am hopeful to help get resolved.

I installed LVSW 3.30 Cingular on my phone last night and it had been working fine although earlier I noticed that my ringtones seemed to be stuttering. When I got home today I started to add my programs back to my device since I didnt have a chance to last night. I started with Spb Pocket Plus, Weather, and Phone Suit, and Core Media Player.I then soft reset the device to complete installation and..... I can't get out of bootloader!

I tried soft-reseting the device with the hold ok/power button stylus method,then tried taking the battery out and in. That left me in bootloader. I then tried reinstalling LVSW 3.30 incase I had a bad install the first time but after install finished it stayed in bootloader where I repeated the soft reset. I then consulted the Wiki and tried the method for problem 4, "stuck in bootloader" to no avail. I've also been unable to find a like problem on the forum. I figure I probably have a bad boot sector or something to that effect but dont know how to resolve it. I have a Herm100 SPL-2.10 Hard SPL. I thank anyone in advance who can help me recover my device and sincerely apologize if I missed this topic already being covered.
[8525, TyTN, MDA Vario II, JasJam ROM Development] JasenR:
Here is the thread you need to fix the problem. http://xdaforums.com/showthread.php?t=286755
[8525, TyTN, MDA Vario II, JasJam ROM Development] srhonkytonk:
Thanks I've made a donation to the site for my incompetance
[One (M8) Q&A, Help & Troubleshooting] Fire n mage:
Hello guys, I've had a problem with my phone since flashing 5.0 firmware months ago but I'm just now getting to fixing it.

I have twrp recovery and some 5.0.1 rom that was in beta awhile ago. Everytime I boot into twrp in boots right into fastboot, whatever it's called, after about 5 seconds, so I can't flash any roms, which I think is the problem since it's pretty buggy.

Another thing is that Whenever I charge the phone while it's off, it boots into bootloader and therefore stops charging. Anyway I can fix my recovery without recovery?

This is Verizon htc one m8.

Thanks guys.

Edit: tried using twrp app to reinstall recovery but it boots into bootloader instead.
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
Of course there's a way. Just like the way you first installed a custom recovery. I will give you instructions in case you've forgotten, or if the phone was pre-rooted when you got it.

Download the latest TWRP from here onto your PC.

When the download is finished, rename it to recovery.img and place it into your fastboot folder.

Hook up your phone to your PC, get into ADB/fastboot, and issue the command fastboot flash recovery recovery.img

Then when it's done fastboot reboot

You should now have a working TWRP recovery.
[One (M8) Q&A, Help & Troubleshooting] Fire n mage:
Had to use my brother computer and set it up since I got a mac. Thanks for your reply, and sorry for the double post, I installed via fastboot, and I can confirm the most updated version was pushed to the device, but it still goes right into fastboot after booting into recovery.img

Edit: Did that fastboot erase cache thing in the command prompt and now it works. Thanks for telling me the commands for cmd again!
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
Oh Crap! I forgot to add that one. :silly:Erase cache is obviously needed. Sorry.
[Fire TV General] porkenhimer:
I have been watching Kingo Root for awhile and I just noticed they added Amazon devices to their list of compatible devices. Its a PC root so you would need to attach the fire TV to your PC. I do not have a cord to do so, but its worth a try.

Also, I know windows notices the Fire TV, but not sure what driver is needed. If anyone has any details on an Amazon device driver for windows, please let us know.

If anyone tries Kingo Root, please report back.

Please do not talk about how to get Kingo Root to work if does not work, cause if it doesn't work it just doesn't work. Please no getting mad about anyone else's comments, cause everyone has a voice.

There is also Root Genius that roots a lot of devices, but I do not know if it has worked on any Amazon devices.
[Fire TV General] porkenhimer:
OK here's a quote from Amazon.com about installing the USB drivers for the Fire TV

"The USB driver for the Fire tablets also works with Fire TV."

So I guess all you have to do is install the Fire tablet driver.
[Fire TV General] KLit75:
Not sure I'm much help here. I have rooted aftvs and don't really want to mess with them. However, I did try it once with my aftv stick with no usb drivers installed.

At first it said to enable usb debugging (which pretty sure isn't an option on stick)

Then it recognized the device as aftm

It started checking root status and downloading scripts but it just repeated that loop for about 10 minutes.

I'm willing to try again later. In the mean time if anyone has a link for drivers please post. It'll save time hunting them down. I actually have them on my Mac.

But this does seem more likely to work on the box since you can enable usb debug there.
[Fire TV General] porkenhimer:
Just google "Fire HD USB Driver". Download and install it. If your computer notices your device then USB debugging should be working or it wouldn't notice your devices.
[Fire TV General] KLit75:
Tried again same result except this time I put the stick back in the tv. It actually installed kingo root on it. So I launched it. There's nothing to click and it says usb not connected. So I plugged the usb into my computer. In the kingo app on tv it says "rooting..." but on the pc it just repeats the same loop as last time.

There's no fastboot on stick. The box would at least have a chance of working. I think that's why it can't reboot which it needs to do during the process.
[Fire TV General] porkenhimer:
Well we now know it doesn't work on the stick. Hopefully someone tries it on the Fire TV. I noticed with Kingroot, it would say that your device may need to reboot during rooting, but I also noticed a couple times, not every time though, Kingroot would say it couldn't reboot the device. So I am guessing maybe we stumbled upon something. Maybe part of the process for some devices Is a need to be rebooted during the root process. I have seen videos where some devices would actually reboot during Kingroot and be rooted after the reboot. Maybe a dev with more knowledge on why a device would need to reboot during the root process can give us some info. Maybe the problem with the Fire TV is that Kingroot and other apps like Kingo Root cannot reboot the Fire TV, but that just an idea. It does not sound likely, but anything is possible.
[Fire TV General] porkenhimer:
I have another idea that I am not sure anyone would be willing to try. Maybe someone can run Kingroot or Kingo Root on a rooted device and see what happens. It would have to be someone that has more than one Fire TV incase they messed their device up, but I am sure it could be easily fixed by flashing a pre rooted ROM. Maybe it could give us a better idea of what Kingroot is doing and what it might take to root, if it actually worked on a rooted device.
[Fire TV General] kingvortex:
Maybe this will help with drivers etc

https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-over-usb

It says the stick can connect to adb via USB. Perhaps installing the correct drivers will help.
[Fire TV General] porkenhimer:
Back up the Kingo Root app and uplod the apk and I'll try installing it on the Fire TV box. If you don't know how to backup apps, you can do it with ES File Explorer. It says "app" under the library tab, click it and it will let you backup apps.
[Fire TV General] KLit75:
Just got your post. This is really just the UI for your phone/tablet so you can see the progress and if it works it'll probably warn you not to disconnect the device. But here you go.
[Fire TV General] AFTVnews.com:
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.

Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that [MENTION=5924408]KLit75[/MENTION] posted with the same result.
[Fire TV General] porkenhimer:
I guess its case closed for unrooted Fire TVs and Fire TV Sticks. I am still wondering what kingroot or Kingo Root would do on an already rooted device. I know it sounds kinda risky, but it may actually be able to commplete its process if the device is already rooted.
[Fire TV General] porkenhimer:
Thanks. Didn't work for me either, but it was worth a try.
[Fire TV General] dk1keith:
I had basically the same results except I let mine continue to run. It eventually said "root failed". Connected fine. One note: it did install the correct usb drivers for the Fire TV. I used version 1.3
[Fire TV General] KLit75:
I'm not gonna have time for a little while. Both my aftvs get used a lot so I'm not willing to risk (even if its slight) losing one of them for an undetermined amount of time. If that changes and no one steps up I might reconsider. However, surely there are better eyes than mine when it comes to diagnosing what might be needed.

Here's a thought. You could email AFTVNews. He's got many aftvs, some of which he probably just uses for testing purposes. He'd also be a good resource since he has tons of experience with this device. Actually its possible he already tried this root method.
[Fire TV General] jpeg42:
AFTVNews is responding to this thread. ;);)

Verified it doesn't work. /thread
[Fire TV General] porkenhimer:
He may not have been paying attention to who was posting on the thread, but he was actually talking about asking him to run Kingroot or Kingo Root on an already rooted device, to see what haapens so that maybe we can figure out what they do during the root process. My thinking is that you can write to the system if you are already rooted so maybe Kingroot or Kingo Root can complete the process if the device you run it on is already rooted. Who knows, it may be hugely helpful towards achieving root if someone runs these apps on rooted devices and reports their findings, that is if it completes the process on the rooted device.
[Fire TV General] KLit75:
LOL! Yes it looks like he has indeed. And I'm looking pretty stupid. Am I imagining this or wasn't there a thread started by [MENTION=1694289]porkenhimer[/MENTION] last night? I must've somehow responded to a different thread thinking it was the one from last night. Anyway if he tried it on a rooted device and it doesn't bring about any new info then I guess this topic is dead.

Edit--oh I see. Aftvnews chimed in a few posts back. I was just responding to those who quoted me & didn't keep up with the thread.
[Fire TV General] dk1keith:
I know doing a factory reset was tried on the Fire Stick but I didn't see where it was tried on the Fire TV (i may have just missed it) so I tried it. Did factory reset and tried Kingroot 4.0 and 4.1 with no success. Also tried the PC version of Kingroot and Kingoroot with no success. Just wanted to make sure I tried everything I could to get it to work before giving up on it. Only have one rooted Fire TV so I can't mess with that one.

Just wanted to pass on my results.
[Galaxy S 4 Q&A, Help & Troubleshooting] iBlueee:
Can anyone post the default voltage table for i9505?
[Eee Pad Transformer Q&A, Help & Troubleshooting] QA Bot:
Q&A for [Linux] [Dev] [WIP] *Ubuntu images for Rootbind [TF101 / TF101G][/URL][/B][/SIZE]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [URL="http://cleanimport.xda/index.php?threads/2648862/"][Linux] [IMG] [Dev] [WIP] *Ubuntu images for Rootbind [TF101 / TF101G][/URL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Eee Pad Transformer Q&A, Help & Troubleshooting] fr1s:
Anyone?
[T-Mobile Samsung Galaxy S 4] pitmanr2003:
I have messed my phone up bad trying to get gps to lock. I have come to the conclusion after odin back to stock 4.2 and still cant get lock that its a hardware issue. Now for the life of me I cant get back to lolipop. No matter what i do i cant get my radio to update. is there a place to just download modems? I have never had this much trouble. IM so confused and about firmware, baseband, and roms at this point. Tell me the quickest easiest way to get to rooted GPE with the latest modem from MDL that is what i am back to at this point.
[T-Mobile Samsung Galaxy S 4] serio22:
Have you tried flashing latest firmware? NK2. Don't use MDL modem. To update modem (if you don't want to flash latest firmware) shut phone down manually, reboot into download mode, flash modem, remove battery, reboot straight into download mode and reflash modem. Yes, I believe there is a thread that has modems
[T-Mobile Samsung Galaxy S 4] pitmanr2003:
No I haven't. But It updated ota to nh7 whatever that is
[T-Mobile Samsung Galaxy S 4] Frankenscript:
Ah. Then going back to 4.2 would definitely cause trouble. Do the double NK2 flash and see it you get back to normal.
[T-Mobile Samsung Galaxy S 4] pitmanr2003:
what do you mean by double and you are meaning the whole rom right?
[Nexus 6 Q&A, Help & Troubleshooting] GoodTimesDT:
I bought a Verizon N6 from Verizon a few weeks ago. I unlocked the bootloader, rooted it, installed TWRP and Chroma rom. Everything was working fine with the exception of occasional force closes of Facebook. I then flashed Benzo rom. I noticed days later that I was consistently not getting 4G LTE. From there, I flashed different roms (AOSP, CM, and stocks bases) and the LMY47E bootloader/radio combination all resulting in no 4G. I also tried tinkering with the APN settings and the other settings in Mobile Networks without any luck. I tried creating an APN, but it doesn't save it. Lastly, I tried doing the *228 update and a factory reset without the SIM card in, still no luck.

So in the end, I have no 4G LTE. My phone seems to work like normal, just slower data. (3G data and voice work). If anybody has any suggestions, I really appreciate it!
[Nexus 6 Q&A, Help & Troubleshooting] kenbrownstone:
Mine has done that too..just use wug tool kit ...flash back to stock then reroot and do twrp again....that's what I've had to do ....just don't relock bootloader of course..will take about 2o minutes but you will have lte back....
[Nexus 6 Q&A, Help & Troubleshooting] GoodTimesDT:
I did try that, except I went and relocked the bootloader. Wug didn't install stock recovery though, so I flashed stock, unrooted and relocked the bootloader.. All with TWRP still installed. I thought it was bricked for a moment, but it worked out. Unlocked and rooted again, but still no 4G.
[Nexus 6 Q&A, Help & Troubleshooting] kenbrownstone:
Don't lock boot loader.... No reason for it

---------- Post added at 08:58 PM ---------- Previous post was at 08:56 PM ----------

Why did it not install stock recovery?

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

Was the *228 done with sim card in..???...never dial that again it doe nothing but fry your sim
[Nexus 6 Q&A, Help & Troubleshooting] GoodTimesDT:
I'm not sure why it didn't install stock recovery; I thought it was supposed to too. Maybe I missed something.

And yes, the sim was in with the *228. I was a little skeptical about that afterwards too, but my wife was having signal issues and remedied it with that on her Note 3. So I gave it a go.
[Nexus 6 Q&A, Help & Troubleshooting] kenbrownstone:
Go get a new sim card....when u go back to stock 4g should've came on ...always did for me

..
[Nexus 6 Q&A, Help & Troubleshooting] GoodTimesDT:
Went to Verizon this morning and got a new SIM. 4G LTE back online. Thank you!
[Nexus 6 Q&A, Help & Troubleshooting] kenbrownstone:
Never call *228 on 4g phones....

---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------

Glad u got it running
[Nexus 5 Q&A, Help & Troubleshooting] SrPintas:
Hey there guys and gals

I've posted this before on the helpdesk thread but it's been a while and I've had no luck so I decided to create a new thread to see if more people with the knowledge to help me see this.

Help I think I might have f*cked up =\

So I updated with the OTA as I did last time.

"48B" file as my phone was on build "47D"

Activated usb debugging

Sideloaded with ADB.

All went well till the end. And then I had the "brilliant" idea to format the cache because that was normal procedure when I was using odd roms on my old Motorola Razr M...

It got stuck there forever, so I rebooted the phone thinking... "it's just the cache should be ok" wrong...

Doesn't load into OS and now on Recovery mode it shows repeatedly:

E:failed to mount /cache (Invalid argument)

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

then the same but with /last_log ; /last_install ; /last_kmsg

Tried formating it again...

-- Wiping cache...

E:failed to mount /cache (Invalid argument)

Help! =(

Was it the format cache? shouldn't it only hold temporary stuff not needed for the update nor anything essential to the OS?!

Anything I can do? In particular that doesn't imply wiping my phone's memory as I have important stuff there that I didn't backup this time because nothing bad happens anytime I update with an OTA file anyway :P =(

Sandman-007 was kind enough to try to help but I couldn't move onwards

"Don't worry. This is an easy fix . Just Fastboot flash cache.img from a factory image (one you upgraded from). Then wipe cache in recovery. Reboot"

I tried doing that but couldn't Flash:

"Remote: not supported in locked devices"

Locked bootloader I suppose.

How do I go about unlocking it, and... doesn't it void my warranty ? It still has nearly 1 year left of warranty, I don't wanna void it just in case.

The command: "fastboot oem unlock" is the only unlock "method" I'm aware off, I'm not sure if that's what I need to do, but by doing so the phone wipes all my data =\

How should I proceed?

Thanks in advance for any and all help
[Nexus 5 Q&A, Help & Troubleshooting] chiragkrishna:
some times formating without wiping cache helps.

how did you format your cache???

try this command in bootloader mode

fastboot -u format cache

-u option skips wiping the cache before formating

EDIT: first time boot usually takes a long long time,
[Nexus 5 Q&A, Help & Troubleshooting] Noname017:
You should proceed with "fastboot oem unlock" and then flash cache.img from the 5.1.1 factory image. Your data will probably be gone, but it's the only way to fix this problem. Well, the only one I'm aware of.

You can leave the bootloader unlocked to avoid this kind of problems in the future. You can lock it at any time and it doesn't void the warranty.

EDIT: oh, I never knew about "fastboot -u format cache". This may help too.

Also, I'd suggest to never use the "wipe cache" function in the stock Recovery. Something is broken there. I've used it once, just like you did - and got the same problem. By the way, what Recovery version do you have? It may be not the latest one after updating with "adb sideload".
[Nexus 5 Q&A, Help & Troubleshooting] SrPintas:
Thanks for the help guys!

Gonna try that right away, fingers crossed.

By the way my recovery is version LMY47D. I had no idea it would have problems since it's an official thing and all =\

This came at the worst possible moment too
[Nexus 5 Q&A, Help & Troubleshooting] SrPintas:
Creating filesystem with parameters:

Size: 734003200

Block size: 4096

Blocks per group: 32768

Inodes per group: 7472

Inode size: 256

Journal blocks: 2800

Label:

Blocks: 179200

Block groups: 6

Reserved block group size: 47

Created filesystem with 11/44832 inodes and 5813/179200 blocks

target reported max download size of 1073741824 bytes

sending 'cache' (13348 KB)...

OKAY [ 0.589s]

writing 'cache'...

FAILED (remote: not supported in locked device)

finished. total time: 0.692s

=(

Any other ideas?
[Nexus 5 Q&A, Help & Troubleshooting] 31ken31:
You have to unlock the bootloader first.